+ 6 dB | – | CW carrier |
+
+NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS.
+
+**Table 7.8D-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in 5.2(f)**
+
+| Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|---------------------------------------|
+| 1880-1920 MHz | -30 dBm | -90 dBm | ±3.2 MHz | Narrow band CDMA signal with one code |
+| 1860 - 1880 MHz,
1920 - 1940MHz | -30 dBm | -90 dBm | ±3.2 MHz | Narrow band CDMA signal with one code |
+| 1 - 1860 MHz,
1940 – 12750 MHz | -15 dBm | -90 dBm | – | CW carrier |
+
+NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS.
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.5.0.2.
+
+#### 7.5.2.2.2 Co-location with GSM, DCS, UTRA FDD and/or E-UTRA FDD, UTRA TDD and/or E-UTRA TDD
+
+This additional blocking requirement may be applied for the protection of TDD BS receivers when GSM, DCS, UTRA FDD, E-UTRA FDD, FDD unsynchronized UTRA TDD and/or unsynchronized E-UTRA TDD BTS operating in a different frequency band are co-located with UTRA TDD Wide Area BS.
+
+The blocking performance requirement applies to interfering signals with centre frequency within the ranges specified in the tables below, using a 1MHz step size.
+
+In case this additional blocking requirement is applied, the static reference performance as specified in clause 7.2.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the following parameters.
+
+**Table 7.9A: Additional blocking requirements for Wide Area BS**
+
+| System type operating in the same geographic area | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | Note |
+|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|--------------------------------------------------------------------------|
+| Macro GSM900 | 921 – 960 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| Macro DCS1800 | 1805 – 1880 MHz | +16 dBm | -104 dBm | – | CW carrier | For UTRA TDD BS operating in Band 5.2(f), it applies for 1805 - 1850 MHz |
+| GSM850 or CDMA850 | 869 – 894 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA BS UTRA FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA BS UTRA FDD Band iii or E-UTRA Band 3 | 1805 – 1880 MHz | +16 dBm | -104 dBm | – | CW carrier | For UTRA TDD BS operating in Band 5.2(f), the requirement is FFS |
+| WA BS UTRA FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA UTRA TDD Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA E-UTRA Band 41 | 2496 – 2690 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA E-UTRA Band 42 | 3400 – 3600 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+| WA E-UTRA Band 44 | 703 – 803 MHz | +16 dBm | -104 dBm | – | CW carrier | |
+
+| | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------|----------|---|------------|------------------------------------------------------------------|
+| Pico GSM850 | 869 – 894 | -7 dBm | -104 dBm | – | CW carrier | |
+| Pico GSM900 | 921 – 960 | -7 dBm | -104 dBm | – | CW carrier | |
+| Pico DCS1800 | 1805 – 1880 | -7 dBm | -104 dBm | – | CW carrier | |
+| LA BS UTRA FDD Band I or E-UTRA Band 1 | 2110 – 2170 | -6 dBm | -104 dBm | – | CW carrier | |
+| LA BS UTRA FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | -6 dBm | -104 dBm | – | CW carrier | For UTRA TDD BS operating in Band 5.2(f), the requirement is FFS |
+| LA BS UTRA FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA UTRA TDD Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA E-UTRA Band 41 | 2496 – 2690 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| LA E-UTRA Band 42 | 3400 – 3600 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| WA E-UTRA Band 44 | 703 – 803 MHz | -6 dBm | -104 dBm | – | CW carrier | |
+| NOTE 1: These requirements do not apply when the interfering signal falls within any of the supported uplink operating band or in the 10 MHz frequency range immediately outside the any of the supported uplink operating band. | | | | | | |
+| NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements above. The current state-of-the-art technology does not allow a single generic solution for co-location of UTRA TDD with UTRA FDD or E-UTRA FDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9]. | | | | | | |
+
+**Table 7.10A: Void****Table 7.10A-1: Void**
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.5.1.2.
+
+### 7.5.2.2.3 Void
+
+**Table 7.10B: Void****Table 7.10C: Void**
+
+### 7.5.2.3 7,68 Mcps TDD option
+
+#### 7.5.2.3.1 General requirements
+
+The static reference performance as specified in clause 7.2 shall be met with a wanted and an interfering signal coupled to the BS antenna input using the parameters specified in tables 7.6-1B, 7.7-1B, 7.8-1B, 7.6-2B, 7.7-2B or 7.8-2B, respectively.
+
+**Table 7.6-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a)**
+
+| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal |
+|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1900 - 1920 MHz,
2010 - 2025 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1880 - 1900 MHz,
1990 - 2010 MHz,
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,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier |
+
+**Table 7.7-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 b)**
+
+| Center 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,
1990 - 2010 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier |
+
+**Table 7.8-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 c)**
+
+| Center 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,
1930 - 1950 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier |
+
+**Table 7.9-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 d)**
+
+| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 2570 - 2620 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 2550 - 2570 MHz
2620 - 2640 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 2500 - 2570 MHz
2620 - 2690 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1 - 2550 MHz,
2690 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier |
+
+**Table 7.6-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 a)**
+
+| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal |
+|---------------------------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------|
+| 1900 - 1920 MHz,
2010 - 2025 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1880 - 1900 MHz,
1990 - 2010 MHz,
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,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier |
+
+**Table 7.7-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 b)**
+
+| Center frequency of interfering signal | Interfering signal level | Wanted signal level | 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,
1990 - 2010 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier |
+
+**Table 7.8-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 c)**
+
+| Center frequency of interfering signal | Interfering signal level | Wanted signal level | 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,
1930 - 1950 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier |
+
+**Table 7.9-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 d)**
+
+| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 2570 - 2620 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 2550 - 2570 MHz
2620 - 2640 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 2500 - 2570 MHz
2620 - 2690 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1 - 2550 MHz,
2690 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.5.0.3.
+
+#### 7.5.2.3.2 Void
+
+**Table 7.9B: Void**
+
+**Table 7.10F: Void**
+
+#### 7.5.2.3.3 Void
+
+**Table 7.10G: Void**
+
+**Table 7.10H: Void**
+
+#### 7.5.2.3.4 Co-location with GSM, DCS, UTRA-FDD and/or E-UTRA FDD
+
+This additional blocking requirement may be applied for the protection of TDD BS receivers when GSM, DCS, UTRA-FDD and/or E-UTRA-FDD BTS are co-located with UTRA TDD Wide Area BS.
+
+The blocking performance requirement applies to interfering signals with center frequency within the ranges specified in the tables below, using a 1MHz step size.
+
+In case this additional blocking requirement is applied, the static reference performance as specified in clause 7.2.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the following parameters.
+
+**Table 7.9C: Additional blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a) and 4.2 d)**
+
+| System type operating in the same geographic area | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | Note |
+|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|-------------------------------------------------------------------------|
+| GSM900 | 921 - 960 MHz | +16 dBm | -103 dBm | – | CW carrier | |
+| DCS1800 | 1805 - 1880 MHz | +16 dBm | -103 dBm | – | CW carrier | |
+| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | +13 dBm | -103 dBm | – | CW carrier | This requirement does not apply to UTRA TDD BS operating in Band 5.2(a) |
+| LA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | -6 dBm | -103 dBm | – | CW carrier | This requirement does not apply to UTRA TDD BS operating in Band 5.2(a) |
+
+NOTE 1: These requirements do not apply when the interfering signal falls within the uplink operating band or in the 10 MHz immediately outside the uplink operating band.
+
+NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements above. The current state-of-the-art technology does not allow a single generic solution for co-location of UTRA TDD with UTRA FDD or E-UTRA FDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9].
+
+## 7.5.3 Test purpose
+
+### 7.5.3.1 3,84 Mcps TDD option
+
+The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at frequency offsets of 10 MHz or more, without undue degradation of its sensitivity.
+
+### 7.5.3.2 1,28 Mcps TDD option
+
+The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at frequency offsets of 3,2 MHz or more, without undue degradation of its sensitivity.
+
+### 7.5.3.3 7,68 Mcps TDD option
+
+The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at frequency offsets of 20 MHz or more, without undue degradation of its sensitivity.
+
+## 7.5.4 Method of test
+
+### 7.5.4.1 Initial conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested for single carrier: $M$ ; see subclause 5.3. The BS shall be configured to operate as close to the centre of the operating band as possible.
+
+RF bandwidth positions to be tested for multi-carrier: $M_{\text{RFBW}}$ in single band operation, see subclause 5.3; $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see subclause 5.3;
+
+In addition, in multi-band operation:
+
+- For $B_{\text{RFBW\_T}}^{\text{RFBW}}$ , out-of-band blocking testing above the highest operating band may be omitted.
+ - For $B_{\text{RFBW\_T}}^{\text{RFBW}}$ , out-of-band blocking testing below the lowest operating band may be omitted.
+- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and a signal generator to the antenna connector of one Rx port.
+ - (2) Terminate or disable any other Rx port not under test.
+ - (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. For a BS supporting multi-carrier operation, generate the wanted signal according to the applicable test configuration (see subclause 5.20 and 5.21) using the UL reference measurement channel in Annex A.2.1 on all carriers for the BS under test. The level of the UE simulator signal measured at the BS antenna connector shall be set according to subclause 7.5.2.2.
+
+### 7.5.4.2 Procedure
+
+#### 7.5.4.2.1 3,84 Mcps TDD option
+
+- (1) Set the signal generator to produce an interfering signal at a frequency offset $F_{\text{uw}}$ from the assigned channel frequency of the wanted signal which is given by
+
+$$F_{\text{uw}} = \pm (n \times 1 \text{ MHz}),$$
+
+where $n$ shall be increased in integer steps from $n = 10$ up to such a value that the center frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the antenna connector shall be set in dependency of its center frequency, as specified in tables 7.6 to 7.10. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 3,84 Mcchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see tables 7.6 to 7.10.
+
+- (2) Measure the BER of the wanted signal at the BS receiver.
+
+- (3) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) and (2).
+
+#### 7.5.4.2.2 1,28 Mcps TDD option
+
+- (1) Set the signal generator to produce an interfering signal at a frequency offset Fuw from the assigned channel frequency of the wanted signal which is given by
+
+$$Fuw = \pm(3,2 \pm n) \times 1 \text{ MHz}$$
+
+where n shall be increased in integer steps from n = 0 up to such a value that the center frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the antenna connector shall be set in dependency of its center frequency, as specified in tables 7.6A to 7.10A. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 1,28 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see tables 7.6A to 7.10A.
+
+- (2) Measure the BER of the wanted signal at the BS receiver.
+- (3) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) and (2).
+
+In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply:
+
+- (4) For single band tests, repeat the steps above per involved band with no carrier activated in the other band.
+- (5) The interfering signal shall first be applied on the same port as the wanted signal. The test shall be repeated with the interfering signal applied on the other port (if any) mapped to the same receiver as the wanted signal. Any antenna connector with no signal applied in case of single-band or multi-band test shall be terminated.
+- (6) Repeat step (5) with the wanted signal for the other band(s) applied on the respective port(s).
+
+#### 7.5.4.2.3 7,68 Mcps TDD option
+
+- (1) Set the signal generator to produce an interfering signal at a frequency offset Fuw from the assigned channel frequency of the wanted signal which is given by
+
+$$Fuw = \pm (n \times 1 \text{ MHz}),$$
+
+where n shall be increased in integer steps from n = 20 up to such a value that the center frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the antenna connector shall be set in dependency of its center frequency, as specified in tables 7.6B to 7.10F. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 7,68 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see subclause tables 7.6B to 7.10F.
+
+- (2) Measure the BER of the wanted signal at the BS receiver.
+- (3) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) and (2).
+
+### 7.5.5 Test Requirements
+
+NOTE 1: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+In all measurements made according to subclause 7.5.4.2, the BER shall not exceed 0,001.
+
+NOTE 2: Annex F describes the procedure for BER tests taking into account the statistical consequence of frequent repetition of BER measurements within the blocking test. The consequence is: a DUT exactly on the limit may fail due to the statistical nature 2.55 times(mean value) in 12750 BER measurements using the predefined wrong decision probability of 0.02%. If the fail cases are $\leq 12$ , it is allowed to repeat the fail cases 1 time before the final verdict.
+
+## 7.6 Intermodulation characteristics
+
+### 7.6.1 Definition and applicability
+
+Third and higher order mixing of 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.
+
+### 7.6.2 Minimum Requirements
+
+#### 7.6.2.1 3,84 Mcps TDD option
+
+The static reference performance as specified in clause 7.2 should be met when the following signals are coupled to the BS antenna input.
+
+- A wanted signal at the assigned channel frequency, with mean power 6 dB above the static reference level.
+- Two interfering signals with the parameters specified in table 7.11.
+
+**Table 7.11: Parameters of the interfering signals for intermodulation characteristics testing**
+
+| Interfering Signal mean power | | Offset | Type of Interfering Signal |
+|-------------------------------|---------------|--------|----------------------------|
+| Wide Area BS | Local Area BS | | |
+| - 48 dBm | - 38 dBm | 10 MHz | CW signal |
+| - 48 dBm | - 38 dBm | 20 MHz | WCDMA signal with one code |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.6.1.1.
+
+#### 7.6.2.2 1,28 Mcps TDD option
+
+The static reference performance as specified in clause 7.2 should be met when the following signals are coupled to the BS antenna input.
+
+- A wanted signal at the assigned channel frequency, with mean power 6 dB above the static reference level.
+- Two interfering signals with the parameters specified in table 7.11A.
+
+The blocking requirement is always applicable outside the Base Station RF bandwidth or maximum radio bandwidth edges. The interfering signal offset is defined relative to the lower (upper) or maximum radio bandwidth edges.
+
+For BS capable of multi-band operation, the requirement applies in addition inside any inter RF bandwidth gap, in case the gap size is at least 11.2MHz. The CW interfering signal offset is defined relative to lower/upper RF bandwidth edges inside the inter RF bandwidth gap and is equal to -2.4MHz/+2.4MHz, respectively. The modulated interfering signal offset is defined relative to lower/upper RF bandwidth edges inside the inter RF bandwidth gap and is equal to -5.6MHz/+5.6MHz, respectively.
+
+**Table 7.11A: Parameters of the interfering signals for intermodulation characteristics testing for 1,28 Mcps TDD**
+
+| Interfering Signal mean power | | Offset | Type of Interfering Signal |
+|-------------------------------|-------------------------|----------|------------------------------------|
+| Wide Area BS | Local Area BS / Home BS | | |
+| - 48 dBm | - 38 dBm | ±3,2 MHz | CW signal |
+| - 48 dBm | - 38 dBm | ±6,4 MHz | 1,28 Mcps TDD signal with one code |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.6.1.2.
+
+#### 7.6.2.3 7,68 Mcps TDD option
+
+The static reference performance as specified in clause 7.2 should be met when the following signals are coupled to the BS antenna input.
+
+- A wanted signal at the assigned channel frequency, with mean power 6 dB above the static reference level.
+- Two interfering signals with the parameters specified in table 7.11B.
+
+**Table 7.11B: Parameters of the interfering signals for intermodulation characteristics testing**
+
+| Interfering Signal mean power | | Offset | Type of Interfering Signal |
+|-------------------------------|---------------|--------|----------------------------|
+| Wide Area BS | Local Area BS | | |
+| - 48 dBm | - 38 dBm | 20 MHz | CW signal |
+| - 48 dBm | - 38 dBm | 40 MHz | WCDMA signal with one code |
+
+The normative reference for this requirement is subclause 7.6.1.3.
+
+## 7.6.3 Test purpose
+
+The test purpose is to verify the ability of the BS receiver to inhibit the generation of intermodulation products in its non-linear elements caused by the presence of two high-level interfering signals at frequencies with a specific relationship to the frequency of the wanted signal.
+
+## 7.6.4 Method of test
+
+### 7.6.4.1 Initial conditions
+
+#### 7.6.4.1.1 3,84 Mcps TDD option
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and two signal generators to the antenna connector of one Rx port.
+- (2) Terminate or disable any other Rx port not under test.
+- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. The level of the UE simulator signal measured at the BS antenna connector shall be set to 6 dB above the reference sensitivity level specified in subclause 7.2.2.
+- (4) Set the first signal generator to produce a CW signal with a level measured at the BS antenna connector as specified in table 7.11..
+- (5) Set the second signal generator to produce an interfering signal equivalent to a wideband CDMA signal with one code of chip frequency 3,84 MHz, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The level of the signal measured at the BS antenna connector shall be set as specified in table 7.11.
+
+#### 7.6.4.1.2 1,28 Mcps TDD option
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested for single carrier: B, M and T; see subclause 5.3.
+
+RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , and $T_{RFBW}$ in single band operation, see subclause 5.3; $B_{RFBW\_T}{}_{RFBW}$ and $B'_{RFBW\_T}{}_{RFBW}$ in multi-band operation, see subclause 4.7.1;
+
+- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and two signal generators to the antenna connector of one Rx port.
+- (2) Terminate or disable any other Rx port not under test.
+- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. For a BS supporting multi-carrier operation, generate the wanted signal using the applicable test configuration specified in subclause 5.20 and 5.21, and the UL reference measurement channel in Annex A.2.1 shall be used on all carriers for the BS under test. The level of the UE simulator signal measured at the BS antenna connector shall be set to 6 dB above the reference sensitivity level specified in subclause 7.2.2.
+
+- (4) Set the first signal generator to produce a CW signal with a level measured at the BS antenna connector as specified in table 7.11A.
+- (5) Set the second signal generator to produce an interfering signal equivalent to a wideband CDMA signal with one code of chip frequency 1,28 MHz, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The level of the signal measured at the BS antenna connector shall be set as specified in table 7.11A.
+
+#### 7.6.4.1.3 7,68 Mcps TDD option
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and two signal generators to the antenna connector of one Rx port.
+- (2) Terminate or disable any other Rx port not under test.
+- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. The level of the UE simulator signal measured at the BS antenna connector shall be set to 6 dB above the reference sensitivity level specified in subclause 7.2.2.
+- (4) Set the first signal generator to produce a CW signal with a level measured at the BS antenna connector as specified in table 7.11B.
+- (5) Set the second signal generator to produce an interfering signal equivalent to a wideband CDMA signal with one code of chip frequency 7,68 MHz, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The level of the signal measured at the BS antenna connector shall be set as specified in table 7.11B.
+
+#### 7.6.4.2 Procedure
+
+##### 7.6.4.2.1 3,84 Mcps TDD option
+
+- (1) The frequency of the first and the second signal generator shall be set to 10 MHz and 20 MHz, respectively, above the assigned channel frequency of the wanted signal.
+- (2) Measure the BER of the wanted signal at the BS receiver.
+- (3) The frequency of the first and the second signal generator shall be set to 10 MHz and 20 MHz, respectively, below the assigned channel frequency of the wanted signal.
+- (4) Measure the BER of the wanted signal at the BS receiver.
+- (5) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) to (4).
+
+##### 7.6.4.2.2 1,28 Mcps TDD option
+
+- (1) Measure the BER of the wanted signal at the BS receiver.
+- (2) Interchange the connections of the BS Rx ports and repeat the measurements.
+
+In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply:
+
+- (3) For single band tests, repeat the steps above per involved band with no carrier activated in the other band.
+- (4) The interfering signal shall first be applied on the same port as the wanted signal. The test shall be repeated with the interfering signal applied on the other port (if any) mapped to the same receiver as the wanted signal. Any antenna connector with no signal applied in case of single-band or multi-band test shall be terminated.
+- (5) Repeat step 4) with the wanted signal for the other band(s) applied on the respective port(s)
+
+##### 7.6.4.2.3 7,68 Mcps TDD option
+
+- (1) The frequency of the first and the second signal generator shall be set to 20 MHz and 40 MHz, respectively, above the assigned channel frequency of the wanted signal.
+- (2) Measure the BER of the wanted signal at the BS receiver.
+
+- (3) The frequency of the first and the second signal generator shall be set to 20 MHz and 40 MHz, respectively, below the assigned channel frequency of the wanted signal.
+- (4) Measure the BER of the wanted signal at the BS receiver.
+- (5) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) to (4).
+
+## 7.6.5 Test Requirements
+
+NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+The BER measured according subclause 7.6.4.2 to shall not exceed 0,001.
+
+## 7.7 Spurious emissions
+
+### 7.7.1 Definition and applicability
+
+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 connectors. For BS equipped with only a single antenna connector for both transmitter and receiver, the requirements of subclause 6.6.3 shall apply to this port, and this test need not be performed.
+
+### 7.7.2 Minimum Requirements
+
+#### 7.7.2.1 3,84 Mcps TDD option
+
+The power of any spurious emission shall not exceed the values given in table 7.12.
+
+**Table 7.12: Receiver spurious emission requirements**
+
+| Band | Maximum level | Measurement Bandwidth | Note |
+|-----------------------|---------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| 30 MHz - 1 GHz | -57 dBm | 100 kHz | |
+| 1 GHz - 1,9 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 BS |
+| 1,900 - 1,980 GHz | -78 dBm | 3,84 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 BS |
+| 1,980 - 2,010 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 BS |
+| 2,010 - 2,025 GHz | -78 dBm | 3,84 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 BS |
+| 2,025 - 2,500 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 BS |
+| 2,500 - 2,620 | -78 dBm | 3,84 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 BS |
+| 2,620 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 BS |
+
+**Table 7.12AA: Additional receiver spurious emission requirements**
+
+| Band | Maximum level | Measurement Bandwidth | Note |
+|----------------------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 815 MHz - 850 MHz
1749.9 MHz - 1784.9 MHz | -78 dBm | 3,84 MHz | Applicable in Japan
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 BS |
+
+In addition to the requirements in table 7.12 and 7.12AA, the co-existence requirements for co-located base stations in subclauses 6.6.3.2.2.2, 6.6.3.2.3.2 and 6.6.3.2.4.2 may also be applied.
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.7.1.1.
+
+### 7.7.2.2 1,28 Mcps TDD option
+
+The power of any spurious emission shall not exceed the values given in table 7.12A.
+
+For BS capable of multi-band operation, the exclusion applies for all supported operating bands.
+
+For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the excluded frequency range is only applicable for the operating band supported on each antenna connector.
+
+**Table 7.12A: General receiver spurious emission minimum requirements**
+
+| 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 4 MHz below the first carrier frequency and 4 MHz above the last carrier frequency used by the BS. |
+
+**Table 7.12A-1: Void****Table 7.12A-2: Void**
+
+In addition to the requirements in table 7.12A, the power of any spurious emission shall not exceed the levels specified for Co-existence with other systems in the same geographical area in subclause 6.6.3.2.2.1 and 6.6.3.5.2.2.2. In addition, the co-existence requirements for co-located base stations specified in subclause 6.6.3.2.5.1.2 and 6.6.3.2.5.2.2 may also be applied.
+
+The normative reference for this requirement is TS 25.105 [1] subclause 7.7.1.2.
+
+### 7.7.2.3 7,68 Mcps TDD option
+
+The power of any spurious emission shall not exceed the values given in table 7.12B and table 7.12BB.
+
+**Table 7.12B: Receiver spurious emission requirements**
+
+| Band | Maximum level | Measurement Bandwidth | Note |
+|----------------------------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| 30 MHz - 1 GHz | -57 dBm | 100 kHz | |
+| 1 GHz - 1.9 GHz and
1.98 GHz - 2.01 GHz
2.025 GHz - 2.5 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
2.01 GHz - 2.025 GHz
2.5 GHz - 2.62 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.62 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. |
+
+**Table 7.12BB: Additional receiver spurious emission requirements**
+
+| Band | Maximum level | Measurement Bandwidth | Note |
+|-----------------------------------------------------------------------|---------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 815 MHz - 850 MHz
1427.9MHz - 1452.9MHz
1749.9 MHz - 1784.9 MHz | -78 dBm | 3,84 MHz | Applicable in Japan
With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. |
+
+In addition to the requirements in table 7.12B and 7.12BB, the co-existence requirements for co-located base stations specified in subclause 6.6.3.2.2.2, 6.6.3.2.3.2 and 6.6.3.2.4.2 may also be applied.
+
+The normative reference for this requirement is subclause 6.3.7.1.
+
+## 7.7.3 Test purpose
+
+The test purpose is to verify the ability of the BS to limit the interference caused by receiver spurious emissions to other systems.
+
+## 7.7.4 Method of test
+
+### 7.7.4.1 Initial conditions
+
+#### 7.7.4.1.0 General test conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested for single carrier: M; see subclause 5.3.
+
+RF bandwidth positions to be tested for multi-carrier: $M_{RFBW}$ in single band operation, see sub-clause 5.3; $B_{RFBW\_T'RFBW}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see subclause 5.3;
+
+#### 7.7.4.1.1 3,84 Mcps TDD option
+
+- (1) Connect the measuring equipment to the antenna connector of one BS Rx port.
+- (2) Terminate or disable any other BS Rx port not under test.
+- (3) Set the BS receiver to operational mode.
+- (4) Set the BS to transmit a signal with parameters according to table 7.13.
+- (5) Terminate the Tx port(s).
+
+**Table 7.13: Parameters of the transmitted signal for Rx spurious emissions test**
+
+| Parameter | Value/description |
+|---------------------------------------------|------------------------------------------------------------------------------------|
+| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. |
+| Time slot carrying SCH | TS0 |
+| Time slots under test | TS i, i even and non zero |
+| BS output power setting | PRAT |
+| Number of DPCH in each time slot under test | 9 |
+| Power of each DPCH | 1/9 of Base Station output power |
+| Data content of DPCH | real life (sufficient irregular) |
+
+#### 7.7.4.1.2 1,28 Mcps TDD option
+
+- (1) Connect the measuring equipment to the antenna connector of one BS Rx port under test.
+- (2) Terminate or disable any other BS Rx port not under test.
+- (3) For a BS declared to be capable of single carrier operation only, set the BS to transmit a signal with parameters according to table 7.13A at manufacturer's declared output power, PRAT.
+
+For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 7.13A on all carriers using the applicable test configuration and corresponding power setting for receiver test, as specified in subclause 5.20 and 5.21.
+
+- (4) Terminate the Tx port(s).
+
+**Table 7.13A: Parameters of the transmitted signal for Rx spurious emissions test for 1,28 Mcps TDD**
+
+| Parameter | Value/description |
+|---------------------------------------------|----------------------------------------------------------------------------------------|
+| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. |
+| Time slots under test | TS1, TS2 and TS3 |
+| BS output power setting | PRAT |
+| Number of DPCH in each time slot under test | 8 |
+| Power of each DPCH | 1/8 of Base Station output power |
+| Data content of DPCH | real life (sufficient irregular) |
+
+#### 7.7.4.1.3 7,68 Mcps TDD option
+
+- (1) Connect the measuring equipment to the antenna connector of one BS Rx port.
+- (2) Terminate or disable any other BS Rx port not under test.
+- (3) Set the BS receiver to operational mode.
+- (4) Set the BS to transmit a signal with parameters according to table 7.13B.
+- (5) Terminate the Tx port(s).
+
+**Table 7.13B: Parameters of the transmitted signal for Rx spurious emissions test**
+
+| Parameter | Value/description |
+|---------------------------------------------|---------------------------------------------------------------------------------|
+| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. |
+| Time slot carrying SCH | TS0 |
+| Time slots under test | TS i, i even and non zero |
+| BS output power setting | PRAT |
+| Number of DPCH in each time slot under test | 9 |
+| Power of each DPCH | 1/9 of Base Station output power |
+| Data content of DPCH | real life (sufficient irregular) |
+
+## 7.7.4.2 Procedure
+
+### 7.7.4.2.1 3,84 Mcps TDD option
+
+- (1) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.14. The characteristics of the measurement filter with the bandwidth 3,84 MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.14 and table 7.14AA. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot.
+- (2) If the BS is equipped with more than one Rx port, interchange the connections of the BS Rx ports and repeat the measurement according to (1).
+
+**Table 7.14: Measurement equipment settings**
+
+| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode |
+|-------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| 30 MHz - 1 GHz | 100 kHz | 100 kHz | 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 BS | true RMS |
+| 1 GHz - 1,900 GHz | 1 MHz | 1 MHz | | |
+| 1,900 GHz - 1,980 GHz | 3,84 MHz | 200 kHz | | |
+| 1,980 GHz - 2,010 GHz | 1 MHz | 1 MHz | | |
+| 2,010 GHz - 2,025 GHz | 3,84 MHz | 200 kHz | | |
+| 2,025 GHz - 2,500 GHz | 1 MHz | 1 MHz | | |
+| 2,500 GHz - 2,620 GHz | 3,84 MHz | 200 kHz | | |
+| 2,620 GHz - 12,75 GHz | 1 MHz | 1 MHz | | |
+
+**Table 7.14 AA: Additional measurement equipment settings**
+
+| Band | Measurement Bandwidth | Step Width | Note | Detection mode |
+|----------------------------------------------|-----------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| 815 MHz - 850 MHz
1749,9 MHz - 1784,9 MHz | 3,84 MHz | 200 kHz | Applicable in Japan
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 BS | True RMS |
+
+### 7.7.4.2.2 1,28 Mcps TDD option
+
+- (1) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.14A. The characteristics of the measurement filter with the bandwidth 1,28 MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.14A. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot.
+- (2) Repeat the test for the other port(s), which was (were) terminated.
+
+In addition, for a multi-band capable BS, the following steps shall apply:
+
+- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band.
+- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated.
+
+**Table 7.14A: Measurement equipment settings**
+
+| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode |
+|-------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| 30 MHz - 1 GHz | 100 kHz | 100 kHz | With the exception of frequencies between 4 MHz below the first carrier frequency and 4 MHz above the last carrier frequency used by the BS | true RMS |
+| 1 GHz - 1,880 GHz | 1 MHz | 1 MHz | | |
+| 1,880 GHz - 1,980 GHz | 1,28 MHz | 200 kHz | | |
+| 1,980 GHz - 2,010 GHz | 1 MHz | 1 MHz | | |
+| 2,010 GHz - 2,025 GHz | 1,28 MHz | 200 kHz | | |
+| 2,025 – 2,300 GHz | 1 MHz | 1 MHz | | |
+| 2,300 GHz -2,400 GHz | 1,28 MHz | 200 kHz | | |
+| 2,400 GHz -2,500 GHz | 1 MHz | 1 MHz | | |
+| 2,500 GHz - 2,620GHz | 1,28 MHz | 200 kHz | | |
+| 2,620 GHz - 12,75 GHz | 1 MHz | 1 MHz | | |
+
+### 7.7.4.2.3 7,68 Mcps TDD option
+
+- (1) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.14B. The characteristics of the measurement filter with the bandwidth 7,68 MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.14B and 7.14BB. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot.
+- (2) If the BS is equipped with more than one Rx port, interchange the connections of the BS Rx ports and repeat the measurement according to (1).
+
+**Table 7.14B: Measurement equipment settings**
+
+| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode |
+|-------------------------|-----------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| 30 MHz - 1 GHz | 100 kHz | 100 kHz | With the exception of frequencies between 25 MHz below the first carrier frequency and 25 MHz above the last carrier frequency used by the BS | true RMS |
+| 1 GHz - 1,900 GHz | 1 MHz | 1 MHz | | |
+| 1,900 GHz - 1,980 GHz | 7,68 MHz | 200 kHz | | |
+| 1,980 GHz - 2,010 GHz | 1 MHz | 1 MHz | | |
+| 2,010 GHz - 2,025 GHz | 7,68 MHz | 200 kHz | | |
+| 2,025 GHz - 12,75 GHz | 1 MHz | 1 MHz | | |
+
+**Table 7.14 BB: Additional measurement equipment settings**
+
+| Band | Measurement bandwidth | Step width | Note | Detection mode |
+|-----------------------------------------------------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| 815 MHz - 850 MHz
1427.9MHz - 1452.9MHz
1749.9 MHz - 1784.9 MHz | 3,84 MHz | 200 kHz | Applicable in Japan
With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | true RMS |
+
+## 7.7.5 Test Requirements
+
+NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+The spurious emissions measured according to subclause 7.7.4.2 shall not exceed the limits specified in subclause 7.7.2.
+
+## 8 Performance requirements
+
+### 8.1 General
+
+Performance requirements for the BS are specified for the measurement channels defined in Annex A and the propagation conditions in Annex B. The requirements only apply to those measurement channels that are supported by the base station. The performance requirements for the high speed train conditions defined in Annex B.3 are optional. All Bit Error Ratio (BER) and Block Error ratio (BLER) measurements shall be carried out according to the general rules for statistical testing defined in ITU-T Recommendation O.153 [10] and Annex F.
+
+Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a BS supporting MC-HSUPA are defined in terms of single carrier requirements.
+
+The characteristics of the white noise source, simulating interference from other cells ( $I_{oc}$ ), shall comply with the AWGN interferer definition in subclause 5.18.
+
+The requirements only apply to a base station with dual receiver antenna diversity unless otherwise stated. The required $\hat{I}_{or}/I_{oc}$ shall be applied separately at each antenna port.
+
+**Table 8.1: Summary of Base Station performance targets**
+
+| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2** | Multi-path Case 3** | High speed train** |
+|------------------|---------------------|------------------------------|------------------------------|------------------------------|------------------------------------------|------------------------------|
+| | | Performance metric | | | | |
+| DCH | 12,2 kbps | BLER < $10^{-2}$ | BLER < $10^{-2}$ | BLER < $10^{-2}$ | BLER < $10^{-2}$ | BLER < $10^{-2}$ |
+| | 64 kbps | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ , $10^{-3}$ | BLER < $10^{-1}$ , $10^{-2}$ |
+| | 144 kbps | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ , $10^{-3}$ | - |
+| | 384 kbps | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ , $10^{-3}$ | - |
+
+\*Note: Optional condition, not applicable for all BSs.
+\*\*Note: Not applicable for Home BS
+
+## 8.2 Demodulation in static propagation conditions
+
+### 8.2.1 Demodulation of DCH
+
+#### 8.2.1.1 Definition and applicability
+
+The performance requirement of DCH in static propagation conditions is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station.
+
+In this subclause, different requirements shall apply to Wide Area BS, Local Area BS and Home BS.
+
+#### 8.2.1.2 Minimum Requirements
+
+##### 8.2.1.2.1 3,84 Mcps TDD option
+
+For the parameters specified in table 8.2, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.3. These requirements are applicable for TFCS size 16.
+
+**Table 8.2: Parameters in static propagation conditions**
+
+| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|-----------------------------------------|---------------|--------------|-------------------|-------------------|-------------------|--------|
+| Number of DPCH o | | | 6 | 4 | 0 | 0 |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | | DB | -9 | -9,5 | - | - |
+| I oc | Wide Area BS | dBm/3,84 MHz | -89 | | | |
+| | Local Area BS | dBm/3,84 MHz | -74 | | | |
+| Cell Parameter* | | | 0,1 | | | |
+| DPCH Channelization Codes* | | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) |
+| DPCH o Channelization Codes* | | C(k,Q) | C(i,16) 3 ≤ i ≤ 8 | C(i,16) 6 ≤ i ≤ 9 | - | - |
+| Information Data Rate | | Kbps | 12,2 | 64 | 144 | 384 |
+
+\*Note: Refer to TS 25.223 for definition of channelization codes and cell parameter.
+
+**Table 8.3: Performance requirements in AWGN channel.**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|------------------|
+| 1 | -2,0 | 10 -2 |
+| 2 | -0,4 | 10 -1 |
+| | -0,1 | 10 -2 |
+| 3 | -0,2 | 10 -1 |
+| | 0,1 | 10 -2 |
+| 4 | -0,8 | 10 -1 |
+| | -0,6 | 10 -2 |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.2.1.1.1.
+
+#### 8.2.1.2.2 1,28 Mcps TDD option
+
+For the parameters specified in table 8.2A, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.3A. These requirements are applicable for TFCS size 16.
+
+**Table 8.2A: Parameters in static propagation conditions for 1,28 Mcps TDD**
+
+| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|------------------------------------|---------------|--------------|--------|--------|--------|--------|
+| Number of DPCH o | | | 4 | 1 | 1 | 0 |
+| Spread factor of DPCH o | | | 8 | 8 | 8 | |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | | dB | -7 | -7 | -7 | - |
+| I oc | Wide Area BS | dBm/1,28 MHz | -91 | | | |
+| | Local Area BS | dBm/1,28 MHz | -77 | | | |
+| | Home BS | dBm/1,28 MHz | -82 | | | |
+| Information Data Rate | | kbps | 12,2 | 64 | 144 | 384 |
+
+**Table 8.3A: Performance requirements in AWGN channel for 1,28 Mcps TDD**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|------------------|
+| 1 | 0.6 | 10 -2 |
+| 2 | -0.9 | 10 -1 |
+| | -0.4 | 10 -2 |
+| 3 | -0.3 | 10 -1 |
+| | -0.1 | 10 -2 |
+| 4 | 0.6 | 10 -1 |
+| | 0.8 | 10 -2 |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.2.1.1.2.
+
+### 8.2.1.2.3 7,68 Mcps TDD option
+
+For the parameters specified in table 8.2B, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.3B. These requirements are applicable for TFCS size 16.
+
+**Table 8.2B: Parameters in static propagation conditions**
+
+| Parameters | | Unit | Test 1 |
+|--------------------------------------------------------------------------------------|---------------|--------------|------------------------|
+| Number of DPCH 0 | | | 14 |
+| | | dB | -12 |
+| I oc | Wide Area BS | dBm/7.68 MHz | -89 |
+| | Local Area BS | dBm/7.68 MHz | -74 |
+| Cell Parameter* | | | 0,1 |
+| DPCH Channelization Codes* | | C(k,Q) | C(1, 16) |
+| DPCH 0 Channelization Codes* | | C(k,Q) | C(i, 32)
3 ≤ i ≤ 16 |
+| Information Data Rate | | kbps | 12.2 |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.3B: Performance requirements in AWGN channel.**
+
+| Test Number | [dB] | BLER |
+|-------------|------|------------------|
+| 1 | -2.0 | 10 -2 |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.2.1.1.3.
+
+### 8.2.1.3 Test purpose
+
+The test purpose is to verify the ability of the BS to receive a prescribed test signal under static propagation conditions with a BLER not exceeding a specified limit. Within the wanted channel, intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver to extract the wanted signal from the interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part.
+
+### 8.2.1.4 Method of test
+
+#### 8.2.1.4.1 Initial conditions
+
+##### 8.2.1.4.1.0 General test conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+##### 8.2.1.4.1.1 3,84 Mcps TDD option
+
+Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.2.
+
+##### 8.2.1.4.1.2 1,28 Mcps TDD option
+
+Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0
+
+generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.2A.
+
+#### 8.2.1.4.1.3 7,68 Mcps TDD option
+
+Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.2B.
+
+#### 8.2.1.4.2 Procedure
+
+##### 8.2.1.4.2.1 3,84 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.2.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.4.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.4.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.4: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | |
+|-------------|----------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------|
+| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | |
+| | | | | | | | Wide Area BS | Local Area BS |
+| 1 | $10^{-2}$ | 6 | -100,0 | -85 | DPCH 1 | 8 | -97,0 | -82,0 |
+| 2 | $10^{-1}$ | 4 | -98,9 | -83,9 | DPCH 1 | 16 | -98,9 | -83,9 |
+| | | | | | DPCH 2 | 4 | -92,9 | -77,9 |
+| | $10^{-2}$ | 4 | -98,6 | -83,6 | DPCH 1 | 16 | -98,6 | -83,6 |
+| | | | | | DPCH 2 | 4 | -92,6 | -77,6 |
+| 3 | $10^{-1}$ | 0 | - | - | DPCH 1 | 16 | -98,7 | -83,7 |
+| | | | | | DPCH 2 | 2 | -89,7 | -74,7 |
+| | $10^{-2}$ | 0 | - | - | DPCH 1 | 16 | -98,4 | -83,4 |
+| | | | | | DPCH 2 | 2 | -89,4 | -74,4 |
+| 4 | $10^{-1}$ | 0 | - | - | DPCH 1 | 2 | -89,8 | -74,8 |
+| | $10^{-2}$ | 0 | - | - | DPCH 1 | 2 | -89,6 | -74,6 |
+
+##### 8.2.1.4.2.2 1,28 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.2A.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.4A.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference
+
+measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.4A.
+
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.4A: Parameters of DPCH0 and the wanted signal for 1,28 Mcps TDD**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | | Parameters of the wanted signal | | | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------|---------------------------------|----|--------------------------------------------------|---------------|---------|
+| | | | Wide Area BS | Local Area BS | Home BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | |
+| | | | | | | | | Wide Area BS | Local Area BS | Home BS |
+| 1 | 10 -2 | 4 | -97.4 | -83.4 | -88.4 | DPCH 1 | 8 | -97.4 | -83.4 | -88.4 |
+| 2 | 10 -1 | 1 | -98.9 | -84.9 | -89.9 | DPCH 1 | 2 | -92.9 | -78.9 | -83.9 |
+| | 10 -2 | 1 | -98.4 | -84.4 | -89.4 | DPCH 1 | 2 | -92.5 | -78.5 | -83.5 |
+| 3 | 10 -1 | 1 | -98.3 | -84.3 | -89.3 | DPCH 1 | 2 | -92.3 | -78.3 | -83.3 |
+| | 10 -2 | 1 | -98.1 | -84.1 | -89.1 | DPCH 1 | 2 | -92.1 | -78.1 | -83.1 |
+| 4 | 10 -1 | 0 | - | - | | DPCH 1 | 16 | -99.9 | -85.9 | -90.9 |
+| | | | | | | DPCH 2 | 2 | -90.9 | -76.9 | -81.9 |
+| | 10 -2 | 0 | - | - | | DPCH 1 | 16 | -99.7 | -85.7 | -90.7 |
+| | | | | | | DPCH 2 | 2 | -90.7 | -76.7 | -81.7 |
+
+#### 8.2.1.4.2.3 7,68 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.2B.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.4B.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.4B.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.4B: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------|
+| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | |
+| | | | | | | | Wide Area BS | Local Area BS |
+| 1 | 10 -2 | 14 | -103,0 | -88 | DPCH 1 | 16 | -100,0 | -85,0 |
+
+#### 8.2.1.5 Test Requirements
+
+NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+##### 8.2.1.5.1 3,84 Mcps TDD option
+
+The BLER measured according to subclause 8.2.1.4.2 shall not exceed the limits specified in table 8.3.
+
+#### 8.2.1.5.2 1,28 Mcps TDD option
+
+The BLER measured according to subclause 8.2.1.4.2. shall not exceed the limits specified in table 8.3A.
+
+#### 8.2.1.5.3 7,68 Mcps TDD option
+
+The BLER measured according to subclause 8.2.1.4.2 shall not exceed the limits specified in table 8.3B.
+
+### 8.3 Demodulation of DCH in multipath fading conditions
+
+#### 8.3.1 Multipath fading Case 1
+
+##### 8.3.1.1 Definition and applicability
+
+The performance requirement of DCH in multipath fading Case 1 is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station.
+
+In this subclause, different requirements shall apply to Wide Area BS, Local Area BS and Home BS.
+
+##### 8.3.1.2 Minimum Requirements
+
+###### 8.3.1.2.1 3,84 Mcps TDD option
+
+For the parameters specified in table 8.5, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.6. These requirements are applicable for TFCS size 16.
+
+**Table 8.5: Parameters in multipath Case 1 channel**
+
+| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|-----------------------------------------|---------------|--------------|---------------------------|---------------------------|-------------------|--------|
+| Number of DPCH o | | | 6 | 4 | 0 | 0 |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | | dB | -9 | -9,5 | - | - |
+| $I_{oc}$ | Wide Area BS | dBm/3,84 MHz | -89 | | | |
+| | Local Area BS | dBm/3,84 MHz | -74 | | | |
+| Cell Parameter* | | | 0,1 | | | |
+| DPCH Channelization Codes* | | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) |
+| DPCH o Channelization Codes* | | C(k,Q) | C(i,16) $3 \leq i \leq 8$ | C(i,16) $6 \leq i \leq 9$ | - | - |
+| Information Data Rate | | Kbps | 12,2 | 64 | 144 | 384 |
+
+\*Note: Refer to TS 25.223 for definition of channelization codes and cell parameter.
+
+**Table 8.6: Performance requirements in multipath Case 1 channel.**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|-----------|
+| 1 | 6,5 | $10^{-2}$ |
+| 2 | 5,5 | $10^{-1}$ |
+| | 9,8 | $10^{-2}$ |
+| 3 | 5,5 | $10^{-1}$ |
+| | 9,8 | $10^{-2}$ |
+| 4 | 5,1 | $10^{-1}$ |
+| | 9,5 | $10^{-2}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.1.1.1.
+
+###### 8.3.1.2.2 1,28 Mcps TDD option
+
+For the parameters specified in table 8.5A, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.6A. These requirements are applicable for TFCS size 16.
+
+**Table 8.5A: Parameters in multipath Case 1 channel for 1,28 Mcps TDD**
+
+| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|------------------------------------|---------------|--------------|--------|--------|--------|--------|
+| Number of DPCH o | | | 4 | 1 | 1 | 0 |
+| Spread factor of DPCH o | | | 8 | 8 | 8 | |
+| $\frac{DPCH_o\_E_c}{I_{or}}$ | | dB | -7 | -7 | -7 | - |
+| I oc | Wide Area BS | dBm/1,28 MHz | | | -91 | |
+| | Local Area BS | dBm/1,28 MHz | | | -77 | |
+| | Home BS | dBm/1,28 MHz | | | -82 | |
+| Information Data Rate | | kbps | 12,2 | 64 | 144 | 384 |
+
+**Table 8.6A: Performance requirements multipath Case 1 channel for 1,28 Mcps TDD**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|-----------|
+| 1 | 10.4 | $10^{-2}$ |
+| 2 | 5.3 | $10^{-1}$ |
+| | 9.4 | $10^{-2}$ |
+| 3 | 5.7 | $10^{-1}$ |
+| | 10.1 | $10^{-2}$ |
+| 4 | 6.8 | $10^{-1}$ |
+| | 10.9 | $10^{-2}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.1.1.2.
+
+### 8.3.1.2.3 7,68 Mcps TDD option
+
+For the parameters specified in table 8.5B, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.6B. These requirements are applicable for TFCS size 16.
+
+**Table 8.5B: Parameters in multipath Case 1 channel**
+
+| Parameters | | Unit | Test 1 |
+|--------------------------------------------------------------------------------------|---------------|--------------|--------------------------------|
+| Number of DPCH o | | | 14 |
+| | | dB | -12 |
+| I oc | Wide Area BS | dBm/7.68 MHz | -89 |
+| | Local Area BS | dBm/7.68 MHz | -74 |
+| Cell Parameter* | | | 0,1 |
+| DPCH Channelization Codes* | | C(k,Q) | C(1, 16) |
+| DPCH o Channelization Codes* | | C(k,Q) | C(i, 32)
$3 \leq i \leq 16$ |
+| Information Data Rate | | Kbps | 12.2 |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.6B: Performance requirements in multipath Case 1 channel.**
+
+| Test Number | [dB] | BLER |
+|-------------|------|-----------|
+| 1 | 6.5 | $10^{-2}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.1.1.3.
+
+### 8.3.1.3 Test purpose
+
+The test purpose is to verify the ability of the BS to receive a prescribed test signal under defined propagation conditions (multipath fading Case 1) with a BLER not exceeding a specified limit. Within the wanted channel, independent intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver
+
+to extract the wanted signal from the distorted and interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part.
+
+#### 8.3.1.4 Method of test
+
+##### 8.3.1.4.1 Initial conditions
+
+###### 8.3.1.4.1.0 General test conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+###### 8.3.1.4.1.1 3,84 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.5.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 1.
+
+###### 8.3.1.4.1.2 1,28 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.5A.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 1.
+
+###### 8.3.1.4.1.3 7,68 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.5B.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 1.
+
+##### 8.3.1.4.2 Procedure
+
+###### 8.3.1.4.2.1 3,84 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.5.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.7.
+
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.7.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.7: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------|
+| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | |
+| | | | | | | | Wide Area BS | Local Area BS |
+| 1 | 10 -2 | 6 | -91,5 | -76,5 | DPCH 1 | 8 | -88,5 | -73,5 |
+| 2 | 10 -1 | 4 | -93,0 | -78,0 | DPCH 1 | 16 | -93,0 | -78,0 |
+| | | | | | DPCH 2 | 4 | -87,0 | -72,0 |
+| | 10 -2 | 4 | -88,7 | -73,7 | DPCH 1 | 16 | -88,7 | -73,7 |
+| | | | | | DPCH 2 | 4 | -82,7 | -67,7 |
+| 3 | 10 -1 | 0 | - | - | DPCH 1 | 16 | -93,0 | -78,0 |
+| | | | | | DPCH 2 | 2 | -84,0 | -69,0 |
+| | 10 -2 | 0 | - | - | DPCH 1 | 16 | -88,7 | -73,7 |
+| | | | | | DPCH 2 | 2 | -79,7 | -64,7 |
+| 4 | 10 -1 | 0 | - | - | DPCH 1 | 2 | -83,9 | -68,9 |
+| | 10 -2 | 0 | - | - | DPCH 1 | 2 | -79,5 | -64,5 |
+
+#### 8.3.1.4.2.2 1,28 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.5A.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.7A.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.7A.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.7A: Parameters of DPCH0 and the wanted signal for 1,28 Mcps TDD**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | | Parameters of the wanted signal | | | | |
+|-------------|----------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------|---------------------------------|----|--------------------------------------------------|---------------|---------|
+| | | | Wide Area BS | Local Area BS | Home BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | |
+| | | | | | | | | Wide Area BS | Local Area BS | Home BS |
+
+| | | | | | | | | | | |
+|---|-----------|---|-------|-------|-------|-------------------|----|-------|-------|-------|
+| 1 | $10^{-2}$ | 4 | -87.6 | -73,6 | -78.6 | DPCH 1 | 8 | -87.6 | -73,6 | -78.6 |
+| 2 | $10^{-1}$ | 1 | -92.7 | -78,7 | -83.7 | DPCH 1 | 2 | -86.7 | -72,7 | -77.7 |
+| | $10^{-2}$ | 1 | -88.6 | -74,6 | -79.6 | DPCH 1 | 2 | -82.6 | -68,6 | -73.6 |
+| 3 | $10^{-1}$ | 1 | -92.3 | -78,3 | -83.3 | DPCH 1 | 2 | -86.3 | -72,3 | -77.3 |
+| | $10^{-2}$ | 1 | -87.9 | -73,9 | -78.9 | DPCH 1 | 2 | -81.9 | -67,9 | -72.9 |
+| 4 | $10^{-1}$ | 0 | - | | | DPCH 1 | 16 | -93.7 | -79.7 | -84.7 |
+| | | | | | | DPCH 2 | 2 | -84.7 | -70.7 | -75.7 |
+| | $10^{-2}$ | 0 | - | | | DPCH 1 | 16 | -89.6 | -75.6 | -80.6 |
+| | | | | | | DPCH 2 | 2 | -80.6 | -66.6 | -71.6 |
+
+#### 8.3.1.4.2.3 7,68 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.5B.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.7B.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.7B.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.7B: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | |
+|-------------|----------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------|
+| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | |
+| | | | | | | | Wide Area BS | Local Area BS |
+| 1 | $10^{-2}$ | 14 | -94,5 | -79,5 | DPCH 1 | 16 | -91,5 | -76,5 |
+
+#### 8.3.1.5 Test Requirements
+
+NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+##### 8.3.1.5.1 3,84 Mcps TDD option
+
+The BLER measured according to subclause 8.3.1.4.2 shall not exceed the limits specified in table 8.6.
+
+##### 8.3.1.5.2 1,28 Mcps TDD option
+
+The BLER measured according to subclause 8.3.1.4.2 shall not exceed the limits specified in table 8.6A.
+
+##### 8.3.1.5.3 7,68 Mcps TDD option
+
+The BLER measured according to subclause 8.3.1.4.2 shall not exceed the limits specified in table 8.6B.
+
+### 8.3.2 Multipath fading Case 2
+
+#### 8.3.2.1 Definition and applicability
+
+The performance requirement of DCH in multipath fading Case 2 is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station.
+
+The requirements in this subclause shall apply to Wide Area BS only. There is no requirement to test Local Area BS and Home BS in multipath fading Case 2 conditions.
+
+### 8.3.2.2 Minimum Requirements
+
+#### 8.3.2.2.1 3,84 Mcps TDD option
+
+For the parameters specified in table 8.8, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.8. These requirements are applicable for TFCS size 16.
+
+**Table 8.8: Parameters in multipath Case 2 channel**
+
+| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|-----------------------------------------|--------------|-----------------|-------------------|-------------------|--------|
+| Number of DPCH o | | 2 | 0 | 0 | 0 |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | DB | -6 | - | - | - |
+| I oc | dBm/3,84 MHz | -89 | | | |
+| Cell Parameter* | | 0,1 | | | |
+| DPCH Channelization Codes* | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) |
+| DPCH o Channelization Codes* | C(k,Q) | C(i,16) 3≤ i ≤4 | - | - | - |
+| Information Data Rate | Kbps | 12,2 | 64 | 144 | 384 |
+
+\*Note: Refer to TS 25.223 for definition of channelization codes and cell parameter.
+
+**Table 8.9: Performance requirements in multipath Case 2 channel.**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|------------------|
+| 1 | -0,4 | 10 -2 |
+| 2 | 0,2 | 10 -1 |
+| | 2,5 | 10 -2 |
+| 3 | 3,6 | 10 -1 |
+| | 6,0 | 10 -2 |
+| 4 | 2,8 | 10 -1 |
+| | 5,2 | 10 -2 |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.2.1.1.
+
+#### 8.3.2.2.2 1,28 Mcps option
+
+For the parameters specified in table 8.8A, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.9A. These requirements are applicable for TFCS size 16.
+
+**Table 8.8A: Parameters in multipath Case 2 channel for 1,28 Mcps TDD**
+
+| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|------------------------------------|--------------|--------|--------|--------|--------|
+| Number of DPCH o | | 4 | 1 | 1 | 0 |
+| Spread factor of DPCH o | | 8 | 8 | 8 | |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | dB | -7 | -7 | -7 | - |
+| I oc | dBm/1,28 MHz | -91 | | | |
+| Information Data Rate | kbps | 12,2 | 64 | 144 | 384 |
+
+**Table 8.9A: Performance requirements multipath Case 2 channel for 1,28 Mcps TDD.**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|-----------|
+| 1 | 6.7 | $10^{-2}$ |
+| 2 | 3.6 | $10^{-1}$ |
+| | 5.9 | $10^{-2}$ |
+| 3 | 4.2 | $10^{-1}$ |
+| | 6.3 | $10^{-2}$ |
+| 4 | 4.8 | $10^{-1}$ |
+| | 7.1 | $10^{-2}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.2.1.2.
+
+### 8.3.2.2.3 7,68 Mcps TDD option
+
+For the parameters specified in table 8.8B, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.9B. These requirements are applicable for TFCS size 16.
+
+**Table 8.8B: Parameters in multipath Case 2 channel**
+
+| Parameters | Unit | Test 1 |
+|--------------------------------------------------------------------------------------|--------------|-------------------------------|
+| Number of DPCH o | | 6 |
+| | dB | -9 |
+| $I_{oc}$ | dBm/7.68 MHz | -89 |
+| Cell Parameter* | | 0,1 |
+| DPCH Channelization Codes* | C(k,Q) | C(1, 16) |
+| DPCH o Channelization Codes* | C(k,Q) | C(i, 32)
$3 \leq i \leq 8$ |
+| Information Data Rate | kbps | 12.2 |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | |
+
+**Table 8.9B: Performance requirements in multipath Case 2 channel.**
+
+| Test Number | [dB] | BLER |
+|-------------|------|-----------|
+| 1 | 1 | $10^{-2}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.2.1.3.
+
+### 8.3.2.3 Test purpose
+
+The test purpose is to verify the ability of the BS to receive a prescribed test signal under defined propagation conditions (multipath fading Case 2) with a BLER not exceeding a specified limit. Within the wanted channel, independent intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver to extract the wanted signal from the distorted and interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part.
+
+### 8.3.2.4 Method of test
+
+#### 8.3.2.4.1 Initial conditions
+
+##### 8.3.2.4.1.0 General test conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+#### 8.3.2.4.1.1 3,84 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.8.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 2.
+
+#### 8.3.2.4.1.2 1,28 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.8A.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 2.
+
+#### 8.3.2.4.1.3 7,68 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.8B.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 2.
+
+#### 8.3.2.4.2 Procedure
+
+##### 8.3.2.4.2.1 3,84 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.8.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.101.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.10.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.10: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | 10 -2 | 2 | -95,4 | DPCH 1 | 8 | -92,4 |
+| 2 | 10 -1 | 0 | - | DPCH 1 | 16 | -95,8 |
+| | | | | DPCH 2 | 4 | -89,8 |
+| | 10 -2 | 0 | - | DPCH 1 | 16 | -93,5 |
+| | | | | DPCH 2 | 4 | -87,5 |
+| 3 | 10 -1 | 0 | - | DPCH 1 | 16 | -94,9 |
+| | | | | DPCH 2 | 2 | -85,9 |
+| | 10 -2 | 0 | - | DPCH 1 | 16 | -92,5 |
+| | | | | DPCH 2 | 2 | -83,5 |
+| 4 | 10 -1 | 0 | - | DPCH 1 | 2 | -86,2 |
+| | 10 -2 | 0 | - | DPCH 1 | 2 | -83,8 |
+
+#### 8.3.2.4.2.2 1,28 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.8A.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.10A.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.10A.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.10A: Parameters of DPCH0 and the wanted signal for 1,28 Mcps TDD**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | 10 -2 | 4 | -91.3 | DPCH 1 | 8 | -91.3 |
+| 2 | 10 -1 | 1 | -94.4 | DPCH 1 | 2 | -88.4 |
+| | 10 -2 | 1 | -92.1 | DPCH 1 | 2 | -86.1 |
+| 3 | 10 -1 | 1 | -93.8 | DPCH 1 | 2 | -87.8 |
+| | 10 -2 | 1 | -91.7 | DPCH 1 | 2 | -85.7 |
+| 4 | 10 -1 | 0 | - | DPCH 1 | 16 | -95.7 |
+| | | | | DPCH 2 | 2 | -86.7 |
+| | 10 -2 | 0 | - | DPCH 1 | 16 | -93.4 |
+| | | | | DPCH 2 | 2 | -84.4 |
+
+#### 8.3.2.4.2.3 7,68 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.8B.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.10B.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different
+
+spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.10B.
+
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.10B: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | 10 -2 | 6 | -97 | DPCH 1 | 16 | -94 |
+
+### 8.3.2.5 Test Requirements
+
+NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+#### 8.3.2.5.1 3,84 Mcps TDD option
+
+The BLER measured according to subclause 8.3.2.4.2 shall not exceed the limits specified in table 8.9.
+
+#### 8.3.2.5.2 1,28 Mcps TDD option
+
+The BLER measured according to subclause 8.3.2.4.2 shall not exceed the limits specified in table 8.9A
+
+#### 8.3.2.5.3 7,68 Mcps TDD option
+
+The BLER measured according to subclause 8.3.2.4.2 shall not exceed the limits specified in table 8.9B.
+
+## 8.3.3 Multipath fading Case 3
+
+### 8.3.3.1 Definition and applicability
+
+The performance requirement of DCH in multipath fading Case 3 is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station.
+
+The requirements in this subclause shall apply to Wide Area BS only. There is no requirement to test Local Area BS and Home BS in multipath fading Case 3 conditions.
+
+### 8.3.3.2 Minimum Requirements
+
+#### 8.3.3.2.1 3,84 Mcps TDD option
+
+For the parameters specified in table 8.11, the BLER should not exceed the piece-wise linear BLER curve specified in Table 8.12. These requirements are applicable for TFCS size 16.
+
+**Table 8.11: Parameters in multipath Case 3 channel**
+
+| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|--------------------------------------------------------------------------------------|--------------|---------------------------|-------------------|-------------------|--------|
+| Number of DPCH 0 | | 2 | 0 | 0 | 0 |
+| $\frac{DPCH_{0\_E_c}}{I_{or}}$ | dB | -6 | - | - | - |
+| I oc | dBm/3,84 MHz | -89 | | | |
+| Cell Parameter* | | 0,1 | | | |
+| DPCH Channelization Codes* | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) |
+| DPCH 0 Channelization Codes* | C(k,Q) | C(i,16) $3 \leq i \leq 4$ | - | - | - |
+| Information Data Rate | Kbps | 12,2 | 64 | 144 | 384 |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | | |
+
+**Table 8.12: Performance requirements in multipath Case 3 channel.**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|-----------|
+| 1 | -0,1 | $10^{-2}$ |
+| 2 | 0,8 | $10^{-1}$ |
+| | 2,7 | $10^{-2}$ |
+| | 4,2 | $10^{-3}$ |
+| 3 | 4,5 | $10^{-1}$ |
+| | 6,3 | $10^{-2}$ |
+| | 8,0 | $10^{-3}$ |
+| 4 | 3,6 | $10^{-1}$ |
+| | 5,0 | $10^{-2}$ |
+| | 6,3 | $10^{-3}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.3.1.1.
+
+### 8.3.3.2.2 1,28 Mcps TDD option
+
+For the parameters specified in table 8.11A, the BLER should not exceed the piece-wise linear BLER curve specified in Table 8.12A. These requirements are applicable for TFCS size 16.
+
+**Table 8.11A: Parameters in multipath Case 3 channel (1,28 Mcps option)**
+
+| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 |
+|------------------------------------|--------------|--------|--------|--------|--------|
+| Number of DPCH o | | 4 | 1 | 1 | 0 |
+| Spread factor of DPCH o | | 8 | 8 | 8 | |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | dB | -7 | -7 | -7 | - |
+| $I_{oc}$ | dBm/1,28 MHz | | | -91 | |
+| Information Data Rate | kbps | 12,2 | 64 | 144 | 384 |
+
+**Table 8.12A: Performance requirements multipath Case 3 channel (1,28 Mcps option).**
+
+| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER |
+|-------------|------------------------------------|-----------|
+| 1 | 5.6 | $10^{-2}$ |
+| 2 | 3.2 | $10^{-1}$ |
+| | 4.6 | $10^{-2}$ |
+| | 5.9 | $10^{-3}$ |
+| 3 | 3.7 | $10^{-1}$ |
+| | 4.8 | $10^{-2}$ |
+| | 5.9 | $10^{-3}$ |
+| 4 | 3.9 | $10^{-1}$ |
+| | 4.8 | $10^{-2}$ |
+| | 5.7 | $10^{-3}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.3.1.2
+
+### 8.3.3.2.3 7,68 Mcps TDD option
+
+For the parameters specified in table 8.11B, the BLER should not exceed the piece-wise linear BLER curve specified in Table 8.12B. These requirements are applicable for TFCS size 16.
+
+**Table 8.11B: Parameters in multipath Case 3 channel**
+
+| Parameters | Unit | Test 1 |
+|--------------------------------------------------------------------------------------|--------------|-------------------------------|
+| Number of DPCH 0 | | 6 |
+| | dB | -9 |
+| $I_{oc}$ | dBm/7.68 MHz | -89 |
+| Cell Parameter* | | 0,1 |
+| DPCH Channelization Codes* | C(k,Q) | C(1, 16) |
+| DPCH 0 Channelization Codes* | C(k,Q) | C(i, 32)
$3 \leq i \leq 8$ |
+| Information Data Rate | kbps | 12.2 |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | |
+
+**Table 8.12B: Performance requirements in multipath Case 3 channel.**
+
+| Test Number | [dB] | BLER |
+|-------------|------|-----------|
+| 1 | -0.1 | $10^{-2}$ |
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3.3.1.3.
+
+### 8.3.3.3 Test purpose
+
+The test purpose is to verify the ability of the BS to receive a prescribed test signal under defined propagation conditions (multipath fading Case 3) with a BLER not exceeding a specified limit. Within the wanted channel, independent intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver to extract the wanted signal from the distorted and interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part.
+
+### 8.3.3.4 Method of test
+
+#### 8.3.3.4.1 Initial conditions
+
+##### 8.3.3.4.1.0 General test conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+##### 8.3.3.4.1.1 3,84 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.11.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3.
+
+##### 8.3.3.4.1.2 1,28 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal
+
+with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.11A.
+
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3.
+
+#### 8.3.3.4.1.3 7,68 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.11B.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3.
+
+#### 8.3.3.4.2 Procedure
+
+##### 8.3.3.4.2.1 3,84 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.11.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.13.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.131.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.13: Parameters of DPCH0 and the wanted signal**
+
+| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | 10 -2 | 2 | -95,1 | DPCH 1 | 8 | -92,1 |
+| 2 | 10 -1 | 0 | - | DPCH 1 | 16 | -95,2 |
+| | | | | DPCH 2 | 4 | -89,2 |
+| | 10 -2 | 0 | - | DPCH 1 | 16 | -93,3 |
+| | | | | DPCH 2 | 4 | -87,3 |
+| | 10 -3 | 0 | - | DPCH 1 | 16 | -91,8 |
+| | | | | DPCH 2 | 4 | -85,8 |
+| 3 | 10 -1 | 0 | - | DPCH 1 | 16 | -94,0 |
+| | | | | DPCH 2 | 2 | -85,0 |
+| | 10 -2 | 0 | - | DPCH 1 | 16 | -92,2 |
+| | | | | DPCH 2 | 2 | -83,2 |
+| | 10 -3 | 0 | - | DPCH 1 | 16 | -90,5 |
+| | | | | DPCH 2 | 2 | -81,5 |
+| 4 | 10 -1 | 0 | - | DPCH 1 | 2 | -85,4 |
+| | 10 -2 | 0 | - | DPCH 1 | 2 | -84,0 |
+| | 10 -3 | 0 | - | DPCH 1 | 2 | -82,7 |
+
+## 8.3.3.4.2.2 1,28 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.11A.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each $DPCH_0$ measured at the BS antenna connector during the active time slots to the value specified in table 8.13A.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels ( $DPCH_1$ and $DPCH_2$ ) with different spreading factors SF. The power(s) of $DPCH_1$ and $DPCH_2$ (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.13A.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.13A: Parameters of $DPCH_0$ and the wanted signal for 1,28 Mcps TDD**
+
+| Test Number | BLER objective | Number of $DPCH_0$ | Power of each $DPCH_0$ measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|-------------|----------------|--------------------|-------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | $10^{-2}$ | 4 | -92.4 | $DPCH_1$ | 8 | -92.4 |
+| 2 | $10^{-1}$ | 1 | -94.8 | $DPCH_1$ | 2 | -88.8 |
+| | $10^{-2}$ | 1 | -93.4 | $DPCH_1$ | 2 | -87.4 |
+| | $10^{-3}$ | 1 | -92.1 | $DPCH_1$ | 2 | -86.1 |
+| 3 | $10^{-1}$ | 1 | -94.3 | $DPCH_1$ | 2 | -88.3 |
+| | $10^{-2}$ | 1 | -93.2 | $DPCH_1$ | 2 | -87.2 |
+| | $10^{-3}$ | 1 | -92.1 | $DPCH_1$ | 2 | -86.1 |
+| 4 | $10^{-1}$ | 0 | - | $DPCH_1$ | 16 | -96.6 |
+| | | | | $DPCH_2$ | 2 | -87.6 |
+| | $10^{-2}$ | 0 | - | $DPCH_1$ | 16 | -95.7 |
+| | $10^{-3}$ | 0 | - | $DPCH_2$ | 2 | -86.7 |
+| | | | | $DPCH_1$ | 16 | -94.8 |
+| | | | | $DPCH_2$ | 2 | -85.8 |
+
+## 8.3.3.4.2.3 7,68 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.11B.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each $DPCH_0$ measured at the BS antenna connector during the active time slots to the value specified in table 8.13B.
+- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels ( $DPCH_1$ and $DPCH_2$ ) with different spreading factors SF. The power(s) of $DPCH_1$ and $DPCH_2$ (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.13B.
+- (4) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.13B: Parameters of $DPCH_0$ and the wanted signal**
+
+| Test Number | BLER objective | Number of $DPCH_0$ | Power of each $DPCH_0$ measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|-------------|----------------|--------------------|-------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | $10^{-2}$ | 6 | -98,1 | $DPCH_1$ | 16 | -95,1 |
+
+### 8.3.3.5 Test Requirements
+
+NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+#### 8.3.3.5.1 3,84 Mcps TDD option
+
+The BLER measured according to subclause 8.3.3.4.2 shall not exceed the limits specified in table 8.12.
+
+#### 8.3.3.5.2 1,28 Mcps TDD option
+
+The BLER measured according to subclause 8.3.3.4.2 shall not exceed the limits specified in table 8.12A.
+
+#### 8.3.3.5.3 7,68 Mcps TDD option
+
+The BLER measured according to subclause 8.3.3.4.2 shall not exceed the limits specified in table 8.12B.
+
+## 8.3A Demodulation of DCH in high speed train conditions
+
+### 8.3A.1 Definition and applicability
+
+The performance requirement of DCH in high speed train conditions is determined by the maximum BLER allowed when the receiver input signal is at a specified $I_{or}/I_{oc}$ limit. The BLER is calculated for the measurement channel supported by the base station.
+
+This requirement shall only be applied to BS supporting high speed mode.
+
+### 8.3A.2 Minimum requirement
+
+#### 8.3A.2.1 3.84 Mcps TDD option
+
+(void)
+
+#### 8.3A.2.2 1.28 Mcps TDD option
+
+For the parameters specified in Table 8.13C the BLER should not exceed the BLER requirement specified in Table 8.13D. These requirements are applicable for TFCS size 16.
+
+**Table 8.13C: DCH parameters in high speed train condition**
+
+| Parameters | Unit | Test 1 | Test 2 |
+|--------------------------------------------------------------------------------------|-------------|-----------------------------|--------|
+| Number of DPCHo | | 4 | 1 |
+| Spread factor of DPCHO | | 8 | 8 |
+| Scrambling code and basic midamble code number* | | 0 | 0 |
+| DPCH Channelization Codes* | C(k,Q) | C(1,8) | C(1,2) |
+| DPCHo Channelization Codes* | C(k,Q) | C(i,8)
$2 \leq i \leq 5$ | C(5,8) |
+| $\frac{DPCH_o - E_c}{I_{or}}$ | dB | -7 | -7 |
+| $I_{oc}$ | dBm/1.28MHz | -91 | |
+| Information Data Rate | Kbps | 12.2 | 64 |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.13D: DCH requirements in high speed train condition**
+
+| Test number | Scenario | dual receiver antenna diversity | [dB] | BLER |
+|-------------|----------|---------------------------------|------|-----------|
+| 1 | 1 | On | 4.0 | $10^{-2}$ |
+| | | Off * | 7.5 | $10^{-2}$ |
+| | 3 | Off * | 7.7 | $10^{-2}$ |
+| 2 | 1 | On | 1.2 | $10^{-1}$ |
+| | | On | 2.0 | $10^{-2}$ |
+| | | Off * | 4.6 | $10^{-1}$ |
+| | | Off * | 5.4 | $10^{-2}$ |
+| | 3 | Off * | 4.8 | $10^{-1}$ |
+| | | Off * | 6.0 | $10^{-2}$ |
+
+\*Note: The requirement is only applicable for BS without receiver antenna diversity, the required shall be applied at the BS Rx antenna port.
+
+The normative reference for this requirement is TS 25.105 [1] subclause 8.3A.2.2.
+
+### 8.3A.2.3 7.68 Mcps TDD option
+
+(void)
+
+## 8.3A.3 Test purpose
+
+The test shall verify the receiver's ability to receive the test signal in high speed train conditions with a BLER not exceeding the specified limit.
+
+## 8.3A.4 Method of test
+
+### 8.3A.4.1 Initial conditions
+
+#### 8.3A.4.1.1 General test conditions
+
+Test environment: normal; see subclause 5.9.1
+
+RF channels to be tested: B, M and T; see subclause 5.3
+
+#### 8.3A.4.1.1 3.84 Mcps TDD option
+
+(void)
+
+#### 8.3A.4.1.1 1.28 Mcps TDD option
+
+Connect the BS tester (UE simulator) generating the wanted signal , Channel Simulator generating Doppler shift and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.13C.
+
+#### 8.3A.4.1.1 7.68 Mcps TDD option
+
+(void)
+
+### 8.3A.4.2 Procedure
+
+#### 8.3A.4.2.1 3.84 Mcps TDD option
+
+(void)
+
+#### 8.3A.4.2.2 1.28 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.13C.
+- (2) For a given test defined by the information data rate and the BLER objective, set the power of each $DPCH_0$ measured at the BS antenna connector during the active time slots to the value specified in table 8.13E.
+- (4) The Channel Simulator shall be configured according to the corresponding Doppler shift trajectories defined in annex B.
+- (5) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels ( $DPCH_1$ and $DPCH_2$ ) with different spreading factors SF. The power(s) of $DPCH_1$ and $DPCH_2$ (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.13E.
+- (6) Measure the BLER of the wanted signal at the BS receiver.
+
+**Table 8.13E: Parameters of $DPCH_0$ and the wanted signal for 1,28 Mcps TDD**
+
+| Test Number | Scenario | Dual receiver antenna diversity | BLER objective | Number of $DPCH_0$ | Power of each $DPCH_0$ measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------------|----------------|--------------------|-------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------|
+| | | | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] |
+| 1 | 1 | On | $10^{-2}$ | 4 | -94.0 | $DPCH_1$ | 8 | -94.0 |
+| | | Off * | $10^{-2}$ | 4 | -90.5 | $DPCH_1$ | 8 | -90.5 |
+| | 3 | Off * | $10^{-2}$ | 4 | -90.3 | $DPCH_1$ | 8 | -90.3 |
+| 2 | 1 | On | $10^{-1}$ | 1 | -96.8 | $DPCH_1$ | 2 | -90.8 |
+| | | On | $10^{-2}$ | 1 | -96.0 | $DPCH_1$ | 2 | -90.0 |
+| | | Off * | $10^{-1}$ | 1 | -93.4 | $DPCH_1$ | 2 | -87.4 |
+| | | Off * | $10^{-2}$ | 1 | -92.6 | $DPCH_1$ | 2 | -86.6 |
+| | 3 | Off * | $10^{-1}$ | 1 | -93.2 | $DPCH_1$ | 2 | -87.2 |
+| | | Off * | $10^{-2}$ | 1 | -92.0 | $DPCH_1$ | 2 | -86.0 |
+| *Note: The requirement is only applicable for BS without receiver antenna diversity, the required shall be applied at the BS Rx antenna port. | | | | | | | | |
+
+#### 8.3A.4.2.3 7.68 Mcps TDD option
+
+(void)
+
+### 8.3A.5 Test requirements
+
+NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+#### 8.3A.5.1 3,84 Mcps TDD option
+
+(void)
+
+### 8. 3A.5.2 1,28 Mcps TDD option
+
+The BLER measured according to subclause 8.3A.4.2.2. shall not exceed the limits specified in table 8.13F.
+
+**Table 8.13F: DCH requirements in high speed train condition**
+
+| Test number | Scenario | dual receiver antenna diversity | [dB] | BLER |
+|-----------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------------|------|-----------|
+| 1 | 1 | On | 4.4 | $10^{-2}$ |
+| | | Off * | 7.9 | $10^{-2}$ |
+| | 3 | Off * | 8.1 | $10^{-2}$ |
+| 2 | 1 | On | 1.6 | $10^{-1}$ |
+| | | On | 2.4 | $10^{-2}$ |
+| | | Off * | 5.0 | $10^{-1}$ |
+| | | Off * | 5.8 | $10^{-2}$ |
+| | 3 | Off * | 5.2 | $10^{-1}$ |
+| | | Off * | 6.4 | $10^{-2}$ |
+| *Note: The requirement is only applicable for BS without receiver antenna diversity, the required shall be applied at the BS Rx antenna port. | | | | |
+
+### 8. 3A.5.3 7,68 Mcps TDD option
+
+(void)
+
+## 8.4 Demodulation of E-DCH FRC in multipath fading conditions
+
+### 8.4.1 Definition and applicability
+
+The performance requirement of the E-DCH in multi-path fading condition is determined by the minimum throughput R.
+
+### 8.4.2 Minimum Requirements
+
+#### 8.4.2.1 3,84 Mcps TDD Option
+
+For the test parameters specified in Table 8.14, the minimum requirements are specified in Table 8.15.
+
+**Table 8.14: Test parameters for testing E-DCH (3,84 Mcps TDD Option)**
+
+| Parameter | Unit | Value | | |
+|--------------------------------------------------------------------------------------|---------------|-----------------------|---------|---------|
+| | | FRC1 | FRC2 | FRC3 |
+| Max information rate | kbps | 34.7 | 1083.1 | 2073.7 |
+| $I_{oc}$ | Wide Area BS | dBm/3,84 MHz -89 | | |
+| | Local Area BS | dBm/3,84 MHz -74 | | |
+| E-DCH $E_s/I_{or}$ | dB | 0 | 0 | 0 |
+| Cell Parameter* | | 0, 1 | | |
+| E-DCH channelization code* | C(k, Q) | C(1, 16) | C(1, 2) | C(1, 1) |
+| RSN | | {0, 1, 2, 3} | | |
+| HARQ combining | | IR | | |
+| Maximum number of HARQ transmission | | 4 | | |
+| Power control | | OFF | | |
+| Receiver antenna diversity | | ON | | |
+| Midamble | | Default midamble | | |
+| Physical channels to be turned on | | E-PUCH | | |
+| Propagation condition | | PA3, PB3, VA30, VA120 | | |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | |
+
+**Table 8.15 Minimum Requirement for E-DCH (3,84 Mcps TDD Option)**
+
+| Fixed Reference Channel | | Reference value, $\hat{I}_{or}/I_{oc}$ (dB),
for R $\geq$ 30% and R $\geq$ 70% of maximum information bit rate | | | |
+|---------------------------|-----|-------------------------------------------------------------------------------------------------------------------|--------|-------|-------|
+| | | Propagation conditions | FRC1 | FRC2 | FRC3 |
+| Pedestrian A
(3 kmph) | 30% | | -13.76 | -0.55 | 4.94 |
+| | 70% | | -9.89 | 5.2 | 12.76 |
+| Pedestrian B
(3 kmph) | 30% | | -12.12 | 0.48 | 5.13 |
+| | 70% | | -9.46 | 5.22 | 13.1 |
+| Vehicular A
(30 kmph) | 30% | | -12.58 | -0.62 | 5.14 |
+| | 70% | | -9.51 | 5.3 | 13.46 |
+| Vehicular A
(120 kmph) | 30% | | -12.55 | -0.69 | 5.1 |
+| | 70% | | -9.78 | 5.22 | 13.14 |
+
+#### 8.4.2.2 1.28 Mcps TDD option
+
+For the test parameters specified in Table 8.14A, the minimum requirements are specified in Table 8.15A.
+
+**Table 8.14A: Test parameters for testing E-DCH (1.28 Mcps TDD Option)**
+
+| Parameter | Unit | Value | | | |
+|-------------------------------------------------|---------------|------------------|---------|---------|---------|
+| | | FRC1 | FRC2 | FRC3 | FRC4 |
+| Max information rate | kbps | 56.4 | 227.8 | 515.6 | 1281.2 |
+| $I_{oc}$ | Wide Area BS | dBm/1.28 MHz | -91 | | |
+| | Local Area BS | dBm/1.28MHz | -77 | | |
+| | Home BS | dBm/1.28MHz | -82 | | |
+| Scrambling code and basic midamble code number* | | 0 | 0 | 0 | 0 |
+| E-PUCH channelization code* | C(k, Q) | C(1, 4) | C(1, 2) | C(1, 2) | C(1, 1) |
+| RSN | | {0, 1, 2, 3} | | | |
+| HARQ combining | | IR | | | |
+| Maximum number of HARQ transmission | | 4 | | | |
+| Power control | | OFF | | | |
+| Receiver antenna diversity | | ON | | | |
+| Midamble | | Default midamble | | | |
+| Propagation condition | | PA3, PB3, VA30 | | | |
+
+\*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code
+
+**Table 8.15A Minimum Requirement for E-DCH (1.28 Mcps TDD Option)**
+
+| Fixed Reference Channel | | Reference value, $\hat{I}_{or}/I_{oc}$ (dB),
for R $\geq$ 30% and R $\geq$ 70% of maximum information bit rate | | | | |
+|-------------------------|-----|-------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------|
+| | | Propagation conditions | FRC1 | FRC2 | FRC3 | FRC4 |
+| Pedestrian A (3 kmph) | 30% | | -6.78 | -1.58 | 2.84 | 6.34 |
+| | 70% | | -1.83 | 4.6 | 10.19 | 13.45 |
+| Pedestrian B (3 kmph) | 30% | | -5.62 | -1.1 | 2.88 | 6.55 |
+| | 70% | | -1.65 | 5.09 | 8.99 | 12.26 |
+| Vehicular A (30 kmph) | 30% | | -4.96 | -0.88 | 3.09 | 7.14 |
+| | 70% | | -1.2 | 6.0 | 10.89 | 14.01 |
+
+#### 8.4.2.3 7.68 Mcps TDD Option
+
+For the test parameters specified in Table 8.14B, the minimum requirements are specified in Table 8.15B.
+
+**Table 8.14B: Test parameters for testing E-DCH (7.68 Mcps TDD Option)**
+
+| Parameter | Unit | Value | | |
+|--------------------------------------------------------------------------------------|---------------|-----------------------|---------|---------|
+| | | FRC1 | FRC2 | FRC3 |
+| Max information rate | kbps | 35.9 | 1083.1 | 2085.1 |
+| $I_{oc}$ | Wide Area BS | dBm/7.68 MHz | -89 | |
+| | Local Area BS | dBm/7.68 MHz | -74 | |
+| E-DCH $E_c/I_{or}$ | dB | 0 | 0 | 0 |
+| Cell Parameter* | | 0, 1 | | |
+| E-DCH channelization code* | C(k, Q) | C(1, 32) | C(1, 4) | C(1, 2) |
+| RSN | | {0, 1, 2, 3} | | |
+| HARQ combining | | IR | | |
+| Maximum number of HARQ transmission | | 4 | | |
+| Power control | | OFF | | |
+| Receiver antenna diversity | | ON | | |
+| Midamble | | Default midamble | | |
+| Physical channels to be turned on | | E-PUCH | | |
+| Propagation condition | | PA3, PB3, VA30, VA120 | | |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | |
+
+**Table 8.15B Minimum Requirement for E-DCH (7.68 Mcps TDD Option)**
+
+| Fixed Reference Channel | Reference value, $\hat{I}_{or}/I_{oc}$ (dB),
for R ≥ 30% and R ≥ 70% of maximum information bit rate | | | |
+|---------------------------|---------------------------------------------------------------------------------------------------------|--------|-------|------|
+| | Propagation conditions | FRC1 | FRC2 | FRC3 |
+| Pedestrian A
(3 kmph) | 30% | -16.22 | -3.71 | 1.72 |
+| | 70% | -12.56 | 1.79 | 9.39 |
+| Pedestrian B
(3 kmph) | 30% | -14.44 | -3.71 | 1.45 |
+| | 70% | -11.54 | 1.48 | 8.87 |
+| Vehicular A
(30 kmph) | 30% | -14.81 | -3.68 | 1.48 |
+| | 70% | -11.84 | 1.89 | 9.28 |
+| Vehicular A
(120 kmph) | 30% | -14.81 | -3.83 | 1.38 |
+| | 70% | -12.27 | 1.67 | 9.17 |
+
+### 8.4.3 Test purpose
+
+The test shall verify the receiver's ability to receive the test signal under multipath fading propagation conditions with a throughput not below a specified limit.†
+
+## 8.4.4 Method of test
+
+### 8.4.4.1 Initial conditions
+
+#### 8.4.4.1.0 General test conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3.
+
+#### 8.4.4.1.1 3,84 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a band-limited white noise source, simulating interference from other cells, to both BS antenna connectors for diversity reception via a combining network.
+- (2) The wanted signal produced by the BS tester to both BS antenna connectors are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading conditions specified in Table 8.14 and 8.15.
+
+#### 8.4.4.1.2 1.28Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a band-limited white noise source, simulating interference from other cells, to both BS antenna connectors for diversity reception via a combining network.
+- (2) The wanted signal produced by the BS tester to both BS antenna connectors are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading conditions specified in Table 8.14A and 8.15A.
+
+#### 8.4.4.1.3 7.68 Mcps TDD option
+
+- (1) Connect the BS tester (UE simulator) generating the wanted signal and a band-limited white noise source, simulating interference from other cells, to both BS antenna connectors for diversity reception via a combining network.
+- (2) The wanted signal produced by the BS tester to both BS antenna connectors are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading conditions specified in Table 8.14B and 8.15B.
+
+#### 8.4.4.2 Procedure
+
+##### 8.4.4.2.1 3,84 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.14.
+- (2) The characteristics of the wanted signal shall be configured according to the corresponding E-DCH Fixed Reference Channel (FRC) measurement channel defined in annex A.3. Depending upon the E-DCH FRC measurement channel makes use of one physical channel (E-PUCH) with different spreading factors SF. The power of the E-PUCH measured at the BS antenna connector during the active time slots shall be set to the values given in Table 8.16.
+- (3) The Multipath Fading Simulators shall be configured according to the corresponding channel model defined in annex D.
+- (4) For each of the fixed reference channels in table 8.16 applicable for the base station, measure the throughput for each E-PUCH power and propagation condition settings.
+
+**Table 8.16: Parameters of the wanted signal (E-PUCH) (3,84 Mcps TDD Option)**
+
+| Propagation Conditions | Throughput R
(% of max
information bit
rate) | Wanted signal (E-PUCH) power measured at the BS
antenna connector (dBm) | | | | | |
+|------------------------|-------------------------------------------------------|----------------------------------------------------------------------------|--------|--------|---------------|--------|--------|
+| | | Wide Area BS | | | Local Area BS | | |
+| | | FRC1 | FRC2 | FRC3 | FRC1 | FRC2 | FRC3 |
+| Pedestrian A (3 kmph) | 30% | -102.76 | -89.55 | -84.06 | -87.76 | -74.55 | -69.06 |
+| | 70% | -98.89 | -83.80 | -76.24 | -83.89 | -68.80 | -61.24 |
+| Pedestrian B (3 kmph) | 30% | -101.12 | -88.52 | -83.87 | -86.12 | -73.52 | -68.87 |
+| | 70% | -98.46 | -83.78 | -75.90 | -83.46 | -68.78 | -60.90 |
+| Vehicular A (30 kmph) | 30% | -101.58 | -89.62 | -83.86 | -86.58 | -74.62 | -68.86 |
+| | 70% | -98.51 | -83.70 | -75.54 | -83.51 | -68.70 | -60.54 |
+| Vehicular A (120 kmph) | 30% | -101.55 | -89.69 | -83.90 | -86.55 | -74.69 | -68.90 |
+| | 70% | -98.78 | -83.78 | -75.86 | -83.78 | -68.78 | -60.86 |
+
+##### 8.4.4.2.2 1.28Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.14A.
+- (2) The characteristics of the wanted signal shall be configured according to the corresponding E-DCH Fixed Reference Channel (FRC) measurement channel defined in annex A.3. Depending upon the E-DCH FRC measurement channel makes use of one physical channel (E-PUCH) with different spreading factors SF. The power of the E-PUCH measured at the BS antenna connector during the active time slots shall be set to the values given in Table 8.16A.
+
+- (3) The Multipath Fading Simulators shall be configured according to the corresponding channel model defined in annex B.
+- (4) For each of the fixed reference channels in table 8.16A applicable for the base station, measure the throughput for each E-PUCH power and propagation condition settings.
+
+**Table 8.16A: Parameters of the wanted signal (E-PUCH) (1.28 Mcps TDD Option)**
+
+| Propagation Conditions | Throughput R (% of max information bit rate) | Wanted signal (E-PUCH) power measured at the BS antenna connector (dBm) | | | | | | | | | | | |
+|------------------------|----------------------------------------------|-------------------------------------------------------------------------|--------|--------|--------|---------------|--------|--------|--------|--------------|--------|--------|--------|
+| | | Wide Area BS | | | | Local Area BS | | | | Wide Area BS | | | |
+| | | FRC1 | FRC2 | FRC1 | FRC2 | FRC1 | FRC2 | FRC1 | FRC2 | FRC1 | FRC2 | FRC3 | FRC4 |
+| Pedestrian A (3 kmph) | 30% | -97.78 | -92.58 | -97.78 | -92.58 | -97.78 | -92.58 | -97.78 | -92.58 | -88.78 | -83.58 | -79.16 | -75.66 |
+| | 70% | -92.83 | -86.4 | -92.83 | -86.4 | -92.83 | -86.4 | -92.83 | -86.4 | -83.83 | -77.4 | -71.81 | -68.55 |
+| Pedestrian B (3 kmph) | 30% | -96.62 | -92.1 | -96.62 | -92.1 | -96.62 | -92.1 | -96.62 | -92.1 | -87.62 | -83.1 | -79.12 | -75.45 |
+| | 70% | -92.65 | -85.91 | -92.65 | -85.91 | -92.65 | -85.91 | -92.65 | -85.91 | -83.65 | -76.91 | -73.01 | -69.74 |
+| Vehicular A (30 kmph) | 30% | -95.96 | -91.88 | -95.96 | -91.88 | -95.96 | -91.88 | -95.96 | -91.88 | -86.96 | -82.88 | -78.91 | -74.86 |
+| | 70% | -92.2 | -85 | -92.2 | -85 | -92.2 | -85 | -92.2 | -85 | -83.2 | -76 | -71.11 | -67.99 |
+
+#### 8.4.4.2.3 7.68 Mcps TDD option
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.14B.
+- (2) The characteristics of the wanted signal shall be configured according to the corresponding E-DCH Fixed Reference Channel (FRC) measurement channel defined in annex A.3. Depending upon the E-DCH FRC measurement channel makes use of one physical channel (E-PUCH) with different spreading factors SF. The power of the E-PUCH measured at the BS antenna connector during the active time slots shall be set to the values given in Table 8.16B.
+- (3) The Multipath Fading Simulators shall be configured according to the corresponding channel model defined in annex D.
+- (4) For each of the fixed reference channels in table 8.16B applicable for the base station, measure the throughput for each E-PUCH power and propagation condition settings.
+
+**Table 8.16B: Parameters of the wanted signal (E-PUCH) (7.68 Mcps TDD Option)**
+
+| Propagation Conditions | Throughput R (% of max information bit rate) | Wanted signal (E-PUCH) power measured at the BS antenna connector (dBm) | | | | | |
+|------------------------|----------------------------------------------|-------------------------------------------------------------------------|--------|--------|---------------|--------|--------|
+| | | Wide Area BS | | | Local Area BS | | |
+| | | FRC1 | FRC2 | FRC3 | FRC1 | FRC2 | FRC3 |
+| Pedestrian A (3 kmph) | 30% | -105.22 | -92.71 | -87.28 | -90.22 | -77.71 | -72.28 |
+| | 70% | -101.56 | -87.21 | -79.61 | -86.56 | -72.21 | -64.61 |
+| Pedestrian B (3 kmph) | 30% | -103.44 | -92.71 | -87.55 | -88.44 | -77.71 | -72.55 |
+| | 70% | -100.54 | -87.52 | -80.13 | -85.54 | -72.52 | -65.13 |
+| Vehicular A (30 kmph) | 30% | -103.81 | -92.68 | -87.52 | -88.81 | -77.68 | -72.52 |
+| | 70% | -100.84 | -87.11 | -79.72 | -85.84 | -72.11 | -64.72 |
+| Vehicular A (120 kmph) | 30% | -103.81 | -92.83 | -87.62 | -88.81 | -77.83 | -72.62 |
+| | 70% | -101.27 | -87.33 | -79.83 | -86.27 | -72.33 | -64.83 |
+
+#### 8.4.5 Test Requirements
+
+NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+#### 8.4.5.1 3,84 Mcps TDD option
+
+The throughput measured according to subclause 8.4.4.2 shall be at least the limits specified in table 8.15.
+
+#### 8.4.5.2 1.28Mcps TDD option
+
+The throughput measured according to subclause 8.4.4.2 shall be at least the limits specified in table 8.15A.
+
+#### 8.4.5.3 7.68 Mcps TDD option
+
+The throughput measured according to subclause 8.4.4.2 shall be at least the limits specified in table 8.15B.
+
+### 8.5 Performance of ACK error detection for HS-SICH
+
+#### 8.5.1 ACK error detection in static propagation conditions
+
+##### 8.5.1.1 3.84 Mcps TDD option
+
+(void)
+
+##### 8.5.1.2 1.28 Mcps TDD option
+
+###### 8.5.1.2.1 Definition and applicability
+
+The performance requirement of the HS-SICH is ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ when ACK is transmitted.
+
+###### 8.5.1.2.2 Minimum requirement
+
+The performance requirement of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.18A.
+
+**Table 8.17A: Test parameters for testing ACK error detection using HS-SICH type1 (1.28Mcps TDD Option)**
+
+| Parameters | | Unit | Test |
+|--------------------------------------------------------------------------------------|--------------|--------------|--------------------------------|
+| Number of DPCHo | | | 2 |
+| Spread factor of DPCHo | | | 8 |
+| Scrambling code and basic midamble code number* | | | 0 |
+| DPCHo Channelization Codes* | | $C(k, Q)$ | $C(i, 8)$
$2 \leq i \leq 3$ |
+| | | dB | -4 |
+| | | dB | -7 |
+| loc | Wide Area BS | dBm/1,28 MHz | -91 |
+| | Home BS | dBm/1,28 MHz | -82 |
+| Closed loop power control | | | Off |
+| Midamble | | | Default midamble |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.17B: Test parameters for testing ACK error detection using HS-SICH type2 (1.28Mcps TDD Option)**
+
+| Parameters | | Unit | Test |
+|-------------------------------------------------------------------------------------|--------------|--------------|---------------------|
+| Number of DPCH 0 | | | 2 |
+| Spread factor of DPCH 0 | | | 8 |
+| Scrambling code and basic midamble code number (note) | | | 0 |
+| DPCH 0 Channelization Codes* | | C(k,Q) | C(i,8)
2 ≤ i ≤ 3 |
+| | | dB | -4.8 |
+| | | dB | -4.8 |
+| I oc | Wide Area BS | dBm/1.28 MHz | -91 |
+| | Home BS | dBm/1.28 MHz | -82 |
+| Closed loop power control | | | Off |
+| Midamble | | | Default midamble |
+| NOTE: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.18A: Performance requirements for ACK error detection in AWGN channel using HS-SICH type1**
+
+| Received | Required error ratio |
+|----------|----------------------|
+| -3,1 dB | < 10 -2 |
+
+**Table 8.18B: Performance requirements for ACK error detection in AWGN channel using HS-SICH type2**
+
+| Received | Required error ratio |
+|----------|----------------------|
+| -5.3 dB | < 10 -2 |
+
+The reference for this requirement is TS 25.105 subclause 8.5.
+
+#### 8.5.1.2.3 Test purpose
+
+The test shall verify the receiver's ability to receive the test signal under static propagation conditions with an error ratio not exceeding a specified limit.
+
+#### 8.5.1.2.4 Method of test
+
+##### 8.5.1.2.4.1 Initial conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3
+
+- (1) Connect the BS tester generating the wanted signal and AWGN generators to both BS antenna connectors for diversity reception via a combining network as shown in annex B. Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.17A.
+
+##### 8.5.1.2.4.2 Procedure
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.17A.
+
+- (2) The characteristics of the wanted signal (HS-SICH) shall be configured according to the corresponding UL reference measurement channel defined in annex A. Set the power of HS-SICH and each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.17A.
+- (3) The test signal generator sends the ACKs with HS-SICH and DPCH0s. Adjust the equipment so that required specified in table 8.18A is achieved The receiver tries to detect ACK. The error ratio is calculated for the ACKs that have been detected.
+
+#### 8.5.1.2.5 Test requirements
+
+The performance of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.19A.
+
+**Table 8.19A: Performance requirements for ACK error detection in AWGN channel using HS-SICH type1**
+
+| Received | Required error ratio |
+|----------|----------------------|
+| -2,7dB | $< 10^{-2}$ |
+
+**Table 8.19B: Performance requirements for ACK error detection in AWGN channel using HS-SICH type2**
+
+| Received | Required error ratio |
+|----------|----------------------|
+| -4.9dB | $< 10^{-2}$ |
+
+NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 8.5.2 ACK error detection in multipath fading conditions
+
+#### 8.5.2.1 3,84Mcps TDD option
+
+(void)
+
+#### 8.5.2.2 1,28Mcps TDD option
+
+##### 8.5.2.2.1 Definition and applicability
+
+The performance requirement of the HS-SICH is ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ when ACK is transmitted..
+
+##### 8.5.2.2.2 Minimum requirement
+
+The performance of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.20A.
+
+**Table 8.20A: Test parameters for testing ACK error detection using HS-SICH type1 (1,28Mcps TDD Option)**
+
+| Parameters | | Unit | Test |
+|--------------------------------------------------------------------------------------|--------------|--------------|-----------------------------|
+| Number of DPCH 0 | | | 2 |
+| Spread factor of DPCH 0 | | | 8 |
+| Scrambling code and basic midamble code number* | | | 0 |
+| DPCH 0 Channelization Codes* | | C(k,Q) | C(i,8)
$2 \leq i \leq 3$ |
+| | | dB | -4 |
+| | | dB | -7 |
+| I oc | Wide Area BS | dBm/1,28 MHz | -91 |
+| | Home BS | dBm/1,28 MHz | -82 |
+| Closed loop power control | | | Off |
+| Midamble | | | Default midamble |
+| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.20B: Test parameters for testing ACK error detection using HS-SICH type2 (1.28Mcps TDD Option)**
+
+| Parameters | | Unit | Test |
+|-------------------------------------------------------------------------------------|--------------|--------------|-----------------------------|
+| Number of DPCH 0 | | | 2 |
+| Spread factor of DPCH 0 | | | 8 |
+| Scrambling code and basic midamble code number (note) | | | 0 |
+| DPCH 0 Channelization Codes* | | C(k,Q) | C(i,8)
$2 \leq i \leq 3$ |
+| | | dB | -4.8 |
+| | | dB | -4.8 |
+| I oc | Wide Area BS | dBm/1.28 MHz | -91 |
+| | Home BS | dBm/1,28 MHz | -82 |
+| Closed loop power control | | | Off |
+| Midamble | | | Default midamble |
+| NOTE: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | |
+
+**Table 8.21A: Performance requirements for ACK error detection in fading channels using HS-SICH type1**
+
+| Propagation conditions | Received(dB) | Required error ratio |
+|-----------------------------------------------|--------------|----------------------|
+| Case 1 | 1,2 | $< 10^{-2}$ |
+| Case 2* | 0,9 | $< 10^{-2}$ |
+| Case 3* | 0,2 | $< 10^{-2}$ |
+| *Note: This case is not applicable to Home BS | | |
+
+**Table 8.21B: Performance requirements for ACK error detection in fading channels using HS-SICH type2**
+
+| Propagation conditions | Received(dB) | Required error ratio |
+|-----------------------------------------------|--------------|----------------------|
+| Case 1 | -1,2 | $< 10^{-2}$ |
+| Case 2* | -0,7 | $< 10^{-2}$ |
+| *Note: This case is not applicable to Home BS | | |
+
+The reference for this requirement is TS 25.105 subclause 8.5.
+
+### 8.5.2.2.3 Test purpose
+
+The test shall verify the receiver's ability to receive the test signal under multipath fading propagation conditions with an error ratio not exceeding a specified limit.
+
+### 8.5.2.2.4 Method of test
+
+#### 8.5.2.2.4.1 Initial conditions
+
+Test environment: normal; see subclause 5.9.1.
+
+RF channels to be tested: B, M and T; see subclause 5.3
+
+- (1) Connect the BS tester generating the wanted signal and AWGN generators to both BS antenna connectors for diversity reception via a combining network as shown in annex B. Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.20A.
+- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3.
+
+#### 8.5.2.2.4.2 Procedure
+
+- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.20A.
+- (2) The characteristics of the wanted signal (HS-SICH) shall be configured according to the corresponding UL reference measurement channel defined in annex A. Set the power of HS-SICH and each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.20A.
+- (3) The test signal generator sends the ACKs with HS-SICH and DPCH0s. Adjust the equipment so that required specified in table 8.21A is achieved The receiver tries to detect ACK. The error ratio is calculated for the ACKs that have been detected.
+
+### 8.5.2.2.5 Test requirements
+
+The performance of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.22A.
+
+**Table 8.22A: Performance requirements for ACK error detection in fading channels using HS-SICH type1**
+
+| Propagation conditions | Received (dB) | Required error ratio |
+|-----------------------------------------------|---------------|----------------------|
+| Case 1 | 1,8 | $< 10^{-2}$ |
+| Case 2* | 1,5 | $< 10^{-2}$ |
+| Case 3* | 0,8 | $< 10^{-2}$ |
+| *Note: This case is not applicable to Home BS | | |
+
+**Table 8.22B: Performance requirements for ACK error detection in fading channels using HS-SICH type2**
+
+| Propagation conditions | Received (dB) | Required error ratio |
+|-----------------------------------------------|---------------|----------------------|
+| Case 1 | -0.6 | $< 10^{-2}$ |
+| Case 2* | -0.1 | $< 10^{-2}$ |
+| *Note: This case is not applicable to Home BS | | |
+
+NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+---
+
+## Annex A (normative): Measurement Channels
+
+### A.1 (void)
+
+### A.2 Reference measurement channel
+
+#### A.2.1 UL reference measurement channel (12,2 kbps)
+
+##### A.2.1.1 3,84 Mcps TDD option
+
+Table A.1
+
+| Parameter | Value |
+|-----------------------------------------------------------------------|------------------|
+| Information data rate | 12.2 kbps |
+| RU's allocated | 2 RU |
+| Midamble | 512 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate 1/3 : DCH of the DTCH / DCH of the DCCH | 10% / 0% |
+
+
+
+**Information data** 244 244
+
+**CRC attachment** 244 16 244 16
+
+**Tail bit attachment** 260 bit/20ms 8 260 bit/20ms 8
+
+**Conv. Coding 1/3** $[(260+8) \times 3 = 804]$ $[(260+8) \times 3 = 804]$
+
+**1st Interleaving** 804 bit/20ms 804 bit/20ms
+
+**RF-segmentation** 402 402 402 402
+
+**Puncturing Ratematching**
+402 bit punct. to 362 bit
+puncturing-level: 10%
+ $2 \text{ RU} \rightarrow 244 \times 2 = 488 \text{ Bits available}$
+
+| gross | 488 bit |
+|----------|-------------|
+| -TFCI | -16 bit * 2 |
+| -TPC | -2 bit * 2 |
+| -Signal. | -90 bit |
+| punc. to | 362 bit |
+
+**DCCH**
+4 96
+MAC-Header
+100 12
+CRC
+112 8
+Tail
+ $120 \times 3 = 360$
+Conv. Coding 1/3
+1st Interleaving (360)
+Repetition 0%
+Rate Matching (360)
+
+**Service Multiplex.** 362 90 362 90 362 90 362 90
+
+**2nd Interleaving** 452 452 452 452
+
+**TFCI / TPC** 452 16 2 452 16 2 452 16 2 452 16 2
+
+**Slot segmentation**
+SF=8
+228 CI MA PC CI 224 228 CI MA PC CI 224 228 CI MA PC CI 224 228 CI MA PC CI 224
+8 512 2 8 8 512 2 8 8 512 2 8 8 512 2 8
+chips chips chips chips
+
+**Radio Frame #1 Radio Frame #2 Radio Frame #3 Radio Frame #4**
+
+Figure A.1: Data flow diagram for 1,28 Mcps option. It shows the processing of information data (244 bits) through CRC attachment, tail bit attachment, convolutional coding (1/3), and interleaving. The data is then split into four radio frames. Each frame undergoes RF-segmentation, puncturing (10% level), and service multiplexing with DCCH data (90 bits). The resulting 452 bits are further interleaved and then segmented into slots for transmission. The DCCH section shows MAC-Header (4, 96), CRC (100, 12), and tail bits (112, 8) being processed similarly. The final slot structure for each radio frame is 228 chips (CI), 512 chips (MA), 2 chips (PC), 2 chips (CI), and 224 chips (CI).
+
+Figure A.1
+
+## A.2.1.2 1,28 Mcps option
+
+Table A.1A
+
+| Parameter | Value |
+|----------------------------------------------------------------------|-----------------------|
+| Information data rate | 12.2 kbps |
+| RU's allocated | 1TS (1*SF8) = 2RU/5ms |
+| Midamble | 144 |
+| Interleaving | 20 ms |
+| Power control | 4 Bit/user/10ms |
+| TFCI | 16 Bit/user/10ms |
+| Synchronisation Shift (SS) | 4 Bit/user/10ms |
+| Inband signalling DCCH | 2.4 kbps |
+| Puncturing level at Code rate 1/3 : DCH of the DTCH/ DCH of the DCCH | 33% / 33% |
+
+
+
+The diagram illustrates the data flow for a 7,68 Mcps TDD Option. It shows the processing of information bits through several stages:
+
+- Information:** 244 bits are input to the CRC stage.
+- CRC:** 16 bits are added to the information bits, resulting in 260 bits (244 + 16).
+- Tail bit:** 8 tail bits are added, resulting in 268 bits (260 + 8).
+- Conv. Coding:** The 268 bits are convolutedly coded with a rate of 1/3, resulting in 804 bits ((260+8)\*3=804).
+- 1st Interleaving:** The 804 bits are interleaved, resulting in 402 bits (804/2).
+- RF-:** The 402 bits are further processed, resulting in 402 bits.
+- Rate:** The 402 bits are rate-matched to 268 bits. The puncturing level is 4 RU = 88 \* 4 = 352 bits. The gross rate is 352 bits, which includes TFCI (16 bit), TPC (4 bit), SS (4 bit), and puncturing (60 bit).
+- Service:** The 268 bits are mapped to the service layer, resulting in 328 bits (268 + 60).
+- 2nd Interleaving:** The 328 bits are interleaved, resulting in 176 bits (328/2).
+- TFCI, TPC and Physical Channel:** The 176 bits are mapped to the physical channel, resulting in 176 bits.
+- Slot:** The 176 bits are mapped to the slot structure (SF=8), resulting in 84 bits per slot (144 chp / 4 = 36, 84 + 36 = 120, 120 + 4 = 124, 124 + 4 = 128, 128 + 4 = 132, 132 + 4 = 136, 136 + 4 = 140, 140 + 4 = 144, 144 + 4 = 148, 148 + 4 = 152, 152 + 4 = 156, 156 + 4 = 160, 160 + 4 = 164, 164 + 4 = 168, 168 + 4 = 172, 172 + 4 = 176).
+
+The diagram also shows the mapping of the 268 bits to the physical channel across 8 sub-frames. The mapping is as follows:
+
+| Sub Frame | Slot 1 | Slot 2 |
+|--------------|--------|--------|
+| Sub Frame #1 | 268 | 60 |
+| Sub Frame #2 | 268 | 60 |
+| Sub Frame #3 | 268 | 60 |
+| Sub Frame #4 | 268 | 60 |
+| Sub Frame #5 | 268 | 60 |
+| Sub Frame #6 | 268 | 60 |
+| Sub Frame #7 | 268 | 60 |
+| Sub Frame #8 | 268 | 60 |
+
+Figure A.1A: Data flow diagram showing the processing of information bits through various stages including CRC, tail bits, convolutional coding, rate matching, and physical channel mapping across 8 sub-frames.
+
+Figure A.1A
+
+### A.2.1.3 7,68 Mcps TDD Option
+
+Table A.1B
+
+| Parameter | Value |
+|-----------------------------------------------------------------------|-------------|
+| Information data rate | 12.2 kbps |
+| RU's allocated | 2 RU |
+| Midamble | 1024 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate 1/3 : DCH of the DTCH / DCH of the DCCH | 10% / 0% |
+
+
+
+**Information data processing:**
+
+- Information data: 244
+- CRC attachment: 244 | 16
+- Tail bit attachment: 260 bit/20ms | 8
+- Conv. Coding 1/3: $[(260 + 8) \times 3 = 804$
+- 1st Interleaving: 804 bit/20ms
+- RF-segmentation: 402 | 402
+- Puncturing Ratemaching: 402 bit punct. to 362 bit puncturing-level: 10%
+2 RU $\rightarrow$ 244x2 = 488 Bits available
+
+
+| gross | 488 bit |
+|----------|-------------|
+| -TFCI | -16 bit * 2 |
+| -TPC | -2 bit * 2 |
+| -Signal. | -90 bit |
+| punc. to | 362 bit |
+- Service Multiplex: 362 | 90
+- 2nd Interleaving: 452
+- TFCI / TPC: 452 | TF CI PC 16 2
+- Slot segmentation: SF=16 | 228 | TF CI MA PC 8 1024 2 8 | 224
+- Radio Frame #1 | Radio Frame #2 | Radio Frame #3 | Radio Frame #4
+
+**DCCH processing:**
+
+- DCCH: 4 | 96
+- MAC-Header: 100 | 12
+- CRC: 112 | 8
+- Tail: 120 x 3 = 360
+- Conv. Coding 1/3: 360
+- 1st Interleaving (360)
+- Repetition 0% Rate Matching (360)
+- 90 | 90 | 90 | 90
+
+Figure A.1B: Bit processing flow diagram for a 64 kbps UL reference measurement channel. The diagram shows the processing of information data and DCCH across four radio frames. Information data (244 bits) is processed through CRC, tail bits, convolutional coding (1/3), interleaving, and rate matching to produce 452 bits per frame. DCCH (4 bits info + 96 bits MAC header) is processed through CRC, tail bits, convolutional coding (1/3), interleaving, and rate matching to produce 90 bits per frame. The 452 bits and 90 bits are multiplexed and then processed through a second interleaving stage. Finally, the data is segmented into slots (SF=16) containing Midamble (MA), TFCI, and Power Control (PC) bits, resulting in four radio frames.
+
+Figure A.1B
+
+## A.2.2 UL reference measurement channel (64 kbps)
+
+### A.2.2.1 3,84 Mcps TDD option
+
+Table A.2
+
+| Parameter | Value |
+|---------------------------------------------------------------------------|----------------------|
+| Information data rate | 64 kbps |
+| RU's allocated | 1 SF4 + 1 SF16 = 5RU |
+| Midamble | 512 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 43.8% / 13.3% |
+
+
+
+**DCCH**
+
+Information data: 4, 96
+MAC-Header: 100, 12
+CRC: 112, 8
+Tail: 120 x 2 = 240
+Conv. Coding 1/2
+
+**Information data**: 1280, 1280
+
+**CRC attachment**: 1280, 16 | 1280, 16
+
+**Turbo Coding 1/3**: $[(640 \times 2) + 16] \times 3 = 3888$ | $[(640 \times 2) + 16] \times 2 = 3888$
+
+**Trellis-Termination**: 3888 bit/20ms, 12 | 3888 bit/20ms, 12
+
+**1st Interleaving**: 3900 bit/20ms | 3900 bit/20ms
+
+**RF-segmentation**: 1950, 1950 | 1950, 1950
+
+**Puncturing Ratematching**:
+1950 bit punct. to 1096 bit puncturing-level: 44%
+5 RU $\rightarrow$ 244x5 = 1220 Bits available
+
+| | |
+|----------|-------------|
+| gross | 1220 bit |
+| -TFCI | -16 bit * 4 |
+| -TPC | 2 bit * 4 |
+| -Signal. | -52 bit |
+| punc. to | 1096 bit |
+
+**Service Multiplex.**: 1096, 52 | 1096, 52 | 1096, 52 | 1096, 52
+
+**2nd Interleaving**: 1148 | 1148 | 1148 | 1148
+
+**TFCI / TPC**: 1148, 16, 2 | 1148, 16, 2 | 1148, 16, 2 | 1148, 16, 2
+
+**Slot segmentation**
+
+**SF=16**: 122 MA 122 | 122 MA 122 | 122 MA 122 | 122 MA 122
+
+**SF=4**: 456 TF CI MA PC TF CI 448 | 456 TF CI MA PC TF CI 448 | 456 TF CI MA PC TF CI 448 | 456 TF CI MA PC TF CI 448
+
+8 512 2 8 chips | 8 512 2 8 chips | 8 512 2 8 chips | 8 512 2 8 chips
+
+Radio Frame #1 | Radio Frame #2 | Radio Frame #3 | Radio Frame #4
+
+Figure A.2: Data flow diagram showing the processing of information data through various stages including CRC attachment, Turbo Coding, Interleaving, and Slot Segmentation for four radio frames. The diagram also shows the DCCH channel structure and the mapping of bits to slots for SF=16 and SF=4.
+
+Figure A.2
+
+## A.2.2.2 1,28 Mcps TDD option
+
+Table A.2A
+
+| Parameter | Value |
+|--------------------------------------------------------------------------|-----------------------|
+| Information data rate | 64 kbps |
+| RU's allocated | 1TS (1*SF2) = 8RU/5ms |
+| Midamble | 144 |
+| Interleaving | 20 ms |
+| Power control (TPC) | 4 Bit/user/10ms |
+| TFCI | 16 Bit/user/10ms |
+| Synchronisation Shift (SS) | 4 Bit/user/10ms |
+| Inband signalling DCCH | 2.4 kbps |
+| Puncturing level at Code rate: 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 32% / 0 |
+
+
+
+The diagram illustrates the data processing chain for the 7,68 Mcps TDD Option. It details the transformation of Information Data through several layers of coding, interleaving, and mapping.
+
+**Processing Chain Details:**
+
+- Information Data:** 1280 bits.
+- CRC attachment:** 1280 bits + 16 bits CRC.
+- Turbo Coding 1/3:** $((640*2)+16)*3=3888$ bits.
+- Trellis Termination:** 3888bit / 20ms, with 12 bits added.
+- Interleaving:** 3900bit / 20ms.
+- RF-Segmentation:** Splits 3900 bits into two 1950 bit segments.
+- Rate Matching:** 1950 bit punctured to 1324 bit. Puncturing Level: 32%. 16 RU = 88 \* 16 = 1408 Bits available.
+
+
+| | |
+|---------------|----------|
+| gross | 1408 bit |
+| - TFCI | - 16 bit |
+| - TPC | - 4 bit |
+| - SS | - 4 bit |
+| - Signalling | - 60 bit |
+| puncturing to | 1324 bit |
+- MAC-Header & DCCH:** 4 bit header + 96 bit DCCH = 100 bits + 12 bits CRC.
+- Convolutional Coding 1/2:** $((112+8)*2=240$ bits.
+- Service Multiplexing:** Combines 1324 bits and 60 bits into 1384 bits.
+- Physical Channel Mapping:** Maps 1384 bits into two 704 bit segments (with TFCI, TPC, and SS bits).
+- Slot Segmentation (SF=2):** Final physical layer format with 348 chips, 144 chips midamble, and TFCI/TPC/SS insertion.
+
+The process is repeated across **Sub Frame #1** through **Sub Frame #8**.
+
+Figure A.2A: Data flow diagram for 7,68 Mcps TDD Option showing processing from Information Data to Slot Segmentation across 8 sub-frames.
+
+Figure A.2A
+
+### A.2.2.3 7,68 Mcps TDD Option
+
+Table A.2B
+
+| Parameter | Value |
+|---------------------------------------------------------------------------|----------------------|
+| Information data rate | 64 kbps |
+| RU's allocated | 1 SF8 + 1 SF32 = 5RU |
+| Midamble | 1024 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 43.8% / 13.3% |
+
+
+
+**DCCH**
+
+| | |
+|---|----|
+| 4 | 96 |
+|---|----|
+
+MAC-Header
+
+| | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------|-------------|------|-----------|----------|---------|-----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------|-------|-------------|------|-----------|----------|---------|-----------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Information data | 1280
| 1280
| | | | | | | | | | | | | | | | | | | | | |
+| CRC attachment | 1280 16
| 1280 16
| 100 12
CRC | | | | | | | | | | | | | | | | | | | | |
+| Turbo Coding 1/3 | | | 112 8
Tail | | | | | | | | | | | | | | | | | | | | |
+| Trellis-Termination | 3888 bit/20ms 12
| 3888 bit/20ms 12
| 120 x 2 = 240
Conv. Coding 1/2 | | | | | | | | | | | | | | | | | | | | |
+| 1 st Interleaving | 3900 bit/20ms
| 3900 bit/20ms
| 1st Interleaving (240)
| | | | | | | | | | | | | | | | | | | | |
+| RF-segmentation | 1950 1950
| 1950 1950
| | | | | | | | | | | | | | | | | | | | | |
+| Puncturing Ratemaching | 1950 bit punct. to 1096 bit
puncturing-level: 44%
5 RU → 244x5 =
1220 Bits available
| gross | 1220 bit |
| -TFCI | -16 bit * 4 |
| -TPC | 2 bit * 4 |
| -Signal. | -52 bit |
| punc. to | 1096 bit |
1950 bit punct. to 1096 bit
puncturing-level: 44%
5 RU → 244x5 =
1220 Bits available
| gross | 1220 bit |
| -TFCI | -16 bit * 4 |
| -TPC | 2 bit * 4 |
| -Signal. | -52 bit |
| punc. to | 1096 bit |
Puncturing 13%
Rate Matching (208)
|
+| gross | 1220 bit | | | | | | | | | | | | | | | | | | | | | | |
+| -TFCI | -16 bit * 4 | | | | | | | | | | | | | | | | | | | | | | |
+| -TPC | 2 bit * 4 | | | | | | | | | | | | | | | | | | | | | | |
+| -Signal. | -52 bit | | | | | | | | | | | | | | | | | | | | | | |
+| punc. to | 1096 bit | | | | | | | | | | | | | | | | | | | | | | |
+| gross | 1220 bit | | | | | | | | | | | | | | | | | | | | | | |
+| -TFCI | -16 bit * 4 | | | | | | | | | | | | | | | | | | | | | | |
+| -TPC | 2 bit * 4 | | | | | | | | | | | | | | | | | | | | | | |
+| -Signal. | -52 bit | | | | | | | | | | | | | | | | | | | | | | |
+| punc. to | 1096 bit | | | | | | | | | | | | | | | | | | | | | | |
+
+1096
+
+1096
+
+1096
+
+1096
+
+52
+
+52
+
+52
+
+52
+
+Service Multiplex.
+
+1096 | 52
+
+1096 | 52
+
+1096 | 52
+
+1096 | 52
+
+2nd Interleaving
+
+1148
+
+1148
+
+1148
+
+1148
+
+TFCI / TPC
+
+1148 | TF CI T PC
+16 2
+
+1148 | TF CI T PC
+16 2
+
+1148 | TF CI T PC
+16 2
+
+1148 | TF CI T PC
+16 2
+
+---
+
+Slot segmentation
+
+SF=32
+
+122
+
+MA
+
+122
+
+122
+
+MA
+
+122
+
+122
+
+MA
+
+122
+
+122
+
+MA
+
+122
+
+SF=8
+
+456
+
+TF CI
+
+MA
+
+T PC
+
+TF CI
+
+448
+
+8 1024 2 8 chips
+Radio Frame #1
+
+456
+
+TF CI
+
+MA
+
+T PC
+
+TF CI
+
+448
+
+8 1024 2 8 chips
+Radio Frame #2
+
+456
+
+TF CI
+
+MA
+
+T PC
+
+TF CI
+
+448
+
+8 1024 2 8 chips
+Radio Frame #3
+
+456
+
+TF CI
+
+MA
+
+T PC
+
+TF CI
+
+448
+
+8 1024 2 8 chips
+Radio Frame #4
+
+Diagram showing the processing flow of DCCH data across four radio frames. It details steps from information data and MAC-header to slot segmentation for SF=32 and SF=8. The diagram includes tables for puncturing calculations and visual representations of bit blocks at various stages.
+
+Figure A.2B
+
+## A.2.3 UL reference measurement channel (144 kbps)
+
+### A.2.3.1 3,84 Mcps TDD option
+
+**Table A.3**
+
+| Parameter | Value |
+|---------------------------------------------------------------------------|----------------------|
+| Information data rate | 144 kbps |
+| RU's allocated | 1 SF2 + 1 SF16 = 9RU |
+| Midamble | 256 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 47.3% / 20% |
+
+
+
+**DCCH**
+
+| | |
+|---|----|
+| 4 | 96 |
+|---|----|
+
+MAC-Header
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-------------|--------------------------------------------------------------------------------------------------------------------|------------|----------|---------|-----------------|-----------------|--------------|-----------------|-------|-------------|------|------------|----------|---------|-----------------|-----------------|-------------------------------------------------------------------------------------------------------|----|----|----|----|
+| Information data | 2880 | 2880 |
CRC | 100 | 12 | | | | | | | | | | | | | | | | | | | | | | |
+| 100 | 12 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CRC attachment | | | 2880 | 16 | 2880 | 16 |
Tail | 112 | 8 | | | | | | | | | | | | | | | | | | |
+| 2880 | 16 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 2880 | 16 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 112 | 8 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Turbo Coding 1/3 | $[(1440 \times 2) + 16] \times 3 = 8688$ | $[(1440 \times 2) + 16] \times 3 = 8688$ | 120 x 2= 240
Conv. Coding 1/2 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Trellis-Termination | | 8688 bit/20ms | 12 | | 8688 bit/20ms | 12 | 1st Interleaving (240)
| | | | | | | | | | | | | | | | | | | | |
+| 8688 bit/20ms | 12 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 8688 bit/20ms | 12 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 1 st Interleaving | 8700 bit/20ms | 8700 bit/20ms | Puncturing 20%
Rate Matching (192)
| | | | | | | | | | | | | | | | | | | | | | | | |
+| RF-segmentation | | 4350 | | 4350 | | 4350 | 4350 | | | | | | | | | | | | | | | | | | | | |
+| 4350 | 4350 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 4350 | 4350 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Puncturing Ratemaching | 4350 bit punct. to 2292 bit puncturing-level:
47% 2484 Bits available
| gross | 2484 bit |
| -TFCI | -16 bit * 8 |
| -TPC | -2 bit * 8 |
| -Signal. | -48 bit |
| punc. to | 2292 bit |
4350 bit punct. to 2292 bit puncturing-level:
47% 2484 Bits available
| gross | 2484 bit |
| -TFCI | -16 bit * 8 |
| -TPC | -2 bit * 8 |
| -Signal. | -48 bit |
| punc. to | 2292 bit |
| | gross | 2484 bit | -TFCI | -16 bit * 8 | -TPC | -2 bit * 8 | -Signal. | -48 bit | punc. to | 2292 bit | gross | 2484 bit | -TFCI | -16 bit * 8 | -TPC | -2 bit * 8 | -Signal. | -48 bit | punc. to | 2292 bit | | 48 | 48 | 48 | 48 |
+| gross | 2484 bit | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| -TFCI | -16 bit * 8 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| -TPC | -2 bit * 8 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| -Signal. | -48 bit | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| punc. to | 2292 bit | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| gross | 2484 bit | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| -TFCI | -16 bit * 8 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| -TPC | -2 bit * 8 | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| -Signal. | -48 bit | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| punc. to | 2292 bit | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 48 | 48 | 48 | 48 | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | |
+|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------|----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|--------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------|-------------------------|
+| Service Multiplex. | | 2292 | 48 | | 2292 | 48 | | 2292 | 48 | | 2292 | 48 | | | | |
+| 2292 | 48 | | | | | | | | | | | | | | | |
+| 2292 | 48 | | | | | | | | | | | | | | | |
+| 2292 | 48 | | | | | | | | | | | | | | | |
+| 2292 | 48 | | | | | | | | | | | | | | | |
+| 2 nd Interleaving | 2340 | 2340 | 2340 | 2340 | | | | | | | | | | | | |
+| TFCI / TPC |
16 2 | 2340 | TF
CI | T
PC |
16 2 | 2340 | TF
CI | T
PC |
16 2 | 2340 | TF
CI | T
PC |
16 2 | 2340 | TF
CI | T
PC |
+| 2340 | TF
CI | T
PC | | | | | | | | | | | | | | |
+| 2340 | TF
CI | T
PC | | | | | | | | | | | | | | |
+| 2340 | TF
CI | T
PC | | | | | | | | | | | | | | |
+| 2340 | TF
CI | T
PC | | | | | | | | | | | | | | |
+
+---
+
+Slot segmentation
+
+SF=16
+
+| | | |
+|-----|----|-----|
+| 138 | MA | 138 |
+|-----|----|-----|
+
+| | | |
+|-----|----|-----|
+| 138 | MA | 138 |
+|-----|----|-----|
+
+| | | |
+|-----|----|-----|
+| 138 | MA | 138 |
+|-----|----|-----|
+
+| | | |
+|-----|----|-----|
+| 138 | MA | 138 |
+|-----|----|-----|
+
+SF=2
+
+| | | | | | |
+|------|----------|-----|---------|----------|------|
+| 1040 | TF
CI | MA | T
PC | TF
CI | 1024 |
+| | 8 | 256 | 2 | 8 | |
+
+chips
+Radio Frame #1
+
+| | | | | | |
+|------|----------|-----|---------|----------|------|
+| 1040 | TF
CI | MA | T
PC | TF
CI | 1024 |
+| | 8 | 256 | 2 | 8 | |
+
+chips
+Radio Frame #2
+
+| | | | | | |
+|------|----------|-----|---------|----------|------|
+| 1040 | TF
CI | MA | T
PC | TF
CI | 1024 |
+| | 8 | 256 | 2 | 8 | |
+
+chips
+Radio Frame #3
+
+| | | | | | |
+|------|----------|-----|---------|----------|------|
+| 1040 | TF
CI | MA | T
PC | TF
CI | 1024 |
+| | 8 | 256 | 2 | 8 | |
+
+chips
+Radio Frame #4
+
+Diagram illustrating the data processing flow for a DCCH channel and DTCH channels, showing steps from information data input to slot segmentation across four radio frames.
+
+**Figure A.3**
+
+### A.2.3.2 1,28 Mcps TDD option
+
+**Table A.3A**
+
+| Parameter | Value |
+|------------------------------------------------------------------------|------------------------|
+| Information data rate | 144 kbps |
+| RU's allocated | 2TS (1*SF2) = 16RU/5ms |
+| Midamble | 144 |
+| Interleaving | 20 ms |
+| Power control (TPC) | 8 Bit/user/10ms |
+| TFCI | 32 Bit/user/10ms |
+| Synchronisation Shift (SS) | 8 Bit/user/10ms |
+| Inband signalling DCCH | 2.4 kbps |
+| Puncturing level at Code rate: 1/3 DCH of the DTCH / ½ DCH of the DCCH | 38% / 7% |
+
+
+
+Information Data: 2880 (x2 paths)
+
+CRC attachment: 2880 | 16
+
+Turbo Coding 1/3: $[(1440 \cdot 2) + 16] \cdot 3 = 8688$
+
+Trellis Termination: 8688bit / 20ms | 12
+
+1st Interleaving: 8700bit / 20ms
+
+RF-Segmentation: 4350 | 4350
+
+Rate Matching:
+4350 bit punctured to 2712 bit
+Puncturing Level: 38%
+32 RU = 88 \* 32 = 2816 Bits available
+
+| | |
+|---------------|----------|
+| gross | 2816 bit |
+| - TFCI | - 32 bit |
+| - TPC | - 8 bit |
+| - SS | - 8 bit |
+| - Signalling | - 56 bit |
+| puncturing to | 2712 bit |
+
+MAC-Header: 4 | 96 DCCH
+
+CRC: 100 | 12
+
+112 | 8
+
+Convolutional Coding 1/2: $(112+8) \cdot 2 = 240$
+
+240bit
+
+Rate Matching (224): Puncturing Level: 7%
+
+Service Multiplexing: 2712 | 56 (per path)
+
+2nd Interleaving: 2768
+
+TFCI, TPC and SS: 2768 | 32 | 16
+
+Physical Channel Mapping: 1408 | 1408
+
+Slot segmentation: SF=2, 2 Timeslots
+
+Sub Frame #1 | Sub Frame #2 | Sub Frame #3 | Sub Frame #4 | Sub Frame #5 | Sub Frame #6 | Sub Frame #7 | Sub Frame #8
+
+Figure A.3A: Data flow diagram for 7,68 Mcps TDD Option. The diagram illustrates the processing chain from Information Data and DCCH through various coding, interleaving, and multiplexing stages to final slot segmentation across 8 sub-frames.
+
+Figure A.3A
+
+### A.2.3.3 7,68 Mcps TDD Option
+
+Table A.3B
+
+| Parameter | Value |
+|---------------------------------------------------------------------------|----------------------|
+| Information data rate | 144 kbps |
+| RU’s allocated | 1 SF4 + 1 SF32 = 9RU |
+| Midamble | 512 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 47.3% / 20% |
+
+
+
+The diagram depicts the physical layer processing chain for data and control channels.
+
+### Data Path Processing (Two Parallel Streams)
+
+- Information data:** 2880 bits
+- CRC attachment:** 2880 + 16 bits
+- Turbo Coding 1/3:** $[(1440 \times 2) + 16] \times 3 = 8688$ bits
+- Trellis-Termination:** 8688 bit/20ms (with 12 bits tail)
+- 1st Interleaving:** 8700 bit/20ms
+- RF-segmentation:** Split into two 4350 bit blocks
+- Puncturing Ratematching:** 4350 bit punct. to 2292 bit (puncturing-level: 47%).
+ 9 RU → $276 \times 9 = 2484$ Bits available.
+
+
+| | |
+|-----------------|-----------------|
+| gross | 2484 bit |
+| -TFCI | -16 bit * 8 |
+| -TPC | -2 bit * 8 |
+| -Signal. | -48 bit |
+| punc. to | 2292 bit |
+
+### DCCH Path Processing
+
+- Information data:** 4 | 96 (MAC-Header | Data)
+- CRC attachment:** 100 | 12 (Data | CRC)
+- Convolutional Coding 1/2:** 112 | 8 (Data | Tail) → $120 \times 2 = 240$ bits
+- 1st Interleaving (240)**
+- Puncturing 20% Rate Matching (192):** Results in four 48-bit segments.
+
+### Multiplexing and Slot Segmentation
+
+- Service Multiplex.:** Combines 2292 bits (Data) and 48 bits (DCCH).
+
+
+| | |
+|------|----|
+| 2292 | 48 |
+|------|----|
+- 2nd Interleaving:** 2340 bits
+- TFCI / TPC:**
+
+| | | |
+|------|-------|------|
+| 2340 | TF CI | T PC |
+| | 16 | 2 |
+- Slot segmentation:**
+ - SF=32:**
+
+| | | |
+|-----|----|-----|
+| 138 | MA | 138 |
+|-----|----|-----|
+ - SF=4:**
+
+| | | | | | |
+|---------|-----------|----|---------|---------|------|
+| 1040 | TF CI | MA | T PC | TF CI | 1024 |
+| 8 chips | 512 chips | | 2 chips | 8 chips | |
+
+The process is repeated across **Radio Frame #1**, **Radio Frame #2**, **Radio Frame #3**, and **Radio Frame #4**.
+
+Figure A.3B: Detailed data flow diagram for physical layer processing including Turbo coding, rate matching, and slot segmentation for SF=32 and SF=4.
+
+Figure A.3B
+
+## A.2.4 UL reference measurement channel (384 kbps)
+
+### A.2.4.1 3,84 Mcps TDD option
+
+Table A.4
+
+| Parameter | Value |
+|---------------------------------------------------------------------------|--------------|
+| Information data rate | 384 kbps |
+| RU's allocated | 8*3TS = 24RU |
+| Midamble | 256 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 44% / 15.3% |
+
+
+
+The diagram illustrates the physical layer processing for the UL reference measurement channel. It is divided into two main data paths: Information data and DCCH.
+
+- Information Data Path:**
+ - Starts with four blocks of 3840 bits.
+ - CRC attachment adds 16 bits to each block.
+ - Turbo Coding 1/3 results in $[(3840+16) \times 2] \times 3 = 23136$ bits per block.
+ - Trellis-Termination adds 24 bits per block.
+ - 1st Interleaving results in 23160 bits per block.
+ - RF-segmentation splits each into two 11580 bit segments.
+ - Puncturing Ratematching (44% level) reduces each 11580 bit segment to 6429 bits. A table shows the breakdown:
+
+
+| | |
+|----------|-------------|
+| gross | 6624 bit |
+| -TFCI | -16 bit * 8 |
+| -TPC | -2 bit * 8 |
+| -Signal. | -51 bit |
+| punc. to | 6429 bit |
+ - Service Multiplex. combines each 6429 bit segment with 51 bits from the DCCH path.
+ - 2nd Interleaving results in 6480 bits per segment.
+ - TFCI / TPC adds 16 bits for TFCI and 2 bits for TPC.
+ - Slot segmentation for SF=2 (3 Timeslots) results in a frame structure of 1040 bits, followed by IF CI, MA, T PC, IF CI, and 1024 bits, totaling 256 chips per timeslot.
+- DCCH Path:**
+ - Starts with 4 bits of MAC-Header and 96 bits of data.
+ - CRC attachment adds 12 bits.
+ - Tail bits are added.
+ - Conv. Coding 1/2 results in 120 x 2 = 240 bits.
+ - 1st Interleaving (240) and Puncturing 15% Rate Matching (204) result in four blocks of 51 bits each.
+
+The final output shows four Radio Frames (Radio Frame #1 to #4), each containing three timeslots (TS #1..#3).
+
+Figure A.4: Detailed block diagram of the UL reference measurement channel processing flow for 384 kbps at 3.84 Mcps TDD option. The diagram shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation across four radio frames.
+
+Figure A.4
+
+## A.2.4.2 1,28 Mcps TDD option
+
+Table A.4A
+
+| Parameter | Value |
+|--------------------------------------------------------------------------|---------------------------------|
+| Information data rate | 384 kbps |
+| RU's allocated | 4TS (1*SF2 + 1*SF16) = 36RU/5ms |
+| Midamble | 144 |
+| Interleaving | 20 ms |
+| Power control (TPC) | 16 Bit/user/10ms |
+| TFCI | 64 Bit/user/10ms |
+| Synchronisation Shift (SS) | 16 Bit/user/10ms |
+| Inband signalling DCCH | 2.4 kbps |
+| Puncturing level at Code rate: 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 47% / 12% |
+
+
+
+The diagram illustrates the data processing flow for the 1,28 Mcps TDD option across eight sub-frames. The main data path starts with 'Information Data' (3840 bits) which undergoes 'CRC attachment' (adding 16 bits), 'Turbo Coding 1/3' (resulting in $((3840+16)*2)*3=23136$ bits), 'Trellis Termination' (24 bits), '1st Interleaving' (23160bit / 20ms), and 'RF-Segmentation' (11580 bits). This is followed by 'Rate Matching' where 11580 bits are punctured to 6187 bits at a 47% puncturing level. A table for Rate Matching (100) shows the gross output of 6336 bits, with deductions for TFCI (64 bit), TPC (16 bit), and SS (16 bit), and 53 bits for Signalling, resulting in 6187 bits. These are then processed through 'Service Multiplexing' (6187 + 53 bits), '2nd Interleaving' (6240 bits), 'TFCI, TPC and SS' (6240 + 64 + 32 bits), and 'Physical Channel Mapping' (3168 bits). The final 'Slot segmentation' for SF=16 (4 Timeslots) and SF=2 (4 Timeslots) shows the mapping of bits to chips (144 chips per timeslot). A secondary path for 'DCCH' (MAC-Header 4, 96) shows 'Convolutional Coding 1/2' (112 + 8 bits) and 'Puncturing Level: 12% Rate Matching (165)' resulting in 53 bits per sub-frame.
+
+Figure A.4A: Data flow diagram for 1,28 Mcps TDD option showing the processing of information data and DCCH across multiple sub-frames.
+
+Figure A.4A
+
+## A.2.4.3 7,68 Mcps TDD Option
+
+Table A.4B
+
+| Parameter | Value |
+|---------------------------------------------------------------------------|---------------|
+| Information data rate | 384 kbps |
+| RU's allocated | 8*3TS = 24RU |
+| Midamble | 512 chips |
+| Interleaving | 20 ms |
+| Power control | 2 Bit/user |
+| TFCI | 16 Bit/user |
+| Inband signalling DCCH | 2 kbps |
+| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 43.4% / 15.3% |
+
+
+
+**Information Data Processing:**
+
+- Information data:** Four blocks of 3840 bits.
+- CRC attachment:** Each 3840-bit block has a 16-bit CRC attached, resulting in 3856-bit blocks.
+- Turbo Coding 1/3:** Each 3856-bit block is turbo-coded to produce 23136 bits ([(3840+16)x2] x 3 = 23136).
+- Trellis-Termination:** 24 tail bits are added to each 23136-bit block.
+- 1st Interleaving:** Each 23160-bit block is interleaved.
+- RF-segmentation:** Each 23160-bit block is segmented into two 11580-bit blocks.
+- Puncturing Ratemaching:** Each 11580-bit block is punctured to 6429 bits at a 44% puncturing level.
+
+
+| | |
+|-----------------|-----------------|
+| gross | 6624 bit |
+| -TFCI | -16 bit * 8 |
+| -TPC | -2 bit * 8 |
+| -Signal. | -51 bit |
+| punc. to | 6429 bit |
+- Service Multiplex.:** Each 6429-bit block is multiplexed with 51 bits from the DCCH, resulting in 6480-bit blocks.
+- 2nd Interleaving:** Each 6480-bit block is interleaved.
+- TFCI / TPC:** Each 6480-bit block is further segmented into 16 TFCI bits and 2 TPC bits.
+- Slot segmentation:** Each 6480-bit block is segmented into two 1040-bit slots, with a 512-chip midamble (MA) and TFCI/TPC bits (TFCI=16, TPC=2) inserted.
+
+
+| | | | | |
+|------|------|----|-----|------|
+| 1040 | TFCI | MA | TPC | 1024 |
+|------|------|----|-----|------|
+
+ This results in 3 timeslots per radio frame (SF=4).
+- Radio Frames:** The process results in four radio frames (Radio Frame #1 to #4).
+
+**DCCH Processing:**
+
+- DCCH:** 4 MAC-Header (96 bits) + 100 CRC (12 bits) + 112 Tail (8 bits) = 120 bits.
+- Conv. Coding 1/2:** 120 bits are convolutedly coded to 240 bits (120 x 2 = 240).
+- 1st Interleaving (240):** The 240 bits are interleaved.
+- Puncturing 15% Rate Matching (204):** The 240 bits are punctured to 204 bits (15% puncturing level).
+- Service Multiplex.:** The 204 bits are divided into four 51-bit segments for multiplexing with the information data.
+
+Figure A.4B: Detailed bit processing flow diagram for 7,68 Mcps TDD Option. It shows the processing of information data (384 kbps) and DCCH (2 kbps) through various stages including CRC attachment, Turbo coding, interleaving, rate matching, and slot segmentation into radio frames.
+
+Figure A.4B
+
+## A.2.5 RACH reference measurement channel
+
+### A.2.5.1 3,84 Mcps TDD option
+
+Table A.5
+
+| Parameter | Value |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| Information data rate e.g. 2 TBs ( $B_{RACH}=2$ ):
SF16:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2
$N_{RACH} = \frac{\frac{232 + N_{RM}}{2} - 8}{B_{RACH}}$
SF8:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2
$N_{RACH} = \frac{\frac{464 + N_{RM}}{2} - 16}{B_{RACH}}$ | 46 bits per frame and TB
53 bits per frame and TB
96 bits per frame and TB
109 bits per frame and TB |
+| RU's allocated | 1 RU |
+| Midamble | 512 chips |
+| Power control | 0 bit |
+| TFCI | 0 bit |
+
+$N_{RACH}$ = number of bits per TB
+
+$B_{RACH}$ = number of TBs
+
+#### A.2.5.1.1 RACH mapped to 1 code SF16
+
+
+
+The diagram illustrates the mapping of RACH data to a Radio Frame #1 for SF=16. It shows the following stages:
+
+- Information data:** Divided into $N_{RACH}$ bits per TB, with $B_{RACH}$ TBs per frame.
+- CRC attachment:** 8 bits are added to each TB, resulting in $N_{RACH} + 8$ bits per TB.
+- Tail bit attachment:** 8 tail bits are added to each TB, resulting in $(N_{RACH} + 8) \times B_{RACH}$ bits per frame.
+- Convolutional Coding 1/2:** The data is encoded, resulting in $[(N_{RACH} + 8) \times B_{RACH} + 8] \times 2$ bits per frame.
+- Puncturing Ratemaching:** The encoded data is punctured to achieve a rate of 1/2, resulting in $[(N_{RACH} + 8) \times B_{RACH} + 8] \times 2 - N_{RM} = 232$ bits per frame.
+- 2nd Interleaving:** The data is interleaved, resulting in 232 bits per frame.
+- Slot segmentation:** The data is mapped to slots in a Radio Frame #1. For SF=16, the frame consists of 122 slots for information data, 1 slot for Midamble (MA), and 110 slots for tail bits. The total number of chips is 512.
+
+Diagram illustrating the mapping of RACH data to a Radio Frame #1 for SF=16. The diagram shows the flow from Information data to CRC attachment, Tail bit attachment, Convolutional Coding 1/2, Puncturing Ratemaching, 2nd Interleaving, and finally Slot segmentation into a Radio Frame #1.
+
+Figure A.5
+
+## A.2.5.1.2 RACH mapped to 1 code SF8
+
+
+
+The diagram illustrates the bit processing stages for RACH mapping to 1 code SF8:
+
+- Information data:** Shown as a sequence of blocks labeled $N_{RACH}$ for TB #1 and TB # $B_{RACH}$ .
+- CRC attachment:** Each TB is followed by a 16-bit CRC block.
+- Tail bit attachment:** Each TB with CRC is followed by 8 tail bits. The total length for one TB is $(N_{RACH} + 16) \times B_{RACH} + 8$ .
+- Convolutional Coding 1/2:** The total length is doubled to $[(N_{RACH} + 16) \times B_{RACH} + 8] \times 2$ .
+- Puncturing Ratematching:** The length is reduced to $[(N_{RACH} + 16) \times B_{RACH} + 8] \times 2 - N_{RM} = 464$ .
+- 2nd Interleaving:** The resulting 464 bits are interleaved.
+- Slot segmentation:** The 464 bits are mapped to a slot. For SF=16, this is shown as 244 bits, a Midamble (MA), and 220 bits, totaling 512 chips for Radio Frame #1.
+
+Diagram of RACH mapping to 1 code SF8 showing bit processing stages from information data to slot segmentation.
+
+Figure A.6
+
+## A.2.5.2 1,28 Mcps TDD option
+
+Table A5.A
+
+| Parameter | Value |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Information data rate:
$88 * \frac{16}{SF} \left( \frac{N_{RM}}{100} + 1 \right) - 8$ $N_{RACH} = \frac{2}{B_{RACH}} - 16$ SF16 (RU's allocated:1):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2
SF8 (RU's allocated:2):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2
SF4 (RU's allocated:4):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2 | Transport Block Set Size=1
CRC length = 16
Tail Bits = 8
20 bits per frame and TB
24 bits per frame and TB
64 bits per frame and TB
73 bits per frame and TB
152 bits per frame and TB
170 bits per frame and TB |
+| TTI | 5msec |
+| Midamble | 144 chips |
+| Power control | 0 bit |
+| TFCI | 0 bit |
+
+ $N_{RACH}$ = number of bits per TB $B_{RACH}$ = number of TBs $N_{RM}$ = puncturing rate
+
+## A.2.5.2.1 RACH mapped to 1 code SF16
+
+
+
+| | #1 | ... | #B RACH |
+|------------------------------|-----------------------------------------------------------------------------|-----------------|------------------------|
+| Information data | N RACH | | N RACH |
+| CRC attachment | N RACH 16 | | N RACH 16 |
+| Tail bit attachment | (N RACH +16) x B RACH 8 | | |
+| Convolutional Coding 1/2 | [(N RACH +16) x B RACH +8] x 2 | | |
+| Puncturing Ratematching | [(N RACH +16) x B RACH +8] x 2 - N RM = 88 | | |
+| 2 nd Interleaving | 88 | | |
+| Slot segmentation | | | |
+| SF=16 | 44 | MA
144 chips | 44 |
+
+Radio Subframe #1
+5msec
+
+Figure A.5A: RACH mapping to 1 code SF16. The diagram shows the processing steps for a RACH preamble. It starts with Information data (N\_RACH bits) across #1 to #B\_RACH blocks. CRC attachment adds 16 bits. Tail bit attachment adds 8 bits. Convolutional Coding 1/2 doubles the bits. Puncturing/Ratematching results in 88 bits. 2nd Interleaving results in 88 bits. Slot segmentation for SF=16 results in 44 bits, MA (144 chips), and 44 bits, totaling 144 chips. The entire process is labeled as Radio Subframe #1, 5msec.
+
+Figure A.5A
+
+## A.2.5.2.2 RACH mapped to 1 code SF8
+
+
+
+| | #1 | ... | #B RACH |
+|------------------------------|-----------------------------------------------------------------------------|-----------------|------------------------|
+| Information data | N RACH | | N RACH |
+| CRC attachment | N RACH 16 | | N RACH 16 |
+| Tail bit attachment | (N RACH +16) x B RACH 8 | | |
+| Convolutional Coding 1/2 | [(N RACH +16) x B RACH +8] x 2 | | |
+| Puncturing Ratematching | [(N RACH +16) x B RACH +8] x 2 - N RM = 16 | | |
+| 2 nd Interleaving | 16 | | |
+| Slot segmentation | | | |
+| SF=8 | 88 | MA
144 chips | 88 |
+
+Radio Subframe #1
+5msec
+
+Figure A.6A: RACH mapping to 1 code SF8. The diagram shows the processing steps for a RACH preamble. It starts with Information data (N\_RACH bits) across #1 to #B\_RACH blocks. CRC attachment adds 16 bits. Tail bit attachment adds 8 bits. Convolutional Coding 1/2 doubles the bits. Puncturing/Ratematching results in 16 bits. 2nd Interleaving results in 16 bits. Slot segmentation for SF=8 results in 88 bits, MA (144 chips), and 88 bits, totaling 144 chips. The entire process is labeled as Radio Subframe #1, 5msec.
+
+Figure A.6A
+
+## A.2.5.2.3 RACH mapped to 1 code SF4
+
+Figure A.7
+
+## A.2.5.3 7,68 Mcps TDD option
+
+Table A5.B
+
+| Parameter | Value |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| Information data rate e.g. 2 TBs ( $B_{RACH}=2$ ):
SF32:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2
SF16:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2 | 46 bits per frame and TB
53 bits per frame and TB
96 bits per frame and TB
109 bits per frame and TB |
+| RU's allocated | 1 RU for SF32, 2 RUs for SF16 |
+| Midamble | 1024 chips |
+| Power control | 0 bit |
+| TFCI | 0 bit |
+
+$N_{RACH}$ = number of bits per TB
+
+$B_{RACH}$ = number of TBs
+
+## A.2.5.3.1 RACH mapped to 1 code SF16
+
+
+
+The diagram illustrates the RACH mapping process for SF16. It shows the flow of data through various processing stages:
+
+- Information data:** The initial data is split into $B_{RACH}$ transport blocks (TBs). The first TB (#1) and the last TB (# $B_{RACH}$ ) each contain $N_{RACH}$ bits.
+- CRC attachment:** A 16-bit CRC is attached to each TB, resulting in $N_{RACH} + 16$ bits per TB.
+- Tail bit attachment:** 8 tail bits are added to each TB, resulting in $(N_{RACH} + 16) \times B_{RACH} + 8$ bits total.
+- Convolutional Coding 1/2:** The data is then convolutedly coded with a rate of 1/2, doubling the number of bits to $[(N_{RACH} + 16) \times B_{RACH} + 8] \times 2$ .
+- Puncturing Ratematching:** Puncturing is applied to achieve the desired rate, resulting in $[(N_{RACH} + 16) \times B_{RACH} + 8] \times 2 - N_{RM} = 464$ bits.
+- 2nd Interleaving:** The bits are then interleaved, resulting in 464 bits.
+- Slot segmentation:** The bits are segmented into slots. For SF=16, each slot contains 244 data bits, 1024 midamble (MA) chips, and 220 tail bits.
+- Radio Frame #1:** The segmented slots form the structure of Radio Frame #1.
+
+Diagram illustrating the RACH mapping process for SF16, showing the flow from information data through CRC, tail bits, convolutional coding, puncturing, interleaving, and slot segmentation to form a radio frame.
+
+Figure A.8
+
+### A.2.5.3.2 RACH mapped to 1 code SF32
+
+
+
+The diagram illustrates the RACH mapping process for 1 code SF32. It shows the flow from Information data and CRC/Tail bit attachments through Convolutional Coding, Puncturing, and Interleaving to Slot segmentation, resulting in a Radio Frame #1 with SF=32, 122 MA, and 110 chips (1024 total).
+
+**Information data:** #1 ( $N_{RACH}$ ) ... # $B_{RACH}$ ( $N_{RACH}$ )
+
+**CRC attachment:** ( $N_{RACH}$ 8) ... ( $N_{RACH}$ 8)
+
+**Tail bit attachment:** ( $(N_{RACH}+8) \times B_{RACH}$ 8)
+
+**Convolutional Coding 1/2:** $[(N_{RACH}+8) \times B_{RACH} + 8] \times 2$
+
+**Puncturing Ratematching:** $[(N_{RACH}+8) \times B_{RACH} + 8] \times 2 - N_{RM} = 232$
+
+**2nd Interleaving:** 232
+
+**Slot segmentation:** SF=32, 122 MA, 110 chips (1024 chips)
+
+**Radio Frame #1**
+
+Diagram illustrating the RACH mapping process for 1 code SF32. It shows the flow from Information data and CRC/Tail bit attachments through Convolutional Coding, Puncturing, and Interleaving to Slot segmentation, resulting in a Radio Frame #1 with SF=32, 122 MA, and 110 chips (1024 total).
+
+Figure A.9
+
+## A.3 E-DCH Reference measurement channels
+
+### A.3.1 E-DCH Fixed Reference Channels
+
+#### A.3.1.1 3,84 Mcps TDD Option
+
+##### A.3.1.1.1 Fixed Reference Channel 1 (FRC1)
+
+Table A.6: E-DCH Fixed Reference Channel 1 (3,84 Mcps TDD Option)
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|-------|
+| Maximum information bit throughput | kbps | 34.7 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 347 |
+| Number Code Blocks | Blocks | 1 |
+| Number of coded bits per TTI | Bits | 1200 |
+| Coding Rate | | 0.312 |
+| Modulation | | QPSK |
+| Number of E-DCH Timeslots | Slots | 6 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 16 |
+| Number of E-UCCH per TTI | | 4 |
+
+
+
+Inf. Bit Payload: 347
+
+CRC addition: 347 | CRC 24
+
+Code Block Segmentation: 1 blocks of 371
+
+Turbo coding R=1/3: 1 blocks of $3 \times 371 + 12$ tail bits = 1125 bits
+
+Rate Matching: 1200
+
+Time slot segmentation 1 codes/TS, 6 TS/TTI:
+ 4 slots of 178 bits
+ 2 slots of 244 bits
+ =1200bits/10 ms
+
+Diagram showing the coding process for E-DCH FRC1. It includes steps: Inf. Bit Payload (347), CRC addition (347 + CRC 24), Code Block Segmentation (1 blocks of 371), Turbo coding R=1/3 (1 blocks of 3 \* 371 + 12 tail bits = 1125 bits), Rate Matching (1200), and Time slot segmentation (4 slots of 178 bits and 2 slots of 244 bits, totaling 1200 bits/10 ms).
+
+Figure A.10: Coding for E-DCH FRC1 (3,84 Mcps TDD Option)
+
+A.3.1.1.2 Fixed Reference Channel 2 (FRC2)
+
+Table A.7: E-DCH Fixed Reference Channel 2 (3,84 Mcps TDD Option)
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|--------|
+| Maximum information bit throughput | kbps | 1083.1 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 10831 |
+| Number Code Blocks | Blocks | 3 |
+| Number of coded bits per TTI | Bits | 22272 |
+| Coding Rate | | 0.488 |
+| Modulation | | 16QAM |
+| Number of E-DCH Timeslots | Slots | 6 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 2 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+The diagram illustrates the coding process for E-DCH FRC2 (3,84 Mcps TDD Option):
+
+- Inf. Bit Payload:** 10831
+- CRC addition:** 10831 + CRC 24
+- Code Block Segmentation:** 3 blocks of 3619
+- Turbo coding R=1/3:** 3 blocks of $3 \times 3619 + 12 \text{ tail bits}$ = 32607bits
+- Rate Matching:** 22272
+- Time slot segmentation 1 codes/TS, 6 TS/TTI:**
+ - 2 slots of 3328 bits
+ - 4 slots of 3904 bits
+
+=22272 bits/10 ms
+
+Diagram illustrating the coding process for E-DCH FRC2 (3,84 Mcps TDD Option).
+
+**Figure A.11: Coding for E-DCH FRC2 (3,84 Mcps TDD Option)**
+
+### A.3.1.1.3 Fixed Reference Channel 3 (FRC3)
+
+**Table A.8: E-DCH Fixed Reference Channel 3 (3,84 Mcps TDD Option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|--------|
+| Maximum information bit throughput | kbps | 2073.7 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 20737 |
+| Number Code Blocks | Blocks | 5 |
+| Number of coded bits per TTI | Bits | 28992 |
+| Coding Rate | | 0.716 |
+| Modulation | | 16QAM |
+| Number of E-DCH Timeslots | Slots | 4 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 1 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+| | | |
+|---------------------------------------------|-------------|-----------------------------------------------------|
+| Inf. Bit Payload | 20737 | |
+| CRC addition | 20737 | CRC 24 |
+| Code Block Segmentation | 5 blocks of | 4153 |
+| Turbo coding R=1/3 | 5 blocks of | $3 \times 4153 + 12 \text{ tail bits}$ = 62355 bits |
+| Rate Matching | 28992 | |
+| Time slot segmentation 1 codes/TS, 4 TS/TTI | 2 slots of | 6688 bits |
+| | 2 slots of | 7808 bits |
+
+= 28992 bits/10 ms
+
+**Figure A.12: Coding for E-DCH FRC3 (3,84 Mcps TDD Option)**
+
+### A.3.1.2 1.28Mcps TDD Option
+
+#### A.3.1.2.1 Fixed reference channel 1(FRC1)
+
+**Table A.9: E-DCH Fixed reference channel 1 (1.28Mcps TDD option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|--------|
+| Maximum information bit throughput | kbps | 56.4 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 282 |
+| Number Code Blocks | Blocks | 1 |
+| Number of coded bits per TTI | Bits | 306 |
+| Coding Rate | | 0.4965 |
+| Modulation | | QPSK |
+| Number of E-DCH Timeslots | Slots | 2 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 4 |
+| Number of E-UCCH per TTI | | 4 |
+
+
+
+Inf. Bit Payload: 282
+
+CRC addition: 282 | CRC 24
+
+Code Block Segmentation: 1 blocks of 306
+
+Turbo coding R=1/3: 1 blocks of $3 \times 306 + 12$ tail bits = 930 bits
+
+Rate Matching: 568
+
+Time slot segmentation 1 codes/TS, 2TS/TTI: 2 slots of 284 bits = 568 bits/5 ms
+
+Diagram showing the bit processing flow for E-DCH FRC1. It includes Inf. Bit Payload (282), CRC addition (282 + CRC 24), Code Block Segmentation (1 block of 306), Turbo coding R=1/3 (1 block of 3 \* 306 + 12 tail bits = 930 bits), Rate Matching (568), and Time slot segmentation (2 slots of 284 bits = 568 bits/5 ms).
+
+Figure A.12A: Coding for E-DCH FRC1 (1.28 Mcps TDD Option)
+
+A.3.1.2.2 Fixed reference channel 2(FRC2)
+
+Table A.10: E-DCH Fixed reference channel 2(1.28Mcps TDD option)
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|-------|
+| Maximum information bit throughput | kbps | 227.8 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 1139 |
+| Number Code Blocks | Blocks | 1 |
+| Number of coded bits per TTI | Bits | 1163 |
+| Coding Rate | | 0.85 |
+| Modulation | | QPSK |
+| Number of E-DCH Timeslots | Slots | 2 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 2 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+| | | |
+|--------------------------------------------|--------------------------------------------|----------------|
+| Inf. Bit Payload | 1139 | |
+| CRC addition | 1139 | CRC 24 |
+| Code Block Segmentation | 1 blocks of 1163 | |
+| Turbo coding R=1/3 | 1 blocks of $3 \times 1163 + 12$ tail bits | = 3501 bits |
+| Rate Matching | 1340 | |
+| Time slot segmentation 1 codes/TS, 2TS/TTI | 2 slots of 670 bits | =1340bits/5 ms |
+
+**Figure A.13: Coding for E-DCH FRC2 (1.28 Mcps TDD Option)**
+
+### A.3.1.2.3 Fixed reference channel 3(FRC3)
+
+**Table A.11: E-DCH Fixed reference channel 3 (1.28Mcps TDD option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|-------|
+| Maximum information bit throughput | kbps | 489 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 2445 |
+| Number Code Blocks | Blocks | 1 |
+| Number of coded bits per TTI | Bits | 2469 |
+| Coding Rate | | 0.598 |
+| Modulation | | 16QAM |
+| Number of E-DCH Timeslots | Slots | 3 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 2 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+| | | |
+|---------------------------------------------|-------------|----------------------------------------------------|
+| Inf. Bit Payload | 2445 | |
+| CRC addition | 2445 | CRC 24 |
+| Code Block Segmentation | 1 blocks of | 2469 |
+| Turbo coding R=1/3 | 1 blocks of | $3 \times 2469 + 12 \text{ tail bits}$ = 7419 bits |
+| Rate Matching | 4088 | |
+| Time slot segmentation 1 codes/TS, 3 TS/TTI | 2 slots of | 1340bits |
+| | 1 slots of | 1408bits |
+
+= 4088 bits/5 ms
+
+**Figure A.14: Coding for E-DCH FRC3 (1.28 Mcps TDD Option)**
+
+#### A.3.1.2.4 Fixed reference channel 4(FRC4)
+
+**Table A.12: E-DCH Fixed reference channel 4 (1.28Mcps TDD option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|--------|
+| Maximum information bit throughput | kbps | 1281.2 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 6406 |
+| Number Code Blocks | Blocks | 2 |
+| Number of coded bits per TTI | Bits | 6430 |
+| Coding Rate | | 0.5757 |
+| Modulation | | 16QAM |
+| Number of E-DCH Timeslots | Slots | 4 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 1 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+| | | |
+|-----------------------------------------------|-------------|---------------------------------------------------|
+| Inf. Bit Payload | 6406 | |
+| CRC addition | 6406 | CRC 24 |
+| Code Block Segmentation | 2 blocks of | 3215 |
+| Turbo coding R=1/3 | 2 blocks of | $3 \times 3215 + 12 \text{ tail bits}$ = 9657bits |
+| Rate Matching | 11128 | |
+| Time slot segmentation 1
codes/TS, 4TS/TTI | 2 slots of | 2748 bits |
+| | 2 slots of | 2816 bits |
+
+=11128 bits/5 ms
+
+**Figure A.15: Coding for E-DCH FRC4 (1.28 Mcps TDD Option)**
+
+### A.3.1.3 7,68 Mcps TDD Option
+
+#### A.3.1.3.1 Fixed Reference Channel 1 (FRC1)
+
+**Table A.13: E-DCH Fixed Reference Channel 1 (7.68 Mcps TDD Option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|-------|
+| Maximum information bit throughput | kbps | 35.9 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 359 |
+| Number Code Blocks | Blocks | 1 |
+| Number of coded bits per TTI | Bits | 1200 |
+| Coding Rate | | 0.323 |
+| Modulation | | QPSK |
+| Number of E-DCH Timeslots | Slots | 6 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 32 |
+| Number of E-UCCH per TTI | | 4 |
+
+
+
+The diagram illustrates the coding process for E-DCH FRC1 (7.68 Mcps TDD Option):
+
+- Inf. Bit Payload:** 359 bits.
+- CRC addition:** 359 bits + CRC 24 = 383 bits.
+- Code Block Segmentation:** 1 blocks of 383 bits.
+- Turbo coding R=1/3:** 1 blocks of $3 \times 383 + 12$ tail bits = 1161 bits.
+- Rate Matching:** 1200 bits.
+- Time slot segmentation:** 1200 bits are segmented into 4 slots of 178 bits and 2 slots of 244 bits. This results in $= 1200 \text{ bits} / 10 \text{ ms}$ .
+
+Diagram illustrating the coding process for E-DCH FRC1 (7.68 Mcps TDD Option).
+
+**Figure A.16: Coding for E-DCH FRC1 (7.68 Mcps TDD Option)**
+
+### A.3.1.3.2 Fixed Reference Channel 2 (FRC2)
+
+**Table A.14: E-DCH Fixed Reference Channel 2 (7.68 Mcps TDD Option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|--------|
+| Maximum information bit throughput | kbps | 1083.1 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 10831 |
+| Number Code Blocks | Blocks | 3 |
+| Number of coded bits per TTI | Bits | 22272 |
+| Coding Rate | | 0.488 |
+| Modulation | | 16QAM |
+| Number of E-DCH Timeslots | Slots | 6 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 4 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+The diagram illustrates the coding process for E-DCH FRC2 (7.68 Mcps TDD Option):
+
+- Inf. Bit Payload:** 10831
+- CRC addition:** 10831 + CRC 24
+- Code Block Segmentation:** 3 blocks of 3619
+- Turbo coding R=1/3:** 3 blocks of $3 \times 3619 + 12 \text{ tail bits}$ = 32607bits
+- Rate Matching:** 22272
+- Time slot segmentation 1 codes/TS, 6 TS/TTI:**
+ - 2 slots of 3328 bits
+ - 4 slots of 3904 bits
+
+=22272 bits/10 ms
+
+Diagram illustrating the coding process for E-DCH FRC2 (7.68 Mcps TDD Option).
+
+**Figure A.17: Coding for E-DCH FRC2 (7.68 Mcps TDD Option)**
+
+### A.3.1.3.3 Fixed Reference Channel 3 (FRC3)
+
+**Table A.15: E-DCH Fixed Reference Channel 3 (7.68 Mcps TDD Option)**
+
+| Parameter | Unit | Value |
+|---------------------------------------|--------|--------|
+| Maximum information bit throughput | kbps | 2085.1 |
+| Information Bit Payload ( $N_{INF}$ ) | Bits | 20851 |
+| Number Code Blocks | Blocks | 5 |
+| Number of coded bits per TTI | Bits | 28992 |
+| Coding Rate | | 0.720 |
+| Modulation | | 16QAM |
+| Number of E-DCH Timeslots | Slots | 6 |
+| Number of E-DCH codes per TS | Codes | 1 |
+| Spreading factor | SF | 2 |
+| Number of E-UCCH per TTI | | 2 |
+
+
+
+The diagram illustrates the bit processing flow for E-DCH FRC3 (7.68 Mcps TDD Option):
+
+- Inf. Bit Payload:** 20851 bits.
+- CRC addition:** 20851 bits + CRC 24 bits.
+- Code Block Segmentation:** 5 blocks of 4175 bits each.
+- Turbo coding R=1/3:** 5 blocks of $3 \times 4175 + 12$ tail bits = 62685 bits.
+- Rate Matching:** 28992 bits.
+- Time slot segmentation 1 codes/TS, 4 TS/TTI:**
+ - 2 slots of 6688 bits
+ - 2 slots of 7808 bits
+ Total = 28992 bits/10 ms.
+
+Diagram showing the coding process for E-DCH FRC3 (7.68 Mcps TDD Option).
+
+Figure A.18: Coding for E-DCH FRC3 (7.68 Mcps TDD Option)
+
+## A.4 HS-SICH Reference measurement channels
+
+### A.4.1 3,84 Mcps TDD Option
+
+(void)
+
+### A.4.2 1,28 Mcps TDD Option
+
+Table A.16: HS-SICH type1 Reference Channel 1 (1,28 Mcps TDD Option)
+
+| Parameter | Unit | Value |
+|---------------------|------|-------|
+| Information bits | bits | 8 |
+| Encoded bits | bits | 84 |
+| Number of codes | - | 1 |
+| Number of timeslots | - | 1 |
+| TTI | ms | 5 |
+| Spreading Factor | SF | 16 |
+
+
+
+Inf. Bit Payload: 8
+
+Coding and multiplex: 84
+
+Interleaving: 84bits/5ms
+
+Slot segmentation 1 codes/TS, 1TS/TTI: 44, 144chips, SS, TPC, 40
+
+Diagram showing the coding process for HS-SICH type1 channel. It includes boxes for Inf. Bit Payload (8), Coding and multiplex (84), Interleaving (84bits/5ms), and Slot segmentation 1 codes/TS, 1TS/TTI (44, 144chips, SS, TPC, 40).
+
+Figure A.19: Coding for HS-SICH type1 channel (1,28 Mcps TDD Option)
+
+Table A.17: HS-SICH type2 Reference Channel 1 (1.28 Mcps TDD Option)
+
+| Parameter | Unit | Value |
+|---------------------|------|-------|
+| Information bits | bits | 16 |
+| Encoded bits | bits | 168 |
+| Number of codes | - | 1 |
+| Number of timeslots | - | 1 |
+| TTI | ms | 5 |
+| Spreading Factor | SF | 8 |
+
+
+
+Inf. Bit Payload: 16
+
+Coding and multiplex: 168
+
+Interleaving: 168bits/5ms
+
+Slot segmentation 1 codes/TS, 1TS/TTI: 88, 144chips, SS, TPC, 80
+
+Diagram showing the coding process for HS-SICH type2 channel. It includes boxes for Inf. Bit Payload (16), Coding and multiplex (168), Interleaving (168bits/5ms), and Slot segmentation 1 codes/TS, 1TS/TTI (88, 144chips, SS, TPC, 80).
+
+Figure A.20: Coding for HS-SICH type2 channel (1.28 Mcps TDD Option)
+
+## Annex B (normative): Propagation conditions
+
+### B.1 Static propagation condition
+
+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.
+
+### B.2 Multi-path fading propagation conditions
+
+#### B.2.1 3,84 Mcps TDD option
+
+Table B.1 and B.1A shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum, defined as:
+
+$$(CLASS) \quad S(f) \propto 1/(1 - (f/f_D)^2)^{0.5} \quad \text{for } f \in -f_D, f_D$$
+
+**Table B.1: Propagation Conditions for Multi path Fading Environments for 3,84 Mcps TDD option for operations referenced in 4.2 a), 4.2 b) and 4.2 c)**
+
+| Case 1, speed 3km/h | | Case 2, speed 3 km/h | | Case 3, speed 120 km/h | |
+|---------------------|--------------------------|----------------------|--------------------------|------------------------|--------------------------|
+| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] |
+| 0 | 0 | 0 | 0 | 0 | 0 |
+| 976 | -10 | 976 | 0 | 260 | -3 |
+| | | 12000 | 0 | 521 | -6 |
+| | | | | 781 | -9 |
+
+**Table B.1A: Propagation Conditions for Multi path Fading Environments for operations referenced in 4.2 d)**
+
+| Case 1, speed 2.3km/h | | Case 2, speed 2.3 km/h | | Case 3, speed 92 km/h | |
+|-----------------------|--------------------------|------------------------|--------------------------|-----------------------|--------------------------|
+| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] |
+| 0 | 0 | 0 | 0 | 0 | 0 |
+| 976 | -10 | 976 | 0 | 260 | -3 |
+| | | 12000 | 0 | 521 | -6 |
+| | | | | 781 | -9 |
+
+#### B.2.2 1,28 Mcps TDD option
+
+Table B.2 shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum, defined as:
+
+$$(CLASS) \quad S(f) \propto 1/(1 - (f/f_D)^2)^{0.5} \quad \text{for } f \in -f_D, f_D$$
+
+**Table B2: Propagation Conditions for Multi path Fading Environments**
+
+| Case 1 | | Case 2 | | Case 3 | |
+|----------------------------------------------|--------------------------|-----------------------------------------------|--------------------------|-------------------------------------------------|--------------------------|
+| Speed for operating in band a, b, c, f 3km/h | | Speed for operating in band a, b, c, f: 3km/h | | Speed for operating in band a, b, c, f: 120km/h | |
+| Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 92km/h | |
+| Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 102km/h | |
+| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] |
+| 0 | 0 | 0 | 0 | 0 | 0 |
+| 2928 | -10 | 2928 | 0 | 781 | -3 |
+| | | 12000 | 0 | 1563 | -6 |
+| | | | | 2344 | -9 |
+
+**Table B.2A: Propagation Conditions for Multipath Fading Environments for E-DCH Performance Requirements for 1,28 Mcps TDD**
+
+| ITU Pedestrian A
Speed 3km/h
(PA3) | | ITU Pedestrian B
Speed 3km/h
(PB3) | | ITU vehicular A
Speed 30km/h
(VA30) | |
+|-----------------------------------------------|---------------------------|----------------------------------------------|---------------------------|------------------------------------------------|---------------------------|
+| Speed for operating in band a, b, c, f: 3km/h | | Speed for operating in band a, b, c, f 3km/h | | Speed for operating in band a, b, c, f: 30km/h | |
+| Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 23km/h | |
+| Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 26km/h | |
+| Relative Delay [ns] | Relative Mean Power [ dB] | Relative Delay [ns] | Relative Mean Power [ dB] | Relative Delay [ns] | Relative Mean Power [ dB] |
+| 0 | 0 | 0 | 0 | 0 | 0 |
+| 110 | -9.7 | 200 | -0.9 | 310 | -1.0 |
+| 190 | -19.2 | 800 | -4.9 | 710 | -9.0 |
+| 410 | -22.8 | 1200 | -8.0 | 1090 | -10.0 |
+| | | 2300 | -7.8 | 1730 | -15.0 |
+| | | 3700 | -23.9 | 2510 | -20.0 |
+
+Note: For MC-HSUPA requirements, the fading of the signals for each carrier shall be independent.
+
+## B.2.3 7,68 Mcps TDD option
+
+Table B.4 and B.5 shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum, defined as:
+
+$$(CLASS) \quad S(f) \propto 1/(1 - (f/f_D)^2)^{0.5} \quad \text{for } f \in -f_D, f_D$$
+
+**Table B.3: Propagation Conditions for Multi path Fading Environments for 3,84 Mcps TDD option for operations referenced in 4.2 a), 4.2 b) and 4.2 c)**
+
+| Case 1, speed 3km/h | | Case 2, speed 3 km/h | | Case 3, speed 120 km/h | |
+|---------------------|--------------------------|----------------------|--------------------------|------------------------|--------------------------|
+| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] |
+| 0 | 0 | 0 | 0 | 0 | 0 |
+| 976 | -10 | 976 | 0 | 260 | -3 |
+| | | 12000 | 0 | 521 | -6 |
+| | | | | 781 | -9 |
+
+**Table B.5: Propagation Conditions for Multi path Fading Environments for operations referenced in 4.2 d)**
+
+| Case 1, speed 2.3km/h | | Case 2, speed 2.3 km/h | | Case 3, speed 92 km/h | |
+|-----------------------|--------------------------|------------------------|--------------------------|-----------------------|--------------------------|
+| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] |
+| 0 | 0 | 0 | 0 | 0 | 0 |
+| 976 | -10 | 976 | 0 | 260 | -3 |
+| | | 12000 | 0 | 521 | -6 |
+| | | | | 781 | -9 |
+
+## B.3 High speed train conditions
+
+High speed train conditions are as follows:
+
+Scenario 1: Open space
+
+Scenario 3: Tunnel for multi-antennas
+
+The high speed train conditions for the test of the baseband performance are two non-fading propagation channels in both scenarios.
+
+Doppler shift for both scenarios is given by:
+
+$$(B.1)$$
+
+where $f_d$ is the Doppler shift and $f_{max}$ is the maximum Doppler frequency. The cosine of angle is given by:
+
+$$(B.2)$$
+
+$$(B.3)$$
+
+$$(B.4)$$
+
+where $d_0$ is the initial distance of the train from BS, and $d$ is BS-Railway track distance, both in meters; $v$ is the velocity of the train in m/s, $t$ is time in seconds.
+
+Doppler shift and cosine angle is given by equation B.1 and B.2-B.4 respectively, where the required input parameters listed in table B.6 and the resulting Doppler shift shown in Figure B.1 and B.2 are applied for all frequency bands.
+
+Table B.6: Parameters for high speed train conditions
+
+| Parameter | Value | |
+|-----------|------------|------------|
+| | Scenario 1 | Scenario 3 |
+| | 1000 m | 300 m |
+| | 50 m | 2 m |
+| | 350 km/h | 300 km/h |
+| | 1310 Hz | 1125 Hz |
+
+NOTE1: Parameters for HST conditions in table B. including $d_0$ and Doppler shift trajectories presented on figures B.1 and B.2 were derived for Band a).
+
+
+
+Figure B.1: Doppler shift trajectory for scenario 1. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 50). The trajectory starts at approximately 1250 Hz, drops sharply to about -1350 Hz between 5 and 10 seconds, rises back to 1250 Hz between 15 and 20 seconds, drops again to -1350 Hz between 25 and 30 seconds, rises to 1250 Hz between 35 and 40 seconds, and finally drops to -1350 Hz after 45 seconds.
+
+Figure B.1: Doppler shift trajectory for scenario 1
+
+
+
+Figure B.2: Doppler shift trajectory for scenario 3. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 20). The trajectory starts at approximately 1150 Hz, drops sharply to about -1150 Hz between 2 and 5 seconds, rises back to 1150 Hz between 5 and 10 seconds, drops again to -1150 Hz between 10 and 15 seconds, rises to 1150 Hz between 15 and 20 seconds, and ends at approximately 1150 Hz at the 20-second mark.
+
+Figure B.2: Doppler shift trajectory for scenario 3
+
+---
+
+## Annex C (normative): Global in-channel Tx test
+
+### C.1 General
+
+The global in-channel Tx test enables the measurement of all relevant parameters that describe the in-channel quality of the output signal of the Tx under test in a single measurement process.
+
+The parameters describing the in-channel quality of a transmitter, however, are not necessarily independent. The algorithm chosen for description inside this annex places particular emphasis on the exclusion of all interdependencies among the parameters. Any other algorithm (e.g. having better computational efficiency) may be applied, as long as the results are the same within the accuracy limits.
+
+All notes referred to in the various subclauses of C.2 are put together in clause C.3
+
+---
+
+### C.2 Definition of the process
+
+#### C.2.1 Basic principle
+
+The process is based on the comparison of the actual **output signal of the Tx under test**, received by an ideal receiver, with a **reference signal**, that is generated by the measuring equipment and represents an ideal error free received signal. The reference signal shall be composed of the same number of codes at the correct spreading factors as contained in the test signal. Note, for simplification, the notation below assumes only codes of one spreading factor although the algorithm is valid for signals containing multiple spreading factors. All signals are represented as equivalent (generally complex) base band signals.
+
+#### C.2.2 Output signal of the Tx under test
+
+The output signal of the Tx under test is acquired by the measuring equipment, filtered by a matched filter (RRC characteristic with roll-off $\alpha = 0,22$ , correct in shape and in position on the frequency axis) and stored for further processing.
+
+The following form represents the physical signal in the entire measurement interval:
+
+one vector **Z**, containing $N = n_s \times sf + m_a$ complex samples;
+
+with
+
+$n_s$ : number of symbols in the measurement interval;
+
+$sf$ : number of chips per symbol. ( $sf$ : spreading factor) (see Note: Symbol length)
+
+$m_a$ : number of midamble chips, or for IMB the number of chips in the TDM pilot region
+
+#### C.2.3 Reference signal
+
+The reference signal is constructed by the measuring equipment according to the relevant Tx specifications.
+
+It is filtered by the same matched filter, mentioned in C.2.2, and stored at the intersymbol interference free instants. The following form represents the reference signal in the entire measurement interval:
+
+one vector **R**, containing $N = n_s \times sf + m_a$ complex samples;
+
+where $n_s$ , $sf$ and $m_a$ have the same meaning as defined above in C.2.2.
+
+#### C.2.4 Classification of measurement results
+
+The measurement results achieved by the global in-channel Tx test can be classified into two types:
+
+- **Results of type "deviation"**, where the error-free parameter has a non-zero magnitude. (These are the parameters that represent the signal). These parameters are:
+
+RF Frequency
+
+Power
+
+(in case of single code)
+
+Code Domain Power
+
+(in case of multi-code)
+
+Timing
+
+(only for UE) (see Note: Deviation)
+
+(Additional parameters: see Note: Deviation)
+
+- **Results of type "residual"**, where the error-free parameter has value zero. (These are the parameters that represent the error values of the measured signal; ideally, their magnitude is zero). These parameters are:
+
+Error Vector Magnitude (EVM)
+
+Peak Code Domain Error (PCDE)
+
+(Additional parameters: see Note: Residual)
+
+## C.2.5 Process definition to achieve results of type "deviation"
+
+The reference signal (**R**; see subclause C.2.3) and the signal under Test (**Z**; see subclause C.2.2) are varied with respect to the parameters mentioned in subclause C.2.4 under "results of type deviation" in order to achieve best fit. Best fit is achieved when the RMS difference value between the varied signal under test and the varied reference signal is an absolute minimum.
+
+Overview:
+
+**Z**: Signal under test.
+
+**R**: Reference signal,
+
+with frequency $f$ , the timing $t$ , the phase $\varphi$ , gain of code1 ( $g_1$ ), gain of code2 ( $g_2$ ) etc, and the gain of the synch channel $g_{\text{synch}}$
+
+The parameters marked with a tilde in **Z** and **R** are varied in order to achieve a best fit.
+
+**R'** and **Z'** are each of length $n_s \cdot sf$ and depending on the length of the measurement interval result of possibly multiple successive applications of the minimum process.
+
+Detailed formula: see Note: Formula for the minimum process
+
+The varied reference signal, after the best-fit process, will be called **R'**.
+
+The varied signal under test, after the best fit process, will be called **Z'**.
+
+**R'** and **Z'** are each of length $n_s \cdot sf$ and depending on the length of the measurement interval result of possibly multiple successive applications of the minimum process.
+
+Those parameter values, which - after the best-fit process -lead to **R'** and **Z'**, represent directly the wanted results of type "deviation". These parameter values are expressed as deviations from the reference value, using the same units as the corresponding reference value.
+
+In the case of multi-code transmission, the best-fit process of the type "deviation" parameters frequency, timing (and any additional parameter as e.g. RF phase) is not done with respect to the individual codes, but commonly for the complete code set used; therefore, the process returns one measurement value only for each parameter.
+
+(These parameters are not varied on the individual codes signals such that the process would return $k_r$ frequency errors... ( $k_r$ : number of codes in the reference signal)).
+
+The only type-"deviation"-parameters varied individually are the code domain gain factors ( $g_1, g_2, \dots$ )
+
+### C.2.5.1 Decision Point Power
+
+The mean-square value of the signal-under-test, sampled at the best estimate of the of Intersymbol-Interference-free points using the process defined in subclause 2.5, is referred to the *Decision Point Power* (DPP):
+
+### C.2.5.2 Code-Domain Power
+
+The samples, $Z'$ , are separated into symbol intervals to create $n_s$ time-sequential vectors $\mathbf{z}$ with $s_f$ complex samples comprising one symbol interval. The *Code Domain Power* is calculated according to the following steps:
+
+- 1) Take the vectors $\mathbf{z}$ defined above.
+- 2) To achieve meaningful results it is necessary to descramble $\mathbf{z}$ , leading to $\mathbf{z}'$
+- 3) Take the orthogonal vectors of the channelization code set $\mathbf{C}$ (all codes belonging to one spreading factor) as defined in TS 25.213 and TS 25.223 (range +1, -1), and normalize by the norm of the vectors to produce $\mathbf{C}_{\text{norm}} = \mathbf{C} / \sqrt{s_f}$ . (see Note: Symbol length)
+- 4) Calculate the inner product of $\mathbf{z}'$ with $\mathbf{C}_{\text{norm}}$ . Do this for all symbols of the measurement interval and for all codes in the code space.
+This gives an array of format $k \times n_s$ , each value representing a specific symbol and a specific code, which can be exploited in a variety of ways.
+
+$k$ : total number of codes in the code space
+
+$n_s$ : number of symbols in the measurement interval
+
+- 5) Calculate $k$ mean-square values, each mean-square value unifying $n_s$ symbols within one code.
+(These values can be called "*Absolute CodeDomainPower* (CDP)" [ $\text{Volt}^2$ ].) The sum of the $k$ values of CDP is equal to DPP.
+- 6) Normalize by the decision point power to obtain
+
+$$\text{Relative CodeDomain Power} = \frac{\text{Absolute CodeDomainPower}}{\text{DecisionPointPower}}$$
+
+## C.2.6 Process definition to achieve results of type "residual"
+
+The difference between the varied reference signal ( $\mathbf{R}'$ ; see subclause C.2.5.) and the varied Tx signal under test ( $\mathbf{Z}$ ; see subclause C.2.2) is the error vector $\mathbf{E}$ versus time:
+
+$$\mathbf{E} = \mathbf{Z}' - \mathbf{R}'$$
+
+Depending on the parameter to be evaluated, it is appropriate to represent $\mathbf{E}$ in one of the following two different forms:
+
+**Form EVM** (representing the physical error signal in the entire measurement interval)
+
+One vector $\mathbf{E}$ , containing $N = n_s \times s_f + m_a$ complex samples;
+
+where $n_s$ , $s_f$ and $m_a$ have the same meaning as defined above in C.2.2.
+
+**Form PCDE** (derived from Form EVM by separating the samples into symbol intervals)
+
+$n_s$ time-sequential vectors $\mathbf{e}$ with $s_f$ complex samples comprising one symbol interval.
+
+$\mathbf{E}$ gives results of type "residual" applying the two algorithms defined in subclauses C.2.6.1 and C.2.6.2.
+
+### C.2.6.1 Error Vector Magnitude (EVM)
+
+The Error Vector Magnitude EVM is calculated according to the following steps:
+
+- 1) Take the error vector $\mathbf{E}$ defined in subclause C.2.6 (Form EVM) and calculate the RMS value of $\mathbf{E}$ ; the result will be called $\text{RMS}(\mathbf{E})$ .
+
+- 2) Take the varied reference vector **R** defined in subclause C.2.3 and calculate the RMS value of **R**; the result will be called $\text{RMS}(\mathbf{R})$ .
+- 3) Calculate EVM according to:
+
+$$\text{EVM} = \frac{\text{RMS}(\mathbf{E})}{\text{RMS}(\mathbf{R})} \times 100\% \quad (\text{here, EVM is relative and expressed in \%})$$
+
+(see Note: TDD)
+
+(see Note: Formula for EVM)
+
+### C.2.6.2 Peak Code Domain Error (PCDE)
+
+The Peak Code Domain Error is calculated according to the following steps:
+
+- 1) Take the error vectors **e** defined in subclause C.2.6 (Form PCDE)
+- 2) Take the orthogonal vectors of the spreading code set **C** (all codes belonging to one spreading factor) as defined in TS 25.213 and TS 25.223 (range +1, -1). (see Note: Symbol length) and normalize by the norm of the vectors to produce $\mathbf{C}_{\text{norm}} = \mathbf{C}/\sqrt{\text{s}f}$ . (see Note: Symbol length)
+- 3) To achieve meaningful results, it is necessary to descramble **e**, leading to **e'**
+- 4) Calculate the inner product of **e'** with $\mathbf{C}_{\text{norm}}$ . Do this for all symbols of the measurement interval and for all codes in the code space.
+This gives an array of format $k \times n_s$ , each value representing an error-vector representing a specific symbol and a specific code, which can be exploited in a variety of ways.
+
+$k$ : total number of codes in the code space
+
+$n_s$ : number of symbols in the measurement interval
+
+- 5) Calculate $k$ RMS values, each RMS value unifying $n$ symbols within one code.
+(These values can be called "Absolute CodeEVMs" [Volt].)
+- 6) Find the peak value among the $k$ "absolute Code-EVMs".
+(This value can be called "Absolute PeakCodeEVM" [Volt].)
+- 7) Calculate PCDE according to:
+
+$$\text{PCDE} = 10 \lg \frac{(\text{absolute PeakCodeEVM})^2}{(\text{RMS}(\mathbf{R}))^2} \text{ dB} \quad (\text{a relative value in dB}).$$
+
+see Note: TDD
+
+see Note: Synch channel
+
+### C.2.6.3 Relative Code Domain Error (RCDE)
+
+The Relative Code Domain Error is calculated for a wanted code according to the following steps:
+
+- 1) Calculate the value "*Absolute CodeEVM*" [Volt] for the wanted code according to C.2.6.2, as an RMS value unifying $n_s = 2400$ symbols corresponding to the measurement interval of one timeslot.
+- 2) Calculate the value "*Absolute CodeDomainPower (CDP)*" [Volt2] for the wanted code according to C.2.5.2, with $n_s = 2400$ symbols corresponding to the measurement interval of one timeslot.
+- 3) Calculate RCDE according to:
+
+4) The average RCDE across a set of wanted codes is defined as the mean of the linear RCDE values and subsequently expressed in dB.
+
+---
+
+## C.3 Notes
+
+### C.3.1 Symbol length
+
+A general code-multiplexed signal is multi-code and multi-rate. In order to avoid unnecessary complexity, the measurement applications use a unique symbol-length, corresponding to a specific spreading factor, regardless of the really intended spreading factor. Nevertheless, the complexity with a multi-code / multi-rate signal can be mastered by introducing appropriate definitions.
+
+### C.3.2 Deviation
+
+It is conceivable to regard more parameters as type „deviation“, e.g. chip clock and RF phase. However, because chip clock and RF frequency are linked together by a statement in the core specifications [1], it is sufficient to process RF frequency only.
+
+The parameter RF phase must be varied within the best-fit process (C.2.5). Although necessary, this parameter-variation does not describe any error, as the modulation schemes used in the system do not depend on an absolute RF-phase.
+
+The parameter Timing must be varied within the best fit process (C.2.5.) This parameter variation does not describe any error, when applied to the Node B test. However when applied to the UE test, it describes the error of the UE's Timing Advance.
+
+### C.3.3 Residual
+
+It is conceivable to regard more parameters as type „residual“, e.g. IQ origin offset. As it is not the intention of the test to separate for different error sources, but to quantify the quality of the signal, all such parameters are not extracted by the best-fit process, instead remain part of EVM and PCDE.
+
+### C.3.4 TDD
+
+EVM covers the midamble (or for IMB the TDM pilot region) part as well as the data part; however PCDE disregards the midamble (or IMB TDM pilot) part.
+
+### C.3.5 Synch channel
+
+A node B signal contains a physical synch channel, which is non-orthogonal, related to the other DPCHs. In this context note: The code channel bearing the result of PCDE is exactly one of the DPCHs (never the synch channel). The origin of PCDE (erroneous code power) can be any DPCH and/or the synch channel. This means that the error due to the synch channel is projected onto the other (orthogonal) codes that make up the code domain.
+
+### C.3.6 Formula for the minimum process
+
+where
+
+L is the function to be minimised
+
+The parameters to be varied in order to minimize are:
+
+the RF frequency offset
+
+the timing offset
+
+the phase offset
+
+code power offsets (one offset for each code)
+
+the power offset of the midamble (or for IMB the TDM pilot region)
+
+the code power offset of the primary SCH
+
+the code power offsets of secondary SCHs, (*i*: 1,2,3)
+
+( and are only applied, if the timeslot under test contains the synchronisation channel.)
+
+$Z(v)$ Samples of the signal under Test
+
+$R(v)$ Samples of the reference signal
+
+counting index starting at the beginning of the measurement interval and ending at its end.
+
+$N$ No of chips during the measurement interval.
+
+$Z(v)$ : Samples of the signal under Test. It is modelled as a sequence of complex baseband samples $Z(\gamma)$ with a time-shift $\Delta t$ , a frequency offset $\Delta f$ , a phase offset $\Delta \varphi$ , the latter three with respect to the reference signal.
+
+$R(v)$ : Samples of the reference signal:
+
+where
+
+$g$ nominal gain of the code channel or midamble (or for IMB the TDM pilot region)
+
+The gain offset to be varied in the minimum process
+
+$Chip(v)$ is the chip sequence of the code channel or midamble (or for IMB the TDM pilot region)
+
+Indices at $g$ , $\Delta g$ and $Chip$ : The index indicates the code channel:
+
+$c = 1, 2, \dots$ No of code channels
+
+prim = primary SCH
+
+seci = three secondary SCHs, i:1,2,3
+
+Range for $Chip_c$ : +1,-1
+
+## C.3.7 Formula for EVM
+
+$Z'(\gamma)$ , $R'(\gamma)$ are the varied measured and reference signals.
+
+## Annex D (informative): Derivation of Test Requirements
+
+The Test Requirements in this specification have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances defined in subclause 5.11. When the Test Tolerance is zero, the Test Requirement will be the same as the Minimum Requirement. When the Test Tolerance is non-zero, the Test Requirements will differ from the Minimum Requirements, and the formula used for this relaxation is given in tables D.1 to D.3
+
+Note that a formula for applying Test Tolerances is provided for all tests, even those with a test tolerance of zero. This is necessary in the case that the Test System uncertainty is greater than that allowed in subclause 5.10. In this event, the excess error shall be subtracted from the defined test tolerance in order to generate the correct tightened Test Requirements as defined in subclause 5.12.
+
+For example, a Test System having 0,9 dB accuracy for test 6.2 Maximum output power (which is 0,2 dB above the limit specified in subclause 5.10.2) would subtract 0,2 dB from the Test Tolerance of 0,7 dB defined in subclause 5.11.1. This new test tolerance of 0,5 dB would then be applied to the Minimum Requirement using the formula defined in Table D.1 to give a new range of $\pm 2,5$ dB of the manufacturer's rated output power.
+
+For the case where an excess error of 0.2 dB exists, when applied to a test with a test tolerance of zero, the test tolerance used in the formula would be -0.2 dB.
+
+**Table D.1: Derivation of Test Requirements (Transmitter tests)**
+
+| Test | Minimum Requirement in TS 25.105
(numbering of tables in the column below refers to TS 25.142) | Test Tolerance (TT) | Test Requirement in TS 25.142 |
+|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6.2 Maximum output power | In normal conditions ...
within +2 dB and -2 dB of the manufacturer's rated output power
In extreme conditions...
within +2,5 dB and -2,5 dB of the manufacturer's rated output power | 0,7 dB | Formula: Upper limit + TT
Lower limit - TT
In normal conditions ...
within +2,7 dB and -2,7 dB of the manufacturer's rated output power
In extreme conditions...
within +3,2 dB and -3,2 dB of the manufacturer's rated output power |
+| 6.3 Frequency stability | Frequency stability
Wide Area BS: $\pm 0,05$ ppm
Local Area BS: $\pm 0,1$ ppm | 12 Hz | Formula:
$\pm$ (frequency stability +TT)
Wide Area BS:
$\pm (0,05 \text{ ppm} + 12 \text{ Hz})$
Local Area BS:
$\pm (0,1 \text{ ppm} + 12 \text{ Hz})$ |
+| 6.4.2 Power control steps | single step: step size tolerance specified in table 6.3
ten steps: minimum and maximum average rate of change in mean power specified in table 6.3 | single step:
0,1 dB
ten steps:
0,3 dB | Formula:
single step:
$\pm$ (step size tolerance + TT)
ten steps:
maximum average rate + TT
minimum average rate - TT
0,1 dB and 0,3 dB, respectively, applied as above to table 6.3 |
+| 6.4.3 Power control dynamic range | range $\geq 30$ dB | 0,3 dB | Formula: Range - TT
range $\geq 29,7$ dB |
+| 6.4.4 Minimum output power | PRAT - 30 dB | 0,7 dB | Formula :
PRAT - 30 dB +TT
PRAT - 29,3 dB |
+| 6.4.5 Primary CCPCH power | PCCPCH power tolerance defined in table 6.8 | 0,8 dB | Formula:
$\pm$ (power tolerance + TT)
0,8 dB applied as above to table 6.8 |
+| 6.4.6 Differential accuracy of Primary CCPCH power | Differential accuracy of PCCPCH power: $\leq \pm 0,5$ dB | 0,1 dB | Formula:
$\pm$ (PCCPCH tolerance + TT)
$\pm 0,6$ dB |
+| 6.5.1 Transmit OFF power | Tx OFF power limit $< -79$ dBm | 2,0 dB | Formula:
$< \text{Tx OFF power limit} + \text{TT}$
$< - 77$ dBm |
+
+| | | | | |
+|------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6.5.2 mask | Transmit ON/OFF time | Tx power limit:
3,84 Mcps TDD option:
< -33 dBm or -79 dBm, resp.
1,28 Mcps TDD option:
< -42 dBm or -82 dBm, resp. | < -33 dBm:
0,7 dB
< -79 dBm:
2,0 dB
< -42 dBm:
0,7 dB
< -82 dBm:
2,0 dB | Formula:
< Tx power limit + TT
for 3,84 Mcps TDD option:
< -32,3 dBm
or
< - 77 dBm
for 1,28 Mcps TDD option:
< -41,3 dBm
or
< -80 dBm |
+| 6.6.1 | Occupied bandwidth | occupied bandwidth limit
3,84 Mcps TDD option: = 5 MHz
1,28 Mcps TDD option: 1,6 MHz | 0 kHz | Formula:
Occupied bandwidth limit + TT
3,84 Mcps TDD option: = 5 MHz
1,28 Mcps TDD option: 1,6 MHz |
+| 6.6.2.1 | Spectrum emission mask | Maximum level defined in tables 6.13 to 6.16 | 1,5 dB | Formula: Maximum level + TT
Add 1,5 dB to Maximum level entries in tables 6.13 to 6.16 |
+
+| | | | |
+|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6.6.2.2 Adjacent Channel Leakage power Ratio (ACLR) | 3,84 Mcps TDD option:
minimum requirement:
ACLR limit = 45 dB at 5 MHz
ACLR limit = 55 dB at 10 MHz
requirement for operation in the same geographic area with unsynchronised TDD BS or FDD BS on adjacent channels:
Maximum Level defined in tables 6.23 and 6.23AA
requirement in case of co-siting with unsynchronised TDD BS or FDD BS operating on adjacent channels:
Maximum Level defined in tables 6.24 and 6.24A
1,28 Mcps TDD option:
minimum requirement:
ACLR limit = 40 dB at 1,6 MHz
ACLR limit = 45 dB at 3,2 MHz
requirement for operation in the same geographic area with unsynchronised TDD or FDD on adjacent channels:
Maximum Level defined in tables 6.23A, 6.23B and 6.23C
requirement in case of co-siting with unsynchronised TDD or FDD on an adjacent channel:
Maximum Level defined in tables 6.24B, 6.24C and 6.24D
| 3,84 Mcps TDD option:
min. req. : 0,8 dB
operation in the same geographic area:
4 dB (TBD in table 6.23A, 5 MHz offset, resp.) for Wide Area BS ; 0,8 dB for Local Area BS
co-siting:
TBD for Wide Area BS; 1 dB for Local Area BS
1,28 Mcps TDD option:
min. req. : 0,8 dB
operation in the same geographic area:
1 dB or 4 dB for the Wide Area BS; 0,8 dB for the Local Area BS
co-siting:
TBD for the Wide Area BS; 1 dB for the Local Area BS
| Formula: ACLR limit - TT
3,84 Mcps TDD option:
min. requirement:
ACLR limit = 44,2 dB at 5 MHz
ACLR limit = 54,2 dB at 10 MHz
operation in the same geographic area:
Wide Area BS:
Add 4 dB (TBD in table 6.23A, 5 MHz offset, resp.) to the Maximum Level entries in tables 6.23 and 6.23AA.
Local Area BS:
Add 0,8 dB to the Maximum Level entries in tables 6.23 and 6.23AA.
co-siting:
Wide Area BS:
Add TBD to the Maximum Level entries in tables 6.24 and 6.24A.
Local Area BS:
Add 1 dB to the Maximum Level entries in tables 6.24 and 6.24A.
1,28 Mcps TDD option:
min. requirement:
ACLR limit = 39,2 dB at 1,6 MHz
ACLR limit = 44,2 dB at 3,2 MHz
operation in the same geographic area:
Wide Area BS:
Add 1 dB to the Maximum Level entries in tables 6.23A and 6.23B, and 4 dB to the Maximum Level entry in table 6.23C.
Local Area BS:
Add 0,8 dB to the Maximum Level entries in tables 6.23A, 6.23B and 6.23C.
co-siting:
Wide Area BS:
Add TBD to the Maximum Level entries in tables 6.24B, 6.24C and 6.24D.
Local Area BS:
Add 1 dB to the Maximum Level entries in tables 6.24B, 6.24C and 6.24D.
|
+| 6.6.3 Spurious emissions | maximum level defined in tables 6.29 to 6.37 | 0 dB | Formula: Maximum limit + TT
add 0 dB to maximum levels in tables 6.29 to 6.37
|
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6.7 Transmit intermodulation (interferer requirements)
This tolerance applies to the stimulus and not the measurements defined in 6.6.2.1, 6.6.2.2 and 6.6.3. | Wanted signal level - interferer level = 30 dB | 0 dB | Formula: Ratio + TT
Wanted signal level - interferer level = 30 + 0 dB |
+| 6.8.1 Modulation accuracy | EVM limit = 12,5 % | 0 % | Formula: EVM limit + TT
EVM limit = 12,5 % |
+| 6.8.2 Peak code domain error | PCDE limit = - 28 dB | 1 dB | Formula: PCDE limit + TT
PCDE limit = - 27 dB |
+| 6.8.3 Relative Code Domain Error | RCDE limit = -21.9 dB | 1.0 dB | Formula: RCDE limit + TT
RCDE limit = -20.9 dB |
+| 6.8.4 Time alignment error in MIMO transmission | 1,28 Mcps TDD option:
Max time alignment error = 65 ns
Min time alignment error = - 65 ns | 1,28 Mcps TDD option:
[78] ns | Formula:
Max time alignment error + TT
Min time alignment error – TT
1,28 Mcps TDD option:
Max time alignment error = [143]ns
Min time alignment error = [-143]ns |
+
+**Table D.2: Derivation of Test Requirements (Receiver tests)**
+
+| Test | Minimum Requirement in TS 25.105
(numbering of tables in the column below refers to TS 25.142) | Test Tolerance (TT) | Test Requirement in TS 25.142 |
+|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 7.2 Reference sensitivity | Reference sensitivity level
3,84 Mcps TDD option: =
Wide Area BS: -109 dBm
Local Area BS: -95 dBm
1,28 Mcps TDD option:
Wide Area BS: -110 dBm
Local Area BS: -96 dBm
BER limit = 0,001 | 0,7 dB | Formula:
Reference sensitivity level + TT
Reference sensitivity level
3,84 Mcps TDD option:
Wide Area BS: -108,3 dBm
Local Area BS: -94,3 dBm
1,28 Mcps TDD option:
Wide Area BS: -110 dBm
Local Area BS: -95,3 dBm
BER limit is not changed |
+| 7.3 Dynamic range | Wanted signal level =
+ 30 dB
Interfering AWGN level
3,84 Mcps TDD option:
Wide Area BS: -73 dBm/3,84 MHz
Local Area BS: -59 dBm/3,84 MHz
1,28 Mcps TDD option:
Wide Area BS: -76 dBm/1,28 MHz
Local Area BS: -62 dBm/1,28 MHz | 1,2 dB | Formula:
Wanted signal level + TT
AWGN level unchanged
Wanted signal level =
+ 31,2 dB |
+| 7.4 Adjacent Channel Selectivity (ACS) | Wanted signal level =
Ref. sensitivity level + 6 dB
Interfering signal level
3,84 Mcps TDD option:
Wide Area BS: -52 dBm/3,84 MHz
Local Area BS: -38 dBm/3,84 MHz
1,28 Mcps TDD option:
Wide Area BS: -55 dBm/1,28 MHz
Local Area BS: -41 dBm/1,28 MHz | 0 dB | Formula:
Wanted signal level + TT
Interfering signal level unchanged
Wanted signal level =
Ref. sensitivity level + 6 dB |
+| 7.5 Blocking characteristics | Wanted signal level =
+ 6 dB
3,84 Mcps TDD option:
Interfering signal level see tables 7.6 to 7.10
1,28 Mcps TDD option:
Interfering signal level see tables 7.6A to 7.10A | 0 dB | Formula:
Wanted signal level + TT
Interfering signal level unchanged
Wanted signal level =
+ 6 dB |
+| 7.6 Intermodulation characteristics | Wanted signal level =
+ 6 dB
Interferer1 level (10 MHz offset CW for 3,84 Mcps TDD option; 3,2 MHz offset CW for 1,28 Mcps TDD option)) = -48 dBm
Interferer2 level (20 MHz offset W-CDMA Modulated for 3,84 Mcps TDD option; 6,4 Mcps offset W-CDMA Modulated for 1,28 Mcps TDD option)) = -48 dBm | 0 dB | Formula:
Wanted signal level + TT
Interferer 1 level: unchanged
Interferer 2 level: unchanged
Wanted signal level =
+ 6 dB |
+
+| | | | | |
+|------------------|----------|-------------------------------------|------|--------------------------------------------------------------------------|
+| 7.7
emissions | Spurious | Maximum level defined in table 7.12 | 0 dB | Formula: Maximum level + TT
Add TT to maximum level in table 7.12 |
+|------------------|----------|-------------------------------------|------|--------------------------------------------------------------------------|
+
+**Table D.3: Derivation of Test Requirements (Performance requirements)**
+
+| Test | Minimum Requirement in TS 25.105 | Test Tolerance (TT) | Test Requirement in TS 25.142 |
+|---------------------------------------------------------|----------------------------------|---------------------|-------------------------------|
+| 8.2 Demodulation in static propagation conditions | | TBD | |
+| 8.3 Demodulation of DCH in multipath fading conditions | | TBD | |
+| 8.3A Demodulation of DCH in high speed train conditions | Received value | 0.4dB | Minimum requirement + TT |
+
+## Annex E (informative): Acceptable uncertainty of Test Equipment
+
+This informative annex specifies the critical parameters of the components of an overall Test System (e.g. Signal generators, Signal Analysers etc.) which are necessary when assembling a Test System which complies with subclause 5.10 Acceptable Uncertainty of Test System. These Test Equipment parameters are fundamental to the accuracy of the overall Test System and are unlikely to be improved upon through System Calibration.
+
+**Table E.1: Equipment accuracy for transmitter measurements**
+
+| Test | | Equipment accuracy | Range over which equipment accuracy applies |
+|---------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|
+| 6.2 | Maximum output power | Not critical | Not critical |
+| 6.3 | Frequency stability | $\pm 10$ Hz + timebase = 12 Hz | Measurements in the range $\pm 500$ Hz. |
+| 6.4.2 | Power control steps | single step: $\pm 0,1$ dB
ten steps: $\pm 0,3$ dB | Pmax to Pmax - 30 dB |
+| 6.4.3 | Power control dynamic range | $\pm 0,3$ dB | Pmax to Pmax - 30 dB |
+| 6.4.4 | Minimum output power | Not critical | Pmax to Pmax - 30 dB |
+| 6.4.5 | Primary CCPCH power | Not critical | Not critical |
+| 6.4.6 | Differential accuracy of Primary CCPCH power | $\pm 0,1$ dB | |
+| 6.5.1 | Transmit OFF power | Not critical | Not critical |
+| 6.5.2 | Transmit ON/OFF time mask | Not critical | Not critical |
+| 6.6.1 | Occupied bandwidth | $\pm 100$ kHz | $\pm 1$ MHz of the minimum requirement |
+| 6.6.2.1 | Spectrum emission mask | Not critical | Not critical |
+| 6.6.2.2 | ACLR | minimum requirement: $\pm 0,8$ dB
requirement in case of operation in proximity: $\pm 4,0$ dB
requirement in case of co-siting: TBD | Measurements in the range $\pm 3$ dB of the minimum requirement at signal power = Pmax |
+| 6.6.3 | Spurious emissions | Not critical | Not critical |
+| 6.7 | Transmit intermodulation (interferer requirements) | Not critical | Not critical |
+| 6.8.1 | Modulation accuracy | $\pm 2,5$ %
(for single code) | Specified accuracy applies to measurement results between $\pm 7,5$ % and 17,5% at signal power = Pmax to Pmax - 30 dB |
+| 6.8.2 | Peak code domain error | $\pm 1$ dB | Measurements in the range -25 dB to -30 dB at signal power = Pmax |
+| 6.8.3 | Relative Code Domain Error | $\pm 1,0$ dB | Measurements in the range -18.9 to -24.9 dB at signal power = Pmax |
+| 6.8.4 | Time alignment error in MIMO transmission | 1,28 Mcps TDD option: $\pm [78]$ ns | |
+
+**Table E.2: Equipment accuracy for receiver measurements**
+
+| Subclause | | Equipment accuracy | Range over which equipment accuracy applies |
+|-----------|---------------------------------|--------------------|---------------------------------------------|
+| 7.2 | Reference sensitivity level | Not critical | Not critical |
+| 7.3 | Dynamic range | Not critical | Not critical |
+| 7.4 | Adjacent channel selectivity | Not critical | Not critical |
+| 7.5 | Blocking characteristics | Not critical | Not critical |
+| 7.6 | Intermodulation characteristics | Not critical | Not critical |
+| 7.7 | Spurious Emissions | Not critical | Not critical |
+
+**Table E.3: Equipment accuracy for performance measurements**
+
+| Subclause | Equipment accuracy | Range over which equipment accuracy applies |
+|---------------------------------------------------------|---------------------------|----------------------------------------------------|
+| 8.2 Demodulation in static propagation conditions | Not critical | Not critical |
+| 8.3 Demodulation of DCH in multipath fading conditions | Not critical | Not critical |
+| 8.3A Demodulation of DCH in high speed train conditions | Not critical | Not critical |
+
+---
+
+## Annex F (normative): General rules for statistical testing
+
+### F.1 Statistical testing of receiver BER/BLER performance
+
+#### F.1.1 Error Definition
+
+Bit Error Ratio (BER) and Block Error Ratio (BLER) are defined in section 3.1.
+
+#### F.1.2 Test Method
+
+Each test is performed in the following manner:
+
+- a) Setup the required test conditions.
+- b) Record the number of samples tested and the number of occurred events (bit error or block error)
+- c) Stop the test at a stop criterion which is minimum test time or an early pass or an early fail event.
+- d) Once the test is stopped decide according to the pass fail decision rules ( subclause F.1.7)
+
+#### F.1.3 Test Criteria
+
+The test shall fulfil the following requirements:
+
+- a) good pass fail decision
+ - 1) to keep reasonably low the probability (risk) of passing a bad unit for each individual test;
+ - 2) to have high probability of passing a good unit for each individual test;
+- b) good balance between test time and statistical significance
+ - 3) to perform measurements with a high degree of statistical significance;
+ - 4) to keep the test time as low as possible.
+
+#### F.1.4 Calculation assumptions
+
+##### F.1.4.1 Statistical independence
+
+- a) It is assumed, that error events are rare ( $\lim \text{BER BLER} \ll 0$ ) independent statistical events. However the memory of the convolutional /turbo coder is terminated after oneTTI. Samples and errors are summed up everyTTI. So the assumption of independent error events is justified.
+- b) In the BLER test with fading there is the memory of the multipath fading channel which interferes the statistical independence. A minimum test time is introduced to average fluctuations of the multipath fading channel. So the assumption of independent error events is justified approximately.
+
+##### F.1.4.2 Applied formulas
+
+The formulas, applied to describe the BER BLER test, are based on the following experiments:
+
+- 1) After having observed a certain number of errors (**ne**) the number of samples are counted to calculate BER BLER. Provisions are made (note 1) such that the complementary experiment is valid as well:
+- 2) After a certain number of samples (**ns**) the number of errors, occurred, are counted to calculate BER BLER.
+
+Experiment 1) stipulates to use the following Chi Square Distribution with degree of freedom ne:
+
+$$2 \cdot \text{dchisq}(2 \cdot \text{NE}, 2 \cdot \text{ne}).$$
+
+Experiment 2) stipulates to use the Poisson Distribution:
+
+$$\text{dpois}(\text{ne}, \text{NE})$$
+
+(NE: mean of the distribution)
+
+To determine the early stop conditions, the following inverse cumulative operation is applied:
+
+$$0.5 * \text{qchisq}(D, 2 * \text{ne}). \text{ This is applicable for experiment (1) and (2).}$$
+
+D: wrong decision risk per test step
+
+Note: other inverse cumulative operations are available, however only this is suited for experiment (1) and (2).
+
+### F.1.4.3 Approximation of the distribution
+
+The test procedure is as follows:
+
+During a running measurement for a BS ns (number of samples) and ne (number of errors) are accumulated and from this the preliminary BER BLER is calculated. Then new samples up to the next error are taken. The entire past and the new samples are basis for the next preliminary BER BLER. Depending on the result at every step, the BS can pass, can fail or must continue the test.
+
+As early pass- and early fail-BSs leave the statistical totality under consideration, the experimental conditions are changed every step resulting in a distribution that is truncated more and more towards the end of the entire test. Such a distribution can not any more be handled analytically. The unchanged distribution is used as an approximation to calculate the early fail and early pass bounds.
+
+### F.1.5 Definition of good pass fail decision
+
+This is defined by the probability of wrong decision F at the end of the test. The probability of a correct decision is 1-F.
+
+The probability (risk) to fail a good DUT shall be $\leq F$ according to the following definition: The failed DUT is still better than the specified error ratio (Test requirement) with a probability of $\leq F$ .
+
+The probability to pass a bad DUT shall be $\leq F$ according to the following definition: The passed DUT is still worse than M times the specified error ratio ( $M > 1$ is the bad DUT factor) with a probability of $\leq F$ .
+
+This definitions lead to an early pass and an early fail limit:
+
+Early fail: $\text{ber} \geq \text{berlim}_{\text{fail}}$
+
+$$(1)$$
+
+For $\text{ne} \geq 7$
+
+Early pass: $\text{ber} \leq \text{berlimbad}_{\text{pass}}$
+
+$$(2)$$
+
+For $\text{ne} \geq 1$
+
+With
+
+ber (normalized BER,BLER): BER,BLER according to F.1.1 divided by Test requirement
+
+D: wrong decision probability for a test step . This is a numerically evaluated fraction of F, the wrong decision probability at the end of the test. See table F.1.
+
+ne: Number of error events
+
+M: bad DUT factor see table F.1.
+
+qchisq: inverse-cumulative-function of the chi-squared-distribution
+
+## F.1.6 Good balance between test time and statistical significance
+
+Three independent test parameters are introduced into the test and shown in Table F.1. These are the obvious basis of test time and statistical significance. From the first two of them four dependent test parameters are derived. The third independent test parameter is justified separately.
+
+**Table F.1: independent and dependant test parameters**
+
+| Independent parameters | | | Dependant parameters | | |
+|-------------------------------------------------|--------------------------|------------------|---------------------------------------------------------|------------------------------------------|-------------------------------|
+| Test Parameter | Value | Reference | Test parameter | Value | Reference |
+| Bad DUT factor M | 1.5 | Tables F.4 & F.5 | Early pass/fail condition | Curves | Subclause F.1.5
Figure F.1 |
+| Final probability of wrong pass/fail decision F | 0.2%,
(0.02%, note 2) | Subclause F.1.5 | Target number of error events | 345 | Table F.4 & F.5 |
+| | | | Probability of wrong pass/fail decision per test step D | 0.0085%,
(0.0008% and 0.008%, note 2) | |
+| | | | Test limit factor TL | 1.234 | Table F.4 & F.5 |
+| Minimum test time | | Tables F.2 & F.3 | | | |
+
+The minimum test time is derived from the following justification:
+
+- 1) For no propagation conditions and static propagation condition
+
+No early fail calculated from fractional number of errors <1 (see note 1)
+
+- 2) For multipath fading condition
+
+No stop of the test until [990] wavelengths are crossed during relevant BS reception timeslots, relevant for BER BLER testing, with the speed given in the fading profile.
+
+- 3) For high speed train condition
+
+Scenario 1: 82.3s. This corresponds to 4 complete cycles of approach towards and departure leave to and from a BS antenna
+
+Scenario 3: 28.8s. This corresponds to 4 complete cycles of approach towards and departure from a BS antenna
+
+**Table F.2: minimum Test time**
+
+| Fading profile | Minimum test time |
+|--------------------------------------------------------------------------------------------------------------|--------------------|
+| Multipath propagation 3 km/h | [164 s*TSPF/TSRX] |
+| Multipath propagation 120 km/h | [4.1 s* TSPF/TSRX] |
+| High speed train conditions
Scenario 1 | 82.3 sec |
+| High speed train conditions
Scenario 3 | 28.8 sec |
+| TSPF = Time slots per frame
TSRX = relevant reception timeslots per frame, relevant for the BER BLER test | |
+
+TSPF and TSRX form the prolongation factor and depend on the user data rate and the TDD Option (3,84 Mchip/s or 1,28 Mchip/s )
+
+**Table F.3: Prolongation factor for minimum Test time**
+
+| User Data rate | TSPF/TSRX for TDD 3,84 Mchip/s | TSPF/TSRX for TDD 1,28 Mchip/s |
+|----------------|--------------------------------|--------------------------------|
+| 12.2 kbit/s | 15/1 | 7/1 |
+| 64 kbit/s | 15/1 | 7/1 |
+| 144 kbit/s | 15/1 | 7/2 |
+| 384 kbit/s | 15/3 | 7/4 |
+
+In tables F.4 and F.5 the minimum test time is converted in minimum number of samples.
+
+## F.1.7 Pass fail decision rules
+
+No decision is allowed before the minimum test time is elapsed.
+
+- 1) If minimum Test time < time for target number of error events then the following applies: The required confidence level 1-F (= correct decision probability) shall be achieved. This is fulfilled at an early pass or early fail event.
+
+### For BER:
+
+For every TTI (Transmit Time Interval) sum up the number of bits (ns) and the number of errors (ne) from the beginning of the test and calculate
+
+BER1 (including the artificial error at the beginning of the test (Note 1)) and
+
+BER0 (excluding the artificial error at the beginning of the test (Note 1)).
+
+If BER0 is above the early fail limit, fail the DUT.
+
+If BER1 is below the early pass limit, pass the DUT.
+
+Otherwise continue the test
+
+### For BLER:
+
+For every TTI sum up the number of blocks (ns) and the number of erroneous blocks (ne) from the beginning of the test and calculate
+
+BLER1 (including the artificial error at the beginning of the test (Note 1)) and
+
+BLER0 (excluding the artificial error at the beginning of the test (Note 1)).
+
+If BLER1 is below the early pass limit, pass the DUT.
+
+If BLER0 is above the early fail limit, fail the DUT.
+
+Otherwise continue the test
+
+- 2) If the minimum test time ≥ time for target error events, then the test runs for the minimum test time and the decision is done by comparing the result with the test limit.
+
+### For BER:
+
+For every TTI (Transmit Time Interval) sum up the number of bits (ns) and the number of errors (ne) from the beginning of the test and calculate BER0
+
+### For BLER:
+
+For every TTI sum up the number of blocks (ns) and the number of erroneous blocks (ne) from the beginning of the test and calculate BLER0
+
+If BER0/BLER0 is above the test limit, fail the DUT.
+
+If BER0/BLER0 is on or below the test limit, pass the DUT.
+
+## F.1.8 Test conditions for BER,BLER Tests
+
+Table F.4: Test conditions for BER tests
+
+| Type of test (BER) | Propagation conditions | Test requirement (BER) | Test limit (BER)= Test requirement (BER)x TL | Target number of error events (time) Note * | Minimum number of samples | Prob that good unit will fail = Prob that bad unit will pass (%) | Bad unit BER factor M |
+|------------------------------------------------|------------------------|------------------------|----------------------------------------------|---------------------------------------------|---------------------------|------------------------------------------------------------------|-----------------------|
+| Reference Sensitivity Level | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 |
+| Dynamic Range | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 |
+| Adjacent Channel Selectivity | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 |
+| Blocking Characteristics Pass condition Note 2 | - | 0.001 | 1.251 | 402 (26.3s) | Note 1 | 0.2 | 1.5 |
+| Blocking Characteristics Fail condition Note 2 | - | 0.001 | 1.251 | 402 (26.3s) | Note 1 | 0.02 | 1.5 |
+| Intermodulation Characteristics | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 |
+
+Note \*: the time in the bracket means the reception time
+
+**Table F.5: Test conditions for BLER tests**
+
+| Type of test (BLER) | Information Bit rate (kbit/s) | Test requirement (BLER) | Test limit (BLER)= Test requirement (BLER)x TL | Target number of error events (time) | Minimum number of samples (time) TDD 3,84 Mchip/s | Minimum number of samples (time) TDD 1,28 Mchip/s | Prob that bad unit will pass = Prob that good unit will fail (%) | Bad unit BLER factor M |
+|----------------------------------------------------------------------------------------|-------------------------------|-------------------------|------------------------------------------------|--------------------------------------|---------------------------------------------------|----------------------------------------------------------------|------------------------------------------------------------------|------------------------|
+| Demodulation in Static Propagation conditions | 12.2 | 0.01 | 1.234 | 345 (559s) | Note1 | Note1 | 0.2 | 1.5 |
+| | 64 | 0.1 | | (55.9s) | | | | |
+| | | 0.01 | | (559s) | | | | |
+| | 144 | 0.1 | | (55.9s) | | | | |
+| | | 0.01 | | (559s) | | | | |
+| | 384 | 0.1 | | (28s) | | | | |
+| | | 0.01 | | (280s) | | | | |
+| Demodulation of DCH in Multi-path Fading Propagation conditions 3km/h (Case 1, Case 2) | 12.2 | 0.01 | 1.234 | 345 (559s) | [(2460s)] | [(1148s)] | 0.2 | 1.5 |
+| | 64 | 0.1 | | (55.9s) | [123000] | [5740] | | |
+| | | 0.01 | | (559s) | [123000] | [5740] | | |
+| | 144 | 0.1 | | (55.9s) | [123000] | [5740]
[(574s)] | | |
+| | | 0.01 | | (559s) | [123000] | [2870] | | |
+| | 384 | 0.1 | | (28s) | [82000]
[(820s)] | [2870]
[(278s)] | | |
+| | | 0.01 | | (280s) | [82000] | [27800]
[27800] | | |
+| Demodulation of DCH in Multi-path Fading Propagation conditions 120 km/h (Case3) | 12.2 | 0.01 | 1.234 | 345 (559s) | [(61.5s)] | [(28.7s)] | 0.2 | 1.5 |
+| | 64 | 0.1 | | (55.9s) | [3075] | [1435] | | |
+| | | 0.01 | | (559s) | [3075] | [1435] | | |
+| | 144 | 0.1 | | (55.9s) | [3075] | [1435]
[(14.35s)] | | |
+| | | 0.01 | | (559s) | [3075] | [718] | | |
+| | 384 | 0.1 | | (28s) | [3075]
[(20.5s)] | [718]
[(7.175s)] | | |
+| | | 0.01 | | (280s) | [2050]
[2050] | [718]
[718] | | |
+| Demodulation of DCH in high speed train condition | 12.2 | 0.01 | 1.234 | 345 (559s) | | Scenario 1
(82.3s)
4115
Scenario 3
(28.8s)
1440 | 0.2 | 1.5 |
+| | 64 | 0.1 | | (55.9s) | | | | |
+| | | 0.01 | | (559s) | | | | |
+
+## F.1.9 Practical Use (informative)
+
+See figure F.1:
+
+- The early fail limit represents formula (1) in F.1.5. The range of validity is $n_e \geq 7$ ( $\geq 8$ in case of blocking test) to $n_e = 345$
+- The early pass limit represents formula (2) in F.1.5. The range of validity is $n_e = 1$ to $n_e = 345$ . See note 1
+- The intersection co-ordinates of both curves are : target number of errors $n_e = 345$ and test limit $TL = 1.234$ .
+- The range of validity for $TL$ is $n_e > 345$ .
+
+A typical BER BLER test, calculated from the number of samples and errors (F.1.2.(b)) using experimental method (1) or (2) (see F.1.4.2 calculation assumptions) runs along the yellow trajectory. With an errorless sample the trajectory goes down vertically. With an erroneous sample it jumps up right. The tester checks if the BER BLER test intersects the early fail or early pass limits. The real time processing can be reduced by the following actions:
+
+$BLER_0$ (excluding the artificial error at the beginning of the test (Note 1)). is calculated only in case of an error event.
+
+$BER_0$ (excluding the artificial error at the beginning of the test (Note 1)). is calculated only in case of an error event within a TTI.
+
+So the early fail limit cannot be missed by errorless samples.
+
+The check against the early pass limit may be done by transforming formula (2) in F.1.5 such that the tester checks against a Limit-Number-of-samples ( $NL(ne)$ ) depending on the current number of errors (including the artificial error at the beginning of the test (Note 1)).
+
+Early pass if
+
+TR: test requirement (0.001)
+
+
+
+Figure F.1: A log-log plot showing the relationship between BER (normalised to test requirement) on the y-axis and Number of errors (ne) on the x-axis. The y-axis ranges from 0.1 to 10, and the x-axis ranges from 1 to 1000. The plot is divided into four regions: 'continue' (yellow), 'early fail' (pink), 'fail' (purple), and 'pass' (cyan). A red curve represents the 'early fail' limit, and a black curve represents the 'test limit'. A horizontal line at y=1 represents the 'test requirement'. A dashed orange line represents the 'BER trajectory'. A legend on the left shows 'berlim\_fail(ne, D)' as a red line, 'berlimbad\_pass(ne, D)' as a black line, 'M' as a horizontal line, 'TL' as a horizontal line, and '1' as a horizontal line.
+
+Figure F.1
+
+NOTE 1: At the beginning of the test, an artificial error is introduced. This ensures that an ideal DUT meets the valid range of the early pass limit. In addition this ensures that the complementary experiment (F.1.4.2 bullet point (2)) is applicable as well.
+
+For the check against the early fail limit the artificial erroneous sample, introduced at the beginning of the test, is disregarded.
+
+Due to the nature of the test, namely discrete error events, the early fail condition shall not be valid, when fractional errors $< 1$ are used to calculate the early fail limit: Any early fail decision is postponed until number of errors $ne \geq 7$ . In the blocking test any early fail decision is postponed until number of errors $ne \geq 8$ .
+
+NOTE 2: $F=0.2\%$ is intended to be used for a test containing a few BER/BLER tests (e.g. receiver sensitivity is repeated 12 times(3 RF Channels \* 2 Power-supplies \* 2 Temperatures). For a test containing many BER/BLER tests (e.g. blocking test) this value is not appropriate for a single BER/BLER test.
+
+The blocking test contains approx. 12750 single BER tests. A DUT on the limit will fail approx. 25 to 26 times due to statistical reasons using wrong decision probability at the end of the test $F=0.2\%$ . This shall be solved by the following rule:
+
+All passes (based on $F=0.2\%$ ) are accepted, including the wrong decisions due to statistical reasons.
+
+An early fail limit based on $F=0.02\%$ instead of $0.2\%$ is established. That ensures that wrong decisions due to statistical reasons are reduced to 2 to 3 in 12750 BER measurements. If the fail cases are $\leq 12$ , it is allowed to repeat each fail cases 1 time before the final verdict.
+
+These asymmetric test conditions ensure that a DUT on the limit consumes hardly more test time for a blocking test than in the symmetric case and reduces the wrong decision probability considerably and on the other hand the repetition allowance sufficiently suppresses the residual statistically caused wrong verdict for the aggregate test.
+
+---
+
+## Annex G (informative): Change History
+
+**Table G.1: Change History**
+
+| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item |
+|-------|-----------|------|---|-----------------------------------------------------------------------------------------------|-----|-------|-------|------------------------|
+| RP-29 | | | | Rel-7 version created based on v6.3.0 | | | 7.0.0 | |
+| RP-29 | RP-050579 | 0176 | | Introduction of UMTS 2.6 GHz operating band for TDD | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-29 | RP-050579 | 0177 | | UMTS 2.6 GHz TDD Propagation Conditions | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-29 | RP-050579 | 0178 | 2 | Channel Raster for 3,84 Mcps TDD in UMTS 2.6 GHz | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-29 | RP-050579 | 0179 | | UMTS 2.6 GHz TDD BS Transmitter Specifications | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-29 | RP-050579 | 0180 | | UMTS 2.6 GHz TDD BS Receiver Specifications | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-29 | RP-050579 | 0181 | | Introduction of Propagation Conditions for UMTS 2.6 GHz for 1,28Mcps TDD | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-29 | RP-050579 | 0182 | | UMTS 2.6 GHz TDD BS receiver spurious emission | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD |
+| RP-30 | RP-050740 | 0183 | | Introduction of UMTS 2.6 BS transmitter specification for 1,28Mcps TDD | B | 7.0.0 | 7.1.0 | RInImp-UMTS2600 TDD |
+| RP-30 | RP-050740 | 0184 | | Introduction of UMTS 2.6 BS receiver specification for 1,28Mcps TDD | B | 7.0.0 | 7.1.0 | RInImp-UMTS2600 TDD |
+| RP-30 | RP-050841 | 0186 | | Name correction of logical and transport channels in Annex 2 | A | 7.0.0 | 7.1.0 | TEI6 |
+| RP-32 | RP-060307 | 0187 | | UMTS 2.6 GHz blocking and spurious emission test condition | F | 7.1.0 | 7.2.0 | RInImp-UMTS2600 TDD |
+| RP-32 | RP-060312 | 0188 | 1 | 7.68 Mcps Frequency Band & Channel Arrangement | B | 7.1.0 | 7.2.0 | VHCR TDD-RF |
+| RP-32 | RP-060312 | 0189 | | 7.68 Mcps Transmitter Characteristics | B | 7.1.0 | 7.2.0 | VHCR TDD-RF |
+| RP-32 | RP-060312 | 0190 | 1 | 7.68 Mcps Receiver Characteristics | B | 7.1.0 | 7.2.0 | VHCR TDD-RF |
+| RP-32 | RP-060312 | 0191 | | 7.68 Mcps - Channel Performance | B | 7.1.0 | 7.2.0 | VHCR TDD-RF |
+| RP-32 | RP-060312 | 0192 | | 7.68 Mcps Measurement Channels & Propagation Conditions | B | 7.1.0 | 7.2.0 | VHCR TDD-RF |
+| RP-33 | RP-060517 | 0205 | | Clarification of Tx spurious emission level from 3,84 Mcps and 7.68 Mcps TDD BS into PHS band | F | 7.2.0 | 7.3.0 | TEI7 |
+| RP-33 | RP-060518 | 0212 | 1 | Clarification on the deployment of UTRA TDD in Japan | A | 7.2.0 | 7.3.0 | TEI |
+| RP-33 | RP-060519 | 0214 | 1 | Tx and Rx Spurious Emission from 3,84 Mcps and 7.68 Mcps TDD BS into FDD bands in Japan | A | 7.2.0 | 7.3.0 | TEI6 |
+| RP-33 | RP-060528 | 0206 | | Performance requirements for 3,84 Mcps E-DCH channel. | B | 7.2.0 | 7.3.0 | EDCH TDD-RF |
+| RP-33 | RP-060526 | 0207 | 2 | 7.68 Mcps Operations in 2.6 GHz band | B | 7.2.0 | 7.3.0 | RInImp-UMTS26V HCR TDD |
+| RP-34 | RP-060818 | 0215 | | Performance requirements for 7.68 Mcps E-DCH channel. | B | 7.3.0 | 7.4.0 | TEI7 |
+| RP-35 | RP-070081 | 0219 | | HS-SICH detection performance test specification for 1,28Mcps TDD | A | 7.4.0 | 7.5.0 | TEI6 |
+| RP-35 | RP-070082 | 0216 | | Tx and Rx Spurious Emission from 7.68 Mcps TDD BS into FDD band in Japan | F | 7.4.0 | 7.5.0 | TEI7 |
+| RP-35 | RP-070082 | 0217 | | Clarification on the deployment of UTRA TDD in Japan | F | 7.4.0 | 7.5.0 | TEI7 |
+| RP-36 | RP-070369 | 0225 | | Modifying category B spurious emission limits for UTRA TDD BS | A | 7.5.0 | 7.6.0 | TEI |
+| RP-36 | RP-070377 | 0221 | | Adding test case of E-DCH performance requirement for 1,28Mcps TDD option | F | 7.5.0 | 7.6.0 | LCRTDD-EDCH-RF |
+
+| | | | | | | | | |
+|-------|-----------|------|---|--------------------------------------------------------------------------------------------------------|---|-------|--------|-----------------------|
+| RP-37 | RP-070651 | 0227 | | 7.68 Mcps TDD Option test tolerances and transmit ON/OFF time mask level. | F | 7.6.0 | 7.7.0 | TEI7 |
+| RP-37 | RP-070651 | 0226 | | Inclusion of 7.68 Mcps in the scope of document | F | 7.6.0 | 7.7.0 | TEI7 |
+| RP-39 | RP-080119 | 0229 | 1 | Correcting the power allocation for HS-SICH performance detection | A | 7.7.0 | 7.8.0 | TEI6 |
+| RP-40 | RP-080329 | 0234 | | RCDE for 1.28Mcps TDD 64QAM modulated codes | B | 7.8.0 | 7.9.0 | RANimp-64 Qam1.28T DD |
+| RP-40 | RP-080384 | 0233 | 1 | UMTS2300MHz propagation channel model addition for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD |
+| RP-40 | RP-080384 | 0232 | 1 | UMTS2300MHz Receiver performance addition for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD |
+| RP-40 | RP-080384 | 0231 | 1 | UMTS2300MHz Transmitter performance addition for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD |
+| RP-40 | RP-080384 | 0230 | 1 | UMTS2300MHz New band introduction for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD |
+| RP-41 | RP-080636 | 0236 | 1 | Modify the Fixed Reference Channels of E-DCH for LCR TDD | A | 8.0.0 | 8.1.0 | TEI7 |
+| RP-43 | RP-090166 | 0241 | | Correction of BS reference measurement channel and performance requirement for LCR TDD 384kbps service | A | 8.1.0 | 8.2.0 | TEI4 |
+| RP-43 | RP-090197 | 0242 | | Introduction of band 1880MHz for 25.142 | F | 8.1.0 | 8.2.0 | RlnImp9-UMTS1880 TDD |
+| RP-43 | RP-090197 | 0243 | | UMTS1880MHz: transmitter characteristic | F | 8.1.0 | 8.2.0 | RlnImp9-UMTS1880 TDD |
+| RP-43 | RP-090197 | 0244 | | UMTS1880MHz: receiver characteristic and propagation conditions | F | 8.1.0 | 8.2.0 | RlnImp9-UMTS1880 TDD |
+| RP-44 | RP-090553 | 0247 | | Correction of local area base station coexistence requirements | F | 8.2.0 | 8.3.0 | RlnImp9-UMTS1880 TDD |
+| RP-44 | RP-090554 | 0245 | 1 | Addition of Time alignment error test for BS supporting 1.28Mcps TDD MIMO | F | 8.2.0 | 8.3.0 | RANimp-LCRMIMO |
+| RP-44 | RP-090556 | 0246 | | Correction on the test parameter table of E-DCH for 1.28Mcps TDD | F | 8.2.0 | 8.3.0 | TEI8 |
+| RP-45 | RP-090818 | 251 | | Changes to 25.142 accommodating IMB | F | 8.3.0 | 8.4.0 | MSBFN-DOB |
+| RP-46 | RP-091285 | 255 | | BS test requirements in high speed train condition for LCR TDD | B | 8.5.0 | 9.0.0 | RlnImp9-LCRTDD350 |
+| RP-47 | RP-100257 | 260 | | Correction of E-DCH FRC3 for LCR TDD | A | 9.0.0 | 9.1.0 | TEI7 |
+| RP-47 | RP-100253 | 262 | | Protection of E-UTRA for UTRA TDD BS | A | 9.0.0 | 9.1.0 | LTE-RF |
+| RP-47 | RP-100273 | 257 | | Additional BS test requirements in high speed train conditions for LCR TDD | F | 9.0.0 | 9.1.0 | RlnImp9-LCRTDD350 |
+| RP-48 | RP-100631 | 263 | 1 | Corrections for performance requirements in HST condition | F | 9.1.0 | 9.2.0 | TEI9 |
+| RP-49 | RP-100922 | 264 | 1 | Clarification on applicability of requirements for multi-carrier BS | F | 9.2.0 | 9.3.0 | RlnImp9-RFmulti |
+| RP-50 | RP-101340 | 275 | | Addition of test case for HS-SICH type2 performance | A | 9.3.0 | 9.4.0 | TEI8 |
+| RP-50 | RP-101340 | 277 | | Clarifications of Base Station transmit and receive configurations | A | 9.3.0 | 9.4.0 | TEI8 |
+| RP-50 | RP-101351 | 267 | 1 | Introduction of the BS requirements for 1.28Mcps TDD MC-HSUPA | B | 9.4.0 | 10.0.0 | TDD_MC_H SUPA |
+| RP-50 | RP-101352 | 269 | | 1.28Mcps TDD Home NodeB class into Base Station class in 25.142 | B | 9.4.0 | 10.0.0 | HNB_LCRT DD_RF-Perf |
+| RP-50 | RP-101352 | 270 | | 1.28Mcps TDD Home NodeB Transmitter | B | 9.4.0 | 10.0.0 | HNB_LCRT DD_RF-Perf |
+| RP-50 | RP-101352 | 271 | | 1.28Mcps TDD Home NodeB Receiver | B | 9.4.0 | 10.0.0 | HNB_LCRT DD_RF-Perf |
+
+| | | | | | | | | |
+|-------|-----------|------|---|---------------------------------------------------------------------------------------------|---|--------|--------|-----------------------------|
+| RP-50 | RP-101352 | 272 | | 1.28Mcps TDD Home NodeB Demodulation Requirement | B | 9.4.0 | 10.0.0 | HNB_LCRT
DD_RF-Perf |
+| RP-51 | RP-110352 | 0278 | - | Adding missing demodulation requirements for LCR TDD Home BS | F | 10.0.0 | 10.1.0 | TEI10 |
+| RP-51 | RP-110352 | 0279 | 1 | Harmonization of co-existence/co-location requirements between 25.142 and 36.141 | F | 10.0.0 | 10.1.0 | TEI10 |
+| RP-52 | RP-110796 | 280 | | Correction of co-existence requirement for UTRA TDD | F | 10.1.0 | 10.2.0 | TEI10 |
+| RP-52 | RP-110796 | 281 | | Correction of the test port description for TS 25.142 | F | 10.1.0 | 10.2.0 | TEI10 |
+| RP-53 | RP-111262 | 282 | | Clarification of demodulation in static propagation and Multipath fading case 1 for Home BS | F | 10.2.0 | 10.3.0 | TEI10 |
+| RP-56 | RP-120783 | 286 | | Update to regional requirement table | F | 10.3.0 | 10.4.0 | TEI10 |
+| RP-56 | RP-120765 | 292 | 1 | Additional spurious emissions requirements for PHS | A | 10.3.0 | 10.4.0 | TEI8 |
+| RP-56 | RP-120795 | 283 | 1 | TDD blocking for co-location | F | 10.4.0 | 11.0.0 | TEI11 |
+| RP-56 | RP-120795 | 284 | 1 | WA co-existence/co-location | F | 10.4.0 | 11.0.0 | TEI11 |
+| RP-56 | RP-120795 | 285 | 1 | Co-existence between TDD systems | F | 10.4.0 | 11.0.0 | TEI11 |
+| RP-56 | RP-120795 | 287 | | LA co-existence/co-location | F | 10.4.0 | 11.0.0 | TEI11 |
+| RP-56 | RP-120795 | 288 | | Co-existence/co-location between LA TDD systems | F | 10.4.0 | 11.0.0 | TEI11 |
+| RP-56 | RP-120793 | 289 | | Introduction of Band 44 | B | 10.4.0 | 11.0.0 | LTE_APAC7
00-Core |
+| RP-57 | RP-121296 | 296 | | Clarification for TDD Band | A | 11.0.0 | 11.1.0 | TEI8 |
+| RP-59 | RP-130287 | 297 | | Update of BS co-existence requirement towards UTRA TDD bands in China | F | 11.1.0 | 11.2.0 | TEI11 |
+| RP-60 | RP-130768 | 298 | 1 | On additional ACLR requirement | F | 11.2.0 | 11.3.0 | TEI11 |
+| RP-60 | RP-130764 | 299 | | Co-existence around 3500 MHz | F | 11.2.0 | 11.3.0 | RInImp8-
UMTSLTE3
500 |
+| RP-60 | RP-130768 | 300 | | Rel.11 CR for 25.142: Editorial Corrections and Amendment with Missed TT Values | F | 11.2.0 | 11.3.0 | TEI11 |
+| RP-60 | RP-130768 | 301 | 1 | Addition of MC-HSDPA for general clause 6.1 | F | 11.2.0 | 11.3.0 | TEI11 |
+| RP-66 | RP-142146 | 313 | 1 | Introduction of testing for multi-carrier and multi-band operation in TS25.142 | B | 11.3.0 | 11.4.0 | MB_MSR_
RF-Perf |
+| RP-66 | RP-142146 | 312 | 1 | Introduction of requirements for BS capable of multi-band operation | F | 11.3.0 | 11.4.0 | MB_MSR_
RF-Perf |
+| RP-70 | RP-152132 | 316 | | TX intermodulation requirement correction | F | 11.4.0 | 11.5.0 | TEI11 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25143/0f7871077bba48a2c97f7859a5edda0d_img.jpg b/marked/Rel-11/25_series/25143/0f7871077bba48a2c97f7859a5edda0d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4216824e8a8cb5b78a2fd839ecb0c206bc73e3c9
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/0f7871077bba48a2c97f7859a5edda0d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca7402ed21a85587d22d9b56cc5bfbfb725ba84521f098975ead7a654a281410
+size 39436
diff --git a/marked/Rel-11/25_series/25143/1dee555540363b842d1171ffb8dfe479_img.jpg b/marked/Rel-11/25_series/25143/1dee555540363b842d1171ffb8dfe479_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3af45839bc8fd56015431cf690d3032a351540af
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/1dee555540363b842d1171ffb8dfe479_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1de75c427db12f635d58e883b8401a30df832223feb1bc5bc2e61dfae5433ec6
+size 16127
diff --git a/marked/Rel-11/25_series/25143/443ee770f0d3d98d7411497a3191e2e0_img.jpg b/marked/Rel-11/25_series/25143/443ee770f0d3d98d7411497a3191e2e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..baa6d4eb6642be1fb32f5d9defc611bb2f2198e7
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/443ee770f0d3d98d7411497a3191e2e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc94aac007ad2eaba292ae8940a9de42b3df461aa94563537915bf3a5cdcc67c
+size 16482
diff --git a/marked/Rel-11/25_series/25143/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/Rel-11/25_series/25143/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14ce640b5ab19e560f09521ef49af135662bb823
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca5679586fd63467cca8f7454335a18efd06596312bb785b49b76bcd62f1b824
+size 17642
diff --git a/marked/Rel-11/25_series/25143/5603b5c0db1dd6b96f76b2c851504557_img.jpg b/marked/Rel-11/25_series/25143/5603b5c0db1dd6b96f76b2c851504557_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70fb813359bffcaadffdf7bd2088f2538f5dc3fe
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/5603b5c0db1dd6b96f76b2c851504557_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18bfddc1fcd3b7f032d5f2cd100f208dbcf5781f0cda0149680794fc4e1da849
+size 23540
diff --git a/marked/Rel-11/25_series/25143/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-11/25_series/25143/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81df87ba9284ece160c90ce79bf7f0200637f70c
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c94a69ba97dd02c1042b57c255e300e24c23401019390a2db551d7650b0c653d
+size 29724
diff --git a/marked/Rel-11/25_series/25143/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/25_series/25143/694df81535f89c7bfb9ef0df6f130dc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66b7d88549f38bb30ca9f0f9c7f2aa21ae4b75ba
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/694df81535f89c7bfb9ef0df6f130dc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a9c254e3889a206114b07964d2ac986501637452698454c46a1f198e01b6f0e
+size 20483
diff --git a/marked/Rel-11/25_series/25143/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/marked/Rel-11/25_series/25143/708e4c9a044ef61f586126676eb2eeb8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19acc8bb49782fda39b313ccde0b6d055f96c797
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/708e4c9a044ef61f586126676eb2eeb8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:574eddbcd90e938a5b1725e9767310968063c60c53876e38c1afba4540cae1f2
+size 18908
diff --git a/marked/Rel-11/25_series/25143/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/marked/Rel-11/25_series/25143/9f50279046b74a4e66a1a0144c3b1d11_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65705313db85514d1207cfb6a73c369d91894f8a
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/9f50279046b74a4e66a1a0144c3b1d11_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61c79d59e698bc98bbd496f652c6470b00ca10b442c930832150ae956ce3d7f6
+size 17855
diff --git a/marked/Rel-11/25_series/25143/c0f64806753a053854921deb8f4fc798_img.jpg b/marked/Rel-11/25_series/25143/c0f64806753a053854921deb8f4fc798_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..261f4c06a34ce153cc7c268acef876d4a7611f44
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/c0f64806753a053854921deb8f4fc798_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c81e53820d348ec1a4d86ac3d1cb116d7eac26dcd6709bb3cce6ae37a5452225
+size 18566
diff --git a/marked/Rel-11/25_series/25143/raw.md b/marked/Rel-11/25_series/25143/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b9e52efe0c038015792d32bb54f39aeb70d1fb68
--- /dev/null
+++ b/marked/Rel-11/25_series/25143/raw.md
@@ -0,0 +1,2275 @@
+
+
+
+
+
+
+# Contents
+
+| | | |
+|---------|-----------------------------------------------|----|
+| 1 | Scope..... | 7 |
+| 2 | References..... | 7 |
+| 3 | Definitions, symbols and abbreviations..... | 8 |
+| 3.1 | Definitions..... | 8 |
+| 3.2 | (void)..... | 8 |
+| 3.3 | Abbreviations..... | 8 |
+| 4 | Frequency bands and channel arrangement..... | 9 |
+| 4.1 | Frequency bands..... | 9 |
+| 4.2 | TX – RX frequency separation..... | 9 |
+| 4.3 | Channel arrangement..... | 10 |
+| 4.3.1 | Channel spacing..... | 10 |
+| 4.3.2 | Channel raster..... | 10 |
+| 4.3.3 | Channel number..... | 10 |
+| 5 | General test conditions and declarations..... | 12 |
+| 5.1 | Acceptable uncertainty of Test System..... | 13 |
+| 5.1.1 | Measurements of test environments..... | 13 |
+| 5.1.2 | Measurements of Repeater..... | 14 |
+| 5.2 | Repeater test tolerances (informative)..... | 15 |
+| 5.3 | Interpretation of measurement results..... | 16 |
+| 5.4 | Test Environment..... | 17 |
+| 5.4.1 | Normal test environment..... | 17 |
+| 5.4.2 | Extreme test environment..... | 17 |
+| 5.4.2.1 | Extreme temperature..... | 17 |
+| 5.4.3 | Vibration..... | 18 |
+| 5.4.4 | Power supply..... | 18 |
+| 5.5 | Selection of configurations for testing..... | 18 |
+| 5.6 | Regional requirements..... | 19 |
+| 5.7 | Test Models..... | 20 |
+| 5.8 | Format and interpretation of tests..... | 20 |
+| 5.9 | Repeater configurations..... | 21 |
+| 5.9.1 | Power supply options..... | 21 |
+| 5.9.2 | Combining of Repeaters..... | 21 |
+| 6 | Output power..... | 21 |
+| 6.1 | Maximum output power..... | 21 |
+| 6.1.1 | Definition and applicability..... | 21 |
+| 6.1.2 | Minimum Requirements..... | 21 |
+| 6.1.3 | Test purpose..... | 22 |
+| 6.1.4 | Method of test..... | 22 |
+| 6.1.4.1 | Initial conditions..... | 22 |
+| 6.1.4.2 | Procedure..... | 22 |
+| 6.1.5 | Test Requirements..... | 22 |
+| 7 | Frequency stability..... | 23 |
+| 7.1 | Definition and applicability..... | 23 |
+| 7.2 | Minimum Requirement..... | 23 |
+| 7.3 | Test purpose..... | 23 |
+| 7.4 | Method of test..... | 24 |
+| 7.4.1 | Initial conditions..... | 24 |
+| 7.4.2 | Procedure..... | 24 |
+| 7.5 | Test requirements..... | 24 |
+| 8 | Out of band gain..... | 24 |
+| 8.1 | Definitions and applicability..... | 24 |
+| 8.2 | Minimum Requirements..... | 24 |
+| 8.3 | Test purpose..... | 25 |
+| 8.4 | Method of test..... | 25 |
+
+| | | |
+|-----------|-------------------------------------------------------------------------|----|
+| 8.4.1 | Initial conditions ..... | 25 |
+| 8.4.2 | Procedure ..... | 25 |
+| 8.5 | Test requirements ..... | 25 |
+| 9 | Unwanted emission ..... | 26 |
+| 9.1 | Out of band emission..... | 26 |
+| 9.1.1 | Void..... | 26 |
+| 9.1.2 | Operating band unwanted emissions ..... | 26 |
+| 9.1.2.1 | Definitions and applicability..... | 26 |
+| 9.1.2.2 | Minimum Requirements ..... | 27 |
+| 9.1.2.3 | Test purpose..... | 30 |
+| 9.1.2.4 | Method of test..... | 30 |
+| 9.1.2.4.1 | Initial conditions..... | 30 |
+| 9.1.2.4.2 | Procedures ..... | 30 |
+| 9.1.2.5 | Test requirements..... | 30 |
+| 9.1.3 | Protection of BS receiver in the operating band..... | 33 |
+| 9.1.3.1 | Minimum Requirement..... | 33 |
+| 9.1.4 | Co-existence with services in adjacent frequency bands..... | 33 |
+| 9.1.4.1 | Minimum requirement ..... | 33 |
+| 9.2 | Spurious emissions..... | 33 |
+| 9.2.1 | Definition and applicability ..... | 33 |
+| 9.2.2 | Minimum Requirements..... | 34 |
+| 9.2.2.1 | Spurious emission (Category A)..... | 34 |
+| 9.2.2.2 | Spurious emission (Category B)..... | 34 |
+| 9.2.2.3 | Void ..... | 35 |
+| 9.2.2.4 | Co-existence with other systems in the same geographical area ..... | 35 |
+| 9.2.2.4.1 | Minimum Requirements..... | 36 |
+| 9.2.2.5 | Co-existence with co-located and co-sited base stations ..... | 38 |
+| 9.2.2.5.1 | Minimum Requirements..... | 39 |
+| 9.2.2.6 | Co-existence with PHS ..... | 41 |
+| 9.2.2.6.1 | Minimum requirement..... | 41 |
+| 9.2.2.7 | Co-existence with UTRA-TDD and/or E-UTRA TDD ..... | 41 |
+| 9.2.2.7.1 | Operation in the same geographic area ..... | 41 |
+| 9.2.2.7.2 | Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations ..... | 43 |
+| 9.2.2.8 | (Void)..... | 46 |
+| 9.2.2.9 | Protection of public safety operations ..... | 46 |
+| 9.2.2.9.1 | Minimum Requirement ..... | 46 |
+| 9.2.3 | Test purpose..... | 46 |
+| 9.2.4 | Method of test..... | 46 |
+| 9.2.4.1 | Initial conditions ..... | 46 |
+| 9.2.4.2 | Procedures..... | 46 |
+| 9.2.5 | Test requirements ..... | 47 |
+| 10 | Modulation accuracy..... | 47 |
+| 10.1 | Error vector magnitude..... | 47 |
+| 10.1.1 | Definition and applicability ..... | 47 |
+| 10.1.2 | Minimum Requirements..... | 47 |
+| 10.1.3 | Test purpose..... | 47 |
+| 10.1.4 | Method of test..... | 47 |
+| 10.1.4.1 | Initial conditions ..... | 47 |
+| 10.1.4.2 | Procedure ..... | 47 |
+| 10.1.4.3 | Stimulus EVM effect ..... | 48 |
+| 10.1.5 | Test requirements ..... | 48 |
+| 10.2 | Peak code domain error..... | 48 |
+| 10.2.1 | Definition and applicability ..... | 48 |
+| 10.2.2 | Minimum Requirements..... | 48 |
+| 10.2.3 | Test purpose..... | 48 |
+| 10.2.4 | Method of test..... | 48 |
+| 10.2.4.1 | Initial conditions ..... | 48 |
+| 10.2.4.2 | Procedure ..... | 48 |
+| 10.2.5 | Test requirements ..... | 48 |
+| 10.3 | Relative Code Domain Error (RCDE) for 64QAM modulation ..... | 49 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------------------------------------------|-----------|
+| 10.3.1 | Definition and applicability ..... | 49 |
+| 10.3.2 | Minimum requirement..... | 49 |
+| 10.3.3 | Test purpose..... | 49 |
+| 10.3.4 | Method of test..... | 49 |
+| 10.3.4.1 | Initial conditions ..... | 49 |
+| 10.3.4.2 | Procedure ..... | 49 |
+| 10.3.5 | Test requirements ..... | 49 |
+| 11 | Input intermodulation..... | 49 |
+| 11.1 | Definition and applicability..... | 49 |
+| 11.2 | Minimum Requirements..... | 50 |
+| 11.2.1 | General requirement ..... | 50 |
+| 11.2.2 | Co-location with BS in other systems ..... | 50 |
+| 11.2.3 | Co-existence with other systems ..... | 53 |
+| 11.3 | Test purpose ..... | 56 |
+| 11.4 | Method of test..... | 56 |
+| 11.4.1 | Initial conditions ..... | 56 |
+| 11.4.2 | Procedure ..... | 57 |
+| 11.5 | Test requirements ..... | 57 |
+| 11.5.1 | Mandatory requirement ..... | 57 |
+| 11.5.2 | Co-location with BS in other systems ..... | 57 |
+| 11.5.3 | Co-existence with other systems ..... | 60 |
+| 12 | Output intermodulation ..... | 63 |
+| 12.1 | Definition and applicability..... | 63 |
+| 12.2 | Minimum requirement..... | 64 |
+| 12.3 | Test purpose ..... | 64 |
+| 12.4 | Method of test..... | 64 |
+| 12.4.1 | Initial conditions ..... | 64 |
+| 12.4.2 | Procedures ..... | 64 |
+| 12.5 | Test requirements..... | 64 |
+| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 65 |
+| 13.1 | Definitions and applicability ..... | 65 |
+| 13.2 | Minimum Requirements..... | 65 |
+| 13.3 | Test purpose ..... | 65 |
+| 13.4 | Method of test..... | 65 |
+| 13.4.1 | Initial conditions ..... | 65 |
+| 13.4.2 | Procedure ..... | 65 |
+| 13.4.3 | Test Requirements ..... | 66 |
+| Annex A (informative): | Repeater measurement system set-up ..... | 67 |
+| A.1 | Maximum output power..... | 67 |
+| A.2 | Frequency stability..... | 67 |
+| A.3 | Out of band gain..... | 67 |
+| A.4 | Unwanted emission: Spectrum emission mask..... | 67 |
+| A.5 | Unwanted emission: Spurious emission ..... | 68 |
+| A.6 | Modulation Accuracy: Error Vector Magnitude..... | 68 |
+| A.7 | Modulation Accuracy: Peak Code Domain Error Error and Relative Coder Domain Error ..... | 68 |
+| A.8 | Input inter modulation..... | 69 |
+| A.9 | Output Intermodulation..... | 69 |
+| Annex B (informative): | Derivation of Test Requirements ..... | 70 |
+| Annex C (informative): | Acceptable uncertainty of Test Equipment ..... | 73 |
+| Annex D (informative): | Change History..... | 74 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the Radio Frequency (RF) test methods and Minimum Requirements for UTRA FDD Repeaters. These have been derived from, and are consistent with the UTRA FDD Repeater specifications defined in TS 25.106.
+
+This document establishes the minimum RF characteristics of the UTRA FDD 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 TS 25.104: “UTRA(BS) FDD; Radio transmission and Reception”.
+- [2] 3GPP TS 25.942: “RF system scenarios”.
+- [3] 3GPP TS 25.113 : « Base station EMC ».
+- [4] ITU-R recommendation SM.329: “Unwanted emissions in the spurious domain “.
+- [5] ITU-T recommendation O.153: “Basic parameters for the measurement of error performance at bit rates below the primary rate”.
+- [6] IEC 60721-3-3 (1994): “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”.
+- [8] IEC 60068-2-1 (1990): “Environmental testing – Part 2: Tests. Tests A: Cold”.
+- [9] IEC 60068-2-2 (1974): “Environmental testing – Part 2: Tests. Tests B: Dry heat”.
+- [10] IEC 60068-2-6 (1995): “Environmental testing – Part 2: Tests – Test Fc: Vibration (sinusoidal)”.
+- [11] 3GPP TS 25.141: “Base station conformance testing (FDD)”.
+- [12] 3GPP TS 25.106: “UTRA Repeater; Radio transmission and reception”.
+- [13] 3GPP TS 36.143: “Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater conformance testing”
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Donor coupling loss:** is the coupling loss between the repeater and the donor base station.
+
+**Down-link:** 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.
+
+**Operating band:** the frequency range in which UTRA FDD operates, that is defined with a specific set of technical requirements.
+
+NOTE 1: The operating band(s) for an UTRA Repeater is declared by the manufacturer according to the designations in clause 4.1, Table 4.1.
+
+NOTE 2: Unless specified, operating band refers to the uplink operating band and downlink operating band.
+
+**Pass band:** the pass band is the frequency range in which the Repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal 5 MHz channels. If they are not consecutive each subset of channels shall be considered as an individual pass band. A repeater can have one or several pass bands.
+
+**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).
+
+**Up-link:** signal path where mobile transmits and base station receives.
+
+## 3.2 (void)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|---------|---------------------------------------------|
+| BS | Base Transceiver Station |
+| CW | Continuous Wave (unmodulated signal) |
+| DL | Down Link (forward link) |
+| DTT | Digital Terrestrial Television |
+| EVM | Error Vector Magnitude |
+| FDD | Frequency Division Duplex |
+| FFS | For Further Study |
+| IMT2000 | International Mobile Telecommunication-2000 |
+
+| | |
+|--------|----------------------------------------------|
+| ITU | International Telecommunication Union |
+| MS | Mobile Station |
+| RCDE | Relative Code Domain Error |
+| RF | Radio Frequency |
+| RSS | Root Sum of the Squares |
+| TDD | Time Division Duplex |
+| UARFCN | UTRA Absolute Radio Frequency Channel Number |
+| UL | Up Link (reverse link) |
+| UMTS | Universal Mobile Telecommunication System |
+| UTRA | Universal Terrestrial Radio Access |
+| WCDMA | Wide band Code Division Multiple Access |
+
+# 4 Frequency bands and channel arrangement
+
+## 4.1 Frequency bands
+
+- a) A UTRA/FDD Repeater is designed to operate in one or several pass bands within either of the following paired frequency bands;
+
+**Table 4.1: Frequency bands**
+
+| Operating Band | UL Frequencies | DL frequencies |
+|----------------|-----------------------------|-----------------------------|
+| | UE transmit, Node B receive | UE receive, Node B transmit |
+| I | 1920 – 1980 MHz | 2110 – 2170 MHz |
+| II | 1850 – 1910 MHz | 1930 – 1990 MHz |
+| III | 1710 – 1785 MHz | 1805 – 1880 MHz |
+| IV | 1710 – 1755 MHz | 2110 – 2155 MHz |
+| V | 824 – 849 MHz | 869 – 894 MHz |
+| VI | 830 – 840 MHz | 875 – 885 MHz |
+| VII | 2500 – 2570 MHz | 2620 – 2690 MHz |
+| VIII | 880 – 915 MHz | 925 – 960 MHz |
+| IX | 1749.9 – 1784.9 MHz | 1844.9 – 1879.9 MHz |
+| X | 1710 – 1770 MHz | 2110 – 2170 MHz |
+| XI | 1427.9 – 1452.9 MHz | 1475.9 – 1500.9 MHz |
+| XII | 698 – 716 MHz | 728 – 746 MHz |
+| XIII | 777 – 787 MHz | 746 – 756 MHz |
+| XIV | 788 – 798 MHz | 758 – 768 MHz |
+| XV | Reserved | Reserved |
+| XVI | Reserved | Reserved |
+| XVII | Reserved | Reserved |
+| XVIII | Reserved | Reserved |
+| XIX | 830 – 845 MHz | 875 – 890 MHz |
+| XX | 832 – 862 MHz | 791 – 821 MHz |
+| XXI | 1447.9 – 1462.9 MHz | 1495.9 – 1510.9 MHz |
+| XXII | 3410 – 3490 MHz | 3510 – 3590 MHz |
+| XXV | 1850 – 1915 MHz | 1930 – 1995 MHz |
+
+- b) Deployment in other frequency bands is not precluded.
+
+## 4.2 TX – RX frequency separation
+
+- a) A UTRA/FDD repeaters is designed to operate with the following TX to RX frequency separation
+
+**Table 4.2: TX-RX frequency separation**
+
+| Operating Band | TX-RX frequency separation |
+|----------------|----------------------------|
+| I | 190 MHz |
+| II | 80 MHz |
+| III | 95 MHz |
+| IV | 400 MHz |
+| V | 45 MHz |
+| VI | 45 MHz |
+| VII | 120 MHz |
+| VIII | 45 MHz |
+| IX | 95 MHz |
+| X | 400 MHz |
+| XI | 48 MHz |
+| XII | 30 MHz |
+| XIII | 31 MHz |
+| XIV | 30 MHz |
+| XIX | 45 MHz |
+| XX | 41 MHz |
+| XXI | 48 MHz |
+| XXII | 100 MHz |
+| XXV | 80 MHz |
+
+- b) A UTRA/FDD Repeater can support both fixed and variable up-link to down-link frequency separation.
+- c) The use of other up-link to down-link frequency separations in existing or other frequency bands shall not be precluded.
+
+## 4.3 Channel arrangement
+
+### 4.3.1 Channel spacing
+
+The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario.
+
+### 4.3.2 Channel raster
+
+The channel raster is 200 kHz for all bands, which means that the centre frequency must be an integer multiple of 200 kHz. In addition a number of additional centre frequencies are specified according to the table 4.4, which means that the centre frequencies for these channels are shifted 100 kHz relative to the general raster.
+
+### 4.3.3 Channel number
+
+The carrier frequency is designated by the UTRA Absolute Radio Frequency Channel Number (UARFCN).
+
+For each operating band, the UARFCN values are defined as follows.
+
+Uplink: $N_U = 5 * (F_{UL} - F_{UL\_offset})$ , for the carrier frequency range $F_{UL\_low} \leq F_{UL} \leq F_{UL\_high}$
+
+Downlink: $N_D = 5 * (F_{DL} - F_{DL\_offset})$ , for the carrier frequency range $F_{DL\_low} \leq F_{DL} \leq F_{DL\_high}$
+
+For each operating Band, $F_{UL\_offset}$ , $F_{UL\_low}$ , $F_{UL\_high}$ , $F_{DL\_offset}$ , $F_{DL\_low}$ and $F_{DL\_high}$ are defined in Table 4.3 for the general UARFCN. For the additional UARFCN, $F_{UL\_offset}$ , $F_{DL\_offset}$ and the specific $F_{UL}$ and $F_{DL}$ are defined in Table 4.4.
+
+**Table 4.3: UARFCN definition (general)**
+
+| Band | UPLINK (UL) | | | DOWNLINK (DL) | | |
+|------|-----------------------------------------------------|--------------------------------------------------|----------------------|-----------------------------------------------------|--------------------------------------------------|----------------------|
+| | UE transmit, Node B receive | | | UE receive, Node B transmit | | |
+| | UARFCN formula offset F UL _Offset [MHz] | Carrier frequency (F UL ) range [MHz] | | UARFCN formula offset F DL _Offset [MHz] | Carrier frequency (F DL ) range [MHz] | |
+| | | F UL low | F UL high | | F DL low | F DL high |
+| I | 0 | 1922.4 | 1977.6 | 0 | 2112.4 | 2167.6 |
+| II | 0 | 1852.4 | 1907.6 | 0 | 1932.4 | 1987.6 |
+| III | 1525 | 1712.4 | 1782.6 | 1575 | 1807.4 | 1877.6 |
+| IV | 1450 | 1712.4 | 1752.6 | 1805 | 2112.4 | 2152.6 |
+| V | 0 | 826.4 | 846.6 | 0 | 871.4 | 891.6 |
+| VI | 0 | 832.4 | 837.6 | 0 | 877.4 | 882.6 |
+| VII | 2100 | 2502.4 | 2567.6 | 2175 | 2622.4 | 2687.6 |
+| VIII | 340 | 882.4 | 912.6 | 340 | 927.4 | 957.6 |
+| IX | 0 | 1752.4 | 1782.4 | 0 | 1847.4 | 1877.4 |
+| X | 1135 | 1712.4 | 1767.6 | 1490 | 2112.4 | 2167.6 |
+| XI | 733 | 1430.4 | 1450.4 | 736 | 1478.4 | 1498.4 |
+| XII | -22 | 700.4 | 713.6 | -37 | 730.4 | 743.6 |
+| XIII | 21 | 779.4 | 784.6 | -55 | 748.4 | 753.6 |
+| XIV | 12 | 790.4 | 795.6 | -63 | 760.4 | 765.6 |
+| XIX | 770 | 832.4 | 842.6 | 735 | 877.4 | 887.6 |
+| XX | -23 | 834.4 | 859.6 | -109 | 793.4 | 818.6 |
+| XXI | 1358 | 1450.4 | 1460.4 | 1326 | 1498.4 | 1508.4 |
+| XXII | 2525 | 3412.4 | 3487.6 | 2580 | 3512.4 | 3587.6 |
+| XXV | 875 | 1852.4 | 1912.6 | 910 | 1932.4 | 1992.6 |
+
+**Table 4.4: UARFCN definition (additional channels)**
+
+| Band | UPLINK (UL)
UE transmit, Node B receive | | DOWNLINK (DL)
UE receive, Node B transmit | |
+|------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| | UARFCN
formula offset
$F_{UL\_Offset}$ [MHz] | Carrier frequency [MHz]
(F UL ) | UARFCN
formula offset
$F_{DL\_Offset}$ [MHz] | Carrier frequency [MHz]
(F DL ) |
+| I | - | - | - | - |
+| II | 1850.1 | 1852.5, 1857.5, 1862.5,
1867.5, 1872.5, 1877.5,
1882.5, 1887.5, 1892.5,
1897.5, 1902.5, 1907.5 | 1850.1 | 1932.5, 1937.5, 1942.5,
1947.5, 1952.5, 1957.5,
1962.5, 1967.5, 1972.5,
1977.5, 1982.5, 1987.5 |
+| III | - | - | - | - |
+| IV | 1380.1 | 1712.5, 1717.5, 1722.5,
1727.5, 1732.5, 1737.5,
1742.5, 1747.5, 1752.5 | 1735.1 | 2112.5, 2117.5, 2122.5,
2127.5, 2132.5, 2137.5,
2142.5, 2147.5, 2152.5 |
+| V | 670.1 | 826.5, 827.5, 831.5,
832.5, 837.5, 842.5 | 670.1 | 871.5, 872.5, 876.5,
877.5, 882.5, 887.5 |
+| VI | 670.1 | 832.5, 837.5 | 670.1 | 877.5, 882.5 |
+| VII | 2030.1 | 2502.5, 2507.5, 2512.5,
2517.5, 2522.5, 2527.5,
2532.5, 2537.5, 2542.5,
2547.5, 2552.5, 2557.5,
2562.5, 2567.5 | 2105.1 | 2622.5, 2627.5, 2632.5,
2637.5, 2642.5, 2647.5,
2652.5, 2657.5, 2662.5,
2667.5, 2672.5, 2677.5,
2682.5, 2687.5 |
+| VIII | - | - | - | - |
+| IX | - | - | - | - |
+| X | 1075.1 | 1712.5, 1717.5, 1722.5,
1727.5, 1732.5, 1737.5,
1742.5, 1747.5, 1752.5,
1757.5, 1762.5, 1767.5 | 1430.1 | 2112.5, 2117.5, 2122.5,
2127.5, 2132.5, 2137.5,
2142.5, 2147.5, 2152.5,
2157.5, 2162.5, 2167.5 |
+| XI | - | - | - | - |
+| XII | -39.9 | 700.5, 701.5, 706.5,
707.5, 712.5, 713.5 | -54.9 | 730.5, 731.5, 736.5, 737.5,
742.5, 743.5 |
+| XIII | 11.1 | 779.5, 784.5 | -64.9 | 748.5, 753.5 |
+| XIV | 2.1 | 790.5, 795.5 | -72.9 | 760.5, 765.5 |
+| XIX | 755.1 | 832.5, 837.5, 842.5 | 720.1 | 877.5, 882.5, 887.5 |
+| XX | - | - | - | - |
+| XXI | - | - | - | - |
+| XXII | - | - | - | - |
+| XXV | 810.1 | 1852.5, 1857.5, 1862.5,
1867.5, 1872.5, 1877.5,
1882.5, 1887.5, 1892.5,
1897.5, 1902.5, 1907.5,
1912.5 | 845.1 | 1932.5, 1937.5, 1942.5,
1947.5, 1952.5, 1957.5,
1962.5, 1967.5, 1972.5,
1977.5, 1982.5, 1987.5,
1992.5 |
+
+# 5 General test conditions and declarations
+
+This specification applies only to UTRA/FDD Repeater.
+
+The requirements of this clause apply to all applicable tests in this specification. Many of the tests in this specification measure a parameter relative to a value, that is not fully specified in the UTRA specifications. For these tests, the Minimum Requirement is determined relative to a nominal value specified by the manufacturer.
+
+Some requirements for the Repeater may be regional as listed in subclause 5.6.
+
+When specified in a test, the manufacturer shall declare the nominal value of a parameter, or whether an option is supported.
+
+Schematic drawings for the individual measurement set-up can be found in the Annex.
+
+## 5.1 Acceptable uncertainty of Test System
+
+The maximum acceptable uncertainty of the Test System is specified below for each test, where appropriate. The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance, and 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.
+
+For RF test it should be noted that the uncertainties in subclause 5.1 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System.
+
+### 5.1.1 Measurements of test environments
+
+The measurement accuracy of the Repeater test environments defined in Subclause 5.4, Test environments shall be.
+
+| | |
+|----------------------|--------------|
+| Pressure: | ± 5 kPa. |
+| Temperature: | ± 2 degrees. |
+| Relative Humidity: | ± 5 %. |
+| DC Voltage: | ± 1,0 %. |
+| AC Voltage: | ± 1,5 %. |
+| Vibration: | 10 %. |
+| Vibration frequency: | 0,1 Hz. |
+
+The above values shall apply unless the test environment is otherwise controlled and the specification for the control of the test environment specifies the uncertainty for the parameter.
+
+### 5.1.2 Measurements of Repeater
+
+**Table 5.1: Maximum Test System Uncertainty**
+
+| Subclause | Maximum Test System Uncertainty | Range over which Test System Uncertainty applies |
+|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| 6.1 Maximum output power | ±0,7 dB, $f \leq 3,0$ GHz
±1,0 dB, 3,0 GHz $< f \leq 4,2$ GHz | |
+| 7 Frequency error | ±12 Hz | Measurement results of ± 500 Hz |
+| 8 Out of band gain | ±0,5 dB, $f \leq 3,0$ GHz
±0,8 dB, 3,0 GHz $< f \leq 19,0$ GHz
Calibration of test set-up shall be made without D.U.T. in order to achieve the accuracy | |
+| 9.1.2 Operating band unwanted emissions (except 9.1.3) | ±1,5 dB, $f \leq 3,0$ GHz
±1,8 dB, 3,0 GHz $< f \leq 4,2$ GHz
Due to carrier leakage for measurements specified in a 1MHz bandwidth close to the carrier (4 MHz to 8 MHz), integration of the measurement using several narrower bandwidth measurements may be necessary in order to achieve the above accuracy.
The interference from the signal generator ACLR shall be minimum 10 dB below that of a Base Station according to toTS25.141 | |
+| 9.1.3 Protection of BS receiver in the operating band | for results > -60 dBm ±2,0 dB
for results < -60 dBm ±3,0 dB | |
+| 9.2 Spurious emissions | In UTRA and coexistence receive bands:
for results > -60 dBm ±2,0 dB
for results < -60 dBm ±3,0 dB
Outside above range:
emission power
$f \leq 2,2$ GHz ±1,5 dB;
2,2 GHz $< f \leq 4$ GHz ±2,0 dB;
4 GHz $< f \leq 19$ GHz ±4,0 dB.
The interference from the signal generator ACLR shall be minimum 10 dB below that of a Base Station according to toTS25.141 | |
+| 10.1 Error vector magnitude | ± 2,5 % (single code applied)
(±2,5 % measurement error for single code).
5,0 % EVM in the stimulus signal (single code) will shift the EVM maximum value 0,7% to 18,2%.
(RSS repeater EVM and Stimulus EVM.) | Measurement results from 12,5% to 22,5% at signal power = $P\_max - 3$ dB to $P\_max - 18$ dB |
+| 10.2 Peak code domain error | ±1,1dB
Formula: RSS measurement error and impedance mismatch error
(using ±1,0 dB measurement error and ±0,5 dB impedance mismatch error (stimulus side) assuming 14 dB return loss) | Measurement results from – 36 dB to – 30 dB, at signal power = $P\_max - 3$ dB to $P\_max - 18$ dB |
+| 10.3 Relative Code Domain Error | 1.7 dB
Formula: Linear addition of the stimulus relative error power, analyser relative error power and repeater relative error power.normalised to repeater relative error power and expressed in dB.
-27dB RCDE in the stimulus signal and -27dB RCDE from the analyser and -21 dB repeater minimum requirement is assumed. | Measurements in the range -18 to - 21 dB at signal power = Pmax |
+| 11 Input intermodulation Characteristics | ±1,2 dB
Formula: RSS CW1 level error, 2 x CW2 level error, and measurement error (using all errors = ±0,5 dB) | |
+
+| | | |
+|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| 12 Output Intermodulation | dB Spectrum emission
Formula: RSS 2x Interference signal level error and Spectrum emission measurement level error. (1 dB interference signal level error is assumed.)
Due to carrier leakage for measurements specified in a 1MHz bandwidth close to the carrier (4 MHz to 8 MHz), integration of the measurement using several narrower bandwidth measurements may be necessary in order to achieve the above accuracy.
The interference from the signal generator ACLR shall be minimum 10 dB below that of a Base Station
For spurious emission:
In UTRA and coexistence receive bands:
for results dBm dB
for results dBm dB
Outside above range:
emission power
GHz dB;
GHz GHz dB;
GHz GHz dB.
The interference signal must have a spurious emission level at least 10 dB below the spurious levels required in 9.2.
| |
+| 13 Adjacent Channel Rejection Ratio | $\pm 0,7$ dB | |
+
+## 5.2 Repeater test tolerances (informative)
+
+The Test Tolerances defined in this subclause have been used to relax the Minimum Requirements in this specification to derive the Test Requirements.
+
+The Test Tolerances are derived from Test System uncertainties, regulatory requirements and criticality to system performance. As a result, the Test Tolerances may sometimes be set to zero.
+
+The test tolerances should not be modified for any reason e.g. to take account of commonly known test system errors (such as mismatch, cable loss, etc.)
+
+**Table 5.2: Test Tolerance**
+
+| Subclause | Test Tolerance (Note 1) | Notes |
+|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| 6.1 Maximum output power | 0,7 dB | |
+| 9.1.2 Operating band unwanted emissions | 1,5 dB | 0 dB test tolerance for the additional Band II, IV, V, X, XII, XIII and XIV requirements |
+| 9.2 Spurious emissions | 0 dB | |
+| 7 Frequency error | 12 Hz | |
+| 10.1 Error vector magnitude | 0 % | Target value is shifted due to stimulus EVM |
+| 10.2 Peak code domain error | 1,1 dB | |
+| 10.3 Relative Code Domain Error | 1,7 dB | |
+| 8 Out of band gain | 0,5dB | |
+| 11 Input intermodulation Characteristics | 1,2dB | |
+| 12 Output intermodulation | 1,5 dB for spectrum emission
0 dB for spurious emission | |
+| 13 Adjacent Channel Rejection Ratio | 0,7 dB | |
+| NOTE 1: Unless otherwise stated, The Test Tolerances are applied to the DUT Minimum Requirement. See Annex B. | | |
+
+## 5.3 Interpretation of measurement results
+
+The measurement results returned by the Test System are compared – without any modification – against the Test Requirements as defined by the share risk principle.
+
+The share risk principle is defined in ETR 273 Part 1 sub-part 2 section 6.5.
+
+The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report.
+
+The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in subclause 5.1 of this specification.
+
+If the Test System for a test is known to have a measurement uncertainty greater than that specified in subclause 5.1, it is still permitted to use this apparatus provided that an adjustment is made as follows.
+
+Any additional uncertainty in the Test System over and above that specified in subclause 5.1 shall be used to tighten the Test Requirement-making the test harder to pass. (For some tests e.g. receiver test, this may require modification of stimulus signals). This procedure will ensure that a Test System not compliant with subclause 5.1 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with subclause 5.1 had been used.
+
+## 5.4 Test Environment
+
+For each test in the present document, the environmental conditions under which the Repeater is to be tested are defined.
+
+### 5.4.1 Normal test environment
+
+When a normal test environment is specified for a test, the test should be performed within the minimum and maximum limits of the conditions stated in Table 5.3.
+
+**Table 5.3: Limits of conditions for Normal Test Environment**
+
+| Condition | Minimum | Maximum |
+|---------------------|------------------------------------------|---------|
+| Barometric pressure | 86 kPa | 106 kPa |
+| Temperature | 15°C | 30°C |
+| Relative Humidity | 20 % | 85 % |
+| Power supply | Nominal, as declared by the manufacturer | |
+| Vibration | Negligible | |
+
+The ranges of barometric pressure, temperature and humidity represent the maximum variation expected in the uncontrolled environment of a test laboratory. If it is not possible to maintain these parameters within the specified limits, the actual values shall be recorded in the test report.
+
+NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site.
+
+### 5.4.2 Extreme test environment
+
+The manufacturer shall declare one of the following:
+
+- 1) the equipment class for the equipment under test, as defined in the IEC 60 721-3-3 [6];
+- 2) the equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [7];
+- 3) the equipment that does not comply to the mentioned classes, the relevant classes from IEC 60 721 [6], [7] documentation for Temperature, Humidity and Vibration shall be declared.
+
+NOTE: Reduced functionality for conditions that fall out side of the standard operational conditions are not tested in the present document. These may be stated and tested separately.
+
+#### 5.4.2.1 Extreme temperature
+
+When an extreme temperature test environment is specified for a test, the test shall be performed at the standard minimum and maximum operating temperatures defined by the manufacturer's declaration for the equipment under test.
+
+##### Minimum temperature:
+
+The test shall be performed with the environment test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-1 [8].
+
+##### Maximum temperature:
+
+The test shall be performed with the environmental test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-2 [9].
+
+NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature.
+
+### 5.4.3 Vibration
+
+When vibration conditions are specified for a test, the test shall be performed while the equipment is subjected to a vibration sequence as defined by the manufacturer's declaration for the equipment under test. This shall use the environmental test equipment and methods of inducing the required environmental phenomena in to the equipment, conforming to the test procedure of IEC 60 068-2-6 [10]. Other environmental conditions shall be within the ranges specified in subclause 5.4.1.
+
+NOTE: The higher levels of vibration may induce undue physical stress in to equipment after a prolonged series of tests. The testing body should only vibrate the equipment during the RF measurement process.
+
+### 5.4.4 Power supply
+
+When extreme power supply conditions are specified for a test, the test shall be performed at the standard upper and lower limits of operating voltage defined by manufacturer's declaration for the equipment under test.
+
+#### Upper voltage limit:
+
+The equipment shall be supplied with a voltage equal to the upper limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [8] Test Ab/Ad and IEC 60 068-2-2 [9] Test Bb/Bd: Dry Heat.
+
+#### Lower voltage limit:
+
+The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [8] Test Ab/Ad and IEC 60 068-2-2 [9] Test Bb/Bd: Dry Heat.
+
+## 5.5 Selection of configurations for testing
+
+Most tests in the present document are only performed for a subset of the possible combinations of test conditions. For instance:
+
+- only one RF channel may be specified to be tested;
+- only one timeslot may be specified to be tested.
+
+When a test is performed by a test laboratory, the choice of which combinations are to be tested shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies.
+
+When a test is performed by a manufacturer, the choice of which combinations are to be tested may be specified by an operator.
+
+## 5.6 Regional requirements
+
+Some requirements in TS 25.143 may only apply in certain regions. Table 5.4 lists all requirements that may be applied differently in different regions.
+
+**Table 5.4: List of regional requirements**
+
+| Sub-clause number | Requirement | Comments |
+|-------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 4.1 | Frequency bands | Some bands may be applied regionally. |
+| 4.2 | TX – RX frequency separation | The requirement is applied according to what frequency bands in clause 4.1 that are supported by the Repeater. |
+| 4.3 | Channel arrangement | The requirement is applied according to what frequency bands in clause 4.1 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 ranges of conditions defined as normal. |
+| 9.1.2 | Operating band unwanted emissions | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. |
+| 9.2.2.1 | Spurious emissions (Category A) | These requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. |
+| 9.2.2.2 | Spurious emissions (Category B) | These requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. |
+| 9.2.2.4 | Spurious emissions: Co-existence with other systems in the same geographical area | These requirements may apply in geographic areas in which both UTRA FDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. |
+| 9.2.2.5 | Spurious emissions: Co-existence with co-located and co-sited base stations | These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band are co-located with a UTRA FDD Repeater. |
+| 9.2.2.6 | Spurious emissions: Co-existence with PHS | This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA FDD Repeaters are deployed. |
+| 9.2.2.7.1 | Spurious emissions: Co-existence with UTRA TDD and/or E-UTRA TDD -Operation in the same geographic area | This requirement may be applied for the protection of UTRA UE in geographic areas in which both UTRA TDD BS and UTRA FDD Repeaters are deployed. |
+| 9.2.2.7.2 | Spurious emissions: Co-existence with UTRA TDD and/or E-UTRA TDD – Co-location | This requirement may be applied for the protection of UTRA TDD BS receivers when UTRA TDD BS and UTRA FDD Repeaters are co-located. |
+| 9.2.2.9 | Spurious emissions: Protection of public safety operations | This requirement shall be applied to Repeater operating in Bands XIII and XIV to ensure that appropriate interference protection is provided to 700 MHz public safety operations. |
+| 11.2.2 | Input intermodulation: Co-location with BS in other systems | The requirement may be applied when GSM 900, DCS 1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band and UTRA-FDD Repeaters are co-located. |
+| 11.2.3 | Input Intermodulation: Co-existence with other systems | These requirements may apply in geographic areas in which both UTRA FDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. |
+
+## 5.7 Test Models
+
+The set-up of physical channels for the Repeater tests shall be according to one of the test models described in TS 25.141 [11]. A reference to the applicable test model in TS 25.141 is made for each test in Table 5.5 by referring to the test model number as it appears in TS 25.141.
+
+These test models shall be used in the tests of both the up-link and the down-link directions of the Repeater unless otherwise stated.
+
+**Table 5.5: List of the applicable test models**
+
+| Test model number in TS 25.141 | Requirement | Comments |
+|--------------------------------|----------------------------|----------|
+| Test Model 1 | Repeater output power | |
+| Test Model 1 | Out of band emission | |
+| Test Model 1 | Spurious emission | |
+| Test Model 1 | Error vector magnitude | |
+| Test Model 3 | Peak code domain error | |
+| Test Model 6 | Relative code domain error | |
+
+## 5.8 Format and interpretation of tests
+
+Each test in the following clauses has a standard format:
+
+# **X Title**
+
+All tests are applicable to all equipment within the scope of the present document, unless otherwise stated.
+
+## **X.1 Definition and applicability**
+
+This subclause gives the general definition of the parameter under consideration and specifies whether the test is applicable to all equipment or only to a certain subset.
+
+## **X.2 Minimum Requirements**
+
+This subclause is an informative copy of the Minimum Requirement defined by the core specification.
+
+In addition, this subclause contains the reference to the subclause to the 3GPP reference (or core) specification which defines the Minimum Requirement.
+
+## **X.3 Test purpose**
+
+This subclause defines the purpose of the test.
+
+## **X.4 Method of test**
+
+### **X.4.1 Initial conditions**
+
+This subclause defines the initial conditions for each test, including the basic measurement set-up.
+
+### **X.4.2 Procedure**
+
+This subclause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. antenna port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging).
+
+## **X.5 Test Requirements**
+
+This subclause defines the pass/fail criteria for the equipment under test. See subclause 5.3 Interpretation of measurement results.
+
+## 5.9 Repeater configurations
+
+### 5.9.1 Power supply options
+
+If the repeater is supplied with a number of different power supply configurations, it may not be necessary to test RF parameters for each of the power supply options, provided that it can be demonstrated that the range of conditions over which the equipment is tested is at least as great as the range of conditions due to any of the power supply configurations.
+
+### 5.9.2 Combining of Repeaters
+
+If the repeater is intended for combination with additional apparatus connected to a repeater port and this combination is supplied as a system, the combination of repeater together with the additional apparatus shall also fulfil the repeater requirements. E.g. if the repeater is intended for combination such that multiple repeaters amplify the same signals into the same ports the combination shall also fulfil the repeater requirements.
+
+An example of such a configuration is shown in figure 5.1
+
+
+
+Figure 5.1: Example of repeater configuration. The diagram shows a signal path starting from a 'Test port' on the left, entering a 'Combiner / Splitter' box. The output of this box splits into two parallel 'Repeater' boxes. The outputs of these two repeaters are combined in a second 'Combiner / Splitter' box, which then connects to another 'Test port' on the right. Vertical dashed lines labeled 'Antenna connector' are positioned between the first combiner/splitter and the repeaters, and between the repeaters and the second combiner/splitter.
+
+Figure 5.1: Example of repeater configuration
+
+# 6 Output power
+
+Maximum output power, $P_{max}$ , 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
+
+### 6.1.1 Definition and applicability
+
+Maximum output power, $P_{max}$ , of the Repeater is the mean power level per carrier measured at the antenna connector in specified reference condition.
+
+### 6.1.2 Minimum Requirements
+
+In normal conditions as specified in section 5.4.1, 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 43$ dBm | +2 dB and -2 dB |
+| $39 \leq P < 43$ dBm | +2 dB and -2 dB |
+| $31 \leq P < 39$ dBm | +2 dB and -2 dB |
+| $P < 31$ dBm | +3 dB and -3 dB |
+
+In extreme conditions as specified in section 5.4.2 and 5.4.4, the Repeater maximum output power shall remain within 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 43$ dBm | +2,5 dB and -2,5 dB |
+| $39 \leq P < 43$ dBm | +2,5 dB and -2,5 dB |
+| $31 \leq P < 39$ 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 defined for the Normal test environment in subclause 5.4.1.
+
+### 6.1.3 Test purpose
+
+To verify that the Repeater maximum output power is within the limit specified in 6.1.2.
+
+### 6.1.4 Method of test
+
+#### 6.1.4.1 Initial conditions
+
+- 1) Set-up the equipment as shown in annex A.
+- 2) Connect the signal generator equipment to the Repeater input port.
+- 3) Connect the power measuring equipment to the Repeater output port.
+
+#### 6.1.4.2 Procedure
+
+- 1) Set the signal generator to transmit a signal modulated with a combination of PCCPCH, SCCPCH and Dedicated Physical Channels specified as test model 1 in TS 25.141.
+- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain.
+- 3) Measure the mean power at the RF output port over a certain slot.
+- 4) Increase the power with 10 dB compare to the level obtained in step 2.
+- 5) Measure the mean power at the RF output port over a certain slot.
+
+In addition, on one UARFCN only, the test shall be performed under extreme power supply as defined in subclause 5.4.4
+
+NOTE: Tests under extreme power supply also test extreme temperature.
+
+### 6.1.5 Test Requirements
+
+In normal conditions as specified in section 5.4.1, the Repeater maximum output power shall remain within limits specified in Table 6.3 relative to the manufacturer's rated output power.
+
+**Table 6.3: Repeater output power; normal conditions**
+
+| Rated output power | Carrier frequency | Limit |
+|----------------------|------------------------------|---------------------|
+| $P \geq 43$ dBm | $f \leq 3,0$ GHz | +2,7 dB and -2,7 dB |
+| | $3,0$ GHz $< f \leq 4,2$ GHz | +3,0 dB and -3,0 dB |
+| $39 \leq P < 43$ dBm | $f \leq 3,0$ GHz | +2,7 dB and -2,7 dB |
+| | $3,0$ GHz $< f \leq 4,2$ GHz | +3,0 dB and -3,0 dB |
+| $31 \leq P < 39$ dBm | $f \leq 3,0$ GHz | +2,7 dB and -2,7 dB |
+| | $3,0$ GHz $< f \leq 4,2$ GHz | +3,0 dB and -3,0 dB |
+| $P < 31$ dBm | $f \leq 3,0$ GHz | +3,7 dB and -3,7 dB |
+| | $3,0$ GHz $< f \leq 4,2$ GHz | +4,0 dB and -4,0 dB |
+
+In extreme conditions as specified in section 5.4.2 and 5.4.4, the Repeater maximum output power shall remain within limits specified in Table 6.4 relative to the manufacturer's rated output power.
+
+**Table 6.4: Repeater output power; extreme conditions**
+
+| Rated output power | Carrier frequency | Limit |
+|------------------------------|--------------------------------------------|---------------------|
+| $P \geq 43 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +3,2 dB and -3,2 dB |
+| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +3,5 dB and -3,5 dB |
+| $39 \leq P < 43 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +3,2 dB and -3,2 dB |
+| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +3,5 dB and -3,5 dB |
+| $31 \leq P < 39 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +3,2 dB and -3,2 dB |
+| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +3,5 dB and -3,5 dB |
+| $P < 31 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +4,7 dB and -4,7 dB |
+| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +5,0 dB and -5,0 dB |
+
+In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges defined for the Normal test environment in subclause 5.4.1.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non zero. The Test Tolerance for this test is defined in subclause 5.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex B.
+
+# 7 Frequency stability
+
+Frequency error is the measure of the difference between the frequency of the received signal and the frequency of the re-transmitted signal.
+
+## 7.1 Definition and applicability
+
+The frequency stability is a measure of the frequency deviation of the output signal with respect to the input signal. The test shall address the uplink and the downlink path of the Repeater.
+
+## 7.2 Minimum Requirement
+
+In normal conditions as specified in section 5.4.1 the frequency deviation shall be within $\pm 0,01 \text{ ppm}$ .
+
+## 7.3 Test purpose
+
+To verify that the Frequency Error is within the limit specified in 7.2.
+
+## 7.4 Method of test
+
+### 7.4.1 Initial conditions
+
+- 1) Set-up the equipment as shown in annex A.
+- 2) Connect the cw signal generator equipment to the Repeater input port.
+- 3) Connect the frequency counter to the Repeater output port. Both the signal generator and the frequency counter shall use the same reference frequency.
+- 4) Adjust the input power to the Repeater to create the maximum nominal Repeater output power as declared by the manufacturer at maximum gain.
+
+### 7.4.2 Procedure
+
+Measure the frequency error for both paths uplink and downlink of the Repeater.
+
+## 7.5 Test requirements
+
+The measurement result of 7.4.2 shall not exceed:
+
+$$| f_{IN} - f_{out} | \leq (f_{out} * 0,01 \text{ ppm}) + 12 \text{ Hz}$$
+
+# 8 Out of band gain
+
+## 8.1 Definitions and applicability
+
+Out of band gain refers to the gain of the Repeater immediately outside the pass band. The measurements shall apply to both paths uplink and downlink of the Repeater.
+
+## 8.2 Minimum Requirements
+
+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.
+
+In normal conditions as specified in section 5.4.1 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 5 MHz channel within the pass band.
+
+**Table 8.1: Out of band gain limits 1**
+
+| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain |
+|----------------------------------------------------------|--------------|
+| $2,7 \leq f\_offset < 3,5 \text{ MHz}$ | 60 dB |
+| $3,5 \leq f\_offset < 7,5 \text{ MHz}$ | 45 dB |
+| $7,5 \leq f\_offset < 12,5 \text{ MHz}$ | 45 dB |
+| $12,5 \text{ MHz} \leq f\_offset$ | 35 dB |
+
+For $12,5 \text{ 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 \text{ dBm}$ | Out of band gain $\leq$ minimum donor coupling loss |
+| $31 \text{ dBm} \leq P < 43 \text{ dBm}$ | Out of band gain $\leq$ minimum donor coupling loss |
+| $P \geq 43 \text{ dBm}$ | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) |
+| Note: | The out of band gain is considered with $12,5 \text{ MHz} \leq f\_offset$ |
+
+## 8.3 Test purpose
+
+The purpose of this test is to verify that the Repeater meets the out of band gain requirements as specified in TS 25.106.
+
+## 8.4 Method of test
+
+### 8.4.1 Initial conditions
+
+Set-up the equipment as shown in annex A.
+
+The test shall be performed with an offset between CW-signal and the first or last 5 MHz channel within the pass band of 2,7 MHz, 3 MHz, 3,5 MHz, 5 MHz, 7,5 MHz, 10 MHz, 12,5 MHz, 15 MHz and 20 MHz, excluding other pass
+
+bands. In addition the test shall also be performed for all harmonic frequencies of the repeaters pass band up to 12,75 GHz, for operating bands $f \leq 3,0\text{GHz}$ , or up to the 5th harmonic of the upper frequency edge of the DL or UL operating band, for operating bands $f > 3,0\text{GHz}$ .
+
+### 8.4.2 Procedure
+
+- 1) Set the Repeater to maximum gain.
+- 2) Set the signal generator to generate a CW-signal, applied to the input port of the Repeater. The power level of the RF input signal shall be at least 5 dB below the power level which, when applied within the pass band, would produce the maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range.
+- 3) The average output power in each case shall be measured using a spectrum analyser connected to the output port of the Repeater and the net gain shall be recorded compared to table 8.3 or table 8.4 whichever is lower.
+- 4) With the same input power as in step 1) set the repeater gain to the minimum specified by the manufacturer.
+- 5) The average output power in each case shall be measured using a spectrum analyser connected to the output port of the Repeater and the net gain shall be recorded and compared to table 8.3 or table 8.4 whichever is lower.
+
+## 8.5 Test requirements
+
+**Table 8.3: Out of band gain limits**
+
+| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain |
+|----------------------------------------------------------|--------------|
+| $2,7 \leq f\_offset < 3,5\text{ MHz}$ | 60,5 dB |
+| $3,5 \leq f\_offset < 7,5\text{ MHz}$ | 45,5 dB |
+| $7,5 \leq f\_offset < 12,5\text{ MHz}$ | 45,5 dB |
+| $12,5\text{ MHz} \leq f\_offset$ | 35,5 dB |
+
+**Table 8.4: Out of band gain limits 2**
+
+| Repeater maximum output power as in 9.1.1.1 | Carrier frequency | Maximum gain |
+|---------------------------------------------|------------------------------------------|--------------------------------------------------------------------------|
+| $P < 31\text{ dBm}$ | $f \leq 3,0\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB |
+| | $3,0\text{ GHz} < f \leq 4,2\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,8 dB |
+| $31\text{ dBm} \leq P < 43\text{ dBm}$ | $f \leq 3,0\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB |
+| | $3,0\text{ GHz} < f \leq 4,2\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,8 dB |
+| $P \geq 43\text{ dBm}$ | $f \leq 3,0\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) + 0,5 dB |
+| | $3,0\text{ GHz} < f \leq 4,2\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) + 0,8 dB |
+
+NOTE: The donor coupling loss is considered with $12,5\text{ MHz} \leq f\_offset$
+
+# 9 Unwanted emission
+
+Unwanted emissions consist of out-of-band emissions and spurious emissions [4]. Out of band emissions are unwanted emissions immediately outside the pass band bandwidth resulting from the modulation process and non-linearity in the transmitter, but excluding 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.
+
+The out-of-band emissions requirement for repeater is specified both in terms operating band unwanted emissions and protection of the BS receiver in the operating band. The Operating band unwanted emissions define all unwanted emissions in the repeater operating band plus the frequency ranges 10 MHz above and 10 MHz below that band. Unwanted emissions outside of this frequency range are limited by a spurious emissions requirement.
+
+## 9.1 Out of band emission
+
+### 9.1.1 Void
+
+### 9.1.2 Operating band unwanted emissions
+
+#### 9.1.2.1 Definitions and applicability
+
+Operating band unwanted emissions comprise an emission mask applied outside the repeater passband and a general requirement applied outside the mask but inside the frequency range of the operating band unwanted emissions.
+
+The general operating band unwanted emissions limits are given in table 9.0.
+
+**Table 9.0: General operating band unwanted emissions requirements**
+
+| Frequency range of operating band | Category A | Category B | Measurement bandwidth | Notes |
+|-----------------------------------|------------|------------|-----------------------|-------|
+| $\leq 1$ GHz | -13 dBm | -16 dBm | 100 kHz | 1,2 |
+| $\geq 1$ GHz | -13 dBm | -15 dBm | 1 MHz | 2,3 |
+
+NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1
+
+NOTE 2: Limit based on ITU-R Recommendation SM.329 [4], s4.3 and Annex 7
+
+NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1. Upper frequency as in ITU-R SM.329 [4], s2.5 table 1
+
+The masks defined in Table 9.1, Table 9.2, Table 9.3, and Table 9.4 below may be mandatory in certain regions. In other regions this mask may not be applied.
+
+#### 9.1.2.2 Minimum Requirements
+
+For regions where this clause applies, the requirement shall be met by a repeater's RF-signal output at maximum gain with WCDMA signals in the pass band of the Repeater, at levels that produce the maximum rated output power per channel. In normal conditions as specified in section 5.4.1 emissions shall not exceed the maximum level specified in Table 9.1, Table 9.2, Table 9.3, and Table 9.4 for the appropriate Repeater maximum output power, in the frequency range from $\Delta f = 2,5$ MHz to $\Delta f_{\max}$ from the 5 MHz channel, where:
+
+- $\Delta f$ is the separation between the centre frequency of first or last 5 MHz channel used in the pass band and the nominal -3 dB point of the measuring filter closest to the carrier frequency.
+- $f_{\text{offset}}$ is the separation between the centre frequency of first or last 5 MHz channel in the pass band and the centre of the measuring filter.
+- $f_{\text{offset}_{\max}}$ is 12,5 MHz.
+- $\Delta f_{\max}$ is equal to $f_{\text{offset}_{\max}}$ minus half of the bandwidth of the measurement filter.
+
+To select the table of the maximum level for the spectrum emission mask test, use the maximum output power as defined in subclause 3.1 Definition. If one channel is used for the spectrum emission mask test use this power for the selection. If two channels are used for the spectrum emission mask test use the power of one of these.
+
+**Table 9.1: Emission mask values, 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$ | Minimum requirement (Note 3) | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-14 \text{ dBm} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-26 \text{ dBm} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-13 \text{ dBm} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f\_max$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 1 MHz |
+
+NOTE 3:
+- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\Delta P = 0 \text{ dB}$ ;
+- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\Delta P = 0,3 \text{ dB}$
+
+**Table 9.2: Emission mask values, 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$ | Minimum requirement (Note 3) | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-14 \text{ dBm} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-26 \text{ dBm} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-13 \text{ dBm} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f\_max$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 56 \text{ dB}$ | 1 MHz |
+
+NOTE 3:
+- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\Delta P = 0 \text{ dB}$ ;
+- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\Delta P = 0,3 \text{ dB}$
+
+**Table 9.3: Emission mask values, 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$ | Minimum requirement (Note 3) | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 53 \text{ dB} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $P - 53 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 65 \text{ dB} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 52 \text{ dB} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f\_max$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 56 \text{ dB}$ | 1 MHz |
+
+NOTE 3:
+- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\Delta P = 0 \text{ dB}$ ;
+- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\Delta P = 0,3 \text{ dB}$
+
+**Table 9.4: Emission mask values, maximum output power P < 31 dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-22 \text{ dBm} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-22 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-34 \text{ dBm} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-21 \text{ dBm} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f\_max$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-25 \text{ dBm}$ | 1 MHz |
+
+NOTE 3:
+- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ;
+- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$
+
+For operation in band II, IV, V, X, XII, XIII, XIV and XXV the applicable additional requirement in Tables 9.4A, 9.4B or 9.4C apply in addition to the minimum requirements in Tables 9.1 to 9.4.
+
+**Table 9.4A: Additional emission mask values for Bands II, IV, X, XXV**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $4,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 1 MHz |
+
+**Table 9.4B: Additional emission mask values for Band V**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3,55 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 100 kHz |
+
+**Table 9.4C: Additional emission mask values for Bands XII, XIII, XIV**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,6 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,615 \text{ MHz}$ | $-13 \text{ dBm}$ | 30 kHz |
+| $2,6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $2,65 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 100 kHz |
+
+In certain regions the following requirement may apply for protection of DTT. For UTRA Repeater operating in Band XX, the level of emissions in the band 470-790 MHz, measured in an 8MHz filter bandwidth on centre frequencies $F_{filter}$ according to Table 9.4D, shall not exceed the maximum emission level $P_{EM,N}$ declared by the manufacturer.
+
+**Table 9.4.D: Declared emissions levels for protection of DTT**
+
+| Filter centre frequency,
| Measurement
bandwidth | Declared emission level
[dBm] |
+|---------------------------------------------------------------------|----------------------------------|------------------------------------------|
+| $F_{\text{filter}} = 8 \cdot N + 306$ (MHz);
$21 \leq N \leq 60$ | 8 MHz | $P_{\text{EM,N}}$ |
+
+NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the repeater needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in TS 25.104 [1] Annex D.
+
+Note for Tables 9.1, 9.2, 9.3, 9.4, 9.4A, 9.4B and 9.4C:
+
+NOTE 1: This frequency range ensures that the range of values of $f_{\text{offset}}$ is continuous.
+
+NOTE 2 As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth can be smaller than 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.
+
+#### 9.1.2.3 Test purpose
+
+The purpose of this test is to verify that the Repeater meet the spectrum emission requirements as specified in TS 25.106.
+
+#### 9.1.2.4 Method of test
+
+##### 9.1.2.4.1 Initial conditions
+
+A measurement set-up is shown in annex A
+
+- 1) Connect a signal generator to the input port of the Repeater for tests of repeaters with a pass band corresponding to one 5 MHz channel. If the pass band corresponds to two or more 5 MHz carriers, two signal generators with a combining circuit or one signal generator with the ability to generate several WCDMA carriers is connected to the input. The signals shall be de-correlated as described in TS25.141 [11], clause 6.1.1.6.3 of equal power.
+- 2) Measurements with an offset from the carrier centre frequency between 2,515 MHz and 4,0 MHz shall use a 30 kHz measurement bandwidth.
+- 3) Measurements with an offset from the carrier centre frequency between 4,0 MHz and $(\Delta f_{\text{max}} - 500 \text{ kHz})$ shall use a 1 MHz measurement bandwidth. The 1MHz measurement bandwidth may be calculated by integrating multiple 50 kHz or narrower filter measurements.
+- 4) Detection mode: True RMS.
+
+##### 9.1.2.4.2 Procedures
+
+- 1) Set the Repeater to maximum gain.
+- 2) Set the signal generator(s) to generate signal(s) in accordance to test model 1, TS 25.141 subclause 6.2.1.1.1, at level(s) which produce the manufacturer specified maximum output power at maximum gain.
+- 3) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value.
+- 4) Increase the power with 10 dB compare to the level obtained in step 2.
+- 5) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value.
+- 6) If the pass band corresponds to more than two consecutive nominal 5 MHz channels, repeat step 2) to 5) with any combination of two WCDMA modulated signals of equal power in the repeaters pass band.
+
+- 7) Switch of the signal generator.
+- 8) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value.
+
+#### 9.1.2.5 Test requirements
+
+The measurement result of step 3 and 5 of 9.1.4.2 shall not exceed the maximum level specified in tables 9.5 to 9.8 for the appropriate Repeater maximum output power.
+
+**Table 9.5: Emission mask values, 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$ | Test requirement Band (Note 1) | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-12,5 \text{ dBm} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-12,5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-24,5 \text{ dBm} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-11,5 \text{ dBm} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-11,5 \text{ dBm}$ | 1 MHz |
+
+NOTE 1:
+- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ;
+- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$
+
+**Table 9.6: Emission mask values, 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$ | Test requirement Band (Note 1) | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-12,5 \text{ dBm} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-12,5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-24,5 \text{ dBm} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-11,5 \text{ dBm} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 54,5 \text{ dB}$ | 1 MHz |
+
+NOTE 1:
+- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ;
+- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$
+
+**Table 9.7: Emission mask values, 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$ | Test requirement Band (Note 1) | Measurement bandwidth |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 51,5 \text{ dB} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $P - 51,5 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 63,5 \text{ dB} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 50,5 \text{ dB} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 54,5 \text{ dB}$ | 1 MHz |
+| NOTE 1:
- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ;
- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ | | | |
+
+**Table 9.8: Emission mask values, maximum output power P < 31 dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement Band (Note 1) | Measurement bandwidth |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-20,5 \text{ dBm} + \Delta P$ | 30 kHz |
+| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-20,5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz |
+| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-32,5 \text{ dBm} + \Delta P$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-19,5 \text{ dBm} + \Delta P$ | 1 MHz |
+| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-23,5 \text{ dBm}$ | 1 MHz |
+| NOTE 1:
- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ;
- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ | | | |
+
+For operation in band II, IV, V, X, XII, XIII, XIV and XXV the applicable additional requirement in Tables 9.8A, 9.8B or 9.8C apply in addition to the minimum requirements in Tables 9.5 to 9.8.
+
+**Table 9.8A: Additional emission mask values for Bands II, IV, X, XXV**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $4,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 1 MHz |
+
+**Table 9.8B: Additional emission mask values for Band V**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz |
+| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3,55 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 100 kHz |
+
+**Table 9.8C: Additional emission mask values for Bands XII, XIII, XIV**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-----------------------|
+| $2,5 \text{ MHz} \leq \Delta f < 2,6 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,615 \text{ MHz}$ | $-13 \text{ dBm}$ | 30 kHz |
+| $2,6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2,65 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 100 kHz |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex B.
+
+### 9.1.3 Protection of BS receiver in the operating band
+
+This requirement shall be applied for the protection of UTRA-FDD BS receivers in geographic areas in which UTRA-FDD Repeater and UTRA-FDD BS are deployed.
+
+The requirement applies at frequencies that are more than 10 MHz below or more than 10 MHz above the repeater pass band.
+
+#### 9.1.3.1 Minimum Requirement
+
+This requirement applies to the uplink of the repeater, at maximum gain.
+
+In the up-link direction of the Repeater the power of any spurious emission shall not exceed:
+
+**Table 9.11A: Uplink operating band unwanted emission limits for protection of UTRA FDD BS receiver**
+
+| Maximum Level | Measurement Bandwidth | Note |
+|---------------|-----------------------|------|
+| -53 dBm | 100 kHz | |
+
+NOTE 1: These requirements in Table 9.11A for the up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA FDD BS receiver.
+
+NOTE 2: The requirements shall be reconsidered when the state of the art technology progresses.
+
+NOTE 3: The protection of R-GSM is for further study.
+
+### 9.1.4 Co-existence with services in adjacent frequency bands
+
+This requirement may be applied for the protection in bands adjacent to bands I or VII, as defined in clause 4.1 in geographic areas in which both an adjacent band service and UTRA are deployed.
+
+The requirement applies only to the down-link direction of the repeater.
+
+#### 9.1.4.1 Minimum requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.20: UTRA Repeater down-link spurious emissions limits for protection of adjacent band services**
+
+| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note |
+|----------------|---------------|------------------------------------------------|-----------------------|------|
+| I | 2100-2105 MHz | $-30 + 3.4 (f - 2100 \text{ MHz}) \text{ dBm}$ | 1 MHz | |
+| | 2175-2180 MHz | $-30 + 3.4 (2180 \text{ MHz} - f) \text{ dBm}$ | 1 MHz | |
+| VII | 2610-2615 MHz | $-30 + 3.4 (f - 2610 \text{ MHz}) \text{ dBm}$ | 1 MHz | |
+| | 2695-2700 MHz | $-30 + 3.4 (2700 \text{ MHz} - f) \text{ dBm}$ | 1 MHz | |
+
+## 9.2 Spurious emissions
+
+### 9.2.1 Definition and applicability
+
+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 Repeater output port.
+
+The requirements of either subclause 9.2.2.1 or subclause 9.2.2.2 shall apply whatever the type of Repeater considered (one or several pass bands). It applies for all configurations foreseen by the manufacturer's specification.
+
+The spurious emission limits apply from 9 kHz to 12.75 GHz (or above, as indicated in Table 9.9 and 9.10), excluding the frequency range from 10 MHz below the lowest frequency of the repeaters operating band up to 10 MHz above the
+
+highest frequency of the repeaters operating band. Exceptions are the requirement in Table 9.17 and 9.21 that apply also closer than 10 MHz from repeaters operating band.
+
+Unless otherwise stated, all requirements are measured as mean power (RMS).
+
+For repeaters capable of supporting both UTRA and E-UTRA, conformance to the UTRA spurious emission requirements can also be demonstrated using E-UTRA spurious emission test methods as described in TS 36.143 [13].
+
+### 9.2.2 Minimum Requirements
+
+In normal conditions as specified in section 5.4.1 the following requirements shall be met.
+
+#### 9.2.2.1 Spurious emission (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 [4], are applied.
+
+At maximum Repeater gain, with WCDMA signals in the pass band of the Repeater, at levels that produce the maximum rated output power per channel, the power of any spurious emission shall not exceed the limits specified in Table 9.9.
+
+When the power in all channels is increased by 10 dB the requirements shall still be met.
+
+The requirement shall apply both with or without an input signal applied.
+
+**Table 9.9: Up-link and down-link: General spurious emissions limits, Category A**
+
+| Band | Maximum level | Measurement Bandwidth | Notes |
+|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------|
+| 9kHz – 150kHz | -13 dBm | 1 kHz | Note 1 |
+| 150kHz – 30MHz | | 10 kHz | Note 1 |
+| 30MHz – 1GHz | | 100 kHz | Note 1 |
+| 1GHz – 12,75 GHz | | 1 MHz | Note 2 |
+| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL or UL operating band for DL or UL spurious emissions, respectively | | 1 MHz | Note 2, Note 3 |
+
+NOTE 1: Bandwidth as in ITU-R SM.329 [4], s4.1
+NOTE 2: Upper frequency as in ITU-R SM.329 [4], s2.5 table 1
+NOTE 3: Applies only for Band XXII
+
+#### 9.2.2.2 Spurious emission (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 [4], are applied.
+
+At maximum Repeater gain, with WCDMA signals in the pass band of the Repeater, at levels that produce the maximum rated power output per channel, the power of any spurious emission shall not exceed the limits specified in Tables 9.10 and 9.10A depending on the declared operating band for the down- and up-link.
+
+When the power in all channels is increased by 10 dB the requirements shall still be met.
+
+The requirement shall apply both with or without an input signal applied.
+
+**Table 9.10: General spurious emissions limits (Category B)**
+
+| Band | Maximum Level | Measurement Bandwidth | Note |
+|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------------------|----------------|
+| 9 kHz ↔ 150 kHz | -36 dBm | 1 kHz | Note 1 |
+| 150 kHz ↔ 30 MHz | -36 dBm | 10 kHz | Note 1 |
+| 30 MHz ↔ 1 GHz | -36 dBm | 100 kHz | Note 1 |
+| 1 GHz ↔ 12.75 GHz | -30 dBm | 1 MHz | Note 2 |
+| 12.75 GHz - 5 th harmonic of the upper frequency edge of the DL or UL operating band for DL or UL spurious emissions, respectively | -30 dBm | 1 MHz | Note 2, Note 3 |
+| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1 | | | |
+| NOTE 2: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1. Upper frequency as in ITU-R SM.329 [4], s2.5 table 1 | | | |
+| NOTE 3: Applies only for Band XXII | | | |
+
+**Table 9.10A: (Void)****Table 9.10B: (void)****Table 9.10C: (void)****Table 9.10D: (void)****Table 9.10E: (void)****Table 9.10F: (void)**
+
+#### **9.2.2.3 Void**
+
+#### **9.2.2.4 Co-existence with other systems in the same geographical area**
+
+These requirements may be applied for the protection of UE, MS and/or BS operating in other frequency bands in the same geographical area. The requirements may apply in geographic areas in which both UTRA FDD Repeater and a system operating in another frequency band than the FDD operating band are deployed. The system operating in the other frequency band may be GSM900, DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD.
+
+##### 9.2.2.4.1 Minimum Requirements
+
+The power of any spurious emission shall not exceed the limits of Table 9.13 for a UTRA FDD Repeater where requirements for co-existence with the system listed in the first column apply.
+
+**Table 9.13: UTRA Repeater up-link and down-link spurious emissions limits in geographic coverage area of systems operating in other frequency bands**
+
+| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note |
+|-----------------------------------------------------|-----------------------------------|---------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII. |
+| | 876 – 915 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band III. |
+| | 1710 – 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 9.1.3. |
+| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in frequency band II or band XXV. |
+| | 1850 – 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in frequency band II or band XXV, since it is already covered by the requirement in sub-clause 9.1.3. |
+| GSM850 or CDMA850 | 869 – 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in frequency band V. |
+| | 824 – 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in frequency band V, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I. |
+| | 1920 – 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band II or E-UTRA Band 2 | 1930 – 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. |
+| | 1850 – 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX. |
+| | 1710 – 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 9.1.3. This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IX in the frequency range from 1749,9 MHz to 1784,9 MHz, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X. |
+| | 1710 – 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V. |
+| | 824 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 – 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, VI, XIX or XX. |
+| | 815 – 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V, VI, XIX or XX. |
+| | 830 – 845 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VI or XIX, since it is already covered by the requirement in sub-clause 9.1.3. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or XX. |
+| | 2620 – 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. |
+
+| | | | | |
+|-------------------------------------------------|---------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UTRA FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band VIII or E-UTRA Band 8 | 925 – 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII. |
+| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX. |
+| | 1749.9 – 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X. |
+| | 1710 – 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band X, since it is already covered by the requirement in sub-clause 9.1.3.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IV in the frequency range from 1710 MHz to 1755 MHz, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI or band XXI. |
+| | 1427.9 – 1447.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 9.1.3. |
+| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band XII or E-UTRA Band 12 | 728 – 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII. |
+| | 698 – 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band XIII or E-UTRA Band 13 | 746 – 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII. |
+| | 777 – 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band XIV or E-UTRA Band 14 | 758 – 768 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV. |
+| | 788 – 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 9.1.3. |
+| E-UTRA Band 17 | 734 – 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII. |
+| | 704 – 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band XX or E-UTRA Band 20 | 791 – 821 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX. |
+| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 9.1.3. |
+| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 9.1.3. |
+| E-UTRA Band 23 | 2180 – 2200 MHz | -52 dBm | 1 MHz | |
+| | 2000 – 2020 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, where the limits are defined separately. |
+| | 2000 – 2010 MHz | -30 dBm | 1 MHz | |
+
+| | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 2010 – 2020 MHz | -49 dBm | 1 MHz | This requirement only applies to UTRA FDD Repeater operating in band II or band XXV. This requirement applies starting 5 MHz above the band XXV DL operating band. |
+| E-UTRA Band 24 | 525 – 1559 MHz | -52 dBm | 1 MHz | |
+| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | |
+| UTRA FDD Band XXV or E-UTRA Band 25 | 1930 - 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band II or band XXV. |
+| | 1850 - 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD repeater operating in band XXV since it is already covered by the requirement in sub-clause 9.1.3. For UTRA FDD repeater operating in band II, it applies for 1910 MHz to 1915 MHz, while the rest is covered in sub-clause 9.1.3. |
+| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | |
+| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | |
+
+#### 9.2.2.5 Co-existence with co-located and co-sited base stations
+
+These requirements may be applied for the protection of other BS receivers when GSM900 and/or DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD BS are co-located with a UTRA FDD Repeater.
+
+##### 9.2.2.5.1 Minimum Requirements
+
+The power of any spurious emission shall not exceed the limits of Table 9.14 for a UTRA FDD Repeater where requirements for co-location with the Base Station listed in the first column apply.
+
+**Table 9.14: UTRA Repeater up-link and down-link spurious emissions limits for Repeater co-located with Base Stations**
+
+| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note |
+|----------------------------------------------------|----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900 | 876 – 915 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VIII. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. |
+| DCS1800 | 1710 – 1785 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. |
+| PCS1900 | 1850 – 1910 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band II or band XXV. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. |
+| GSM850 or CDMA850 | 824 – 849 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band I or E-UTRA Band 1 | 1920 – 1980 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band I. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band II or E-UTRA Band 2 | 1850 – 1910 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band II or band XXV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band III or E-UTRA Band 3 | 1710 – 1785 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IX in the frequency Range from 1749,9 MHz to 1784,9 MHz, since it is already covered by the requirement in sub-clause 9.1.3, but requires a 73dB coupling loss between base station and the repeater UL transmit port. |
+| UTRA FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band IV or band X. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band V or E-UTRA Band 5 | 824 – 849 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 – 830 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V, VI, XIX or XX. |
+| | 830 – 845 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VI or XIX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or XX. |
+
+| | | | | |
+|-------------------------------------------------|---------------------|---------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UTRA FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band VIII or E-UTRA Band 8 | 880 – 915 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VIII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 – 1784.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III or band IX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band X. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IV in the frequency range from 1710 MHz to 1755 MHz, since it is already covered by the requirement in sub-clause 9.1.3, but requires a 73dB coupling loss between base station and the repeater UL transmit port. |
+| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1427.9 – 1447.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| | 1447.9 - 1462.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the up-link of UTRA FDD Repeater operating in band XXI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XIII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XIV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| E-UTRA Band 17 | 704 – 716 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band XX or E-UTRA Band 20 | 832 – 862 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+
+| | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| E UTRA Band 23 | 2000 - 2020 MHz | -96 dBm | 100 kHz | |
+| E-UTRA Band 24 | 1626.5 - 1660.5 MHz | -96 dBm | 100 kHz | |
+| UTRA FDD Band XXV or E UTRA Band 25 | 1850 - 1915 MHz | -96 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. |
+| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeater operating band (see Table 4.1). The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB UTRA Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2]. | | | | |
+| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | |
+
+#### 9.2.2.6 Co-existence with PHS
+
+This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA-FDD Repeaters are deployed. This requirement is also applicable at specified frequencies falling between 12,5 MHz below the centre frequency of the first 5 MHz channel or more than 12,5 MHz above the centre frequency of the last 5 MHz channel in the pass band.
+
+##### 9.2.2.6.1 Minimum requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.17: UTRA Repeater Spurious up-link and down-link emissions limits for in geographic coverage area of PHS**
+
+| Band | Maximum Level | Measurement Bandwidth | Note |
+|---------------------|---------------|-----------------------|------|
+| 1884,5 – 1915,7 MHz | -41 dBm | 300 kHz | |
+
+#### 9.2.2.7 Co-existence with UTRA-TDD and/or E-UTRA TDD
+
+##### 9.2.2.7.1 Operation in the same geographic area
+
+This requirement may be applied to geographic areas in which both UTRA-TDD and/or E-UTRA TDD and UTRA-FDD Repeaters are deployed.
+
+###### 9.2.2.7.1.1 Minimum requirement
+
+In the down-link direction of the Repeater the power of any spurious emission shall not exceed:
+
+**Table 9.18: UTRA Repeater down-link spurious emissions limits in geographic coverage area of UTRA-TDD and/or E-UTRA TDD**
+
+| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------|-----------------------|------------------------------------------------------------------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | |
+| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -52 dBm | 1 MHz | |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -52 dBm | 1 MHz | Applicable in China |
+| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | |
+| E-UTRA Band 41 | 2496 – 2690 MHz | -52 dBm | 1 MHz | |
+| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | |
+| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | |
+| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | |
+
+In the up-link direction of the Repeater the power of any spurious emission shall not exceed:
+
+**Table 9.18A: UTRA Repeater up-link spurious emissions limits in geographic coverage area of UTRA-TDD and/or E-UTRA TDD**
+
+| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I, band II or band XXV. |
+| | 1900 - 1920 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I band II or band XXV. |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | |
+| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band VII. |
+| | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -53 dBm | 100 kHz | Applicable in China. This requirement is applied only to UTRA FDD Repeater operating in band II or band XXV. |
+| | 1880 – 1920 MHz | -52 dBm | 1 MHz | Applicable in China. This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. |
+| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | |
+| E-UTRA Band 41 | 2496 - 2690 MHz | -52 dBm | 1 MHz | |
+| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | |
+| NOTE 3: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | |
+| NOTE 4: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | |
+
+NOTE 1: The requirements of -53dBm/100kHz in Table 9.18 and in Table 9.18A, which are respectively for the down link and up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA TDD BS receiver.
+
+NOTE 2: The requirements shall be reconsidered when the state of the art technology progresses.
+
+##### 9.2.2.7.2 Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations
+
+This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD and/or E-UTRA TDD BS and UTRA-FDD Repeater are co-located.
+
+###### 9.2.2.7.2.1 Minimum requirement
+
+In the down-link direction of the Repeater the power of any spurious emission shall not exceed:
+
+**Table 9.19: UTRA Repeater down-link spurious emissions limits for protection of co-located UTRA TDD and/or E-UTRA TDD BS receiver**
+
+| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-----------------------|------------------------------------------------------------------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | - 86 dBm | 1 MHz | |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | - 86 dBm | 1 MHz | |
+| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | - 86 dBm | 1 MHz | |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -86 dBm | 1 MHz | Applicable in China |
+| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -86 dBm | 1 MHz | |
+| E-UTRA Band 41 | 2496 - 2690 MHz | -86 dBm | 1 MHz | |
+| E-UTRA Band 42 | 3400 - 3600 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| E-UTRA Band 43 | 3600 - 3800 MHz | -86 dBm | 1 MHz | |
+| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | |
+| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | |
+
+In the up-link direction of the Repeater the power of any spurious emission shall not exceed:
+
+**Table 9.19A: UTRA Repeater up-link spurious emissions limits for protection of co-located UTRA TDD and/or E-UTRA TDD BS receiver**
+
+| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I, band II or band XXV. |
+| | 1900 - 1920 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -83 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I. |
+| | 2010 - 2025 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I |
+| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band VII. |
+| | 2570 - 2620 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -53 dBm | 100 kHz | Applicable in China. This requirement is applied only to UTRA FDD Repeater operating in band II or band XXV. |
+| | 1880 – 1920 MHz | -86 dBm | 1 MHz | Applicable in China. This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. |
+| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -86 dBm | 1 MHz | |
+| E-UTRA Band 41 | 2496 - 2690 MHz | -86 dBm | 1 MHz | |
+| E-UTRA Band 42 | 3400 – 3600 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| E-UTRA Band 43 | 3600 – 3800 MHz | -86 dBm | 1 MHz | |
+| NOTE 4: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | |
+| NOTE 5: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | |
+
+NOTE 1: The requirements of -53dBm/100kHz in Table 9.19 and Table 9.19A, which are respectively for the down link and up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA TDD BS receiver.
+
+NOTE 2: The requirements of -83dBm/100kHz in Table 9.19A for the up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 43 dB between a Repeater and a UTRA TDD BS receiver.
+
+NOTE 3: The requirements shall be reconsidered when the state of the art technology progresses.
+
+#### 9.2.2.8 (Void)
+
+#### 9.2.2.9 Protection of public safety operations
+
+This requirement shall be applied to Repeater operating in Bands XIII and XIV to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at specified frequencies falling between 12.5 MHz below the first carrier frequency used and 12.5 MHz above the last carrier frequency used.
+
+##### 9.2.2.9.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.21: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of public safety operations**
+
+| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note |
+|----------------|---------------|---------------|-----------------------|------|
+| XIII | 763 - 775 MHz | -46 dBm | 6.25 kHz | |
+| XIII | 793 - 805 MHz | -46 dBm | 6.25 kHz | |
+| XIV | 769 - 775 MHz | -46 dBm | 6.25 kHz | |
+| XIV | 799 - 805 MHz | -46 dBm | 6.25 kHz | |
+
+### 9.2.3 Test purpose
+
+This test measure conducted spurious emission from the Repeater transmitter antenna connector, while the Repeater is in operation.
+
+### 9.2.4 Method of test
+
+#### 9.2.4.1 Initial conditions
+
+A measurement set-up is shown in annex A.
+
+1) Connect a signal generator to the input port of the Repeater for tests of repeaters with a pass band corresponding to one 5 MHz channel. If the pass band corresponds to two or more 5 MHz carriers, two signal generators with a combining circuit or one signal generator with the ability to generate several WCDMA carriers is connected to the input. The signals shall be de-correlated as described in TS25.141 [11], clause 6.1.1.6.3 of equal power.
+
+2) Detection mode: True RMS.
+
+#### 9.2.4.2 Procedures
+
+- 1) Set the Repeater to maximum gain.
+- 2) Set the signal generator(s) to generate signal(s) in accordance to test model 1, TS 25.141 subclause 6.2.1.1.1, at level(s) which produce the manufacturer specified maximum output power at maximum gain.
+- 3) The detecting device shall be configured with a measurement bandwidth as stated in the tables.
+- 4) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value.
+- 5) Increase the input power with 10 dB compare to the level obtained in step 2.
+- 6) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value.
+
+- 7) If the pass band corresponds to more than two consecutive nominal 5 MHz channels, repeat step 2) to 6) with any combination of two WCDMA modulated signals of equal power in the repeaters pass band.
+- 8) Switch of the signal generator.
+- 9) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value.
+
+### 9.2.5 Test requirements
+
+In all measurements, the requirements according to subclause 9.2.2 shall be fulfilled.
+
+# --- 10 Modulation accuracy
+
+In this section the procedure for testing the modulation accuracy of Repeaters is defined. This test includes EVM and peak code domain error.
+
+## 10.1 Error vector magnitude
+
+In this section the procedure for testing the Error Vector Magnitude (EVM) of Repeaters is defined.
+
+### 10.1.1 Definition and applicability
+
+The Error Vector Magnitude is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. The modification is done according to annex E of TS25.141. This difference is called the error vector. The EVM result is defined as the square root of the ratio of the mean error vector power to the modified mean reference signal power expressed as a %. The measurement interval is one power control group (timeslot).
+
+### 10.1.2 Minimum Requirements
+
+In normal conditions as specified in section 5.4.1 the Error Vector Magnitude shall not be worse than 12,5 % as defined in TS25.106.
+
+### 10.1.3 Test purpose
+
+To verify that the EVM is within the limit specified in 10.1.2 after the signal passed through the Repeater..
+
+### 10.1.4 Method of test
+
+#### 10.1.4.1 Initial conditions
+
+Set-up the equipment as shown in annex A.
+
+The test is based upon the test for the base station. Test model 1 as described in TS25.141 is used for the definition of the signal to test on. A signal generator providing the required signals is connected to the input of the Repeater. The Repeater is set to operate at full gain. The signal level is adjusted to the equivalent level to obtain the nominal output power as declared by the manufacturer. A signal analyser connected to the output is used to measure the EVM value.
+
+#### 10.1.4.2 Procedure
+
+The test has to be performed in the uplink and the downlink path of the Repeater. The EVM has to be measured according to Annex E of TS25.141
+
+#### 10.1.4.3 Stimulus EVM effect
+
+The stimulus signal generator EVM will RSS with the tested repeater EVM. The target for the recorded value is adjusted accordingly in the test requirements.
+
+### 10.1.5 Test requirements
+
+In normal conditions as specified in section 5.4.1, the Error Vector Magnitude, as defined in TS25.106, shall not exceed 13,2%.
+
+## 10.2 Peak code domain error
+
+In this section the procedure for testing the Peak Code Domain Error of Repeaters is defined.
+
+### 10.2.1 Definition and applicability
+
+The Peak Code Domain Error is computed by projecting the error vector onto the code domain at a specific spreading factor. The Code Domain Error for every code in the domain is defined as the ratio of the mean power of the projection onto that code, to the mean power of the composite reference waveform. This ratio is expressed in dB. The Peak Code Domain Error is defined as the maximum value for the Code Domain Error for all codes. The measurement interval is one power control group (timeslot).
+
+### 10.2.2 Minimum Requirements
+
+In normal conditions as specified in section 5.4.1 the peak code domain error shall not exceed -35 dB at spreading factor 256 as defined in TS25.106.
+
+### 10.2.3 Test purpose
+
+To verify that the peak code domain error is within the limit specified in 10.2.2 after the signal passed through the Repeater.
+
+### 10.2.4 Method of test
+
+#### 10.2.4.1 Initial conditions
+
+Set-up the equipment as shown in annex A.
+
+The test is based upon the test for the base station. Test model 3 as described in TS25.141 is used for the definition of the signal to test on. A signal generator providing the required signals is connected to the input of the Repeater. The spreading factor of the signal generator is set to 256. The Repeater is set to operate at full gain. The signal level is adjusted to the equivalent level to obtain the nominal output power as declared by the manufacturer. A signal analyser connected to the output is used to measure the peak code domain error value.
+
+#### 10.2.4.2 Procedure
+
+The test has to be performed in the uplink and the downlink path of the Repeater. The peak code domain error as described in TS25.141 Annex E has to be measured.
+
+### 10.2.5 Test requirements
+
+In normal conditions as specified in section 5.4.1 the peak code domain error shall not exceed -33,9 dB at spreading factor 256 as defined in TS25.106.
+
+## 10.3 Relative Code Domain Error (RCDE) for 64QAM modulation
+
+### 10.3.1 Definition and applicability
+
+The Relative Code Domain Error is computed by projecting the error vector (as defined in 10.1) onto the code domain at a specified spreading factor. Only the active code channels in the composite reference waveform are considered for this requirement. The Relative Code Domain Error for every active code is defined as the ratio of the mean power of the error projection onto that code, to the mean power of the active code in the composite reference waveform. This ratio is expressed in dB. The measurement interval is one frame.
+
+The requirement for Relative Code Domain Error is only applicable for Repeater supporting 64QAM modulated codes.
+
+See TS25.141 [11] Annex E for further details.
+
+### 10.3.2 Minimum requirement
+
+The average Relative Code Domain Error for 64QAM modulated codes shall not exceed -21 dB at spreading factor 16.
+
+### 10.3.3 Test purpose
+
+To verify that the peak code domain error is within the limit specified in 10.3.2 after the signal passed through the Repeater.
+
+### 10.3.4 Method of test
+
+#### 10.3.4.1 Initial conditions
+
+Set-up the equipment as shown in annex A.
+
+The test is based upon the test for the base station. Test model 6 as described in TS25.141 is used for the definition of the signal to test on. A signal generator providing the required signals is connected to the input of the Repeater. The spreading factor of the signal generator is set to 16. The Repeater is set to operate at full gain. The signal level is adjusted to the equivalent level to obtain the nominal output power as declared by the manufacturer. A signal analyser connected to the output is used to measure the peak code domain error value.
+
+#### 10.3.4.2 Procedure
+
+The test has to be performed in the uplink and the downlink path of the Repeater. The relative code domain error as described in TS25.141 Annex E has to be measured.
+
+### 10.3.5 Test requirements
+
+In normal conditions as specified in section 5.4.1 the relative code domain error shall not exceed -19.3 dB at spreading factor 16 as defined in TS25.106.
+
+# 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 Definition and applicability
+
+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 Repeater to maintain the wanted frequency free of internally created interference.
+
+The test requirements in Tables 11.2 may be applied for the protection of FDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD BS are co-located with a UTRA FDD Repeater.
+
+The additional test requirements in Tables 11.2A may be applied for the protection of FDD Repeater input when a UTRA TDD BS is co-located with a UTRA FDD Repeater.
+
+This test applies to uplink and downlink path of the Repeater.
+
+## 11.2 Minimum Requirements
+
+### 11.2.1 General requirement
+
+In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater:
+
+**Table 11.1: General input intermodulation requirement**
+
+| f_offset | Interfering Signal Levels | Type of signals | Measurement bandwidth |
+|-----------------|----------------------------------|------------------------|------------------------------|
+| 3,5 MHz | -40 dBm | 2 CW carriers | 1 MHz |
+
+For the parameters specified in table 11.1, the power in the pass band shall not increase by 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.
+
+### 11.2.2 Co-location with BS in other systems
+
+In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater:
+
+**Table 11.2: Input intermodulation requirements for interfering signals in other systems**
+
+| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note |
+|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900 | 921 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| DCS1800 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| PCS1900 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| GSM850 or CDMA850 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band II or E-UTRA Band 2 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 – 890 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+
+| | | | | | |
+|-------------------------------------------------|---------------------|---------|---------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI or band XXI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| E-UTRA Band 17 | 734 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XX or E-UTRA Band 20 | 791 - 821 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| E UTRA Band 23 | 2180 - 2200 MHz | +16 dBm | 2 CW carriers | 1 MHz | |
+| E UTRA Band 24 | 1525 – 1559 MHz | +16 dBm | 2 CW carriers | 1 MHz | |
+| UTRA-FDD Band XXV or E-UTRA Band 25 | 1930 - 1995 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band II, it applies from 1990MHz to 1995MHz, while the rest is covered in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL transmit port. |
+
+| | |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NOTE 1: | The co-location requirements in the table 11.2 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the table 11.2. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2] |
+| NOTE 2: | The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. |
+
+**Table 11.2AA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems**
+
+| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth |
+|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|-----------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA-TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| E-UTRA Band 41 | 2496 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| E-UTRA Band 42 | 3400 - 3600 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| E-UTRA Band 43 | 3600 - 3800 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| NOTE 1: | The co-location requirements in Table 11.2AA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.2AA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2] | | | |
+| NOTE 2: | The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | |
+
+For the parameters specified in table 11.2 and 11.2AA, 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.
+
+### 11.2.3 Co-existence with other systems
+
+In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater:
+
+#### **Table 11.2A: Input intermodulation requirements for interfering signals in other systems**
+
+| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note |
+|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900 | 876 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| DCS1800 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1. |
+| PCS1900 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. |
+| GSM850 or CDMA850 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band I or E-UTRA Band 1 | 1920 – 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band II or E-UTRA Band 2 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band III or E-UTRA Band 3 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band V or E-UTRA Band 5 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 – 845 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.2.1. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or XX. |
+| UTRA-FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band VIII or E-UTRA Band 8 | 880 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band IX or E-UTRA Band 9 | 1749,9 – 1784,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. |
+| | 1427,9 – 1447,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 11.2.1. |
+
+| | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1447.9 - 1462.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1. |
+| E-UTRA Band 17 | 704 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XX or E-UTRA Band 20 | 832 - 862 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XXII or E-UTRA Band 22 | 3410-3490 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| E-UTRA Band 23 | 2000 - 2020 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 24 | 1626.5 – 1660.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| UTRA-FDD Band XXV or E-UTRA Band 25 | 1850-1915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 11.1. |
+| NOTE 1: The co-existence requirements in Table 11.2A do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-existence requirement in the Table 11.2A. The current state-of-the-art technology does not allow a single generic solution for co-existence | | | | | |
+| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | |
+
+**Table 11.2AAA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems**
+
+| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note |
+|--------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|----------------------------------------------------------------------------------------------------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| UTRA-TDD Band d) and or E-UTRA TDD Band 38 | 2570 - 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -15 dBm | 2 CW carriers | 1 MHz | Applicable in China.
This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. |
+| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 41 | 2496 - 2690 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 42 | 3400 - 3600 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| E-UTRA Band 43 | 3600 - 3800 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+
+NOTE 1: The co-existence requirements in Table 11.2AAA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.2AAA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5]
+
+NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications.
+
+For the parameters specified in table 11.2A and table 11.2AAA, 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.
+
+## 11.3 Test purpose
+
+The purpose of this test is to verify that the Repeater meets the intermodulation characteristics requirements as specified in TS 25.106, subclause 11.1.
+
+## 11.4 Method of test
+
+### 11.4.1 Initial conditions
+
+- 1) Set-up the equipment as shown in annex A.
+- 2) Set the Repeater to maximum gain.
+- 3) Connect two signal generators with a combining circuit or one signal generator with the ability to generate several CW carriers to the input.
+- 4) Connect a spectrum analyser to the output of the Repeater. Set the resolution bandwidth to 1 MHz in the centre of the pass band. Set averaging to 1 second or more.
+
+### 11.4.2 Procedure
+
+- 1) Adjust the frequency of the input signals, either below or above the pass band, so that the lowest order intermodulation product is positioned in the centre of the pass band, according to subclause 11.2.
+- 2) Take the measurement of the rise of the output signal.
+- 3) Repeat the measurement for the opposite path of the Repeater.
+
+## 11.5 Test requirements
+
+### 11.5.1 Mandatory requirement
+
+In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater:
+
+**Table 11.3: Input intermodulation requirement**
+
+| f_offset | Interfering Signal Levels | Type of signals | Measurement bandwidth |
+|-----------------|----------------------------------|------------------------|------------------------------|
+| 3,5 MHz | -40 dBm | 2 CW carriers | 1 MHz |
+
+For the parameters specified in table 11.3, the power in the pass band shall not increase by more than 11,2 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.
+
+### 11.5.2 Co-location with BS in other systems
+
+In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater:
+
+**Table 11.4: Input intermodulation requirements for interfering signals in other systems**
+
+| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note |
+|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900 | 921 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| DCS1800 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| PCS1900 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| GSM850 or CDMA850 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band II or E-UTRA Band 2 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 – 890 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+
+| | | | | | |
+|-------------------------------------------------|---------------------|---------|---------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI or band XXI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| E-UTRA Band 17 | 734 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XX or E-UTRA Band 20 | 791 - 821 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| UTRA-FDD Band XXII or E-UTRA Band 22 | 3510-3590 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. |
+| E-UTRA Band 23 | 2180 - 2200 MHz | +16 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 24 | 1626.5 – 1660.5 MHz | +16 dBm | 2 CW carriers | 1 MHz | |
+| UTRA-FDD Band XXV or E-UTRA Band 25 | 1930-1995 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band II, it applies from 1990MHz to 1995MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL transmit port. |
+
+| | |
+|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NOTE 1: | The co-location requirements in the table 11.4 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the table 11.4. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2]. |
+| NOTE 2: | The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. |
+
+**Table 11.4AA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD bands**
+
+| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth |
+|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|-----------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA-TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| E-UTRA Band 41 | 2496 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| E-UTRA Band 42 | 3400 - 3600 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| E-UTRA Band 43 | 3600 - 3800 MHz | +16 dBm | 2 CW carriers | 1 MHz |
+| NOTE 1: | The co-location requirements in Table 11.4AA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.4AA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2]. | | | |
+| NOTE 2: | The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | |
+
+For the parameters specified in table 11.4 and in table 11.4AA, the power in the pass band shall not increase with more than 11,2 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.
+
+### 11.5.3 Co-existence with other systems
+
+In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater:
+
+#### **Table 11.4A: Input intermodulation requirements for interfering signals in other systems**
+
+| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note |
+|--------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900 | 876 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| DCS1800 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1. |
+| PCS1900 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. |
+| GSM850 or CDMA850 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band I or E-UTRA Band 1 | 1920 – 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band II or E-UTRA Band 2 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band III or E-UTRA Band 3 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band V or E-UTRA Band 5 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18, 19 | 815 – 845 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.2.1. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or XX. |
+| UTRA-FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band VIII or E-UTRA Band 8 | 880 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band IX or E-UTRA Band 9 | 1749,9 – 1784,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XI or XXI | 1427.9 – 1447.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 11.2.1. |
+| or E-UTRA Band 11 or 21 | 1447.9 - 1462.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 11.2.1. |
+
+| | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UTRA-FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1. |
+| E-UTRA Band 17 | 704 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XX or E-UTRA Band 20 | 832 - 862 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1. |
+| UTRA-FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1. |
+| E-UTRA Band 23 | 2000 - 2020 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 24 | 1626.5 – 1660.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| UTRA-FDD Band XXV or E-UTRA Band 25 | 1850 - 1915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 11.2.1. |
+| NOTE 1: The co-existence requirements in Table 11.4A do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-existence requirement in the Table 11.4A. The current state-of-the-art technology does not allow a single generic solution for co-existence. | | | | | |
+| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | |
+
+**Table 11.4AAA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems**
+
+| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note |
+|--------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|----------------------------------------------------------------------------------------------------------------|
+| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. |
+| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| UTRA-TDD Band d) and or E-UTRA TDD Band 38 | 2570 - 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. |
+| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -15 dBm | 2 CW carriers | 1 MHz | Applicable in China.
This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. |
+| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 41 | 2496 - 2690 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+| E-UTRA Band 42 | 3400 - 3600 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. |
+| E-UTRA Band 43 | 3600 - 3800 MHz | -15 dBm | 2 CW carriers | 1 MHz | |
+
+NOTE 1: The co-existence requirements in Table 11.4AAA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.4AAA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5]
+
+NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications.
+
+For the parameters specified in table 11.4A and table 11.4AAA, the power in the pass band shall not increase with more than 11,2 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.
+
+# 12 Output intermodulation
+
+The output intermodulation requirement is a measure of the ability of the repeater to inhibit the generation of intermodulation products signals created by the presence of an interfering signal reaching the repeater via the output port.
+
+## 12.1 Definition and applicability
+
+The output intermodulation level is the power of the intermodulation products when a WCDMA modulated interference signal is injected into the output port at a level of 30 dB lower than that of the wanted signal. The frequency of the interference signal shall be $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz offset from the wanted signal, but within the frequency band allocated for UTRA FDD downlink as specified in subclause 4.1.
+
+The requirement is applicable for downlink signals.
+
+The normative reference for this requirement is in TS25.106 [12] section 12.
+
+## 12.2 Minimum requirement
+
+In normal conditions as specified in section 5.4.1, the output intermodulation level shall not exceed the out of band emission or the spurious emission requirements of section 9.1 and 9.2.
+
+## 12.3 Test purpose
+
+The test purpose is to verify the ability of the repeater to restrict the generation of intermodulation products in the presence of a subject signal on the repeater input and output ports, and an interfering signal applied at the repeater output port.
+
+## 12.4 Method of test
+
+### 12.4.1 Initial conditions
+
+- 1) Set-up the equipment as shown in annex A.
+- 2) Connect a signal generator to the input port of the Repeater for tests of repeaters with a pass band corresponding to one 5 MHz channel. Connect a signal generator to the circulator on the output port and make sure the signal generator power is directed to the repeater output port.
+- 3) Measurements with an offset from the carrier centre frequency between 2,515 MHz and 4,0 MHz shall use a 30 kHz measurement bandwidth.
+- 4) Measurements with an offset from the carrier centre frequency between 4,0 MHz and ( $\Delta f_{max} - 500$ kHz) shall use a 1 MHz measurement bandwidth. The 1MHz measurement bandwidth may be calculated by integrating multiple 50 kHz or narrower filter measurements
+- 5) Detection mode: True RMS.
+
+### 12.4.2 Procedures
+
+- 1) Set the Repeater to maximum gain.
+- 2) Set the signal generator at the repeater input port (subject signal) to generate a signal in accordance to test model 1, TS 25.141 subclause 6.1.1.1, at the level which produce the manufacturer specified maximum output power at maximum gain.
+- 3) Set the signal generator at the repeater output port (interference signal) to generate a signal in accordance to test model 1, TS 25.141 subclause 6.1.1.1, at the level producing signal power corresponding to 30 dB below the manufacturer specified maximum output power at the repeater output port with the specified frequency offset from the wanted signal.
+- 4) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. Measurements in the band of the interfering signal shall be excluded. The measurements can be limited to the power of all third and fifth order intermodulation products.
+- 5) Repeat from clause 3 until interference signals $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz frequency offset from the wanted signal has been tested. Note that interfering signals outside the UTRA-FDD allocated frequency band , as specifies in section 4.1. need not be tested.
+
+## 12.5 Test requirements
+
+In all measurements, the requirements according to sections 9.1.1.5 and the downlink requirements in section 9.2.2.1 or 9.2.2.2 shall be fulfilled.
+
+# 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 requirement shall apply to the uplink and downlink of Repeater where the donor link is maintained via antennas (over the air Repeater).
+
+## 13.2 Minimum Requirements
+
+In normal conditions the ACRR shall be higher than the value specified in the Table 13.1.
+
+**Table 13.1: Repeater ACRR**
+
+| Repeater maximum output power as in 9.1.1 | Channel offset from the centre frequency of the first or last 5 MHz channel within the pass band. | ACRR limit |
+|-------------------------------------------|---------------------------------------------------------------------------------------------------|------------|
+| $P \geq 31$ dBm | 5 MHz | 33dB |
+| $P \geq 31$ dBm | 10 MHz | 33dB |
+| $P < 31$ dBm | 5 MHz | 20dB |
+| $P < 31$ dBm | 10 MHz | 20dB |
+
+## 13.3 Test purpose
+
+To verify that the Repeater ACRR requirement shall be met as specified in subclause 13.1.
+
+## 13.4 Method of test
+
+### 13.4.1 Initial conditions
+
+- 1) Set-up the equipment as shown in annex A.
+- 2) Connect the signal generator equipment to the Repeater input port.
+- 3) Connect the power measuring equipment to the Repeater output port.
+- 4) The measurement device characteristics shall be:
+ - measurement filter bandwidth: defined in subclause 13.1;
+ - detection mode: true RMS voltage or true average power.
+
+### 13.4.2 Procedure
+
+- 1) Set the signal generator to transmit a signal modulated with a combination of PCCPCH, SCCPCH and Dedicated Physical Channels specified as test model 1 in TS 25.141 at the first or last 5 MHz channel within the pass band.
+- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain
+- 3) Measure the RRC filtered mean power at the RF output port over a certain slot.
+- 4) Set the signal generator to transmit the same signal and the same input power at one of the channel offsets according to Table 13.1.
+- 5) Measure the RRC filtered mean power at the RF output port over a certain slot.
+- 6) Calculate the ratio of the measured power in the pass band to the measured power at the channel offset.
+- 7) Repeat step 4) to 6) until all channel offsets in Table 13.1 are measured.
+
+### 13.4.3 Test Requirements
+
+In normal conditions as specified in section 5.4.1, the ACRR shall be higher than the value specified in the Table 13.2.
+
+**Table 13.2: Repeater ACRR**
+
+| Repeater maximum output power as in 9.1.1.1 | Channel offset from the centre frequency of the first or last 5 MHz channel within the pass band. | ACRR limit |
+|----------------------------------------------------|----------------------------------------------------------------------------------------------------------|-------------------|
+| $P \geq 31$ dBm | 5 MHz | 32,3dB |
+| $P \geq 31$ dBm | 10 MHz | 32,3dB |
+| $P < 31$ dBm | 5 MHz | 19,3dB |
+| $P < 31$ dBm | 10 MHz | 19,3dB |
+
+# --- Annex A (informative): Repeater measurement system set-up
+
+Example of measurement system set-ups are attached below as an informative annex.
+
+## --- A.1 Maximum output power
+
+
+
+```
+graph LR; A[WCDMA Signal Generator] --> B[Repeater under test]; B --> C[Power meter or equivalent];
+```
+
+The diagram shows a linear measurement setup. A 'WCDMA Signal Generator' is connected to the right side of a 'Repeater under test' block. The output of the repeater is connected to a 'Power meter or equivalent' block on the left.
+
+Block diagram for maximum output power measurement
+
+**Figure A.1: Measuring system set-up for maximum output power.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## --- A.2 Frequency stability
+
+
+
+```
+graph LR; A[CW Signal Generator] --> B[Repeater under test]; B --> C[Frequency counter];
+```
+
+The diagram shows a linear measurement setup. A 'CW Signal Generator' is connected to the right side of a 'Repeater under test' block. The output of the repeater is connected to a 'Frequency counter' block on the left.
+
+Block diagram for RF frequency stability measurement
+
+**Figure A.2: Measurement system set-up for RF frequency stability.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## --- A.3 Out of band gain
+
+
+
+```
+graph LR; A[CW Signal Generator] --> B[-30 dB precision attenuator]; B --> C[Repeater under test]; C --> D[-30 dB precision attenuator]; D --> E[Spectrum analyser];
+```
+
+The diagram shows a linear measurement setup. A 'CW Signal Generator' is connected to the right side of a '-30 dB precision attenuator' block. This is followed by a 'Repeater under test' block. The output of the repeater is connected to another '-30 dB precision attenuator' block, which is then connected to a 'Spectrum analyser' block on the far left.
+
+Block diagram for out of band gain measurement
+
+**Figure A.3: Measuring system set-up for out of band gain.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## --- A.4 Unwanted emission: Spectrum emission mask
+
+
+
+```
+graph LR; WCDMA[WCDMA Signal Generator] --> Filter[5 MHz channel filter]; Filter --> Repeater[Repeater under test]; Repeater --> Analyser[Spectrum analyser];
+```
+
+Block diagram of the measuring system set-up for unwanted emission: spectrum emission mask. The diagram shows a WCDMA Signal Generator connected to a 5 MHz channel filter, which is connected to a Repeater under test, which is in turn connected to a Spectrum analyser.
+
+**Figure A.4: Measuring system Set-up for unwanted emission: spectrum emission mask.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## --- A.5 Unwanted emission: Spurious emission
+
+
+
+```
+graph LR; WCDMA[WCDMA Signal Generator] --> Filter[5 MHz channel filter]; Filter --> Repeater[Repeater under test]; Repeater --> Analyser[Spectrum analyser];
+```
+
+Block diagram of the measuring system set-up for unwanted emission: spurious emission. The diagram shows a WCDMA Signal Generator connected to a 5 MHz channel filter, which is connected to a Repeater under test, which is in turn connected to a Spectrum analyser.
+
+**Figure A.5: Measuring system set-up for unwanted emission: spurious emission.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## --- A.6 Modulation Accuracy: Error Vector Magnitude
+
+
+
+```
+graph LR; WCDMA[WCDMA Signal Generator] --> Repeater[Repeater under test]; Repeater --> Analyser[Signal analyser];
+```
+
+Block diagram of the measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows a WCDMA Signal Generator connected to a Repeater under test, which is in turn connected to a Signal analyser.
+
+**Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## --- A.7 Modulation Accuracy: Peak Code Domain Error Error and Relative Coder Domain Error
+
+
+
+```
+graph LR; WCDMA[WCDMA Signal Generator] --> Repeater[Repeater under test]; Repeater --> Analyser[Signal analyser];
+```
+
+Block diagram of the measuring system set-up for modulation accuracy: peak code domain error and relative code domain error. The diagram shows a WCDMA Signal Generator connected to a Repeater under test, which is in turn connected to a Signal analyser.
+
+**Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error and relative code domain error.**
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+## A.8 Input inter modulation
+
+
+
+```
+graph LR; CW[\"CW Signal Generator\"] --> Repeater[\"Repeater under test\"]; Repeater --> SA[\"Spectrum analyser\"];
+```
+
+Block diagram for input intermodulation measurement. A CW Signal Generator is connected to the input of a Repeater under test. The output of the Repeater under test is connected to a Spectrum analyser.
+
+Figure A.8: Measuring system set-up for input intermodulation.
+
+## A.9 Output Intermodulation
+
+
+
+```
+graph LR; WCDMA1[\"WCDMA Signal Generator\"] --> F1[\"5 MHz channel filter\"]; WCDMA2[\"WCDMA Signal Generator\"] --> F2[\"5 MHz channel filter\"]; F1 --> C((circulator)); F2 --> C; C --> SA[\"Spectrum analyser\"]; C --> Repeater[\"Repeater under test\"]; Repeater --> A[\"attenuator\"]; A --> C;
+```
+
+Block diagram for output intermodulation measurement. Two WCDMA Signal Generators are connected to 5 MHz channel filters. The outputs of these filters are connected to a circulator. The circulator is also connected to a Spectrum analyser and a Repeater under test. The Repeater under test is connected to an attenuator, which is connected to the circulator.
+
+Figure A.9: Measuring system set-up for Output Intermodulation.
+
+Note that a repeater is a bi-directional device. The signal generator may need protection.
+
+The 5 MHz channel filter is only required if the WCDMA signal generator does not fulfil the unwanted emission requirement for base stations (TS25.141 [11], section 6.5) with at least 10 dB margin in the described set-up.
+
+# --- Annex B (informative): Derivation of Test Requirements
+
+The Test Requirements in this specification have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances defined in subclause 5.2. When the Test Tolerance is zero, the Test Requirement will be the same as the Minimum Requirement. When the Test Tolerance is non-zero, the Test Requirements will differ from the Minimum Requirements, and the formula used for this relaxation is given in table B.1.
+
+## **Table B.1: Derivation of Test Requirements**
+
+| Clause number | Title | Minimum Requirement in TS 25.106 | Test Tolerance (TT) | Test Requirement in TS 25.143 |
+|---------------|-----------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6.1 | Maximum output power | In normal conditions
Table 6.1 | 0,7 dB, $f \leq 3,0$ GHz;
1,0 dB,
$3,0\text{ GHz} < f \leq 4,2\text{GHz}$ | Formula:
Upper limit + TT
Lower limit – TT |
+| | | In extreme conditions
Tabel 6.2 | | In normal conditions refer to Table 6.3
In extreme conditions refer to Table 6.4 |
+| 9.1.2 | Operating band unwanted emissions | Tables 9.1, 9.2, 9.3 and 9.4:
“Maximum level” = X dB | 1,5 dB, $f \leq 3,0$ GHz;
(0 dB for the additional Band II, IV, V, X, XII, XIII and XIV requirements)
1,8 dB,
$3,0\text{ GHz} < f \leq 4,2\text{GHz}$ | Formula:
Maximum level + TT
Refer to tables 9.5, 9.6, 9.7 and 9.8 |
+| 7 | Frequency stability | 7.1 minimum requirement | 12 Hz | Formula:
Relative error + TT
Refer to 7.5 Test requirements |
+| 8 | Out of Band Gain | Table 8.1: Out of band gain limits | 0,5 dB, $f \leq 3,0$ GHz;
0,8 dB,
$3,0\text{ GHz} < f \leq 4,2\text{GHz}$ | Formula:
Maximum level + TT
Refer to table 8.2 |
+| 9.2 | Spurious emissions | Tables 9.5, to 9.15 | 0 dB | |
+| 10.1 | Error Vector Magnitude | 10.1.1 Minimum requirement | 0 % | Formula:
RSS Stimulus EVM and Repeater EVM to get target EVM
Refer to 10.1.5 Test requirements |
+| 10.2 | Peak code domain error | 10.2.1 Minimum requirement | 1,1 dB | Formula:
Maximum error + TT
Refer to 10.2.5 Test requirements |
+| 10.3 | Relative code domain error | 10.3.1 Minimum requirement | 1,7 dB | Formula:
Maximum error + TT
Formula for linear offset:
Linear addition of relative error power from measurement system and repater
Formula TT:
Offset – minimum requirement.
Refer to 10.3.5 Test requirements |
+| 11 | Input intermodulation | 11.5 Minimum requirements, and Tables 11.1 and 11.2 | 1,2 dB | Maximum in-band power increase + TT
Refer to 11.5 Test requirements. |
+
+| | | | | |
+|----|------------------------|---------------------------|-----------------------------------------------------------------------|-------------------------------------------------------|
+| 12 | Output intermodulation | 12.1 Minimum requirements | 1,5 dB for spectrum emission mask.
0 dB for spurious emissions | Maximum level + TT
Refer to tables 9.5 to 9.19 |
+|----|------------------------|---------------------------|-----------------------------------------------------------------------|-------------------------------------------------------|
+
+# Annex C (informative): Acceptable uncertainty of Test Equipment
+
+This informative annex specifies the critical parameters of the components of an overall Test System (e.g. signal generators, signal analysers etc.) which are necessary when assembling a Test System which complies with subclause 5.1 Acceptable uncertainty of Test System. These Test Equipment parameters are fundamental to the accuracy of the overall Test System and are unlikely to be improved upon through System Calibration.
+
+**Table C.1: Equipment accuracy**
+
+| Test | Equipment accuracy | Test condition |
+|---------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------------------------------------|
+| 6.1 Maximum output power | Not critical | |
+| 9.1 Spectrum emission mask | Not critical | |
+| 9.2 Spurious emissions | Not critical | |
+| 11 Input intermodulation (interferer requirement) | Not critical | |
+| 7 Frequency error | $\pm 10 \text{ Hz} + \text{timebase} = 12 \text{ Hz}$ | Range 0 to 500 Hz. (This is to allow for UE range that at 0,1 PPM is larger than BTS). |
+| 10.1 Error vector magnitude | $\pm 2,5 \%$ (for single code) | $P\_Max-3$ to $P\_Max - 18 \text{ dB}$
Applies for reading from 10% to 25%. |
+| 10.2 Peak code domain error | | |
+| 10.3 Relative code domain error | | |
+| 8 Out of band gain | | |
+| 11 Input intermodulation Characteristics | | |
+| 12 Output intermodulation | | |
+
+# Annex D (informative): Change History
+
+| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item |
+|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|--------|------------------|
+| RP-31 | | | | Rel-7 version created from v6.4.0 | | | 7.0.0 | |
+| RP-31 | RP-060100 | 0053 | 2 | Introduction of operating band III to IX requirements in 25.143 | B | 6.3.0 | 7.0.0 | TEI7 |
+| RP-31 | RP-060110 | 0054 | | Correction of spurious emissions for coexistence with GSM900 in same geographic area | F | 6.3.0 | 7.0.0 | RinImp-UMTS900 |
+| RP-33 | RP-060520 | 0057 | 1 | Clean up of Spurious emissions | A | 7.0.0 | 7.1.0 | TEI5 |
+| RP-33 | RP-060521 | 0060 | 1 | New UTRA Repeater up-link spurious emissions limits for co-existence/co-location with TDD | A | 7.0.0 | 7.1.0 | TEI5 |
+| RP-34 | RP-060811 | 0063 | 1 | Corrections to input intermodulation | A | 7.1.0 | 7.2.0 | TEI5 |
+| RP-36 | RP-070370 | 0067 | | Category B spurious emission limits for UTRA Repeater | A | 7.2.0 | 7.3.0 | TEI4 |
+| RP-36 | RP-070373 | 0068 | | Introduction of operating band X into the repeater specification | B | 7.2.0 | 7.3.0 | TEI7 |
+| RP-39 | RP-080126 | 0069 | | Introduction of UMTS1500 requirements | B | 7.3.0 | 8.0.0 | RinImp8-UMTS1500 |
+| RP-42 | RP-080943 | 71 | 1 | Introduction of operating band unwanted emission | F | 8.0.0 | 8.1.0 | TEI8 |
+| RP-44 | RP-080555 | 72 | | Spurious emission testing for repeater capable of UTRA and E-UTRA | F | 8.1.0 | 8.2.0 | TEI8 |
+| RP-44 | RP-080555 | 73 | | Clean up | F | 8.1.0 | 8.2.0 | TEI8 |
+| RP-44 | RP-080555 | 74 | | Test procedure amendment | F | 8.1.0 | 8.2.0 | TEI8 |
+| RP-45 | RP-080819 | 75 | | Introduction of band XII, XIII, XIV | F | 8.2.0 | 8.3.0 | TEI8 |
+| RP-45 | RP-080819 | 76 | | Operating band unwanted emissions test tolerance correction | F | 8.2.0 | 8.3.0 | TEI8 |
+| RP-45 | RP-080819 | 77 | | CR to limit the scope to FDD only to 25.143 | F | 8.2.0 | 8.3.0 | TEI8 |
+| RP-46 | RP-091277 | 078 | | Corrections on additional spectrum emission limits for Bands XII, XIII, XIV | F | 8.3.0 | 8.4.0 | TEI8 |
+| RP-46 | RP-091281 | 079 | | Editorial corrections to 25.143 | F | 8.3.0 | 8.4.0 | TEI8 |
+| | | | | Automatic upgrade from previous Release | | 8.4.0 | 9.0.0 | |
+| RP-49 | RP-100913 | 083 | 2 | RCDE for 64QAM modulated codes for FDD Repeater | A | 9.0.0 | 9.1.0 | TEI7 |
+| RP-49 | RP-100925 | 080 | | Introduction of operating band XIX, XX and XXI and correction of band XI | F | 9.0.0 | 9.1.0 | TEI9 |
+| RP-50 | RP-101336 | 088 | | Protection of cdma and E-UTRA bands | A | 9.1.0 | 9.2.0 | TEI8 |
+| RP-50 | RP-101337 | 090 | | Removal of brackets | A | 9.1.0 | 9.2.0 | TEI8 |
+| RP-50 | RP-101347 | 084 | | Remove test settings for unwanted emissions from the minimum requirement | F | 9.1.0 | 9.2.0 | TEI9 |
+| RP-50 | RP-101347 | 085 | | Corrections to the symbols and abbreviations clause related to DTT requirement | F | 9.1.0 | 9.2.0 | TEI9 |
+| RP-50 | RP-101347 | 086 | | Co-existence with services in adjacent frequency bands | F | 9.1.0 | 9.2.0 | TEI9 |
+| RP-50 | RP-101347 | 091 | | Editorial correction to TS 25.143 | F | 9.1.0 | 9.2.0 | TEI9 |
+| RP-51 | RP-110352 | 092 | | Inclusion of E-UTRA TDD text to co-location on 25.143 | F | 9.2.0 | 10.0.0 | TEI10 |
+| RP-55 | RP-120303 | 095 | 1 | Correction on the table of Regional requirements | B | 10.0.0 | 10.1.0 | TEI10 |
+| RP-55 | RP-120303 | 096 | 1 | Introduction of operating frequency band XXII | B | 10.0.0 | 10.1.0 | TEI10 |
+| RP-55 | RP-120303 | 097 | 1 | Introduction of operating frequency band XXV and protection limits towards E-UTRA Band 23 | B | 10.0.0 | 10.1.0 | TEI10 |
+| RP-56 | RP-120783 | 099 | 2 | Update of the Definition clause with repeaters operating band definition and introduction of minor editorial changes for better alignment with BS core specification | F | 10.1.0 | 10.2.0 | TEI10 |
+| RP-56 | RP-120765 | 104 | | Additional spurious emissions requirements for PHS | A | 10.1.0 | 10.2.0 | TEI8 |
+| RP-57 | RP-121313 | 105 | 2 | Introduction of missing Spurious Emission and Input Intermodulation protection limits towards E-UTRA FDD Band 24 | F | 10.2.0 | 10.3.0 | TEI10 |
+
+| | | | | | | | | |
+|-------|-----------|------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|--------|---------------------|
+| RP-57 | RP-121312 | 109 | 1 | Repeater test uncertainties for UTRA bands above 3 GHz | F | 10.2.0 | 10.3.0 | RInImp8-UMTSLTE3500 |
+| SP-57 | - | - | - | Update to Rel-11 version (MCC) | - | 10.3.0 | 11.0.0 | - |
+| RP-58 | RP-121867 | 0113 | | Introduction of Spurious Emission limits and Input Intermodulation requirements towards missing UTRA and E-UTRA TDD frequency bands | A | 11.0.0 | 11.1.0 | TEI10 |
+| RP-58 | RP-121867 | 0114 | | Introduction of a Note on non deployment of operating bands with overlapping frequency ranges for the tables for Input Intermodulation requirements | A | 11.0.0 | 11.1.0 | TEI10 |
+| RP-58 | RP-121858 | 0115 | | Modifications of frequency ranges for E-UTRA Band 6, 18, 19 in the Tables for Spurious Emission limits and Input Intermodulation requirements | A | 11.0.0 | 11.1.0 | RInImp9-UMTSLTE800 |
+| RP-58 | RP-121867 | 0118 | | The special cases for protection of UTRA Band III and Band X in co-existence and co-location with UTRA Repeaters | A | 11.0.0 | 11.1.0 | TEI10 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25144/raw.md b/marked/Rel-11/25_series/25144/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e6e47574bc19c441c0dc46ec632b6c8c142fa466
--- /dev/null
+++ b/marked/Rel-11/25_series/25144/raw.md
@@ -0,0 +1,975 @@
+
+
+
+
+
+
+# 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 Minimum Requirements for Roaming Bands ..... | 7 |
+| 4.2 Relationship between Minimum Requirements for Roaming Bands and Test Requirements ..... | 7 |
+| 4.3 Terminal Classes ..... | 7 |
+| 4.3.1 Mechanical modes ..... | 7 |
+| 5 Frequency bands ..... | 7 |
+| 5.1 General ..... | 8 |
+| 5.2 FDD Frequency bands..... | 8 |
+| 5.3 TDD Frequency bands ..... | 8 |
+| 5.4 GSM Frequency Bands ..... | 8 |
+| 6 Transmitter Performance..... | 9 |
+| 6.1 Total Radiated Power ..... | 9 |
+| 6.1.1 Minimum requirement for roaming bands ..... | 9 |
+| 6.1.1.1 FDD ..... | 9 |
+| 6.1.1.2 GSM..... | 10 |
+| 6.1.1.3 UTRA LCR TDD..... | 10 |
+| 6.2 Total Radiated Power for LME/LEE ..... | 10 |
+| 6.2.1 Minimum requirement for roaming bands ..... | 11 |
+| 6.2.1.1 FDD ..... | 11 |
+| 6.2.1.2 GSM..... | 11 |
+| 6.2.1.3 UTRA LCR TDD..... | 12 |
+| 7 Receiver Performance ..... | 13 |
+| 7.1 Total Radiated Sensitivity ..... | 13 |
+| 7.2 Minimum requirement for roaming bands ..... | 13 |
+| 7.2.1 FDD ..... | 13 |
+| 7.2.2 GSM ..... | 14 |
+| 7.2.3 UTRA LCR TDD..... | 15 |
+| 7.3 Total Radiated Sensitivity for LME/LEE..... | 15 |
+| 7.3.1 Minimum requirement for roaming bands ..... | 15 |
+| 7.3.1.1 FDD ..... | 15 |
+| 7.3.1.2 GSM..... | 16 |
+| 7.3.1.3 UTRA LCR TDD..... | 17 |
+| Annex A (normative): Environmental conditions..... | 17 |
+| A.1 General..... | 17 |
+| A.2 Environmental requirements..... | 18 |
+| A.2.2 Temperature ..... | 18 |
+| A.2.3 Voltage ..... | 18 |
+
+**Annex B (informative): Recommended performance..... 18**
+
+B.1 General..... 18
+
+B.2 Total Radiated Power..... 18
+
+B.3 Total Radiated Sensitivity..... 21
+
+Annex C (informative): Change history..... 24
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document establishes Over the Air antenna minimum requirements for User Equipment (UE) and Mobile Station (MS).
+
+Requirements are defined for roaming bands for the speech position (beside the head) and for the data transfer position (free space). Requirements for free space are applicable to devices used in the data transfer position and consist of laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs. All bands are potential roaming bands, and the requirements for roaming bands shall therefore be fulfilled for all bands supported by a UE/MS.
+
+Requirements for operating bands are dependent on how the network has been built and are thus operator specific and can not be specified here. Recommended performance values for operating bands (Annex B) are however included in this specification for information. It should be recognised that the ability to meet the recommended performance values depends on the number of frequency bands supported by the UE/MS.
+
+# --- 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: "User Equipment (UE) radio transmission and reception (FDD)".
+- [3] 3GPP TS 45.005: "Radio transmission and reception".
+- [4] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing".
+- [5] ETSI ETR 273: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+
+# --- 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].
+
+**Primary mechanical mode:** the mode that is most often used during a call beside the head. Other mechanical modes are secondary. Every terminal has at least one primary mechanical mode.
+
+**Speech position:** UE used close to head phantom (Specific Anthropomorphic Mannequin).
+
+**Data transfer position:** UE used away from the user's head For LME and LEE devices free space configuration without head and hand phantoms is applicable.
+
+**FS:** UE used in a free space configuration.
+
+**LME:** Laptop mounted equipment (such as plug-in devices like USB dongles).
+
+**LEE:** Laptop embedded equipment (such as embedded module card embedded in notebooks).
+
+## 3.2 Symbols
+
+None
+
+## 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].
+
+| | |
+|-----|----------------------------|
+| OTA | Over the Air |
+| TRP | Total Radiated Power |
+| TRS | Total Radiated Sensitivity |
+
+# --- 4 General
+
+## 4.1 Minimum Requirements for Roaming Bands
+
+The minimum requirements for roaming bands apply only to the primary mechanical mode in the environmental conditions specified in Annex A. All bands are potential roaming bands, and a UE/MS shall fulfil the minimum requirements for roaming bands for all bands supported by the UE/MS.
+
+## 4.2 Relationship between Minimum Requirements for Roaming Bands and Test Requirements
+
+The Minimum Requirements for roaming bands given in this specification make no allowance for measurement uncertainty. The test specification 34.114 [4] Annex F 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 ETR 273 [5] Part 1 sub-part 2 section 6.5.
+
+## 4.3 Terminal Classes
+
+### 4.3.1 Mechanical modes
+
+The mechanical modes of a terminal are declared by the manufacturer. A terminal shall have at least one mechanical mode. If only one mode is supported, then this is defined as the primary.
+
+# --- 5 Frequency bands
+
+The requirements defined in this specification apply to the frequency bands defined below.
+
+## 5.1 General
+
+The information presented in this subclause is based on a chip rate of 3.84 Mcps and 1.28 Mcps (TDD).
+
+NOTE: Other chip rates may be considered in future releases.
+
+## 5.2 FDD Frequency bands
+
+- UTRA/FDD is designed to operate in the following paired bands:
+
+**Table 5.1: UTRA FDD frequency bands**
+
+| Operating Band | UL Frequencies | DL frequencies |
+|----------------|-----------------------------|-----------------------------|
+| | UE transmit, Node B receive | UE receive, Node B transmit |
+| I | 1920 - 1980 MHz | 2110 -2170 MHz |
+| II | 1850 -1910 MHz | 1930 -1990 MHz |
+| III | 1710-1785 MHz | 1805-1880 MHz |
+| IV | 1710-1755 MHz | 2110-2155 MHz |
+| V | 824 - 849 MHz | 869-894 MHz |
+| VI | 830-840 MHz | 875-885 MHz |
+| VII | 2500-2570 MHz | 2620-2690 MHz |
+| VIII | 880 - 915 MHz | 925 - 960 MHz |
+| IX | 1749.9-1784.9 MHz | 1844.9-1879.9 MHz |
+| XIX | 830 - 845MHz | 875 - 890 MHz |
+
+- b) Deployment in other frequency bands is not precluded
+
+## 5.3 TDD 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
+
+\* Used in ITU Region 2
+
+\*\*Used in ITU Region 1
+
+## 5.4 GSM Frequency Bands
+
+**Table 5.2: GSM frequency bands**
+
+| Operating Band | UL Frequencies | DL frequencies |
+|----------------|--------------------------|--------------------------|
+| | MS transmit, BTS receive | MS receive, BTS transmit |
+| GSM 850 | 824 - 849 MHz | 869-894 MHz |
+| P-GSM 900 | 890 - 915 MHz | 935 - 960 MHz |
+| E-GSM 900 | 880 - 915 MHz | 925 - 960 MHz |
+| DCS 1800 | 1710-1785 MHz | 1805-1880 MHz |
+| PCS 1900 | 1850 -1910 MHz | 1930 -1990 MHz |
+
+# --- 6 Transmitter Performance
+
+## 6.1 Total Radiated Power
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 5.2. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+$$\text{TRP}_{\text{average}} = 10 \log \left[ \frac{10^{P_{\text{leftlow}}/10} + 10^{P_{\text{leftmid}}/10} + 10^{P_{\text{lefthigh}}/10} + 10^{P_{\text{rightlow}}/10} + 10^{P_{\text{rightmid}}/10} + 10^{P_{\text{ighthigh}}/10}}{6} \right]$$
+
+Figure 6.1: Average TRP
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns "Min".
+
+$$\text{TRP}_{\text{min}} = 10 \log \left[ \min \left( 10^{P_{\text{leftlow}}/10}, 10^{P_{\text{leftmid}}/10}, 10^{P_{\text{lefthigh}}/10}, 10^{P_{\text{rightlow}}/10}, 10^{P_{\text{rightmid}}/10}, 10^{P_{\text{ighthigh}}/10} \right) \right]$$
+
+Figure 6.2: Minimum TRP
+
+### 6.1.1 Minimum requirement for roaming bands
+
+#### 6.1.1.1 FDD
+
+Minimum performance requirements for FDD roaming bands are shown in Table 6.1.
+
+**Table 6.1: TRP minimum performance requirement for FDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | | Power Class 3bis | | Power Class 4 | |
+|----------------|---------------|---------------|---------------|------|------------------|------|---------------|------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | | | Average | Min | Average | Min | Average | Min |
+| I | - | - | +15 | +13 | +15 | +13 | +13 | +11 |
+| II | - | - | +15 | +13 | +15 | +13 | +13 | +11 |
+| III | - | - | +15 | +13 | +15 | +13 | +13 | +11 |
+| IV | - | - | +15 | +13 | +15 | +13 | +13 | +11 |
+| V | - | - | +11 | +9 | +11 | +9 | +9 | +7 |
+| VI | - | - | +11 | +9 | +11 | +9 | +9 | +7 |
+| VII | - | - | +15 | +13 | +15 | +13 | +13 | +11 |
+| VIII | - | - | +12 | +10 | +12 | +10 | +10 | +8 |
+| IX | - | - | +15 | +13 | +15 | +13 | +13 | +11 |
+| XIX | - | - | +11.5 | +9.5 | +11.5 | +9.5 | +9.5 | +7.5 |
+
+NOTE: applicable for dual-mode GSM/UMTS.
+
+#### 6.1.1.2 GSM
+
+For GMSK in the speech position and the primary mechanical mode.
+
+**Table 6.2: TRP minimum performance requirement for GSM roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 4 | | Power Class 5 | |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|------|---------------|-----|
+| | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | Average | Min | Average | Min | Average | Min | Average | Min | Average | Min |
+| GSM 850 | | | | | | | 19.5 | 17.5 | | |
+| GSM 900 | | | | | | | 20.5 | 18.5 | | |
+| DCS 1800 | 21 | 19 | | | | | | | | |
+| PCS 1900 | 21 | 19 | | | | | | | | |
+
+NOTE: applicable for dual-mode GSM/UMTS.
+
+#### 6.1.1.3 UTRA LCR TDD
+
+For UTRA LCR TDD UE in the speech position and the primary mechanical mode, the TRP minimum performance requirements are listed in Table 6.3.
+
+**Table 6.3: TRP minimum performance requirement for UTRA LCR TDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 4 | |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+| | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | Average | Min | Average | Min | Average | Min | Average | Min |
+| a | - | - | +15 | +13 | - | - | - | - |
+| b | - | - | TBD | TBD | - | - | - | - |
+| c | - | - | TBD | TBD | - | - | - | - |
+| d | - | - | TBD | TBD | - | - | - | - |
+| e | - | - | +15 | +13 | - | - | - | - |
+| f | - | - | +15 | +13 | - | - | - | - |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+## 6.2 Total Radiated Power for LME/LEE
+
+Requirements in this section are stated for free space configuration and are applicable to devices used in data transfer position such as laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
+
+The average TRP of low, mid and high channel shall be higher than minimum performance requirements for roaming bands shown in section 5.2. The averaging shall be done in linear scale for the TRP results.
+
+$$\text{TRP}_{\text{average}} = 10 \log \left[ \frac{10^{P_{\text{low}}/10} + 10^{P_{\text{mid}}/10} + 10^{P_{\text{high}}/10}}{3} \right]$$
+
+**Figure 6.3: Average TRP**
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+$$\text{TRP}_{\text{min}} = 10 \log [\min(10^{P_{\text{low}}/10}, 10^{P_{\text{mid}}/10}, 10^{P_{\text{high}}/10})]$$
+
+**Figure 6.4: Minimum TRP**
+
+### 6.2.1 Minimum requirement for roaming bands
+
+#### 6.2.1.1 FDD
+
+Minimum performance requirements for FDD roaming bands are shown in Table 6.4 and Table 6.5.
+
+**Table 6.4: TRP minimum performance requirement for LME devices in the data transfers position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | | Power Class 3bis | | Power Class 4 | |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+| | Power (dBm) | Power (dBm) | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | | | Average | Min | Average | Min | Average | Min |
+| I | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| II | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| III | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| IV | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| V | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VI | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VII | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VIII | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| IX | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| XIX | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table 6.5: TRP minimum performance requirement for LEE devices in the data transfers position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | | Power Class 3bis | | Power Class 4 | |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+| | Power (dBm) | Power (dBm) | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | | | Average | Min | Average | Min | Average | Min |
+| I | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| II | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| III | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| IV | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| V | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VI | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VII | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VIII | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| IX | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| XIX | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for notebook devices.
+
+#### 6.2.1.2 GSM
+
+Minimum performance requirements for GSM roaming bands are shown in Table 6.6 and Table 6.7.
+
+**Table 6.6: TRP minimum performance requirement for LME devices in the data transfer position**
+
+| Operating band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 4 | | Power Class 5 | |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+| | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | Average | Min | Average | Min | Average | Min | Average | Min | Average | Min |
+| GSM 850 | - | - | - | - | - | - | TBD | TBD | - | - |
+| GSM 900 | - | - | - | - | - | - | TBD | TBD | - | - |
+| DCS 1800 | TBD | TBD | - | - | - | - | - | - | - | - |
+| PCS 1900 | TBD | TBD | - | - | - | - | - | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table 6.7: TRP minimum performance requirement for LEE devices in the data transfer position**
+
+| Operating band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 4 | | Power Class 5 | |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+| | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | Average | Min | Average | Min | Average | Min | Average | Min | Average | Min |
+| GSM 850 | - | - | - | - | - | - | TBD | TBD | - | - |
+| GSM 900 | - | - | - | - | - | - | TBD | TBD | - | - |
+| DCS 1800 | TBD | TBD | - | - | - | - | - | - | - | - |
+| PCS 1900 | TBD | TBD | - | - | - | - | - | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 2: Applicable for notebook devices.
+
+#### 6.2.1.3 UTRA LCR TDD
+
+For UTRA LCR TDD the TRP minimum performance requirements are listed in Table 6.8 and Table 6.9.
+
+**Table 6.8: TRP minimum performance requirement for LME devices in the data transfer position**
+
+| Operating band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 4 | |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+| | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | Average | Min | Average | Min | Average | Min | Average | Min |
+| a | - | - | TBD | TBD | - | - | - | - |
+| b | - | - | TBD | TBD | - | - | - | - |
+| c | - | - | TBD | TBD | - | - | - | - |
+| d | - | - | TBD | TBD | - | - | - | - |
+| e | - | - | TBD | TBD | - | - | - | - |
+| f | - | - | TBD | TBD | - | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table 6.9: TRP minimum performance requirement for LEE devices in the data transfer position**
+
+| Operating band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 4 | |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+| | Power (dBm) | | Power (dBm) | | Power (dBm) | | Power (dBm) | |
+| | Average | Min | Average | Min | Average | Min | Average | Min |
+| A | - | - | TBD | TBD | - | - | - | - |
+| B | - | - | TBD | TBD | - | - | - | - |
+| C | - | - | TBD | TBD | - | - | - | - |
+| D | - | - | TBD | TBD | - | - | - | - |
+| E | - | - | TBD | TBD | - | - | - | - |
+| F | - | - | TBD | TBD | - | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.
+NOTE 2: Applicable for notebook devices.
+
+# 7 Receiver Performance
+
+## 7.1 Total Radiated Sensitivity
+
+The average TRS of low, mid and high channel in beside head position for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] shall be lower than minimum performance requirements for roaming bands shown in Table 7.1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head.
+
+$$\text{TRS}_{\text{average}} = 10\log \left[ 6 / \left( \frac{1}{10^{P_{\text{leftlow}}/10}} + \frac{1}{10^{P_{\text{leftmid}}/10}} + \frac{1}{10^{P_{\text{lefthigh}}/10}} + \frac{1}{10^{P_{\text{rightlow}}/10}} + \frac{1}{10^{P_{\text{rightmid}}/10}} + \frac{1}{10^{P_{\text{ighthigh}}/10}} \right) \right]$$
+
+Figure 7.1: Average TRS
+
+In addition the maximum TRS of each measured channel in beside head position shall be better than minimum performance requirements for roaming bands shown in the columns "Max".
+
+$$\text{TRS}_{\text{max}} = 10\log \left[ \max \left( 10^{P_{\text{leftlow}}/10}, 10^{P_{\text{leftmid}}/10}, 10^{P_{\text{lefthigh}}/10}, 10^{P_{\text{rightlow}}/10}, 10^{P_{\text{rightmid}}/10}, 10^{P_{\text{ighthigh}}/10} \right) \right]$$
+
+Figure 7.2: Maximum TRS
+
+## 7.2 Minimum requirement for roaming bands
+
+### 7.2.1 FDD
+
+Minimum performance requirements for FDD roaming bands are shown in Table 7.1. The values in the tables are for with no interference.
+
+**Table 7.1: TRS minimum requirements for FDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating Band | Unit | [ior > | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|-----|
+| | | Average | Max |
+| I | dBm/3.84 MHz | -101 | -98 |
+| II | dBm/3.84 MHz | -99 | -96 |
+| III | dBm/3.84 MHz | -98 | -95 |
+| IV | dBm/3.84 MHz | -101 | -98 |
+| V | dBm/3.84 MHz | -96 | -93 |
+| VI | dBm/3.84 MHz | -96 | -93 |
+| VII | dBm/3.84 MHz | -99 | -96 |
+| VIII | dBm/3.84 MHz | -96 | -93 |
+| IX | dBm/3.84 MHz | -100 | -97 |
+| XIX | dBm/3.84 MHz | -96 | -93 |
+| NOTE 1 For Power Class 3, 3bis and 4 this shall be achieved at the maximum output power. | | | |
+| NOTE 2 For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS ][ior > [average and min] shall apply for Band IX. | | | |
+| NOTE 3 Applicable for dual-mode GSM/UMTS. | | | |
+| NOTE 4 For the UE which supports DB-DC-HSDPA configuration 2, average ][ior > level of -98 dBm/3.84 MHz and max ][ior > level of -95 dBm/3.84 MHz shall apply for Band II. | | | |
+| NOTE 5 For the UE which supports DB-DC-HSDPA configuration 2, average ][ior > level of -100 dBm/3.84 MHz and max ][ior > level of -97 dBm/3.84 MHz shall apply for Band IV. | | | |
+
+### 7.2.2 GSM
+
+Transmitted radiated sensitivity in the primary mechanical mode for TCH/FS at 2% class II (RBER) [3].
+
+**Table 7.2: TRS minimum requirements for FDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating Band | Unit | ][ior > | |
+|----------------|------|-----------------------|-------|
+| | | Average | Max |
+| GSM 850 | dBm | -98 | -95 |
+| GSM 900 | dBm | -97 | -94 |
+| DCS 1800 | dBm | -99.5 | -96.5 |
+| PCS 1900 | dBm | -98.5 | -95.5 |
+
+NOTE 1: For Power Class 1 and 4 this shall be achieved at the maximum output power.
+NOTE2: Applicable for dual-mode GSM/UMTS.
+
+Annexes are only to be used where appropriate.
+
+### 7.2.3 UTRA LCR TDD
+
+For UTRA LCR TDD UE in the speech position and the primary mechanical mode, the TRS minimum performance requirements are listed in Table 7.3.
+
+**Table 7.3: TRS minimum requirement for UTRA LCR TDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating Band | Unit | ][ior > | |
+|----------------|--------------|-----------------------|------|
+| | | Average | Max |
+| - | - | | |
+| a | dBm/1.28 MHz | -101 | -100 |
+| b | dBm/1.28 MHz | TBD | TBD |
+| c | dBm/1.28 MHz | TBD | TBD |
+| d | dBm/1.28 MHz | TBD | TBD |
+| e | dBm/1.28 MHz | -101 | -100 |
+| f | dBm/1.28 MHz | -101 | -100 |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+## 7.3 Total Radiated Sensitivity for LME/LEE
+
+Requirements in this section are stated for free space configuration and are applicable to devices used in data transfer position such as laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
+
+The average TRS of low, mid and high shall be lower than minimum performance requirements for roaming bands shown in section 5.2. The averaging shall be done in linear scale for the TRS results.
+
+$$\text{TRS}_{\text{average}} = 10 \log \left[ 3 / \left( \frac{1}{10^{P_{\text{low}}/10}} + \frac{1}{10^{P_{\text{mid}}/10}} + \frac{1}{10^{P_{\text{high}}/10}} \right) \right]$$
+
+**Figure 7.3: Average TRS**
+
+In addition the maximum TRS of each measured channel shall be better than minimum performance requirements for bands shown in the columns "Max".
+
+$$\text{TRS}_{\text{max}} = 10 \log [\max(10^{P_{\text{low}}/10}, 10^{P_{\text{mid}}/10}, 10^{P_{\text{high}}/10})]$$
+
+**Figure 7.4: Maximum TRS**
+
+### 7.3.1 Minimum requirement for roaming bands
+
+#### 7.3.1.1 FDD
+
+Minimum performance requirements for FDD roaming bands are shown in Table 7.4 and Table 7.5. The values in the tables are for with no interference.
+
+The average TRS in data transfer position for 1% BER with 12.2 kbps DL reference channel as defined in C.3 [2] shall be lower than minimum requirements for roaming bands shown in Table 7.4 and Table 7.5.
+
+**Table 7.4: TRS minimum requirements for LME devices in data transfer position**
+
+| Operating Band | Unit | or > | |
+|----------------|--------------|-----------------------|-----|
+| | | Average | Max |
+| I | dBm/3.84 MHz | TBD | TBD |
+| II | dBm/3.84 MHz | TBD | TBD |
+| III | dBm/3.84 MHz | TBD | TBD |
+| IV | dBm/3.84 MHz | TBD | TBD |
+| V | dBm/3.84 MHz | TBD | TBD |
+| VI | dBm/3.84 MHz | TBD | TBD |
+| VII | dBm/3.84 MHz | TBD | TBD |
+| VIII | dBm/3.84 MHz | TBD | TBD |
+| IX | dBm/3.84 MHz | TBD | TBD |
+| XIX | dBm/3.84 MHz | TBD | TBD |
+
+NOTE 1 For Power Class 3, 3bis and 4 this shall be achieved at the maximum output power.
+NOTE 2 Applicable for dual-mode GSM/UMTS.
+NOTE 3 Applicable for USB plug-in devices.
+
+**Table 7.5: TRS minimum requirements for LEE devices in data transfer position**
+
+| Operating Band | Unit | or > | |
+|----------------|--------------|-----------------------|-----|
+| | | Average | Max |
+| I | dBm/3.84 MHz | TBD | TBD |
+| II | dBm/3.84 MHz | TBD | TBD |
+| III | dBm/3.84 MHz | TBD | TBD |
+| IV | dBm/3.84 MHz | TBD | TBD |
+| V | dBm/3.84 MHz | TBD | TBD |
+| VI | dBm/3.84 MHz | TBD | TBD |
+| VII | dBm/3.84 MHz | TBD | TBD |
+| VIII | dBm/3.84 MHz | TBD | TBD |
+| IX | dBm/3.84 MHz | TBD | TBD |
+| XIX | dBm/3.84 MHz | TBD | TBD |
+
+NOTE 1 For Power Class 3, 3bis and 4 this shall be achieved at the maximum output power.
+NOTE 2 Applicable for dual-mode GSM/UMTS.
+NOTE 3 Applicable for notebook devices.
+
+#### 7.3.1.2 GSM
+
+For GPRS the PDTCH/CS1 at 10% BLER [3] TRS minimum performance requirements are listed in Table 7.6 and Table 7.7.
+
+**Table 7.6: TRS minimum requirements for LME devices in data transfer position**
+
+| Operating Band | Unit | or > | |
+|----------------|------|-----------------------|-----|
+| | | Average | Max |
+| GSM 850 | dBm | TBD | TBD |
+| GSM 900 | dBm | TBD | TBD |
+| DCS 1800 | dBm | TBD | TBD |
+| PCS 1900 | dBm | TBD | TBD |
+
+NOTE 1: For Power Class 1 and 4 this shall be achieved at the maximum output power.
+NOTE 2: Applicable for dual-mode GSM/UMTS.
+NOTE 3: Applicable for USB plug-in devices.
+
+**Table 7.7: TRS minimum requirements for LEE devices in data transfer position**
+
+| Operating Band | Unit | ][lor > | |
+|----------------|------|-----------------------|-----|
+| | | Average | Max |
+| GSM 850 | dBm | TBD | TBD |
+| GSM 900 | dBm | TBD | TBD |
+| DCS 1800 | dBm | TBD | TBD |
+| PCS 1900 | dBm | TBD | TBD |
+
+NOTE 1: For Power Class 1 and 4 this shall be achieved at the maximum output power.
+NOTE 2: Applicable for dual-mode GSM/UMTS.
+NOTE 3: Applicable for notebook devices.
+
+#### 7.3.1.3 UTRA LCR TDD
+
+For UTRA LCR TDD the TRS minimum performance requirements are listed in Table 7.8 and Table 7.9.
+
+**Table 7.8: TRS minimum requirements for LME devices in data transfer position**
+
+| Operating Band | Unit | ][lor > | |
+|----------------|--------------|-----------------------|-----|
+| | | Average | Max |
+| - | - | | |
+| a | dBm/1.28 MHz | TBD | TBD |
+| b | dBm/1.28 MHz | TBD | TBD |
+| c | dBm/1.28 MHz | TBD | TBD |
+| d | dBm/1.28 MHz | TBD | TBD |
+| e | dBm/1.28 MHz | TBD | TBD |
+| F | dBm/1.28 MHz | TBD | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table 7.9: TRS minimum requirements for LEE devices in data transfer position**
+
+| Operating Band | Unit | ][lor > | |
+|----------------|--------------|-----------------------|-----|
+| | | Average | Max |
+| - | - | | |
+| A | dBm/1.28 MHz | TBD | TBD |
+| B | dBm/1.28 MHz | TBD | TBD |
+| C | dBm/1.28 MHz | TBD | TBD |
+| D | dBm/1.28 MHz | TBD | TBD |
+| E | dBm/1.28 MHz | TBD | TBD |
+| F | dBm/1.28 MHz | TBD | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.
+NOTE 2: Applicable for notebook devices.
+
+# --- Annex A (normative): Environmental conditions
+
+## A.1 General
+
+This normative annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled.
+
+## --- A.2 Environmental requirements
+
+The requirements in this clause apply to all types of UE(s) and MS(s).
+
+### A.2.2 Temperature
+
+All the OTA requirements are applicable in room temperature [e.g. 25°C].
+
+### A.2.3 Voltage
+
+The UE shall be equipped with a real battery that is fully charged (in the beginning of the Test).
+
+# Annex B (informative): Recommended performance
+
+## B.1 General
+
+This annex introduces the concept of recommended OTA performance for operating bands. This requirement is not mandatory but is recommended.
+
+The concept of recommended performance is to ensure that UE/MS OTA performance is maximised in order to improve user experience and network performance. It is recognised that the ability to meet the recommended performance depends on the number of frequency bands supported by the UE/MS.
+
+## B.2 Total Radiated Power
+
+The OTA performance for FDD, GSM and UTRA LCR TDD should be greater or equal than the recommended values shown in Tables B.1, B.1a, B.1b, B.2, B.2a, B.2b and B.3, B.3a, B.3b, respectively.
+
+**Table B.1: TRP recommended performance for FDD in the speech position and the primary mechanical mode.**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 3bis | Power Class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | | | Average | Average | Average |
+| I | - | - | +18 | +18 | +16 |
+| II | - | - | +18 | +18 | +16 |
+| III | - | - | +18 | +18 | +16 |
+| IV | - | - | +18 | +18 | +16 |
+| V | - | - | +14 | +14 | +12 |
+| VI | - | - | +14.5 | +14.5 | +12.5 |
+| VII | - | - | +18 | +18 | +16 |
+| VIII | - | - | +15 | +15 | +13 |
+| IX | - | - | +18 | +18 | +16 |
+| XIX | - | - | +14.5 | +14.5 | +12.5 |
+
+NOTE: applicable for dual-mode GSM/UMTS.
+
+**Table B.1a: TRP recommended performance for FDD and LME devices in data transfer position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 3bis | Power Class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | | | Average | Average | Average |
+| I | - | - | TBD | TBD | TBD |
+| II | - | - | TBD | TBD | TBD |
+| III | - | - | TBD | TBD | TBD |
+| IV | - | - | TBD | TBD | TBD |
+| V | - | - | TBD | TBD | TBD |
+| VI | - | - | TBD | TBD | TBD |
+| VII | - | - | TBD | TBD | TBD |
+| VIII | - | - | TBD | TBD | TBD |
+| IX | - | - | TBD | TBD | TBD |
+| XIX | | | TBD | TBD | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table B.1b: TRP recommended performance for FDD and LEE devices in data transfer position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 3bis | Power Class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | | | Average | Average | Average |
+| I | - | - | TBD | TBD | TBD |
+| II | - | - | TBD | TBD | TBD |
+| III | - | - | TBD | TBD | TBD |
+| IV | - | - | TBD | TBD | TBD |
+| V | - | - | TBD | TBD | TBD |
+| VI | - | - | TBD | TBD | TBD |
+| VII | - | - | TBD | TBD | TBD |
+| VIII | - | - | TBD | TBD | TBD |
+| IX | - | - | TBD | TBD | TBD |
+| XIX | | | TBD | TBD | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 2: Applicable for notebook devices.
+
+**Table B.2: TRP recommended performance for GSM in the speech position and the primary mechanical mode.**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 4 | Power Class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | Average | Average | Average | Average | Average |
+| GSM 850 | | | | 24 | |
+| GSM 900 | | | | 24 | |
+| DCS 1800 | 24 | | | | |
+| PCS 1900 | 24 | | | | |
+
+NOTE: applicable for dual-mode GSM/UMTS.
+
+**Table B.2a: TRP recommended performance for GSM and LME devices in data transfer position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 4 | Power Class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | Average | Average | Average | Average | Average |
+| GSM 850 | - | - | - | TBD | - |
+| GSM 900 | - | - | - | TBD | - |
+| DCS 1800 | TBD | - | - | - | - |
+| PCS 1900 | TBD | - | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table B.2b: TRP recommended performance for GSM and LEE devices in data transfer position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 4 | Power Class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | Average | Average | Average | Average | Average |
+| GSM 850 | - | - | - | TBD | - |
+| GSM 900 | - | - | - | TBD | - |
+| DCS 1800 | TBD | - | - | - | - |
+| PCS 1900 | TBD | - | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 2: Applicable for notebook devices.
+
+**Table B.3: TRP recommended performance for UTRA LCR TDD in the speech position and the primary mechanical mode.**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 3bis | Power Class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | Average | Average | Average | Average | Average |
+| a | - | +18 | - | - | - |
+| b | - | TBD | - | - | - |
+| c | - | TBD | - | - | - |
+| d | - | TBD | - | - | - |
+| e | - | +18 | - | - | - |
+| f | - | +18 | - | - | - |
+
+Note : Applicable for dual-mode GSM/UTRA LCR TDD..
+
+**Table B.3a: TRP recommended performance for UTRA LCR TDD and LME devices in data transfer position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 3bis | Power Class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | Average | Average | Average | Average | Average |
+| a | - | TBD | - | - | - |
+| b | - | TBD | - | - | - |
+| c | - | TBD | - | - | - |
+| d | - | TBD | - | - | - |
+| e | - | TBD | - | - | - |
+| f | - | TBD | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD..
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table B.3b: TRP recommended performance for UTRA LCR TDD and LEE devices in data transfer position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 3bis | Power Class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+| | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) | Power (dBm) |
+| | Average | Average | Average | Average | Average |
+| a | - | TBD | - | - | - |
+| b | - | TBD | - | - | - |
+| c | - | TBD | - | - | - |
+| d | - | TBD | - | - | - |
+| e | - | TBD | - | - | - |
+| f | - | TBD | - | - | - |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD..
+NOTE 2: Applicable for notebook devices.
+
+## B.3 Total Radiated Sensitivity
+
+The OTA performance for FDD, GSM and UTRA LCR TDD should be lesser or equal than the recommended values shown in Tables B.4, B.4a, B.4b, B.5, B.5a, B.5b and B.6, B.6a, B.6b respectively.
+
+**Table B.4: TRS recommended performance for FDD in the speech position for the primary mechanical mode**
+
+| Operating Band | Unit | lo >]
Average |
+|----------------|--------------|----------------------------------|
+| I | dBm/3.84 MHz | -104 |
+| II | dBm/3.84 MHz | -102 |
+| III | dBm/3.84 MHz | -101 |
+| IV | dBm/3.84 MHz | -104 |
+| V | dBm/3.84 MHz | -99.5 |
+| VI | dBm/3.84 MHz | -101 |
+| VII | dBm/3.84 MHz | -102 |
+| VIII | dBm/3.84 MHz | -100 |
+| IX | dBm/3.84 MHz | -103 |
+| XIX | dBm/3.84 MHz | -101 |
+
+NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average lo> level of -101 dBm/3.84 shall apply for Band II.
+NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average lo> level of -103 dBm/3.84 MHz shall apply for Band IV.
+
+**Table B.4a: TRS recommended performance for FDD and LME devices in the data transfer position**
+
+| Operating Band | Unit | lo >
Average |
+|----------------|--------------|----------------------------------|
+| I | dBm/3.84 MHz | TBD |
+| II | dBm/3.84 MHz | TBD |
+| III | dBm/3.84 MHz | TBD |
+| IV | dBm/3.84 MHz | TBD |
+| V | dBm/3.84 MHz | TBD |
+| VI | dBm/3.84 MHz | TBD |
+| VII | dBm/3.84 MHz | TBD |
+| VIII | dBm/3.84 MHz | TBD |
+| IX | dBm/3.84 MHz | TBD |
+| XIX | dBm/3.84 MHz | TBD |
+
+NOTE 1: Applicable for USB plug-in devices.
+
+**Table B.4b: TRS recommended performance for FDD and LEE devices in the data transfer position**
+
+| Operating Band | Unit | lo >
Average |
+|----------------|--------------|----------------------------------|
+| I | dBm/3.84 MHz | TBD |
+| II | dBm/3.84 MHz | TBD |
+| III | dBm/3.84 MHz | TBD |
+| IV | dBm/3.84 MHz | TBD |
+| V | dBm/3.84 MHz | TBD |
+| VI | dBm/3.84 MHz | TBD |
+| VII | dBm/3.84 MHz | TBD |
+| VIII | dBm/3.84 MHz | TBD |
+| IX | dBm/3.84 MHz | TBD |
+| XIX | dBm/3.84 MHz | TBD |
+
+NOTE 1: Applicable for notebook devices.
+
+**Table B.5: TRS recommended performance for GSM in the speech position and the primary mechanical mode.**
+
+| Operating Band | Unit | or > |
+|----------------|------|-----------------------|
+| | | Average |
+| GSM 850 | dBm | -100.5 |
+| GSM 900 | dBm | -100.5 |
+| DCS 1800 | dBm | -103.5 |
+| PCS 1900 | dBm | -103.5 |
+
+NOTE: applicable for dual-mode GSM/UMTS.
+
+**Table B.5a: TRS recommended performance for GSM and LME devices in the data transfer position**
+
+| Operating Band | Unit | or > |
+|----------------|------|-----------------------|
+| | | Average |
+| GSM 850 | dBm | TBD |
+| GSM 900 | dBm | TBD |
+| DCS 1800 | dBm | TBD |
+| PCS 1900 | dBm | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 3: Applicable for USB plug-in devices.
+
+**Table B.5b: TRS recommended performance for GSM and LEE devices in the data transfer position**
+
+| Operating Band | Unit | or > |
+|----------------|------|-----------------------|
+| | | Average |
+| GSM 850 | dBm | TBD |
+| GSM 900 | dBm | TBD |
+| DCS 1800 | dBm | TBD |
+| PCS 1900 | dBm | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+NOTE 2: Applicable for notebook devices.
+
+**Table B.6: TRS recommended performance for UTRA LCR TDD in the speech position and the primary mechanical mode.**
+
+| Operating Band | Unit | or > |
+|----------------|--------------|-----------------------|
+| - | - | Average |
+| a | dBm/1.28 MHz | -105 |
+| b | dBm/1.28 MHz | TBD |
+| c | dBm/1.28 MHz | TBD |
+| d | dBm/1.28 MHz | TBD |
+| e | dBm/1.28 MHz | -105 |
+| f | dBm/1.28 MHz | -105 |
+
+NOTE: Applicable for dual-mode GSM/UTRA LCR TDD..
+
+**Table B.6a: TRS recommended performance for UTRA LCR TDD and LME devices in the data transfer position**
+
+| Operating Band | Unit | or > |
+|----------------|--------------|-----------------------|
+| - | - | Average |
+| a | dBm/1.28 MHz | TBD |
+| b | dBm/1.28 MHz | TBD |
+| c | dBm/1.28 MHz | TBD |
+| d | dBm/1.28 MHz | TBD |
+| e | dBm/1.28 MHz | TBD |
+| f | dBm/1.28 MHz | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD..
+NOTE 2: Applicable for USB plug-in devices.
+
+**Table B.6a: TRS recommended performance for UTRA LCR TDD and LEE devices in the data transfer position**
+
+| Operating Band | Unit | <REFior> |
+|-----------------------------------------------------|--------------|-----------------------|
+| - | - | Average |
+| a | dBm/1.28 MHz | TBD |
+| b | dBm/1.28 MHz | TBD |
+| c | dBm/1.28 MHz | TBD |
+| d | dBm/1.28 MHz | TBD |
+| e | dBm/1.28 MHz | TBD |
+| f | dBm/1.28 MHz | TBD |
+| NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.. | | |
+| NOTE 2: Applicable for notebook devices. | | |
+
+# Annex C (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|-----|-----|-----------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 2007-06 | RP-35 | | | | First published version following approval at TSG RAN #35 | | 7.0.0 |
+| | SP-42 | | | | Upgraded unchanged from Rel-7 | | 8.0.0 |
+| 2009-03 | RP-43 | RP-090193 | 3 | | TRP and TRS OTA requirements for UTRA bands below 1 GHz (FDD) | 8.0.0 | 8.1.0 |
+| 2009-03 | RP-43 | RP-090193 | 5 | | TRP requirements for power classes 3bis and 4 | 8.0.0 | 8.1.0 |
+| 2009-03 | RP-43 | RP-090306 | 4 | 3 | UTRA TDD OTA performance requirements | 8.1.0 | 9.0.0 |
+| 2009-05 | RP-44 | RP-090558 | 7 | 1 | UTRA LCR TDD OTA performance requirements | 9.0.0 | 9.1.0 |
+| 2010-03 | RP-47 | RP-100274 | 9 | | DB-DC-HSDPA Configuration 2 REFSENS relaxation to OTA requirements | 9.1.0 | 9.2.0 |
+| 2010-12 | RP-50 | RP-101348 | 010 | 3 | TRP and TRS requirements for GSM 850, GSM 900, DCS 1800 and PCS 1900 | 9.2.0 | 9.3.0 |
+| | SP-51 | | | | Upgraded unchanged from Rel-9 | 9.3.0 | 10.0.0 |
+| 2011-12 | RP-54 | RP-111695 | 023 | | Agreed CR R4-114706 "Adding sections for TRP and TRS requirements for LME/LEE devices" for approval | 10.0.0 | 11.0.0 |
+| 2012-03 | RP-55 | RP-120347 | 031 | 1 | TRP and TRS requirements for UMTS band XIX | 11.0.0 | 11.1.0 |
+| 2012-06 | RP-56 | RP-120795 | 032 | 1 | LME and LEE clarifications to User Equipment (UE) and Mobile Station (MS) over the air performance requirements | 11.1.0 | 11.2.0 |
+| 2012-06 | RP-56 | RP-120795 | 034 | | Clarification to TRP and TRS Requirements for LME and LEE UMTS Bands | 11.1.0 | 11.2.0 |
+| 2012-06 | RP-56 | RP-120778 | 036 | | Clarification to TRS Requirements for Roaming Bands | 11.1.0 | 11.2.0 |
+| 2012-06 | RP-56 | RP-120781 | 038 | | Frequency Band Requirements for UMTS Band XIX | 11.1.0 | 11.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25172/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-11/25_series/25172/75e4b78ee25f885d73120e3066a5253e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2c03edcfbc6162801faddaea82564080af28841
--- /dev/null
+++ b/marked/Rel-11/25_series/25172/75e4b78ee25f885d73120e3066a5253e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3445fc605335ad3bcaf1f05a814710de21eb4f6c08d19947fb28d1920bb1469
+size 56337
diff --git a/marked/Rel-11/25_series/25172/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/25_series/25172/7efae06af3af43ffe5d4b956a679cf54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..667fac1c4c3992da75c078133b48d3c7623b588a
--- /dev/null
+++ b/marked/Rel-11/25_series/25172/7efae06af3af43ffe5d4b956a679cf54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ddc891e745834531fa7317fbf609235a8672cb5601df71c139cdaa45620a921
+size 25655
diff --git a/marked/Rel-11/25_series/25172/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-11/25_series/25172/90ddf538ef276510e2b631f7b96654e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8a2dcba43ab5401765454d7354078042664f0cf
--- /dev/null
+++ b/marked/Rel-11/25_series/25172/90ddf538ef276510e2b631f7b96654e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70d9f15af4a9848b3b1952e6215248576a8fcd34610b154771089ccd13400154
+size 77723
diff --git a/marked/Rel-11/25_series/25172/raw.md b/marked/Rel-11/25_series/25172/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0699200bd82158e746927901ac23cc36f1310fb6
--- /dev/null
+++ b/marked/Rel-11/25_series/25172/raw.md
@@ -0,0 +1,1137 @@
+
+
+
+
+
+
+# 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-GANSS measurement parameters ..... | 8 |
+| 4.2.2 UE-assisted A-GANSS measurement parameters ..... | 8 |
+| 4.3 Response time ..... | 9 |
+| 4.4 Time assistance ..... | 9 |
+| 4.4.1 Use of fine time assistance ..... | 9 |
+| 4.5 RRC states..... | 9 |
+| 4.6 2D position error ..... | 9 |
+| 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..... | 10 |
+| 5.1.1 Coarse time assistance..... | 10 |
+| 5.1.1.1 Minimum requirements (coarse time assistance)..... | 11 |
+| 5.1.2 Fine time assistance..... | 11 |
+| 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)..... | 13 |
+| 5.4 Multi-path scenario ..... | 14 |
+| 5.4.1 Minimum requirements (multi-path scenario)..... | 14 |
+| 5.5 Moving scenario and periodic update ..... | 14 |
+| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 16 |
+| Annex A (normative): Test cases..... | 17 |
+| A.1 Conformance tests..... | 17 |
+| A.2 Requirement classification for statistical testing ..... | 17 |
+| Annex B (normative): Test conditions..... | 18 |
+| B.1 General..... | 18 |
+| B.1.1 Parameter values ..... | 18 |
+| B.1.2 Time assistance ..... | 18 |
+| B.1.3 GANSS reference time..... | 18 |
+| B.1.4 Reference and UE locations ..... | 19 |
+| B.1.5 Satellite constellation and assistance data..... | 19 |
+| B.1.6 Atmospheric delay..... | 19 |
+| B.1.7 Sensors ..... | 19 |
+| B.1.8 Information elements..... | 19 |
+| B.1.9 GNSS signals..... | 19 |
+| B.1.10 RESET UE POSITIONING STORED INFORMATION Message ..... | 19 |
+| B.1.11 GNSS system time offsets..... | 20 |
+
+| | | |
+|-----------------------------|--------------------------------------------------------------------------------|-----------|
+| Annex C (normative): | Propagation conditions ..... | 21 |
+| C.1 | Static propagation conditions..... | 21 |
+| C.2 | Multi-path case..... | 21 |
+| Annex D (normative): | Measurement sequence chart..... | 22 |
+| D.1 | General..... | 22 |
+| D.2 | TTFF measurement sequence chart ..... | 22 |
+| D.3 | Periodic update measurement sequence chart..... | 23 |
+| Annex E (normative): | Assistance data required for testing ..... | 25 |
+| E.1 | Introduction..... | 25 |
+| E.2 | GPS assistance data..... | 25 |
+| E.3 | GANSS assistance data..... | 25 |
+| Annex F (normative): | Converting UE-assisted measurement reports into position estimates .... | 29 |
+| F.1 | Introduction..... | 29 |
+| F.2 | UE measurement reports..... | 29 |
+| F.3 | Weighted Least Squares (WLS) position solution ..... | 30 |
+| Annex G (informative): | Change history..... | 33 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document 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 7th, 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 23rd, 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)".
+
+# 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:
+
+| | |
+|--------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| $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. |
+| G | Geometry Matrix. |
+| $\rho_{\text{GNSS}_m,i}$ | Measured pseudo-range of satellite $i$ of $\text{GNSS}_m$ . |
+| W | 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 |
+| C/A | Coarse/Acquisition |
+| DUT | Device Under Test |
+| ECEF | Earth-Centered, Earth-Fixed |
+| ECI | Earth-Centered-Inertial |
+| FDD | Frequency Division Duplex |
+| 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 |
+| IS | Interface Specification |
+
+| | |
+|--------|--------------------------------------------|
+| LOS | Line Of Sight |
+| 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 GNSS and GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS and GNSS 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 GNSS 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, and GLONASS). 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 | |
+|--------------------------------------------------------|---------|-------|--------------------|---------|---------|-------|--------|---------|------|------|
+| | E1 | 0 dB | L1 C/A | 0 dB | G1 | 0 dB | L1 C/A | 0 dB | L1 | 0 dB |
+| Signal power levels relative to reference power levels | E6 | +2 dB | L1C | +1.5 dB | G2 | -6 dB | L1C | +1.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.
+
+# 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**
+
+| 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 | ±2 |
+| Galileo | Reference high signal power level | dBm | -142 |
+| | Reference low signal power level | dBm | -147 |
+| GPS (1) | 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 |
+| 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 (1) | 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 |
+| | GNSS coarse time assistance error range | seconds | ±2 |
+| | GNSS fine time assistance error range | µs | ±10 |
+| Galileo | Reference signal power level | dBm | -147 |
+| GPS (1) | Reference signal power level | dBm | -147 |
+| GLONASS | 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 (2) |
+| | HDOP Range | - | 1.4 to 2.1 |
+| | Propagation conditions | - | AWGN |
+| | GANSS coarse time assistance error range | seconds | ±2 |
+| GPS (1) | 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 |
+| 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 (1) | GNSS 2 (1) | GNSS 3 (1) | 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. | | | | |
+
+### 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 (1) | 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 |
+
+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 (1) | GNSS 2 (1) | GNSS 3 (1) |
+| 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.
+
+### 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 |
+| | GANSS coarse time assistance error range | seconds | ±2 |
+| Galileo | Reference signal power level | dBm | -127 |
+| GPS (1) | Reference signal power level | dBm | -128.5 |
+| GLONASS | Reference signal power level | dBm | -131 |
+| 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 dimensions 1 440 m by 940 m and corner radius r = 20 m. The trajectory is defined by points I11, I12, I13, I14, I15 on the left vertical axis and I21, I22, I23, I24, I25 on the bottom horizontal axis. Arrows indicate the clockwise direction of the path.
+
+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 (1) | Reference signal power level for all satellites | dBm | -128.5 |
+| GLONASS | Reference signal power level for all satellites | dBm | -131 |
+
+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 (1) | GNSS 2 (1) | GNSS 3 (1) |
+| Single constellation | 6 | -- | -- |
+| Dual constellation | 3 | 3 | -- |
+| Triple constellation | 2 | 2 | 2 |
+
+Note1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS.
+
+### 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 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; and 2 satellites for SBAS. Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per GPS, Modernized GPS, Galileo or GLONASS 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. 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 and GLONASS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test.
+
+### 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 |
+
+**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$ |
+
+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.
+
+
+
+```
+
+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:
+
+| | |
+|------------------------------------------|------------------------------------------------------------------------|
+| MEASUREMENT COMMAND | Setup |
+| CHOICE MEASUREMENT TYPE | 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 |
+| >GANSS 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 | 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.
+
+
+
+```
+
+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 a 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:
+
+| | |
+|--------------------------------|----------------------------|
+| MEASUREMENT COMMAND | Setup |
+| CHOICE MEASUREMENT TYPE | 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 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
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 |
+
+- 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 th order term) |
+| | Doppler (1 st 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 |
+
+- 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**
+
+| GANSS | UTC Model Choice |
+|---------------------|--------------------------------|
+| 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 |
+
+- 1) **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**
+
+| Name of the IE | Fields of the IE |
+|-----------------------------------------------|-------------------------|
+| 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 :
+ - 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 :
+ - 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$$
+
+of GNSSm (calculated in 1) above), and $\hat{\mathbf{r}}_u$ 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.
+
+# Annex G (informative): Change history
+
+| Date | Meeting | Document | CR num | Rev | Comment | Version old | Version New |
+|---------|---------|-----------|--------|-----|-------------------------------------------------------------------------------------------------|-------------|-------------|
+| 2010-02 | RAN4#54 | R4-100668 | | | Text proposal for A-GANSS minimum performance requirements in UTRAN | | 0.0.1 |
+| 2010-03 | RAN#47 | RP-100133 | | | TS presented for information | 0.0.1 | 1.0.0 |
+| 2010-05 | RAN4#55 | R4-101671 | | | Minor editorial corrections and allignments with GERAN | 1.0.0 | 2.0.0 |
+| 2010-05 | RAN4#55 | R4-101671 | | | Approved by TSG RAN | 2.0.0 | 10.0.0 |
+| 2010-12 | RP-50 | RP-101350 | 001 | 1 | Addition of Galileo sensitivity numbers in the A-GANSS minimum performance requirements in UMTS | 10.0.0 | 10.1.0 |
+| 2011-04 | RP-51 | RP-110351 | 002 | | Addition of missing values and references | 10.1.0 | 10.2.0 |
+| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25202/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg b/marked/Rel-11/25_series/25202/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e141fc53484afbb1a140fe2774b831b3a5ac8d11
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff2520b9fc35abddfa6e29bcae12975c6cd4289d42205ee2b9144f7d15436807
+size 20516
diff --git a/marked/Rel-11/25_series/25202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/25_series/25202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b35630a08e8ae08ca4abcc7a205896e14fee14e7
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4ac41115e0f87c110b863c4f6e2c10eba3b6a868df9ccf6960198b092c7a7af
+size 109086
diff --git a/marked/Rel-11/25_series/25202/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/25_series/25202/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7eb43346d8cface83689462386a0366cfd536e16
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b74ece325353ff8631359fc9785797f0706a430e376d89c031d48fcda2517d1a
+size 108363
diff --git a/marked/Rel-11/25_series/25202/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/Rel-11/25_series/25202/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc4f57697c83c71f9478ff370e04d6380f8f2a15
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d78c8ab29e8d84a362a2142ef3e11d0c6f08860d3bee4beeabd0e6bfdcd8e12
+size 31948
diff --git a/marked/Rel-11/25_series/25202/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-11/25_series/25202/a289b64f80c6df506c0c55d553fc4496_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9366fdd8660552c4f7e334997c9bd0203264c650
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/a289b64f80c6df506c0c55d553fc4496_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83c532c6789eb11d9cd7b495e0b9409d88a3e0fb8cb51cd9f847a1f9df99135d
+size 55878
diff --git a/marked/Rel-11/25_series/25202/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/25_series/25202/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f208beb8e5d05c8f9de102ff5c66b2fccc2b9fd7
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8643d8db780046120dfaba6d080a6200ce019de545fe69552c426e6735c9a88
+size 110983
diff --git a/marked/Rel-11/25_series/25202/raw.md b/marked/Rel-11/25_series/25202/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..23ab7073b9b8161f5258e7e3c677592a7cd22916
--- /dev/null
+++ b/marked/Rel-11/25_series/25202/raw.md
@@ -0,0 +1,1215 @@
+
+
+
+
+
+
+# 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..... | 14 |
+| 7.1 Power Control ..... | 14 |
+| 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 ..... | 15 |
+| 7.11 E-DCH procedures ..... | 15 |
+| 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..... | 18 |
+| 11.1 | UE radio transmission and reception ..... | 18 |
+| 11.1.1 | Transmitter characteristics..... | 18 |
+| 11.1.1.1 | Transmit power ..... | 18 |
+| 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)..... | 19 |
+| 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 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is 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 * T_c$ , where $T_c$ is the chip duration ( $T_c = 1 / 7.68 * 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. A diagram showing a 10ms frame divided into 15 timeslots. The vertical axis is labeled 'frequency' and the horizontal axis is labeled 'time'. Each timeslot is represented by a box with a vertical double-headed arrow. A horizontal double-headed arrow above the frame indicates a duration of 10ms. A horizontal double-headed arrow below one timeslot indicates a duration of 5120 \* Tc. A vertical double-headed arrow on the right indicates a rate of 7.68Mcps.
+
+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. A diagram showing a burst divided into four fields: Data field, Midamble, Data field, and guard period. A horizontal double-headed arrow below the entire burst indicates a total duration of 5120 \* Tc.
+
+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.
+
+
+
+```
+
+graph LR
+ Root["m(1) - c1(1)"] --> m1c21["m(1) - c2(1)"]
+ Root --> m5c22["m(5) - c2(2)"]
+ m1c21 --> m1c41["m(1) - c4(1)"]
+ m1c21 --> m3c42["m(3) - c4(2)"]
+ m5c22 --> m5c43["m(5) - c4(3)"]
+ m5c22 --> m7c44["m(7) - c4(4)"]
+ m1c41 --> m1c81["m(1) - c8(1)"]
+ m1c41 --> m2c82["m(2) - c8(2)"]
+ m3c42 --> m3c83["m(3) - c8(3)"]
+ m3c42 --> m6c84["m(6) - c8(4)"]
+ m5c43 --> m5c85["m(5) - c8(5)"]
+ m5c43 --> m4c86["m(4) - c8(6)"]
+ m7c44 --> m7c87["m(7) - c8(7)"]
+ m7c44 --> m8c88["m(8) - c8(8)"]
+ m1c81 --> m1c161["m(1) - c16(1)"]
+ m1c81 --> m9c162["m(9) - c16(2)"]
+ m2c82 --> m2c163["m(2) - c16(3)"]
+ m2c82 --> m10c164["m(10) - c16(4)"]
+ m3c83 --> m3c165["m(3) - c16(5)"]
+ m3c83 --> m11c166["m(11) - c16(6)"]
+ m6c84 --> m6c167["m(6) - c16(7)"]
+ m6c84 --> m14c168["m(14) - c16(8)"]
+ m5c85 --> m5c169["m(5) - c16(9)"]
+ m5c85 --> m13c1610["m(13) - c16(10)"]
+ m4c86 --> m4c1611["m(4) - c16(11)"]
+ m4c86 --> m12c1612["m(12) - c16(12)"]
+ m7c87 --> m7c1613["m(7) - c16(13)"]
+ m7c87 --> m15c1614["m(15) - c16(14)"]
+ m8c88 --> m8c1615["m(8) - c16(15)"]
+ m8c88 --> m16c1616["m(16) - c16(16)"]
+ m1c161 --> m1c321["m(1) - c32(1)"]
+ m1c161 --> m1c322star["m(1) - c32(2)*"]
+ m9c162 --> m9c323["m(9) - c32(3)"]
+ m9c162 --> m9c324star["m(9) - c32(4)*"]
+ m2c163 --> m2c325["m(2) - c32(5)"]
+ m2c163 --> m2c326star["m(2) - c32(6)*"]
+ m10c164 --> m10c327["m(10) - c32(7)"]
+ m10c164 --> m10c328star["m(10) - c32(8)*"]
+ m3c165 --> m3c329["m(3) - c32(9)"]
+ m3c165 --> m3c3210star["m(3) - c32(10)*"]
+ m11c166 --> m11c3211["m(11) - c32(11)"]
+ m11c166 --> m11c3212star["m(11) - c32(12)*"]
+ m6c167 --> m6c3213["m(6) - c32(13)"]
+ m6c167 --> m6c3214star["m(6) - c32(14)*"]
+ m14c168 --> m14c3215["m(14) - c32(15)"]
+ m14c168 --> m14c3216star["m(14) - c32(16)*"]
+ m5c169 --> m5c3217["m(5) - c32(17)"]
+ m5c169 --> m5c3218star["m(5) - c32(18)*"]
+ m13c1610 --> m13c3219["m(13) - c32(19)"]
+ m13c1610 --> m13c3220star["m(13) - c32(20)*"]
+ m4c1611 --> m4c3221["m(4) - c32(21)"]
+ m4c1611 --> m4c3222star["m(4) - c32(22)*"]
+ m12c1612 --> m12c3223["m(12) - c32(23)"]
+ m12c1612 --> m12c3224star["m(12) - c32(24)*"]
+ m7c1613 --> m7c3225["m(7) - c32(25)"]
+ m7c1613 --> m7c3226star["m(7) - c32(26)*"]
+ m15c1614 --> m15c3227["m(15) - c32(27)"]
+ m15c1614 --> m15c3228star["m(15) - c32(28)*"]
+ m8c1615 --> m8c3229["m(8) - c32(29)"]
+ m8c1615 --> m8c3230star["m(8) - c32(30)*"]
+ m16c1616 --> m16c3231["m(16) - c32(31)"]
+ m16c1616 --> m16c3232star["m(16) - c32(32)*"]
+
+```
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for KCell = 16. The tree starts with m(1) - c1(1) at the root, branching into m(1) - c2(1) and m(5) - c2(2). It further branches through various levels of midambles (m) and codes (c) until it reaches the final spreading codes (c32) at the leaf nodes.
+
+Figure 6.3.1: Association of Midambles to Spreading Codes for KCell = 16
+
+
+
+```
+
+ graph LR
+ Root["m(1) - c1(1)"] --> m1c2["m(1) - c2(1)"]
+ Root --> m5c2["m(5) - c2(2)"]
+
+ m1c2 --> m1c4["m(1) - c4(1)"]
+ m1c2 --> m3c4["m(3) - c4(2)"]
+
+ m5c2 --> m5c4["m(5) - c4(3)"]
+ m5c2 --> m7c4["m(7) - c4(4)"]
+
+ m1c4 --> m1c8["m(1) - c8(1)"]
+ m1c4 --> m2c8["m(2) - c8(2)"]
+
+ m3c4 --> m3c8["m(3) - c8(3)"]
+ m3c4 --> m6c8["m(6) - c8(4)"]
+
+ m5c4 --> m5c8["m(5) - c8(5)"]
+ m5c4 --> m4c8["m(4) - c8(6)"]
+
+ m7c4 --> m7c8["m(7) - c8(7)"]
+ m7c4 --> m8c8["m(8) - c8(8)"]
+
+ m1c8 --> m1c16_1["m(1) - c16(1)"]
+ m1c8 --> m1c16_2["m(1) - c16(2)*"]
+
+ m2c8 --> m2c16_3["m(2) - c16(3)"]
+ m2c8 --> m2c16_4["m(2) - c16(4)*"]
+
+ m3c8 --> m3c16_5["m(3) - c16(5)"]
+ m3c8 --> m3c16_6["m(3) - c16(6)*"]
+
+ m6c8 --> m6c16_7["m(6) - c16(7)"]
+ m6c8 --> m6c16_8["m(6) - c16(8)*"]
+
+ m5c8 --> m5c16_9["m(5) - c16(9)"]
+ m5c8 --> m5c16_10["m(5) - c16(10)*"]
+
+ m4c8 --> m4c16_11["m(4) - c16(11)"]
+ m4c8 --> m4c16_12["m(4) - c16(12)*"]
+
+ m7c8 --> m7c16_13["m(7) - c16(13)"]
+ m7c8 --> m7c16_14["m(7) - c16(14)*"]
+
+ m8c8 --> m8c16_15["m(8) - c16(15)"]
+ m8c8 --> m8c16_16["m(8) - c16(16)*"]
+
+ m1c16_1 --> m1c32_1["m(1) - c32(1)"]
+ m1c16_1 --> m1c32_2["m(1) - c32(2)*"]
+ m1c16_2 --> m1c32_3["m(1) - c32(3)*"]
+ m1c16_2 --> m1c32_4["m(1) - c32(4)*"]
+
+ m2c16_3 --> m2c32_5["m(2) - c32(5)"]
+ m2c16_3 --> m2c32_6["m(2) - c32(6)*"]
+ m2c16_4 --> m2c32_7["m(2) - c32(7)*"]
+ m2c16_4 --> m2c32_8["m(2) - c32(8)*"]
+
+ m3c16_5 --> m3c32_9["m(3) - c32(9)"]
+ m3c16_5 --> m3c32_10["m(3) - c32(10)*"]
+ m3c16_6 --> m3c32_11["m(3) - c32(11)*"]
+ m3c16_6 --> m3c32_12["m(3) - c32(12)*"]
+
+ m6c16_7 --> m6c32_13["m(6) - c32(13)"]
+ m6c16_7 --> m6c32_14["m(6) - c32(14)*"]
+ m6c16_8 --> m6c32_15["m(6) - c32(15)*"]
+ m6c16_8 --> m6c32_16["m(6) - c32(16)*"]
+
+ m5c16_9 --> m5c32_17["m(5) - c32(17)"]
+ m5c16_9 --> m5c32_18["m(5) - c32(18)*"]
+ m5c16_10 --> m5c32_19["m(5) - c32(19)*"]
+ m5c16_10 --> m5c32_20["m(5) - c32(20)*"]
+
+ m4c16_11 --> m4c32_21["m(4) - c32(21)"]
+ m4c16_11 --> m4c32_22["m(4) - c32(22)*"]
+ m4c16_12 --> m4c32_23["m(4) - c32(23)*"]
+ m4c16_12 --> m4c32_24["m(4) - c32(24)*"]
+
+ m7c16_13 --> m7c32_25["m(7) - c32(25)"]
+ m7c16_13 --> m7c32_26["m(7) - c32(26)*"]
+ m7c16_14 --> m7c32_27["m(7) - c32(27)*"]
+ m7c16_14 --> m7c32_28["m(7) - c32(28)*"]
+
+ m8c16_15 --> m8c32_29["m(8) - c32(29)"]
+ m8c16_15 --> m8c32_30["m(8) - c32(30)*"]
+ m8c16_16 --> m8c32_31["m(8) - c32(31)*"]
+ m8c16_16 --> m8c32_32["m(8) - c32(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 various levels of midambles (m) and codes (c) until it reaches the final spreading codes (c\_32) at the leaf nodes.
+
+Figure 6.3.2: Association of Midambles to Spreading Codes for $K_{Cell} = 8$
+
+
+
+```
+
+graph LR
+ Root["m(1) - c1(1)"] --- m1c2["m(1) - c2(1)"]
+ Root --- m5c2["m(5) - c2(2)"]
+
+ m1c2 --- m1c4_1["m(1) - c4(1)"]
+ m1c2 --- m3c4_2["m(3) - c4(2)"]
+
+ m5c2 --- m5c4_3["m(5) - c4(3)"]
+ m5c2 --- m7c4_4["m(7) - c4(4)"]
+
+ m1c4_1 --- m1c8_1["m(1) - c8(1)"]
+ m1c4_1 --- m1c8_2["m(1) - c8(2)*"]
+
+ m3c4_2 --- m3c8_3["m(3) - c8(3)"]
+ m3c4_2 --- m3c8_4["m(3) - c8(4)*"]
+
+ m5c4_3 --- m5c8_5["m(5) - c8(5)"]
+ m5c4_3 --- m5c8_6["m(5) - c8(6)*"]
+
+ m7c4_4 --- m7c8_7["m(7) - c8(7)"]
+ m7c4_4 --- m7c8_8["m(7) - c8(8)*"]
+
+ m1c8_1 --- m1c16_1["m(1) - c16(1)"]
+ m1c8_1 --- m1c16_2["m(1) - c16(2)*"]
+ m1c8_2 --- m1c16_3["m(1) - c16(3)*"]
+ m1c8_2 --- m1c16_4["m(1) - c16(4)*"]
+
+ m3c8_3 --- m3c16_5["m(3) - c16(5)"]
+ m3c8_3 --- m3c16_6["m(3) - c16(6)*"]
+ m3c8_4 --- m3c16_7["m(3) - c16(7)*"]
+ m3c8_4 --- m3c16_8["m(3) - c16(8)*"]
+
+ m5c8_5 --- m5c16_9["m(5) - c16(9)"]
+ m5c8_5 --- m5c16_10["m(5) - c16(10)*"]
+ m5c8_6 --- m5c16_11["m(5) - c16(11)*"]
+ m5c8_6 --- m5c16_12["m(5) - c16(12)*"]
+
+ m7c8_7 --- m7c16_13["m(7) - c16(13)"]
+ m7c8_7 --- m7c16_14["m(7) - c16(14)*"]
+ m7c8_8 --- m7c16_15["m(7) - c16(15)*"]
+ m7c8_8 --- m7c16_16["m(7) - c16(16)*"]
+
+ m1c16_1 --- m1c32_1["m(1) - c32(1)"]
+ m1c16_1 --- m1c32_2["m(1) - c32(2)*"]
+ m1c16_2 --- m1c32_3["m(1) - c32(3)*"]
+ m1c16_2 --- m1c32_4["m(1) - c32(4)*"]
+ m1c16_3 --- m1c32_5["m(1) - c32(5)*"]
+ m1c16_3 --- m1c32_6["m(1) - c32(6)*"]
+ m1c16_4 --- m1c32_7["m(1) - c32(7)*"]
+ m1c16_4 --- m1c32_8["m(1) - c32(8)*"]
+
+ m3c16_5 --- m3c32_9["m(3) - c32(9)"]
+ m3c16_5 --- m3c32_10["m(3) - c32(10)*"]
+ m3c16_6 --- m3c32_11["m(3) - c32(11)*"]
+ m3c16_6 --- m3c32_12["m(3) - c32(12)*"]
+ m3c16_7 --- m3c32_13["m(3) - c32(13)*"]
+ m3c16_7 --- m3c32_14["m(3) - c32(14)*"]
+ m3c16_8 --- m3c32_15["m(3) - c32(15)*"]
+ m3c16_8 --- m3c32_16["m(3) - c32(16)*"]
+
+ m5c16_9 --- m5c32_17["m(5) - c32(17)"]
+ m5c16_9 --- m5c32_18["m(5) - c32(18)*"]
+ m5c16_10 --- m5c32_19["m(5) - c32(19)*"]
+ m5c16_10 --- m5c32_20["m(5) - c32(20)*"]
+ m5c16_11 --- m5c32_21["m(5) - c32(21)*"]
+ m5c16_11 --- m5c32_22["m(5) - c32(22)*"]
+ m5c16_12 --- m5c32_23["m(5) - c32(23)*"]
+ m5c16_12 --- m5c32_24["m(5) - c32(24)*"]
+
+ m7c16_13 --- m7c32_25["m(7) - c32(25)"]
+ m7c16_13 --- m7c32_26["m(7) - c32(26)*"]
+ m7c16_14 --- m7c32_27["m(7) - c32(27)*"]
+ m7c16_14 --- m7c32_28["m(7) - c32(28)*"]
+ m7c16_15 --- m7c32_29["m(7) - c32(29)*"]
+ m7c16_15 --- m7c32_30["m(7) - c32(30)*"]
+ m7c16_16 --- m7c32_31["m(7) - c32(31)*"]
+ m7c16_16 --- m7c32_32["m(7) - c32(32)*"]
+
+```
+
+Figure 6.3.3: Association of Midambles to Spreading Codes for K\_Cell = 4. The diagram shows a hierarchical tree structure starting from a root node m^(1) - c\_1^(1). It branches into two main paths: m^(1) - c\_2^(1) and m^(5) - c\_2^(2). Each path further branches into midambles m^(1) - c\_4^(1), m^(3) - c\_4^(2), m^(5) - c\_4^(3), and m^(7) - c\_4^(4). These are then split into c\_8 and c\_16 midambles, which finally lead to 32 spreading codes c\_32^(1) through c\_32^(32).
+
+**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.
+
+| Transport Channels | Physical Channels |
+|--------------------|--------------------------------------------------------|
+| 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.4 Mbps) and a higher capability E-DCH UE at 7.68 Mcps (17.7 Mbps). 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_{\text{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_{ouu}$ mean power (modulated) | -53
(for $F_{uw}$ offset $\pm 20$ MHz) | -41
(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}$
For operation in frequency bands as defined in subclause 5.2(a) of TS25.102 [10] | 1840 < f < 1870
1950 < f < 1980
2055 < f < 2085 | 1815 < f < 1840
2085 < f < 2110 | 1 < f < 1815
2110 < f < 12750 | MHz |
+| $F_{uw}$
For operation in frequency bands as defined in subclause 5.2(b) of TS25.102 [10] | 1790 < f < 1820
2020 < f < 2050 | 1765 < f < 1790
2050 < f < 2075 | 1 < f < 1765
2075 < f < 12750 | MHz |
+| $F_{uw}$
For operation in frequency bands as defined in subclause 5.2(c) of TS25.102 [10] | 1850 < f < 1880
1960 < f < 1990 | 1825 < f < 1850
1990 < f < 2015 | 1 < f < 1825
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
1.92 GHz – 2.01 GHz and
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
2.01 GHz – 2.025 GHz and
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{offset}_{\max}}$ 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{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 -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, 15.0, and f_offset_max. The mask is defined by three power levels: P = 43 dBm (top line), P = 39 dBm (middle line), and P = 31 dBm (bottom line). The mask starts at -17 dBm for 5 MHz ≤ Δf < 5.2 MHz, then decreases linearly to -29 dBm at 6.015 MHz, and then to -16 dBm at 6.5 MHz. For Δf ≥ 15 MHz, the mask is P - 59 dB.](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, 15.0, and f\_offset\_max. The mask is defined by three power levels: P = 43 dBm (top line), P = 39 dBm (middle line), and P = 31 dBm (bottom line). The mask starts at -17 dBm for 5 MHz ≤ Δf < 5.2 MHz, then decreases linearly to -29 dBm at 6.015 MHz, and then to -16 dBm at 6.5 MHz. For Δf ≥ 15 MHz, the mask is P - 59 dB.
+
+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,
2010 – 2025 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1880 – 1900 MHz,
1990 – 2010 MHz,
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,
1980 – 1990 MHz,
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,
1990 – 2010 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1 – 1830 MHz,
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,
1930 – 1950 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code |
+| 1 – 1890 MHz,
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,
2010 – 2025 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1880 – 1900 MHz,
1990 – 2010 MHz,
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,
1980 – 1990 MHz,
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,
1990 – 2010 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1 – 1830 MHz,
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,
1930 – 1950 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code |
+| 1 – 1890 MHz,
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
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
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. |
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------------|-----------|------|-----|------------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 2005-04 | RAN1#40 bis | R1-050343 | | | Frame Structure for 7.68Mcps TDD Option | - | 0.0.1 |
+| 2005-04 | RAN1#40 bis | R1-050344 | | | Timing Advance for 7.68Mcps TDD Option | - | 0.0.1 |
+| 2005-05 | RAN1#41 | | | | V0.0.1 approved by RAN1. | 0.0.1 | 0.1.0 |
+| 2005-08 | RAN1#41 | R1-050455 | | | Services offered to higher layers by 7.68Mcps TDD option | 0.1.0 | 0.1.1 |
+| 2005-08 | RAN1#41 | R1-050556 | | | Spreading factors and burst types for 7.68Mcps TDD option | 0.1.0 | 0.1.1 |
+| 2005-09 | RAN1#42 | R1-050974 | | | V0.1.1 approved by RAN1 | 0.1.1 | 0.2.0 |
+| 2005-09 | RAN1#42 | R1-050858 | | | 7.68Mcps TDD: Mapping of transport channels to physical channels | 0.2.0 | 0.2.1 |
+| 2005-09 | RAN1#42 | R1-050859 | | | 7.68Mcps TDD: Paging aspects | 0.2.0 | 0.2.1 |
+| 2005-09 | RAN1#42 | R1-050860 | | | 7.68Mcps TDD: PRACH Aspects | 0.2.0 | 0.2.1 |
+| 2005-09 | RAN1#42 | R1-050861 | | | 7.68Mcps TDD: midamble aspects | 0.2.0 | 0.2.1 |
+| 2005-09 | RAN1#42 | R1-050862 | | | 7.68Mcps TDD: Transmission of TPC and TFCI | 0.2.0 | 0.2.1 |
+| 2005-09 | RAN1#42 | R1-050930 | | | Synchronisation aspects for 7.68Mcps TDD option | 0.2.0 | 0.2.1 |
+| 2005-09 | RAN1#42 | R1-050931 | | | 7.68Mcps TDD: Transmitter power control | 0.2.0 | 0.2.1 |
+| 2005-10 | RAN1#42 bis | R1-051251 | | | V0.2.1 approved by RAN1 | 0.2.1 | 0.3.0 |
+| 2005-10 | RAN1#42 bis | R1-051223 | | | 7.68Mcps TDD option: HSDPA aspects of TS25.221 | 0.3.0 | 0.3.1 |
+| 2005-10 | RAN1#42 bis | R1-051224 | | | SCH channel definition for the 7.68Mcps TDD option | 0.3.0 | 0.3.1 |
+| 2005-10 | RAN1#42 bis | R1-051226 | | | Physical layer procedures for the 7.68Mcps TDD option | 0.3.0 | 0.3.1 |
+| 2005-10 | RAN1#42 bis | R1-051228 | | | Tx diversity for the 7.68Mcps TDD option | 0.3.0 | 0.3.1 |
+| 2005-10 | RAN1#42 bis | R1-051230 | | | 7.68Mcps TDD option: beacon channel aspects | 0.3.0 | 0.3.1 |
+| 2005-11 | RAN1#43 | R1-051564 | | | V0.3.1 approved by RAN1 | 0.3.1 | 0.4.0 |
+| 2005-11 | RAN1#43 | R1-051520 | | | Transport channel processing for the 7.68Mcps TDD option | 0.4.0 | 0.4.1 |
+| 2005-11 | RAN1#43 | R1-051522 | | | Spreading and modulation for the 7.68Mcps TDD option | 0.4.0 | 0.4.1 |
+| 2005-11 | RAN1#43 | R1-051620 | | | Updated to v0.4.2 | 0.4.1 | 0.4.2 |
+| 2005-11 | TSG-RAN#30 | RP-050829 | | | v1.0.0 created for presentation to RAN plenary for information | 0.4.2 | 1.0.0 |
+| 2006-02 | RAN1#44 | R1-060628 | | | MICH Aspects for the 7.68Mcps TDD option | 1.0.0 | 1.1.0 |
+| 2006-02 | RAN1#44 | R1-060629 | | | IPDL Aspects for the 7.68Mcps TDD option | 1.0.0 | 1.1.0 |
+| 2006-02 | RAN1#44 | R1-060728 | | | Response LS from RAN3 on input to TS25.202 | 1.1.0 | 1.1.1 |
+| 2006-02 | RAN1#44 | R1-060744 | | | Response LS from RAN2 on input to TS25.202 | 1.1.0 | 1.1.1 |
+| 2006-02 | RAN1#44 | R1-060736 | | | Response LS from RAN4 on input to TS25.202 | 1.1.0 | 1.1.1 |
+| 2006-03 | RAN 31 | RP-060117 | | | v2.0.0 created for presentation to RAN plenary for approval | 1.1.1 | 2.0.0 |
+| 20/03/06 | RAN 31 | RP-060117 | - | - | Approved as v7.0.0 to put under change control | 2.0.0 | 7.0.0 |
+| 29/09/06 | RAN 33 | RP-060493 | 0001 | - | Introduction of E-DCH for 7.68Mcps TDD | 7.0.0 | 7.1.0 |
+| 04/03/08 | RAN 39 | - | - | - | Creation of Release 8 further to RAN 39 decision | 7.1.0 | 8.0.0 |
+| 07/12/09 | SP 46 | - | - | - | Creation of Release 9 further to SA 46 decision | 8.0.0 | 9.0.0 |
+| 21/03/11 | SP 51 | - | - | - | Creation of Release 10 further to SA 51 decision | 9.0.0 | 10.0.0 |
+| 2012-09 | SP 57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25211/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/25_series/25211/00504fc688ebcf131ccbeff94dfc9939_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ceff074dcc18b422800894c9126d917fd823c6a
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/00504fc688ebcf131ccbeff94dfc9939_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86d08a7d6293edbbc97bbb1eddc9b01408da90b21a0cb7c2c13929df49a5e21b
+size 42268
diff --git a/marked/Rel-11/25_series/25211/0977b81510f7649846289ee785d20e74_img.jpg b/marked/Rel-11/25_series/25211/0977b81510f7649846289ee785d20e74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0343d9c06fb12a31b0046922976d0197455ce54a
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/0977b81510f7649846289ee785d20e74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bd2bfaeaa72807ce9e8ae5d06f9d0c56387da7b5c9d3eeaf200792b7c4d9cd0
+size 36124
diff --git a/marked/Rel-11/25_series/25211/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Rel-11/25_series/25211/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7455f1135ab816e5aa90500be62d87c6c80a012c
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40ebcdbbb06d958b4003ace91f4399824c6875b1703d96ddfcaa12e2ab4b632d
+size 26412
diff --git a/marked/Rel-11/25_series/25211/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/25_series/25211/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40838935e33b224ccc3731f8b3d4e643e6eb65e3
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:808ab8add45622150a8c4540efc1ee625bc67eec0b6448a6b8e2b91e5dd2f57c
+size 40253
diff --git a/marked/Rel-11/25_series/25211/0b452c5334567cbdc22ee9817e1246f5_img.jpg b/marked/Rel-11/25_series/25211/0b452c5334567cbdc22ee9817e1246f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44633623e896abf09a7d2b043f396a01f7ae77fd
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/0b452c5334567cbdc22ee9817e1246f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08cd647250029179cdd8275bac2547bfffc68236f4a67d3e89a833ba3aa69b71
+size 105432
diff --git a/marked/Rel-11/25_series/25211/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-11/25_series/25211/0f26e70157bd4c45f825795cdcd20fbd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c23f5538bac611a62380a69170909b39c68ce095
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/0f26e70157bd4c45f825795cdcd20fbd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:568b4781ec87a2d5ddb659b3a24839aee77525718f0bbd63b19453871391cb58
+size 164392
diff --git a/marked/Rel-11/25_series/25211/15906392337ec83a921988b52f102a44_img.jpg b/marked/Rel-11/25_series/25211/15906392337ec83a921988b52f102a44_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e43e837dba6b863c1dc3c820a166f9da121ea967
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/15906392337ec83a921988b52f102a44_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:449e2fba2083a6ddf3c47122912bfdd922ba8a01be8047ffbadedfe30e5a3ba1
+size 7042
diff --git a/marked/Rel-11/25_series/25211/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/25_series/25211/187d05bf7ead21e1394b61320d8b3632_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f19e399bb117913a3b09e85d595b553c981c0a9d
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/187d05bf7ead21e1394b61320d8b3632_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f53acea18018b46005fbdb57c46071873a5da2777c5c10ab6ba1aff2ee58658
+size 15513
diff --git a/marked/Rel-11/25_series/25211/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg b/marked/Rel-11/25_series/25211/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8123feeed631a47d9ae89aa91d61d38690d0934
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b492441089b2290191700adb321e37b315265eecac5a808332412b1296cbd2f
+size 43192
diff --git a/marked/Rel-11/25_series/25211/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/Rel-11/25_series/25211/1e8c50ad4fca7f315a407347dd5091cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22958986d066af81884db8c21ed12530b99a2243
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/1e8c50ad4fca7f315a407347dd5091cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a90385a08ad0ee22a84bd1c7f3d951c8768918a23ef527b73a49ed27c1d3ecd
+size 35795
diff --git a/marked/Rel-11/25_series/25211/26e334e61dd059cff029338a2a604d8d_img.jpg b/marked/Rel-11/25_series/25211/26e334e61dd059cff029338a2a604d8d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f87886969be640d35fe28bc3e38e34773d6b990d
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/26e334e61dd059cff029338a2a604d8d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5026d64278024674dc6ab73ec0add958542748166056b645bca682cf273544a
+size 44289
diff --git a/marked/Rel-11/25_series/25211/2c3bf03decbeb6a8038deccc5a796b46_img.jpg b/marked/Rel-11/25_series/25211/2c3bf03decbeb6a8038deccc5a796b46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5bc29f4fe1a910c0c421b5f5da7d67c5dca054c8
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/2c3bf03decbeb6a8038deccc5a796b46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e86b4724fc9d8cee579d021f3e008ec11a9c30e559ea121881d39a394907009
+size 78324
diff --git a/marked/Rel-11/25_series/25211/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/Rel-11/25_series/25211/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..445774f5bebf7af8dee0bb8b6884eef3db0c43e2
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0553ac92b375fafc528851c49076737dd1cf4eed7b0dd2167c8977905b25e91a
+size 39753
diff --git a/marked/Rel-11/25_series/25211/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-11/25_series/25211/408c4798ea60469e0728a7cbbd598668_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c696a30f13aa32a0089ffcd93ba4f3a804f4d41
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/408c4798ea60469e0728a7cbbd598668_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbe553673d3095904e13f4683d222219c389c1c8f26be556e48be038c27b62c3
+size 24013
diff --git a/marked/Rel-11/25_series/25211/42c65f5cb106938992fc73c05c8713d2_img.jpg b/marked/Rel-11/25_series/25211/42c65f5cb106938992fc73c05c8713d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c796be407a88b328cb51dc9c8255694185084200
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/42c65f5cb106938992fc73c05c8713d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2abaa6f7594f88d3de17bec307563e533dafcc851b84e3da68d258c7e2d35009
+size 18747
diff --git a/marked/Rel-11/25_series/25211/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/25_series/25211/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aba37540041b6eb9fda98083a2ffb8f8fe4f079f
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9e43db64021fc3e25cc4d18648ab346ba5c3d4e683d9ddf73de6a2a663e0e53b
+size 41588
diff --git a/marked/Rel-11/25_series/25211/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg b/marked/Rel-11/25_series/25211/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc3afefa56d30dbce4e7d14a0a4d993e88f78dd0
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb987b2586ffdb5431bd9e452b2d041e64642be2059be699511a768c9741b9e0
+size 26574
diff --git a/marked/Rel-11/25_series/25211/6584b95e34ea1f0b67144aa841db0863_img.jpg b/marked/Rel-11/25_series/25211/6584b95e34ea1f0b67144aa841db0863_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d66f4dce3cc4d755f5eb70b559357bb34821fdc
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/6584b95e34ea1f0b67144aa841db0863_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85f6b7a1e20a74dd02a17dbc240eeb3e4784046ede6f15960a74ff2541b13bfa
+size 32551
diff --git a/marked/Rel-11/25_series/25211/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/marked/Rel-11/25_series/25211/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0247f9845bb847a422922e8b1282922bd1f75aca
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da9b737c532332405e3655463af36762b0bd4218c6162fcb5b4db75c956307e9
+size 40265
diff --git a/marked/Rel-11/25_series/25211/69f52512bb7387a5dc9f952279513019_img.jpg b/marked/Rel-11/25_series/25211/69f52512bb7387a5dc9f952279513019_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c25f19a17db953028e443072844e8b17e1ad7e8
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/69f52512bb7387a5dc9f952279513019_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed57bcaeef735221c360895629c87869c0ace2d7c8168486b6e4a7ec37845a03
+size 53376
diff --git a/marked/Rel-11/25_series/25211/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-11/25_series/25211/6be06b7dc72bb42afcb3465394667c3b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9f817715395a4f9d603e97787634e0cd5117f20
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/6be06b7dc72bb42afcb3465394667c3b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2872582ed9f451e56febcf0f5916de567cceba3e303b0a41b110a9794dad4db
+size 40935
diff --git a/marked/Rel-11/25_series/25211/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-11/25_series/25211/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e9a9786733621f70c26458039d95fef1e9c65f3
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff3f755a5d417a08a796dff6dac1940f9b1cbebf5266dfbd7e55f37dd8f06d8c
+size 65073
diff --git a/marked/Rel-11/25_series/25211/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/25_series/25211/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a580050ab2f75a1e48014bc31581e4df6946753
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c82b4f0f0551ab3f804493e45bdf6a73ceba10123640b9368f1c6fe41e44cbf8
+size 42804
diff --git a/marked/Rel-11/25_series/25211/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/25_series/25211/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1cb583106ead347b84eb6dd42b8bcdf1d839f3f4
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8a26742cefb1985ea4c6d0d2b73e4a64e05d5d696ff9ef5cff9a7f6bf502fa9
+size 21276
diff --git a/marked/Rel-11/25_series/25211/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/25_series/25211/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e997afbd926a0503d99a603e94d14f417f248a6
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9cdee591bcc210d54af07575fa57034cfd30e4fb3aa8842658e7f9a0048eacdd
+size 32508
diff --git a/marked/Rel-11/25_series/25211/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/25_series/25211/90ddb84c323b956e2d50a54d3f870566_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50989701424136791e7f1d332c64a14632db070f
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/90ddb84c323b956e2d50a54d3f870566_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c6b203a67b89875468265c3a769d9a3751a18681a53b98d6f246162ae57a7fd
+size 52716
diff --git a/marked/Rel-11/25_series/25211/92c4d3a4d29d64c167855449f1aeba2a_img.jpg b/marked/Rel-11/25_series/25211/92c4d3a4d29d64c167855449f1aeba2a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7a27cb0b03858bd0c1a329036cff4880e67aece
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/92c4d3a4d29d64c167855449f1aeba2a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a8d0a840d527e8df6a03f3296a60fcc6e7286c9afa86b904b3d4d3a99712412
+size 32441
diff --git a/marked/Rel-11/25_series/25211/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/25_series/25211/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9bbb3f2c5199088a31a36d13e03f4ec81cdf00f3
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4456e1d369771167c65a90a5fb4e171a9320ca1004023b162c83af6f8c15ace
+size 23234
diff --git a/marked/Rel-11/25_series/25211/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/25_series/25211/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b38f8e2c42bfe656ad51b498d0e867e96e37e173
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73b82f0c965c31ac9f3b51738e6dfae19f986ff0ded81a45614e94bb94c590de
+size 73267
diff --git a/marked/Rel-11/25_series/25211/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/marked/Rel-11/25_series/25211/a93de4c3f80bd4a972ab65510b09b68d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c6dbb033c20d38780f3e6a443cd5e152e16d1f4
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/a93de4c3f80bd4a972ab65510b09b68d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36e8033ed2f141e165f9cc55efcfdb245ee98ed056b2925be144a5813d7023da
+size 36019
diff --git a/marked/Rel-11/25_series/25211/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/Rel-11/25_series/25211/b0d4609bc46c2d88a8318706bb5321f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d35ef47c5a2fc0046e957054392e0a8eafb7c207
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/b0d4609bc46c2d88a8318706bb5321f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce598830b308ef7c638a4b4e96d0b4fc6430ec52c56601ba67a8a468a88a6320
+size 49757
diff --git a/marked/Rel-11/25_series/25211/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/25_series/25211/b5335262987c819d7f71ce40f99cb71b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..741fe2c32a0c1f4478bf65b15c6ac6bf8e4c7c0c
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/b5335262987c819d7f71ce40f99cb71b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8374c9f913115b0ad36013ba2cffb592bc7c5cea94315ac5075a9f4b2c5805d2
+size 51296
diff --git a/marked/Rel-11/25_series/25211/b560268ea8f6526970f23f0da225b099_img.jpg b/marked/Rel-11/25_series/25211/b560268ea8f6526970f23f0da225b099_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4e2f3bb14f2df8f80f39bed12ecbc1807e2533d
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/b560268ea8f6526970f23f0da225b099_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff6220e2c8ebaad2c36d5d8283e260accb0b13cc221f38b340e608272e213c35
+size 37862
diff --git a/marked/Rel-11/25_series/25211/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-11/25_series/25211/bd671b21db63e6fdb2196e9b18502aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..249444b89fbd9c4c8ad5fd890e18f86d026241ce
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/bd671b21db63e6fdb2196e9b18502aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10d3f36999efb0a2144d85f2de0934556c55a69c92b3cf6144a4b62ec7c1f4ca
+size 39284
diff --git a/marked/Rel-11/25_series/25211/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/25_series/25211/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..baa12c97886f7853e55a07bb68c8b0ee297a941e
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:013eab7f2da139827afd1926fe8d1bb9a8983eb0c8b7872adc4b1424dd67d59e
+size 43337
diff --git a/marked/Rel-11/25_series/25211/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-11/25_series/25211/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b9fefbacf6e6097c958091d0253c81890395d49
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70653304b1a9f33c1f7c60c45687c2bee2b6a3ae98338ceef9552afddcb3c46e
+size 79654
diff --git a/marked/Rel-11/25_series/25211/da6000b1371b5528262d4f9cb2f2707c_img.jpg b/marked/Rel-11/25_series/25211/da6000b1371b5528262d4f9cb2f2707c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..680bd5a6db057b0df9cace0bb991fb486f2004b5
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/da6000b1371b5528262d4f9cb2f2707c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e4ea43fdca01de1b7f4bb9ef68c36662555bd22ebf694b9969cf0cda72750ad
+size 41238
diff --git a/marked/Rel-11/25_series/25211/dc37a040cf9e2add7488c7c37cbf3687_img.jpg b/marked/Rel-11/25_series/25211/dc37a040cf9e2add7488c7c37cbf3687_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1dce5abc36d8c0b7ab6e4203b2e274ae14c1bb58
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/dc37a040cf9e2add7488c7c37cbf3687_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0b2526dadf5d97037f41669bf6f218a2791c5dad2b10b2de768056ec3f42df7c
+size 31891
diff --git a/marked/Rel-11/25_series/25211/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/25_series/25211/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12c1ff18918b9f05b706e72c2ee4c694ab1e6ca9
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d95f1ac108cb1785c41f2b883e195026127f3b01cdbbf11cf869ad66122e49c0
+size 44777
diff --git a/marked/Rel-11/25_series/25211/e9f5aa7b76362051c591d6783211f820_img.jpg b/marked/Rel-11/25_series/25211/e9f5aa7b76362051c591d6783211f820_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9987862ca5a2d733d8c954c4b11daf0dcefc7b47
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/e9f5aa7b76362051c591d6783211f820_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4925253713ea05ba84a0f2d091ac8c08e833838ce36236106b23d880e0373dd0
+size 11147
diff --git a/marked/Rel-11/25_series/25211/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/25_series/25211/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12826cb416a872ec869867483180d825a93a9ff8
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1f48a3af599682342897b0cfd278bd4942638671915bf7cf21d270a2b67df2f
+size 50810
diff --git a/marked/Rel-11/25_series/25211/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-11/25_series/25211/ef5f5c6665b6ae13660ede412333ba45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6434e1e4e7412401ff70079a01e4f2e1c9cd556
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/ef5f5c6665b6ae13660ede412333ba45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ba3fc42c9170179b1be390c068d2e64fb408fc2c249c082fd0492af4fb15cf5
+size 53752
diff --git a/marked/Rel-11/25_series/25211/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-11/25_series/25211/fd76efce549d3713543bb5ed9b023c2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7657bb35a9a1caf76c90c95fed99d6f41bb2575
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/fd76efce549d3713543bb5ed9b023c2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42e15340d978610eb0001b18b35cf6f6ff276601bbe8539b06aa5cab08c87457
+size 26452
diff --git a/marked/Rel-11/25_series/25211/raw.md b/marked/Rel-11/25_series/25211/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c05c75d25b01499bd3825eb6578a93a3dfd8cfa
--- /dev/null
+++ b/marked/Rel-11/25_series/25211/raw.md
@@ -0,0 +1,2337 @@
+
+
+
+
+**Error:**
+
+**2**
+
+**Error: Reference source not**
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------------|----|
+| Foreword..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Symbols, abbreviations and definitions..... | 7 |
+| 3.1 Symbols..... | 7 |
+| 3.2 Abbreviations..... | 7 |
+| 3.3 Definitions..... | 8 |
+| 4 Services offered to higher layers..... | 8 |
+| 4.1 Transport channels..... | 8 |
+| 4.1.1 Dedicated transport channels..... | 9 |
+| 4.1.1.1 DCH - Dedicated Channel..... | 9 |
+| 4.1.1.2 E-DCH – Enhanced Dedicated Channel..... | 9 |
+| 4.1.2 Common transport channels..... | 9 |
+| 4.1.2.1 BCH - Broadcast Channel..... | 9 |
+| 4.1.2.2 FACH - Forward Access Channel..... | 9 |
+| 4.1.2.3 PCH - Paging Channel..... | 9 |
+| 4.1.2.4 RACH - Random Access Channel..... | 9 |
+| 4.1.2.5 Void..... | 9 |
+| 4.1.2.6 Void..... | 9 |
+| 4.1.2.7 HS-DSCH – High Speed Downlink Shared Channel..... | 9 |
+| 4.1.2.7A E-DCH - Enhanced Dedicated Channel..... | 9 |
+| 4.2 Indicators..... | 9 |
+| 5 Physical channels and physical signals..... | 10 |
+| 5.1 Physical signals..... | 10 |
+| 5.2 Uplink physical channels..... | 10 |
+| 5.2.1 Dedicated uplink physical channels..... | 10 |
+| 5.2.1.1 DPCCH, S-DPCCH and DPDCH..... | 10 |
+| 5.2.1.2 HS-DPCCH..... | 14 |
+| 5.2.1.3 E-DPCCH and E-DPDCH..... | 14 |
+| 5.2.1.3A S-E-DPCCH and S-E-DPDCH..... | 16 |
+| 5.2.2 Common uplink physical channels..... | 16 |
+| 5.2.2.1 Physical Random Access Channel (PRACH)..... | 16 |
+| 5.2.2.1.1 Overall structure of random-access transmission..... | 16 |
+| 5.2.2.1.2 RACH preamble part..... | 17 |
+| 5.2.2.1.3 RACH message part..... | 17 |
+| 5.2.2.2 Void..... | 18 |
+| 5.3 Downlink physical channels..... | 18 |
+| 5.3.1 Downlink transmit diversity..... | 18 |
+| 5.3.1.1 Open loop transmit diversity..... | 20 |
+| 5.3.1.1.1 Space time block coding based transmit antenna diversity (STTD)..... | 20 |
+| 5.3.1.1.2 Time Switched Transmit Diversity for SCH (TSTD)..... | 22 |
+| 5.3.1.2 Closed loop transmit diversity..... | 22 |
+| 5.3.2 Dedicated downlink physical channels..... | 22 |
+| 5.3.2.1 STTD for DPCH, F-DPCH and F-TPICH..... | 26 |
+| 5.3.2.2 Dedicated channel pilots with closed loop mode transmit diversity..... | 27 |
+| 5.3.2.3 Void..... | 28 |
+| 5.3.2.4 E-DCH Relative Grant Channel..... | 28 |
+| 5.3.2.5 E-DCH Hybrid ARQ Indicator Channel..... | 30 |
+| 5.3.2.6 Fractional Dedicated Physical Channel (F-DPCH)..... | 30 |
+| 5.3.2.7 Fractional Transmitted Precoding Indicator Channel (F-TPICH)..... | 31 |
+| 5.3.3 Common downlink physical channels..... | 32 |
+| 5.3.3.1 Common Pilot Channel (CPICH)..... | 32 |
+| 5.3.3.1.1 Primary Common Pilot Channel (P-CPICH)..... | 33 |
+| 5.3.3.1.2 Secondary Common Pilot Channel (S-CPICH)..... | 33 |
+| 5.3.3.1.3 Demodulation Common Pilot Channel (D-CPICH)..... | 33 |
+
+| | | |
+|------------------------|---------------------------------------------------------------------------------|----|
+| 5.3.3.2 | Downlink phase reference..... | 34 |
+| 5.3.3.3 | Primary Common Control Physical Channel (P-CCPCH)..... | 36 |
+| 5.3.3.3.1 | Primary CCPCH structure with STTD encoding..... | 36 |
+| 5.3.3.4 | Secondary Common Control Physical Channel (S-CCPCH)..... | 37 |
+| 5.3.3.4.1 | Secondary CCPCH structure with STTD encoding..... | 39 |
+| 5.3.3.5 | Synchronisation Channel (SCH)..... | 39 |
+| 5.3.3.5.1 | SCH transmitted by TSTD..... | 40 |
+| 5.3.3.6 | Void..... | 40 |
+| 5.3.3.7 | Acquisition Indicator Channel (AICH)..... | 40 |
+| 5.3.3.8 | Void..... | 44 |
+| 5.3.3.9 | Void..... | 44 |
+| 5.3.3.10 | Paging Indicator Channel (PICH)..... | 44 |
+| 5.3.3.11 | Void..... | 45 |
+| 5.3.3.12 | Shared Control Channel (HS-SCCH)..... | 45 |
+| 5.3.3.13 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 45 |
+| 5.3.3.14 | E-DCH Absolute Grant Channel (E-AGCH)..... | 46 |
+| 5.3.3.14B | E-DCH Rank and Offset Channel (E-ROCH)..... | 46 |
+| 5.3.3.15 | MBMS Indicator Channel (MICH)..... | 46 |
+| 5.3.3.16 | Common E-DCH Relative Grant Channel..... | 47 |
+| 6 | Mapping and association of physical channels..... | 48 |
+| 6.1 | Mapping of transport channels onto physical channels..... | 48 |
+| 6.2 | Association of physical channels and physical signals..... | 49 |
+| 7 | Timing relationship between physical channels..... | 49 |
+| 7.1 | General..... | 49 |
+| 7.2 | PICH/S-CCPCH timing relation..... | 51 |
+| 7.2A | PICH/HS-SCCH timing relation..... | 51 |
+| 7.3 | PRACH/AICH timing relation..... | 51 |
+| 7.3A | UL/DL timing relation for Enhanced Uplink in CELL_FACH state and IDLE mode..... | 53 |
+| 7.4 | Void..... | 54 |
+| 7.5 | Void..... | 54 |
+| 7.6 | DPCCH/DPDCH timing relations..... | 54 |
+| 7.6.1 | Uplink..... | 54 |
+| 7.6.2 | Downlink..... | 54 |
+| 7.6.3 | Uplink/downlink timing at UE..... | 54 |
+| 7.7 | Uplink DPCCH/HS-DPCCH/HS-PDSCH timing at the UE..... | 54 |
+| 7.7.1 | Timing when Multiflow is not configured..... | 54 |
+| 7.7.2 | Timing when Multiflow is configured..... | 55 |
+| 7.8 | HS-SCCH/HS-PDSCH timing..... | 56 |
+| 7.9 | MICH/S-CCPCH timing relation..... | 57 |
+| 7.10 | E-HICH/P-CCPCH/DPCH timing relation..... | 57 |
+| 7.11 | E-RGCH/P-CCPCH/DPCH timing relation..... | 58 |
+| 7.12 | E-AGCH/P-CCPCH timing relation..... | 59 |
+| 7.12A | E-ROCH/P-CCPCH timing relation..... | 59 |
+| 7.13 | E-DPDCH/E-DPCCH/DPCH timing relation..... | 59 |
+| 7.14 | S-DPCCH/DPCH timing relation..... | 59 |
+| 7.15 | DPCH/F-DPCH/F-TPICH timing relations in softer handover..... | 59 |
+| 7.16 | S-E-DPDCH/S-E-DPCCH/DPCH timing relation..... | 59 |
+| Annex A (informative): | Change history..... | 60 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document describes the characteristics of the Layer 1 transport channels and physical channels in the FDD mode of UTRA. The main objectives of the document are to be a part of the full description of the UTRA Layer 1, and to serve as a basis for the drafting of the actual technical specification (TS).
+
+# --- 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.201: "Physical layer - general description".
+- [2] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".
+- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
+- [4] 3GPP TS 25.213: "Spreading and modulation (FDD)".
+- [5] 3GPP TS 25.214: "Physical layer procedures (FDD)".
+- [6] 3GPP TS 25.221: "Transport channels and 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.215: "Physical layer - Measurements (FDD)".
+- [11] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [12] 3GPP TS 25.302: "Services Provided by the Physical Layer".
+- [13] 3GPP TS 25.401: "UTRAN Overall Description".
+- [14] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)".
+- [15] 3G TS 25.427: "UTRAN Overall Description :UTRA Iub/Iur Interface User Plane Protocol for DCH data streams".
+- [16] 3GPP TS 25.435: "UTRAN Iub Interface User Plane Protocols for Common Transport Channel Data Streams".
+- [17] 3GPP TS 25.331: "Radio Resource Control (RRC)".
+
+# --- 3 Symbols, abbreviations and definitions
+
+## 3.1 Symbols
+
+$N_{data1}$ The number of data bits per downlink slot in Data1 field.
+
+$N_{data2}$ The number of data bits per downlink slot in Data2 field. If the slot format does not contain a Data2 field, $N_{data2} = 0$ .
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-----------|---------------------------------------------------------|
+| 16QAM | 16 Quadrature Amplitude Modulation |
+| 4PAM | 4 Pulse-Amplitude Modulation |
+| 64QAM | 64 Quadrature Amplitude Modulation |
+| 8PAM | 8 Pulse-Amplitude Modulation |
+| AI | Acquisition Indicator |
+| AICH | Acquisition Indicator Channel |
+| BCH | Broadcast Channel |
+| BPSK | Binary Phase Shift Keying |
+| CCPCH | Common Control Physical Channel |
+| CCTrCH | Coded Composite Transport Channel |
+| CLTD | Closed Loop Transmit Diversity |
+| CPICH | Common Pilot Channel |
+| CQI | Channel Quality Indicator |
+| DCH | Dedicated Channel |
+| DPCCH | Dedicated Physical Control Channel |
+| DPCH | Dedicated Physical Channel |
+| DPDCH | Dedicated Physical Data Channel |
+| DTX | Discontinuous Transmission |
+| E-AGCH | E-DCH Absolute Grant Channel |
+| E-DCH | Enhanced Dedicated Channel |
+| E-DPCCH | E-DCH Dedicated Physical Control Channel |
+| E-DPDCH | E-DCH Dedicated Physical Data Channel |
+| E-HICH | E-DCH Hybrid ARQ Indicator Channel |
+| E-RGCH | E-DCH Relative Grant Channel |
+| E-ROCH | E-DCH Rank and Offset Channel |
+| FACH | Forward Access Channel |
+| FBI | Feedback Information |
+| F-DPCH | Fractional Dedicated Physical Channel |
+| F-TPICH | Fractional Transmitted Precoding Indicator Channel |
+| FSW | Frame Synchronization Word |
+| HS-DPCCH | Dedicated Physical Control Channel (uplink) for HS-DSCH |
+| HS-DSCH | High Speed Downlink Shared Channel |
+| HS-PDSCH | High Speed Physical Downlink Shared Channel |
+| HS-SCCH | Shared Control Channel for HS-DSCH |
+| ICH | Indicator Channel |
+| MBSFN | MBMS over a Single Frequency Network |
+| MICH | MBMS Indicator Channel |
+| MIMO | Multiple Input Multiple Output |
+| MUI | Mobile User Identifier |
+| NI | MBMS Notification Indicator |
+| PCH | Paging Channel |
+| P-CCPCH | Primary Common Control Physical Channel |
+| PICH | Page Indicator Channel |
+| PRACH | Physical Random Access Channel |
+| PSC | Primary Synchronisation Code |
+| QPSK | Quadrature Phase Shift Keying |
+| RACH | Random Access Channel |
+| RNC | Radio Network Controller |
+| S-CCPCH | Secondary Common Control Physical Channel |
+| SCH | Synchronisation Channel |
+| S-E-DPCCH | Secondary Dedicated Physical Control Channel for E-DCH |
+| S-E-DPDCH | Secondary Dedicated Physical Data Channel for E-DCH |
+| S-DPCCH | Secondary Dedicated Physical Control Channel |
+| SF | Spreading Factor |
+
+| | |
+|-------|----------------------------------------|
+| SFN | System Frame Number |
+| SSC | Secondary Synchronisation Code |
+| STTD | Space Time Transmit Diversity |
+| TFCI | Transport Format Combination Indicator |
+| TSTD | Time Switched Transmit Diversity |
+| TPC | Transmit Power Control |
+| TPI | Transmitted Precoding Indicator |
+| UE | User Equipment |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+## 3.3 Definitions
+
+**Assisting secondary serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the secondary downlink frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell.
+
+**Assisting serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the same frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell.
+
+**HS-DSCH cell set:** A set of cells that can be configured together as the serving and secondary serving HS-DSCH cells for a UE. This term is applicable also to non-serving cells in an active set.
+
+**MIMO mode:** This term refers to the downlink MIMO configuration with two transmit antennas
+
+**MIMO mode with four transmit antennas:** This term refers to the downlink MIMO configuration with four transmit antennas
+
+**Multiflow mode:** The UE is configured in Multiflow mode when it is configured with an assisting serving HS-DSCH cell.
+
+**Non-time reference cell:** An HS-DSCH cell configured for a UE in Multiflow mode that has a different timing than the time reference cell. If the time reference cell is the Assisting Serving HS-DSCH cell then the non-time reference cell is the Serving HS-DSCH cell. If the time reference cell is the Serving HS-DSCH Cell, then the non-time reference cell is the Assisting Serving HS-DSCH cell.
+
+**Time reference cell:** The (Serving or Assisting Serving, but not Secondary Serving or Assisting Secondary Serving) HS-DSCH cell acting as the time reference for the uplink HS-DPCCH when the UE is configured in Multiflow mode. There is only one Time reference cell.
+
+# --- 4 Services offered to higher layers
+
+## 4.1 Transport channels
+
+Transport channels are services offered by Layer 1 to the higher layers. General concepts about transport channels are described in [12].
+
+A transport channel is defined by how and with what characteristics data is transferred over the air interface. A general classification of transport channels is into two groups:
+
+- Dedicated channels, using inherent addressing of UE;
+- Common channels, using explicit addressing of UE if addressing is needed.
+
+### 4.1.1 Dedicated transport channels
+
+There exists two types of dedicated transport channel, the Dedicated Channel (DCH) and the Enhanced Dedicated Channel (E-DCH).
+
+#### 4.1.1.1 DCH - Dedicated Channel
+
+The Dedicated Channel (DCH) is a downlink or uplink transport channel. The DCH is transmitted over the entire cell or over only a part of the cell using e.g. beam-forming antennas.
+
+#### 4.1.1.2 E-DCH – Enhanced Dedicated Channel
+
+The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel in CELL\_DCH.
+
+### 4.1.2 Common transport channels
+
+There are six types of common transport channels: BCH, FACH, PCH, RACH, HS-DSCH and E-DCH.
+
+#### 4.1.2.1 BCH - Broadcast Channel
+
+The Broadcast Channel (BCH) is a downlink transport channel that is used to broadcast system- and cell-specific information. The BCH is always transmitted over the entire cell and has a single transport format.
+
+#### 4.1.2.2 FACH - Forward Access Channel
+
+The Forward Access Channel (FACH) is a downlink transport channel. The FACH is transmitted over the entire cell. The FACH can be transmitted using power setting described in [16].
+
+#### 4.1.2.3 PCH - Paging Channel
+
+The Paging Channel (PCH) is a downlink transport channel. The PCH is always transmitted over the entire cell. The transmission of the PCH is associated with the transmission of physical-layer generated Paging Indicators, to support efficient sleep-mode procedures.
+
+#### 4.1.2.4 RACH - Random Access Channel
+
+The Random Access Channel (RACH) is an uplink transport channel. The RACH is always received from the entire cell. The RACH is characterized by a collision risk and by being transmitted using open loop power control.
+
+#### 4.1.2.5 Void
+
+#### 4.1.2.6 Void
+
+#### 4.1.2.7 HS-DSCH – High Speed Downlink Shared Channel
+
+The High Speed Downlink Shared Channel is a downlink transport channel shared by several UEs. The HS-DSCH can be associated with one downlink DPCH or F-DPCH, and one or several Shared Control Channels (HS-SCCH). The HS-DSCH is transmitted over the entire cell or over only part of the cell using e.g. beam-forming antennas.
+
+#### 4.1.2.7A E-DCH - Enhanced Dedicated Channel
+
+The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel in CELL\_FACH state and IDLE mode.
+
+## 4.2 Indicators
+
+Indicators are means of fast low-level signalling entities which are transmitted without using information blocks sent over transport channels. The meaning of indicators is specific to the type of indicator.
+
+The indicators defined in the current version of the specifications are: Acquisition Indicator (AI), Page Indicator (PI) and MBMS Notification Indicator (NI).
+
+Indicators may be either boolean (two-valued) or three-valued. Their mapping to indicator channels is channel specific.
+
+Indicators are transmitted on those physical channels that are indicator channels (ICH).
+
+# 5 Physical channels and physical signals
+
+Physical channels are defined by a specific carrier frequency, scrambling code, channelization code (optional), time start & stop (giving a duration) and, on the uplink, relative phase (0 or $\pi/2$ ). The downlink E-HICH and E-RGCH are each further defined by a specific orthogonal signature sequence. Scrambling and channelization codes are specified in [4]. Time durations are defined by start and stop instants, measured in integer multiples of chips. Suitable multiples of chips also used in specification are:
+
+| | |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Radio frame: | A radio frame is a processing duration which consists of 15 slots. The length of a radio frame corresponds to 38400 chips. |
+| Slot: | A slot is a duration which consists of fields containing bits. The length of a slot corresponds to 2560 chips. |
+| Sub-frame: | A sub-frame is the basic time interval for E-DCH and HS-DSCH transmission and E-DCH and HS-DSCH-related signalling at the physical layer. The length of a sub-frame corresponds to 3 slots (7680 chips). |
+
+The default time duration for a physical channel is continuous from the instant when it is started to the instant when it is stopped. Physical channels that are not continuous will be explicitly described.
+
+Transport channels are described (in more abstract higher layer models of the physical layer) as being capable of being mapped to physical channels. Within the physical layer itself the exact mapping is from a composite coded transport channel (CCTrCH) to the data part of a physical channel. In addition to data parts there also exist channel control parts and physical signals.
+
+## 5.1 Physical signals
+
+Physical signals are entities with the same basic on-air attributes as physical channels but do not have transport channels or indicators mapped to them. Physical signals may be associated with physical channels in order to support the function of physical channels.
+
+## 5.2 Uplink physical channels
+
+### 5.2.1 Dedicated uplink physical channels
+
+There are six types of uplink dedicated physical channels, the uplink Dedicated Physical Data Channel (uplink DPDCH), the uplink Dedicated Physical Control Channel (uplink DPCCH), the uplink Secondary Dedicated Physical Control Channel (uplink S-DPCCH), the uplink E-DCH Dedicated Physical Data Channel (uplink E-DPDCH), the uplink E-DCH Dedicated Physical Control Channel (uplink E-DPCCH) and the uplink Dedicated Control Channel associated with HS-DSCH transmission (uplink HS-DPCCH).
+
+The DPDCH, the DPCCH, the S-DPCCH, the E-DPDCH, the E-DPCCH and the HS-DPCCH are I/Q code multiplexed (see [4]).
+
+#### 5.2.1.1 DPCCH, S-DPCCH and DPDCH
+
+The uplink DPDCH is used to carry the DCH transport channel. There may be zero, one, or several uplink DPDCHs on each radio link.
+
+The uplink DPCCH is used to carry control information generated at Layer 1. The Layer 1 control information consists of known pilot bits to support channel estimation for coherent detection, transmit power-control (TPC) commands, feedback information (FBI), and an optional transport-format combination indicator (TFCI). The transport-format combination indicator informs the receiver about the instantaneous transport format combination of the transport channels mapped to the simultaneously transmitted uplink DPDCH radio frame. There is one and only one uplink DPCCH on each radio link.
+
+The uplink S-DPCCH is used to carry control information generated at Layer 1. The Layer 1 control information consists of known pilot bits to support channel sounding and channel estimation for coherent detection. There is up to one uplink S-DPCCH on each radio link in the case that UL\_CLTD\_Enabled as defined in [5] is TRUE. Figure 1 shows the frame structure of the uplink DPDCH, the uplink DPCCH and the uplink S-DPCCH. Each radio frame of length 10
+
+ms is split into 5 subframes, each of 3 slots, each of length $T_{\text{slot}} = 2560$ chips, corresponding to one power-control period. The DPDCH, DPCCH and S-DPCCH are always frame aligned with each other.
+
+
+
+DPDCH
+
+Data
+ $N_{\text{data}}$ bits
+
+$T_{\text{slot}} = 2560$ chips, $N_{\text{data}} = 10 \cdot 2^k$ bits ( $k=0..6$ )
+
+DPCCH
+
+Pilot
+ $N_{\text{pilot}}$ bits
+
+TFCI
+ $N_{\text{TFCI}}$ bits
+
+FBI
+ $N_{\text{FBI}}$ bits
+
+TPC
+ $N_{\text{TPC}}$ bits
+
+$T_{\text{slot}} = 2560$ chips, 10 bits
+
+S-DPCCH
+
+Pilot
+ $N_{\text{pilot}}$ bits
+
+$N_{\text{fixed}}$ bits
+
+$T_{\text{slot}} = 2560$ chips, 10 bits
+
+Slot #0 Slot #1 Slot #2 Slot #3 Slot #i Slot #14
+
+Subframe #0 Subframe #1 Subframe #2 Subframe #3 Subframe #4
+
+1 subframe = 2 ms
+
+1 radio frame: $T_r = 10$ ms
+
+Figure 1: Frame structure for uplink DPDCH/DPCCH/S-DPCCH. The diagram shows the hierarchical structure of a radio frame. At the top, three channel structures are shown: DPDCH (Data, N\_data bits), DPCCH (Pilot, N\_pilot bits; TFCI, N\_TFCI bits; FBI, N\_FBI bits; TPC, N\_TPC bits), and S-DPCCH (Pilot, N\_pilot bits; N\_fixed bits). Below these, a timeline shows slots (Slot #0 to Slot #14) grouped into subframes (Subframe #0 to Subframe #4). A callout shows a detailed view of a subframe containing three slots. Time scales are indicated: T\_slot = 2560 chips, N\_data = 10\*2^k bits (k=0..6) for DPDCH; T\_slot = 2560 chips, 10 bits for DPCCH and S-DPCCH; 1 subframe = 2 ms; and 1 radio frame: T\_r = 10 ms.
+
+**Figure 1: Frame structure for uplink DPDCH/DPCCH/S-DPCCH**
+
+The parameter $k$ in figure 1 determines the number of bits per uplink DPDCH slot. It is related to the spreading factor $SF$ of the DPDCH as $SF = 256/2^k$ . The DPDCH spreading factor may range from 256 down to 4. The spreading factor of the uplink DPCCH and the uplink S-DPCCH is always equal to 256, i.e. there are 10 bits per uplink DPCCH/S-DPCCH slot.
+
+The exact number of bits of the uplink DPDCH and the different uplink DPCCH fields ( $N_{\text{pilot}}$ , $N_{\text{TFCI}}$ , $N_{\text{FBI}}$ , and $N_{\text{TPC}}$ ) is given by table 1 and table 2. What slot format to use is configured by higher layers and can also be reconfigured by higher layers. The exact number of bits of the uplink S-DPCCH is given by table 2A.
+
+The channel bit and symbol rates given in table 1, table 2 and table 2A are the rates immediately before spreading. The pilot patterns are given in table 3 and table 4, the TPC bit pattern is given in table 5.
+
+The FBI bits are used to support techniques requiring feedback from the UE to the UTRAN Access Point for operation of closed loop mode transmit diversity. The use of the FBI bits is described in detail in [5].
+
+**Table 1: DPDCH fields**
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Frame | Bits/Slot | N data |
+|----------------|-------------------------|----------------------------|-----|------------|-----------|-------------------|
+| 0 | 15 | 15 | 256 | 150 | 10 | 10 |
+| 1 | 30 | 30 | 128 | 300 | 20 | 20 |
+| 2 | 60 | 60 | 64 | 600 | 40 | 40 |
+| 3 | 120 | 120 | 32 | 1200 | 80 | 80 |
+| 4 | 240 | 240 | 16 | 2400 | 160 | 160 |
+| 5 | 480 | 480 | 8 | 4800 | 320 | 320 |
+| 6 | 960 | 960 | 4 | 9600 | 640 | 640 |
+
+There are two types of uplink dedicated physical channels; those that include TFCI (e.g. for several simultaneous services) and those that do not include TFCI (e.g. for fixed-rate services). These types are reflected by the duplicated rows of table 2. It is the UTRAN that determines if a TFCI should be transmitted and it is mandatory for all UEs to support the use of TFCI in the uplink. The mapping of TFCI bits onto slots is described in [3].
+
+In compressed mode, DPCCH slot formats with TFCI fields are changed. There are two possible compressed slot formats for each normal slot format. They are labelled A and B and the selection between them is dependent on the number of slots that are transmitted in each frame in compressed mode.
+
+If UL\_DTX\_Active is TRUE (see [5]), the number of transmitted slots per radio frame may be less than the number shown in Table 2 and Table 2A.
+
+**Table 2: DPCCH fields**
+
+| Slot Form at #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Frame | Bits/Slot | N pilot | N TPC | N TFCI | N FBI | Transmitted slots per radio frame |
+|-----------------|-------------------------|----------------------------|-----|------------|-----------|--------------------|------------------|-------------------|------------------|-----------------------------------|
+| 0 | 15 | 15 | 256 | 150 | 10 | 6 | 2 | 2 | 0 | 15 |
+| 0A | 15 | 15 | 256 | 150 | 10 | 5 | 2 | 3 | 0 | 10-14 |
+| 0B | 15 | 15 | 256 | 150 | 10 | 4 | 2 | 4 | 0 | 8-9 |
+| 1 | 15 | 15 | 256 | 150 | 10 | 8 | 2 | 0 | 0 | 8-15 |
+| 2 | 15 | 15 | 256 | 150 | 10 | 5 | 2 | 2 | 1 | 15 |
+| 2A | 15 | 15 | 256 | 150 | 10 | 4 | 2 | 3 | 1 | 10-14 |
+| 2B | 15 | 15 | 256 | 150 | 10 | 3 | 2 | 4 | 1 | 8-9 |
+| 3 | 15 | 15 | 256 | 150 | 10 | 7 | 2 | 0 | 1 | 8-15 |
+| 4 | 15 | 15 | 256 | 150 | 10 | 6 | 4 | 0 | 0 | 8-15 |
+
+**Table 2A: S-DPCCH fields**
+
+| Slot Form at #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Frame | Bits/Slot | N pilot | N fixed | Transmitted slots per radio frame |
+|-----------------|-------------------------|----------------------------|-----|------------|-----------|--------------------|--------------------|-----------------------------------|
+| 1 | 15 | 15 | 256 | 150 | 10 | 8 | 2 | 8-15 |
+
+The pilot bit pattern for S-DPCCH is the same as that for uplink DPCCH with Npilot = 8. The Nfixed bits in the S-DPCCH are fixed to "10".
+
+The pilot bit patterns are described in table 3 and table 4. The shadowed column part of pilot bit pattern is defined as FSW and FSWs can be used to confirm frame synchronization. (The value of the pilot bit pattern other than FSWs shall be "1".)
+
+**Table 3: Pilot bit patterns for uplink DPCCH with $N_{pilot} = 3, 4, 5$ and 6**
+
+| Bit # | $N_{pilot} = 3$ | | | $N_{pilot} = 4$ | | | | $N_{pilot} = 5$ | | | | | $N_{pilot} = 6$ | | | | | |
+|---------|-----------------|---|---|-----------------|---|---|---|-----------------|---|---|---|---|-----------------|---|---|---|---|---|
+| | 0 | 1 | 2 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 |
+| Slot #0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 |
+| 2 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 |
+| 3 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 |
+| 4 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 1 |
+| 5 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 6 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 |
+| 7 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 |
+| 8 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 |
+| 9 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
+| 10 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 |
+| 11 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 |
+| 12 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 |
+| 13 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 |
+| 14 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 |
+
+**Table 4: Pilot bit patterns for uplink DPCCH with $N_{pilot} = 7$ and 8**
+
+| Bit # | $N_{pilot} = 7$ | | | | | | | $N_{pilot} = 8$ | | | | | | | |
+|---------|-----------------|---|---|---|---|---|---|-----------------|---|---|---|---|---|---|---|
+| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| Slot #0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 |
+| 2 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 |
+| 3 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 |
+| 4 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 |
+| 5 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 6 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 |
+| 7 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 |
+| 8 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 9 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
+| 10 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 |
+| 11 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 |
+| 12 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 |
+| 13 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 |
+| 14 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 |
+
+The relationship between the TPC bit pattern and transmitter power control command is presented in table 5.
+
+**Table 5: TPC Bit Pattern**
+
+| TPC Bit Pattern | | Transmitter power control command |
+|-----------------|---------------|-----------------------------------|
+| $N_{TPC} = 2$ | $N_{TPC} = 4$ | |
+| 11 | 1111 | 1 |
+| 00 | 0000 | 0 |
+
+Multi-code operation is possible for the uplink dedicated physical channels. When multi-code transmission is used, several parallel DPDCH are transmitted using different channelization codes, see [4]. However, there is only one DPCCH per radio link, and up to one S-DPCCH in the case that UL\_CLTD\_Enable is TRUE.
+
+A period of uplink DPCCH transmission prior to the start of the uplink DPDCH transmission (uplink DPCCH power control preamble) shall be used for initialisation of a DCH. The length of the power control preamble is a higher layer parameter, $N_{pcp}$ , signalled by the network [5]. The UL DPCCH shall take the same slot format in the power control preamble as afterwards, as given in table 2. When $N_{pcp} > 0$ the pilot patterns of table 3 and table 4 shall be used. The timing of the power control preamble is described in [5], subclause 4.3.2.3. The TFCI field is filled with "0" bits.
+
+#### 5.2.1.2 HS-DPCCH
+
+Figure 2A illustrates the frame structure of the HS-DPCCH. The HS-DPCCH carries uplink feedback signalling related to downlink HS-DSCH transmission and to HS-SCCH orders according to subclause 6A.1.1 in [5]. The feedback
+
+signalling consists of Hybrid-ARQ Acknowledgement (HARQ-ACK) and Channel-Quality Indication (CQI), in case the UE is configured in MIMO mode or in MIMO mode with four transmit antennas Precoding Control Indication (PCI) as well and in case the UE is configured in MIMO mode with four transmit antennas the number of transport blocks preferred (NTBP) as well [3]. Each sub frame of length 2 ms ( $3 \times 2560$ chips) consists of 3 slots, each of length 2560 chips. The HARQ-ACK is carried in the first slot of the HS-DPCCH sub-frame. The CQI, in case the UE is configured in MIMO mode also the PCI, and in case the UE is configured in MIMO mode with four transmit antennas also the PCI and the number of UE preferred transport blocks are carried in the second and third slot of a HS-DPCCH sub-frame. There is at most one HS-DPCCH on each radio link if Secondary\_Cell\_Enabled as defined in [5] is less than 4 in case the UE is not configured in MIMO mode with four transmit antennas, 2 in case the UE is configured in MIMO mode with four transmit antennas and at most two HS-DPCCHs otherwise. The HS-DPCCH(s) can only exist together with an uplink DPCCH. The timing of the HS-DPCCH relative to the uplink DPCCH is shown in section 7.7 for the case where one HS-DPCCH exists. In the case where two HS-DPCCH exist, both HS-DPCCHs have identical timing.
+
+
+
+Figure 2A: Frame structure for uplink HS-DPCCH. The diagram shows a radio frame of length T\_f = 10 ms, divided into 5 subframes (Subframe #0 to Subframe #4). A detailed view of one subframe (2 ms) shows it is divided into 3 slots. The first slot is HARQ-ACK, with a duration of T\_slot = 2560 chips. The second and third slots are CQI/PCI, with a combined duration of 2 \* T\_slot = 5120 chips.
+
+**Figure 2A: Frame structure for uplink HS-DPCCH**
+
+The slot formats for uplink HS-DPCCH are defined in Table 5A.
+
+**Table 5A: HS-DPCCH fields**
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Subframe | Bits/Slot | Transmitted slots per Subframe |
+|----------------|-------------------------|----------------------------|-----|---------------|-----------|--------------------------------|
+| 0 | 15 | 15 | 256 | 30 | 10 | 3 |
+| 1 | 30 | 30 | 128 | 60 | 20 | 3 |
+
+#### 5.2.1.3 E-DPCCH and E-DPDCH
+
+The E-DPDCH is used to carry the E-DCH transport channel. There may be zero, one, or several E-DPDCH on each radio link.
+
+The E-DPCCH is a physical channel used to transmit control information associated with the E-DCH. There is at most one E-DPCCH on each radio link.
+
+E-DPDCH and E-DPCCH are always transmitted simultaneously, except for the following cases when E-DPCCH is transmitted without E-DPDCH:
+
+- when E-DPDCH but not E-DPCCH is DTXed due to power scaling as described in [5] section 5.1.2.6, or
+- during the $n_{dtx}$ E-DPDCH idle slots if $n_{max} > n_{tx1}$ as described in [3] section 4.4.5.2.
+
+E-DPCCH shall not be transmitted in a slot unless DPCCH is also transmitted in the same slot.
+
+Figure 2B shows the E-DPDCH and E-DPCCH (sub)frame structure. Each radio frame is divided in 5 subframes, each of length 2 ms; the first subframe starts at the start of each radio frame and the 5th subframe ends at the end of each radio frame.
+
+An E-DPDCH may use BPSK, 4PAM or 8PAM modulation symbols. In figure 2B, M is the number of bits per modulation symbol i.e. M=1 for BPSK, M=2 for 4PAM and M=3 for 8PAM.
+
+The E-DPDCH slot formats, corresponding rates and number of bits are specified in Table 5B. The E-DPCCH slot format is listed in Table 5C.
+
+
+
+E-DPDCH: Data, $N_{data}$ bits
+ $T_{slot} = 2560\text{ chips}, N_{data} = M \cdot 10 \cdot 2^k\text{ bits } (k=0...7)$
+
+E-DPCCH: 10 bits
+ $T_{slot} = 2560\text{ chips}$
+
+Radio frame structure: Slot #0, Slot #1, Slot #2, Slot #3 ... Slot #i ... Slot #14
+ Subframe #0, Subframe #1, Subframe #2, Subframe #3, Subframe #4
+ 1 subframe = 2 ms
+ 1 radio frame, $T_f = 10\text{ ms}$
+
+Figure 2B: E-DPDCH frame structure diagram. The diagram shows the hierarchy of a radio frame. At the top, an E-DPDCH slot contains 'Data, N\_data bits' over a duration of T\_slot = 2560 chips, where N\_data = M \* 10 \* 2^k bits (k=0...7). Below it, an E-DPCCH slot contains '10 bits' over the same duration T\_slot = 2560 chips. A zoomed-in view shows a radio frame (T\_f = 10 ms) consisting of 5 subframes (Subframe #0 to #4), each 2 ms long. Each subframe contains 3 slots (Slot #0 to Slot #14 are shown across the frame).
+
+**Figure 2B: E-DPDCH frame structure**
+
+**Table 5B: E-DPDCH slot formats**
+
+| Slot Format #i | Channel Bit Rate (kbps) | Bits/Symbol M | SF | Bits/Frame | Bits/Subframe | Bits/Slot $N_{data}$ |
+|----------------|-------------------------|---------------|-----|------------|---------------|----------------------|
+| 0 | 15 | 1 | 256 | 150 | 30 | 10 |
+| 1 | 30 | 1 | 128 | 300 | 60 | 20 |
+| 2 | 60 | 1 | 64 | 600 | 120 | 40 |
+| 3 | 120 | 1 | 32 | 1200 | 240 | 80 |
+| 4 | 240 | 1 | 16 | 2400 | 480 | 160 |
+| 5 | 480 | 1 | 8 | 4800 | 960 | 320 |
+| 6 | 960 | 1 | 4 | 9600 | 1920 | 640 |
+| 7 | 1920 | 1 | 2 | 19200 | 3840 | 1280 |
+| 8 | 1920 | 2 | 4 | 19200 | 3840 | 1280 |
+| 9 | 3840 | 2 | 2 | 38400 | 7680 | 2560 |
+| 10 | 2880 | 3 | 4 | 28800 | 5760 | 1920 |
+| 11 | 5760 | 3 | 2 | 57600 | 11520 | 3840 |
+
+**Table 5C: E-DPCCH slot formats**
+
+| Slot Format #i | Channel Bit Rate (kbps) | SF | Bits/Frame | Bits/Subframe | Bits/Slot $N_{data}$ |
+|----------------|-------------------------|-----|------------|---------------|----------------------|
+| 0 | 15 | 256 | 150 | 30 | 10 |
+
+#### 5.2.1.3A S-E-DPCCH and S-E-DPDCH
+
+The S-E-DPDCH is used to carry the E-DCH transport channel. When UL\_MIMO\_Enabled is set to TRUE and rank-2 transmission takes place on a radio link, the number of S-E-DPDCH channels on that radio link is 4, otherwise, it is zero.
+
+The S-E-DPCCH is a physical channel used to transmit control information associated with the S-E-DPDCH. There is at most one S-E-DPCCH on each radio link.
+
+S-E-DPDCH and S-E-DPCCH are always transmitted simultaneously.
+
+S-E-DPCCH shall not be transmitted in a slot unless DPCCH and S-DPCCH is also transmitted in the same slot.
+
+The S-E-DPDCH frame structure is the same as the E-DPDCH frame structure. The S-E-DPCCH frame structure is the same as the E-DPCCH frame structure.
+
+An S-E-DPDCH may use BPSK, 4PAM or 8PAM modulation symbols.
+
+The S-E-DPDCH slot formats, corresponding rates and number of bits are as specified for slot formats 6-11 in table 5B for E-DPDCH. Slot formats 0-5 are not applicable for S-E-DPDCH.
+
+The S-E-DPCCH slot format is as specified for E-DPCCH in Table 5C.
+
+### 5.2.2 Common uplink physical channels
+
+#### 5.2.2.1 Physical Random Access Channel (PRACH)
+
+The Physical Random Access Channel (PRACH) is used to carry the RACH.
+
+##### 5.2.2.1.1 Overall structure of random-access transmission
+
+The random-access transmission is based on a Slotted ALOHA approach with fast acquisition indication. The UE can start the random-access transmission at the beginning of a number of well-defined time intervals, denoted *access slots*. There are 15 access slots per two frames and they are spaced 5120 chips apart, see figure 3. The timing of the access slots and the acquisition indication is described in subclause 7.3. Information on what access slots are available for random-access transmission is given by higher layers.
+
+
+
+Figure 3: RACH access slot numbers and their spacing. The diagram shows a timeline of two radio frames, each 10 ms long, separated by a dashed vertical line. Below the timeline, 15 access slots are numbered #0 through #14. A double-headed arrow above the first slot indicates a spacing of 5120 chips. Four horizontal bars labeled 'Random Access Transmission' show different start times for random access: the first starts at the beginning of slot #0, the second at the beginning of slot #1, the third at the beginning of slot #7, and the fourth at the beginning of slot #14. Vertical dashed lines extend downwards from the start of each slot.
+
+Figure 3: RACH access slot numbers and their spacing
+
+The structure of the random-access transmission is shown in figure 4. The random-access transmission consists of one or several *preambles* of length 4096 chips and a *message* of length 10 ms or 20 ms.
+
+
+
+Figure 4: Structure of the random-access transmission. The diagram shows two rows of transmission structures. The top row shows a 'Preamble' (4096 chips), followed by two more 'Preamble' blocks connected by a dotted line, and then a 'Message part' (10 ms, one radio frame). The bottom row shows a 'Preamble' (4096 chips), followed by two more 'Preamble' blocks connected by a dotted line, and then a 'Message part' (20 ms, two radio frames).
+
+Figure 4: Structure of the random-access transmission
+
+##### 5.2.2.1.2 RACH preamble part
+
+Each preamble is of length 4096 chips and consists of 256 repetitions of a signature of length 16 chips. There are a maximum of 16 available signatures, see [4] for more details.
+
+##### 5.2.2.1.3 RACH message part
+
+Figure 5 shows the structure of the random-access message part radio frame. The 10 ms message part radio frame is split into 15 slots, each of length $T_{\text{slot}} = 2560$ chips. Each slot consists of two parts, a data part to which the RACH transport channel is mapped and a control part that carries Layer 1 control information. The data and control parts are transmitted in parallel. A 10 ms message part consists of one message part radio frame, while a 20 ms message part consists of two consecutive 10 ms message part radio frames. The message part length is equal to the Transmission Time Interval of the RACH Transport channel in use. This TTI length is configured by higher layers.
+
+The data part consists of $10 \cdot 2^k$ bits, where $k=0,1,2,3$ . This corresponds to a spreading factor of 256, 128, 64, and 32 respectively for the message data part.
+
+The control part consists of 8 known pilot bits to support channel estimation for coherent detection and 2 TFCI bits. This corresponds to a spreading factor of 256 for the message control part. The pilot bit pattern is described in table 8. The total number of TFCI bits in the random-access message is $15 \cdot 2 = 30$ . The TFCI of a radio frame indicates the transport format of the RACH transport channel mapped to the simultaneously transmitted message part radio frame. In case of a 20 ms PRACH message part, the TFCI is repeated in the second radio frame.
+
+
+
+Figure 5: Structure of the random-access message part radio frame. The diagram shows a 'Data' part with 'N\_data bits' and a 'Control' part with 'Pilot' (N\_pilot bits) and 'TFCI' (N\_TFCI bits). Below this, a slot is shown with 'T\_slot = 2560 chips, 10 \* 2^k bits (k=0..3)'. At the bottom, a 'Message part radio frame' is shown with 15 slots, labeled 'Slot #0', 'Slot #1', 'Slot #i', and 'Slot #14', with a total duration of 'T\_RACH = 10 ms'.
+
+Figure 5: Structure of the random-access message part radio frame
+
+Table 6: Random-access message data fields
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Frame | Bits/Slot | N_data |
+|----------------|-------------------------|----------------------------|-----|------------|-----------|--------|
+| 0 | 15 | 15 | 256 | 150 | 10 | 10 |
+| 1 | 30 | 30 | 128 | 300 | 20 | 20 |
+| 2 | 60 | 60 | 64 | 600 | 40 | 40 |
+| 3 | 120 | 120 | 32 | 1200 | 80 | 80 |
+
+**Table 7: Random-access message control fields**
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Frame | Bits/Slot | N pilot | N TFCI |
+|----------------|-------------------------|----------------------------|-----|------------|-----------|--------------------|-------------------|
+| 0 | 15 | 15 | 256 | 150 | 10 | 8 | 2 |
+
+**Table 8: Pilot bit patterns for RACH message part with Npilot = 8**
+
+| Bit # | N pilot = 8 | | | | | | | |
+|---------|------------------------|---|---|---|---|---|---|---|
+| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| Slot #0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 |
+| 2 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 |
+| 3 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 |
+| 4 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 |
+| 5 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 6 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 |
+| 7 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 |
+| 8 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 9 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
+| 10 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 |
+| 11 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 |
+| 12 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 |
+| 13 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 |
+| 14 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 |
+
+#### 5.2.2.2 Void
+
+## 5.3 Downlink physical channels
+
+### 5.3.1 Downlink transmit diversity
+
+Table 10 summarises the possible application of open and closed loop transmit diversity modes on different downlink physical channel types. Simultaneous use of STTD and closed loop modes on the same physical channel is not allowed. In addition, if Tx diversity is applied on any of the downlink physical channels allocated to a UE(s) that is configured to use P-CPICH as a phase reference on both antennas, then Tx diversity shall also be applied on P-CCPCH and SCH. If Tx diversity is applied on SCH it shall also be applied on P-CCPCH and vice versa. Regarding CPICH transmission in case of transmit diversity used on SCH and P-CCPCH, see subclause 5.3.3.1.
+
+With respect to the usage of Tx diversity for DPCH or F-DPCH on different radio links within an active set, the following rules apply:
+
+- Different Tx diversity modes (STTD and closed loop) shall not be used on the radio links within one active set.
+- No Tx diversity on one or more radio links shall not prevent UTRAN to use Tx diversity on other radio links within the same active set.
+- If STTD is activated on one or several radio links in the active set, the UE shall operate STTD on only those radio links where STTD has been activated. Higher layers inform the UE about the usage of STTD on the individual radio links in the active set.
+- Regarding the usage of Tx diversity for DPCH on different radio links within an active set, if closed loop TX diversity is activated on one or several radio links in the active set, the UE shall operate closed loop TX diversity on only those radio links where closed loop TX diversity has been activated. Higher layers inform the UE about the usage of closed loop TX diversity on the individual radio links in the active set.
+
+Furthermore, if the UE is not configured in MIMO mode and in MIMO mode with four transmit antennas in a cell the following restrictions apply in this cell:
+
+- If a DPCH is associated with an HS-PDSCH subframe in the same cell, the transmit diversity mode used for the HS-PDSCH subframe shall be the same as the transmit diversity mode used for the DPCH associated with this HS-PDSCH subframe.
+- If an F-DPCH is associated with an HS-PDSCH subframe in the same cell, the transmit diversity mode used for the HS-PDSCH subframe shall be the same as the transmit diversity mode signalled for the F-DPCH associated with this HS-PDSCH subframe.
+- If neither DPCH nor F-DPCH is associated with an HS-PDSCH subframe the transmit diversity mode used for the HS-PDSCH subframe shall be the STTD if the P-CCPCH in the cell is using transmit diversity. Otherwise, no transmit diversity is used for the HS-PDSCH subframe.
+- If the UE is configured with a secondary serving HS-DSCH cell not associated with either DPCH or F-DPCH in the same cell, the diversity mode used for the HS-PDSCH subframe of that cell is configured by higher layers and independent from that used in the serving HS-DSCH cell.
+
+If the UE is configured in MIMO mode in a cell then a DPCH or F-DPCH associated with an HS-PDSCH subframe can be either in transmit diversity mode or in no transmit diversity mode in this cell.
+
+Regardless of whether or not the UE is configured in MIMO mode or in MIMO mode with four transmit antennas in a cell,
+
+- If the DPCH associated with an HS-SCCH subframe in the same cell is using either open or closed loop transmit diversity on the radio link transmitted from the HS-DSCH serving cell, the HS-SCCH subframe from this cell shall be transmitted using STTD, otherwise no transmit diversity shall be used for this HS-SCCH subframe.
+- If an F-DPCH for which STTD is signalled is associated with an HS-SCCH subframe in the same cell, the HS-SCCH subframe shall be transmitted using STTD, otherwise no transmit diversity shall be used for this HS-SCCH subframe.
+- If neither DPCH nor F-DPCH is associated with an HS-SCCH subframe the transmit diversity mode used for the HS-SCCH subframe shall be the STTD if the P-CCPCH in the cell is using transmit diversity. Otherwise, no transmit diversity is used for the HS-SCCH subframe.
+- If the UE is configured with a secondary serving HS-DSCH cell not associated with either DPCH or F-DPCH in the same cell, the diversity mode used for the HS-SCCH subframe of that cell is configured by higher layers and independent from that used in the serving HS-DSCH cell.
+
+The transmit diversity mode on the associated DPCH or F-DPCH may not change during a HS-SCCH and or HS-PDSCH subframe and within the slot prior to the HS-SCCH subframe. This includes any change between no Tx diversity and either open loop or closed loop mode.
+
+If the UE is receiving a DPCH on which transmit diversity is used from a cell, or if the UE is receiving an F-DPCH for which STTD is signalled from a cell, the UE shall assume that the E-AGCH, E-ROCH, E-RGCH, E-HICH, and F-TPICH from the same cell are transmitted using STTD.
+
+**Table 10: Application of Tx diversity modes on downlink physical channel types**
+ "X" – can be applied, "–" – not applied
+
+| Physical channel type | Open loop mode | | Closed loop mode
Mode 1 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------|----------------------------|
+| | TSTD | STTD | |
+| P-CCPCH | – | X | – |
+| SCH | X | – | – |
+| S-CCPCH | – | X | – |
+| DPCH | – | X | X |
+| F-DPCH | – | X | – |
+| PICH | – | X | – |
+| MICH | – | X | – |
+| HS-PDSCH (UE not in MIMO mode and not in MIMO mode with four transmit antennas , UE configured without a secondary serving HS-DSCH cell) | – | X | X |
+| HS-PDSCH (UE not in MIMO mode and not in MIMO mode with four transmit antennas in this cell, UE configured with a secondary serving HS-DSCH cell) (*1) (*2) | – | X | – |
+| HS-PDSCH (UE in MIMO mode or in MIMO mode with four transmit antennas in this cell ) (*2) | – | – | – |
+| HS-SCCH (*1) | – | X | – |
+| E-AGCH | – | X | – |
+| E-ROCH | – | X | – |
+| E-RGCH | – | X | – |
+| E-HICH | – | X | – |
+| AICH | – | X | – |
+| F-TPICH | – | X | – |
+
+NOTE \*1: The Tx diversity mode can be configured independently across cells.
+
+NOTE \*2: The MIMO mode or MIMO mode with four transmit antennas can be configured independently across cells.
+
+#### 5.3.1.1 Open loop transmit diversity
+
+##### 5.3.1.1.1 Space time block coding based transmit antenna diversity (STTD)
+
+The open loop downlink transmit diversity employs a space time block coding based transmit diversity (STTD).
+
+The STTD encoding is optional in UTRAN. STTD support is mandatory at the UE.
+
+A block diagram of a generic STTD encoder is shown in the figure 8, figure 8A and figure 8B below. Channel coding, rate matching and interleaving are done as in the non-diversity mode. For QPSK, the STTD encoder operates on 4 symbols $b_0, b_1, b_2, b_3$ as shown in figure 8. For AICH, E-RGCH, E-HICH the $\bar{b}_i$ are real valued signals, and $\bar{b}_i$ is defined as $-b_i$ . For channels other than AICH, E-RGCH, E-HICH the $\bar{b}_i$ are 3-valued digits, taking the values 0, 1, "DTX", and $\bar{b}_i$ is defined as follows: if $b_i = 0$ then $\bar{b}_i = 1$ , if $b_i = 1$ then $\bar{b}_i = 0$ , otherwise $\bar{b}_i = b_i$ .
+
+![Generic block diagram of the STTD encoder for QPSK. It shows an input block of four symbols [b0, b1, b2, b3] labeled 'Symbols'. This block is split into two antennas. Antenna 1 receives the symbols [b0, b1, b2, b3]. Antenna 2 receives the symbols [\bar{b}_2, b_3, b_0, \bar{b}_1]. The output for both antennas is labeled 'STTD encoded symbols for antenna 1 and antenna 2'.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+Figure 8 shows a generic block diagram of the STTD encoder for QPSK. An input block of four symbols $b_0, b_1, b_2, b_3$ (labeled "Symbols") is processed. The symbols are split into two antennas. Antenna 1 receives the symbols $b_0, b_1, b_2, b_3$ . Antenna 2 receives the symbols $\bar{b}_2, b_3, b_0, \bar{b}_1$ . The output for both antennas is labeled "STTD encoded symbols for antenna 1 and antenna 2".
+
+Generic block diagram of the STTD encoder for QPSK. It shows an input block of four symbols [b0, b1, b2, b3] labeled 'Symbols'. This block is split into two antennas. Antenna 1 receives the symbols [b0, b1, b2, b3]. Antenna 2 receives the symbols [\bar{b}\_2, b\_3, b\_0, \bar{b}\_1]. The output for both antennas is labeled 'STTD encoded symbols for antenna 1 and antenna 2'.
+
+**Figure 8: Generic block diagram of the STTD encoder for QPSK**
+
+For 16QAM, STTD operates on blocks of 8 consecutive symbols $b_0, b_1, b_2, b_3, b_4, b_5, b_6, b_7$ as shown in figure 8A below.
+
+![Generic block diagram of the STTD encoder for 16QAM. It shows an input block of eight symbols [b0, b1, b2, b3, b4, b5, b6, b7] labeled 'Symbols'. This block is split into two antennas. Antenna 1 receives the symbols [b0, b1, b2, b3, b4, b5, b6, b7]. Antenna 2 receives the symbols [\bar{b}_4, b_5, b_6, b_7, b_0, \bar{b}_1, b_2, b_3]. The output for both antennas is labeled 'STTD encoded symbols for antenna 1 and antenna 2'.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg)
+
+Figure 8A shows a generic block diagram of the STTD encoder for 16QAM. An input block of eight symbols $b_0, b_1, b_2, b_3, b_4, b_5, b_6, b_7$ (labeled "Symbols") is processed. The symbols are split into two antennas. Antenna 1 receives the symbols $b_0, b_1, b_2, b_3, b_4, b_5, b_6, b_7$ . Antenna 2 receives the symbols $\bar{b}_4, b_5, b_6, b_7, b_0, \bar{b}_1, b_2, b_3$ . The output for both antennas is labeled "STTD encoded symbols for antenna 1 and antenna 2".
+
+Generic block diagram of the STTD encoder for 16QAM. It shows an input block of eight symbols [b0, b1, b2, b3, b4, b5, b6, b7] labeled 'Symbols'. This block is split into two antennas. Antenna 1 receives the symbols [b0, b1, b2, b3, b4, b5, b6, b7]. Antenna 2 receives the symbols [\bar{b}\_4, b\_5, b\_6, b\_7, b\_0, \bar{b}\_1, b\_2, b\_3]. The output for both antennas is labeled 'STTD encoded symbols for antenna 1 and antenna 2'.
+
+**Figure 8A: Generic block diagram of the STTD encoder for 16QAM**
+
+For 64QAM, STTD operates on blocks of 12 consecutive symbols $b_0, b_1, b_2, b_3, b_4, b_5, b_6, b_7, b_8, b_9, b_{10}, b_{11}$ as shown in figure 8B below.
+
+
+
+The diagram illustrates the STTD encoding process for 64QAM. An input block of 12 symbols, labeled $b_0$ through $b_{11}$ , is shown. Below this block is a bracket labeled "Symbols". An arrow points from the input block to a central block labeled "STTD encoder". From the STTD encoder, two arrows point to two output blocks. The top output block is labeled "Antenna 1" and contains the symbols $b_0, b_1, b_2, b_3, b_4, b_5, b_6, b_7, b_8, b_9, b_{10}, b_{11}$ . The bottom output block is labeled "Antenna 2" and contains the symbols $\bar{b}_6, b_7, b_8, b_9, b_{10}, b_{11}, b_0, \bar{b}_1, b_2, b_3, b_4, b_5$ . Below the Antenna 2 block is a bracket labeled "STTD encoded symbols for antenna 1 and antenna 2".
+
+Generic block diagram of the STTD encoder for 64QAM. The diagram shows an input sequence of 12 symbols (b0 to b11) being processed by an STTD encoder. The output is two sequences of 12 symbols each, one for Antenna 1 and one for Antenna 2. Antenna 1's sequence is b0, b1, b2, b3, b4, b5, b6, b7, b8, b9, b10, b11. Antenna 2's sequence is b6-bar, b7, b8, b9, b10, b11, b0, b1-bar, b2, b3, b4, b5. The final output is labeled 'STTD encoded symbols for antenna 1 and antenna 2'.
+
+**Figure 8B: Generic block diagram of the STTD encoder for 64QAM**
+
+##### 5.3.1.1.2 Time Switched Transmit Diversity for SCH (TSTD)
+
+Transmit diversity, in the form of Time Switched Transmit Diversity (TSTD), can be applied to the SCH. TSTD for the SCH is optional in UTRAN, while TSTD support is mandatory in the UE. TSTD for the SCH is described in subclause 5.3.3.5.1.
+
+#### 5.3.1.2 Closed loop transmit diversity
+
+Closed loop transmit diversity is described in [5]. Closed loop transmit diversity mode 1 shall be supported at the UE and may be supported in the UTRAN.
+
+### 5.3.2 Dedicated downlink physical channels
+
+There are five types of downlink dedicated physical channels, the Downlink Dedicated Physical Channel (downlink DPCH), the Fractional Dedicated Physical Channel (F-DPCH), the E-DCH Relative Grant Channel (E-RGCH), the E-DCH Hybrid ARQ Indicator Channel (E-HICH), and the Fractional Transmitted Precoding Indicator Channel (F-TPICH).
+
+The F-DPCH is described in subclause 5.3.2.6.
+
+Within one downlink DPCH, dedicated data generated at Layer 2 and above, i.e. the dedicated transport channel (DCH), is transmitted in time-multiplex with control information generated at Layer 1 (known pilot bits, TPC commands, and an optional TFCI). The downlink DPCH can thus be seen as a time multiplex of a downlink DPDCH and a downlink DPCCH, compare subclause 5.2.1.
+
+Figure 9 shows the frame structure of the downlink DPCH. Each frame of length 10 ms is split into 15 slots, each of length $T_{\text{slot}} = 2560$ chips, corresponding to one power-control period.
+
+
+
+The diagram illustrates the frame structure for downlink DPCH. At the top, a single slot is shown with the following fields:
+
+
+- DPDCH**: Data1 ( $N_{\text{data1}}$ bits)
+- DPCCH**: TPC ( $N_{\text{TPC}}$ bits) and TFCI ( $N_{\text{TFCI}}$ bits)
+- DPDCH**: Data2 ( $N_{\text{data2}}$ bits)
+- DPCCH**: Pilot ( $N_{\text{pilot}}$ bits)
+
+ The total slot duration is $T_{\text{slot}} = 2560 \text{ chips}, 10 \cdot 2^k \text{ bits } (k=0..7)$ .
+ At the bottom, a radio frame is shown, consisting of 15 slots (Slot #0 to Slot #14). The total duration of one radio frame is $T_f = 10 \text{ ms}$ .
+
+Figure 9: Frame structure for downlink DPCH. The diagram shows a single slot structure at the top and a radio frame structure at the bottom. The slot structure consists of five fields: DPDCH (Data1, N\_data1 bits), DPCCH (TPC, N\_TPC bits and TFCI, N\_TFCI bits), DPDCH (Data2, N\_data2 bits), and DPCCH (Pilot, N\_pilot bits). The total slot duration is T\_slot = 2560 chips, 10 \* 2^k bits (k=0..7). The radio frame structure shows 15 slots (Slot #0 to Slot #14) over a duration of One radio frame, T\_f = 10 ms.
+
+**Figure 9: Frame structure for downlink DPCH**
+
+The parameter $k$ in figure 9 determines the total number of bits per downlink DPCH slot. It is related to the spreading factor $SF$ of the physical channel as $SF = 512/2^k$ . The spreading factor may thus range from 512 down to 4.
+
+The exact number of bits of the different downlink DPCH fields ( $N_{\text{pilot}}$ , $N_{\text{TPC}}$ , $N_{\text{TFCI}}$ , $N_{\text{data1}}$ and $N_{\text{data2}}$ ) is given in table 11. What slot format to use is configured by higher layers and can also be reconfigured by higher layers.
+
+There are basically two types of downlink Dedicated Physical Channels; those that include TFCI (e.g. for several simultaneous services) and those that do not include TFCI (e.g. for fixed-rate services). These types are reflected by the duplicated rows of table 11. It is the UTRAN that determines if a TFCI should be transmitted and it is mandatory for all UEs to support the use of TFCI in the downlink. The mapping of TFCI bits onto slots is described in [3].
+
+In compressed frames, a different slot format is used compared to normal mode. There are two possible compressed slot formats that are labelled A and B. Slot format B shall be used in frames compressed by spreading factor reduction and slot format A shall be used in frames compressed by higher layer scheduling. The channel bit and symbol rates given in table 11 are the rates immediately before spreading.
+
+Table 11: DPDCH and DPCCH fields
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Slot | DPDCH Bits/Slot | | DPCCH Bits/Slot | | | Transmitted slots per radio frame N Tr |
+|----------------|-------------------------|----------------------------|-----|-----------|--------------------|--------------------|------------------|-------------------|--------------------|---------------------------------------------------|
+| | | | | | N Data1 | N Data2 | N TPC | N TFCI | N Pilot | |
+| 0 | 15 | 7.5 | 512 | 10 | 0 | 4 | 2 | 0 | 4 | 15 |
+| 0A | 15 | 7.5 | 512 | 10 | 0 | 4 | 2 | 0 | 4 | 8-14 |
+| 0B | 30 | 15 | 256 | 20 | 0 | 8 | 4 | 0 | 8 | 8-14 |
+| 1 | 15 | 7.5 | 512 | 10 | 0 | 2 | 2 | 2 | 4 | 15 |
+| 1B | 30 | 15 | 256 | 20 | 0 | 4 | 4 | 4 | 8 | 8-14 |
+| 2 | 30 | 15 | 256 | 20 | 2 | 14 | 2 | 0 | 2 | 15 |
+| 2A | 30 | 15 | 256 | 20 | 2 | 14 | 2 | 0 | 2 | 8-14 |
+| 2B | 60 | 30 | 128 | 40 | 4 | 28 | 4 | 0 | 4 | 8-14 |
+| 3 | 30 | 15 | 256 | 20 | 2 | 12 | 2 | 2 | 2 | 15 |
+| 3A | 30 | 15 | 256 | 20 | 2 | 10 | 2 | 4 | 2 | 8-14 |
+| 3B | 60 | 30 | 128 | 40 | 4 | 24 | 4 | 4 | 4 | 8-14 |
+| 4 | 30 | 15 | 256 | 20 | 2 | 12 | 2 | 0 | 4 | 15 |
+| 4A | 30 | 15 | 256 | 20 | 2 | 12 | 2 | 0 | 4 | 8-14 |
+| 4B | 60 | 30 | 128 | 40 | 4 | 24 | 4 | 0 | 8 | 8-14 |
+| 5 | 30 | 15 | 256 | 20 | 2 | 10 | 2 | 2 | 4 | 15 |
+| 5A | 30 | 15 | 256 | 20 | 2 | 8 | 2 | 4 | 4 | 8-14 |
+| 5B | 60 | 30 | 128 | 40 | 4 | 20 | 4 | 4 | 8 | 8-14 |
+| 6 | 30 | 15 | 256 | 20 | 2 | 8 | 2 | 0 | 8 | 15 |
+| 6A | 30 | 15 | 256 | 20 | 2 | 8 | 2 | 0 | 8 | 8-14 |
+| 6B | 60 | 30 | 128 | 40 | 4 | 16 | 4 | 0 | 16 | 8-14 |
+| 7 | 30 | 15 | 256 | 20 | 2 | 6 | 2 | 2 | 8 | 15 |
+| 7A | 30 | 15 | 256 | 20 | 2 | 4 | 2 | 4 | 8 | 8-14 |
+| 7B | 60 | 30 | 128 | 40 | 4 | 12 | 4 | 4 | 16 | 8-14 |
+| 8 | 60 | 30 | 128 | 40 | 6 | 28 | 2 | 0 | 4 | 15 |
+| 8A | 60 | 30 | 128 | 40 | 6 | 28 | 2 | 0 | 4 | 8-14 |
+| 8B | 120 | 60 | 64 | 80 | 12 | 56 | 4 | 0 | 8 | 8-14 |
+| 9 | 60 | 30 | 128 | 40 | 6 | 26 | 2 | 2 | 4 | 15 |
+| 9A | 60 | 30 | 128 | 40 | 6 | 24 | 2 | 4 | 4 | 8-14 |
+| 9B | 120 | 60 | 64 | 80 | 12 | 52 | 4 | 4 | 8 | 8-14 |
+| 10 | 60 | 30 | 128 | 40 | 6 | 24 | 2 | 0 | 8 | 15 |
+| 10A | 60 | 30 | 128 | 40 | 6 | 24 | 2 | 0 | 8 | 8-14 |
+| 10B | 120 | 60 | 64 | 80 | 12 | 48 | 4 | 0 | 16 | 8-14 |
+| 11 | 60 | 30 | 128 | 40 | 6 | 22 | 2 | 2 | 8 | 15 |
+| 11A | 60 | 30 | 128 | 40 | 6 | 20 | 2 | 4 | 8 | 8-14 |
+| 11B | 120 | 60 | 64 | 80 | 12 | 44 | 4 | 4 | 16 | 8-14 |
+| 12 | 120 | 60 | 64 | 80 | 12 | 48 | 4 | 8* | 8 | 15 |
+| 12A | 120 | 60 | 64 | 80 | 12 | 40 | 4 | 16* | 8 | 8-14 |
+| 12B | 240 | 120 | 32 | 160 | 24 | 96 | 8 | 16* | 16 | 8-14 |
+| 13 | 240 | 120 | 32 | 160 | 28 | 112 | 4 | 8* | 8 | 15 |
+| 13A | 240 | 120 | 32 | 160 | 28 | 104 | 4 | 16* | 8 | 8-14 |
+| 13B | 480 | 240 | 16 | 320 | 56 | 224 | 8 | 16* | 16 | 8-14 |
+| 14 | 480 | 240 | 16 | 320 | 56 | 232 | 8 | 8* | 16 | 15 |
+| 14A | 480 | 240 | 16 | 320 | 56 | 224 | 8 | 16* | 16 | 8-14 |
+| 14B | 960 | 480 | 8 | 640 | 112 | 464 | 16 | 16* | 32 | 8-14 |
+| 15 | 960 | 480 | 8 | 640 | 120 | 488 | 8 | 8* | 16 | 15 |
+| 15A | 960 | 480 | 8 | 640 | 120 | 480 | 8 | 16* | 16 | 8-14 |
+| 15B | 1920 | 960 | 4 | 1280 | 240 | 976 | 16 | 16* | 32 | 8-14 |
+| 16 | 1920 | 960 | 4 | 1280 | 248 | 1000 | 8 | 8* | 16 | 15 |
+| 16A | 1920 | 960 | 4 | 1280 | 248 | 992 | 8 | 16* | 16 | 8-14 |
+
+\* If TFCI bits are not used, then DTX shall be used in TFCI field.
+
+NOTE 1: Compressed mode is only supported through spreading factor reduction for SF=512 with TFCI.
+
+NOTE 2: Compressed mode by spreading factor reduction is not supported for SF=4.
+
+NOTE 3: If the Node B receives an invalid combination of data frames for downlink transmission, the procedure specified in [15], sub-clause 5.1.2, may require the use of DTX in both the DPDCH and the TFCI field of the DPCCH.
+
+The pilot bit patterns are described in table 12. The shadowed column part of pilot bit pattern is defined as FSW and FSWs can be used to confirm frame synchronization. (The value of the pilot bit pattern other than FSWs shall be "11".) In table 12, the transmission order is from left to right.
+
+In downlink compressed mode through spreading factor reduction, the number of bits in the TPC and Pilot fields are doubled. Symbol repetition is used to fill up the fields. Denote the bits in one of these fields in normal mode by $x_1, x_2, x_3, \dots, x_X$ . In compressed mode the following bit sequence is sent in corresponding field: $x_1, x_2, x_1, x_2, x_3, x_4, x_3, x_4, \dots, x_X$ .
+
+**Table 12: Pilot bit patterns for downlink DPCCH with $N_{pilot} = 2, 4, 8$ and 16**
+
+| Symbol # | $N_{pilot} = 2$ | $N_{pilot} = 4$
(*1) | | $N_{pilot} = 8$
(*2) | | | | $N_{pilot} = 16$
(*3) | | | | | | | |
+|----------|-----------------|-------------------------|----|-------------------------|----|----|----|--------------------------|----|----|----|----|----|----|----|
+| | 0 | 0 | 1 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| Slot #0 | 11 | 11 | 11 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 10 |
+| 1 | 00 | 11 | 00 | 11 | 00 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 11 | 11 | 00 |
+| 2 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 10 | 11 | 00 |
+| 3 | 00 | 11 | 00 | 11 | 00 | 11 | 00 | 11 | 00 | 11 | 00 | 11 | 01 | 11 | 10 |
+| 4 | 10 | 11 | 10 | 11 | 10 | 11 | 01 | 11 | 10 | 11 | 01 | 11 | 11 | 11 | 11 |
+| 5 | 11 | 11 | 11 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 10 | 11 | 01 | 11 | 01 |
+| 6 | 11 | 11 | 11 | 11 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 10 | 11 | 11 |
+| 7 | 10 | 11 | 10 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 00 |
+| 8 | 01 | 11 | 01 | 11 | 01 | 11 | 10 | 11 | 01 | 11 | 10 | 11 | 00 | 11 | 11 |
+| 9 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 00 | 11 | 11 |
+| 10 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 11 | 11 | 10 |
+| 11 | 10 | 11 | 10 | 11 | 10 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 00 | 11 | 10 |
+| 12 | 10 | 11 | 10 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 00 | 11 | 01 | 11 | 01 |
+| 13 | 00 | 11 | 00 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 00 |
+| 14 | 00 | 11 | 00 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 11 | 10 | 11 | 01 |
+
+NOTE \*1: This pattern is used except slot formats 2B and 3B.
+
+NOTE \*2: This pattern is used except slot formats 0B, 1B, 4B, 5B, 8B, and 9B.
+
+NOTE \*3: This pattern is used except slot formats 6B, 7B, 10B, 11B, 12B, and 13B.
+
+NOTE: For slot format $nB$ where $n = 0, \dots, 15$ , the pilot bit pattern corresponding to $N_{pilot}/2$ is to be used and symbol repetition shall be applied.
+
+The relationship between the TPC symbol and the transmitter power control command is presented in table 13.
+
+**Table 13: TPC Bit Pattern**
+
+| TPC Bit Pattern | | | Transmitter power control command |
+|-----------------|---------------|---------------|-----------------------------------|
+| $N_{TPC} = 2$ | $N_{TPC} = 4$ | $N_{TPC} = 8$ | |
+| 11 | 1111 | 11111111 | 1 |
+| 00 | 0000 | 00000000 | 0 |
+
+Multicode transmission may be employed in the downlink, i.e. the CCTrCH (see [3]) is mapped onto several parallel downlink DPCHs using the same spreading factor. In this case, the Layer 1 control information is transmitted only on the first downlink DPCH. DTX bits are transmitted during the corresponding time period for the additional downlink DPCHs, see figure 10.
+
+In case there are several CCTrCHs mapped to different DPCHs transmitted to the same UE different spreading factors can be used on DPCHs to which different CCTrCHs are mapped. Also in this case, Layer 1 control information is only transmitted on the first DPCH while DTX bits are transmitted during the corresponding time period for the additional DPCHs.
+
+Note : support of multiple CCTrCHs of dedicated type is not part of the current release.
+
+
+
+Figure 10: Downlink slot format in case of multi-code transmission. The diagram shows three horizontal axes representing Transmission Power for Physical Channel 1, Physical Channel 2, and Physical Channel L. Each axis has a rectangular pulse. Above the first channel, the pulse is divided into three segments labeled TPC, TFCI, and Pilot. The TPC and TFCI segments are shaded. Above the pulse, two double-headed arrows labeled DPDCH indicate the duration of the data fields. A vertical dashed line separates the TPC and TFCI segments. A horizontal double-headed arrow at the bottom indicates the duration of 'One Slot (2560 chips)'.
+
+**Figure 10: Downlink slot format in case of multi-code transmission**
+
+#### 5.3.2.1 STTD for DPCH, F-DPCH and F-TPICH
+
+The pilot bit pattern for the DPCH channel transmitted on antenna 2 is given in table 14.
+
+- For $N_{\text{pilot}} = 8, 16$ the shadowed part indicates pilot bits that are obtained by STTD encoding the corresponding (shadowed) bits in Table 12. The non-shadowed pilot bit pattern is orthogonal to the corresponding (non-shadowed) pilot bit pattern in table 12.
+- For $N_{\text{pilot}} = 4$ , the diversity antenna pilot bit pattern is obtained by STTD encoding both the shadowed and non-shadowed pilot bits in table 12.
+- For $N_{\text{pilot}} = 2$ , the diversity antenna pilot pattern is obtained by STTD encoding the two pilot bits in table 12 with the last two bits (data or DTX) of the second data field (data2) of the slot. Thus for $N_{\text{pilot}} = 2$ case, the last two bits of the second data field (data 2) after STTD encoding, follow the diversity antenna pilot bits in Table 14.
+
+STTD encoding for the DPDCH, TPC, and TFCI fields is done as described in subclause 5.3.1.1.1. For the SF=512 DPCH, the first two bits in each slot, i.e. TPC bits, are not STTD encoded and the same bits are transmitted with equal power from the two antennas. The remaining four bits are STTD encoded.
+
+For F-DPCH, the TPC bits are not STTD encoded and the same bits are transmitted with equal power from the two antennas.
+
+For F-TPICH, the TPI bits are not STTD encoded and the same bits are transmitted with equal power from the two antennas.
+
+For compressed mode through spreading factor reduction and for $N_{\text{pilot}} > 4$ , symbol repetition shall be applied to the pilot bit patterns of table 14, in the same manner as described in 5.3.2. For slot formats 2B and 3B, i.e. compressed mode through spreading factor reduction and $N_{\text{pilot}} = 4$ , the pilot bits transmitted on antenna 2 are STTD encoded, and thus the pilot bit pattern is as shown in the most right set of table 14.
+
+**Table 14: Pilot bit patterns of downlink DPCCH for antenna 2 using STTD**
+
+| Symbol # | $N_{pilot} = 2$ | $N_{pilot} = 4$ | | $N_{pilot} = 8$ | | | | $N_{pilot} = 16$ | | | | | | | | $N_{pilot} = 4$ | |
+|----------------|-----------------|-----------------|----|-----------------|----|----|----|------------------|----|----|----|----|----|----|----|-----------------|----|
+| | 0 | 0 | 1 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 0 | 1 |
+| Slot #0 | 01 | 01 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 01 | 10 |
+| 1 | 10 | 10 | 10 | 11 | 00 | 00 | 01 | 11 | 00 | 00 | 01 | 11 | 10 | 00 | 10 | 10 | 01 |
+| 2 | 11 | 11 | 10 | 11 | 11 | 00 | 00 | 11 | 11 | 00 | 00 | 11 | 10 | 00 | 11 | 11 | 00 |
+| 3 | 10 | 10 | 10 | 11 | 10 | 00 | 01 | 11 | 10 | 00 | 01 | 11 | 00 | 00 | 00 | 10 | 01 |
+| 4 | 00 | 00 | 10 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 01 | 00 | 10 | 00 | 11 |
+| 5 | 01 | 01 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 11 | 11 | 00 | 00 | 01 | 10 |
+| 6 | 01 | 01 | 10 | 11 | 10 | 00 | 10 | 11 | 10 | 00 | 10 | 11 | 01 | 00 | 11 | 01 | 10 |
+| 7 | 00 | 00 | 10 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 00 | 11 |
+| 8 | 11 | 11 | 10 | 11 | 00 | 00 | 00 | 11 | 00 | 00 | 00 | 11 | 01 | 00 | 01 | 11 | 00 |
+| 9 | 01 | 01 | 10 | 11 | 01 | 00 | 10 | 11 | 01 | 00 | 10 | 11 | 01 | 00 | 01 | 01 | 10 |
+| 10 | 11 | 11 | 10 | 11 | 11 | 00 | 00 | 11 | 11 | 00 | 00 | 11 | 00 | 00 | 10 | 11 | 00 |
+| 11 | 00 | 00 | 10 | 11 | 01 | 00 | 11 | 11 | 01 | 00 | 11 | 11 | 00 | 00 | 01 | 00 | 11 |
+| 12 | 00 | 00 | 10 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 11 | 11 | 00 | 00 | 00 | 11 |
+| 13 | 10 | 10 | 10 | 11 | 01 | 00 | 01 | 11 | 01 | 00 | 01 | 11 | 10 | 00 | 01 | 10 | 01 |
+| 14 | 10 | 10 | 10 | 11 | 01 | 00 | 01 | 11 | 01 | 00 | 01 | 11 | 11 | 00 | 11 | 10 | 01 |
+
+NOTE \*1: The pilot bits precede the last two bits of the data2 field.
+
+NOTE \*2: This pattern is used except slot formats 2B and 3B.
+
+NOTE \*3: This pattern is used except slot formats 0B, 1B, 4B, 5B, 8B, and 9B.
+
+NOTE \*4: This pattern is used except slot formats 6B, 7B, 10B, 11B, 12B, and 13B.
+
+NOTE \*5: This pattern is used for slot formats 2B and 3B.
+
+NOTE: For slot format $nB$ where $n = 0, 1, 4, 5, 6, \dots, 15$ , the pilot bit pattern corresponding to $N_{pilot}/2$ is to be used and symbol repetition shall be applied.
+
+#### 5.3.2.2 Dedicated channel pilots with closed loop mode transmit diversity
+
+In closed loop mode 1 orthogonal pilot patterns are used between the transmit antennas. Closed loop mode 1 shall not be used with DPCH slot formats for which $N_{pilot}=2$ . Pilot patterns defined in the table 12 will be used on antenna 1 and pilot patterns defined in the table 15 on antenna 2. This is illustrated in the figure 11 a which indicates the difference in the pilot patterns with different shading.
+
+**Table 15: Pilot bit patterns of downlink DPCCH for antenna 2 using closed loop mode 1**
+
+| Symbol # | $N_{pilot} = 4$ | | $N_{pilot} = 8$ | | | | $N_{pilot} = 16$ | | | | | | | |
+|----------------|-----------------|----|-----------------|----|----|----|------------------|----|----|----|----|----|----|----|
+| | 0 | 1 | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| Slot #0 | 01 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 |
+| 1 | 10 | 10 | 11 | 00 | 00 | 01 | 11 | 00 | 00 | 01 | 11 | 10 | 00 | 10 |
+| 2 | 11 | 10 | 11 | 11 | 00 | 00 | 11 | 11 | 00 | 00 | 11 | 10 | 00 | 11 |
+| 3 | 10 | 10 | 11 | 10 | 00 | 01 | 11 | 10 | 00 | 01 | 11 | 00 | 00 | 00 |
+| 4 | 00 | 10 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 01 | 00 | 10 |
+| 5 | 01 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 11 | 11 | 00 | 00 |
+| 6 | 01 | 10 | 11 | 10 | 00 | 10 | 11 | 10 | 00 | 10 | 11 | 01 | 00 | 11 |
+| 7 | 00 | 10 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 |
+| 8 | 11 | 10 | 11 | 00 | 00 | 00 | 11 | 00 | 00 | 00 | 11 | 01 | 00 | 01 |
+| 9 | 01 | 10 | 11 | 01 | 00 | 10 | 11 | 01 | 00 | 10 | 11 | 01 | 00 | 01 |
+| 10 | 11 | 10 | 11 | 11 | 00 | 00 | 11 | 11 | 00 | 00 | 11 | 00 | 00 | 10 |
+| 11 | 00 | 10 | 11 | 01 | 00 | 11 | 11 | 01 | 00 | 11 | 11 | 00 | 00 | 01 |
+| 12 | 00 | 10 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 11 | 11 | 00 | 00 |
+| 13 | 10 | 10 | 11 | 01 | 00 | 01 | 11 | 01 | 00 | 01 | 11 | 10 | 00 | 01 |
+| 14 | 10 | 10 | 11 | 01 | 00 | 01 | 11 | 01 | 00 | 01 | 11 | 11 | 00 | 11 |
+
+NOTE \*1: This pattern is used except slot formats 0B, 1B, 4B, 5B, 8B, and 9B.
+
+NOTE \*2: This pattern is used except slot formats 6B, 7B, 10B, 11B, 12B, and 13B.
+
+NOTE: For slot format $nB$ where $n = 0, 1, 4, 5, 6, \dots, 15$ , the pilot bit pattern corresponding to $N_{pilot}/2$ is to be used and symbol repetition shall be applied.
+
+
+
+| | Slot i | | | | | Slot i+1 | | | | |
+|-----------|---------|-------|--------|---------|---------|----------|-------|--------|---------|---------|
+| Antenna 1 | N_Data1 | N_TPC | N_TFCI | N_Data2 | N_Pilot | N_Data1 | N_TPC | N_TFCI | N_Data2 | N_Pilot |
+| Antenna 2 | N_Data1 | N_TPC | N_TFCI | N_Data2 | N_Pilot | N_Data1 | N_TPC | N_TFCI | N_Data2 | N_Pilot |
+
+Figure 11: Slot structures for downlink dedicated physical channel diversity transmission. The diagram shows two antennas, Antenna 1 and Antenna 2, across two slots, Slot i and Slot i+1. Each slot contains fields: N\_Data1, N\_TPC, N\_TFCI, N\_Data2, and N\_Pilot. In Slot i, Antenna 1 has a solid grey N\_Pilot, while Antenna 2 has a dotted N\_Pilot. In Slot i+1, Antenna 1 has a solid grey N\_Pilot, while Antenna 2 has a dotted N\_Pilot.
+
+(a)
+
+**Figure 11: Slot structures for downlink dedicated physical channel diversity transmission. Structure (a) is used in closed loop mode 1. Different shading of the pilots indicate orthogonality of the patterns**
+
+#### **5.3.2.3 Void**
+
+#### **5.3.2.4 E-DCH Relative Grant Channel**
+
+An E-DCH Relative Grant Channel (E-RGCH) is a fixed rate (SF=128) dedicated downlink physical channel carrying the uplink E-DCH relative grants for one uplink E-DCH associated with the E-RGCH by higher layer signalling. Figure 12A illustrates the structure of the E-RGCH. A relative grant is transmitted using 3, 12 or 15 consecutive slots and in each slot a sequence of 40 ternary values is transmitted. The 3 and 12 slot duration shall be used on an E-RGCH transmitted to UEs for which the cell transmitting the E-RGCH is in the E-DCH serving radio link set and for which the E-DCH TTI is respectively 2 and 10 ms. The 15 slot duration shall be used on an E-RGCH transmitted to UEs for which the cell transmitting the E-RGCH is not in the E-DCH serving radio link set.
+
+The sequence $b_{i,0}, b_{i,1}, \dots, b_{i,39}$ transmitted in slot $i$ in Figure 12A is given by $b_{i,j} = a C_{ss,40,m(i),j}$ . In a serving E-DCH radio link set, the relative grant $a$ is set to +1, 0, or -1 and in a radio link not belonging to the serving E-DCH radio link set, the relative grant $a$ is set to 0 or -1. The orthogonal signature sequences $C_{ss,40,m(i)}$ is given by Table 16A and the index $m(i)$ in slot $i$ is given by Table 16B. The E-RGCH signature sequence index $l$ in Table 16B is given by higher layers.
+
+In case STTD-based open loop transmit diversity is applied for E-RGCH, STTD encoding according to subclause 5.3.1.1.1 is applied to the sequence $b_{i,j}$ .
+
+
+
+The diagram illustrates the structure of the E-RGCH and E-HICH. The top part shows a sequence of 40 ternary values $b_{i,0}, b_{i,1}, \dots, b_{i,39}$ transmitted in a slot, with a total duration of $T_{slot} = 2560$ chip. The bottom part shows a sequence of slots Slot #0, Slot #1, Slot #2, ..., Slot #i, ..., Slot #14, which constitute 1 radio frame with a duration of $T_f = 10$ ms. A subframe duration of 2 ms is also indicated.
+
+Figure 12A: E-RGCH and E-HICH structure. The top part shows a sequence of 40 ternary values b\_i,0, b\_i,1, ..., b\_i,39 over a slot duration T\_slot = 2560 chip. The bottom part shows a sequence of slots Slot #0, Slot #1, Slot #2, ..., Slot #i, ..., Slot #14 over a radio frame duration T\_f = 10 ms. A subframe duration of 2 ms is also indicated.
+
+**Figure 12A: E-RGCH and E-HICH structure**
+
+**Error:**
+
+29
+
+**Error: Reference source not**
+
+**Table 16A: E-RGCH and E-HICH signature sequences**
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| C ss,40,0 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | |
+| C ss,40,1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 |
+| C ss,40,2 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
+| C ss,40,3 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
+| C ss,40,4 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 |
+| C ss,40,5 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 |
+| C ss,40,6 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 |
+| C ss,40,7 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 |
+| C ss,40,8 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 |
+| C ss,40,9 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 |
+| C ss,40,10 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 |
+| C ss,40,11 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 |
+| C ss,40,12 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 |
+| C ss,40,13 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 |
+| C ss,40,14 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 |
+| C ss,40,15 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 |
+| C ss,40,16 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
+| C ss,40,17 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 |
+| C ss,40,18 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 |
+| C ss,40,19 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 |
+| C ss,40,20 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 |
+| C ss,40,21 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 |
+| C ss,40,22 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 |
+| C ss,40,23 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 |
+| C ss,40,24 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 |
+| C ss,40,25 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 |
+| C ss,40,26 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 |
+| C ss,40,27 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 |
+| C ss,40,28 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 |
+| C ss,40,29 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 |
+| C ss,40,30 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 |
+| C ss,40,31 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 |
+| C ss,40,32 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 |
+| C ss,40,33 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 |
+| C ss,40,34 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 |
+| C ss,40,35 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 |
+| C ss,40,36 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 |
+| C ss,40,37 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 |
+| C ss,40,38 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 |
+| C ss,40,39 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 |
+
+The bits are transmitted in order from left to right, i.e., column 2 corresponds to index $j=0$ and the rightmost column corresponds to index $j=39$ .
+
+**Table 16B: E-HICH and E-RGCH signature hopping pattern**
+
+| Sequence index
l | Row index m(i) for slot i | | |
+|----------------------------|-----------------------------------------|----|----|
+| | 0 | 2 | 13 |
+| 0 | 0 | 2 | 13 |
+| 1 | 1 | 18 | 18 |
+| 2 | 2 | 8 | 33 |
+| 3 | 3 | 16 | 32 |
+| 4 | 4 | 13 | 10 |
+| 5 | 5 | 3 | 25 |
+| 6 | 6 | 12 | 16 |
+| 7 | 7 | 6 | 1 |
+| 8 | 8 | 19 | 39 |
+| 9 | 9 | 34 | 14 |
+| 10 | 10 | 4 | 5 |
+| 11 | 11 | 17 | 34 |
+
+| | | | |
+|----|----|----|----|
+| 12 | 12 | 29 | 30 |
+| 13 | 13 | 11 | 23 |
+| 14 | 14 | 24 | 22 |
+| 15 | 15 | 28 | 21 |
+| 16 | 16 | 35 | 19 |
+| 17 | 17 | 21 | 36 |
+| 18 | 18 | 37 | 2 |
+| 19 | 19 | 23 | 11 |
+| 20 | 20 | 39 | 9 |
+| 21 | 21 | 22 | 3 |
+| 22 | 22 | 9 | 15 |
+| 23 | 23 | 36 | 20 |
+| 24 | 24 | 0 | 26 |
+| 25 | 25 | 5 | 24 |
+| 26 | 26 | 7 | 8 |
+| 27 | 27 | 27 | 17 |
+| 28 | 28 | 32 | 29 |
+| 29 | 29 | 15 | 38 |
+| 30 | 30 | 30 | 12 |
+| 31 | 31 | 26 | 7 |
+| 32 | 32 | 20 | 37 |
+| 33 | 33 | 1 | 35 |
+| 34 | 34 | 14 | 0 |
+| 35 | 35 | 33 | 31 |
+| 36 | 36 | 25 | 28 |
+| 37 | 37 | 10 | 27 |
+| 38 | 38 | 31 | 4 |
+| 39 | 39 | 38 | 6 |
+
+#### 5.3.2.5 E-DCH Hybrid ARQ Indicator Channel
+
+An E-DCH Hybrid ARQ Indicator Channel (E-HICH) is a fixed rate (SF=128) dedicated downlink physical channel carrying the uplink E-DCH hybrid ARQ acknowledgement indicator for one uplink E-DCH.
+
+The uplink E-DCH is associated with the E-HICH signature sequence(s) provided by higher layer signalling. Figure 12A illustrates the structure of the E-HICH. A hybrid ARQ acknowledgement indicator is transmitted using 3 or 12 consecutive slots and in each slot a sequence of 40 binary values is transmitted. The 3 and 12 slot duration shall be used for UEs which E-DCH TTI is set to respectively 2 ms and 10 ms.
+
+The sequence $b_{i,0}, b_{i,1}, \dots, b_{i,39}$ transmitted in slot $i$ in Figure 12A is given by $b_{i,j} = a \cdot C_{ss,40,m(i),j}$ . In a radio link set containing the serving E-DCH radio link set, the hybrid ARQ acknowledgement indicator $a$ is set to $+1$ or $-1$ , and in a radio link set not containing the serving E-DCH radio link set the hybrid ARQ indicator $a$ is set to $+1$ or $0$ . The orthogonal signature sequences $C_{ss,40,m(i)}$ is given by Table 16A and the index $m(i)$ in slot $i$ is given by Table 16B. The E-HICH signature sequence index $l$ is given by higher layers.
+
+In case STTD-based open loop transmit diversity is applied for E-HICH, STTD encoding according to subclause 5.3.1.1.1 is applied to the sequence $b_{i,j}$
+
+If UL\_MIMO\_Enabled is TRUE, the UE is configured with a second E-HICH signature sequence associated with HARQ acknowledgments for the transport block transmitted on S-E-DPDCHs.
+
+#### 5.3.2.6 Fractional Dedicated Physical Channel (F-DPCH)
+
+An F-DPCH carries control information generated at layer 1 (TPC commands) for one uplink DPCCH associated with the F-DPCH by higher layer signalling. It is a special case of downlink DPCCH.
+
+Figure 12B shows the frame structure of the F-DPCH. Each frame of length 10ms is split into 15 slots, each of length $T_{slot} = 2560$ chips, corresponding to one power-control period.
+
+
+
+Figure 12B: Frame structure for F-DPCH. The diagram shows a slot structure at the top and a radio frame structure at the bottom. The slot structure consists of three fields: (Tx OFF) N\_OFF1 bits, TPC N\_TPC bits, and (Tx OFF) N\_OFF2 bits. The total slot duration is T\_slot = 2560 chips. The radio frame structure shows 15 slots, labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a total duration of 1 radio frame: T\_f = 10 ms.
+
+Figure 12B: Frame structure for F-DPCH
+
+The exact number of bits of the OFF periods and of the F-DPCH fields ( $N_{TPC}$ ) is described in table 16C. Each slot format corresponds to a different set of OFF periods within the F-DPCH slot.
+
+Table 16C: F-DPCH fields
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/ Slot | $N_{OFF1}$ Bits/Slot | $N_{TPC}$ Bits/Slot | $N_{OFF2}$ Bits/Slot |
+|----------------|-------------------------|----------------------------|-----|------------|----------------------|---------------------|----------------------|
+| 0 | 3 | 1.5 | 256 | 20 | 2 | 2 | 16 |
+| 1 | 3 | 1.5 | 256 | 20 | 4 | 2 | 14 |
+| 2 | 3 | 1.5 | 256 | 20 | 6 | 2 | 12 |
+| 3 | 3 | 1.5 | 256 | 20 | 8 | 2 | 10 |
+| 4 | 3 | 1.5 | 256 | 20 | 10 | 2 | 8 |
+| 5 | 3 | 1.5 | 256 | 20 | 12 | 2 | 6 |
+| 6 | 3 | 1.5 | 256 | 20 | 14 | 2 | 4 |
+| 7 | 3 | 1.5 | 256 | 20 | 16 | 2 | 2 |
+| 8 | 3 | 1.5 | 256 | 20 | 18 | 2 | 0 |
+| 9 | 3 | 1.5 | 256 | 20 | 0 | 2 | 18 |
+
+In compressed frames, F-DPCH is not transmitted in downlink transmission gaps given by transmission gap pattern sequences signalled by higher layers.
+
+The relationship between the TPC symbol and the transmitter power control command is according to table 13.
+
+#### 5.3.2.7 Fractional Transmitted Precoding Indicator Channel (F-TPICH)
+
+An F-TPICH carries transmitted precoding indicator generated at layer 1 for uplink CLTD operation.
+
+Figure 12C shows the frame structure of the F-TPICH. Each frame of length 10ms is split into 15 slots, each of length $T_{slot} = 2560$ chips. A TPI is transmitted using the first two consecutive slots within one subframe, and in each slot one symbol is transmitted using the same slot format.
+
+
+
+Figure 12C: Frame structure for F-TPICH. The diagram shows a slot structure at the top and a subframe structure at the bottom. The slot structure consists of three fields: (Tx OFF) N\_OFF1 bits, TPI N\_TPI bits, and (Tx OFF) N\_OFF2 bits. The total slot duration is T\_slot = 2560 chips. The subframe structure shows 5 subframes, labeled Subframe #0, Subframe #i, and Subframe #4, with a total duration of 1 radio frame: T\_f = 10 ms.
+
+Figure 12C: Frame structure for F-TPICH
+
+The exact number of bits of the OFF periods and of the F-TPICH fields ( $N_{TPI}$ ) is described in table 16D. Each slot format corresponds to a different set of OFF periods within the F-TPICH slot.
+
+Table 16D: F-TPICH fields
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/ Slot | $N_{OFF1}$ Bits/Slot | $N_{TPI}$ Bits/Slot | $N_{OFF2}$ Bits/Slot |
+|----------------|-------------------------|----------------------------|-----|------------|----------------------|---------------------|----------------------|
+| 0 | 3 | 1.5 | 256 | 20 | 2 | 2 | 16 |
+| 1 | 3 | 1.5 | 256 | 20 | 4 | 2 | 14 |
+| 2 | 3 | 1.5 | 256 | 20 | 6 | 2 | 12 |
+| 3 | 3 | 1.5 | 256 | 20 | 8 | 2 | 10 |
+| 4 | 3 | 1.5 | 256 | 20 | 10 | 2 | 8 |
+| 5 | 3 | 1.5 | 256 | 20 | 12 | 2 | 6 |
+| 6 | 3 | 1.5 | 256 | 20 | 14 | 2 | 4 |
+| 7 | 3 | 1.5 | 256 | 20 | 16 | 2 | 2 |
+| 8 | 3 | 1.5 | 256 | 20 | 18 | 2 | 0 |
+| 9 | 3 | 1.5 | 256 | 20 | 0 | 2 | 18 |
+
+The relationship between TPI and bit pattern on F-TPICH is defined in [5].
+
+For a given UE, the TPI feedback bits are not transmitted on F-TPICH bits that overlap with the TPC bits on the F-DPCH channel.
+
+In compressed frames, if one of the two slots corresponding to the TPI indication overlaps with the downlink transmission gaps given by transmission gap pattern sequences signalled by higher layers, neither of the slots is transmitted.
+
+### 5.3.3 Common downlink physical channels
+
+#### 5.3.3.1 Common Pilot Channel (CPICH)
+
+The CPICH is a fixed rate (30 kbps, SF=256) downlink physical channel that carries a pre-defined bit sequence. Figure 13 shows the frame structure of the CPICH.
+
+
+
+Figure 13: Frame structure for Common Pilot Channel. The diagram shows a 'Pre-defined bit sequence' represented by a long horizontal bar at the top. Below it, a double-headed arrow indicates a duration labeled 'T\_slot = 2560 chips, 20 bits'. At the bottom, a horizontal bar represents '1 radio frame: T\_f = 10 ms', which is divided into slots. The first two slots are labeled 'Slot #0' and 'Slot #1', followed by a gap, then 'Slot #i', another gap, and finally 'Slot #14'. Two diagonal lines connect the ends of the 'Pre-defined bit sequence' bar to the boundaries of 'Slot #i'.
+
+Figure 13: Frame structure for Common Pilot Channel
+
+In case transmit diversity is used on P-CCPCH and SCH, the CPICH shall be transmitted from both antennas using the same channelization and scrambling code. In this case, the pre-defined bit sequence of the CPICH is different for Antenna 1 and Antenna 2, see figure 14. In case of no transmit diversity, the bit sequence of Antenna 1 in figure 14 is used.
+
+
+
+The diagram illustrates the modulation pattern for the Common Pilot Channel across two antennas. Antenna 1 is shown with a continuous sequence of '0' bits. Antenna 2 shows a sequence of '1' and '0' bits. Below the bit sequences, the timeline is divided into slots, with slot #14, slot #0, and slot #1 explicitly labeled. A vertical double-headed arrow indicates the 'Frame Boundary' between slot #14 and slot #0. The frame containing slot #14 is labeled 'Frame#i', and the frame containing slot #0 and slot #1 is labeled 'Frame#i+1'.
+
+Figure 14: Modulation pattern for Common Pilot Channel. The diagram shows two antenna transmission sequences over time. Antenna 1 transmits a sequence of 0s. Antenna 2 transmits a sequence of 1s and 0s. Below the sequences, slots are identified: slot #14, slot #0, and slot #1. A 'Frame Boundary' is marked between slot #14 and slot #0. The frames are labeled Frame#i and Frame#i+1.
+
+**Figure 14: Modulation pattern for Common Pilot Channel**
+
+There are two types of Common pilot channels, the Primary and Secondary CPICH. They differ in their use and the limitations placed on their physical features.
+
+##### 5.3.3.1.1 Primary Common Pilot Channel (P-CPICH)
+
+The Primary Common Pilot Channel (P-CPICH) has the following characteristics:
+
+- The same channelization code is always used for the P-CPICH, see [4];
+- The P-CPICH is scrambled by the primary scrambling code, see [4];
+- There is one and only one P-CPICH per cell;
+- The P-CPICH is broadcast over the entire cell.
+
+##### 5.3.3.1.2 Secondary Common Pilot Channel (S-CPICH)
+
+A Secondary Common Pilot Channel (S-CPICH) has the following characteristics:
+
+- An arbitrary channelization code of SF=256 is used for the S-CPICH, see [4];
+- An S-CPICH is scrambled by either the primary or a secondary scrambling code, see [4];
+- There may be zero, one, or several S-CPICH per cell;
+- An S-CPICH may be transmitted over the entire cell or only over a part of the cell;
+- An S-CPICH that is intended to be used as phase reference for the second, third or fourth transmit antenna by UEs configured in MIMO mode or in MIMO mode with four transmit antennas shall be transmitted over the entire cell using the primary scrambling code and the antenna 1 pattern.
+
+##### 5.3.3.1.3 Demodulation Common Pilot Channel (D-CPICH)
+
+A Demodulation Common Pilot Channel (D-CPICH) has the following characteristics:
+
+- An arbitrary channelization code of SF=256 is used for the D-CPICH, see [4];
+- A D-CPICH is scrambled by the primary scrambling code see [4];
+- There may be zero or two D-CPICH per cell;
+- A D-CPICH shall be transmitted over the entire cell;
+- Carries a pre defined bit sequence same as that of Antenna 1 in Figure 14;
+- A D-CPICH is non precoded and is transmitted from third or fourth transmit antenna;
+- The UE for which the two D-CPICH are activated may assume that the D-CPICHs are present in the HS-DSCH TTIs in which the UE is scheduled to receive HS-PDSCHs.
+
+#### 5.3.3.2 Downlink phase reference
+
+Table 17 specifies the channels which the UE may use as a phase reference for each downlink physical channel type in a cell; it also specifies whether the channels which the UE may use as a phase reference for a channel of a particular
+
+type shall be assumed to be the same as the ones which the UE may use as a phase reference for the associated DPCH or F-DPCH in the same cell, if configured.
+
+For the DPCH or F-DPCH and the associated downlink physical channels the following always applies:
+
+- The UE may use the DPCH pilot bits as a phase reference.
+- In addition, the UE may use either the primary CPICH or a secondary CPICH as a phase reference.
+ - By default (i.e. without any indication by higher layers) the UE may use the primary CPICH as a phase reference.
+ - When a UE is not configured in MIMO mode and not in MIMO mode with four transmit antennas in a cell: The UE is informed by higher layers when it may use a secondary CPICH as a phase reference. In this case the UE shall not use the primary CPICH as a phase reference. Indication that a secondary CPICH may be a phase reference is also applicable when open loop or closed loop TX diversity is enabled for a downlink physical channel in which case Antenna 1 and Antenna 2 secondary CPICH shall be used as phase references.
+ - When the UE is configured in MIMO mode in a cell: The UE is informed by higher layers when it may use a secondary CPICH as a phase reference for a second transmit antenna in addition to the primary CPICH which will be transmitted from the first antenna. In addition, if the UE supports open loop Tx diversity on associated physical channels with the combination of primary CPICH and secondary CPICH, this combination of phase references can also be used as phase references for associated physical channels configured with open loop Tx diversity. If the UE does not support open loop Tx diversity on associated physical channels with the combination of primary CPICH and secondary CPICH and if secondary CPICH is used as a phase reference for second transmit antenna, UE may assume that associated physical channels are not in Tx diversity mode. If no secondary CPICH is signalled as phase reference, the UE may use the Antenna 1 and Antenna 2 primary CPICH as phase references.
+ - When the UE is configured in MIMO mode with four transmit antennas in a cell: The UE is informed by higher layers when it should use any of the secondary CPICH as a phase reference for a second, third or fourth transmit antenna in addition to the primary CPICH which will be transmitted from the first antenna. In addition, if the UE supports open loop Tx diversity on associated physical channels with the combination of primary CPICH and secondary CPICH on second transmit antenna, this combination of phase references can also be used as phase references for associated physical channels configured with open loop Tx diversity. If the UE does not support open loop Tx diversity on associated physical channels with the combination of primary CPICH and secondary CPICH, then the UE may assume that associated physical channels are not in Tx diversity mode.
+
+**Table 17: Phase references for downlink physical channel types in a cell**
+**"X" – Applicable, "-" – Not applicable**
+
+| Physical channel type | DPCH Dedicated pilot (never as the sole phase reference) | Primary -CPICH | Secondary -CPICH | Demodulation-CPICH | Same as associated DPCH or F-DPCH |
+|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|----------------|------------------|--------------------|-----------------------------------|
+| P-CCPCH | - | X | - | - | - |
+| SCH | - | X | - | - | - |
+| S-CCPCH | - | X | - | - | - |
+| DPCH* | X | X | X | - | - |
+| F-DPCH* | - | X | X | - | - |
+| PICH | - | X | - | - | - |
+| MICH | - | X | - | - | - |
+| HS-PDSCH* (UE not in MIMO mode, not in MIMO mode with four transmit antennas and associated DPCH or F-DPCH is configured) | - | - | - | - | X |
+| HS-PDSCH* (UE in MIMO mode) | - | X | X | - | - |
+| HS-PDSCH** (UE in MIMO mode with four transmit antennas) | - | X | X | X | - |
+| HS-PDSCH (if no associated DPCH or F-DPCH is configured) | - | X | - | - | - |
+| HS-SCCH* (if associated DPCH or F-DPCH is configured) | - | - | - | - | X |
+| HS-SCCH (if no associated DPCH or F-DPCH is configured) | - | X | - | - | - |
+| E-AGCH* | - | - | - | - | X |
+| E-RGCH* (if associated DPCH or F-DPCH is configured) | - | - | - | - | X |
+| E-RGCH (if no associated DPCH or F-DPCH is configured) | - | X | - | - | - |
+| E-HICH* | - | - | - | - | X |
+| AICH | - | X | - | - | - |
+| F-TPICH | - | - | - | - | X |
+
+Note \*: A secondary CPICH should not be configured as a phase reference for DPCH or F-DPCH when a UE simultaneously receives S-CCPCHs on different radio links and DPCH or F-DPCH. The UE behavior is undefined if this configuration is used. The support for simultaneous reception of S-CCPCHs on different radio links and DPCH or F-DPCH is optional in the UE.
+
+\*\*: When the UE is configured in MIMO mode with four transmit antennas, Secondary CPICHs on Antennas 2, 3, and 4 and Demodulation CPICHs on Antennas 3 and 4 are used as phase reference.
+
+Dedicated pilot bits are never the sole phase reference for any physical channel, but the UE may always use dedicated pilot bits as a phase reference for DPCH.
+
+Furthermore, during a DPCH or F-DPCH frame overlapping with any part of an associated HS-DSCH or HS-SCCH subframe, the phase reference on this DPCH or F-DPCH shall not change.
+
+#### 5.3.3.3 Primary Common Control Physical Channel (P-CCPCH)
+
+The Primary CCPCH is a fixed rate (30 kbps, SF=256) downlink physical channels used to carry the BCH transport channel.
+
+Figure 15 shows the frame structure of the Primary CCPCH. The frame structure differs from the downlink DPCH in that no TPC commands, no TFCI and no pilot bits are transmitted. The Primary CCPCH is not transmitted during the first 256 chips of each slot. Instead, Primary SCH and Secondary SCH are transmitted during this period (see subclause 5.3.3.5).
+
+
+
+The diagram illustrates the frame structure for the Primary Common Control Physical Channel (P-CCPCH). At the top, a single slot is shown with a duration of $T_{\text{slot}} = 2560$ chips, containing 20 bits. The first 256 chips are designated as '(Tx OFF)', and the remaining 2304 chips are used for 'Data', with $N_{\text{data1}} = 18$ bits. Below this, a '1 radio frame' is shown with a total duration of $T_f = 10$ ms, consisting of 15 slots labeled Slot #0, Slot #1, Slot #i, and Slot #14.
+
+Figure 15: Frame structure for Primary Common Control Physical Channel. The diagram shows a single slot structure at the top and a frame structure at the bottom. The slot structure consists of a 'Tx OFF' period of 256 chips followed by a 'Data' period of N\_data1=18 bits. The total slot duration is T\_slot = 2560 chips, 20 bits. The frame structure shows 15 slots (Slot #0 to Slot #14) over a 10 ms duration (T\_f = 10 ms).
+
+**Figure 15: Frame structure for Primary Common Control Physical Channel**
+
+##### 5.3.3.3.1 Primary CCPCH structure with STTD encoding
+
+In case the diversity antenna is present in UTRAN and the P-CCPCH is to be transmitted using open loop transmit diversity, the data bits of the P-CCPCH are STTD encoded as given in subclause 5.3.1.1.1. The last two data bits in even numbered slots are STTD encoded together with the first two data bits in the following slot, except for slot #14 where the two last data bits are not STTD encoded and instead transmitted with equal power from both the antennas, see figure 16. Higher layers signal whether STTD encoding is used for the P-CCPCH or not. In addition the presence/absence of STTD encoding on P-CCPCH is indicated by modulating the SCH, see 5.3.3.4. During power on and hand over between cells the UE can determine the presence of STTD encoding on the P-CCPCH, by either receiving the higher layer message, by demodulating the SCH channel, or by a combination of the above two schemes.
+
+
+
+Figure 16: STTD encoding for the data bits of the P-CCPCH. The diagram shows three slots: Slot #14, Slot #0, and Slot #1. Each slot contains 'Data on P-CCPCH' represented by a grid of 16 squares. Below Slot #14, an arrow points to the first 8 squares labeled 'STTD encoded' and another arrow points to the last 8 squares labeled 'No STTD encoding'. Below Slot #0, an arrow points to the first 8 squares labeled 'STTD encoded'. Below Slot #1, an arrow points to the first 8 squares labeled 'STTD encoded'.
+
+Figure 16: STTD encoding for the data bits of the P-CCPCH
+
+#### 5.3.3.4 Secondary Common Control Physical Channel (S-CCPCH)
+
+The Secondary CCPCH is used to carry the FACH and PCH. There are two types of Secondary CCPCH: those that include TFCI and those that do not include TFCI. It is the UTRAN that determines if a TFCI should be transmitted, hence making it mandatory for all UEs to support the use of TFCI. The set of possible rates for the Secondary CCPCH is the same as for the downlink DPCH, see subclause 5.3.2. The frame structure of the Secondary CCPCH is shown in figure 17.
+
+
+
+Figure 17: Frame structure for Secondary Common Control Physical Channel. The top part shows a single slot structure with three fields: 'TFCI' (N\_TFCI bits), 'Data' (N\_data1 bits), and 'Pilot' (N\_pilot bits). A double-headed arrow below indicates the total slot duration T\_slot = 2560 chips, 20\*2^k bits (k=0..6). The bottom part shows a radio frame structure with slots labeled Slot #0, Slot #1, Slot #i, and Slot #14. A double-headed arrow below indicates the total frame duration 1 radio frame: T\_f = 10 ms.
+
+Figure 17: Frame structure for Secondary Common Control Physical Channel
+
+The parameter $k$ in figure 17 determines the total number of bits per downlink Secondary CCPCH slot. It is related to the spreading factor $SF$ of the physical channel as $SF = 256/2^k$ . The spreading factor range is from 256 down to 4.
+
+The values for the number of bits per field are given in Table 18. The channel bit and symbol rates given in Table 18 are the rates immediately before spreading. The slot formats applicable to QPSK with pilot bits are not supported in this release. The pilot patterns for the slot formats applicable to QPSK are given in Table 19. DTX shall be used in the pilot field of the 16QAM slot formats, i.e. no pilot bits are used in this release.
+
+The FACH and PCH can be mapped to the same or to separate Secondary CCPCHs. If FACH and PCH are mapped to the same Secondary CCPCH, they can be mapped to the same frame. The main difference between a CCPCH and a downlink dedicated physical channel is that a CCPCH is not inner-loop power controlled. The main difference between the Primary and Secondary CCPCH is that the transport channel mapped to the Primary CCPCH (BCH) can only have a fixed predefined transport format combination, while the Secondary CCPCH support multiple transport format combinations using TFCI.
+
+**Table 18: Secondary CCPCH fields**
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/ Frame | Bits/ Slot | N data1 | N pilot | N TFCI |
+|----------------|-------------------------|----------------------------|-----|-------------|------------|--------------------|--------------------|-------------------|
+| 0 | 30 | 15 | 256 | 300 | 20 | 20 | 0 | 0 |
+| 1 | 30 | 15 | 256 | 300 | 20 | 12 | 8 | 0 |
+| 2 | 30 | 15 | 256 | 300 | 20 | 18 | 0 | 2 |
+| 3 | 30 | 15 | 256 | 300 | 20 | 10 | 8 | 2 |
+| 4 | 60 | 30 | 128 | 600 | 40 | 40 | 0 | 0 |
+| 5 | 60 | 30 | 128 | 600 | 40 | 32 | 8 | 0 |
+| 6 | 60 | 30 | 128 | 600 | 40 | 38 | 0 | 2 |
+| 7 | 60 | 30 | 128 | 600 | 40 | 30 | 8 | 2 |
+| 8 | 120 | 60 | 64 | 1200 | 80 | 72 | 0 | 8* |
+| 9 | 120 | 60 | 64 | 1200 | 80 | 64 | 8 | 8* |
+| 10 | 240 | 120 | 32 | 2400 | 160 | 152 | 0 | 8* |
+| 11 | 240 | 120 | 32 | 2400 | 160 | 144 | 8 | 8* |
+| 12 | 480 | 240 | 16 | 4800 | 320 | 312 | 0 | 8* |
+| 13 | 480 | 240 | 16 | 4800 | 320 | 296 | 16 | 8* |
+| 14 | 960 | 480 | 8 | 9600 | 640 | 632 | 0 | 8* |
+| 15 | 960 | 480 | 8 | 9600 | 640 | 616 | 16 | 8* |
+| 16 | 1920 | 960 | 4 | 19200 | 1280 | 1272 | 0 | 8* |
+| 17 | 1920 | 960 | 4 | 19200 | 1280 | 1256 | 16 | 8* |
+| 18*** | 60 | 15 | 256 | 600 | 40 | 36 | 0 | 4 |
+| 19*** | 120 | 30 | 128 | 1200 | 80 | 76 | 0 | 4 |
+| 20*** | 240 | 60 | 64 | 2400 | 160 | 144 | 0 | 16* |
+| 21*** | 480 | 120 | 32 | 4800 | 320 | 272 | 32** | 16* |
+| 22*** | 960 | 240 | 16 | 9600 | 640 | 560 | 64** | 16* |
+| 23*** | 1920 | 480 | 8 | 19200 | 1280 | 1136 | 128** | 16* |
+
+\* If TFCI bits are not used, then DTX shall be used in TFCI field.
+
+\*\* If pilot bits are not used, then DTX shall be used in pilot field.
+
+\*\*\* Slot formats applicable to 16QAM. See subclause 4.3.5.1.1 in [3] for mapping TFCI bits on 16QAM slot formats.
+
+NOTE 1: The slot formats 18 to 23 in Table 18 are only applicable for MBSFN operations with 16QAM.
+
+NOTE 2: The modulation used in MBSFN operations is signalled by higher layers.
+
+The pilot symbol pattern described in Table 19 is not supported in this release. The shadowed part can be used as frame synchronization words. (The symbol pattern of pilot symbols other than the frame synchronization word shall be "11"). In Table 19, the transmission order is from left to right. (Each two-bit pair represents an I/Q pair of QPSK modulation.)
+
+**Table 19: Pilot Symbol Pattern**
+
+| Symbol # | N pilot = 8 | | | | N pilot = 16 | | | | | | | |
+|----------|------------------------|----|----|----|-------------------------|----|----|----|----|----|----|----|
+| | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| Slot #0 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 10 |
+| 1 | 11 | 00 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 11 | 11 | 00 |
+| 2 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 10 | 11 | 00 |
+| 3 | 11 | 00 | 11 | 00 | 11 | 00 | 11 | 00 | 11 | 01 | 11 | 10 |
+| 4 | 11 | 10 | 11 | 01 | 11 | 10 | 11 | 01 | 11 | 11 | 11 | 11 |
+| 5 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 10 | 11 | 01 | 11 | 01 |
+| 6 | 11 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 10 | 11 | 11 |
+| 7 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 00 |
+| 8 | 11 | 01 | 11 | 10 | 11 | 01 | 11 | 10 | 11 | 00 | 11 | 11 |
+| 9 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 00 | 11 | 11 |
+| 10 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 01 | 11 | 11 | 11 | 10 |
+| 11 | 11 | 10 | 11 | 11 | 11 | 10 | 11 | 11 | 11 | 00 | 11 | 10 |
+| 12 | 11 | 10 | 11 | 00 | 11 | 10 | 11 | 00 | 11 | 01 | 11 | 01 |
+| 13 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 00 |
+| 14 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 11 | 10 | 11 | 01 |
+
+For slot formats using TFCI, the TFCI value in each radio frame corresponds to a certain transport format combination of the FACHs and/or PCHs currently in use. This correspondence is (re-)negotiated at each FACH/PCH addition / removal. The mapping of the TFCI bits onto slots is described in [3].
+
+##### 5.3.3.4.1 Secondary CCPCH structure with STTD encoding
+
+In case the diversity antenna is present in UTRAN and the S-CCPCH is to be transmitted using open loop transmit diversity, the data and TFCI bits of the S-CCPCH are STTD encoded as given in subclause 5.3.1.1.1. The pilot symbol pattern for antenna 2 for the S-CCPCH given in Table 20 is not supported in this release.
+
+**Table 20: Pilot symbol pattern for antenna 2 when STTD encoding is used on the S-CCPCH**
+
+| Symbol # | Npilot = 8 | | | | Npilot = 16 | | | | | | | |
+|----------|------------|----|----|----|-------------|----|----|----|----|----|----|----|
+| | 0 | 1 | 2 | 3 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| Slot #0 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 |
+| 1 | 11 | 00 | 00 | 01 | 11 | 00 | 00 | 01 | 11 | 10 | 00 | 10 |
+| 2 | 11 | 11 | 00 | 00 | 11 | 11 | 00 | 00 | 11 | 10 | 00 | 11 |
+| 3 | 11 | 10 | 00 | 01 | 11 | 10 | 00 | 01 | 11 | 00 | 00 | 00 |
+| 4 | 11 | 11 | 00 | 11 | 11 | 11 | 00 | 11 | 11 | 01 | 00 | 10 |
+| 5 | 11 | 00 | 00 | 10 | 11 | 00 | 00 | 10 | 11 | 11 | 00 | 00 |
+| 6 | 11 | 10 | 00 | 10 | 11 | 10 | 00 | 10 | 11 | 01 | 00 | 11 |
+| 7 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 |
+| 8 | 11 | 00 | 00 | 00 | 11 | 00 | 00 | 00 | 11 | 01 | 00 | 01 |
+| 9 | 11 | 01 | 00 | 10 | 11 | 01 | 00 | 10 | 11 | 01 | 00 | 01 |
+| 10 | 11 | 11 | 00 | 00 | 11 | 11 | 00 | 00 | 11 | 00 | 00 | 10 |
+| 11 | 11 | 01 | 00 | 11 | 11 | 01 | 00 | 11 | 11 | 00 | 00 | 01 |
+| 12 | 11 | 10 | 00 | 11 | 11 | 10 | 00 | 11 | 11 | 11 | 00 | 00 |
+| 13 | 11 | 01 | 00 | 01 | 11 | 01 | 00 | 01 | 11 | 10 | 00 | 01 |
+| 14 | 11 | 01 | 00 | 01 | 11 | 01 | 00 | 01 | 11 | 11 | 00 | 11 |
+
+#### 5.3.3.5 Synchronisation Channel (SCH)
+
+The Synchronisation Channel (SCH) is a downlink signal used for cell search. The SCH consists of two sub channels, the Primary and Secondary SCH. The 10 ms radio frames of the Primary and Secondary SCH are divided into 15 slots, each of length 2560 chips. Figure 18 illustrates the structure of the SCH radio frame.
+
+
+
+Figure 18: Structure of Synchronisation Channel (SCH). The diagram shows a 10 ms SCH radio frame divided into 15 slots (Slot #0 to Slot #14). Each slot contains a Primary SCH (ac\_p) and a Secondary SCH (ac\_s^{i,k}). The Primary SCH is transmitted once every slot. The Secondary SCH is transmitted in parallel with the Primary SCH. The length of each slot is 2560 chips. The length of each sub-channel is 256 chips. The diagram shows the first slot (Slot #0) and the last slot (Slot #14) in detail, with an ellipsis indicating the intermediate slots.
+
+**Figure 18: Structure of Synchronisation Channel (SCH)**
+
+The Primary SCH consists of a modulated code of length 256 chips, the Primary Synchronisation Code (PSC) denoted $c_p$ in figure 18, transmitted once every slot. The PSC is the same for every cell in the system.
+
+The Secondary SCH consists of repeatedly transmitting a length 15 sequence of modulated codes of length 256 chips, the Secondary Synchronisation Codes (SSC), transmitted in parallel with the Primary SCH. The SSC is denoted $c_s^{i,k}$ in figure 18, where $i = 0, 1, \dots, 63$ is the number of the scrambling code group, and $k = 0, 1, \dots, 14$ is the slot number. Each SSC is chosen from a set of 16 different codes of length 256. This sequence on the Secondary SCH indicates which of the code groups the cell's downlink scrambling code belongs to.
+
+The primary and secondary synchronization codes are modulated by the symbol $a$ shown in figure 18, which indicates the presence/absence of STTD encoding on the P-CCPCH and is given by the following table:
+
+| | |
+|--------------------------|----------|
+| P-CCPCH STTD encoded | $a = +1$ |
+| P-CCPCH not STTD encoded | $a = -1$ |
+
+##### 5.3.3.5.1 SCH transmitted by TSTD
+
+Figure 19 illustrates the structure of the SCH transmitted by the TSTD scheme. In even numbered slots both PSC and SSC are transmitted on antenna 1, and in odd numbered slots both PSC and SSC are transmitted on antenna 2.
+
+
+
+Figure 19: Structure of SCH transmitted by TSTD scheme. The diagram shows four slots (Slot #0, Slot #1, Slot #2, Slot #14) and two antennas (Antenna 1 and Antenna 2). In Slot #0, Antenna 1 transmits ac\_p and ac\_s^{i,0}, while Antenna 2 is (Tx OFF). In Slot #1, Antenna 1 is (Tx OFF), and Antenna 2 transmits ac\_p and ac\_s^{i,1}. In Slot #2, Antenna 1 transmits ac\_p and ac\_s^{i,2}, while Antenna 2 is (Tx OFF). In Slot #14, Antenna 1 transmits ac\_p and ac\_s^{i,14}, while Antenna 2 is (Tx OFF). Ellipses between Slot #2 and Slot #14 indicate intermediate slots.
+
+Figure 19: Structure of SCH transmitted by TSTD scheme
+
+#### 5.3.3.6 Void
+
+#### 5.3.3.7 Acquisition Indicator Channel (AICH)
+
+The Acquisition Indicator channel (AICH) is a fixed rate (SF=256) physical channel used to carry Acquisition Indicators (AI) and Extended Acquisition Indicators (EAI). Acquisition Indicator $AI_s$ corresponds to signature $s$ on the PRACH. Extended Acquisition Indicators represent a set of values corresponding to a set of E-DCH resource configurations.
+
+Figure 21 illustrates the structure of the AICH. The AICH consists of a repeated sequence of 15 consecutive *access slots* (AS), each of length 5120 chips. Each access slot consists of two parts, an *Acquisition-Indicator* (AI) part consisting of 32 real-valued signals $a_0, \dots, a_{31}$ and a part of duration 1024 chips with no transmission that is not formally part of the AICH. The part of the slot with no transmission is reserved for possible future use by other physical channels.
+
+The spreading factor (SF) used for channelisation of the AICH is 256.
+
+The phase reference for the AICH is the Primary CPICH.
+
+
+
+The diagram illustrates the structure of the Acquisition Indicator Channel (AICH). At the top, a sequence of real-valued signals is shown, labeled 'AI part = 4096 chips, 32 real-valued signals'. The signals are represented by boxes containing $a_0, a_1, a_2, \dots, a_{30}, a_{31}$ . This is followed by a 'Transmission Off' period. Below this, a sequence of 1024 chips is shown. At the bottom, a sequence of Access Service Class (ASC) identifiers is shown: AS #14, AS #0, AS #1, ..., AS #, ..., AS #14, AS #0. A 20 ms duration is indicated below the ASC identifiers.
+
+Figure 21: Structure of Acquisition Indicator Channel (AICH). The diagram shows a sequence of real-valued signals a\_0, a\_1, a\_2, ..., a\_30, a\_31, followed by a 'Transmission Off' period. The 'AI part' consists of 4096 chips, 32 real-valued signals. The '1024 chips' part is a sequence of 1024 chips. The 'Transmission Off' part is a period of no transmission. Below this, a sequence of Access Service Class (ASC) identifiers is shown: AS #14, AS #0, AS #1, ..., AS #, ..., AS #14, AS #0. A 20 ms duration is indicated below the ASC identifiers.
+
+**Figure 21: Structure of Acquisition Indicator Channel (AICH)**
+
+The real-valued signals $a_0, a_1, \dots, a_{31}$ in figure 21 are given by
+
+$$a_j = \left( \sum_{s=0}^{15} AI_s b_{s,j} \right) + EAI_s c_{s,j}$$
+
+where $AI_s$ , taking the values +1, -1, and 0, is the acquisition indicator corresponding to signature $s$ and the sequence $b_{s,0}, \dots, b_{s,31}$ is given by Table 22, $EAI_s$ , taking the values +1, -1, and 0, is the extended acquisition indicator corresponding to signature $s'$ and the sequence $c_{s',0}, \dots, c_{s',31}$ is given by Table 22B. The $EAI_s$ has the same relative transmit power as the $AI_s$ ; the relative transmit power is indicated by higher layers. If the signature $s$ is not a member of the set of available signatures for all the Access Service Class (ASC) for the corresponding PRACH (cf [5]) then $AI_s$ shall be set to 0.
+
+The use of acquisition indicators is described in [5]. The meaning of acquisition indicators depends on whether a UE sends an access preamble signature corresponding to a PRACH message or corresponding to an E-DCH transmission. Furthermore, if a UE sends an access preamble signature corresponding to an E-DCH transmission, the meaning of the acquisition indicator depends on whether EAI is configured or not. The following rules apply for one PRACH preamble scrambling code. If multiple PRACH preamble scrambling codes are defined in a cell, then for each of them the following rules are used independently.
+
+- If the UE sends an access preamble signature corresponding to a PRACH message, then;
+ - if an Acquisition Indicator is set to +1, it represents a positive acknowledgement,
+ - if an Acquisition Indicator is set to -1, it represents a negative acknowledgement.
+- If the UE sends an access preamble signature corresponding to an E-DCH transmission, then;
+ - if the corresponding Acquisition Indicator is set to +1, it represents a positive acknowledgement and the associated default E-DCH resource configuration is allocated to the UE,
+ - if the corresponding Acquisition Indicator is set to -1 and EAI is not configured, then it represents a negative acknowledgement,
+ - if the corresponding Acquisition Indicator is set to -1 and EAI is configured, then the UE detects which one of the Extended Acquisition Indicator signatures is present.
+
+The association between the AI and the default E-DCH resource index is such that, for 10 ms TTI length:
+
+$$X = \text{SigInd} \bmod Y,$$
+
+The association between the AI and the default E-DCH resource index is such that, for 2 ms TTI length:
+
+$$X = (\text{SigInd} \bmod (Y - \text{Concurrent TTI partition Index})) + \text{Concurrent TTI partition Index},$$
+
+where $X$ is the Default E-DCH resource index, "Concurrent TTI partition Index" is signalled by higher layers or otherwise is set to zero, $Y$ is the total number of E-DCH resources configured in the cell for Enhanced Uplink in CELL\_FACH state and IDLE mode, and $\text{SigInd}$ is the $N$ th PRACH preamble signature corresponding to the AI that is
+
+configured available in the cell and corresponding to E-DCH transmission for Enhanced Uplink in CELL\_FACH state and IDLE mode. PRACH preamble signatures are renumbered as specified in [17] subclause 8.6.6.29.
+
+The use of Extended Acquisition Indicators is described in [5]. If $s'=0$ and an $EAI_0$ is set to +1, it represents a negative acknowledgement. The mapping between the non-zero $EAI_s$ and the E-DCH resource configuration index is presented in Table 22A where X is the index of the default E-DCH resource as defined above and Y is the total number of E-DCH resources configured in the cell.
+
+The real-valued signals, $a_j$ , are spread and modulated in the same fashion as bits when represented in $\{+1, -1\}$ form.
+
+In case STTD-based open-loop transmit diversity is applied to AICH, STTD encoding according to subclause 5.3.1.1.1 is applied to each sequence $b_{s,0}, b_{s,1}, \dots, b_{s,31}$ separately and sequence $c_{s',0}, c_{s',1}, \dots, c_{s',31}$ before the sequences are combined into AICH signals $a_0, \dots, a_{31}$ .
+
+**Table 22: AI signature patterns**
+
+| s | $b_{s,0}, b_{s,1}, \dots, b_{s,31}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----|-------------------------------------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|
+| 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |
+| 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | |
+| 2 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | |
+| 3 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 |
+| 4 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | |
+| 5 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | |
+| 6 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | |
+| 7 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | |
+| 8 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |
+| 9 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | |
+| 10 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 |
+| 11 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | | |
+| 12 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | |
+| 13 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | |
+| 14 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |
+| 15 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 |
+
+**Table 22A: EAI and resource configuration mapping**
+
+| EAI s' | Signature $s'$ | E-DCH Resource configuration index |
+|-------------------|----------------|------------------------------------|
+| +1 | 0 | NACK |
+| -1 | | $(X + 1) \bmod Y$ |
+| +1 | 1 | $(X + 2) \bmod Y$ |
+| -1 | | $(X + 3) \bmod Y$ |
+| +1 | 2 | $(X + 4) \bmod Y$ |
+| -1 | | $(X + 5) \bmod Y$ |
+| +1 | 3 | $(X + 6) \bmod Y$ |
+| -1 | | $(X + 7) \bmod Y$ |
+| +1 | 4 | $(X + 8) \bmod Y$ |
+| -1 | | $(X + 9) \bmod Y$ |
+| +1 | 5 | $(X + 10) \bmod Y$ |
+| -1 | | $(X + 11) \bmod Y$ |
+| +1 | 6 | $(X + 12) \bmod Y$ |
+| -1 | | $(X + 13) \bmod Y$ |
+| +1 | 7 | $(X + 14) \bmod Y$ |
+| -1 | | $(X + 15) \bmod Y$ |
+| +1 | 8 | $(X + 16) \bmod Y$ |
+| -1 | | $(X + 17) \bmod Y$ |
+| +1 | 9 | $(X + 18) \bmod Y$ |
+| -1 | | $(X + 19) \bmod Y$ |
+| +1 | 10 | $(X + 20) \bmod Y$ |
+| -1 | | $(X + 21) \bmod Y$ |
+| +1 | 11 | $(X + 22) \bmod Y$ |
+| -1 | | $(X + 23) \bmod Y$ |
+| +1 | 12 | $(X + 24) \bmod Y$ |
+| -1 | | $(X + 25) \bmod Y$ |
+| +1 | 13 | $(X + 26) \bmod Y$ |
+| -1 | | $(X + 27) \bmod Y$ |
+| +1 | 14 | $(X + 28) \bmod Y$ |
+| -1 | | $(X + 29) \bmod Y$ |
+| +1 | 15 | $(X + 30) \bmod Y$ |
+| -1 | | $(X + 31) \bmod Y$ |
+
+**Table 22B: EAI signature patterns**
+
+| $s'$ | $C_{s',0}, C_{s',1}, \dots, C_{s',31}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------|----------------------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| 0 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 |
+| 2 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 |
+| 3 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 |
+| 4 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 5 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 |
+| 6 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 7 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 |
+| 8 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 9 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 |
+| 10 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 11 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 12 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 13 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 14 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+| 15 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 |
+
+5.3.3.8 Void
+
+5.3.3.9 Void
+
+#### 5.3.3.10 Paging Indicator Channel (PICH)
+
+The Paging Indicator Channel (PICH) is a fixed rate (SF=256) physical channel used to carry the paging indicators. The PICH is associated either with an S-CCPCH to which a PCH transport channel is mapped, or with a HS-SCCH associated with the HS-PDSCH(s) to which a HS-DSCH transport channel carrying paging messages is mapped.
+
+Figure 24 illustrates the frame structure of the PICH. One PICH radio frame of length 10 ms consists of 300 bits ( $b_0, b_1, \dots, b_{299}$ ). Of these, 288 bits ( $b_0, b_1, \dots, b_{287}$ ) are used to carry paging indicators. The remaining 12 bits are not formally part of the PICH and shall not be transmitted (DTX). The part of the frame with no transmission is reserved for possible future use.
+
+
+
+Figure 24: Structure of Paging Indicator Channel (PICH). The diagram shows a 10 ms radio frame containing 300 bits. The first 288 bits (b0 to b287) are used for paging indication. The remaining 12 bits (b288 to b299) are reserved for future use and are not transmitted (DTX). The frame is divided into three segments: the first segment contains bits b0 and b1; the second segment contains bits b287 and b288; and the third segment contains bits b289 to b299. The total duration of the frame is 10 ms.
+
+Figure 24: Structure of Paging Indicator Channel (PICH)
+
+In each PICH frame, $N_p$ paging indicators $\{P_0, \dots, P_{N_p-1}\}$ are transmitted, where $N_p=18, 36, 72, \text{ or } 144$ .
+
+The PI calculated by higher layers for use for a certain UE, is associated to the paging indicator $P_q$ , where $q$ is computed as a function of the PI computed by higher layers, the SFN of the P-CCPCH radio frame during which the start of the PICH radio frame occurs, and the number of paging indicators per frame ( $N_p$ ):
+
+$$q = \left( PI + \left( (18 \times (SFN + \lfloor SFN/8 \rfloor + \lfloor SFN/64 \rfloor + \lfloor SFN/512 \rfloor)) \bmod 144 \right) \times \frac{N_p}{144} \right) \bmod N_p$$
+
+Further, the PI calculated by higher layers is associated with the value of the paging indicator $P_q$ . If a paging indicator in a certain frame is set to "1" it is an indication that UEs associated with this paging indicator and PI should read either the corresponding frame of the associated S-CCPCH, or the corresponding subframes of the associated HS-SCCH
+
+The PI bitmap in the PCH data frames over Iub contains indication values for all higher layer PI values possible. Each bit in the bitmap indicates if the paging indicator associated with that particular PI shall be set to 0 or 1. Hence, the calculation in the formula above is to be performed in Node B to make the association between PI and $P_q$ .
+
+The mapping from $\{P_0, \dots, P_{N_p-1}\}$ to the PICH bits $\{b_0, \dots, b_{287}\}$ are according to Table 24.
+
+Table 24: Mapping of paging indicators $P_q$ to PICH bits
+
+| Number of paging indicators per frame ( $N_p$ ) | $P_q = 1$ | $P_q = 0$ |
+|-------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------|
+| $N_p=18$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{1, 1, \dots, 1\}$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{0, 0, \dots, 0\}$ |
+| $N_p=36$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{1, 1, \dots, 1\}$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{0, 0, \dots, 0\}$ |
+| $N_p=72$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{1, 1, \dots, 1\}$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{0, 0, \dots, 0\}$ |
+| $N_p=144$ | $\{b_{2q}, b_{2q+1}\} = \{1, 1\}$ | $\{b_{2q}, b_{2q+1}\} = \{0, 0\}$ |
+
+When transmit diversity is employed for the PICH, STTD encoding is used on the PICH bits as described in subclause 5.3.1.1.1.
+
+#### 5.3.3.11 Void
+
+#### 5.3.3.12 Shared Control Channel (HS-SCCH)
+
+The HS-SCCH is a fixed rate (60 kbps, SF=128) downlink physical channel used to carry downlink signalling related to HS-DSCH transmission. Figure 26A illustrates the sub-frame structure of the HS-SCCH.
+
+
+
+Figure 26A: Subframe structure for the HS-SCCH. The diagram shows a subframe of duration T\_f = 2 ms, divided into three slots: Slot #0, Slot#1, and Slot #2. Above the slots, a 'Data' block of N\_data1 bits is shown, with a duration T\_slot = 2560 chips, 40 bits indicated for each slot.
+
+Figure 26A: Subframe structure for the HS-SCCH
+
+#### 5.3.3.13 High Speed Physical Downlink Shared Channel (HS-PDSCH)
+
+The High Speed Physical Downlink Shared Channel (HS- PDSCH) is used to carry the High Speed Downlink Shared Channel (HS-DSCH).
+
+A HS-PDSCH corresponds to one channelization code of fixed spreading factor SF=16 from the set of channelization codes reserved for HS-DSCH transmission. Multi-code transmission is allowed, which translates to UE being assigned multiple channelisation codes in the same HS-PDSCH subframe, depending on its UE capability.
+
+The subframe and slot structure of HS-PDSCH are shown in figure 26B.
+
+
+
+Figure 26B: Subframe structure for the HS-PDSCH. The diagram shows a subframe of duration T\_f = 2 ms, divided into three slots: Slot #0, Slot#1, and Slot #2. Above the slots, a 'Data' block of N\_data1 bits is shown, with a duration T\_slot = 2560 chips, M\*10\*2^k bits (k=4) indicated for each slot.
+
+Figure 26B: Subframe structure for the HS-PDSCH
+
+An HS-PDSCH may use QPSK, 16QAM or 64QAM modulation symbols. In figure 26B, M is the number of bits per modulation symbols i.e. M=2 for QPSK, M=4 for 16QAM and M=6 for 64QAM. The slot formats are shown in table 26.
+
+Table 26: HS-DSCH fields
+
+| Slot format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/ HS-DSCH subframe | Bits/ Slot | Ndata |
+|----------------|-------------------------|----------------------------|----|------------------------|------------|-------|
+| 0(QPSK) | 480 | 240 | 16 | 960 | 320 | 320 |
+| 1(16QAM) | 960 | 240 | 16 | 1920 | 640 | 640 |
+| 2(64QAM) | 1440 | 240 | 16 | 2880 | 960 | 960 |
+
+All relevant Layer 1 information is transmitted in the associated HS-SCCH i.e. the HS-PDSCH does not carry any Layer 1 information.
+
+#### 5.3.3.14 E-DCH Absolute Grant Channel (E-AGCH)
+
+An E-DCH Absolute Grant Channel (E-AGCH) is a fixed rate (30 kbps, SF=256) downlink physical channel carrying uplink E-DCH absolute grants for uplink E-DCHs associated with the E-AGCH by higher layer signalling. Figure 26C illustrates the frame and sub-frame structure of the E-AGCH.
+
+An E-DCH absolute grant shall be transmitted over one E-AGCH sub-frame or one E-AGCH frame. The transmission over one E-AGCH sub-frame and over one E-AGCH frame shall be used for UEs for which E-DCH TTI is set to respectively 2 ms and 10 ms.
+
+
+
+Detailed description: The diagram illustrates the E-AGCH structure. At the top, a horizontal block represents "20 bits". Below it, a horizontal double-headed arrow indicates "Tslot = 2560 chips". Further down, a sequence of slots is shown: Slot #0, Slot #1, Slot #2, ..., Slot #i, ..., Slot #14. A double-headed arrow spanning three slots (Slot #0 to Slot #2) is labeled "1 subframe = 2 ms". At the bottom, a long double-headed arrow spanning all 15 slots is labeled "1 radio frame, Tf = 10 ms". Dotted lines connect the 20-bit block to the Tslot arrow, and the Tslot arrow to Slot #i.
+
+Figure 26C: Sub-frame structure for the E-AGCH. The diagram shows a 20-bit data block at the top, which is transmitted over a duration of T\_slot = 2560 chips. Below this, a timeline shows slots labeled Slot #0, Slot #1, Slot #2, Slot #i, and Slot #14. A subframe of 2 ms duration is indicated, covering a portion of the slots. The entire structure is contained within one radio frame of 10 ms duration (T\_f = 10 ms).
+
+**Figure 26C: Sub-frame structure for the E-AGCH**
+
+#### 5.3.3.14B E-DCH Rank and Offset Channel (E-ROCH)
+
+An E-DCH Rank and Offset Channel (E-ROCH) has the same sub-frame structure as the E-AGCH defined in section 5.3.3.14. The transmission shall always take place over one E-ROCH sub-frame. The E-ROCH is only transmitted to a UE for which the E-DCH TTI is set to 2 ms and the UL\_MIMO\_Enabled is set to TRUE.
+
+The E-ROCH and E-AGCH can only be transmitted simultaneously to a UE if they are configured with different channelization codes.
+
+#### 5.3.3.15 MBMS Indicator Channel (MICH)
+
+The MBMS Indicator Channel (MICH) is a fixed rate (SF=256) physical channel used to carry the MBMS notification indicators. The MICH is always associated with an S-CCPCH to which a FACH transport channel is mapped.
+
+Figure 26D illustrates the frame structure of the MICH. One MICH radio frame of length 10 ms consists of 300 bits ( $b_0, b_1, \dots, b_{299}$ ). Of these, 288 bits ( $b_0, b_1, \dots, b_{287}$ ) are used to carry notification indicators. The remaining 12 bits are not formally part of the MICH and shall not be transmitted (DTX).
+
+
+
+Detailed description: The diagram shows the structure of one radio frame (10 ms). It is divided into two main sections. The first section is labeled "288 bits for notification indication" and shows bits $b_0, b_1$ at the beginning and $b_{287}$ at the end. The second section is labeled "12 bits (transmission off)" and shows bits $b_{288}$ and $b_{299}$ . The bits are represented by small vertical rectangles. A dotted line connects the two sections. A double-headed arrow at the bottom spans the entire length and is labeled "One radio frame (10 ms)".
+
+Figure 26D: Structure of MBMS Indicator Channel (MICH). The diagram shows a 300-bit radio frame (10 ms) divided into two parts: 288 bits for notification indication (bits b0 to b287) and 12 bits for transmission off (bits b288 to b299). The bits are shown in a sequence, with b0, b1 at the start and b287, b288, b299 at the end.
+
+**Figure 26D: Structure of MBMS Indicator Channel (MICH)**
+
+In each MICH frame, $N_n$ notification indicators $\{N_0, \dots, N_{N_n-1}\}$ are transmitted, where $N_n=18, 36, 72, \text{ or } 144$ .
+
+The NI calculated by higher layers is associated to the index $q$ of the notification indicator $N_q$ , where $q$ is computed as a function of the NI computed by higher layers, the SFN of the P-CCPCH radio frame during which the start of the MICH radio frame occurs, and the number of notification indicators per frame ( $N_n$ ):
+
+where $G = 2^{16}$ , $C = 25033$ and NI is the 16 bit Notification Indicator calculated by higher layers.
+
+The set of NI signalled over Iub indicates all higher layer NI values for which the associated notification indicator on MICH shall be set to 1 during the corresponding modification period. Hence, the calculation in the formula above shall be performed in the Node B every MICH frame for each NI signalled over Iub to make the association between NI and $q$ and set the related $N_q$ to 1. All other notification indicators on MICH shall be set to 0.
+
+The mapping from $\{N_0, \dots, N_{N_n-1}\}$ to the MICH bits $\{b_0, \dots, b_{287}\}$ are according to table 27.
+
+**Table 27: Mapping of notification indicators $N_q$ to MICH bits**
+
+| Number of notification indicators per frame ( $N_n$ ) | $N_q = 1$ | $N_q = 0$ |
+|-------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------|
+| $N_n=18$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{1, 1, \dots, 1\}$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{0, 0, \dots, 0\}$ |
+| $N_n=36$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{1, 1, \dots, 1\}$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{0, 0, \dots, 0\}$ |
+| $N_n=72$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{1, 1, \dots, 1\}$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{0, 0, \dots, 0\}$ |
+| $N_n=144$ | $\{b_{2q}, b_{2q+1}\} = \{1, 1\}$ | $\{b_{2q}, b_{2q+1}\} = \{0, 0\}$ |
+
+When transmit diversity is employed for the MICH, STTD encoding is used on the MICH bits as described in subclause 5.3.1.1.1.
+
+#### 5.3.3.16 Common E-DCH Relative Grant Channel
+
+The Common E-RGCH is a downlink physical channel for UEs in CELL\_FACH state as described in sub clause 6B.2 of [5]. There is no DPCH or F-DPCH associated with the Common E-RGCH.
+
+The structure, STTD encoding and timing relationship of the Common E-RGCH follow the rules of the dedicated E-RGCH for which the cell transmitting the E-RGCH is not in the E-DCH serving radio link set (sub clause 5.3.2.4 and 7.11).
+
+# 6 Mapping and association of physical channels
+
+## 6.1 Mapping of transport channels onto physical channels
+
+Figure 27 summarises the mapping of transport channels onto physical channels.
+
+
+
+| Transport Channels | Physical Channels |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DCH | Dedicated Physical Data Channel (DPDCH)
Dedicated Physical Control Channel (DPCCH)
Secondary Dedicated Physical Control Channel (S-DPCCH)
Fractional Dedicated Physical Channel (F-DPCH)
Fractional Transmitted Precoding Indicator Channel (F-TPICH) |
+| E-DCH | E-DCH Dedicated Physical Data Channel (E-DPDCH)
E-DCH Dedicated Physical Control Channel (E-DPCCH)
E-DCH Absolute Grant Channel (E-AGCH)
E-DCH Relative Grant Channel (E-RGCH)
E-DCH Hybrid ARQ Indicator Channel (E-HICH)
Secondary E-DCH Dedicated Physical Data Channel (S-E-DPDCH)
Secondary E-DCH Dedicated Physical Control Channel (S-E-DPCCH)
E-DCH Rank and Offset Channel (E-ROCH) |
+| RACH | Physical Random Access Channel (PRACH) |
+| BCH | Common Pilot Channel (CPICH) |
+| FACH | Primary Common Control Physical Channel (P-CCPCH) |
+| PCH | Secondary Common Control Physical Channel (S-CCPCH) |
+| | Synchronisation Channel (SCH)
Acquisition Indicator Channel (AICH)
Paging Indicator Channel (PICH)
MBMS Notification Indicator Channel (MICH) |
+| HS-DSCH | High Speed Physical Downlink Shared Channel (HS-PDSCH)
HS-DSCH-related Shared Control Channel (HS-SCCH)
Dedicated Physical Control Channel (uplink) for HS-DSCH (HS-DPCCH) |
+
+**Figure 27: Transport-channel to physical-channel mapping**
+
+The DCHs are coded and multiplexed as described in [3], and the resulting data stream is mapped sequentially (first-in-first-mapped) directly to the physical channel(s). The mapping of BCH and FACH/PCH is equally straightforward, where the data stream after coding and interleaving is mapped sequentially to the Primary and Secondary CCPCH respectively. Also for the RACH, the coded and interleaved bits are sequentially mapped to the physical channel, in this case the message part of the PRACH. The E-DCH is coded as described in [3], and the resulting data stream is mapped sequentially (first-in-first-mapped) directly to the physical channel(s).
+
+## 6.2 Association of physical channels and physical signals
+
+Figure 28 illustrates the association between physical channels and physical signals.
+
+### Physical Signals
+
+### Physical Channels
+
+PRACH preamble part —— Physical Random Access Channel (PRACH)
+
+Figure 28: Physical channel and physical signal association
+
+# 7 Timing relationship between physical channels
+
+## 7.1 General
+
+The P-CCPCH, on which the cell SFN is transmitted, is used as timing reference for all the physical channels, directly for downlink and indirectly for uplink.
+
+Figure 29 describes the frame timing of some of the downlink physical channels; the timing of the remaining downlink physical channels and of the uplink physical channels is specified in the remaining subclauses. For the AICH the access slot timing is included. Transmission timing for uplink physical channels is given by the received timing of downlink physical channels.
+
+
+
+The diagram illustrates the timing relationship between various downlink physical channels over two 10 ms radio frames. The channels shown are:
+
+- Primary SCH: Represented by a series of vertical pulses.
+- Secondary SCH: Represented by a series of vertical pulses.
+- Any CPICH: A continuous block starting at the frame boundary.
+- P-CCPCH: Divided into "Radio frame with (SFN modulo 2) = 0" and "Radio frame with (SFN modulo 2) = 1".
+- k:th S-CCPCH: Offset from the frame boundary by $\tau_{S-CCPCH,k}$ .
+- PICH for k:th S-CCPCH: Offset from the S-CCPCH by $T_{PICH}$ .
+- AICH access slots: Numbered #0 through #14 across the 20 ms period.
+- n:th DPCH: Offset from the frame boundary by $\tau_{DPCH,n}$ .
+- p:th F-DPCH: Offset from the frame boundary by $\tau_{F-DPCH,p}$ .
+- m:th F-TPICH: Offset from the frame boundary by $\tau_{F-TPICH,m}$ .
+- HS-SCCH Subframes: Divided into Subframe #0, #1, #2, #3, and #4.
+
+The horizontal axis indicates two 10 ms intervals. The P-CCPCH serves as the primary timing reference.
+
+Figure 29: Radio frame timing and access slot timing of downlink physical channels. The diagram shows the timing relationship between various downlink physical channels over two 10 ms radio frames. The channels shown are Primary SCH, Secondary SCH, Any CPICH, P-CCPCH, k:th S-CCPCH, PICH for k:th S-CCPCH, AICH access slots, n:th DPCH, p:th F-DPCH, m:th F-TPICH, and HS-SCCH Subframes. The P-CCPCH is divided into two 10 ms frames based on (SFN modulo 2). The AICH access slots are numbered #0 to #14. The HS-SCCH Subframes are numbered #0 to #4. The timing offsets are indicated by arrows: T\_S-CCPCH,k, T\_PICH, T\_DPCH,n, T\_F-DPCH,p, and T\_F-TPICH,m.
+
+Figure 29: Radio frame timing and access slot timing of downlink physical channels
+
+The following applies:
+
+- SCH (primary and secondary), CPICH (primary and secondary and demodulation CPICHs) and P-CCPCH have identical frame timings.
+- The S-CCPCH timing may be different for different S-CCPCHs, but the offset from the P-CCPCH frame timing is a multiple of 256 chips, i.e. $\tau_{S-CCPCH,k} = T_k \times 256$ chip, $T_k \in \{0, 1, \dots, 149\}$ . For MBMSFN operations using slot formats 21 to 23 in table 18, the offset shall be set in accordance with $\tau_{S-CCPCH,k} = 256 + \lfloor T_k/10 \rfloor \times 2560$ chip.
+- If the PICH is associated to the S-CCPCH, the PICH timing is $\tau_{PICH} = 7680$ chips prior to its corresponding S-CCPCH frame timing, i.e. the timing of the S-CCPCH carrying the PCH transport channel with the corresponding paging information, see also subclause 7.2. If the PICH is associated to the HS-SCCH, the PICH frame timing is the same as the HS-SCCH frame timing.
+- AICH access slots #0 starts the same time as P-CCPCH frames with (SFN modulo 2) = 0. The AICH/PRACH timing is described in subclauses 7.3 and 7.4 respectively.
+- The DPCH timing may be different for different DPCHs, but the offset from the P-CCPCH frame timing is a multiple of 256 chips, i.e. $\tau_{DPCH,n} = T_n \times 256$ chip, $T_n \in \{0, 1, \dots, 149\}$ . The DPCH (DPCCH/DPDCH) timing relation with uplink DPCCH/DPDCHs is described in subclause 7.6.
+- The F-DPCH timing may be different for different F-DPCHs, but the offset from the P-CCPCH frame timing is a multiple of 256 chips, i.e. $\tau_{F-DPCH,p} = T_p \times 256$ chip, $T_p \in \{0, 1, \dots, 149\}$ . All F-DPCHs transmitted to a UE from the same HS-DSCH cell set have the same timing. The F-DPCH timing relation with uplink DPCCH/DPDCHs is described in subclause 7.6.
+- The start of HS-SCCH subframe #0 is aligned with the start of the P-CCPCH frames. The relative timing between a HS-PDSCH and the corresponding HS-SCCH is described in subclause 7.8.
+- The E-HICH, E-RGCH, E-AGCH and E-ROCH downlink timing are respectively specified in subclause 7.10, 7.11, 7.12 and 7.12A. The E-DPCCH and E-DPDCH uplink timing are specified in subclause 7.13.
+- For a secondary serving HS-DSCH cell, the nominal radio frame timing for CPICH and timing reference are the same as the radio frame timing for CPICH and timing reference for the serving HS-DSCH cell.
+- The F-TPICH timing may be different for different F-TPICHs, but the offset from the P-CCPCH frame timing is a multiple of 256 chips, i.e. $\tau_{F-TPICH,m} = T_m \times 256$ chip, $T_m \in \{0, 1, \dots, 149\}$ .
+
+## 7.2 PICH/S-CCPCH timing relation
+
+Figure 30 illustrates the timing between a PICH frame and its associated single S-CCPCH frame, i.e. the S-CCPCH frame that carries the paging information related to the paging indicators in the PICH frame. A paging indicator set in a PICH frame means that the paging message is transmitted on the PCH in the S-CCPCH frame starting $\tau_{PICH}$ chips after the transmitted PICH frame. $\tau_{PICH}$ is defined in subclause 7.1.
+
+
+
+Figure 30: Timing relation between PICH frame and associated S-CCPCH frame. The diagram shows two horizontal bars representing frames. The top bar is labeled 'PICH frame containing paging indicator' and has a dashed right edge. The bottom bar is labeled 'Associated S-CCPCH frame' and has a dashed left edge. A vertical dashed line marks the start of the S-CCPCH frame. A horizontal double-headed arrow labeled tau\_PICH indicates the time offset from the end of the PICH frame to the start of the S-CCPCH frame.
+
+Figure 30: Timing relation between PICH frame and associated S-CCPCH frame
+
+## 7.2A PICH/HS-SCCH timing relation
+
+Figure 30a illustrates the timing between a PICH frame and its set of 5 associated HS-SCCH subframes. The first associated subframe of the associated HS-SCCH starts one HS-SCCH sub-frame after the transmitted PICH frame and is the HS-SCCH subframe number 1 as defined in subclause 7.1. A paging indicator set in a PICH frame means that one or more HS-DSCH subframes may be transmitted to the UE on the HS-PDSCH(s) associated with the HS-SCCH subframes associated with the PICH as defined in [5].
+
+
+
+Figure 30a: Timing relation between PICH frame and associated HS-SCCH subframes. The diagram shows a PICH frame (top) and a series of HS-SCCH subframes (bottom). The PICH frame is divided into two parts: a solid rectangle and a dashed rectangle. The HS-SCCH subframes are shown as a series of six dashed rectangles. A double-headed arrow below the subframes indicates the timing relation between the PICH frame and the subframes.
+
+Figure 30a: Timing relation between PICH frame and associated HS-SCCH subframes
+
+## 7.3 PRACH/AICH timing relation
+
+The downlink AICH is divided into downlink access slots, each access slot is of length 5120 chips. The downlink access slots are time aligned with the P-CCPCH as described in subclause 7.1.
+
+The uplink PRACH is divided into uplink access slots, each access slot is of length 5120 chips. Uplink access slot number $n$ is transmitted from the UE $\tau_{p-a}$ chips prior to the reception of downlink access slot number $n$ , $n = 0, 1, \dots, 14$ .
+
+Transmission of downlink acquisition indicators may only start at the beginning of a downlink access slot. Similarly, transmission of uplink RACH preambles and RACH message parts may only start at the beginning of an uplink access slot.
+
+The PRACH/AICH timing relation is shown in figure 31.
+
+
+
+Figure 31: Timing relation between PRACH and AICH as seen at the UE. The diagram shows two horizontal timelines. The top timeline is labeled 'AICH access slots RX at UE' and shows a series of slots with a bracket labeled 'One access slot'. A box labeled 'Acq. Ind.' is shown in one slot. The bottom timeline is labeled 'PRACH access slots TX at UE' and shows a series of slots. The first slot contains a 'Pre-amble' box. The second slot contains a 'Pre-amble' box. The third slot contains a 'Message part' box. Horizontal double-headed arrows indicate timing intervals: $\tau_{p-p}$ between the start of the first and second preambles, $\tau_{p-m}$ between the start of the second preamble and the message part, and $\tau_{p-a}$ between the start of the second preamble and the 'Acq. Ind.' box.
+
+Figure 31: Timing relation between PRACH and AICH as seen at the UE
+
+The preamble-to-preamble distance $\tau_{p-p}$ shall be larger than or equal to the minimum preamble-to-preamble distance $\tau_{p-p,min}$ , i.e. $\tau_{p-p} \geq \tau_{p-p,min}$ .
+
+In addition to $\tau_{p-p,min}$ , the preamble-to-AI distance $\tau_{p-a}$ and preamble-to-message distance $\tau_{p-m}$ are defined as follows:
+
+- when AICH\_Transmission\_Timing is set to 0, then
+
+$$\tau_{p-p,min} = 15360 \text{ chips (3 access slots)}$$
+
+$$\tau_{p-a} = 7680 \text{ chips}$$
+
+$$\tau_{p-m} = 15360 \text{ chips (3 access slots)}$$
+
+- when AICH\_Transmission\_Timing is set to 1, then
+
+$$\tau_{p-p,min} = 20480 \text{ chips (4 access slots)}$$
+
+$$\tau_{p-a} = 12800 \text{ chips}$$
+
+$$\tau_{p-m} = 20480 \text{ chips (4 access slots)}$$
+
+The parameter AICH\_Transmission\_Timing is signalled by higher layers.
+
+## 7.3A UL/DL timing relation for Enhanced Uplink in CELL\_FACH state and IDLE mode
+
+
+
+Figure 31A: UL/DL timing relation for Enhanced Uplink in CELL\_FACH state and IDLE mode as seen at the UE. The diagram shows two horizontal timelines. The top timeline is labeled 'DL RX at the UE' and shows a sequence of 'One access slot' intervals, followed by an 'Acq. Ind.' (Acquisition Indication) block, and then an 'F-DPCH' (Fast Dedicated Physical Channel) block. The bottom timeline is labeled 'UL TX at the UE' and shows a 'Pre-amble' block, followed by another 'Pre-amble' block, and then a 'DPCCH' (Dedicated Physical Control Channel) block. Timing parameters are indicated by double-headed arrows: t\_p-p (between the start of the first pre-amble and the start of the second pre-amble), t\_p-a (between the start of the second pre-amble and the start of the Acq. Ind.), t\_a-m (between the start of the Acq. Ind. and the start of the F-DPCH), and t\_0 (between the start of the F-DPCH and the start of the DPCCH).
+
+**Figure 31A: UL/DL timing relation for Enhanced Uplink in CELL\_FACH state and IDLE mode as seen at the UE**
+
+The PRACH preamble and Acquisition indication timings $\tau_{p-p}$ and $\tau_{p-a}$ are as defined in section 7.3.
+
+If $C_{offset}$ is not configured by higher layers or the TTI length is 10ms, then
+
+F-DPCH slot format number (according to Table 16C) = 0
+
+$$\tau_{F-DPCH} = [(5120 * \text{AICH access slot \# with the AI}) + 10240 + 256 * S_{offset}] \bmod 38400$$
+
+$$\tau_{a-m} = 10240 + 256 * S_{offset} + \tau_0 \text{ chips, where}$$
+
+$S_{offset}$ = a symbol offset, configured by higher layers, $\{0, \dots, 9\}$ .
+
+$\tau_0$ = 1024 chips defining the DL to UL frame timing difference.
+
+If $C_{offset}$ is configured by higher layers and the TTI length is 2ms, then
+
+F-DPCH slot format number (according to Table 16C) = $(S_{\text{offset}} - C_{\text{offset}}) \bmod 10$
+
+$\tau_{\text{F-DPCH}} = [(5120 * \text{AICH access slot \# with the AI}) + 10240 + 2560 * T_{\text{offset}} + 256 * C_{\text{offset}}] \bmod 38400$
+
+$\tau_{\text{a-m}} = 10240 + 2560 * T_{\text{offset}} + 256 * C_{\text{offset}} + \tau_0$ chips, where
+
+$C_{\text{offset}}$ = a cell-specific symbol offset, configured by higher layers, $\{0, \dots, 29\}$
+
+## 7.4 Void
+
+## 7.5 Void
+
+## 7.6 DPCCH/DPDCH timing relations
+
+### 7.6.1 Uplink
+
+In uplink all the DPCCHs and all the DPDCHs transmitted from one UE have the same frame timing.
+
+### 7.6.2 Downlink
+
+In downlink, the DPCCH and all the DPDCHs carrying CCTrCHs of dedicated type to one UE have the same frame timing.
+
+Note: support of multiple CCTrCHs of dedicated type is not part of the current release.
+
+### 7.6.3 Uplink/downlink timing at UE
+
+At the UE, the uplink DPCCH/DPDCH frame transmission takes place approximately $T_0$ chips after the reception of the first detected path (in time) of the corresponding downlink DPCCH/DPDCH or F-DPCH frame. $T_0$ is a constant defined to be 1024 chips. The first detected path (in time) is defined implicitly by the relevant tests in [14]. More information about the uplink/downlink timing relation and meaning of $T_0$ can be found in [5].
+
+## 7.7 Uplink DPCCH/HS-DPCCH/HS-PDSCH timing at the UE
+
+### 7.7.1 Timing when Multiflow is not configured
+
+Figure 34 shows the timing offset between the uplink DPCH, the HS-PDSCH and the HS-DPCCH at the UE. An HS-DPCCH sub-frame starts $m$ chips after the start of an uplink DPCH frame that corresponds to the DL DPCH or F-DPCH frame from the HS-DSCH serving cell containing the beginning of the related HS-PDSCH subframe with $m$ calculated as
+
+$$m = (T_{\text{TX\_diff}} / 256) + 101$$
+
+where $T_{\text{TX\_diff}}$ is the difference in chips ( $T_{\text{TX\_diff}} = 0, 256, \dots, 38144$ ), between
+
+- the transmit timing of the start of the related HS-PDSCH subframe (see sub-clauses 7.8 and 7.1)
+
+and
+
+- the transmit timing of the start of the downlink DPCH or F-DPCH frame from the HS-DSCH serving cell that contains the beginning of the HS-PDSCH subframe (see sub-clause 7.1).
+
+At any one time, $m$ therefore takes one of a set of five possible values according to the transmission timing of HS-DSCH sub-frame timings relative to the DPCH or F-DPCH frame boundary. The UE and Node B shall only update the set of values of $m$ in connection to UTRAN reconfiguration of downlink timing.
+
+More information about uplink timing adjustments can be found in [5].
+
+
+
+Figure 34: Timing structure at the UE for HS-DPCCH control signalling. The diagram shows three horizontal timelines: Uplink DPCH, HS-PDSCH at UE, and Uplink HS-DPCCH. Uplink DPCH is divided into 13 slots (Slot #0 to Slot #12), with Slot #0 starting at T\_slot 2560 chips. HS-PDSCH at UE starts 3\*T\_slot 7680 chips after Slot #0. Uplink HS-DPCCH starts m\*256 chips after Slot #0 and ends 3\*T\_slot 7680 chips later. A timing offset tau\_UEP approx 19200 chips is shown between the start of HS-PDSCH and the start of Uplink HS-DPCCH.
+
+Figure 34: Timing structure at the UE for HS-DPCCH control signalling
+
+### 7.7.2 Timing when Multiflow is configured
+
+The uplink DPCH, the HS-PDSCH of the time reference cell, and uplink HS-DPCCH follow the same time as defined for the non-Multiflow case in section 7.7.1.
+
+The timing relationship between the non-time reference cell's HS-PDSCH subframe and the related HS-DPCCH subframe is derived from HS-PDSCH frame timing difference $\tau_{DIFF}$ of the two cells, where $-20 \leq \tau_{DIFF} \leq 3860$ chips. The time reference cell for HS-DPCCH is indicated by higher layers.
+
+If $\tau_{DIFF}$ is not within the specified limits:
+
+- HARQ-ACK reporting for the time-reference cell and CQI reporting for both cells are not interrupted.
+- The UE is not required to transmit a valid HARQ-ACK for the non-time reference cell.
+
+If the UE is not configured in MIMO mode in any cell, or it is configured in MIMO mode in at least one cell and the UE indicated not requiring a *Longer HARQ Processing Time* in higher layer capability signalling, then:
+
+Figure 34a shows the timing offset between the uplink DPCH, the HS-PDSCHs and the HS-DPCCH at the UE when the UE is configured with Multiflow. In this case $\tau_{DIFF} = \tau_{non-time\ reference\ cell} - \tau_{time\ reference\ cell}$ .
+
+If the UE is configured in MIMO mode in at least one cell and the UE indicated requiring a *Longer HARQ processing Time* in higher layer capability signalling, then:
+
+Figure 34b shows the timing offset between the uplink DPCH, the HS-PDSCHs and the HS-DPCCH at the UE when the UE is configured with Multiflow. In this case $\tau_{DIFF} = \tau_{time\ reference\ cell} - \tau_{non-time\ reference\ cell}$ .
+
+$\tau_{time\ reference\ cell}$ and $\tau_{non-time\ reference\ cell}$ above refer to the end times of the HS-PDSCH subframes of the time reference cell and the non-time reference cell respectively, with the corresponding HARQ-ACK fields in the same HS-DPCCH sub-frame.
+
+
+
+Figure 34a: Timing structure at the UE for HS-DPCCH control signalling with Multiflow. The diagram shows four horizontal timelines: Uplink DPCH, HS-PDSCH of the time reference cell at the UE, HS-PDSCH of the non-time reference cell at the UE, and Uplink HS-DPCCH. Uplink DPCH is divided into 13 slots (Slot #0 to Slot #12), with Slot #0 starting at 2560 chips. HS-PDSCH of the time reference cell at the UE starts 7680 chips after Slot #0. HS-PDSCH of the non-time reference cell at the UE starts 7680 chips after Slot #0. A timing offset tau\_DIFF is shown between the start of HS-PDSCH of the time reference cell and the start of HS-PDSCH of the non-time reference cell. A timing offset tau\_UEP - tau\_DIFF chips is shown between the start of HS-PDSCH of the time reference cell and the start of Uplink HS-DPCCH. A timing offset tau\_UEP approx 19200 chips is shown between the start of HS-PDSCH of the time reference cell and the start of Uplink HS-DPCCH. The Uplink HS-DPCCH is divided into subframes containing H-ACK and PCI/CQI fields, with a duration of 7680 chips. The start of Uplink HS-DPCCH is m\*256 chips after Slot #0.
+
+Figure 34a: Timing structure at the UE for HS-DPCCH control signalling with Multiflow, when the UE is not configured in MIMO mode, as well as when the UE is configured in MIMO mode in any cell and the UE indicated not requiring a *Longer HARQ processing Time* in higher layers
+
+
+
+Timing diagram for Figure 34b showing the relationship between Uplink DPCH, HS-PDSCH of time reference cell, HS-PDSCH of non-time reference cell, and Uplink HS-DPCCH. The diagram illustrates various timing offsets including 2560 chips per slot, 7680 chips per HS-PDSCH subframe, T\_DIFF, tau\_UEP + T\_DIFF, tau\_UEP approx 19200 chips, and m\*256 chips for the feedback loop ending in H-ACK and PCI/CQI fields in the HS-DPCCH subframe.
+
+Figure 34b: Timing of delayed HARQ-ACK with Multiflow, when the UE is configured in MIMO mode in any cell, and the UE indicated requiring a *Longer HARQ processing Time* in higher layers
+
+$T_{TX\_diff1}$ corresponds to the smallest $T_{TX\_diff}$ value of the time reference cell as configured by higher layers. One $T_{TX\_diff}$ value of the non-time reference cell shall be selected, denoted as $T_{TX\_diff2}$ , where the associated HS-PDSCH subframe of the time reference cell with $T_{TX\_diff1}$ and the associated HS-PDSCH subframe of the non-time reference cell with $T_{TX\_diff2}$ , correspond to the same HARQ-ACK field in the same HS-DPCCH sub-frame. $T_{TX\_diff2}$ is defined as in Table 28.
+
+Table 28: Definition of $T_{TX\_diff2}$ for the non-time reference cell
+
+| Condition: | $T_{TX\_diff2}$ defined as: |
+|------------|-----------------------------|
+| When | |
+| When | |
+
+## 7.8 HS-SCCH/HS-PDSCH timing
+
+Figure 35 shows the relative timing between the HS-SCCH and the associated HS-PDSCH for one HS-PDSCH subframe. The HS-PDSCH starts $\tau_{HS-PDSCH} = 2 \times T_{slot} = 5120$ chips after the start of the HS-SCCH.
+
+
+
+Timing diagram for Figure 35 showing the timing relation between HS-SCCH and HS-PDSCH. The HS-SCCH subframe is 3 \* T\_slot = 7680 chips. The HS-PDSCH subframe is also 3 \* T\_slot = 7680 chips. The HS-PDSCH starts with a delay of tau\_HS-PDSCH (2 \* T\_slot = 5120 chips) relative to the start of the HS-SCCH.
+
+Figure 35: Timing relation between the HS-SCCH and the associated HS-PDSCH.
+
+## 7.9 MICH/S-CCPCH timing relation
+
+Figure 36 illustrates the timing between the MICH frame boundaries and the frame boundaries of the associated S-CCPCH, i.e. the S-CCPCH that carries the MBMS control information related to the notification indicators in the MICH frame. The MICH transmission timing shall be such that the end of radio frame boundary occurs $\tau_{MICH}$ chips before the associated S-CCPCH start of radio frame boundary. $\tau_{MICH}$ is equal to 7680 chips.
+
+The MICH frames during which the Node B shall set specific notification indicators and the S-CCPCH frames during which the Node B shall transmit the corresponding MBMS control data is defined by higher layers.
+
+
+
+Figure 36: Timing relation between MICH frame and associated S-CCPCH frame. The diagram shows two horizontal timelines. The top timeline is labeled 'MICH' and has a double-headed arrow above it labeled 'Radio frame (10 ms)'. The bottom timeline is labeled 'S-CCPCH' and also has a double-headed arrow above it labeled 'Radio frame (10 ms)'. A vertical dashed line marks the end of the MICH radio frame. Another vertical dashed line marks the start of the S-CCPCH radio frame. The time interval between these two dashed lines is labeled with a double-headed arrow and the symbol $\tau_{MICH}$ .
+
+Figure 36: Timing relation between MICH frame and associated S-CCPCH frame
+
+## 7.10 E-HICH/P-CCPCH/DPCH timing relation
+
+The timing of the E-HICH relative to the P-CCPCH is illustrated in figure 37.
+
+When the E-DCH TTI is 10 ms the E-HICH frame offset relative to P-CCPCH shall be $\tau_{E-HICH,n}$ chips with
+
+When the E-DCH TTI is 2 ms the E-HICH frame offset relative to P-CCPCH shall be $\tau_{E-HICH,n}$ chips with
+
+When a downlink F-DPCH is configured, .
+
+
+
+Figure 37: E-HICH timing. The diagram shows a single horizontal timeline with a double-headed arrow below it, indicating a time interval. No specific labels or other details are present in the diagram.
+
+Figure 37: E-HICH timing
+
+## 7.11 E-RGCH/P-CCPCH/DPCH timing relation
+
+The timing of the E-RGCH relative to the P-CCPCH is illustrated in figure 38.
+
+When transmitted to a UE for which the cell transmitting the E-RGCH is in the E-DCH serving radio link set, the E-RGCH frame offset shall be as follows:
+
+- if the E-DCH TTI is 10 ms, the E-RGCH frame offset relative to P-CCPCH shall be $\tau_{E-RGCH,n}$ chips with
+
+- if the E-DCH TTI is 2 ms the E-RGCH frame offset relative to P-CCPCH shall be $\tau_{E-RGCH,n}$ chips with
+
+When a downlink F-DPCH is configured, .
+
+When transmitted to a UE for which the cell transmitting the E-RGCH is not in the E-DCH serving radio link set, the E-RGCH frame offset relative to P-CCPCH shall be $\tau_{E-RGCH} = 5120$ chips.
+
+
+
+The diagram illustrates the timing of E-RGCH relative to P-CCPCH. The P-CCPCH frame is shown as a long bar at the top, with a total duration of 38400 chips indicated by a double-headed arrow above it. Below the P-CCPCH, two E-RGCH frames are shown. The first E-RGCH frame has a duration of 10 ms. A dashed vertical line marks the start of the P-CCPCH frame. A horizontal double-headed arrow between this dashed line and the start of the 10 ms E-RGCH frame is labeled '5120 chips'. A label 'Cell not in serving RLS' is placed next to this arrow. The second E-RGCH frame has a duration of 8 ms. A horizontal double-headed arrow between the start of the P-CCPCH frame and the start of the 8 ms E-RGCH frame is labeled $\tau_{E-RGCH,n}$ . Below the 8 ms E-RGCH frame, a table shows five subframes labeled 'Subframe 0' through 'Subframe 4'. The label 'E-DCH TTI = 10 ms (cell in serving RLS)' is to the left of the 8 ms E-RGCH frame, and 'E-DCH TTI = 2 ms (cell in serving RLS)' is to the left of the subframe table.
+
+Figure 38: E-RGCH timing diagram showing P-CCPCH, E-RGCH (10 ms), and E-RGCH (8 ms) timing relations.
+
+Figure 38: E-RGCH timing
+
+## 7.12 E-AGCH/P-CCPCH timing relation
+
+The E-AGCH frame offset relative to P-CCPCH shall be $\tau_{E-AGCH} = 5120$ chips as illustrated in figure 39.
+
+
+
+The diagram shows the timing relation between P-CCPCH and E-AGCH. The P-CCPCH frame is at the top. Below it, the E-AGCH frame is shown. A dashed vertical line marks the start of the P-CCPCH frame. A horizontal double-headed arrow between this dashed line and the start of the E-AGCH frame indicates an offset. Below the E-AGCH frame, a table shows five subframes, similar to Figure 38.
+
+Figure 39: E-AGCH timing diagram showing the offset between P-CCPCH and E-AGCH frames.
+
+Figure 39: E-AGCH timing
+
+## 7.12A E-ROCH/P-CCPCH timing relation
+
+The E-ROCH frame offset relative to P-CCPCH shall be $\tau_{E-ROCH} = 5120$ chips as illustrated in figure 39A.
+
+
+
+The diagram shows the timing relation between P-CCPCH and E-ROCH. The P-CCPCH frame is at the top. Below it, the E-ROCH frame is shown. A dashed vertical line marks the start of the P-CCPCH frame. A horizontal double-headed arrow between this dashed line and the start of the E-ROCH frame indicates an offset. Below the E-ROCH frame, a table shows five subframes, similar to Figure 38.
+
+Figure 39A: E-ROCH timing diagram showing the offset between P-CCPCH and E-ROCH frames.
+
+Figure 39A: E-ROCH timing
+
+## 7.13 E-DPDCH/E-DPCCH/DPCCH timing relation
+
+The frame timing of all the E-DPCCHs and all the E-DPDCHs transmitted from one UE shall be the same as the uplink DPCCH frame timing.
+
+## 7.14 S-DPCCH/DPCCH timing relation
+
+The frame timing of uplink S-DPCCH transmitted from one UE shall be the same as the uplink DPCCH frame timing.
+
+## 7.15 DPCH/F-DPCH/F-TPICH timing relations in softer handover
+
+When UE is in softer handover and F-TPICH is transmitted from multiple radio links as defined in [5], the F-TPICH radio frame starts 512 chips after the start of the DPCH/F-DPCH radio frame that corresponds to the same radio link.
+
+## 7.16 S-E-DPDCH/S-E-DPCCH/DPCCH timing relation
+
+The frame timing of the S-E-DPCCH and all the S-E-DPDCHs transmitted from one UE shall be the same as the uplink DPCCH frame timing.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| | RAN_05 | RP-99587 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 |
+| 14/01/00 | RAN_06 | RP-99676 | 001 | 1 | Removal of superframe notation | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99677 | 002 | - | Use of CPICH in case of open loop Tx | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99677 | 003 | 2 | CPCH power control preamble length | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99684 | 005 | 1 | Editorial corrections | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99676 | 006 | - | Change to the description of TSTD for SCH | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99678 | 007 | 1 | Introduction of compressed mode by higher layer scheduling | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99676 | 008 | 1 | Modifications to STTD text | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99684 | 009 | 1 | 20 ms RACH message length | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99676 | 010 | - | Update to AICH description | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99678 | 011 | 1 | Sliding paging indicators | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99677 | 016 | - | TAB structure and timing relation for USTS | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99677 | 017 | - | Timing for initialisation procedures | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99677 | 022 | - | Modification of the STTD encoding scheme on DL DPCH with SF 512 | 3.0.0 | 3.1.0 |
+| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 |
+| 31/03/00 | RAN_07 | RP-000060 | 013 | 6 | Addition of a downlink channel indicating CPCH status | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 023 | 6 | CPCH-related editorial changes, technical changes and additions to 25.211 and some clarifications to 7.4 PCPCH/AICH timing relation. | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 024 | 1 | Additional description of TX diversity for PDSCH | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 025 | 1 | Consistent numbering of scrambling code groups | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 026 | - | Minor corrections to timing section | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 028 | 1 | Timing of PDSCH | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 029 | 1 | Modifications to STTD text | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 031 | 4 | CD/CA-ICH for dual mode CPCH | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 033 | - | Clarification of frame synchronization word and its usage | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 034 | 1 | Editorial updates to 25.211 | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 036 | - | PDSCH multi-code transmission | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 037 | - | Clarification of pilot bit patterns for CPCH and slot formats for CPCH PC-P and message part | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 039 | - | Further restrictions on the application of the Tx diversity modes in DL | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 040 | - | Clarification of downlink pilot bit patterns | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 041 | - | Clarification of DCH initialisation | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 044 | 2 | Emergency Stop of CPCH transmission and Start of Message Indicator | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000060 | 046 | - | Clean up of USTS related specifications | 3.1.1 | 3.2.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 047 | 4 | Clarifications to power control preamble sections | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 048 | - | Propagation delay for PCPCH | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 049 | 1 | PICH undefined bits and AICH, AP-ICH, CD/CA-ICH non-transmitted chips | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 051 | 1 | Bit value notation change for PICH and CSICH | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 053 | 1 | Revision of notes in sections 5.3.2 and 5.3.2.1 | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 054 | 5 | Slot format clarification for CPCH | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 055 | 3 | Physical channel nomenclature in FDD | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 056 | 3 | Clarification for the PDSCH channelisation code association with DPCH in 25.211 | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 057 | 2 | Clarification for the PDSCH channelisation code association with DPCH in 25.211 | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 058 | - | Clarification of spreading factor for AICH | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000265 | 060 | - | Explicit mention of slot format reconfiguration also for uplink | 3.2.0 | 3.3.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 065 | - | Correction of reference | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 066 | 4 | Clarification of paging indicator mapping | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 068 | - | Editorial modification of the 25.211 about the CD/CA-ICH | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 070 | 1 | Support of closed loop transmit diversity modes | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 071 | - | DPCH initialisation procedure | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 072 | 3 | Correction on indicators | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 074 | - | Correction of STTD for DPCH | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 075 | - | Clarification of first significant path | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 076 | - | Clarification of SCH transmitted by TSTD | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000340 | 077 | 1 | Clarification of FBI field | 3.3.0 | 3.4.0 |
+| 15/12/00 | RAN_10 | RP-000537 | 079 | 2 | Clarification of downlink phase reference | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000537 | 083 | 1 | DL Transmission in the case of invalid data frames | 3.4.0 | 3.5.0 |
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|-----|-----|------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 15/12/00 | RAN_10 | RP-000537 | 084 | - | Clarification of figure 28 | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000537 | 087 | - | RACH message part length | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000537 | 088 | - | Clarifications on power control preambles | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000537 | 089 | 1 | Proposed CR to 25.211 for transfer of CSICH Information from Layer 3 Specification | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000537 | 090 | - | PCPCH/DL-DPCCH Timing Relationship | 3.4.0 | 3.5.0 |
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|-----|-----|-----------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010058 | 091 | - | DSCH reading indication | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010058 | 092 | 1 | Clarification of the S-CCPCH frame carrying paging information | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010255 | 095 | 3 | Phase Reference for Secondary CCPCH carrying FACH | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010058 | 096 | - | Uplink power control preamble | 3.5.0 | 4.0.0 |
+| 15/06/01 | RAN_12 | RP-010331 | 098 | - | Downlink Phase Reference for DL-DPCCH for CPCH | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010331 | 100 | - | Removal of out-of-date reference to FACH beamforming | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010331 | 102 | - | Correction of compressed mode by puncturing | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010331 | 104 | - | Correction of the representation of slot format | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010331 | 106 | 1 | Clarification of PDSCH definition | 4.0.0 | 4.1.0 |
+| 21/09/01 | RAN_13 | RP-010518 | 111 | 2 | Correction to DPCH/PDSCH timing | 4.1.0 | 4.2.0 |
+| 21/09/01 | RAN_13 | RP-010518 | 121 | 1 | Clarification of the usage of Tx diversity modes in Soft HOV | 4.1.0 | 4.2.0 |
+| 21/09/01 | RAN_13 | RP-010709 | 114 | 2 | Removal of another reference to FACH beamforming | 4.1.0 | 4.2.0 |
+| 21/09/01 | RAN_13 | RP-010518 | 118 | 1 | Clarification of STTD | 4.1.0 | 4.2.0 |
+| 14/12/01 | RAN_14 | RP-010904 | 116 | 2 | Clarification of the pilot bits on CPCH message part and S-CCPCH | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010736 | 123 | - | Addition of pilot bit patterns table of downlink DPCCH for antenna 2 using closed loop mode 1 | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010736 | 125 | - | Slot format for the CPCH | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010736 | 127 | 1 | Clarification of Tx diversity with PDSCH, AP-AICH, CD/CA-ICH and DL-DPCCH associated to CPCH | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010736 | 129 | 1 | Interaction between DSCH scheduling and phase reference modification | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010736 | 131 | - | Support of multiple CCTrChs of dedicated type | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010736 | 133 | - | Removal of slow power control from TS 25.211 | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010932 | 135 | - | Restriction to simultaneous use of SSDT and closed loop mode TX diversity | 4.2.0 | 4.3.0 |
+| 08/03/02 | RAN_15 | RP-020046 | 139 | 1 | Clarification of different diversity modes used in the same active set | 4.3.0 | 4.4.0 |
+| 08/03/02 | RAN_15 | RP-020058 | 146 | - | Specification of HS-DSCH for Release 5 in 25.211 | 4.3.0 | 5.0.0 |
+| 07/06/02 | RAN_16 | RP-020307 | 149 | 1 | SCCPCH structure with STTD encoding | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020307 | 153 | - | Downlink bit mapping | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020437 | 147 | 4 | Specification of TX diversity for HSDPA | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020316 | 150 | 1 | Adding section on HS-SCCH/HS-PDSCH timing relation | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020316 | 155 | - | HSDPA subframe definition | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020316 | 157 | 1 | Clarification for uplink HS-DPCCH/HS-PDSCH timing | 5.0.0 | 5.1.0 |
+| 14/09/02 | RAN_17 | RP-020591 | 161 | 1 | Phase reference for HSDPA | 5.1.0 | 5.2.0 |
+| 14/09/02 | RAN_17 | RP-020571 | 164 | - | Reversal of unwanted corrections resulting from CR 25.211-122 | 5.1.0 | 5.2.0 |
+| 14/09/02 | RAN_17 | RP-020581 | 168 | 1 | Numbering corrections | 5.1.0 | 5.2.0 |
+| 14/09/02 | RAN_17 | RP-020590 | 169 | - | TX diversity on radio links in the active set | 5.1.0 | 5.2.0 |
+| 14/09/02 | RAN_17 | RP-020588 | 170 | 1 | HS-DPCCH timing correction | 5.1.0 | 5.2.0 |
+| 14/09/02 | RAN_17 | RP-020587 | 171 | - | Inclusion of closed loop transmit diversity for HSDPA | 5.1.0 | 5.2.0 |
+| 14/09/02 | RAN_17 | RP-020581 | 172 | - | Physical channel mapping | 5.1.0 | 5.2.0 |
+| 20/12/02 | RAN_18 | RP-020845 | 173 | - | Correction of the number of transport channels in clause 4.1 | 5.2.0 | 5.3.0 |
+| 20/12/02 | RAN_18 | RP-020845 | 175 | - | HSDPA Tx diversity of closed loop transmit diversity mode 2 use with HS-PDSCH/HS-SCCH | 5.2.0 | 5.3.0 |
+| 21/06/03 | RAN_20 | RP-030271 | 178 | - | Alignment of the terminology, "subframe" | 5.3.0 | 5.4.0 |
+| 21/06/03 | RAN_20 | RP-030271 | 179 | - | Correction of AICH description | 5.3.0 | 5.4.0 |
+| 21/06/03 | RAN_20 | RP-030271 | 180 | - | Correction of description of TTX_diff | 5.3.0 | 5.4.0 |
+| 21/09/03 | RAN_21 | RP-030462 | 186 | 1 | Removal of the combination of TxAA Mode 1 with HS-SCCH | 5.4.0 | 5.5.0 |
+| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.5.0 | 6.0.0 |
+| 09/06/04 | RAN_24 | RP-040231 | 189 | 1 | Re-Introduction of S-CPICH in combination with Closed Loop TxDiversity | 6.0.0 | 6.1.0 |
+| 09/06/04 | RAN_24 | RP-040231 | 190 | - | Clarification of NTFCI field of DL-DPCCH power preamble for CPCH | 6.0.0 | 6.1.0 |
+| 07/09/04 | RAN_25 | RP-040317 | 192 | - | Correction for the slot range of DL DPCCH power control preamble for CPCH | 6.1.0 | 6.2.0 |
+| 13/12/04 | RAN_26 | RP-040449 | 195 | 1 | Introduction of E-DCH | 6.2.0 | 6.3.0 |
+| 13/12/04 | RAN_26 | RP-040450 | 193 | 1 | Introduction of MICH | 6.2.0 | 6.3.0 |
+| 14/03/05 | RAN_27 | RP-050043 | 197 | 1 | E-HICH/E-RGCH Signature Sequences | 6.3.0 | 6.4.0 |
+| 14/03/05 | RAN_27 | RP-050043 | 198 | 1 | E-HICH/E-RGCH Signature Sequence Hopping | 6.3.0 | 6.4.0 |
+| 14/03/05 | RAN_27 | RP-050090 | 202 | 2 | E-HICH/E-RGCH/E-AGCH timing | 6.3.0 | 6.4.0 |
+| 14/03/05 | RAN_27 | RP-050088 | 200 | 1 | Introduction of F-DPCH without pilot field | 6.3.0 | 6.4.0 |
+| 16/06/05 | RAN_28 | RP-050357 | 203 | 2 | Correction of text on E-RGCH duration | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050250 | 205 | 1 | Feature Clean Up: Removal of "CPCH" | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050248 | 207 | - | Feature Clean Up: Removal of DSCH (FDD mode) | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050252 | 210 | 1 | Clarification on E-AGCH transmission interval | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050256 | 211 | 2 | Clarification on phase reference for downlink channels | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050252 | 212 | 1 | Clarification on E-DCH timing | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050244 | 214 | - | Feature Clean Up: Removal of "SSDT" | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050247 | 217 | - | Feature clean up: Removal of the 'TX diversity closed loop mode 2' | 6.4.0 | 6.5.0 |
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 16/06/05 | RAN_28 | RP-050249 | 219 | - | Feature clean up: Removal of the 'compressed mode by puncturing' | 6.4.0 | 6.5.0 |
+| 16/06/05 | RAN_28 | RP-050246 | 221 | - | Feature Clean Up: Removal of dedicated pilot as sole phase reference | 6.4.0 | 6.5.0 |
+| 26/09/05 | RAN_29 | RP-050450 | 0222 | - | SF max for E-DPDCH | 6.5.0 | 6.6.0 |
+| 26/09/05 | RAN_29 | RP-050450 | 0223 | 1 | DPCCH, E-DPCCH, E-DPDCH combinations | 6.5.0 | 6.6.0 |
+| 26/09/05 | RAN_29 | RP-050543 | 0244 | - | Correcting the accidental removal of F-DPCH, MICH, E-AGCH, E-RGCH and E-HICH from Tx Diversity applicability table | 6.5.0 | 6.6.0 |
+| 12/12/05 | RAN_30 | RP-050726 | 0224 | - | Clean up due to removal of N TPC =1 | 6.6.0 | 6.7.0 |
+| 12/12/05 | RAN_30 | RP-050727 | 0225 | 2 | Combination of DPCCH and E-DCH | 6.6.0 | 6.7.0 |
+| 12/12/05 | RAN_30 | RP-050725 | 0227 | - | Clean up due to removal of CSICH | 6.6.0 | 6.7.0 |
+| 20/03/06 | RAN_31 | - | - | - | Creation of Release 7 specification (v7.0.0) at RAN#31 | 6.7.0 | 7.0.0 |
+| 07/03/07 | RAN_35 | RP-070114 | 0238 | - | Transmit diversity operation in MIMO mode | 7.0.0 | 7.1.0 |
+| 07/03/07 | RAN_35 | RP-070115 | 0230 | 2 | Support of CPC feature | 7.0.0 | 7.1.0 |
+| 07/03/07 | RAN_35 | RP-070115 | 0231 | - | Support of CPC feature: addition of subframe numbering | 7.0.0 | 7.1.0 |
+| 07/03/07 | RAN_35 | RP-070116 | 0234 | 2 | Introduction of 64QAM for HSDPA | 7.0.0 | 7.1.0 |
+| 30/05/07 | RAN_36 | RP-070388 | 0235 | 2 | Introduction of 16QAM for HSUPA | 7.1.0 | 7.2.0 |
+| 30/05/07 | RAN_36 | RP-070384 | 0237 | 3 | Support for DL only SFN operation for MBMS FDD | 7.1.0 | 7.2.0 |
+| 30/05/07 | RAN_36 | RP-070390 | 0239 | 3 | Introduction of PICH to HS-SCCH timing relation and Tx diversity definition for HS-DSCH without associated DL dedicated channel | 7.1.0 | 7.2.0 |
+| 30/05/07 | RAN_36 | RP-070387 | 0240 | - | Definition of abbreviation "MIMO" | 7.1.0 | 7.2.0 |
+| 30/05/07 | RAN_36 | RP-070389 | 0241 | - | Clarification for CPC feature | 7.1.0 | 7.2.0 |
+| 11/09/07 | RAN_37 | RP-070639 | 0246 | 1 | Clarification on MICH | 7.2.0 | 7.3.0 |
+| 11/09/07 | RAN_37 | RP-070649 | 0232 | 3 | Enhanced F-DPCH | 7.2.0 | 7.3.0 |
+| 11/09/07 | RAN_37 | RP-070643 | 0242 | 1 | PICH associated HS-SCCH for Enhanced CELL_FACH | 7.2.0 | 7.3.0 |
+| 11/09/07 | RAN_37 | RP-070641 | 0243 | - | Clarification for CPC feature | 7.2.0 | 7.3.0 |
+| 11/09/07 | RAN_37 | RP-070646 | 0245 | - | Clarifications on the use of S-CCPCH pilot bits for MBSFN FDD feature | 7.2.0 | 7.3.0 |
+| 27/11/07 | RAN_38 | RP-070940 | 0250 | - | Correction to E-DPCCH transmission | 7.3.0 | 7.4.0 |
+| 27/11/07 | RAN_38 | RP-070941 | 0248 | - | Correction to transmit diversity specification in MIMO mode | 7.3.0 | 7.4.0 |
+| 27/11/07 | RAN_38 | RP-070941 | 0251 | 1 | Mention PCI as part of HS-DPCCH structure | 7.3.0 | 7.4.0 |
+| 04/03/08 | RAN_39 | RP-080142 | 0252 | - | Correction to tie use of transmit diversity on SCH and P-CCPCH | 7.4.0 | 7.5.0 |
+| 04/03/08 | RAN_39 | - | - | - | Release 8 version created further to RAN_39 decision | 7.5.0 | 8.0.0 |
+| 28/05/08 | RAN_40 | RP-080351 | 0255 | 1 | Correction to E-DCH control channel timing | 8.0.0 | 8.1.0 |
+| 10/09/08 | RAN_41 | RP-080672 | 0256 | 2 | Introduction of the Enhanced Uplink for CELL_FACH state | 8.1.0 | 8.2.0 |
+| 03/12/08 | RAN_42 | RP-080989 | 257 | 3 | Introduction of Dual-Cell HSDPA Operation on Adjacent Carriers | 8.2.0 | 8.3.0 |
+| 03/12/08 | RAN_42 | RP-080986 | 259 | 1 | Removal of a reference to E-AICH | 8.2.0 | 8.3.0 |
+| 03/03/09 | RAN_43 | RP-090229 | 261 | 1 | Clarifications to the S-CPICH usage with MIMO | 8.3.0 | 8.4.0 |
+| 03/03/09 | RAN_43 | RP-090227 | 263 | 1 | Clarification of ACK transmission in response to HS-SCCH order | 8.3.0 | 8.4.0 |
+| 15/09/09 | RAN_45 | RP-090890 | 268 | - | Clarification on STTD encoding description for AICH | 8.4.0 | 8.5.0 |
+| 15/09/09 | RAN_45 | RP-090883 | 270 | 2 | Clarification of the applicability of Transmit Diversity | 8.4.0 | 8.5.0 |
+| 15/09/09 | RAN_45 | RP-090884 | 273 | - | Clarification of associated channel for HS-DSCH | 8.4.0 | 8.5.0 |
+| 18/09/09 | RAN_45 | - | - | - | Release 9 version created further to RAN_45 decision | 8.5.0 | 9.0.0 |
+| 01/12/09 | RAN_46 | RP-091170 | 274 | 2 | Introduction of DC-HSUPA | 9.0.0 | 9.1.0 |
+| 01/12/09 | RAN_46 | RP-091171 | 278 | 2 | Clarification of Tx diversity mode and phase reference for DC-HSDPA and MIMO operation | 9.0.0 | 9.1.0 |
+| 01/12/09 | RAN_46 | RP-091160 | 281 | - | Clarification to MIMO phase references | 9.0.0 | 9.1.0 |
+| 14/09/10 | RAN_49 | RP-100892 | 287 | 1 | Clarification of PICH/HS-SCCH timing relation | 9.1.0 | 9.2.0 |
+| 16/09/10 | RAN_49 | RP-100902 | 284 | 2 | Release 10 created with the introduction of 4C-HSDPA | 9.2.0 | 10.0.0 |
+| 05/12/11 | RAN_54 | RP-111671 | 288 | 5 | Introduction of 8C-HSDPA | 10.0.0 | 11.0.0 |
+| 05/12/11 | RAN_54 | RP-111672 | 289 | - | Introduction of Uplink Closed Loop Transmit Diversity for HSPA | 10.0.0 | 11.0.0 |
+| 04/09/12 | RAN_57 | RP-121271 | 295 | 2 | Introduction of Multiflow | 11.0.0 | 11.1.0 |
+| 04/09/12 | RAN_57 | RP-121270 | 298 | 1 | Introduction of Further Enhancements to CELL_FACH | 11.0.0 | 11.1.0 |
+| 04/09/12 | RAN_57 | RP-121384 | 299 | - | Correction of F-TPICH transmission | 11.0.0 | 11.1.0 |
+| 04/12/12 | RAN_58 | RP-121845 | 296 | 5 | Introduction of uplink MIMO and 64QAM | 11.1.0 | 11.2.0 |
+| 04/12/12 | RAN_58 | RP-121843 | 297 | 6 | Introduction of 4Tx_HSDPA in 25.211 | 11.1.0 | 11.2.0 |
+| 04/12/12 | RAN_58 | RP-121838 | 305 | 1 | Removal of the relative amplitude weighting factor between EAI and AI | 11.1.0 | 11.2.0 |
+| 04/12/12 | RAN_58 | RP-121844 | 306 | 1 | Clarifications and corrections to HSDPA Multiflow | 11.1.0 | 11.2.0 |
+| 04/12/12 | RAN_58 | RP-121842 | 307 | 1 | Clarification of TTI Alignment | 11.1.0 | 11.2.0 |
+| 04/12/12 | RAN_58 | RP-121842 | 308 | - | Correction to common E-RGCH | 11.1.0 | 11.2.0 |
+| 26/02/13 | RAN_59 | RP-130251 | 310 | 1 | UE behaviour when non-time reference cell is out of time window | 11.2.0 | 11.3.0 |
+| 11/06/13 | RAN_60 | RP-130745 | 312 | 3 | Correction to the Four Branch MIMO Transmit Diversity | 11.3.0 | 11.4.0 |
+| 11/06/13 | RAN_60 | RP-130746 | 313 | 1 | Signature and default common E-DCH resource mapping | 11.3.0 | 11.4.0 |
+| 10/06/14 | RAN_64 | RP-140860 | 317 | - | Correction of DRX operation for Multiflow | 11.4.0 | 11.5.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25221/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/25_series/25221/00504fc688ebcf131ccbeff94dfc9939_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..100319cbba1379f51520ebb9c081f824d12578ea
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/00504fc688ebcf131ccbeff94dfc9939_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4286e9652d8f2b873a7677bdab48cdea12597cd3a0d749beb2ee7f5fd0d07d30
+size 41609
diff --git a/marked/Rel-11/25_series/25221/014daefdecf9d847ca82cb5b9f50731f_img.jpg b/marked/Rel-11/25_series/25221/014daefdecf9d847ca82cb5b9f50731f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..473aa1b0c034493dd0a7eb6ed6d6d70d355cfb46
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/014daefdecf9d847ca82cb5b9f50731f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69be571f63f4872e61a05eb378c58c02c1185bdc82bbe788fe876cf1195dbfaf
+size 41209
diff --git a/marked/Rel-11/25_series/25221/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-11/25_series/25221/077f85b82901283b4657fd2b45fc0294_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6ad5148ede3eaaa3e053d859ff554468d65fa9a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/077f85b82901283b4657fd2b45fc0294_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1938891d171001d69a52124afc7973b5617a371c6f5e9274014b27b80f575adf
+size 2812
diff --git a/marked/Rel-11/25_series/25221/09084c793f44a50d7a1558dbb45d317d_img.jpg b/marked/Rel-11/25_series/25221/09084c793f44a50d7a1558dbb45d317d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10b93516d77166086b97a6aabcb9173ba8fbf7bb
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/09084c793f44a50d7a1558dbb45d317d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10dca62e04e3e9165f3fd6527184725d723dc3640ebf492f6af6f7016aa16f5f
+size 33967
diff --git a/marked/Rel-11/25_series/25221/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/Rel-11/25_series/25221/098802c99831a6a7d445310d5e874e16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..756c2a9db387b6fb44cdc3a792e051537540e62a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/098802c99831a6a7d445310d5e874e16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61615d590930d057d70d91d71c2422867e6c81a13d60d47f45da1086d2b1efd6
+size 19781
diff --git a/marked/Rel-11/25_series/25221/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-11/25_series/25221/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20eb84417bf23fb0929ff85ddefa32740130e4a9
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a14103ecd9a9ce795778038ac37f9b623446c8c828fbbbe87e72b86282a0909
+size 27355
diff --git a/marked/Rel-11/25_series/25221/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/25_series/25221/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71fe0e11b6990ab1481d9aa853d88a32c9e4545a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4a5f8f562915d4b7685096abbfd93b41d6f8bc6f613f496c75676d62b8c9152
+size 39998
diff --git a/marked/Rel-11/25_series/25221/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-11/25_series/25221/0b998e3ad8f9d104768642612605cb35_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3989dfaf4e07504ba816201a0c855c9ed62c3be5
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/0b998e3ad8f9d104768642612605cb35_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a9083cafde58c4fb56dbe115dabc36973ecaf627a26c8131a8b20bb465fa245
+size 41411
diff --git a/marked/Rel-11/25_series/25221/0bbbad069459da54c1cdef84c90b316a_img.jpg b/marked/Rel-11/25_series/25221/0bbbad069459da54c1cdef84c90b316a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c27c7c13106449432f5dc5547aa8b800fc42f09a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/0bbbad069459da54c1cdef84c90b316a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65fef7389f4bb3f259498543e2acd8c230d63fbb5b96bc66c7c6b1517d742722
+size 40585
diff --git a/marked/Rel-11/25_series/25221/0d475a233dd118d11e7c7958dce3c1c2_img.jpg b/marked/Rel-11/25_series/25221/0d475a233dd118d11e7c7958dce3c1c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7aef81aaf997a7843479f0bb49a7560481594a9
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/0d475a233dd118d11e7c7958dce3c1c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e15fbe2c5b202803237941f1bf125c81d0af3cc08fa62ea5c64339cc2da5506
+size 21409
diff --git a/marked/Rel-11/25_series/25221/1043999278be2d0d419a47a907d4db77_img.jpg b/marked/Rel-11/25_series/25221/1043999278be2d0d419a47a907d4db77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4b33aaac7167bfeeb6fc6ef4dc87907f9d198fc
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1043999278be2d0d419a47a907d4db77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7dcbd019ad456de8b8503bb6f7344aea371bd36f36bae66d7dc82af2af0b9a5
+size 11998
diff --git a/marked/Rel-11/25_series/25221/10b0dda884baae493ad958422d11b552_img.jpg b/marked/Rel-11/25_series/25221/10b0dda884baae493ad958422d11b552_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df971f9f40d95435e14362a8fb971c8d2f90d4c6
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/10b0dda884baae493ad958422d11b552_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c23fb3dbbbf61729c176e2ae07ce95eff2713df71f8b9f10c920b268a8d9f9d
+size 20256
diff --git a/marked/Rel-11/25_series/25221/1187dbd674a100960ed23efa54ccd6c1_img.jpg b/marked/Rel-11/25_series/25221/1187dbd674a100960ed23efa54ccd6c1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c44fbd335b3d0bdbf9921deb2bdd869f65a1aeb
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1187dbd674a100960ed23efa54ccd6c1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:518a5b3d428ddf742676e3053f438bddf4d2592d82c38240d2f93e7fa55a7fc7
+size 41711
diff --git a/marked/Rel-11/25_series/25221/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-11/25_series/25221/16152cf1d84aea10848758f51a91ff6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a970181c1635266a4b1987f352445e529dec6d37
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/16152cf1d84aea10848758f51a91ff6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ecff161fc029caef22f37c27b16aa7d62a08cf869cc91302c38419195162e938
+size 28733
diff --git a/marked/Rel-11/25_series/25221/165508b2526a29efbae96fa16d525d28_img.jpg b/marked/Rel-11/25_series/25221/165508b2526a29efbae96fa16d525d28_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3f3eaf2764c6009922bfd780b2a8a94475bfe5a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/165508b2526a29efbae96fa16d525d28_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:416aa9bb672aafc81ab168605b8b71b68bd4c69d6c344ceda60a16cd2b3949b6
+size 35868
diff --git a/marked/Rel-11/25_series/25221/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-11/25_series/25221/17431d8b59408f09df7552d8bdbaa015_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..55d4c02aef9f4e7a20b7db526aa1ad5354c0c824
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/17431d8b59408f09df7552d8bdbaa015_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67fe4d37a5ae71c3f951d8b8e1f97227f176143829f11d216971ce63734d2957
+size 42315
diff --git a/marked/Rel-11/25_series/25221/17b9d89b91e10c3efc38193baedee268_img.jpg b/marked/Rel-11/25_series/25221/17b9d89b91e10c3efc38193baedee268_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fff0f4716a83b5ea5d791f5374fc9f2171eafc85
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/17b9d89b91e10c3efc38193baedee268_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5caf7e5ee7ff6663ad06517e1505cd00549b781fd1c879ef102733818be6ca1e
+size 9561
diff --git a/marked/Rel-11/25_series/25221/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-11/25_series/25221/18291be12b470a557e8c9f3a74e021be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..58f5e46e34a0114056bc4db05d75248d15161a33
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/18291be12b470a557e8c9f3a74e021be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bc43a4b3f0f31154e7490b9e44a530c6cdf0a1f3a83cabea8fc2094ef4c86fa
+size 23916
diff --git a/marked/Rel-11/25_series/25221/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/Rel-11/25_series/25221/184d3d9a856c77aae93652f4fe30f752_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96fb7308c41b561bb884384550ef64e8b6064efe
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/184d3d9a856c77aae93652f4fe30f752_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a78913775d75895c4bae237d7b1d84d424e34110df94b269d2b4f5bff9b6a7a
+size 40944
diff --git a/marked/Rel-11/25_series/25221/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/25_series/25221/187d05bf7ead21e1394b61320d8b3632_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..170f98fe0841fc46a7c4ea1d6c12e23399a08a53
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/187d05bf7ead21e1394b61320d8b3632_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0da9e6e7b24b629c94753fc3785db771ab808252830f7436097ee4dfa2448ce6
+size 34757
diff --git a/marked/Rel-11/25_series/25221/1b3c088f23921d4eeb45ffc05586e59b_img.jpg b/marked/Rel-11/25_series/25221/1b3c088f23921d4eeb45ffc05586e59b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2748faff2e0dd2ddfc328ffcee8d6b387d7833cf
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1b3c088f23921d4eeb45ffc05586e59b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:575fab260c99528479f7df0cb2fbf766f14c5485c801a908caf286b45aa72a51
+size 60656
diff --git a/marked/Rel-11/25_series/25221/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-11/25_series/25221/1c140ee5d1a87186977da94a96bfa700_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65e6648ab11b8677c9fd53bb26d619710da07d9b
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1c140ee5d1a87186977da94a96bfa700_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1313b57804150430b9f404218661f2b1b87049c6aa99ff838fdb29b62cf9ac40
+size 21543
diff --git a/marked/Rel-11/25_series/25221/1ca688982d625c3b8a8e382b675de466_img.jpg b/marked/Rel-11/25_series/25221/1ca688982d625c3b8a8e382b675de466_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..367ea30bdd7fd9bae4e9975491acf96583c14ee6
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1ca688982d625c3b8a8e382b675de466_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a4f0ac451ee44595a2a39aae39de2be182309ad9ace55ba733c909455457ef20
+size 41946
diff --git a/marked/Rel-11/25_series/25221/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-11/25_series/25221/1ce027dfd26183da52137cf990213724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51c08be91b67aed4d17b60777c16ea2737813fdf
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1ce027dfd26183da52137cf990213724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:faffc442c04ff12fe634cb9428b94bd6f97817911b7f5d648aacbc4e8cd7ee45
+size 11087
diff --git a/marked/Rel-11/25_series/25221/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Rel-11/25_series/25221/1dbb1d90b2022a3a765c85929a515cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1a4266d84e79da3d6dec0219a4daf7cdcd28a85
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1dbb1d90b2022a3a765c85929a515cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:483629a4ce439155cc87c5124048f3f4748fa768bc6e56da26f52be0e03266f9
+size 41993
diff --git a/marked/Rel-11/25_series/25221/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Rel-11/25_series/25221/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e9b25d77cdf0ada2c406c89a9499b3bcd5f96b1
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:332793548d31c53535bbdb1776a9eb134b579a4a070a41334f7ffeeb0f95380a
+size 50750
diff --git a/marked/Rel-11/25_series/25221/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-11/25_series/25221/1f1614411edea7edfc86c839a608e1fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4d846bcbd6e5ccb63f0184fd2287f361e97eda8
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/1f1614411edea7edfc86c839a608e1fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:efe82382721e8c06449aa85575dc6c79b8a6b0f3da8baeeeb18a5bab3911d18d
+size 36945
diff --git a/marked/Rel-11/25_series/25221/23aceb0e7d3c1a644294899d9047df05_img.jpg b/marked/Rel-11/25_series/25221/23aceb0e7d3c1a644294899d9047df05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05e9548895c3bd5bfdb6322d7a14273df2a579e2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/23aceb0e7d3c1a644294899d9047df05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d38f072494392053b001a7040712d0de77ac84a27217ac325f0b5769407b1e19
+size 41770
diff --git a/marked/Rel-11/25_series/25221/24029b85683e6c5b14e96022cd9b6ff6_img.jpg b/marked/Rel-11/25_series/25221/24029b85683e6c5b14e96022cd9b6ff6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25c1e4735c5f643165fd2a0324878389ceb9bcc3
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/24029b85683e6c5b14e96022cd9b6ff6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:593c73b4a0acef236dafee4ad1dd35e961a6a90a5b46c03251138b3c3db0a28a
+size 12027
diff --git a/marked/Rel-11/25_series/25221/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/Rel-11/25_series/25221/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9757f07637e3e1664b8b8d1f1e37f1f07368f25c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ddc71e0990525f33e95a10269ad02be90ce81e12fbd2e4a6b6aa11d06cf65ce
+size 41616
diff --git a/marked/Rel-11/25_series/25221/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/25_series/25221/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03f34875d71c283634804ad243b4f75b138a5f8f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:270f6b55e43ac8dda83283caafcf67016e5a67f76d95c7de1cdb7b10e8ef508e
+size 31871
diff --git a/marked/Rel-11/25_series/25221/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-11/25_series/25221/2b00743506f6a3bbd17af764162dc76d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4703a073f771bbc9b9a7630b7b2349c7c7f02ca2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/2b00743506f6a3bbd17af764162dc76d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be414862eaa77936810476268e13248d50d0736d2c5dc836e04d8ce5626302e0
+size 40660
diff --git a/marked/Rel-11/25_series/25221/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/25_series/25221/2cf3896394a2342a2b46c504ab9a8830_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94ac23626cdc1ec8ac028a834071d303c49d5d49
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/2cf3896394a2342a2b46c504ab9a8830_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bdd2cf4d531ad74318661c1f7e05d13d2c409876ca0dc65c9ef78736afa45a4c
+size 36716
diff --git a/marked/Rel-11/25_series/25221/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-11/25_series/25221/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0699d2dc9a17ffd93374657a38d9763a69f1f286
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bbef7050963567c27a08b0d52737cff8476d40a7191b9841435bf3ab95012f1
+size 149855
diff --git a/marked/Rel-11/25_series/25221/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg b/marked/Rel-11/25_series/25221/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8afc8522afef68661398ac5c7a8bfcc7cedcb297
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3646c2b6d1e591c6ef72bebd3be81aa143475b4a69ecbd361a8361bf146f968c
+size 42931
diff --git a/marked/Rel-11/25_series/25221/2f58bcce74146d4d983070d93be12291_img.jpg b/marked/Rel-11/25_series/25221/2f58bcce74146d4d983070d93be12291_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..094fcf95743ea50fb288f207b780a6ebc4f8c217
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/2f58bcce74146d4d983070d93be12291_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30ab81299747b2c3ef8fb3a015dd967ef2b149ffbb69532bc1c8b0459884da4f
+size 22110
diff --git a/marked/Rel-11/25_series/25221/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/25_series/25221/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6debaf7e5f60c92a7dfc6b8451b99d829af155c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:323034379c4adcbbfca8d5505ee847c33f54994d80fff88fb2cf5a5af0a378ef
+size 42941
diff --git a/marked/Rel-11/25_series/25221/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/25_series/25221/32ff77da4286b58c4778033acaa10836_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..565209a068cd0123457e8f12cecf7cf2b69db61e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/32ff77da4286b58c4778033acaa10836_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e8b631249eef9eafbbf9517e9d3dde16572aba1143efc3d91f3b97833dd6b47
+size 60530
diff --git a/marked/Rel-11/25_series/25221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/25_series/25221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cbec59acda3f2dba4d1e4001af1c4e91d444c9a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43a2752b0b04c644ac117ee341ca8eb697c2b30cdb43fc514a619866b81825ae
+size 40804
diff --git a/marked/Rel-11/25_series/25221/346324c08906e6d9320f632ab916f73e_img.jpg b/marked/Rel-11/25_series/25221/346324c08906e6d9320f632ab916f73e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89ec3418cc5a343d058aacfc07212d9d07b770b9
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/346324c08906e6d9320f632ab916f73e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d34021fc8fadc52fe66173699f354ab799f7389e796a5787da3509f7996ddcb1
+size 41247
diff --git a/marked/Rel-11/25_series/25221/3621e1493d508bd789fec58ba8be9a40_img.jpg b/marked/Rel-11/25_series/25221/3621e1493d508bd789fec58ba8be9a40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20aae316cd56aa6430efd256ddc643ef36b99901
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3621e1493d508bd789fec58ba8be9a40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54d4514bb80e8fa04cb4414ddd1df23c3cf23d67b37a8ab3ecafcf19fa03772b
+size 29981
diff --git a/marked/Rel-11/25_series/25221/367378559e35017a5e1a6f5c30798c5a_img.jpg b/marked/Rel-11/25_series/25221/367378559e35017a5e1a6f5c30798c5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7daab311ed37ac758f97f0553988c739c9a9614a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/367378559e35017a5e1a6f5c30798c5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:258d58f0d5752eb30b8c6397ad5830e0c2dd215fbbdc195b2ed6e3021f1f8edc
+size 45209
diff --git a/marked/Rel-11/25_series/25221/3d590ad29ecfe728f07432e6fcb59064_img.jpg b/marked/Rel-11/25_series/25221/3d590ad29ecfe728f07432e6fcb59064_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b5a0269cf3d71adcedbe27b77b49ef98331cf17
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3d590ad29ecfe728f07432e6fcb59064_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1dac0273225b68d2e203cbd5b27fa135495ef6b46d048ab69dd219133b51bc89
+size 99703
diff --git a/marked/Rel-11/25_series/25221/3d5f590e40a34de3e874fd845a4efd53_img.jpg b/marked/Rel-11/25_series/25221/3d5f590e40a34de3e874fd845a4efd53_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6fa176a7e5a47969b77cd4cec980224cd87dc1c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3d5f590e40a34de3e874fd845a4efd53_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9685e10b0c85bdf76d6bc9ebfb1fd82677cd8e603223ac6bde5103707f8705aa
+size 24894
diff --git a/marked/Rel-11/25_series/25221/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-11/25_series/25221/3da1a07cb87051bf616c9876db958cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4865aefa1cc328142cd0de7e864d99c77f8585d7
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3da1a07cb87051bf616c9876db958cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0108015d76166e5a02c6ce15e1b3b9e6b17e0b83d0479bab6310704d88604d3
+size 21023
diff --git a/marked/Rel-11/25_series/25221/3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg b/marked/Rel-11/25_series/25221/3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97577425327c3f1200448098fdbbcebd4808ee96
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04f9f23c37418a74e453a69c4f271a83cd36954abcb384e2b8d3368b0389e80f
+size 31964
diff --git a/marked/Rel-11/25_series/25221/3f09464f0a8ac9446981a53f9b78df2c_img.jpg b/marked/Rel-11/25_series/25221/3f09464f0a8ac9446981a53f9b78df2c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..875e237b007217f76c805f96cd89cbbc17a96efb
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/3f09464f0a8ac9446981a53f9b78df2c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d1cff6625b54169bd385cde353a91bd3b4155b2d46733cace2b6ea91102b40e
+size 36470
diff --git a/marked/Rel-11/25_series/25221/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/Rel-11/25_series/25221/409498e57b1f988b2b604d12cd997002_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e02b429ca55fd2a2901c140f8cc45057a0026042
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/409498e57b1f988b2b604d12cd997002_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee701c72d70440b8b1496776569f1ba5702e4d987354da88ea86aa0e7a4ab126
+size 19827
diff --git a/marked/Rel-11/25_series/25221/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/25_series/25221/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8aec34415bd169f50a80b487bf624be70ced5281
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e320afd738a9be77e3c170006f7364a437ba4d6d0ca59ac0fbc0f6bb883e038c
+size 60970
diff --git a/marked/Rel-11/25_series/25221/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-11/25_series/25221/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b347ce4817faa3579bcb46029ab0bc7d4c52b7c6
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ebb08051d1a41001aa9bb1387038b3bcba501b9d54bf256a652e5a51f936026b
+size 20047
diff --git a/marked/Rel-11/25_series/25221/42d3842485845d9f6e511e6526061a55_img.jpg b/marked/Rel-11/25_series/25221/42d3842485845d9f6e511e6526061a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf24d59497427904d87412936f8de1238d8721ed
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/42d3842485845d9f6e511e6526061a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:029f04a916dfb90f02199f0a73345d40d94b6a14976459e8a6a085fc9789d1de
+size 22618
diff --git a/marked/Rel-11/25_series/25221/4390b89fdb95cba102ee1f88e218b07b_img.jpg b/marked/Rel-11/25_series/25221/4390b89fdb95cba102ee1f88e218b07b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79d3d43113ab1c9097f7885636e81e66c82a2e94
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/4390b89fdb95cba102ee1f88e218b07b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad76fab0c6b0d7666b3957dd7782fcf7ae603f63348ec0463b1f2c6f09c79431
+size 41909
diff --git a/marked/Rel-11/25_series/25221/468be155058fd5d2862919eb8ec35496_img.jpg b/marked/Rel-11/25_series/25221/468be155058fd5d2862919eb8ec35496_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7297c1830eed1ce4c57576825bf00ceecb89fa6c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/468be155058fd5d2862919eb8ec35496_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee64e8883f5f9bef34c36cee23b012c127ec502b56ae2d00d628c4aff36523e5
+size 41175
diff --git a/marked/Rel-11/25_series/25221/48c6848be25e5a699f0a3412e68bc102_img.jpg b/marked/Rel-11/25_series/25221/48c6848be25e5a699f0a3412e68bc102_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a62f5f2ec383e9bb17f5826a98528555209b769a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/48c6848be25e5a699f0a3412e68bc102_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d255207b473b9ee5b0fbb776d6f8e3ac8eedf9a7182de176c2a5714cd18a0b6
+size 26697
diff --git a/marked/Rel-11/25_series/25221/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/marked/Rel-11/25_series/25221/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3865ef048304202f05887f40b23057fd6ff6bd4
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e344d4a4179bdd65fd75cc047cf773ec67feff3148c5702441fa2283aa20cf84
+size 19380
diff --git a/marked/Rel-11/25_series/25221/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-11/25_series/25221/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63b2ec8eb0cd481e90396885124cea3f2949b613
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5854a1b09817f3b5cd0802bcbef2fbb876b740d49ba05a21e8d5e01bac2b504d
+size 34220
diff --git a/marked/Rel-11/25_series/25221/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/25_series/25221/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c26cd886029844853d8817e7af0c29804b308bcb
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2595e903d8063502bfab5ad7d98fabb11c1b711937d7ef6886d94fd90f0713c
+size 23435
diff --git a/marked/Rel-11/25_series/25221/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-11/25_series/25221/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc11851e50ba241574bfd190136b0f703a132321
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7b497aaa57f8fdaccfd6df63fc43af3783dfa699ce195cf015c3e58ffc994ea
+size 21819
diff --git a/marked/Rel-11/25_series/25221/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-11/25_series/25221/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dd72b0a2c8d5113f648dce69bb18d63a5b319b46
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8be18d65fa5acf3b5d1a133b24552001a8adbf406509278969e9c365570b85f
+size 24920
diff --git a/marked/Rel-11/25_series/25221/5525e7460947727851585808324e1f98_img.jpg b/marked/Rel-11/25_series/25221/5525e7460947727851585808324e1f98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba00f320866aceaa6355f20f8b6fc5d4ce1a4946
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/5525e7460947727851585808324e1f98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e25e70ff19f6e34f8fe11be8444b234fedeb75922281f7f5a3b23188b3516efa
+size 15522
diff --git a/marked/Rel-11/25_series/25221/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/25_series/25221/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40b003121b888cca750c487132bfd0c58b96f087
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1fafd05ff1b3159e237cbaa98892978cb9e3a2147f65eabba7ad715e07d001e
+size 13481
diff --git a/marked/Rel-11/25_series/25221/591746e6f224b8d929697a200e87e976_img.jpg b/marked/Rel-11/25_series/25221/591746e6f224b8d929697a200e87e976_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..028b83b3e1feabb193f70f00ef74fa20010a875f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/591746e6f224b8d929697a200e87e976_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d42e64193f0b519dbb320f7f6b7b32d401c0527654ae2c940d9237e451060919
+size 41950
diff --git a/marked/Rel-11/25_series/25221/5c65cabec7c5062117fb0d578916cf8b_img.jpg b/marked/Rel-11/25_series/25221/5c65cabec7c5062117fb0d578916cf8b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97937aafe03cc5f44d7bb56bbbba26d5593aa63f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/5c65cabec7c5062117fb0d578916cf8b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:044cc803608b7f769d75584319323fa8824a9699e6d42b6a3f30108a78955615
+size 47516
diff --git a/marked/Rel-11/25_series/25221/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-11/25_series/25221/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce12e638d9884c6a1ea92ab9fd8fc9d25520975f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c77f0c35127a10fc3a6dfa675e66de1a0b28fe27f527471f2416644892b2c937
+size 42693
diff --git a/marked/Rel-11/25_series/25221/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/marked/Rel-11/25_series/25221/5ec3284657e4df0df3653dd61d0ecd13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bb8bbbd0742c111e49d967e2e6636afd44566b59
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/5ec3284657e4df0df3653dd61d0ecd13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b11736df4e36260c2b2b96c3c7d895a686ecf9b3e36ccbf26300349a0cb7a71
+size 42001
diff --git a/marked/Rel-11/25_series/25221/6348f4fc8b3848158fcfbe85e26a731d_img.jpg b/marked/Rel-11/25_series/25221/6348f4fc8b3848158fcfbe85e26a731d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ea44fb9074bef0a559dbf6b127241f290daff37
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/6348f4fc8b3848158fcfbe85e26a731d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ad43aa45152a2ea2c010d72c63530df27ad2541c4e93ff6d69a3f41e08832e0
+size 41769
diff --git a/marked/Rel-11/25_series/25221/64bec4cd45e47e1976245711f702aca2_img.jpg b/marked/Rel-11/25_series/25221/64bec4cd45e47e1976245711f702aca2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba11b76724b98695740c47ce18933aac733286c8
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/64bec4cd45e47e1976245711f702aca2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6525138a5beb706cefa420b1815966ac6190d2629e24ddd1d55305cd8ac24757
+size 43224
diff --git a/marked/Rel-11/25_series/25221/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-11/25_series/25221/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..846981eeb0282287874624f192b814b260960d82
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3be0b2086f04da00b2bb96a39cd2b5d1be07ed4a2ffae342737edd99bde1c81c
+size 50927
diff --git a/marked/Rel-11/25_series/25221/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/25_series/25221/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80ada2893a124a261a4ddbf364a0ae04e16fb531
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2183371c78e918440c3a6635247555d451975613060f63c08af0c71b729a3b4
+size 15291
diff --git a/marked/Rel-11/25_series/25221/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/25_series/25221/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b02684fcd2218ed7bd32989bd5cf5a12334791a2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d1ca3b4062e2c8a64a8e13aa606d84f788515db83a2204595db6a4c42d23516
+size 62147
diff --git a/marked/Rel-11/25_series/25221/66f134956ab8cc4e2a57345df38dc091_img.jpg b/marked/Rel-11/25_series/25221/66f134956ab8cc4e2a57345df38dc091_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bd26dac9cc45697beee132cd8683c8768aec3a3
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/66f134956ab8cc4e2a57345df38dc091_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c3d8f451c4befd2ffe34a8e99fb42139bd0ec81f1eeddc09ade84cdf2c1250d
+size 41278
diff --git a/marked/Rel-11/25_series/25221/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/marked/Rel-11/25_series/25221/67a1dd734d3de6e31754caf85d6fe77f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..568512e51533d3e792c36873d6dcf9e0d9a353d2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/67a1dd734d3de6e31754caf85d6fe77f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9730b9d8596412efdfea0fc64eb622759a65d76a2589527152ab5ae19923a2c8
+size 41647
diff --git a/marked/Rel-11/25_series/25221/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-11/25_series/25221/67d03c9e89620d73e3786c869e559752_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6bdc0ea37f5d8136fc2bdd90723c8290cdf359e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/67d03c9e89620d73e3786c869e559752_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2601fbd6597048fb84b1b7c2f8ec093f7f76b18c676da4e9b3a481309184ba18
+size 17651
diff --git a/marked/Rel-11/25_series/25221/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/marked/Rel-11/25_series/25221/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b04841511d117838b449ee970167a89fbe370b0c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ea1015d8fe8b5b5a2d61523e1508cc5e60adfff63c892e51eca671e2fd342d2
+size 29365
diff --git a/marked/Rel-11/25_series/25221/6929132b4964d52244da61d4614bc4d6_img.jpg b/marked/Rel-11/25_series/25221/6929132b4964d52244da61d4614bc4d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..228f82d66bf1dc26f436c81e2c72a2bd318bac35
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/6929132b4964d52244da61d4614bc4d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a0c5dbf0244ace25debe4fb35576da2c25b483512231f27db337ce951506a47
+size 22282
diff --git a/marked/Rel-11/25_series/25221/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-11/25_series/25221/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2210afbb83c89596159dbd4bb642cf1bf058a5d5
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:913582bef807be57cf4e1860a19bc3b321097665b71a3893bad8c0bf9dde127a
+size 41603
diff --git a/marked/Rel-11/25_series/25221/6d2057d7e401741861ca63545a5d7d3b_img.jpg b/marked/Rel-11/25_series/25221/6d2057d7e401741861ca63545a5d7d3b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..767034fd3db4c23ba328372cc10dc250a827527e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/6d2057d7e401741861ca63545a5d7d3b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddf3a45bea27a4aa9effc2b9b2e329eef1a4316b76d7d90fa46487cf2296f08a
+size 2149
diff --git a/marked/Rel-11/25_series/25221/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-11/25_series/25221/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80e34cfdce1b11cebe5d3f509cd09ab203f63bdc
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e60874b81d2e8fb3d41fa7b5fc8e97cd0f2f7e72ae4dc7ae7a2127eb7b3908f
+size 23134
diff --git a/marked/Rel-11/25_series/25221/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg b/marked/Rel-11/25_series/25221/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92ad6348eee68c0435ce03894d3c7faff20376a2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3329e4577f3b3b8dd4fdc5ac14ea2e1137a2acf4b0d337183bdc9152a044d3f0
+size 35081
diff --git a/marked/Rel-11/25_series/25221/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-11/25_series/25221/759c7d62402f0b4651ddce292be5bdef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e118f12c0185fc278817af2e80423b0939584827
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/759c7d62402f0b4651ddce292be5bdef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:018beddf914cc07dc5e83c0e85360b25ba63f08fe23b61712ddfb55d2f935120
+size 20566
diff --git a/marked/Rel-11/25_series/25221/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-11/25_series/25221/75e4b78ee25f885d73120e3066a5253e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1be208a4adbeeaa9c96b77f6e93176468a158bbf
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/75e4b78ee25f885d73120e3066a5253e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11bf22b7e231a1dbe646726f747755ffd1b092bc9febe12b79de505a98ab485a
+size 14015
diff --git a/marked/Rel-11/25_series/25221/768942719f8a9b0d82888157aee1bae4_img.jpg b/marked/Rel-11/25_series/25221/768942719f8a9b0d82888157aee1bae4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efe8bd0f2f5df71c95838a3b3934a5459a82ec94
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/768942719f8a9b0d82888157aee1bae4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592f41f41a91b4c84eca0d31e3018ec9103a9f8f7514cd73270507612a9b8616
+size 32278
diff --git a/marked/Rel-11/25_series/25221/7818b1bd115c04ee738bcf90f51d945b_img.jpg b/marked/Rel-11/25_series/25221/7818b1bd115c04ee738bcf90f51d945b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6bb26eb2a010ec9456f792563c94e720f0ed2c76
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/7818b1bd115c04ee738bcf90f51d945b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2442f036a2bbeaa2b739775d7068b5975cf5d40185d571d11bd5db3677f5ff0f
+size 41712
diff --git a/marked/Rel-11/25_series/25221/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/25_series/25221/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cfe75f8e03ad4c6d773bcddb17e7c3370e5b43ee
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a45cc60a53ed085c3ca50d25e67af2219affff027908733cea19660a9dbb346
+size 72734
diff --git a/marked/Rel-11/25_series/25221/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/25_series/25221/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..171f6a2ec132a1092506176000372b17623db34d
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3593414c161a711fb172509b6186e83dd8ffa77c28ee4b1c42dea4c72aa4d52
+size 8165
diff --git a/marked/Rel-11/25_series/25221/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg b/marked/Rel-11/25_series/25221/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..573ff4e7e4c35e62bf35386a3275e8f8350a485f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77e11197f1062ecf85565cf0efbac0444ced494f70e9938315c2386ff059b9ea
+size 40823
diff --git a/marked/Rel-11/25_series/25221/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/25_series/25221/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f6fa36c2c5b2ab3a12bb5034b82cbab965e0f78
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59e98cdccc04c42f7ad09525ee0411301c5e9f924e8c580c8a46ae917cb8898f
+size 116874
diff --git a/marked/Rel-11/25_series/25221/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-11/25_series/25221/848073118eebfdbfdb9a60e3923fe0b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f07fa2f3665a1a942e250a7fe762292ec3925593
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/848073118eebfdbfdb9a60e3923fe0b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c31257f204ae97738ebead9fa4d6f4e278105621babdffd220bf267610208f16
+size 53955
diff --git a/marked/Rel-11/25_series/25221/85b53faf49a839f512153285c78fbbdb_img.jpg b/marked/Rel-11/25_series/25221/85b53faf49a839f512153285c78fbbdb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57a64ecf46c2bb76da4a9f7957b19a628dc1aceb
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/85b53faf49a839f512153285c78fbbdb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96112f1c4789723c151aeec732beb8f476205109a81f3285195a3c2450a81c59
+size 9513
diff --git a/marked/Rel-11/25_series/25221/87b70d2e8951032d28b4412d82cf1413_img.jpg b/marked/Rel-11/25_series/25221/87b70d2e8951032d28b4412d82cf1413_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a380f4a407d1164fe3d889031f00a8c9a9e61388
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/87b70d2e8951032d28b4412d82cf1413_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea553f5c27b01c18bc4b8b583a0119df8514e110f37c5472065bb0a80f9cd268
+size 13076
diff --git a/marked/Rel-11/25_series/25221/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/25_series/25221/8e80de0cac529b2c3775d677c5203133_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97abbd010f67158eab908ce81352dbc65068291c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/8e80de0cac529b2c3775d677c5203133_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97172543452609c19fb9064e4343b008d80c801839db76306b3fa01259f3016e
+size 31068
diff --git a/marked/Rel-11/25_series/25221/8edfc370769207831f060f44d2281084_img.jpg b/marked/Rel-11/25_series/25221/8edfc370769207831f060f44d2281084_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4e7a8d653f644872599284d5880c8bafdafc598
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/8edfc370769207831f060f44d2281084_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:930ad7fea8ee39eb31a74ce0d3568afcdcebd2b126c1a2d9f60a61cf2ac7f561
+size 42285
diff --git a/marked/Rel-11/25_series/25221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/25_series/25221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b99cf8ff6b33da425b12fd846422b64a72e2cec1
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60d0f6c6ba637be16032b6f99df2d5a13496ea2cecae439b126744ae0816f627
+size 19423
diff --git a/marked/Rel-11/25_series/25221/90df9788d66ecf65abf861caf76be5ca_img.jpg b/marked/Rel-11/25_series/25221/90df9788d66ecf65abf861caf76be5ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e95b9049fcf2b445fe1f7cdec18ca1d92de0de4a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/90df9788d66ecf65abf861caf76be5ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b00e22f198b72f80ad47679b6b26e2447815c87e8e82023de332dcf78f8d2b6d
+size 27474
diff --git a/marked/Rel-11/25_series/25221/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/Rel-11/25_series/25221/91b12db3c85bbf466ad27eb3665a1b06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53f5216e9f0761e02121828b0521ddd50d2930fa
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/91b12db3c85bbf466ad27eb3665a1b06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60d3c15037fa29e5ef73d2639c265556cdb5592fd8d8d9fdf598d8c017b8bcad
+size 7981
diff --git a/marked/Rel-11/25_series/25221/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Rel-11/25_series/25221/91c33f8e1713989e8192322ec2d1212b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..630e262fae99bf17b46be123c34af240b7a861ae
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/91c33f8e1713989e8192322ec2d1212b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0159d9df3f264c865cf1baca947ff9324fa60dab95aee75702c1d093a742794
+size 50108
diff --git a/marked/Rel-11/25_series/25221/973221d410a5fc97ca8868e730bc796a_img.jpg b/marked/Rel-11/25_series/25221/973221d410a5fc97ca8868e730bc796a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b457b5d087045afb9ae8ab399af50c6671e193e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/973221d410a5fc97ca8868e730bc796a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0fcc9fc341b23ff5dee1a3308c9143f69a690338187ca936b5d77cef5a3a7c06
+size 8980
diff --git a/marked/Rel-11/25_series/25221/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-11/25_series/25221/9870bf462aa0d916a16d14b5a100c60a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..adceb176971a12e03de116d11fbd2c30738c5442
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9870bf462aa0d916a16d14b5a100c60a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d01893ccd8f8ed11929c7c55672d4abc7bfff6958cc6cfb0b42e5392f68b7cb8
+size 35667
diff --git a/marked/Rel-11/25_series/25221/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg b/marked/Rel-11/25_series/25221/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d23d0ec49beb97bf1db3aff9669e2a75d03db124
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea2a12e134b4df9329916b9aff05490c15f22c72a8a9c1fc771b65a7c271f615
+size 12388
diff --git a/marked/Rel-11/25_series/25221/99781d878388c3e0f359b1d6ce14119c_img.jpg b/marked/Rel-11/25_series/25221/99781d878388c3e0f359b1d6ce14119c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c92ac0459313ab5ab51c58cdcfdffb1aad88291
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/99781d878388c3e0f359b1d6ce14119c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2786e3ec57fdb634cf9fabd05981e2062bdb8eff70c120994b502be5c6d7430e
+size 34869
diff --git a/marked/Rel-11/25_series/25221/99a0eddf16e836f411661acee6facd17_img.jpg b/marked/Rel-11/25_series/25221/99a0eddf16e836f411661acee6facd17_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2c8a1297a7aa278de462c5aecb5f49aaa068645
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/99a0eddf16e836f411661acee6facd17_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86c127ef0b51ebbcee42c65e525268db6947e3a6fc925188a94d37f6bc55b33e
+size 41418
diff --git a/marked/Rel-11/25_series/25221/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-11/25_series/25221/9a14684f8ae1345c6efea6f5994c730c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9da3719f6dbd884d8c51f975335d69b7681a115
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9a14684f8ae1345c6efea6f5994c730c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:771c5e2e7a9ef624a42def6369338bddc4e548c226b92a2dadc92e16046ee415
+size 26239
diff --git a/marked/Rel-11/25_series/25221/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/25_series/25221/9b1ec0090070bdf52ea28763b8d52477_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef741ba9a6213ac6e2f4eec93804876d6842e98a
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9b1ec0090070bdf52ea28763b8d52477_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8f57a6376fbaf2ff164ca8f8595c67672bd8716c0cc5461efa0a06ef9492118
+size 22713
diff --git a/marked/Rel-11/25_series/25221/9bafc60bf378685e5e246c3ffad7b792_img.jpg b/marked/Rel-11/25_series/25221/9bafc60bf378685e5e246c3ffad7b792_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd26e37c8fe03e70c46f145c881b4f7a930691c6
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9bafc60bf378685e5e246c3ffad7b792_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2b67b2714ce70cb0b0681fb5f29b6357eb0099da9152604aafbc08263ce3471
+size 43031
diff --git a/marked/Rel-11/25_series/25221/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-11/25_series/25221/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b77c9593b5b417165d7815e18dac48dc65a16d67
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:128712f1120564499f9648228e9b613a75e0296aaa7a3e0d628d1aa90daac115
+size 41370
diff --git a/marked/Rel-11/25_series/25221/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-11/25_series/25221/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c748a661cd9884c8ed2fc027e5289d764e6f432f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e846035075a4bd094cc318cce9769dd2e29655319932a5a51258ddd8c0bfe230
+size 42119
diff --git a/marked/Rel-11/25_series/25221/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg b/marked/Rel-11/25_series/25221/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..507598974d465566aeb09d91f8033501c024e27e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b57adf2c52485e5cd209cafa2ffbeb9728247fe118aa4e7ef49a50fa11b5c33a
+size 20349
diff --git a/marked/Rel-11/25_series/25221/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/25_series/25221/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e341617a43953a0a010db7d4488d3d588fd7b31
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7da2d29293ff0cc572a760596b9978fd2ab6b79eceb2dda13edafdb3357bec0f
+size 103746
diff --git a/marked/Rel-11/25_series/25221/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/25_series/25221/a0e8fe7862a6d7341faf5dac275277cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5862159504fb9f824534cfb6ea5662e2bc12ce5e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/a0e8fe7862a6d7341faf5dac275277cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95441f4456a773e8e163dbfdf855f2ddfe08db9dff9d23af3e2374f3c444f2b7
+size 58291
diff --git a/marked/Rel-11/25_series/25221/a166566092dd84196c2ec048ca175290_img.jpg b/marked/Rel-11/25_series/25221/a166566092dd84196c2ec048ca175290_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94a826d742df1b066effdd4a8d0f4e90f178551e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/a166566092dd84196c2ec048ca175290_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ada2ce51413d954122fcda24214f6c0fc3a98460e53d18aa71d00a978f16f9b7
+size 40975
diff --git a/marked/Rel-11/25_series/25221/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-11/25_series/25221/a320e67b369bfde4a5fa360b100da55c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f1e3e784b0fdc7e4b68e820a5cb0b54ebe357f2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/a320e67b369bfde4a5fa360b100da55c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:510218dff696a7f3567a15abd6547cd279e705914106b475e83da99311f4259e
+size 35722
diff --git a/marked/Rel-11/25_series/25221/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-11/25_series/25221/a5404b7275b06497eecf9b5883604753_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f9d1b90414c8b4acdc4c36c36534e7e580b7b22
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/a5404b7275b06497eecf9b5883604753_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f717cdeaf0fa36c7a911f7552b7cbddc0923b1d62eddbf574037a6a774f5116
+size 41683
diff --git a/marked/Rel-11/25_series/25221/a66383962afcd0f0458f0d45c101fabf_img.jpg b/marked/Rel-11/25_series/25221/a66383962afcd0f0458f0d45c101fabf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67d609d8676d393a89b617cf52f4309032d910b2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/a66383962afcd0f0458f0d45c101fabf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3263af5daf3a2dc8224dcb55c8644ea0f90687642ae3b8c372bcf4df6956edc6
+size 42079
diff --git a/marked/Rel-11/25_series/25221/a78db21022e0687c18d97ed547dd7ecb_img.jpg b/marked/Rel-11/25_series/25221/a78db21022e0687c18d97ed547dd7ecb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24745917508b9f9d8347b85c24959a97c04b0695
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/a78db21022e0687c18d97ed547dd7ecb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04469ebf6763948a8669626b99214d973ec61b7cf11331db0a416ddd5d7c6911
+size 65286
diff --git a/marked/Rel-11/25_series/25221/aa39f51ba214496042ee3e2ce4ecee80_img.jpg b/marked/Rel-11/25_series/25221/aa39f51ba214496042ee3e2ce4ecee80_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13ef695168d213ae57faff56d19c16d8b2972f77
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/aa39f51ba214496042ee3e2ce4ecee80_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40e49139040ed8ddce5602db68f9e7dee6a086fde30998dc35c5a099f13b665a
+size 42317
diff --git a/marked/Rel-11/25_series/25221/acdccfc1d546eaad16a58be576456caf_img.jpg b/marked/Rel-11/25_series/25221/acdccfc1d546eaad16a58be576456caf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46f7a7412bd837be99dd3375bf43c57aa27fd14f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/acdccfc1d546eaad16a58be576456caf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6b3d42e88807c0d5039d06e9b4210888c0ffe1a64fe50d016dacd5ee779d653
+size 13259
diff --git a/marked/Rel-11/25_series/25221/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/25_series/25221/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..83f4d51eb3ffc796684275f35ca048e7c70c9a58
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a074057bb41755cba68cd548b4899fc3dc6b8d07ee1a0f869cc93ab1d8e81988
+size 47043
diff --git a/marked/Rel-11/25_series/25221/b4c825454b7a89b4d7744e4f45521174_img.jpg b/marked/Rel-11/25_series/25221/b4c825454b7a89b4d7744e4f45521174_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..85daa51eb167e9a33a73b436775ee76f57cc9e6f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/b4c825454b7a89b4d7744e4f45521174_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a6822c122cc6e04d6241ca42b9d66c4946dd17cb3ee1ac3d6a462c6154a6cd3
+size 42423
diff --git a/marked/Rel-11/25_series/25221/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/25_series/25221/b5335262987c819d7f71ce40f99cb71b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0a54f512496b44d5feddcd1038309e9eaf69e295
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/b5335262987c819d7f71ce40f99cb71b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e3687c8def118c67e23c019026c6c92775f7b0e7e4727e332fa67816685ce95
+size 45095
diff --git a/marked/Rel-11/25_series/25221/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/Rel-11/25_series/25221/b58cedaf15ad4f0edee5621820865ccc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40fbb3c04c76d5fb54f6bfa4bc885eb93eb908ac
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/b58cedaf15ad4f0edee5621820865ccc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ac7009e4c9f9fad356831a6148c8c1bc1534fe7e8764a43c22ff8583212fba1
+size 20892
diff --git a/marked/Rel-11/25_series/25221/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Rel-11/25_series/25221/b8efedb73292a798b3f2050f9335cae6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c77896fa16bd8e1ec89b2ab4b47100c025f3d4d9
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/b8efedb73292a798b3f2050f9335cae6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b6edeb5b42b3dc3a4e0fb3a1834846a5d1ac6cafc078009457f1ce24009c863
+size 33528
diff --git a/marked/Rel-11/25_series/25221/b9d5785720b6edd0917019f211469dde_img.jpg b/marked/Rel-11/25_series/25221/b9d5785720b6edd0917019f211469dde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d93c6a433a1b6b436f8644ab2d48068c87601fc
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/b9d5785720b6edd0917019f211469dde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0cd63bc13bde5102a7123395eb01ffa98d79aa17c890a3b4b3d5f88d3e09cf8
+size 34446
diff --git a/marked/Rel-11/25_series/25221/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-11/25_series/25221/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d31a1e91619c6b36a270cd10649ae15a89023aa1
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08ed97474b7150f250496220699d87365bf6eb04f1094fdc0b0c2116510c45ce
+size 41538
diff --git a/marked/Rel-11/25_series/25221/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg b/marked/Rel-11/25_series/25221/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8af6b6fd69609d3ab80a9829bd7c9e6edc2a123d
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8f8814f4e3927b08052387ea8bbb9fda3df0ee449d320819f24f7a554f1ec52
+size 35116
diff --git a/marked/Rel-11/25_series/25221/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg b/marked/Rel-11/25_series/25221/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc3f9ffc9d66489b262420ea412fe022257b8b74
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a50c4dd21a9c935cf39af5e82ac9669996bfe26e4648fcf235ffd64e448938e1
+size 41364
diff --git a/marked/Rel-11/25_series/25221/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-11/25_series/25221/c21bad844b5cb6026c067a1f43ce67c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea9d1809007a96e314a347879bff4f5fa7c3d850
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/c21bad844b5cb6026c067a1f43ce67c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3bf6ea64d74dbf5da3a916c80f0d3a8c43423fd159d05e477afc6baa676d7bc
+size 41441
diff --git a/marked/Rel-11/25_series/25221/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg b/marked/Rel-11/25_series/25221/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6161e03cd6988bb74b3c44a0e910aa9d93198164
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6436f51dbc122075e92a1a295540168dd99e4cedd94d00fed68346b5a72e728
+size 12861
diff --git a/marked/Rel-11/25_series/25221/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/25_series/25221/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b2bd39d3389cdd16f1ce1efe64f15832d798d3c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:299292195b72826232372d6c733058fb498eedd8e47ae791217b50bb8abee0b4
+size 19938
diff --git a/marked/Rel-11/25_series/25221/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/Rel-11/25_series/25221/d197b6ded14ea918198a280ff07122b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d11b114192563a9cd39245abc53bc3fe3944e0c2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/d197b6ded14ea918198a280ff07122b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc7259174f76afbd1c550eb3cee30d96c8a840a1a99e495ce70fd304e6156aaf
+size 42147
diff --git a/marked/Rel-11/25_series/25221/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-11/25_series/25221/d3b5eac55166fc428a223bba5c46961b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbdc8883e282a2c994f23ab0f21c644fd8242d9e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/d3b5eac55166fc428a223bba5c46961b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16a40a40cd713cb26e8b2f9ea7497fcba264efddf2da0a3cff5d3b8fd820c37d
+size 29900
diff --git a/marked/Rel-11/25_series/25221/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg b/marked/Rel-11/25_series/25221/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..531448f5158a01ce1a6f5624548f866b13b7370c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ad26968ddf6003f728ad352ddab05aa76f1db40049f338491ca3f7d075d4f56
+size 41391
diff --git a/marked/Rel-11/25_series/25221/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-11/25_series/25221/d79d33da852cb7bca3e87b400a15c3e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5543b5bc0be0e4486fcd3eaf1715e6117d0a6baf
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/d79d33da852cb7bca3e87b400a15c3e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:886b4b5f9b600ac3c86e703fcb93a538757f353de54fa68b7dce1b6a247e999f
+size 34565
diff --git a/marked/Rel-11/25_series/25221/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-11/25_series/25221/d9cfc30025244dcd75766061f27ee09f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d3f9906527991910a1100a71c17fddcc9ddf92cb
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/d9cfc30025244dcd75766061f27ee09f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4c31c54c70b88bf0b8ae265e30e768fe275c5ebb7b5d6093c0c433cc7f5a309
+size 55228
diff --git a/marked/Rel-11/25_series/25221/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/marked/Rel-11/25_series/25221/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54174eaf31281350c12df7bd5480dc306fbd22a6
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ff932803dd80389f90780fc79e86648acfbd4a1b6726366e81fa79feef2ea7a
+size 34418
diff --git a/marked/Rel-11/25_series/25221/da5916a6e0721dae9522ac5b8abd218f_img.jpg b/marked/Rel-11/25_series/25221/da5916a6e0721dae9522ac5b8abd218f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5eb9c1b3cfb40b5d6f20af47897f30fb97a0f051
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/da5916a6e0721dae9522ac5b8abd218f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe73404f1b5b648bf5e5ce2d89176f479093588e274b55eb6abe4df5ae73c300
+size 13835
diff --git a/marked/Rel-11/25_series/25221/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-11/25_series/25221/da85343976fdbb19f866d9ddbdad0eae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3619ade7e943d7b4af0c722ea35855965a303c0
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/da85343976fdbb19f866d9ddbdad0eae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2706564dda3f607005abd80c9a9482242d6f4fd5a6ef55f1a4f9873aa76e2a9
+size 41545
diff --git a/marked/Rel-11/25_series/25221/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg b/marked/Rel-11/25_series/25221/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b7203b6ad4e727e28b71f2c9b34227ac600db14
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcfa23157d9ee1c054ec9c3612204502c76bb9dd8b3d3502476ab67dcf1fc2a7
+size 99382
diff --git a/marked/Rel-11/25_series/25221/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-11/25_series/25221/df1966d80c74bc127f159a48f38b13ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f5b723812bb455b72f669d2b301e65a74f6b7c4
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/df1966d80c74bc127f159a48f38b13ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:685f589c7b3ced5f1b4ec12e605f3ec2ef99edc547f2a53666f65087a4a0f7cf
+size 37552
diff --git a/marked/Rel-11/25_series/25221/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-11/25_series/25221/df1d0e45191302de72176e4390224c16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..af29ddf7b7c94544cff3a4a195f6fef1803635b2
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/df1d0e45191302de72176e4390224c16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4690414cd9d6218e699ed1e11335f9fcbbdde15b433bba4ee7ec6fc6e72cdad
+size 25102
diff --git a/marked/Rel-11/25_series/25221/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-11/25_series/25221/df935fc9efbd024af4ba77e46bb0bb19_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b79dae1fb2d2e7b29ccb08d329f70a898c5a1b33
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/df935fc9efbd024af4ba77e46bb0bb19_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb9ff9ae90c6ff3429e8eb6e1cdfe5d01630e9887dfeec0210a968f434cdb08f
+size 41304
diff --git a/marked/Rel-11/25_series/25221/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/25_series/25221/e05b36c0d46549e681ce6581422c66b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c42aa82c0a7dc275d244b767d01a07ee0439b672
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/e05b36c0d46549e681ce6581422c66b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35f659cce1ba540dd72940a797af65da1225d513ac02d9a25d4c26a87cad80bd
+size 41447
diff --git a/marked/Rel-11/25_series/25221/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-11/25_series/25221/e18841eb4a995df8354a793459e12fd0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71ea1fbaa27b6170ad43c91d4b68edcb5fc517a1
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/e18841eb4a995df8354a793459e12fd0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2413b93b2a4b5b003104b8c8c55d27f6d5d76ba17760be0e59a6e502fd660952
+size 40879
diff --git a/marked/Rel-11/25_series/25221/e20792fef9de6560b2d6c5441da7614a_img.jpg b/marked/Rel-11/25_series/25221/e20792fef9de6560b2d6c5441da7614a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..159d02c3f4ca52f5228bd41ea6265c4127580714
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/e20792fef9de6560b2d6c5441da7614a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07bfc47dd4fa0017c43aa86c993786f5519390ef3e96baf6f01520545116c2e9
+size 41231
diff --git a/marked/Rel-11/25_series/25221/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-11/25_series/25221/e354b57563dae469c00b412b2abdf765_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c93dafd68620463ea1773eb8b5ae08245c3127bc
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/e354b57563dae469c00b412b2abdf765_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64754a6c2c20a07ce76ccc3b3fc5e8f09570c2198108da30b2fcba59503fe2eb
+size 32781
diff --git a/marked/Rel-11/25_series/25221/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg b/marked/Rel-11/25_series/25221/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec4598479a154ad4b6470dd4d317ff555cc0132b
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b87411dfb132bb3ea098cf7b9335b68991ee21f23bd0f8b6b3f6e2cc5ea5582
+size 41419
diff --git a/marked/Rel-11/25_series/25221/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-11/25_series/25221/eabcb2f8b9acedb194571d5bc734b463_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6bc4a51d304273ec6ef9f5b751b6c078ed2baab6
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/eabcb2f8b9acedb194571d5bc734b463_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fcb1f7f3654ec2f763dcd0ea0cf04afe04a516667fbe13f9a017cdd8adc7887
+size 41502
diff --git a/marked/Rel-11/25_series/25221/ecd36a62fd70161bcbc5bff4a75b90fa_img.jpg b/marked/Rel-11/25_series/25221/ecd36a62fd70161bcbc5bff4a75b90fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10bc0414ae207a16b036fb3dc00c7cffcc425779
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ecd36a62fd70161bcbc5bff4a75b90fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e52860aacdba2b5ace01f23658c62f7ff3d25519f514ccbd134805a4b0a5b83d
+size 12066
diff --git a/marked/Rel-11/25_series/25221/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/marked/Rel-11/25_series/25221/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..409e7c761bdc92bece45d51a39e5663f3df6dbef
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7631f2310c2c3566ad317a2df12c984d3d20a632b791eac3e978cb5e1d262ed0
+size 55660
diff --git a/marked/Rel-11/25_series/25221/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg b/marked/Rel-11/25_series/25221/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b856f4fa3bb5ef5123dc02e7b497917dafc8634f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be9533170b0444acb2b3cb3898a943e00d5fa88a7f39f593898a55c11750e973
+size 41724
diff --git a/marked/Rel-11/25_series/25221/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-11/25_series/25221/ef45b00396c293be0b18d32b97118bf4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91d980ea694519e59dde439b29c59f329adc798f
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ef45b00396c293be0b18d32b97118bf4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2d36a6574123fb39a2fd5b7eb28fa888c8eb9a0832cab752b7804183a710563
+size 41341
diff --git a/marked/Rel-11/25_series/25221/ef86416097668984aee7611317e77bb9_img.jpg b/marked/Rel-11/25_series/25221/ef86416097668984aee7611317e77bb9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb43275b06d88e9b4e694f2ef810a41740c520f7
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ef86416097668984aee7611317e77bb9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d1ffb3190af7b359e8f890a25d57ec70265879810fdd10cfc700801f461bb99
+size 100140
diff --git a/marked/Rel-11/25_series/25221/efe7822cf973305b4681375549f04650_img.jpg b/marked/Rel-11/25_series/25221/efe7822cf973305b4681375549f04650_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..405145d436a3daa3db6cc5644df5cd2941a1fe50
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/efe7822cf973305b4681375549f04650_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3d479eb5a51c4ed20edd0446764932de5311e29ced9d4e20e90aa7e87067d07
+size 8849
diff --git a/marked/Rel-11/25_series/25221/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/25_series/25221/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe3a371003c3b8d1572dfa2d3ec6d0434e3d40b9
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e5fb3f7c14d098cd88a01ec9f8ddbbe32c110ba6d52c7ca96b7b75ab309d848
+size 26579
diff --git a/marked/Rel-11/25_series/25221/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/marked/Rel-11/25_series/25221/f1ba1e68228ebd4c3109371574a723e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24582fdc9e8d4db8f02892358439a17a9dcd1d25
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/f1ba1e68228ebd4c3109371574a723e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9de955e8cd5d5d0075c4712bd723a0616f91fb5323ee65ce8b5c8df2ccf0f00
+size 41416
diff --git a/marked/Rel-11/25_series/25221/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-11/25_series/25221/f2ea0f64a770b22b902820457d262265_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0241084b82c97540e13e69cc61e0951d24ec7299
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/f2ea0f64a770b22b902820457d262265_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d26574aad12ce928369142675c5570d8a8a04913156b371386a21c302c4c0e8
+size 15369
diff --git a/marked/Rel-11/25_series/25221/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/marked/Rel-11/25_series/25221/f5d2a88925807080157c7cfb1d41cf0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4508e27982d925911b8687420dbcef74039a540b
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/f5d2a88925807080157c7cfb1d41cf0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0782ccc39a860100cd1bf0eb6abb230f3d69ab5c8415a97223b585f15844792
+size 39563
diff --git a/marked/Rel-11/25_series/25221/f9625fa3465b009051f85d91cfa1da7e_img.jpg b/marked/Rel-11/25_series/25221/f9625fa3465b009051f85d91cfa1da7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff36b2fec54fb7e790a33c6aad316ed9e232edff
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/f9625fa3465b009051f85d91cfa1da7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5378bb26fe1f48f76a69d066656b651cb6eaecd07fe07ae088095808360e068
+size 144898
diff --git a/marked/Rel-11/25_series/25221/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-11/25_series/25221/fc3e2b49a9f850951570e502393b697f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e85398920ede30375aa88d9fa638c1964e4a59ef
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/fc3e2b49a9f850951570e502393b697f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1f69726b4d6478ce3a30cfdc535c6abc819b2b7e1c03d8e9dcc269fe22802c5
+size 41497
diff --git a/marked/Rel-11/25_series/25221/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-11/25_series/25221/fe7304192caf64cda93b580c5e7e5c06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef48f276d6d7da055a3bf4593906b5f9b69fbd76
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/fe7304192caf64cda93b580c5e7e5c06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a69c3f39601b3a9f3d530592ddf1e4902dcddfaae04eb2ffec58dfafadb4f214
+size 37372
diff --git a/marked/Rel-11/25_series/25221/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg b/marked/Rel-11/25_series/25221/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..192fc5b35053682977ff6496bd3d8c7a680e0e2c
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94e9b6d973e0c7755839dbce5953c03d9bd1554088934038c3814115fca05de3
+size 41572
diff --git a/marked/Rel-11/25_series/25221/raw.md b/marked/Rel-11/25_series/25221/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c0759a49ec08261ce4f4c03365121c2e654da54e
--- /dev/null
+++ b/marked/Rel-11/25_series/25221/raw.md
@@ -0,0 +1,8241 @@
+**Error:**
+
+**2**
+
+**Error: Reference source not**
+
+# --- Contents
+
+| | |
+|------------------------------------------------------------------------------|----|
+| Foreword..... | 12 |
+| 1 Scope..... | 13 |
+| 2 References..... | 13 |
+| 3 Abbreviations..... | 14 |
+| 4 Services offered to higher layers..... | 15 |
+| 4.1 Transport channels..... | 15 |
+| 4.1.1 Dedicated transport channels..... | 15 |
+| 4.1.1.1 DCH – Dedicated Channel..... | 15 |
+| 4.1.1.2 E-DCH – Enhanced Dedicated Channel..... | 15 |
+| 4.1.2 Common transport channels..... | 15 |
+| 4.1.2.1 BCH - Broadcast Channel..... | 16 |
+| 4.1.2.2 FACH – Forward Access Channel..... | 16 |
+| 4.1.2.3 PCH – Paging Channel..... | 16 |
+| 4.1.2.4 RACH – Random Access Channel..... | 16 |
+| 4.1.2.5 USCH – Uplink Shared Channel..... | 16 |
+| 4.1.2.6 DSCH – Downlink Shared Channel..... | 16 |
+| 4.1.2.7 HS-DSCH – High Speed Downlink Shared Channel..... | 16 |
+| 4.1.2.8 E-DCH – Enhanced Dedicated Channel..... | 16 |
+| 4.2 Indicators..... | 16 |
+| 5 Physical channels for the 3.84 Mcps option..... | 17 |
+| 5.1 Frame structure..... | 17 |
+| 5.2 Dedicated physical channel (DPCH)..... | 18 |
+| 5.2.1 Spreading..... | 19 |
+| 5.2.1.1 Spreading for Downlink Physical Channels..... | 19 |
+| 5.2.1.2 Spreading for Uplink Physical Channels..... | 19 |
+| 5.2.2 Burst Types..... | 19 |
+| 5.2.2.1 Burst Type 1..... | 19 |
+| 5.2.2.2 Burst Type 2..... | 20 |
+| 5.2.2.3 Burst Type 3..... | 20 |
+| 5.2.2.3A Burst Type 4..... | 21 |
+| 5.2.2.4 Transmission of TFCI..... | 21 |
+| 5.2.2.5 Transmission of TPC..... | 23 |
+| 5.2.2.6 Timeslot formats..... | 23 |
+| 5.2.2.6.1 Downlink timeslot formats..... | 23 |
+| 5.2.2.6.2 Uplink timeslot formats..... | 24 |
+| 5.2.3 Training sequences for spread bursts..... | 26 |
+| 5.2.4 Beamforming..... | 28 |
+| 5.3 Common physical channels..... | 29 |
+| 5.3.1 Primary common control physical channel (P-CCPCH)..... | 29 |
+| 5.3.1.1 P-CCPCH Spreading..... | 29 |
+| 5.3.1.2 P-CCPCH Burst Types..... | 29 |
+| 5.3.1.3 P-CCPCH Training sequences..... | 29 |
+| 5.3.2 Secondary common control physical channel (S-CCPCH)..... | 29 |
+| 5.3.2.1 S-CCPCH Spreading..... | 29 |
+| 5.3.2.2 S-CCPCH Burst Types..... | 29 |
+| 5.3.2.2A S-CCPCH Modulation..... | 29 |
+| 5.3.2.3 S-CCPCH Training sequences..... | 29 |
+| 5.3.3 The physical random access channel (PRACH)..... | 29 |
+| 5.3.3.1 PRACH Spreading..... | 29 |
+| 5.3.3.2 PRACH Burst Type..... | 30 |
+| 5.3.3.3 PRACH Training sequences..... | 30 |
+| 5.3.3.4 PRACH timeslot formats..... | 30 |
+| 5.3.3.5 Association between Training Sequences and Channelisation Codes..... | 30 |
+| 5.3.4 The synchronisation channel (SCH)..... | 32 |
+| 5.3.5 Physical Uplink Shared Channel (PUSCH)..... | 33 |
+| 5.3.5.1 PUSCH Spreading..... | 33 |
+
+| | | |
+|-----------|--------------------------------------------------------------------------|----|
+| 5.3.5.2 | PUSCH Burst Types..... | 34 |
+| 5.3.5.3 | PUSCH Training Sequences..... | 34 |
+| 5.3.5.4 | UE Selection..... | 34 |
+| 5.3.6 | Physical Downlink Shared Channel (PDSCH)..... | 34 |
+| 5.3.6.1 | PDSCH Spreading..... | 34 |
+| 5.3.6.2 | PDSCH Burst Types..... | 34 |
+| 5.3.6.3 | PDSCH Training Sequences..... | 34 |
+| 5.3.6.4 | UE Selection..... | 34 |
+| 5.3.7 | The Paging Indicator Channel (PICH)..... | 34 |
+| 5.3.7.1 | Mapping of Paging Indicators to the PICH bits..... | 34 |
+| 5.3.7.2 | Structure of the PICH over multiple radio frames..... | 35 |
+| 5.3.7.3 | PICH Training sequences..... | 36 |
+| 5.3.8 | The physical node B synchronisation channel (PNBSCH)..... | 36 |
+| 5.3.9 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 36 |
+| 5.3.9.1 | HS-PDSCH Spreading..... | 36 |
+| 5.3.9.2 | HS-PDSCH Burst Types..... | 36 |
+| 5.3.9.3 | HS-PDSCH Training Sequences..... | 36 |
+| 5.3.9.4 | UE Selection..... | 36 |
+| 5.3.9.5 | HS-PDSCH timeslot formats..... | 36 |
+| 5.3.10 | Shared Control Channel for HS-DSCH (HS-SCCH)..... | 37 |
+| 5.3.10.1 | HS-SCCH Spreading..... | 37 |
+| 5.3.10.2 | HS-SCCH Burst Types..... | 37 |
+| 5.3.10.3 | HS-SCCH Training Sequences..... | 37 |
+| 5.3.10.4 | HS-SCCH timeslot formats..... | 37 |
+| 5.3.11 | Shared Information Channel for HS-DSCH (HS-SICH)..... | 37 |
+| 5.3.11.1 | HS-SICH Spreading..... | 37 |
+| 5.3.11.2 | HS-SICH Burst Types..... | 37 |
+| 5.3.11.3 | HS-SICH Training Sequences..... | 37 |
+| 5.3.11.4 | HS-SICH timeslot formats..... | 38 |
+| 5.3.12 | The MBMS Indicator Channel (MICH)..... | 38 |
+| 5.3.12.1 | Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2..... | 38 |
+| 5.3.12.1A | Mapping of MBMS Indicators to the MICH bits for burst type 4..... | 39 |
+| 5.3.12.2 | MICH Training sequences..... | 40 |
+| 5.3.13 | E-DCH Physical Uplink Channel (E-PUCH)..... | 40 |
+| 5.3.13.1 | E-UCCH..... | 40 |
+| 5.3.13.2 | E-PUCH Spreading..... | 41 |
+| 5.3.13.3 | E-PUCH Burst Types..... | 41 |
+| 5.3.13.4 | PUSCH Training Sequences..... | 41 |
+| 5.3.13.5 | UE Selection..... | 41 |
+| 5.3.13.6 | E-PUCH timeslot formats..... | 41 |
+| 5.3.14 | E-DCH Random Access Uplink Control Channel (E-RUCCH)..... | 43 |
+| 5.3.15 | E-DCH Absolute Grant Channel (E-AGCH)..... | 43 |
+| 5.3.15.1 | E-AGCH Spreading..... | 43 |
+| 5.3.15.2 | E-AGCH Burst Types..... | 43 |
+| 5.3.15.3 | E-AGCH Training Sequences..... | 44 |
+| 5.3.15.4 | E-AGCH timeslot formats..... | 44 |
+| 5.3.16 | E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)..... | 44 |
+| 5.3.16.1 | E-HICH Spreading..... | 45 |
+| 5.3.16.2 | E-HICH Burst Types..... | 45 |
+| 5.3.16.3 | E-HICH Training Sequences..... | 45 |
+| 5.4 | Transmit Diversity for DL Physical Channels..... | 45 |
+| 5.5 | Beacon characteristics of physical channels..... | 45 |
+| 5.5.1 | Location of beacon channels..... | 45 |
+| 5.5.2 | Physical characteristics of beacon channels..... | 46 |
+| 5.6 | Midamble Allocation for Physical Channels..... | 46 |
+| 5.6.1 | Midamble Allocation for DL Physical Channels..... | 46 |
+| 5.6.1.1 | Midamble Allocation by signalling from higher layers..... | 47 |
+| 5.6.1.2 | Midamble Allocation by layer 1..... | 47 |
+| 5.6.1.2.1 | Default midamble..... | 47 |
+| 5.6.1.2.2 | Common Midamble..... | 47 |
+| 5.6.2 | Midamble Allocation for UL Physical Channels..... | 48 |
+
+| | | |
+|------------|----------------------------------------------------------------------|----|
+| 5.7 | Midamble Transmit Power..... | 48 |
+| 5.8 | Physical channels for the 3.84 Mcps MBSFN IMB option..... | 49 |
+| 5.8.1 | Transmit diversity..... | 50 |
+| 5.8.2 | Common physical channels..... | 50 |
+| 5.8.2.1 | Primary Common Pilot Channel (P-CPICH)..... | 50 |
+| 5.8.2.2 | Time-multiplexed Common Pilot Channel (T-CPICH)..... | 50 |
+| 5.8.2.3 | Primary common control physical channel (P-CCPCH)..... | 51 |
+| 5.8.2.4 | Secondary common control physical channel (S-CCPCH)..... | 52 |
+| 5.8.2.5 | Synchronisation channel (SCH)..... | 54 |
+| 5.8.2.6 | The MBMS indicator channel (MICH)..... | 54 |
+| 5.8.3 | Timing relationship between physical channels..... | 55 |
+| 5A | Physical channels for the 1.28 Mcps option..... | 56 |
+| 5A.1 | Frame structure..... | 57 |
+| 5A.2 | Dedicated physical channel (DPCH)..... | 58 |
+| 5A.2.1 | Spreading..... | 58 |
+| 5A.2.2 | Burst Format..... | 58 |
+| 5A.2.2a | Dedicated carrier MBSFN Burst Format..... | 59 |
+| 5A.2.2.1 | Transmission of TFCI..... | 60 |
+| 5A.2.2.1a | Transmission of TFCI for MT burst and MS burst..... | 61 |
+| 5A.2.2.2 | Transmission of TPC..... | 62 |
+| 5A.2.2.3 | Transmission of SS..... | 65 |
+| 5A.2.2.4 | Timeslot formats..... | 67 |
+| 5A.2.2.4.1 | Timeslot formats for QPSK..... | 68 |
+| 5A.2.2.4.2 | Time slot formats for 8PSK..... | 71 |
+| 5A.2.2.4.3 | Time slot formats for MBSFN..... | 71 |
+| 5A.2.3 | Training sequences for spread bursts..... | 72 |
+| 5A.2.3a | Training sequences for dedicated carrier MBSFN..... | 74 |
+| 5A.2.4 | Beamforming..... | 74 |
+| 5A.3 | Common physical channels..... | 74 |
+| 5A.3.1 | Primary common control physical channel (P-CCPCH)..... | 74 |
+| 5A.3.1.1 | P-CCPCH Spreading..... | 74 |
+| 5A.3.1.2 | P-CCPCH Burst Format..... | 75 |
+| 5A.3.1.3 | P-CCPCH Training sequences..... | 75 |
+| 5A.3.2 | Secondary common control physical channel (S-CCPCH)..... | 75 |
+| 5A.3.2.1 | S-CCPCH Spreading..... | 75 |
+| 5A.3.2.2 | S-CCPCH Burst Format..... | 75 |
+| 5A.3.2.3 | S-CCPCH Training sequences..... | 75 |
+| 5A.3.3 | Fast Physical Access CHannel (FPACH)..... | 75 |
+| 5A.3.3.1 | FPACH burst..... | 75 |
+| 5A.3.3.1.1 | Signature Reference Number..... | 76 |
+| 5A.3.3.1.2 | Relative Sub-Frame Number..... | 76 |
+| 5A.3.3.1.3 | Received starting position of the UpPCH (UpPCH pos )..... | 76 |
+| 5A.3.3.1.4 | Transmit Power Level Command for the RACH message..... | 76 |
+| 5A.3.3.2 | FPACH Spreading..... | 76 |
+| 5A.3.3.3 | FPACH Burst Format..... | 76 |
+| 5A.3.3.4 | FPACH Training sequences..... | 76 |
+| 5A.3.3.5 | FPACH timeslot formats..... | 76 |
+| 5A.3.4 | The physical random access channel (PRACH)..... | 77 |
+| 5A.3.4.1 | PRACH Spreading..... | 77 |
+| 5A.3.4.2 | PRACH Burst Format..... | 77 |
+| 5A.3.4.3 | PRACH Training sequences..... | 77 |
+| 5A.3.4.4 | PRACH timeslot formats..... | 77 |
+| 5A.3.4.5 | Association between Training Sequences and Channelisation Codes..... | 77 |
+| 5A.3.5 | The synchronisation channels (DwPCH, UpPCH)..... | 77 |
+| 5A.3.6 | Physical Uplink Shared Channel (PUSCH)..... | 78 |
+| 5A.3.7 | Physical Downlink Shared Channel (PDSCH)..... | 78 |
+| 5A.3.8 | The Page Indicator Channel (PICH)..... | 78 |
+| 5A.3.8.1 | Mapping of Paging Indicators to the PICH bits..... | 78 |
+| 5A.3.8.2 | Structure of the PICH over multiple radio frames..... | 79 |
+| 5A.3.9 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 79 |
+| 5A.3.9.1 | HS-PDSCH Spreading..... | 79 |
+
+| | | |
+|------------|------------------------------------------------------------------|----|
+| 5A.3.9.2 | HS-PDSCH Burst Format..... | 79 |
+| 5A.3.9.3 | HS-PDSCH Training Sequences..... | 80 |
+| 5A.3.9.4 | UE Selection..... | 80 |
+| 5A.3.9.5 | HS-PDSCH timeslot formats..... | 80 |
+| 5A.3.9.6 | Transmission of SS and TPC..... | 80 |
+| 5A.3.10 | Shared Control Channel for HS-DSCH (HS-SCCH)..... | 80 |
+| 5A.3.10.1 | HS-SCCH Spreading..... | 81 |
+| 5A.3.10.2 | HS-SCCH Burst Format..... | 81 |
+| 5A.3.10.3 | HS-SCCH Training Sequences..... | 81 |
+| 5A.3.10.4 | HS-SCCH timeslot formats..... | 81 |
+| 5A.3.11 | Shared Information Channel for HS-DSCH (HS-SICH)..... | 81 |
+| 5A.3.11.1 | HS-SICH Spreading..... | 81 |
+| 5A.3.11.2 | HS-SICH Burst Format..... | 81 |
+| 5A.3.11.3 | HS-SICH Training Sequences..... | 81 |
+| 5A.3.11.4 | HS-SICH timeslot formats..... | 81 |
+| 5A.3.12 | The MBMS Indicator Channel (MICH) type1..... | 81 |
+| 5A.3.12.1 | Mapping of MBMS Indicators to the type1 MICH bits..... | 82 |
+| 5A.3.12a | The MBMS Indicator Channel (MICH) type 2..... | 82 |
+| 5A.3.12.1 | Mapping of MBMS Indicators to the type 2 MICH bits..... | 82 |
+| 5A.3.13 | Physical Layer Common Control Channel (PLCCH)..... | 83 |
+| 5A.3.13.1 | PLCCH Spreading..... | 83 |
+| 5A.3.13.2 | PLCCH Burst Type..... | 83 |
+| 5A.3.13.3 | PLCCH Training Sequence..... | 83 |
+| 5A.3.13.4 | PLCCH timeslot formats..... | 84 |
+| 5A.3.14 | E-DCH Physical Uplink Channel..... | 84 |
+| 5A.3.14.1 | E-UCCH..... | 84 |
+| 5A.3.14.2 | E-PUCH Spreading..... | 85 |
+| 5A.3.14.3 | E-PUCH Burst Types..... | 85 |
+| 5A.3.14.4 | E-PUCH Training Sequences..... | 85 |
+| 5A.3.14.5 | UE Selection..... | 85 |
+| 5A.3.14.6 | E-PUCH timeslot formats..... | 85 |
+| 5A.3.15 | E-DCH Random Access Uplink Control Channel (E-RUCCH)..... | 92 |
+| 5A.3.15.1 | E-RUCCH Spreading..... | 92 |
+| 5A.3.15.2 | E-RUCCH Burst Format..... | 92 |
+| 5A.3.15.3 | E-RUCCH Training sequences..... | 92 |
+| 5A.3.15.4 | E-RUCCH timeslot formats..... | 92 |
+| 5A.3.16 | E-DCH Absolute Grant Channel (E-AGCH)..... | 92 |
+| 5A.3.16.1 | E-AGCH Spreading..... | 92 |
+| 5A.3.16.2 | E-AGCH Burst Types..... | 92 |
+| 5A.3.16.3 | E-AGCH Training Sequences..... | 93 |
+| 5A.3.16.4 | E-AGCH timeslot formats..... | 93 |
+| 5A.3.17 | E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)..... | 93 |
+| 5A.3.17.1 | E-HICH Spreading..... | 94 |
+| 5A.3.17.2 | E-HICH Burst Types..... | 94 |
+| 5A.3.17.3 | E-HICH Training Sequences..... | 94 |
+| 5A.3.17.4 | E-HICH timeslot formats..... | 94 |
+| 5A.3.18 | Standalone midamble channel..... | 94 |
+| 5A.3.18.1 | Standalone midamble channel Burst Format..... | 94 |
+| 5A.3.18.3 | Standalone midamble channel Training Sequences..... | 95 |
+| 5A.3.18.4 | Standalone midamble channel timeslot formats..... | 95 |
+| 5A.4 | Transmit Diversity for DL Physical Channels..... | 96 |
+| 5A.5 | Beacon characteristics of physical channels..... | 96 |
+| 5A.5.1 | Location of beacon channels..... | 96 |
+| 5A.5.2 | Physical characteristics of the beacon function..... | 96 |
+| 5A.6 | Midamble Allocation for Physical Channels..... | 97 |
+| 5A.6.1 | Midamble Allocation for DL Physical Channels..... | 97 |
+| 5A.6.1.1 | Midamble Allocation by signalling from higher layers..... | 97 |
+| 5A.6.1.2 | Midamble Allocation by layer 1..... | 97 |
+| 5A.6.1.2.1 | Default midamble..... | 97 |
+| 5A.6.1.2.2 | Common Midamble..... | 98 |
+| 5A.6.1.2.3 | Special Default Midamble..... | 98 |
+
+| | | |
+|------------|----------------------------------------------------------------------|-----|
+| 5A.6.2 | Midamble Allocation for UL Physical Channels..... | 98 |
+| 5A.7 | Midamble Transmit Power..... | 98 |
+| 5A.7a | Preamble Allocation and Preamble Transmit Power..... | 98 |
+| 5B | Physical channels for the 7.68 Mcps option..... | 98 |
+| 5B.1 | General..... | 98 |
+| 5B.2 | Frame structure..... | 99 |
+| 5B.3 | Dedicated physical channel (DPCH)..... | 100 |
+| 5B.3.1 | Spreading..... | 100 |
+| 5B.3.1.1 | Spreading for Downlink Physical Channels..... | 100 |
+| 5B.3.1.2 | Spreading for Uplink Physical Channels..... | 100 |
+| 5B.3.2 | Burst Types..... | 100 |
+| 5B.3.2.1 | Burst Type 1..... | 101 |
+| 5B.3.2.2 | Burst Type 2..... | 101 |
+| 5B.3.2.3 | Burst Type 3..... | 102 |
+| 5B.3.2.3A | Burst Type 4..... | 102 |
+| 5B.3.2.4 | Transmission of TFCI..... | 102 |
+| 5B.3.2.5 | Transmission of TPC..... | 104 |
+| 5B.3.2.6 | Timeslot formats..... | 105 |
+| 5B.3.2.6.1 | Downlink timeslot formats..... | 105 |
+| 5B.3.2.6.2 | Uplink timeslot formats..... | 106 |
+| 5B.3.3 | Training sequences for spread bursts..... | 108 |
+| 5B.3.4 | Beamforming..... | 110 |
+| 5B.4 | Common physical channels..... | 110 |
+| 5B.4.1 | Primary common control physical channel (P-CCPCH)..... | 110 |
+| 5B.4.1.1 | P-CCPCH Spreading..... | 110 |
+| 5B.4.1.2 | P-CCPCH Burst Types..... | 110 |
+| 5B.4.1.3 | P-CCPCH Training sequences..... | 110 |
+| 5B.4.2 | Secondary common control physical channel (S-CCPCH)..... | 110 |
+| 5B.4.2.1 | S-CCPCH Spreading..... | 110 |
+| 5B.4.2.2 | S-CCPCH Burst Types..... | 110 |
+| 5B.4.2.2A | S-CCPCH Modulation..... | 110 |
+| 5B.4.2.3 | S-CCPCH Training sequences..... | 110 |
+| 5B.4.3 | The physical random access channel (PRACH)..... | 110 |
+| 5B.4.3.1 | PRACH Spreading..... | 111 |
+| 5B.4.3.2 | PRACH Burst Type..... | 111 |
+| 5B.4.3.3 | PRACH Training sequences..... | 111 |
+| 5B.4.3.4 | PRACH timeslot formats..... | 111 |
+| 5B.4.3.5 | Association between Training Sequences and Channelisation Codes..... | 111 |
+| 5B.4.4 | The synchronisation channel (SCH)..... | 112 |
+| 5B.4.5 | Physical Uplink Shared Channel (PUSCH)..... | 113 |
+| 5B.4.5.1 | PUSCH Spreading..... | 113 |
+| 5B.4.5.2 | PUSCH Burst Types..... | 114 |
+| 5B.4.5.3 | PUSCH Training Sequences..... | 114 |
+| 5B.4.5.4 | UE Selection..... | 114 |
+| 5B.4.6 | Physical Downlink Shared Channel (PDSCH)..... | 114 |
+| 5B.4.6.1 | PDSCH Spreading..... | 114 |
+| 5B.4.6.2 | PDSCH Burst Types..... | 114 |
+| 5B.4.6.3 | PDSCH Training Sequences..... | 114 |
+| 5B.4.6.4 | UE Selection..... | 114 |
+| 5B.4.7 | The Paging Indicator Channel (PICH)..... | 114 |
+| 5B.4.7.1 | Mapping of Paging Indicators to the PICH bits..... | 114 |
+| 5B.4.7.2 | Structure of the PICH over multiple radio frames..... | 115 |
+| 5B.4.7.3 | PICH Training sequences..... | 115 |
+| 5B.4.8 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 115 |
+| 5B.4.8.1 | HS-PDSCH Spreading..... | 115 |
+| 5B.4.8.2 | HS-PDSCH Burst Types..... | 115 |
+| 5B.4.8.3 | HS-PDSCH Training Sequences..... | 116 |
+| 5B.4.8.4 | UE Selection..... | 116 |
+| 5B.4.8.5 | HS-PDSCH timeslot formats..... | 116 |
+| 5B.4.9 | Shared Control Channel for HS-DSCH (HS-SCCH)..... | 116 |
+| 5B.4.9.1 | HS-SCCH Spreading..... | 116 |
+
+| | | |
+|------------|----------------------------------------------------------------------------------|-----|
+| 5B.4.9.2 | HS-SCCH Burst Types..... | 116 |
+| 5B.4.9.3 | HS-SCCH Training Sequences..... | 116 |
+| 5B.4.9.4 | HS-SCCH timeslot formats..... | 116 |
+| 5B.4.10 | Shared Information Channel for HS-DSCH (HS-SICH)..... | 117 |
+| 5B.4.10.1 | HS-SICH Spreading..... | 117 |
+| 5B.4.10.2 | HS-SICH Burst Types..... | 117 |
+| 5B.4.10.3 | HS-SICH Training Sequences..... | 117 |
+| 5B.4.10.4 | HS-SICH timeslot formats..... | 117 |
+| 5B.4.11 | The MBMS Indicator Channel (MICH)..... | 117 |
+| 5B.4.11.1 | Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2..... | 117 |
+| 5B.4.11.1A | Mapping of MBMS Indicators to the MICH bits for burst type 4..... | 118 |
+| 5B.4.11.2 | MICH Training sequences..... | 119 |
+| 5B.4.12 | E-DCH Physical Uplink Channel (E-PUCH)..... | 119 |
+| 5B.4.12.1 | E-UCCH..... | 119 |
+| 5B.4.12.2 | E-PUCH Spreading..... | 120 |
+| 5B.4.12.3 | E-PUCH Burst Types..... | 120 |
+| 5B.4.12.4 | PUSCH Training Sequences..... | 120 |
+| 5B.4.12.5 | UE Selection..... | 120 |
+| 5B.4.12.6 | E-PUCH timeslot formats..... | 121 |
+| 5B.4.13 | E-DCH Random Access Uplink Control Channel (E-RUCCH)..... | 122 |
+| 5B.4.14 | E-DCH Absolute Grant Channel (E-AGCH)..... | 122 |
+| 5B.4.14.1 | E-AGCH Spreading..... | 123 |
+| 5B.4.14.2 | E-AGCH Burst Types..... | 123 |
+| 5B.4.14.3 | E-AGCH Training Sequences..... | 123 |
+| 5B.4.15.4 | E-AGCH timeslot formats..... | 123 |
+| 5B.4.15 | E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)..... | 123 |
+| 5B.4.15.1 | E-HICH Spreading..... | 124 |
+| 5B.4.15.2 | E-HICH Burst Types..... | 124 |
+| 5B.4.15.3 | E-HICH Training Sequences..... | 124 |
+| 5B.5 | Transmit Diversity for DL Physical Channels..... | 124 |
+| 5B.6 | Beacon characteristics of physical channels..... | 124 |
+| 5B.6.1 | Location of beacon channels..... | 125 |
+| 5B.6.2 | Physical characteristics of beacon channels..... | 125 |
+| 5B.7 | Midamble Allocation for Physical Channels..... | 125 |
+| 5B.8 | Midamble Transmit Power..... | 125 |
+| 6 | Mapping of transport channels to physical channels for the 3.84 Mcps option..... | 127 |
+| 6.1 | Dedicated Transport Channels..... | 127 |
+| 6.1.1 | The Dedicated Channel (DCH)..... | 127 |
+| 6.1.2 | The Enhanced Uplink Dedicated Channel (E-DCH)..... | 128 |
+| 6.1.2.1 | E-DCH/E-AGCH Association and Timing..... | 128 |
+| 6.1.2.2 | E-DCH/E-HICH Association and Timing..... | 128 |
+| 6.2 | Common Transport Channels..... | 129 |
+| 6.2.1 | The Broadcast Channel (BCH)..... | 129 |
+| 6.2.2 | The Paging Channel (PCH)..... | 129 |
+| 6.2.2.1 | PCH/PICH Association..... | 130 |
+| 6.2.3 | The Forward Channel (FACH)..... | 130 |
+| 6.2.4 | The Random Access Channel (RACH)..... | 130 |
+| 6.2.5 | The Uplink Shared Channel (USCH)..... | 130 |
+| 6.2.6 | The Downlink Shared Channel (DSCH)..... | 130 |
+| 6.2.7 | The High Speed Downlink Shared Channel (HS-DSCH)..... | 130 |
+| 6.2.7.1 | HS-DSCH/HS-SCCH Association and Timing..... | 130 |
+| 6.2.7.2 | HS-SCCH/HS-DSCH/HS-SICH Association and Timing..... | 131 |
+| 6.3 | Mapping of TrCHs for the 3.84 Mcps MBSFN IMB option..... | 132 |
+| 7 | Mapping of transport channels to physical channels for the 1.28 Mcps option..... | 132 |
+| 7.1 | Dedicated Transport Channels..... | 132 |
+| 7.1.1 | The Dedicated Channel (DCH)..... | 132 |
+| 7.1.2 | The Enhanced Uplink Dedicated Channel (E-DCH)..... | 133 |
+| 7.1.2.1 | E-DCH/E-AGCH Association and Timing..... | 133 |
+| 7.1.2.2 | E-DCH/E-HICH Association and Timing..... | 134 |
+| 7.2 | Common Transport Channels..... | 134 |
+
+| | | |
+|------------------------------|-----------------------------------------------------------------------------------------------------|------------|
+| 7.2.1 | The Broadcast Channel (BCH)..... | 134 |
+| 7.2.2 | The Paging Channel (PCH)..... | 134 |
+| 7.2.3 | The Forward Channel (FACH)..... | 134 |
+| 7.2.4 | The Random Access Channel (RACH)..... | 134 |
+| 7.2.5 | The Uplink Shared Channel (USCH)..... | 135 |
+| 7.2.6 | The Downlink Shared Channel (DSCH)..... | 135 |
+| 7.2.7 | The High Speed Downlink Shared Channel (HS-DSCH)..... | 135 |
+| 7.2.7.1 | HS-DSCH/HS-SCCH Association and Timing..... | 135 |
+| 7.2.7.2 | HS-SCCH/HS-DSCH/HS-SICH Association and Timing..... | 136 |
+| 7.2.7.3 | PICH/HS-SCCH/HS-DSCH Association and Timing..... | 137 |
+| 7.2.7.4 | PICH/ HS-DSCH Association and Timing..... | 137 |
+| 8 | Mapping of transport channels to physical channels for the 7.68 Mcps option..... | 138 |
+| 8.1 | Dedicated Transport Channels..... | 138 |
+| 8.1.1 | The Dedicated Channel (DCH)..... | 138 |
+| 8.1.2 | The Enhanced Uplink Dedicated Channel (E-DCH)..... | 138 |
+| 8.1.2.1 | E-DCH/E-AGCH Association and Timing..... | 138 |
+| 8.1.2.2 | E-DCH/E-HICH Association and Timing..... | 139 |
+| 8.2 | Common Transport Channels..... | 140 |
+| 8.2.1 | The Broadcast Channel (BCH)..... | 140 |
+| 8.2.2 | The Paging Channel (PCH)..... | 140 |
+| 8.2.3 | The Forward Channel (FACH)..... | 140 |
+| 8.2.4 | The Random Access Channel (RACH)..... | 140 |
+| 8.2.5 | The Uplink Shared Channel (USCH)..... | 140 |
+| 8.2.6 | The Downlink Shared Channel (DSCH)..... | 141 |
+| 8.2.7 | The High Speed Downlink Shared Channel (HS-DSCH)..... | 141 |
+| 8.2.7.1 | HS-DSCH/HS-SCCH Association and Timing..... | 141 |
+| 8.2.7.2 | HS-SCCH/HS-DSCH/HS-SICH Association and Timing..... | 141 |
+| Annex A (normative): | Basic Midamble Codes for the 3.84 Mcps option..... | 142 |
+| A.1 | Basic Midamble Codes for Burst Type 1 and 3..... | 142 |
+| A.2 | Basic Midamble Codes for Burst Type 2 and 4..... | 147 |
+| A.3 | Association between Midambles and Channelisation Codes..... | 150 |
+| A.3.1 | Association for Burst Type 1/3 and $K_{\text{Cell}}=16$ Midambles..... | 150 |
+| A.3.2 | Association for Burst Type 1/3 and $K_{\text{Cell}}=8$ Midambles..... | 151 |
+| A.3.3 | Association for Burst Type 1/3 and $K_{\text{Cell}}=4$ Midambles..... | 151 |
+| A.3.4 | Association for Burst Type 2 and $K_{\text{Cell}}=6$ Midambles..... | 152 |
+| A.3.5 | Association for Burst Type 2 and $K_{\text{Cell}}=3$ Midambles..... | 152 |
+| A.3.6 | Association for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble..... | 153 |
+| Annex AA (normative): | Basic Midamble Codes for the 1.28 Mcps option..... | 154 |
+| AA.1 | Basic Midamble Codes..... | 154 |
+| AA.2 | Association between Midambles and Channelisation Codes for default midamble allocation..... | 165 |
+| AA.2.1 | Association for $K=16$ Midambles..... | 165 |
+| AA.2.2 | Association for $K=14$ Midambles..... | 166 |
+| AA.2.3 | Association for $K=12$ Midambles..... | 166 |
+| AA.2.4 | Association for $K=10$ Midambles..... | 167 |
+| AA.2.5 | Association for $K=8$ Midambles..... | 167 |
+| AA.2.6 | Association for $K=6$ Midambles..... | 168 |
+| AA.2.7 | Association for $K=4$ Midambles..... | 168 |
+| AA.2.8 | Association for $K=2$ Midambles..... | 169 |
+| AA.3 | Association between Midambles and Channelisation Codes for special default midamble allocation..... | 169 |
+| AA.3.1 | Association for $K=16$ Midambles..... | 170 |
+| AA.3.2 | Association for $K=14$ Midambles..... | 173 |
+| AA.3.3 | Association for $K=12$ Midambles..... | 176 |
+| AA.3.4 | Association for $K=10$ Midambles..... | 179 |
+| AA.3.5 | Association for $K=8$ Midambles..... | 182 |
+
+| | | |
+|------------------------------|---------------------------------------------------------------------------------------------------------------|------------|
+| AA.3.6 | Association for K=6 Midambles..... | 185 |
+| AA.3.7 | Association for K=4 Midambles..... | 188 |
+| AA.3.8 | Association for K=2 Midambles..... | 191 |
+| Annex AB (normative): | Basic Midamble Codes for the 7.68 Mcps option..... | 192 |
+| AB.1 | Basic Midamble Codes for Burst Type 1 and 3..... | 192 |
+| AB.2 | Basic Midamble Codes for Burst Type 2..... | 200 |
+| AB.2A | Basic Midamble Codes for Burst Type 4..... | 201 |
+| AB.3 | Association between Midambles and Channelisation Codes..... | 206 |
+| AB.3.1 | Association for $K_{\text{Cell}} = 16$ Midambles..... | 206 |
+| AB.3.2 | Association for $K_{\text{Cell}} = 8$ Midambles..... | 207 |
+| AB.3.3 | Association for $K_{\text{Cell}} = 4$ Midambles..... | 208 |
+| AB.3.4 | Association for Burst Types 4 and $K_{\text{Cell}} = 1$ Midamble..... | 208 |
+| Annex B (normative): | Signalling of the number of channelisation codes for the DL common midamble case for 3.84Mcps TDD..... | 209 |
+| B.1 | Mapping scheme for Burst Type 1 and $K_{\text{Cell}} = 16$ Midambles..... | 209 |
+| B.2 | Mapping scheme for Burst Type 1 and $K_{\text{Cell}} = 8$ Midambles..... | 209 |
+| B.3 | Mapping scheme for Burst Type 1 and $K_{\text{Cell}} = 4$ Midambles..... | 210 |
+| B.4 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 16$ Midambles..... | 210 |
+| B.5 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 8$ Midambles..... | 211 |
+| B.6 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 4$ Midambles..... | 211 |
+| B.7 | Mapping scheme for Burst Type 2 and $K_{\text{Cell}} = 6$ Midambles..... | 211 |
+| B.8 | Mapping scheme for Burst Type 2 and $K_{\text{Cell}} = 3$ Midambles..... | 212 |
+| B.9 | Mapping scheme for Burst Type 4 and $K_{\text{Cell}} = 1$ Midamble..... | 212 |
+| Annex BA (normative): | Signalling of the number of channelisation codes for the DL common midamble case for 1.28Mcps TDD..... | 213 |
+| BA.1 | Mapping scheme for K=16 Midambles..... | 213 |
+| BA.2 | Mapping scheme for K=14 Midambles..... | 213 |
+| BA.3 | Mapping scheme for K=12 Midambles..... | 214 |
+| BA.4 | Mapping scheme for K=10 Midambles..... | 214 |
+| BA.5 | Mapping scheme for K=8 Midambles..... | 214 |
+| BA.6 | Mapping scheme for K=6 Midambles..... | 215 |
+| BA.7 | Mapping scheme for K=4 Midambles..... | 215 |
+| BA.8 | Mapping scheme for K=2 Midambles..... | 215 |
+| Annex BB (normative): | Signalling of the number of channelisation codes for the DL common midamble case for 7.68Mcps TDD..... | 216 |
+| BB.1 | Mapping scheme for $K_{\text{Cell}} = 16$ Midambles..... | 216 |
+| BB.2 | Mapping scheme for $K_{\text{Cell}} = 8$ Midambles..... | 216 |
+| BB.3 | Mapping scheme for $K_{\text{Cell}} = 4$ Midambles..... | 217 |
+| BB.4 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 16$ Midambles..... | 217 |
+| BB.5 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 8$ Midambles..... | 218 |
+
+| | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|
+| BB.6 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=4$ Midambles..... | 218 |
+| BB.7 Mapping scheme for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble..... | 218 |
+| Annex C (informative): CCPCH Multiframe Structure for the 3.84 Mcps option..... | 219 |
+| Annex CA (informative): CCPCH Multiframe Structure for the 1.28 Mcps option..... | 221 |
+| Annex CB (informative): Examples of the association of UL TPC commands to UL uplink time slots and CCTrCH pairs for 1.28 Mcps TDD..... | 222 |
+| Annex CC (informative): Examples of the association of UL SS commands to UL uplink time slots..... | 223 |
+| Annex CD (normative): T-CPICH bit sequences for the 3.84 Mcps MBSFN IMB option..... | 224 |
+| Annex D (informative): Change history..... | 230 |
+
+## Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+---
+
+# 1 Scope
+
+The present document describes the characteristics of the physical channels and the mapping of the transport channels to physical channels in the TDD 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.
+
+- [1] 3GPP TS 25.201: "Physical layer - general description".
+- [2] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".
+- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
+- [4] 3GPP TS 25.213: "Spreading and modulation (FDD)".
+- [5] 3GPP TS 25.214: "Physical layer procedures (FDD)".
+- [6] 3GPP TS 25.215: "Physical layer – Measurements (FDD)".
+- [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 TS 25.301: "Radio Interface Protocol Architecture".
+- [12] 3GPP TS 25.302: "Services Provided by the Physical Layer".
+- [13] 3GPP TS 25.401: "UTRAN Overall Description".
+- [14] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2".
+- [15] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode".
+- [16] 3GPP TS 25.427: "UTRAN Iur and Iub interface user plane protocols for DCH data streams".
+- [17] 3GPP TS 25.435: "UTRAN Iub Interface User Plane Protocols for Common Transport Channel Data Streams".
+- [18] 3GPP TS25.308: High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2
+- [19] 3GPP TS25.331: "RRC Protocol Specification ".
+
+## 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|----------------|------------------------------------------------------|
+| 16QAM | 16 Quadrature Amplitude Modulation |
+| BCH | Broadcast Channel |
+| CCPCH | Common Control Physical Channel |
+| CCTrCH | Coded Composite Transport Channel |
+| CDMA | Code Division Multiple Access |
+| CQI | Channel Quality Indicator |
+| DCH | Dedicated Channel |
+| DL | Downlink |
+| DPCH | Dedicated Physical Channel |
+| DRX | Discontinuous Reception |
+| DSCH | Downlink Shared Channel |
+| DTX | Discontinuous Transmission |
+| DwPCH | Downlink Pilot Channel |
+| DwPTS | Downlink Pilot Time Slot |
+| 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 |
+| E-UCCH | E-DCH Uplink Control Channel |
+| FACH | Forward Access Channel |
+| FDD | Frequency Division Duplex |
+| FEC | Forward Error Correction |
+| GP | Guard Period |
+| GSM | Global System for Mobile Communication |
+| HARQ | Hybrid ARQ |
+| 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 |
+| IMB | Integrated Mobile Broadcast |
+| MBSFN | MBMS over a Single Frequency Network |
+| MIB | Master Information Block |
+| MICH | MBMS Indicator Channel |
+| MIMO | single user Multiple Input Multiple Output |
+| MS burst | MBSFN Special burst |
+| MT burst | MBSFN Traffic burst |
+| MU-MIMO | Multi-User Multiple Input Multiple Output |
+| NI | MBMS Notification Indicator |
+| NRT | Non-Real Time |
+| OVSF | Orthogonal Variable Spreading Factor |
+| P-CCPCH | Primary CCPCH |
+| PCH | Paging Channel |
+| PDSCH | Physical Downlink Shared Channel |
+| PI | Paging Indicator (value calculated by higher layers) |
+| PICH | Page Indicator Channel |
+| PLCCH | Physical Layer Common Control Channel |
+| P q | Paging Indicator (indicator set by physical layer) |
+| PRACH | Physical Random Access Channel |
+| PUSCH | Physical Uplink Shared Channel |
+| RACH | Random Access Channel |
+| RF | Radio Frame |
+| RT | Real Time |
+| S-CCPCH | Secondary CCPCH |
+| SCH | Synchronisation Channel |
+| SCTD | Space Code Transmit Diversity |
+| SF | Spreading Factor |
+
+| | |
+|-------|-------------------------------------------|
+| SFN | Cell System Frame Number |
+| SS | Synchronisation Shift |
+| TCH | Traffic Channel |
+| TDD | Time Division Duplex |
+| TDMA | Time Division Multiple Access |
+| TFC | Transport Format Combination |
+| TFCI | Transport Format Combination Indicator |
+| TFI | Transport Format Indicator |
+| TPC | Transmitter Power Control |
+| TrCH | Transport Channel |
+| TSTD | Time Switched Transmit Diversity |
+| TTI | Transmission Time Interval |
+| UE | User Equipment |
+| UL | Uplink |
+| UMTS | Universal Mobil Telecommunications System |
+| UpPTS | Uplink Pilot Time Slot |
+| UpPCH | Uplink Pilot Channel |
+| USCH | Uplink Shared Channel |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+---
+
+## 4 Services offered to higher layers
+
+### 4.1 Transport channels
+
+Transport channels are the services offered by layer 1 to the higher layers. A transport channel is defined by how and with what characteristics data is transferred over the air interface. A general classification of transport channels is into two groups:
+
+- Dedicated Channels, using inherent addressing of UE
+- Common Channels, using explicit addressing of UE if addressing is needed
+
+General concepts about transport channels are described in [12].
+
+#### 4.1.1 Dedicated transport channels
+
+There exists two types of dedicated transport channel, the Dedicated Channel (DCH) and the Enhanced Dedicated Channel (E-DCH).
+
+##### 4.1.1.1 DCH – Dedicated Channel
+
+The Dedicated Channel (DCH) is an up- or downlink transport channel that is used to carry user or control information between the UTRAN and a UE.
+
+##### 4.1.1.2 E-DCH – Enhanced Dedicated Channel
+
+The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel.
+
+For 1.28Mcps TDD multi-carrier E-DCH transmission, a UE in CELL\_DCH state shall have only one E-DCH per carrier. There would be one or more E-DCHs to be transmitted from a UE in CELL\_DCH state in a TTI.
+
+#### 4.1.2 Common transport channels
+
+There are seven types of common transport channels for 3.84Mcps and 7.68Mcps TDD: BCH, FACH, PCH, RACH, USCH, DSCH, HS-DSCH.
+
+There are eight types of common transport channels for 1.28Mcps TDD: BCH, FACH, PCH, RACH, USCH, DSCH, HS-DSCH, E-DCH.
+
+#### 4.1.2.1 BCH – Broadcast Channel
+
+The Broadcast Channel (BCH) is a downlink transport channel that is used to broadcast system- and cell-specific information.
+
+#### 4.1.2.2 FACH – Forward Access Channel
+
+The Forward Access Channel (FACH) is a downlink transport channel that is used to carry control information to a mobile station when the system knows the location cell of the mobile station. The FACH may also carry short user packets.
+
+#### 4.1.2.3 PCH – Paging Channel
+
+The Paging Channel (PCH) is a downlink transport channel that is used to carry control information to a mobile station when the system does not know the location cell of the mobile station.
+
+#### 4.1.2.4 RACH – Random Access Channel
+
+The Random Access Channel (RACH) is an up link transport channel that is used to carry control information from mobile station. The RACH may also carry short user packets.
+
+#### 4.1.2.5 USCH – Uplink Shared Channel
+
+The uplink shared channel (USCH) is an uplink transport channel shared by several UEs carrying dedicated control or traffic data.
+
+#### 4.1.2.6 DSCH – Downlink Shared Channel
+
+The downlink shared channel (DSCH) is a downlink transport channel shared by several UEs carrying dedicated control or traffic data.
+
+#### 4.1.2.7 HS-DSCH – High Speed Downlink Shared Channel
+
+The High Speed Downlink Shared Channel (HS-DSCH) is a downlink transport channel shared by several UEs. The HS-DSCH is associated with one or several Shared Control Channels (HS-SCCH). The HS-DSCH is transmitted over the entire cell or over only part of the cell using e.g. beam-forming antennas.
+
+For 1.28Mcps TDD, in a multi-frequency HS-DSCH cell, the HS-DSCH may be transmitted to a UE on one or more carriers in CELL\_DCH state and on only one carrier in CELL\_FACH, CELL\_PCH and URA\_PCH state in a TTI. The term ‘multi-carrier HS-DSCH reception’ refers to the HS-DSCH reception on multiple carriers in a TTI for a UE.
+
+#### 4.1.2.8 E-DCH – Enhanced Dedicated Channel
+
+The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel in CELL\_FACH and IDLE mode for 1.28Mcps TDD only.
+
+## 4.2 Indicators
+
+Indicators are means of fast low-level signalling entities which are transmitted without using information blocks sent over transport channels. The meaning of indicators is implicit to the receiver.
+
+The indicator(s) defined in the current version of the specifications are: Paging Indicator (PI) and MBMS Notification Indicator (NI).
+
+---
+
+## 5 Physical channels for the 3.84 Mcps option
+
+Sub-clauses 5.1 to 5.7 do not apply to 3.84 Mcps MBSFN IMB. Sub-clause 5.8 describes physical channels for 3.84 Mcps MBSFN IMB.
+
+All physical channels take three-layer structure with respect to timeslots, radio frames and system frame numbering (SFN), see [14]. Depending on the resource allocation, the configuration of radio frames or timeslots becomes different. All physical channels need a guard period in every timeslot. The time slots are used in the sense of a TDMA component to separate different user signals in the time domain. The physical channel signal format is presented in figure 1.
+
+A physical channel in TDD is a burst, which is transmitted in a particular timeslot within allocated Radio Frames. The allocation can be continuous, i.e. the time slot in every frame is allocated to the physical channel or discontinuous, i.e. the time slot in a subset of all frames is allocated only. A burst is the combination of two data parts, a midamble part and a guard period. The duration of a burst is one time slot. Several bursts can be transmitted at the same time from one transmitter. In this case, the data parts must use different OVSF channelisation codes, but the same scrambling code. The midamble parts are either identically or differently shifted versions of a cell-specific basic midamble code, see section 5.2.3. Note when in MBSFN operation, a midamble is not necessarily cell-specific.
+
+
+
+Figure 1: Physical channel signal format. The diagram shows a 'Radio Frame (10ms)' containing two frames, 'frame #i' and 'frame #i+1'. A dashed line zooms into 'frame #i', showing it is divided into 15 'Time Slot (2560\*Tc)' units, with 'timeslot #0', 'timeslot #1', 'timeslot #2', 'timeslot #13', and 'timeslot #14' explicitly labeled.
+
+**Figure 1: Physical channel signal format**
+
+The data part of the burst is spread with a combination of channelisation code and scrambling code. The channelisation code is a OVSF code, that can have a spreading factor of 1, 2, 4, 8, or 16. The data rate of the physical channel is depending on the used spreading factor of the used OVSF code.
+
+The midamble part of the burst can contain two different types of midambles: a short one of length 256 chips, or a long one of 512 chips. The data rate of the physical channel is depending on the used midamble length. Additionally, when in MBSFN operation a midamble of length 320 chips is used.
+
+So a physical channel is defined by frequency, timeslot, channelisation code, burst type and Radio Frame allocation. The scrambling code and the basic midamble code are broadcast and may be constant within a cell. When a physical channel is established, a start frame is given. The physical channels can either be of infinite duration, or a duration for the allocation can be defined.
+
+## 5.1 Frame structure
+
+The TDMA frame has a duration of 10 ms and is subdivided into 15 time slots (TS) of $2560 \cdot T_c$ duration each. A time slot corresponds to 2560 chips. The physical content of the time slots are the bursts of corresponding length as described in subclause 5.2.2.
+
+Each 10 ms frame consists of 15 time slots, each allocated to either the uplink or the downlink (figure 2). With such a flexibility, the TDD mode can be adapted to different environments and deployment scenarios. In any configuration at least one time slot has to be allocated for the downlink and at least one time slot has to be allocated for the uplink with the exception of no uplink timeslots when the entire carrier is dedicated to MBSFN
+
+
+
+Figure 2: The TDD frame structure. The diagram shows a 10 ms frame divided into 15 time slots. The vertical axis is 'frequency' and the horizontal axis is 'time'. Each time slot has a duration of 2560\*Tc. The data rate is indicated as 3.84 Mchip/s.
+
+**Figure 2: The TDD frame structure**
+
+Examples for multiple and single switching point configurations as well as for symmetric and asymmetric UL/DL allocations are given in figure 3.
+
+
+
+10 ms
+
+Multiple-switching-point configuration (symmetric DL/UL allocation)
+
+10 ms
+
+Multiple-switching-point configuration (asymmetric DL/UL allocation)
+
+10 ms
+
+Single-switching-point configuration (symmetric DL/UL allocation)
+
+10 ms
+
+Single-switching-point configuration (asymmetric DL/UL allocation)
+
+10 ms
+
+Entire carrier dedicated to MBSFN
+
+Figure 3: TDD frame structure examples. The figure shows five examples of 10 ms TDD frames. Each frame is a horizontal sequence of 15 subframes. Downlink (DL) is represented by a downward arrow (↓) and uplink (UL) by an upward arrow (↑).
+
+Figure 3: TDD frame structure examples
+
+## 5.2 Dedicated physical channel (DPCH)
+
+The DCH as described in subclause 4.1.1 is mapped onto the dedicated physical channel.
+
+### 5.2.1 Spreading
+
+Spreading is applied to the data part of the physical channels and consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. Details on channelisation and scrambling operation can be found in [8].
+
+#### 5.2.1.1 Spreading for Downlink Physical Channels
+
+Downlink physical channels shall use SF = 16. Multiple parallel physical channels can be used to support higher data rates. These parallel physical channels shall be transmitted using different channelisation codes, see [8]. These codes with SF = 16 are generated as described in [8].
+
+Operation with a single code with spreading factor 1 is possible for the downlink physical channels.
+
+#### 5.2.1.2 Spreading for Uplink Physical Channels
+
+The range of spreading factor that may be used for uplink physical channels shall range from 16 down to 1. For each physical channel an individual minimum spreading factor $SF_{min}$ is transmitted by means of the higher layers. There are two options that are indicated by UTRAN:
+
+1. The UE shall use the spreading factor $SF_{min}$ , independent of the current TFC.
+2. The UE shall autonomously increase the spreading factor depending on the current TFC.
+
+If the UE autonomously changes the SF, it shall always vary the channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree, as depicted in [8]. In the event that code hopping is configured by higher layers, the allowed OVSF sub-tree is that subtended by the effective allocated OVSF code after the hop sequence has been applied to the allocated OVSF code (see [9]).
+
+For multicode transmission a UE shall use a maximum of two physical channels per timeslot simultaneously. These two parallel physical channels shall be transmitted using different channelisation codes, see [8].
+
+## 5.2.2 Burst Types
+
+Four types of bursts for dedicated physical channels are defined. All of them consist of two data symbol fields, a midamble and a guard period, the lengths of which are different for the individual burst types. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 1.
+
+**Table 1: Number of data symbols (N) for burst types 1, 2, 3 and 4**
+
+| Spreading factor (SF) | Burst Type 1 | Burst Type 2 | Burst Type 3 | Burst Type 4 |
+|-----------------------|--------------|--------------|--------------|--------------|
+| 1 | 1952 | 2208 | 1856 | 2112 |
+| 2 | 976 | 1104 | 928 | N/A |
+| 4 | 488 | 552 | 464 | N/A |
+| 8 | 244 | 276 | 232 | N/A |
+| 16 | 122 | 138 | 116 | 132 |
+
+The support of burst types 1, 2 and 3 is mandatory for UEs supporting transmit and receive functions. UEs supporting transmit and receive functions and also MBSFN operation must additionally support burst type 4. UEs with receive only capability need only support burst type 4. The four different bursts defined here are well suited for different applications, as described in the following sections.
+
+### 5.2.2.1 Burst Type 1
+
+The burst type 1 can be used for uplink and downlink. Due to its longer midamble field this burst type supports the construction of a larger number of training sequences, see 5.2.3. The maximum number of training sequences depend on the cell configuration, see annex A. For the burst type 1 this number may be 4, 8, or 16.
+
+The data fields of the burst type 1 are 976 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 1 above. The midamble of burst type 1 has a length of 512 chips. The guard period for the burst type 1 is 96 chip periods long. The burst type 1 is shown in Figure 4. The contents of the burst fields are described in table 2.
+
+**Table 2: The contents of the burst type 1 fields**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-975 | 976 | Cf table 1 | | Data symbols |
+| 976-1487 | 512 | - | | Midamble |
+| 1488-2463 | 976 | Cf table 1 | | Data symbols |
+| 2464-2559 | 96 | - | | Guard period |
+
+
+
+The diagram illustrates the structure of a Burst Type 1. It consists of four contiguous fields:
+
+
+- Data symbols:** 976 chips
+- Midamble:** 512 chips
+- Data symbols:** 976 chips
+- GP (Guard Period):** 96 CP (chip periods)
+
+ The total length of the burst is indicated as $2560 \cdot T_c$ with a double-headed arrow spanning the entire structure.
+
+Diagram of Burst Type 1 structure showing four fields: Data symbols (976 chips), Midamble (512 chips), Data symbols (976 chips), and GP (96 CP). The total length is 2560\*Tc.
+
+**Figure 4: Burst structure of the burst type 1. GP denotes the guard period and CP the chip periods**
+
+### 5.2.2.2 Burst Type 2
+
+The burst type 2 can be used for uplink and downlink. It offers a longer data field than burst type 1 on the cost of a shorter midamble. Due to the shorter midamble field the burst type 2 supports a maximum number of training sequences of 3 or 6 only, depending on the cell configuration, see annex A.
+
+The data fields of the burst type 2 are 1104 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 1 above. The guard period for the burst type 2 is 96 chip periods long. The burst type 2 is shown in Figure 5. The contents of the burst fields are described in table 3.
+
+Table 3: The contents of the burst type 2 fields
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-1103 | 1104 | cf table 1 | | Data symbols |
+| 1104-1359 | 256 | - | | Midamble |
+| 1360-2463 | 1104 | cf table 1 | | Data symbols |
+| 2464-2559 | 96 | - | | Guard period |
+
+
+
+Figure 5: Burst structure of the burst type 2. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1104 chips', 'Midamble 256 chips', 'Data symbols 1104 chips', and 'GP 96 CP'. Below the bar, a double-headed arrow spans the entire length, labeled '2560\*Tc'.
+
+Figure 5: Burst structure of the burst type 2. GP denotes the guard period and CP the chip periods
+
+### 5.2.2.3 Burst Type 3
+
+The burst type 3 is used for uplink only. Due to the longer guard period it is suitable for initial access or access to a new cell after handover. It offers the same number of training sequences as burst type 1.
+
+The data fields of the burst type 3 have a length of 976 chips and 880 chips, respectively. The corresponding number of symbols depends on the spreading factor, as indicated in table 1 above. The midamble of burst type 3 has a length of 512 chips. The guard period for the burst type 3 is 192 chip periods long. The burst type 3 is shown in Figure 6. The contents of the burst fields are described in table 4.
+
+Table 4: The contents of the burst type 3 fields
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-975 | 976 | Cf table 1 | | Data symbols |
+| 976-1487 | 512 | - | | Midamble |
+| 1488-2367 | 880 | Cf table 1 | | Data symbols |
+| 2368-2559 | 192 | - | | Guard period |
+
+
+
+Figure 6: Burst structure of the burst type 3. The diagram shows a horizontal bar divided into four segments: 'Data symbols 976 chips', 'Midamble 512 chips', 'Data symbols 880 chips', and 'GP 192 CP'. Below the bar, a double-headed arrow spans the entire length, labeled '2560\*Tc'.
+
+Figure 6: Burst structure of the burst type 3. GP denotes the guard period and CP the chip periods
+
+### 5.2.2.3A Burst Type 4
+
+The burst type 4 is used for downlink MBSFN operation only and supports a single training sequence.
+
+The data fields of the burst type 4 are 1056 chips long. The corresponding number of symbols is 132 as indicated in table 1 above. The midamble of burst type 4 has a length of 320 chips. The guard period for the burst type 4 is 128 chip periods long. The burst type 4 is shown in Figure 6A. The contents of the burst fields are described in table 4A.
+
+**Table 4A: The contents of the burst type 4 fields**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-1055 | 1056 | Cf table 1 | | Data symbols |
+| 1056-1375 | 320 | - | | Midamble |
+| 1376-2431 | 1056 | Cf table 1 | | Data symbols |
+| 2432-2559 | 128 | - | | Guard period |
+
+
+
+Figure 6A: Burst structure of the burst type 4. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1056 chips', 'Midamble 320 chips', 'Data symbols 1056 chips', and 'GP 128 CP'. Below the bar, a double-headed arrow indicates a total length of 2560\*Tc.
+
+**Figure 6A: Burst structure of the burst type 4. GP denotes the guard period and CP the chip periods**
+
+### 5.2.2.4 Transmission of TFCI
+
+All burst types 1, 2, 3 and 4 provide the possibility for transmission of TFCI.
+
+The transmission of TFCI is negotiated at call setup and can be re-negotiated during the call. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied, except for the MBSFN FACH where the (16,5) bi-orthogonal code is always used for TFCI when TFCI is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (*p*) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+The transmission of TFCI is done in the data parts of the respective physical channel. In DL the TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. In DL, the modulation applied to the TFCI code word bits is the same as that applied to the data symbols. In UL, independent of the SF that is applied to the data symbols in the burst, the data in the TFCI field are always spread with SF=16 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TFCI code word is to be transmitted directly adjacent to the midamble, possibly after the TPC. Figure 7 shows the position of the TFCI code word in a traffic burst in downlink. Figure 8 shows the position of the TFCI code word in a traffic burst in uplink.
+
+
+
+Figure 7: Position of the TFCI code word in the traffic burst in case of downlink. The diagram shows a horizontal bar with segments: 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. Above the 'Midamble' segment, two labels '1st part of TFCI code word' and '2nd part of TFCI code word' point to its beginning and end respectively. Below the 'Midamble' segment, a double-headed arrow indicates its length as 512/320/256 chips. Below the entire bar, another double-headed arrow indicates a total length of 2560\*Tc.
+
+**Figure 7: Position of the TFCI code word in the traffic burst in case of downlink**
+
+
+
+Figure 8: Position of the TFCI code word in the traffic burst in case of uplink. The diagram shows a traffic burst structure with fields: Data symbols, Midamble, TFCI, Data symbols, and GP. The TFCI is split into two parts: the 1st part is located at the beginning of the second Midamble section, and the 2nd part is located at the end of the second Midamble section. The total length of the burst is 2560\*Tc. The length of the Midamble section is 512/256 chips.
+
+Figure 8: Position of the TFCI code word in the traffic burst in case of uplink
+
+Two examples of TFCI transmission in the case of multiple DPCHs used for a connection are given in the Figure 9 and Figure 10 below. Combinations of the two schemes shown are also applicable.
+
+
+
+Figure 9: Example of TFCI transmission with physical channels multiplexed in code domain. The diagram shows three horizontal bars representing different codes over time (t). The top bar has a grey section (Midamble) and a dark grey section (TFCI). The middle bar has a grey section (Midamble) and a dark grey section (TFCI). The bottom bar has a grey section (Midamble) and a dark grey section (TFCI). A legend indicates: Data (white), Midamble (grey), TFCI (dark grey). The total duration is 2560\*Tc.
+
+Figure 9: Example of TFCI transmission with physical channels multiplexed in code domain
+
+
+
+Figure 10: Example of TFCI transmission with physical channels multiplexed in time domain. The diagram shows three horizontal bars representing different codes over time (t). The top bar has a grey section (Midamble) and a dark grey section (TFCI). The middle bar has a grey section (Midamble) and a dark grey section (TFCI). The bottom bar has a grey section (Midamble) and a dark grey section (TFCI). A legend indicates: Data (white), Midamble (grey), TFCI (dark grey). The total duration is 2560\*Tc.
+
+Figure 10: Example of TFCI transmission with physical channels multiplexed in time domain
+
+In case the Node B receives an invalid TFI combination on the DCHs mapped to one CCTrCH the procedure described in [16] shall be applied. According to this procedure DTX shall be applied to all DPCHs to which the CCTrCH is mapped to.
+
+### 5.2.2.5 Transmission of TPC
+
+Burst types 1, 2 and 3 for dedicated channels provide the possibility for transmission of TPC in uplink.
+
+The transmission of TPC is done in the data parts of the traffic burst. Independent of the SF that is applied to the data symbols in the burst, the data in the TPC field are always spread with SF=16 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the midamble. Figure 11 shows the position of the TPC in a traffic burst.
+
+For every user the TPC information shall be transmitted at least once per transmitted frame. If a TFCI is applied for a CCTrCH, TPC shall be transmitted with the same channelization codes and in the same timeslots as the TFCI. If no TFCI is applied for a CCTrCH, TPC shall be transmitted using the physical channel corresponding to physical channel
+
+sequence number $p=1$ . Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+
+
+The diagram illustrates the structure of a traffic burst. It consists of five segments: 'Data symbols', 'Midamble', 'TPC field', 'Data symbols', and 'GP'. The 'TPC field' is a small, hatched portion within the 'Midamble' segment. A double-headed arrow below the 'Midamble' segment indicates its length as '512/256 chips'. A longer double-headed arrow at the bottom indicates the total length of the burst as '2560\*Tc'.
+
+Diagram of a traffic burst structure showing Data symbols, Midamble, TPC field, Data symbols, and GP. The total length is 2560\*Tc, and the Midamble length is 512/256 chips.
+
+**Figure 11: Position of TPC information in the traffic burst**
+
+The length of the TPC field is $N_{TPC}$ bits. The TPC field is formed via repetition encoding a single bit $b_{TPC}$ , $N_{TPC}$ times.
+
+The relationship between $b_{TPC}$ and the TPC command is shown in table 4B.
+
+**Table 4B: TPC bit pattern**
+
+| $b_{TPC}$ | TPC command | Meaning |
+|-----------|-------------|-------------------|
+| 0 | 'Down' | Decrease Tx Power |
+| 1 | 'Up' | Increase Tx Power |
+
+## 5.2.2.6 Timeslot formats
+
+### 5.2.2.6.1 Downlink timeslot formats
+
+The downlink timeslot format depends on the spreading factor, midamble length and on the number of the TFCI code word bits, as depicted in the table 5a. For MBSFN operation the timeslot format also depends upon the symbol modulation scheme used. Slot formats 20-27 are only applicable to MBSFN operation with burst type 4.
+
+Table 5a: Time slot formats for the Downlink
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------|
+| 0 | 16 | 512 | 0 | 244 | 244 | 122 |
+| 1 | 16 | 512 | 4 | 244 | 240 | 120 |
+| 2 | 16 | 512 | 8 | 244 | 236 | 118 |
+| 3 | 16 | 512 | 16 | 244 | 228 | 114 |
+| 4 | 16 | 512 | 32 | 244 | 212 | 106 |
+| 5 | 16 | 256 | 0 | 276 | 276 | 138 |
+| 6 | 16 | 256 | 4 | 276 | 272 | 136 |
+| 7 | 16 | 256 | 8 | 276 | 268 | 134 |
+| 8 | 16 | 256 | 16 | 276 | 260 | 130 |
+| 9 | 16 | 256 | 32 | 276 | 244 | 122 |
+| 10 | 1 | 512 | 0 | 3904 | 3904 | 1952 |
+| 11 | 1 | 512 | 4 | 3904 | 3900 | 1950 |
+| 12 | 1 | 512 | 8 | 3904 | 3896 | 1948 |
+| 13 | 1 | 512 | 16 | 3904 | 3888 | 1944 |
+| 14 | 1 | 512 | 32 | 3904 | 3872 | 1936 |
+| 15 | 1 | 256 | 0 | 4416 | 4416 | 2208 |
+| 16 | 1 | 256 | 4 | 4416 | 4412 | 2206 |
+| 17 | 1 | 256 | 8 | 4416 | 4408 | 2204 |
+| 18 | 1 | 256 | 16 | 4416 | 4400 | 2200 |
+| 19 | 1 | 256 | 32 | 4416 | 4384 | 2192 |
+| 20 (QPSK) | 16 | 320 | 0 | 264 | 264 | 132 |
+| 21 (QPSK) | 16 | 320 | 16 | 264 | 248 | 124 |
+| 22 (16QAM) | 16 | 320 | 0 | 528 | 528 | 264 |
+| 23 (16QAM) | 16 | 320 | 16 | 528 | 512 | 256 |
+| 24 (QPSK) | 1 | 320 | 0 | 4224 | 4224 | 2112 |
+| 25 (QPSK) | 1 | 320 | 16 | 4224 | 4208 | 2104 |
+| 26 (16QAM) | 1 | 320 | 0 | 8448 | 8448 | 4224 |
+| 27 (16QAM) | 1 | 320 | 16 | 8448 | 8432 | 4216 |
+
+#### 5.2.2.6.2 Uplink timeslot formats
+
+The uplink timeslot format depends on the spreading factor, midamble length, guard period length and on the number of the TFCI code word bits. Due to TPC, different amount of bits are mapped to the two data fields. The timeslot formats are depicted in the table 5b. Note that slot format #90 shall only be used for HS\_SICH.
+
+**Table 5b: Timeslot formats for the Uplink**
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 | 16 | 512 | 96 | 0 | 0 | 244 | 244 | 122 | 122 |
+| 1 | 16 | 512 | 96 | 0 | 2 | 244 | 242 | 122 | 120 |
+| 2 | 16 | 512 | 96 | 4 | 2 | 244 | 238 | 120 | 118 |
+| 3 | 16 | 512 | 96 | 8 | 2 | 244 | 234 | 118 | 116 |
+| 4 | 16 | 512 | 96 | 16 | 2 | 244 | 226 | 114 | 112 |
+| 5 | 16 | 512 | 96 | 32 | 2 | 244 | 210 | 106 | 104 |
+| 6 | 16 | 256 | 96 | 0 | 0 | 276 | 276 | 138 | 138 |
+| 7 | 16 | 256 | 96 | 0 | 2 | 276 | 274 | 138 | 136 |
+| 8 | 16 | 256 | 96 | 4 | 2 | 276 | 270 | 136 | 134 |
+| 9 | 16 | 256 | 96 | 8 | 2 | 276 | 266 | 134 | 132 |
+| 10 | 16 | 256 | 96 | 16 | 2 | 276 | 258 | 130 | 128 |
+| 11 | 16 | 256 | 96 | 32 | 2 | 276 | 242 | 122 | 120 |
+| 12 | 8 | 512 | 96 | 0 | 0 | 488 | 488 | 244 | 244 |
+| 13 | 8 | 512 | 96 | 0 | 2 | 486 | 484 | 244 | 240 |
+| 14 | 8 | 512 | 96 | 4 | 2 | 482 | 476 | 240 | 236 |
+| 15 | 8 | 512 | 96 | 8 | 2 | 478 | 468 | 236 | 232 |
+| 16 | 8 | 512 | 96 | 16 | 2 | 470 | 452 | 228 | 224 |
+| 17 | 8 | 512 | 96 | 32 | 2 | 454 | 420 | 212 | 208 |
+| 18 | 8 | 256 | 96 | 0 | 0 | 552 | 552 | 276 | 276 |
+| 19 | 8 | 256 | 96 | 0 | 2 | 550 | 548 | 276 | 272 |
+| 20 | 8 | 256 | 96 | 4 | 2 | 546 | 540 | 272 | 268 |
+| 21 | 8 | 256 | 96 | 8 | 2 | 542 | 532 | 268 | 264 |
+| 22 | 8 | 256 | 96 | 16 | 2 | 534 | 516 | 260 | 256 |
+| 23 | 8 | 256 | 96 | 32 | 2 | 518 | 484 | 244 | 240 |
+| 24 | 4 | 512 | 96 | 0 | 0 | 976 | 976 | 488 | 488 |
+| 25 | 4 | 512 | 96 | 0 | 2 | 970 | 968 | 488 | 480 |
+| 26 | 4 | 512 | 96 | 4 | 2 | 958 | 952 | 480 | 472 |
+| 27 | 4 | 512 | 96 | 8 | 2 | 946 | 936 | 472 | 464 |
+| 28 | 4 | 512 | 96 | 16 | 2 | 922 | 904 | 456 | 448 |
+| 29 | 4 | 512 | 96 | 32 | 2 | 874 | 840 | 424 | 416 |
+| 30 | 4 | 256 | 96 | 0 | 0 | 1104 | 1104 | 552 | 552 |
+| 31 | 4 | 256 | 96 | 0 | 2 | 1098 | 1096 | 552 | 544 |
+| 32 | 4 | 256 | 96 | 4 | 2 | 1086 | 1080 | 544 | 536 |
+| 33 | 4 | 256 | 96 | 8 | 2 | 1074 | 1064 | 536 | 528 |
+| 34 | 4 | 256 | 96 | 16 | 2 | 1050 | 1032 | 520 | 512 |
+| 35 | 4 | 256 | 96 | 32 | 2 | 1002 | 968 | 488 | 480 |
+| 36 | 2 | 512 | 96 | 0 | 0 | 1952 | 1952 | 976 | 976 |
+| 37 | 2 | 512 | 96 | 0 | 2 | 1938 | 1936 | 976 | 960 |
+| 38 | 2 | 512 | 96 | 4 | 2 | 1910 | 1904 | 960 | 944 |
+| 39 | 2 | 512 | 96 | 8 | 2 | 1882 | 1872 | 944 | 928 |
+| 40 | 2 | 512 | 96 | 16 | 2 | 1826 | 1808 | 912 | 896 |
+| 41 | 2 | 512 | 96 | 32 | 2 | 1714 | 1680 | 848 | 832 |
+| 42 | 2 | 256 | 96 | 0 | 0 | 2208 | 2208 | 1104 | 1104 |
+| 43 | 2 | 256 | 96 | 0 | 2 | 2194 | 2192 | 1104 | 1088 |
+| 44 | 2 | 256 | 96 | 4 | 2 | 2166 | 2160 | 1088 | 1072 |
+| 45 | 2 | 256 | 96 | 8 | 2 | 2138 | 2128 | 1072 | 1056 |
+| 46 | 2 | 256 | 96 | 16 | 2 | 2082 | 2064 | 1040 | 1024 |
+| 47 | 2 | 256 | 96 | 32 | 2 | 1970 | 1936 | 976 | 960 |
+| 48 | 1 | 512 | 96 | 0 | 0 | 3904 | 3904 | 1952 | 1952 |
+| 49 | 1 | 512 | 96 | 0 | 2 | 3874 | 3872 | 1952 | 1920 |
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 50 | 1 | 512 | 96 | 4 | 2 | 3814 | 3808 | 1920 | 1888 |
+| 51 | 1 | 512 | 96 | 8 | 2 | 3754 | 3744 | 1888 | 1856 |
+| 52 | 1 | 512 | 96 | 16 | 2 | 3634 | 3616 | 1824 | 1792 |
+| 53 | 1 | 512 | 96 | 32 | 2 | 3394 | 3360 | 1696 | 1664 |
+| 54 | 1 | 256 | 96 | 0 | 0 | 4416 | 4416 | 2208 | 2208 |
+| 55 | 1 | 256 | 96 | 0 | 2 | 4386 | 4384 | 2208 | 2176 |
+| 56 | 1 | 256 | 96 | 4 | 2 | 4326 | 4320 | 2176 | 2144 |
+| 57 | 1 | 256 | 96 | 8 | 2 | 4266 | 4256 | 2144 | 2112 |
+| 58 | 1 | 256 | 96 | 16 | 2 | 4146 | 4128 | 2080 | 2048 |
+| 59 | 1 | 256 | 96 | 32 | 2 | 3906 | 3872 | 1952 | 1920 |
+| 60 | 16 | 512 | 192 | 0 | 0 | 232 | 232 | 122 | 110 |
+| 61 | 16 | 512 | 192 | 0 | 2 | 232 | 230 | 122 | 108 |
+| 62 | 16 | 512 | 192 | 4 | 2 | 232 | 226 | 120 | 106 |
+| 63 | 16 | 512 | 192 | 8 | 2 | 232 | 222 | 118 | 104 |
+| 64 | 16 | 512 | 192 | 16 | 2 | 232 | 214 | 114 | 100 |
+| 65 | 16 | 512 | 192 | 32 | 2 | 232 | 198 | 106 | 92 |
+| 66 | 8 | 512 | 192 | 0 | 0 | 464 | 464 | 244 | 220 |
+| 67 | 8 | 512 | 192 | 0 | 2 | 462 | 460 | 244 | 216 |
+| 68 | 8 | 512 | 192 | 4 | 2 | 458 | 452 | 240 | 212 |
+| 69 | 8 | 512 | 192 | 8 | 2 | 454 | 444 | 236 | 208 |
+| 70 | 8 | 512 | 192 | 16 | 2 | 446 | 428 | 228 | 200 |
+| 71 | 8 | 512 | 192 | 32 | 2 | 430 | 396 | 212 | 184 |
+| 72 | 4 | 512 | 192 | 0 | 0 | 928 | 928 | 488 | 440 |
+| 73 | 4 | 512 | 192 | 0 | 2 | 922 | 920 | 488 | 432 |
+| 74 | 4 | 512 | 192 | 4 | 2 | 910 | 904 | 480 | 424 |
+| 75 | 4 | 512 | 192 | 8 | 2 | 898 | 888 | 472 | 416 |
+| 76 | 4 | 512 | 192 | 16 | 2 | 874 | 856 | 456 | 400 |
+| 77 | 4 | 512 | 192 | 32 | 2 | 826 | 792 | 424 | 368 |
+| 78 | 2 | 512 | 192 | 0 | 0 | 1856 | 1856 | 976 | 880 |
+| 79 | 2 | 512 | 192 | 0 | 2 | 1842 | 1840 | 976 | 864 |
+| 80 | 2 | 512 | 192 | 4 | 2 | 1814 | 1808 | 960 | 848 |
+| 81 | 2 | 512 | 192 | 8 | 2 | 1786 | 1776 | 944 | 832 |
+| 82 | 2 | 512 | 192 | 16 | 2 | 1730 | 1712 | 912 | 800 |
+| 83 | 2 | 512 | 192 | 32 | 2 | 1618 | 1584 | 848 | 736 |
+| 84 | 1 | 512 | 192 | 0 | 0 | 3712 | 3712 | 1952 | 1760 |
+| 85 | 1 | 512 | 192 | 0 | 2 | 3682 | 3680 | 1952 | 1728 |
+| 86 | 1 | 512 | 192 | 4 | 2 | 3622 | 3616 | 1920 | 1696 |
+| 87 | 1 | 512 | 192 | 8 | 2 | 3562 | 3552 | 1888 | 1664 |
+| 88 | 1 | 512 | 192 | 16 | 2 | 3442 | 3424 | 1824 | 1600 |
+| 89 | 1 | 512 | 192 | 32 | 2 | 3202 | 3168 | 1696 | 1472 |
+| 90 | 16 | 512 | 96 | 0 | 8 | 244 | 236 | 122 | 114 |
+
+### 5.2.3 Training sequences for spread bursts
+
+In this subclause, the training sequences for usage as midambles in burst type 1, 2, 3 and 4 (see subclause 5.2.2) are defined. The training sequences, i.e. midambles, of different users active in the same cell and same time slot are cyclically shifted versions of one cell-specific single basic midamble code. In the case of MBSFN timeslots there is only a single midamble and this is derived from a single basic midamble code which is not necessarily cell-specific. The applicable basic midamble codes are given in Annex A.1 and A.2. As different basic midamble codes are required for different burst formats, the Annex A.1 shows the basic midamble codes $m_{PL}$ for burst type 1 and 3, and Annex A.2
+
+shows $\mathbf{m}_{\text{PS}}$ for burst types 2 and 4. It should be noted that burst type 2 must not be mixed with burst type 1 or 3 in the same timeslot of one cell and furthermore burst type 4 shall not be mixed with any other burst type in the same timeslot of one cell.
+
+The basic midamble codes in Annex A.1 and A.2 are listed in hexadecimal notation. The binary form of the basic midamble code shall be derived according to table 6 below.
+
+**Table 6: Mapping of 4 binary elements $m_i$ on a single hexadecimal digit**
+
+| 4 binary elements
$m_i$ | Mapped on hexadecimal digit |
+|----------------------------|-----------------------------|
+| -1 -1 -1 -1 | 0 |
+| -1 -1 -1 1 | 1 |
+| -1 -1 1 -1 | 2 |
+| -1 -1 1 1 | 3 |
+| -1 1 -1 -1 | 4 |
+| -1 1 -1 1 | 5 |
+| -1 1 1 -1 | 6 |
+| -1 1 1 1 | 7 |
+| 1 -1 -1 -1 | 8 |
+| 1 -1 -1 1 | 9 |
+| 1 -1 1 -1 | A |
+| 1 -1 1 1 | B |
+| 1 1 -1 -1 | C |
+| 1 1 -1 1 | D |
+| 1 1 1 -1 | E |
+| 1 1 1 1 | F |
+
+For each particular basic midamble code, its binary representation can be written as a vector $\mathbf{m}_P$ :
+
+$$\mathbf{m}_P = (m_1, m_2, \dots, m_P) \quad (1)$$
+
+According to Annex A.1, the size of this vector $\mathbf{m}_P$ is $P=456$ for burst types 1 and 3. Annex A.2 is setting $P=192$ for burst types 2 and 4. As QPSK modulation is used, the training sequences are transformed into a complex form, denoted as the complex vector $\underline{\mathbf{m}}_P$ :
+
+$$\underline{\mathbf{m}}_P = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_P) \quad (2)$$
+
+The elements $\underline{m}_i$ of $\underline{\mathbf{m}}_P$ are derived from elements $m_i$ of $\mathbf{m}_P$ using equation (3):
+
+$$\underline{m}_i = (j)^i \cdot m_i \text{ for all } i = 1, \dots, P \quad (3)$$
+
+Hence, the elements $\underline{m}_i$ of the complex basic midamble code are alternating real and imaginary.
+
+To derive the required training sequences (different shifts), this vector $\underline{\mathbf{m}}_P$ is periodically extended to the size:
+
+$$i_{\max} = L_m + (K' - 1)W + \lfloor P/K \rfloor \quad (4)$$
+
+Notes on equation (4):
+
+- $L_m$ : Midamble length
+- $K'$ : Maximum number of different midamble shifts in a cell, when no intermediate shifts are used. This value depends on the midamble length.
+
+- K: Maximum number of different midamble shifts in a cell, when intermediate shifts are used, $K=2K'$ .
+
+This value depends on the midamble length.
+
+Note that intermediate shifts are not used for burst type 4, i.e $K=K'=1$ for burst type 4
+
+- W: Shift between the midambles, when the number of midambles is $K'$ .
+- $\lfloor x \rfloor$ denotes the largest integer smaller or equal to x
+
+Allowed values for $L_m$ , $K'$ and W are given in Annex A.1 and A.2.
+
+So we obtain a new vector $\underline{m}$ containing the periodic basic midamble sequence:
+
+$$\underline{m} = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{i_{\max}}) = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{L_m + (K'-1)W + \lfloor P/K \rfloor}) \quad (5)$$
+
+The first P elements of this vector $\underline{m}$ are the same ones as in vector $\underline{m}^P$ , the following elements repeat the beginning:
+
+$$\underline{m}_i = \underline{m}_{i-P} \text{ for the subset } i = (P+1), \dots, i_{\max} \quad (6)$$
+
+Using this periodic basic midamble sequence $\underline{m}$ for each shift k a midamble $\underline{m}^{(k)}$ of length $L_m$ is derived, which can be written as a shift specific vector:
+
+$$\underline{m}^{(k)} = (\underline{m}_1^{(k)}, \underline{m}_2^{(k)}, \dots, \underline{m}_{L_m}^{(k)}) \quad (7)$$
+
+The $L_m$ midamble elements $\underline{m}_i^{(k)}$ are generated for each midamble of the first $K'$ shifts ( $k = 1, \dots, K'$ ) based on:
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-k)W} \text{ with } i = 1, \dots, L_m \text{ and } k = 1, \dots, K' \quad (8)$$
+
+The elements of midambles for the second $K'$ shifts ( $k = (K'+1), \dots, K = (K'+1), \dots, 2K'$ ) are generated based on a slight modification of this formula introducing intermediate shifts:
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K-k-1)W + \lfloor P/K \rfloor} \text{ with } i = 1, \dots, L_m \text{ and } k = K'+1, \dots, K-1 \quad (9)$$
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-1)W + \lfloor P/K \rfloor} \text{ with } i = 1, \dots, L_m \text{ and } k = K \quad (10)$$
+
+The number $K_{\text{Cell}}$ of midambles that is supported in each cell can be smaller than K, depending on the cell size and the possible delay spreads, see annex A. The number $K_{\text{Cell}}$ is signalled by higher layers. The midamble sequences derived according to equations (7) to (10) have complex values and are not subject to channelisation or scrambling process, i.e.
+
+the elements $\underline{m}_i^{(k)}$ represent complex chips for usage in the pulse shaping process at modulation.
+
+The term 'a midamble code set' or 'a midamble code family' denotes K specific midamble codes $\underline{m}^{(k)}$ ; $k=1, \dots, K$ , based on a single basic midamble code $\underline{m}^P$ according to (1).
+
+## 5.2.4 Beamforming
+
+When DL beamforming is used, at least that user to which beamforming is applied and which has a dedicated channel shall get one individual midamble according to subclause 5.2.3, even in DL. DL beamforming is not applied to timeslots containing burst type 4.
+
+## 5.3 Common physical channels
+
+### 5.3.1 Primary common control physical channel (P-CCPCH)
+
+The BCH as described in subclause 4.1.2 is mapped onto the Primary Common Control Physical Channel (P-CCPCH). The position (time slot / code) of the P-CCPCH is known from the Physical Synchronisation Channel (PSCH), see subclause 5.3.4.
+
+#### 5.3.1.1 P-CCPCH Spreading
+
+The P-CCPCH uses fixed spreading with a spreading factor $SF = 16$ as described in subclause 5.2.1.1. The P-CCPCH always uses channelisation code $c_{Q=16}^{(k=1)}$ .
+
+#### 5.3.1.2 P-CCPCH Burst Types
+
+The burst type 1 as described in subclause 5.2.2 is used for the P-CCPCH unless the entire carrier is dedicated to MBMSFN then burst type 4 is used for P-CCPCH. No TFCI is applied for the P-CCPCH.
+
+#### 5.3.1.3 P-CCPCH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5.2.3 are used for the P-CCPCH.
+
+### 5.3.2 Secondary common control physical channel (S-CCPCH)
+
+PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements.
+
+#### 5.3.2.1 S-CCPCH Spreading
+
+The S-CCPCH uses fixed spreading with a spreading factor $SF = 16$ as described in subclause 5.2.1.1. When S-CCPCH is used for MBMSFN operation the spreading factor may be $SF = 16$ or $SF = 1$ .
+
+#### 5.3.2.2 S-CCPCH Burst Types
+
+The burst types 1,2 or 4 as described in subclause 5.2.2 are used for the S-CCPCHs. TFCI may be applied for S-CCPCHs.
+
+#### 5.3.2.2A S-CCPCH Modulation
+
+When S-CCPCH is used for MBMSFN operation, burst type 4 shall be used and the modulation may be QPSK or 16QAM, see table 5A for slot formats. When S-CCPCH is used for all other purposes the modulation shall be QPSK.
+
+#### 5.3.2.3 S-CCPCH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5.2.3 are used for the S-CCPCH.
+
+### 5.3.3 The physical random access channel (PRACH)
+
+The RACH as described in subclause 4.1.2 is mapped onto one uplink physical random access channel (PRACH).
+
+#### 5.3.3.1 PRACH Spreading
+
+The uplink PRACH uses either spreading factor $SF=16$ or $SF=8$ as described in subclause 5.2.1.2. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH).
+
+#### 5.3.3.2 PRACH Burst Type
+
+The UEs send uplink access bursts of type 3 randomly in the PRACH. TFCI and TPC are not applied for the PRACH.
+
+### 5.3.3.3 PRACH Training sequences
+
+The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a single periodic basic code. The basic midamble codes for burst type 3 are shown in Annex A. The necessary time shifts are obtained by choosing either *all* $k=1,2,3,\dots,K'$ (for cells with small radius) or *uneven* $k=1,3,5,\dots\leq K'$ (for cells with large radius). Different cells use different periodic basic codes, i.e. different midamble sets.
+
+For cells with large radius additional midambles may be derived from the time-inverted Basic Midamble Sequence. Thus, the second Basic Midamble Code $m_2$ is the time inverted version of Basic Midamble Code $m_1$ .
+
+In this way, a joint channel estimation for the channel impulse responses of all active users within one time slot can be performed by a maximum of two cyclic correlations (in cells with small radius, a single cyclic correlator suffices). The different user specific channel impulse response estimates are obtained sequentially in time at the output of the cyclic correlators.
+
+### 5.3.3.4 PRACH timeslot formats
+
+For the PRACH the timeslot format is only spreading factor dependent. The timeslot formats 60 and 66 of table 5b are applicable for the PRACH.
+
+### 5.3.3.5 Association between Training Sequences and Channelisation Codes
+
+For the PRACH there exists a fixed association between the training sequence and the channelisation code. The generic rule to define this association is based on the order of the channelisation codes $c_Q^{(k)}$ given by $k$ and the order of the midambles $m_j^{(k)}$ given by $k$ , firstly, and $j$ , secondly, with the constraint that the midamble for a spreading factor $Q$ is the same as in the upper branch for the spreading factor $2Q$ . The index $j=1$ or $2$ indicates whether the original Basic Midamble Sequence ( $j=1$ ) or the time-inverted Basic Midamble Sequence is used ( $j=2$ ).
+
+- For the case that all $k$ are allowed and only one periodic basic code $m_1$ is available for the RACH, the association depicted in figure 12 is straightforward.
+- For the case that only odd $k$ are allowed the principle of the association is shown in figure 13. This association is applied for one and two basic periodic codes.
+
+
+
+The diagram illustrates the hierarchical association of Midambles to Channelisation Codes in an OVSF tree. The tree structure is as follows:
+
+- Root
+ - Top Main Branch
+ - Sub-branch 1
+ - Node $m_1^{(1)} - c_8^{(1)}$
+ - Leaf $m_1^{(1)} - c_{16}^{(1)}$
+ - Leaf $m_1^{(2)} - c_{16}^{(2)}$
+ - Node $m_1^{(3)} - c_8^{(2)}$
+ - Leaf $m_1^{(3)} - c_{16}^{(3)}$
+ - Leaf $m_1^{(4)} - c_{16}^{(4)}$
+ - Sub-branch 2
+ - Node $m_1^{(5)} - c_8^{(3)}$
+ - Leaf $m_1^{(5)} - c_{16}^{(5)}$
+ - Leaf $m_1^{(6)} - c_{16}^{(6)}$
+ - Node $m_1^{(7)} - c_8^{(4)}$
+ - Leaf $m_1^{(7)} - c_{16}^{(7)}$
+ - Leaf $m_1^{(8)} - c_{16}^{(8)}$
+ - Bottom Main Branch
+ - Sub-branch 3
+ - Node $m_1^{(2)} - c_8^{(5)}$
+ - Node $m_1^{(4)} - c_8^{(6)}$
+ - Sub-branch 4
+ - Node $m_1^{(6)} - c_8^{(7)}$
+ - Node $m_1^{(8)} - c_8^{(8)}$
+
+A hierarchical tree diagram showing the association of Midambles to Channelisation Codes in an OVSF tree. The tree starts from a single root on the left and branches out to the right. It has two main branches from the first split. The top main branch eventually leads to leaf nodes with c\_16 codes, while the bottom main branch leads to leaf nodes with c\_8 codes.
+
+Figure 12: Association of Midambles to Channelisation Codes in the OVSF tree for all $k$
+
+
+
+The diagram illustrates the hierarchical association of midambles to channelisation codes in an OVSF tree for odd $k$ . Starting from a root on the left, the tree branches into four main sections.
+- The first section branches into $m_1^{(1)} - c_8^{(1)}$ and $m_1^{(5)} - c_8^{(2)}$ . $m_1^{(1)} - c_8^{(1)}$ further branches into $m_1^{(1)} - c_{16}^{(1)}$ and $m_1^{(3)} - c_{16}^{(2)}$ . $m_1^{(5)} - c_8^{(2)}$ branches into $m_1^{(5)} - c_{16}^{(3)}$ and $m_1^{(7)} - c_{16}^{(4)}$ .
+- The second section branches into $m_2^{(1)} - c_8^{(3)}$ and $m_2^{(5)} - c_8^{(4)}$ . $m_2^{(1)} - c_8^{(3)}$ branches into $m_2^{(1)} - c_{16}^{(5)}$ and $m_2^{(3)} - c_{16}^{(6)}$ . $m_2^{(5)} - c_8^{(4)}$ branches into $m_2^{(5)} - c_{16}^{(7)}$ and $m_2^{(7)} - c_{16}^{(8)}$ .
+- The third section branches into $m_1^{(3)} - c_8^{(5)}$ and $m_1^{(7)} - c_8^{(6)}$ , each leading to two further unlabeled branches at the $c_{16}$ level.
+- The fourth section branches into $m_2^{(3)} - c_8^{(7)}$ and $m_2^{(7)} - c_8^{(8)}$ , each leading to two further unlabeled branches at the $c_{16}$ level.
+
+Figure 13: Association of Midambles to Channelisation Codes in the OVSF tree for odd k. The diagram shows a hierarchical tree structure starting from a single root on the left. The tree branches out to the right, with nodes labeled with midamble identifiers (m) and channelisation codes (c).
+
+Figure 13: Association of Midambles to Channelisation Codes in the OVSF tree for odd $k$
+
+### 5.3.4 The synchronisation channel (SCH)
+
+In TDD mode code group of a cell can be derived from the synchronisation channel. In order not to limit the uplink/downlink asymmetry the SCH is mapped on one or two downlink slots per frame only.
+
+There are two cases of SCH and P-CCPCH allocation as follows:
+
+- Case 1) SCH and P-CCPCH allocated in TS# $k$ , $k=0\dots14$
+- Case 2) SCH allocated in two TS: TS# $k$ and TS# $k+8$ , $k=0\dots6$ ; P-CCPCH allocated in TS# $k$ .
+
+Only case 1 is supported in the case that the entire carrier is dedicated to MBSFN.
+
+The position of SCH (value of $k$ ) in frame can change on a long term basis in any case.
+
+Due to this SCH scheme, the position of P-CCPCH is known from the SCH.
+
+Figure 14 is an example for transmission of SCH, $k=0$ , of Case 2.
+
+
+
+Figure 14: Scheme for Synchronisation channel SCH. The diagram shows a frame structure at the top with '1 Frame = 10 ms' and 10 slots, with slots 0 and 5 highlighted. Below, a zoomed-in view of a 'Time slot = 2560 \* T\_c' is shown. Inside the slot, a primary sequence C\_p is shown as a block of 256 chips, starting at a time offset t\_offset,n. Below C\_p are three parallel secondary sequences b\_i C\_{s,i} for i=1,2,3, each also 256 chips long. The vertical spacing between C\_p and the first secondary sequence is P\_p. The total vertical span of the three secondary sequences is P\_s, with each sequence separated by P\_s/3.
+
+$$b_i \in \{ \frac{1}{2}, -\frac{1}{2} \}, C_{s,i} \in \{ C_0, C_1, C_3, C_4, C_5, C_6, C_8, C_{10}, C_{12}, C_{13}, C_{14}, C_{15} \}, i=1,2,3; \text{ see [8]}$$
+
+**Figure 14: Scheme for Synchronisation channel SCH consisting of one primary sequence $C_p$ and 3 parallel secondary sequences $C_{s,i}$ in slot $k$ and $k+8$ (example for $k=0$ in Case 2)**
+
+As depicted in figure 14, the SCH consists of a primary and three secondary code sequences each 256 chips long. The primary and secondary code sequences are defined in [8] clause 7 'Synchronisation codes for the 3.84 Mcps option'.
+
+Due to mobile to mobile interference, it is mandatory for public TDD systems to keep synchronisation between base stations. As a consequence of this, a capture effect concerning SCH can arise. The time offset $t_{offset,n}$ enables the system to overcome the capture effect.
+
+The time offset $t_{offset,n}$ is one of 32 values, depending on the code group of the cell, $n$ , cf. 'table 6 Mapping scheme for Cell Parameters, Code Groups, Scrambling Codes, Midambles and $t_{offset}$ ' in [8]. Note that the cell parameter will change from frame to frame, cf. 'Table 7 Alignment of cell parameter cycling and system frame number' in [8], but the cell will belong to only one code group and thus have one time offset $t_{offset,n}$ . The exact value for $t_{offset,n}$ , regarding column 'Associated $t_{offset}$ ' in table 6 in [8] is given by:
+
+$$t_{offset,n} = \begin{cases} n \cdot 48 \cdot T_c & n < 16 \\ (720 + n \cdot 48) T_c & n \geq 16 \end{cases}; \quad n = 0, \dots, 31$$
+
+### 5.3.5 Physical Uplink Shared Channel (PUSCH)
+
+The USCH as described in subclause 4.1.2 is mapped onto one or more physical uplink shared channels (PUSCH). Timing advance, as described in [9], subclause 4.3, is applied to the PUSCH.
+
+#### 5.3.5.1 PUSCH Spreading
+
+The spreading factors that can be applied to the PUSCH are $SF = 1, 2, 4, 8, 16$ as described in subclause 5.2.1.2.
+
+#### 5.3.5.2 PUSCH Burst Types
+
+Burst types 1, 2 or 3 as described in subclause 5.2.2 can be used for PUSCH. TFCI and TPC can be transmitted on the PUSCH.
+
+### 5.3.5.3 PUSCH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the PUSCH.
+
+### 5.3.5.4 UE Selection
+
+The UE that shall transmit on the PUSCH is selected by higher layer signalling.
+
+## 5.3.6 Physical Downlink Shared Channel (PDSCH)
+
+The DSCH as described in subclause 4.1.2 is mapped onto one or more physical downlink shared channels (PDSCH).
+
+### 5.3.6.1 PDSCH Spreading
+
+The PDSCH uses either spreading factor $SF = 16$ or $SF = 1$ as described in subclause 5.2.1.1.
+
+### 5.3.6.2 PDSCH Burst Types
+
+Burst types 1 or 2 as described in subclause 5.2.2 can be used for PDSCH. TFCI can be transmitted on the PDSCH.
+
+### 5.3.6.3 PDSCH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the PDSCH.
+
+### 5.3.6.4 UE Selection
+
+To indicate to the UE that there is data to decode on the DSCH, three signalling methods are available:
+
+- 1) using the TFCI field of the associated channel or PDSCH;
+- 2) using on the DSCH user specific midamble derived from the set of midambles used for that cell;
+- 3) using higher layer signalling.
+
+When the midamble based method is used, the UE specific midamble allocation method shall be employed (see subclause 5.6), and the UE shall decode the PDSCH if the PDSCH was transmitted with the midamble assigned to the UE by UTRAN. For this method no other physical channels may use the same time slot as the PDSCH and only one UE may share the PDSCH time slot within one TTI.
+
+Note: From the above mentioned signalling methods, only the higher layer signalling method is supported by higher layers in this release.
+
+## 5.3.7 The Paging Indicator Channel (PICH)
+
+The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators.
+
+### 5.3.7.1 Mapping of Paging Indicators to the PICH bits
+
+Figure 15 depicts the structure of a PICH burst and the numbering of the bits within the burst. The same burst type is used for the PICH in every cell. $N_{PIB}$ bits in a normal burst of type 1 or 2 are used to carry the paging indicators, where $N_{PIB}$ depends on the burst type: $N_{PIB}=240$ for burst type 1 and $N_{PIB}=272$ for burst type 2. The bits $s_{N_{PIB}+1}, \dots, s_{N_{PIB}+4}$ adjacent to the midamble are reserved for possible future use.
+
+
+
+The diagram illustrates the bit structure of a PICH burst within a single time slot. It is divided into three main segments:
+
+- Bits for Page Indication (Left):** Includes bits $s_1, s_3, \dots, s_{N_{PIB}-1}$ .
+- Reserved Bits (Middle):** Includes bits $s_{N_{PIB}+1}, s_{N_{PIB}+3}$ , a **Midamble**, $s_{N_{PIB}+2}$ , and $s_{N_{PIB}+4}$ .
+- Bits for Page Indication (Right):** Includes bits $s_2, s_4, \dots, s_{N_{PIB}}$ .
+
+The entire sequence is followed by a **Guard Period**. The total duration of the burst and guard period is labeled as **1 Time Slot**.
+
+Diagram of a PICH burst structure within a 1 Time Slot. The burst is divided into three main sections: Bits for Page Indication (left), Reserved Bits (middle), and Bits for Page Indication (right). The left section contains bits s1, s3, ..., s\_{N\_{PIB}-1}. The Reserved Bits section contains bits s\_{N\_{PIB}+1}, s\_{N\_{PIB}+3}, a Midamble, s\_{N\_{PIB}+2}, and s\_{N\_{PIB}+4}. The right section contains bits s2, s4, ..., s\_{N\_{PIB}}. The entire burst is followed by a Guard Period. The total duration is 1 Time Slot.
+
+Figure 15: Transmission and numbering of paging indicator carrying bits in a PICH burst
+
+Each paging indicator $P_q$ in one time slot is mapped to the bits $\{s_{2L_{PI} \cdot q+1}, \dots, s_{2L_{PI} \cdot (q+1)}}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each paging indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part, as exemplary shown in figure 16 for a paging indicator length $L_{PI}$ of 4 symbols.
+
+
+
+Figure 16: Example of mapping of paging indicators on PICH bits for L\_PI=4. The diagram shows two identical time slot structures. Each slot has a total duration of 2560 T\_c. It contains a 'Midamble (256 Chips)' block, '2 unused symbols', and a 'GP' (Guard Period) block. Paging indicators are mapped to specific bits: P\_0 and P\_33 in the first slot, and P\_0 and P\_29 in the second slot. The mapping is shown by lines connecting the indicator labels to specific bits within the slot structure.
+
+**Figure 16: Example of mapping of paging indicators on PICH bits for $L_{PI}=4$**
+
+The setting of the paging indicators and the corresponding PICH bits (including the reserved ones) is described in [7].
+
+$N_{PI}$ paging indicators of length $L_{PI}=2$ , $L_{PI}=4$ or $L_{PI}=8$ symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators $N_{PI}$ per radio frame is given by the paging indicator length and the burst type, which are both known by higher layer signalling. In table 7 this number is shown for the different possibilities of burst types and paging indicator lengths.
+
+**Table 7: Number $N_{PI}$ of paging indicators per time slot for the different burst types and paging indicator lengths $L_{PI}$**
+
+| | $L_{PI}=2$ | $L_{PI}=4$ | $L_{PI}=8$ |
+|--------------|-------------|-------------|-------------|
+| Burst Type 1 | $N_{PI}=60$ | $N_{PI}=30$ | $N_{PI}=15$ |
+| Burst Type 2 | $N_{PI}=68$ | $N_{PI}=34$ | $N_{PI}=17$ |
+
+### 5.3.7.2 Structure of the PICH over multiple radio frames
+
+As shown in figure 17, the paging indicators of $N_{PICH}$ consecutive frames form a PICH block, $N_{PICH}$ is configured by higher layers. Thus, $N_P = N_{PICH} \cdot N_{PI}$ paging indicators are transmitted in each PICH block.
+
+
+
+Figure 17: Structure of a PICH block. The diagram shows a horizontal sequence of frames labeled '1 PICH Block'. The frames are numbered 0, 1, ..., N\_PICH-2, N\_PICH-1. Each frame contains a set of paging indicators: P\_0, ..., P\_{N\_PI-1}. The frames are represented by boxes, with an ellipsis between frame 1 and frame N\_PICH-2.
+
+**Figure 17: Structure of a PICH block**
+
+The value PI ( $PI = 0, \dots, N_P-1$ ) calculated by higher layers for use for a certain UE, see [15], is associated to the paging indicator $P_q$ in the nth frame of one PICH block, where q is given by
+
+$$q = PI \bmod N_{PI}$$
+
+and n is given by
+
+$$n = PI \text{ div } N_{PI}$$
+
+The PI bitmap in the PCH data frames over Iub contains indication values for all possible higher layer PI values, see [17]. Each bit in the bitmap indicates if the paging indicator $P_q$ associated with that particular PI shall be set to 0 or 1. Hence, the calculation in the formulas above is to be performed in Node B to make the association between PI and $P_q$ .
+
+### 5.3.7.3 PICH Training sequences
+
+The training sequences, i.e. midambles for the PICH, are generated as described in subclause 5.2.3. The allocation of midambles depends on whether SCTD is applied to the PICH.
+
+- If no antenna diversity is applied the PICH the midambles can be allocated as described in subclause 5.6.
+- If SCTD antenna diversity is applied to the PICH the allocation of midambles shall be as described in [9].
+
+## 5.3.8 The physical node B synchronisation channel (PNBSCH)
+
+In case cell sync bursts are used for Node B synchronisation the PNBSCH shall be used for the transmission of the cell sync burst [8]. The PNBSCH shall be mapped on the same timeslot as the PRACH acc. to a higher layer schedule. The cell sync burst shall be transmitted at the beginning of a timeslot. In case of Node B synchronisation via the air interface the transmission of a RACH may be prohibited on higher layer command in specified frames and timeslots.
+
+
+
+| | |
+|-------------------------------|-----------------|
+| Cell Sync Burst
2304 chips | GP
256 chips |
+| 2560 * T c | |
+
+Diagram of a timeslot structure for PNBSCH. It shows a 'Cell Sync Burst' of 2304 chips followed by a 'GP' (Guard Period) of 256 chips. The total duration of the timeslot is indicated as 2560 \* Tc.
+
+## 5.3.9 High Speed Physical Downlink Shared Channel (HS-PDSCH)
+
+The HS-DSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH).
+
+### 5.3.9.1 HS-PDSCH Spreading
+
+The HS-PDSCH shall use either spreading factor SF = 16 or SF=1, as described in 5.2.1.1.
+
+### 5.3.9.2 HS-PDSCH Burst Types
+
+Burst types 1 or 2 as described in subclause 5.2.2 can be used for PDSCH. TFCI shall not be transmitted on the HS-PDSCH. The TF of the HS-DSCH is derived from the associated HS-SCCH.
+
+### 5.3.9.3 HS-PDSCH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the HS-PDSCH.
+
+### 5.3.9.4 UE Selection
+
+To indicate to the UE that there is data to decode on the HS-DSCH, the UE id on the associated HS-SCCH shall be used.
+
+### 5.3.9.5 HS-PDSCH timeslot formats
+
+An HS-PDSCH may use QPSK or 16QAM modulation symbols. The time slot formats are shown in table 7A.
+
+Table 7A: Time slot formats for the HS-PDSCH
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------|
+| 0 (QPSK) | 16 | 512 | 0 | 244 | 244 | 122 |
+| 1 (16QAM) | 16 | 512 | 0 | 488 | 488 | 244 |
+| 2 (QPSK) | 16 | 256 | 0 | 276 | 276 | 138 |
+| 3 (16QAM) | 16 | 256 | 0 | 552 | 552 | 276 |
+| 4 (QPSK) | 1 | 512 | 0 | 3904 | 3904 | 1952 |
+| 5 (16QAM) | 1 | 512 | 0 | 7808 | 7808 | 3904 |
+| 6 (QPSK) | 1 | 256 | 0 | 4416 | 4416 | 2208 |
+| 7 (16QAM) | 1 | 256 | 0 | 8832 | 8832 | 4416 |
+
+## 5.3.10 Shared Control Channel for HS-DSCH (HS-SCCH)
+
+The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below.
+
+### 5.3.10.1 HS-SCCH Spreading
+
+The HS-SCCH shall use spreading factor $SF = 16$ , as described in 5.2.1.1.
+
+### 5.3.10.2 HS-SCCH Burst Types
+
+Burst type 1 as described in subclause 5.2.2 can be used for HS-SCCH. TFCI shall not be transmitted on the HS-SCCH.
+
+### 5.3.10.3 HS-SCCH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the HS-SCCH.
+
+### 5.3.10.4 HS-SCCH timeslot formats
+
+The HS-SCCH always uses time slot format #0 from table 5a, see section 5.2.2.6.1.
+
+## 5.3.11 Shared Information Channel for HS-DSCH (HS-SICH)
+
+The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below.
+
+### 5.3.11.1 HS-SICH Spreading
+
+The HS-SICH shall use spreading factor $SF = 16$ , as described in 5.2.1.2.
+
+### 5.3.11.2 HS-SICH Burst Types
+
+Burst type 1 as described in subclause 5.2.2 can be used for HS-SICH. TFCI shall not be transmitted on the HS-SICH, however, the HS-SICH shall carry TPC information.
+
+### 5.3.11.3 HS-SICH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the HS-SICH.
+
+### 5.3.11.4 HS-SICH timeslot formats
+
+The HS-SICH shall use time slot format #90 from table 5b, see section 5.2.2.6.2.
+
+## 5.3.12 The MBMS Indicator Channel (MICH)
+
+The MBMS Indicator Channel (MICH) is a physical channel used to carry the MBMS notification indicators. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
+
+### 5.3.12.1 Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2
+
+Figure 17a depicts the structure of a MICH burst and the numbering of the bits within the burst. The same burst type is used for the MICH in every cell. $N_{\text{NIB}}$ bits in a normal burst of type 1 or 2 are used to carry the MBMS notification indicators, where $N_{\text{NIB}}$ depends on the burst type: $N_{\text{NIB}}=240$ for burst type 1 and $N_{\text{NIB}}=272$ for burst type 2. The bits $s_{N_{\text{NIB}}+1}, \dots, s_{N_{\text{NIB}}+4}$ adjacent to the midamble are reserved for possible future use.
+
+
+
+Figure 17a: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2. The diagram shows a '1 Time Slot' containing several bit groups. From left to right: 'Bits for Notification Indication' (bits S1, S3, ..., S\_NNIB-1), 'Reserved Bits' (bits S\_NNIB+1, S\_NNIB+3, which are part of the 'Midamble'), 'Midamble', 'Reserved Bits' (bits S\_NNIB+2, S\_NNIB+4, which are part of the 'Midamble'), 'Bits for Notification Indication' (bits S2, S4, ..., S\_NNIB), and a 'Guard Period'. Arrows indicate the mapping of notification indicators to specific bit positions.
+
+**Figure 17a: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2**
+
+Each notification indicator $N_q$ in one time slot is mapped to the bits $\{S_{2L_{NI} \cdot q+1}, \dots, S_{2L_{NI} \cdot (q+1)}}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each MBMS notification indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part: an example is shown in figure 17b for a MBMS notification indicator length $L_{NI}$ of 4 symbols.
+
+
+
+Figure 17b: Example of mapping of MBMS notification indicators on MICH bits for L\_NI=4 for burst types 2 and 1 respectively. The diagram shows two side-by-side representations of a 2560T\_C time slot. Each slot contains a 'Midamble (256 Chips)' and a 'GP' (Guard Period). Between the midamble and GP, there are '2 unused symbols'. On the left (Burst Type 2), notification indicators N0 and N33 are shown. On the right (Burst Type 1), notification indicators N0 and N29 are shown. Arrows indicate the mapping of these indicators to specific bit positions within the slot.
+
+**Figure 17b: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst types 2 and 1 respectively**
+
+The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7].
+
+$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 7B this number is shown for burst types 1 and 2 and differing MBMS notification indicator lengths.
+
+**Table 7B: Number $N_n$ of MBMS notification indicators per time slot for the different burst types 1 and 2 and differing MBMS notification indicator lengths $L_{NI}$**
+
+| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ |
+|--------------|------------|------------|------------|
+| Burst Type 1 | $N_n=60$ | $N_n=30$ | $N_n=15$ |
+| Burst Type 2 | $N_n=68$ | $N_n=34$ | $N_n=17$ |
+
+The value NI ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ .
+
+The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
+
+### 5.3.12.1A Mapping of MBMS Indicators to the MICH bits for burst type 4
+
+When an entire carrier is dedicated to MBSFN operation, the MICH shall use burst type 4. In this case $N_{NIB}=256$ and there are 8 reserved/unused bits adjacent to the midamble reserved for possible future use. The transmission and numbering of MBMS notification indicator carrying bits in a MICH burst is similar to that of figure 17a with the
+
+exception of 4 reserved bits either side of the midamble as opposed to 2 for burst types 1 and 2. An example mapping is shown in figure 17ba for a MBMS notification indicator length $L_{NI}$ of 4 symbols.
+
+
+
+The diagram illustrates a burst structure. At the top, a double-headed arrow indicates a total length of $2560 T_C$ . Below this, a horizontal bar represents the burst. From left to right, it consists of: a hatched segment labeled $N_0$ , a series of empty rectangles with an ellipsis, a hatched segment labeled $N_{31}$ , a solid black rectangle labeled 'Midamble (320 Chips)', another hatched segment, a series of empty rectangles with an ellipsis, and a final hatched segment. Above the 'Midamble' rectangle, a label '4 unused symbols' points to the gap between the $N_{31}$ segment and the midamble.
+
+Figure 17ba: Example of mapping of MBMS notification indicators on MICH bits for L\_NI=4 for burst type 4. The diagram shows a burst structure with a total length of 2560 T\_C. It includes a 'Midamble (320 Chips)' in the center, flanked by '4 unused symbols' on each side. The burst is divided into segments labeled N\_0 and N\_31.
+
+**Figure 17ba: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst type 4**
+
+The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7].
+
+$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 7BA this number is shown for the different possibilities of burst types and MBMS notification indicator lengths.
+
+**Table 7BA: Number $N_n$ of MBMS notification indicators per time slot for burst type 4 and differing MBMS notification indicator lengths $L_{NI}$**
+
+| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ |
+|--------------|------------|------------|------------|
+| Burst Type 4 | $N_n=64$ | $N_n=32$ | $N_n=16$ |
+
+The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ .
+
+The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
+
+### 5.3.12.2 MICH Training sequences
+
+The training sequences, i.e. midambles for the MICH, are generated as described in subclause 5.2.3. The allocation of midambles depends on whether SCTD is applied to the MICH.
+
+- If no antenna diversity is applied the MICH the midambles can be allocated as described in subclause 5.6.
+- If SCTD antenna diversity is applied to the MICH the allocation of midambles shall be as described in [9].
+
+Note that when the entire carrier is dedicated to MBFSN operation MICH employs burst type 4 as described in subclause 5.3.12.1A. Burst type 4 supports a single midamble and hence SCTD is precluded from operation in such a scenario.
+
+### 5.3.13 E-DCH Physical Uplink Channel (E-PUCH)
+
+One or more E-PUCH are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE. No other physical channels may be transmitted by a UE in an E-PUCH timeslot.
+
+Timing advance, as described in [9], subclause 4.3, is applied to the E-PUCH.
+
+### 5.3.13.1 E-UCCH
+
+The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is carried within indicator fields mapped to E-PUCH. Depending on the configuration by higher layers, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted.
+
+Higher layers shall indicate the maximum number of timeslots ( $N_{E-UCCH}$ ) that may contain E-UCCH/TPC in the E-DCH TTI. For an allocation of $n_{TS}$ E-PUCH timeslots, the UE shall transmit E-UCCH and TPC on the first $m$ allocated timeslots of the E-DCH TTI, where $m = \min(n_{TS}, N_{E-UCCH})$ .
+
+The E-UCCH comprises two parts, E-UCCH part 1 and E-UCCH part 2.
+
+E-UCCH part 1:
+
+- is of length 32 physical channel bits
+- is mapped to the TFCI field of the E-PUCH (16 bits either side of the midamble)
+- is spread at $SF=16$ using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]
+- uses QPSK modulation
+
+E-UCCH part 2:
+
+- is of length 32 physical channel bits
+- is spread using the same spreading factor as the data payloads
+- uses the same modulation as the data payloads
+
+Figures 17c and 17d show the E-PUCH data burst with and without the E-UCCH/TPC fields.
+
+
+
+The diagram illustrates the structure of an E-PUCH data burst. It consists of a sequence of fields: 'Data symbols', followed by a block containing 'E-UCCH part 1', 'Midamble', and 'E-UCCH part 2', then another block containing 'TPC' and 'Data symbols', and finally a 'GP' (Guard Period). The 'Midamble' is shown as a central block. 'E-UCCH part 1' and 'E-UCCH part 2' are indicated by lines pointing to the blocks immediately adjacent to the 'Midamble'. 'TPC' is indicated by a line pointing to a block between the second 'Data symbols' block and the 'GP'. A double-headed arrow below the 'Midamble' block is labeled '512/256 chips'. A long double-headed arrow at the bottom of the diagram spans the entire burst and is labeled '2560 \* Tc'.
+
+Diagram of an E-PUCH data burst structure showing the placement of E-UCCH part 1, E-UCCH part 2, and TPC relative to data symbols, a midamble, and a guard period (GP).
+
+**Figure 17c: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst**
+
+
+
+Diagram of E-PUCH data burst structure without E-UCCH/TPC. It shows a sequence of four fields: Data symbols, Midamble, Data symbols, and GP. A double-headed arrow below the Midamble field indicates its length is 512/256 chips. A longer double-headed arrow below the entire sequence indicates the total length is 2560 \* Tc.
+
+Figure 17d: E-PUCH data burst without E-UCCH/TPC
+
+### 5.3.13.2 E-PUCH Spreading
+
+The spreading factors that can be applied to the E-PUCH are SF = 1, 2, 4, 8, 16 as described in subclause 5.2.1.2.
+
+### 5.3.13.3 E-PUCH Burst Types
+
+Burst types 1, 2 or 3 as described in subclause 5.2.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH.
+
+### 5.3.13.4 PUSCH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the E-PUCH.
+
+### 5.3.13.5 UE Selection
+
+UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification.
+
+### 5.3.13.6 E-PUCH timeslot formats
+
+An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 7c.
+
+Table 7c: Timeslot formats for E-PUCH
+
+| slot format # | SF | Midamble Length (chips) | GP (chips) | N EUCCH1 (bits) | N EUCCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 (QPSK) | 16 | 512 | 96 | 0 | 0 | 0 | 244 | 244 | 122 | 122 |
+| 1 (16QAM) | 16 | 512 | 96 | 0 | 0 | 0 | 488 | 488 | 244 | 244 |
+| 2 (QPSK) | 16 | 512 | 96 | 32 | 32 | 2 | 244 | 178 | 90 | 88 |
+| 3 (16QAM) | 16 | 512 | 96 | 32 | 32 | 2 | 454 | 388 | 196 | 192 |
+| 4 (QPSK) | 16 | 256 | 96 | 0 | 0 | 0 | 276 | 276 | 138 | 138 |
+| 5 (16QAM) | 16 | 256 | 96 | 0 | 0 | 0 | 552 | 552 | 276 | 276 |
+| 6 (QPSK) | 16 | 256 | 96 | 32 | 32 | 2 | 276 | 210 | 106 | 104 |
+| 7 (16QAM) | 16 | 256 | 96 | 32 | 32 | 2 | 518 | 452 | 228 | 224 |
+| 8 (QPSK) | 8 | 512 | 96 | 0 | 0 | 0 | 488 | 488 | 244 | 244 |
+| 9 (16QAM) | 8 | 512 | 96 | 0 | 0 | 0 | 976 | 976 | 488 | 488 |
+| 10 (QPSK) | 8 | 512 | 96 | 32 | 32 | 2 | 454 | 388 | 196 | 192 |
+| 11 (16QAM) | 8 | 512 | 96 | 32 | 32 | 2 | 874 | 808 | 408 | 400 |
+| 12 (QPSK) | 8 | 256 | 96 | 0 | 0 | 0 | 552 | 552 | 276 | 276 |
+| 13 (16QAM) | 8 | 256 | 96 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 |
+| 14 (QPSK) | 8 | 256 | 96 | 32 | 32 | 2 | 518 | 452 | 228 | 224 |
+| 15 (16QAM) | 8 | 256 | 96 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 |
+| 16 (QPSK) | 4 | 512 | 96 | 0 | 0 | 0 | 976 | 976 | 488 | 488 |
+| 17 (16QAM) | 4 | 512 | 96 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 |
+| 18 (QPSK) | 4 | 512 | 96 | 32 | 32 | 2 | 874 | 808 | 408 | 400 |
+
+| | | | | | | | | | | |
+|------------|----|-----|-----|----|----|---|------|------|------|------|
+| 19 (16QAM) | 4 | 512 | 96 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 |
+| 20 (QPSK) | 4 | 256 | 96 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 |
+| 21 (16QAM) | 4 | 256 | 96 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 |
+| 22 (QPSK) | 4 | 256 | 96 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 |
+| 23 (16QAM) | 4 | 256 | 96 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 |
+| 24 (QPSK) | 2 | 512 | 96 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 |
+| 25 (16QAM) | 2 | 512 | 96 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 |
+| 26 (QPSK) | 2 | 512 | 96 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 |
+| 27 (16QAM) | 2 | 512 | 96 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 |
+| 28 (QPSK) | 2 | 256 | 96 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 |
+| 29 (16QAM) | 2 | 256 | 96 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 |
+| 30 (QPSK) | 2 | 256 | 96 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 |
+| 31 (16QAM) | 2 | 256 | 96 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 |
+| 32 (QPSK) | 1 | 512 | 96 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 |
+| 33 (16QAM) | 1 | 512 | 96 | 0 | 0 | 0 | 7808 | 7808 | 3904 | 3904 |
+| 34 (QPSK) | 1 | 512 | 96 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 |
+| 35 (16QAM) | 1 | 512 | 96 | 32 | 32 | 2 | 6754 | 6688 | 3376 | 3312 |
+| 36 (QPSK) | 1 | 256 | 96 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 |
+| 37 (16QAM) | 1 | 256 | 96 | 0 | 0 | 0 | 8832 | 8832 | 4416 | 4416 |
+| 38 (QPSK) | 1 | 256 | 96 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 |
+| 39 (16QAM) | 1 | 256 | 96 | 32 | 32 | 2 | 7778 | 7712 | 3888 | 3824 |
+| 40 (QPSK) | 16 | 512 | 192 | 0 | 0 | 0 | 232 | 232 | 122 | 110 |
+| 41 (16QAM) | 16 | 512 | 192 | 0 | 0 | 0 | 464 | 464 | 244 | 220 |
+| 42 (QPSK) | 16 | 512 | 192 | 32 | 32 | 2 | 232 | 166 | 90 | 76 |
+| 43 (16QAM) | 16 | 512 | 192 | 32 | 32 | 2 | 430 | 364 | 196 | 168 |
+| 44 (QPSK) | 8 | 512 | 192 | 0 | 0 | 0 | 464 | 464 | 244 | 220 |
+| 45 (16QAM) | 8 | 512 | 192 | 0 | 0 | 0 | 928 | 928 | 488 | 440 |
+| 46 (QPSK) | 8 | 512 | 192 | 32 | 32 | 2 | 430 | 364 | 196 | 168 |
+| 47 (16QAM) | 8 | 512 | 192 | 32 | 32 | 2 | 826 | 760 | 408 | 352 |
+| 48 (QPSK) | 4 | 512 | 192 | 0 | 0 | 0 | 928 | 928 | 488 | 440 |
+| 49 (16QAM) | 4 | 512 | 192 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 |
+| 50 (QPSK) | 4 | 512 | 192 | 32 | 32 | 2 | 826 | 760 | 408 | 352 |
+| 51 (16QAM) | 4 | 512 | 192 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 |
+| 52 (QPSK) | 2 | 512 | 192 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 |
+| 53 (16QAM) | 2 | 512 | 192 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 |
+| 54 (QPSK) | 2 | 512 | 192 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 |
+| 55 (16QAM) | 2 | 512 | 192 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 |
+| 56 (QPSK) | 1 | 512 | 192 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 |
+| 57 (16QAM) | 1 | 512 | 192 | 0 | 0 | 0 | 7424 | 7424 | 3904 | 3520 |
+| 58 (QPSK) | 1 | 512 | 192 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 |
+| 59 (16QAM) | 1 | 512 | 192 | 32 | 32 | 2 | 6370 | 6304 | 3376 | 2928 |
+
+### 5.3.14 E-DCH Random Access Uplink Control Channel (E-RUCCH)
+
+The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. The characteristics of the E-RUCCH physical channel are identical to those of PRACH (see subclause 5.3.3).
+
+Physical resources available for E-RUCCH are configured by higher layers. E-RUCCH may be mapped to the same physical resources that are assigned for PRACH.
+
+### 5.3.15 E-DCH Absolute Grant Channel (E-AGCH)
+
+The E-DCH Absolute Grant Channel (E-AGCH) is a downlink physical channel carrying the uplink E-DCH absolute grant control information. E-AGCH carries a TPC field (located immediately after the midamble and spread using SF16) which is used to control the E-PUCH power. Figure 17e illustrates the burst structure of the E-AGCH.
+
+
+
+Figure 17e: Burst structure of E-AGCH. The diagram shows a horizontal bar representing the burst structure. From left to right, it consists of: 'Data symbols', 'Midamble', a small hatched box labeled 'TPC field', 'Data symbols', and 'GP'. A double-headed arrow below the 'Midamble' and 'TPC field' section is labeled '512/256 chips'. A longer double-headed arrow at the bottom, spanning the entire length of the bar, is labeled '2560\*Tc'.
+
+Figure 17e: Burst structure of E-AGCH
+
+One E-DCH absolute grant for a UE shall be transmitted over one E-AGCH.
+
+#### 5.3.15.1 E-AGCH Spreading
+
+The E-AGCH shall use spreading factor $SF = 16$ , as described in 5.2.1.1.
+
+#### 5.3.15.2 E-AGCH Burst Types
+
+Burst types 1 and 2 as described in subclause 5.2.2 can be used for E-AGCH. TPC shall be transmitted on E-AGCH whereas TFCI shall not be transmitted.
+
+#### 5.3.15.3 E-AGCH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the E-AGCH.
+
+#### 5.3.15.4 E-AGCH timeslot formats
+
+The E-AGCH uses the timeslot formats of Table 7d. These augment downlink slot formats 0...19 of table 5a, see subclause 5.2.2.6.1.
+
+Table 7d: Time slot formats for E-AGCH
+
+| Slot Format # | SF | Midamble length (chips) | $N_{TFCI}$ code word (bits) | $N_{TPC}$ (bits) | Bits/slot | $N_{Data/Slot}$ (bits) | $N_{data/data\ field\ (1)}$ (bits) | $N_{data/data\ field\ (2)}$ (bits) |
+|---------------|----|-------------------------|-----------------------------|------------------|-----------|------------------------|------------------------------------|------------------------------------|
+| 20 | 16 | 512 | 0 | 2 | 244 | 242 | 122 | 120 |
+| 21 | 16 | 256 | 0 | 2 | 276 | 274 | 138 | 136 |
+
+### 5.3.16 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)
+
+The E-DCH HARQ Acknowledgement indicator channel (E-HICH) is defined in terms of a SF16 downlink physical channel and a signature sequence. The E-HICH carries the uplink E-DCH hybrid ARQ acknowledgement indicator. Figure 17f illustrates the structure of the E-HICH.
+
+
+
+The diagram illustrates the E-HICH structure. At the top, three user rows are shown: user #H, user #1, and user #0. Each row contains a sequence of bits: $b_{i,0}, b_{i,1}, \dots, b_{i,119}$ , followed by two 'spare bits', then $b_{i,120}, b_{i,121}, \dots, b_{i,239}$ , and finally a 'GP' (Guard Period). A 'midamble' is indicated in the center of each row. A bracket on the right side groups the GP for all users, labeled '1xSF16'. Below the user rows, a timeline shows 'Slot #0', 'Slot #1', 'Slot #2', ..., 'Slot #n', ..., 'Slot #14'. A double-headed arrow below the slots is labeled '1 radio frame, 10ms'.
+
+Figure 17f – E-HICH Structure. The diagram shows the structure of an E-HICH burst across multiple users (user #H, user #1, user #0) and slots (Slot #0 to Slot #14). Each user's burst consists of data bits (b\_{i,j}), spare bits, a midamble, and a GP. The total duration of the burst is 1 radio frame (10ms). The GP is shared across all users and has a duration of 1xSF16.
+
+**Figure 17f – E-HICH Structure**
+
+A single channelisation code may carry one or multiple signature sequences. Each signature sequence conveys a HARQ acknowledgement indicator. A maximum of one indicator may be transmitted to a UE. Each acknowledgement indicator is coded to form a signature sequence of 240 bits ( $b_0, b_1, \dots, b_{239}$ ) as defined in [7] and is transmitted within a single E-HICH timeslot. The E-HICH also contains $U$ spare bit locations, where $U=4$ for burst type 1 and $U=36$ for burst type 2. The spare bit values are not defined.
+
+### 5.3.16.1 E-HICH Spreading
+
+Signature sequences (including spare bits inserted) that share the same channelisation code are combined and spread using spreading factor $SF=16$ as described in [8].
+
+### 5.3.16.2 E-HICH Burst Types
+
+Burst types 1 and 2 as described in subclause 5.2.2 can be used for E-HICH. Neither TFCI nor TPC shall be transmitted on the E-HICH.
+
+### 5.3.16.3 E-HICH Training Sequences
+
+The training sequences as described in subclause 5.2.3 are used for the E-HICH.
+
+## 5.4 Transmit Diversity for DL Physical Channels
+
+Table 8 summarizes the different transmit diversity schemes for different downlink physical channel types that are described in [9].
+
+**Table 8: Application of Tx diversity schemes on downlink physical channel types**
+ "X" – can be applied, "--" – must not be applied
+
+| Physical channel type | Open loop TxDiversity | | Closed loop TxDiversity |
+|-----------------------|-----------------------|---------------------|-------------------------|
+| | TSTD | SCTD (*) | |
+| P-CCPCH | -- | X(†) | -- |
+| S-CCPCH | X(**) | X(†) | -- |
+| SCH | X | -- | -- |
+| DPCH | -- | -- | X |
+| PDSCH | -- | X | X |
+| PICH | -- | X | -- |
+| MICH | -- | X(†) | -- |
+| HS-SCCH | -- | X | X |
+| HS-PDSCH | -- | X | X |
+| E-AGCH | -- | X | X |
+| E-HICH | -- | X | -- |
+
+(\*) Note: SCTD may only be applied to physical channels when they are allocated to beacon locations.
+
+(\*\*) Note: TSTD may not be applied to S-CCPCH in beacon locations.
+
+(†) Note: that when the entire carrier is dedicated to MBSFN operation SCTD shall not be applied.
+
+## 5.5 Beacon characteristics of physical channels
+
+For the purpose of measurements, common physical channels that are allocated to particular locations (time slot, code) shall have particular physical characteristics, called beacon characteristics. Physical channels with beacon characteristics are called beacon channels. The locations of the beacon channels are called beacon locations. The ensemble of beacon channels shall provide the beacon function, i.e. a reference power level at the beacon locations, regularly existing in each radio frame. Thus, beacon channels must be present in each radio frame, the only exception is when idle periods are used to support time difference measurements for location services [9]. Then it may be possible that the beacon channels occur in the same frame and time slot as the idle periods. In this case, the beacon channels will not be transmitted in that particular frame and time slot.
+
+### 5.5.1 Location of beacon channels
+
+The beacon locations are determined by the SCH and depend on the SCH allocation case, see subclause 5.3.4:
+
+- Case 1) The beacon function shall be provided by the physical channels that are allocated to channelisation code $c_{Q=6}^{(k=1)}$ and to TS#k, k=0,...,14.
+- Case 2) The beacon function shall be provided by the physical channels that are allocated to channelisation code $c_{Q=6}^{(k=1)}$ and to TS#k and TS#k+8, k=0,...,6.
+
+Note that by this definition the P-CCPCH always has beacon characteristics.
+
+### 5.5.2 Physical characteristics of beacon channels
+
+The beacon channels shall have the following physical characteristics. They:
+
+- are transmitted with reference power;
+- are transmitted without beamforming;
+- use burst type 1 or burst type 4 when MBSFN is applied to beacon channels;
+- use midamble m(1) and m(2) exclusively in this time slot; and
+- midambles m(9) and m(10) are always left unused in this time slot, if 16 midambles are allowed in that cell.
+
+Note that in the time slot where the P-CCPCH is transmitted only the midambles m(1) to m(8) shall be used, see 5.6.1. Thus, midambles m(9) and m(10) are always left unused in this time slot.
+
+Note that when MBSFN is applied to beacon channels there is a single midamble and hence midamble $m^{(1)}$ is exclusively used in the timeslot.
+
+The reference power corresponds to the sum of the power allocated to both midambles $m^{(1)}$ and $m^{(2)}$ . Two possibilities exist:
+
+- If SCTD antenna diversity is not applied to beacon channels all the reference power of any beacon channel is allocated to $m^{(1)}$ .
+- If SCTD antenna diversity is applied to beacon channels, for any beacon channel midambles $m^{(1)}$ and $m^{(2)}$ are each allocated half of the reference power.
+
+## 5.6 Midamble Allocation for Physical Channels
+
+Midambles are part of the physical channel configuration which is performed by higher layers. Three different midamble allocation schemes exist:
+
+- UE specific midamble allocation: A UE specific midamble for DL or UL is explicitly assigned by higher layers.
+- Default midamble allocation: The midamble for DL or UL is allocated by layer 1 depending on the associated channelisation code.
+- Common midamble allocation: The midamble for the DL is allocated by layer 1 depending on the number of channelisation codes currently being present in the DL time slot.
+
+If a midamble is not explicitly assigned and the use of the common midamble allocation scheme is not signalled by higher layers, the midamble shall be allocated by layer 1, based on the default midamble allocation scheme. This default midamble allocation scheme is given by a fixed association between midambles and channelisation codes, see clause A.3, and shall be applied individually to all channelisation codes within one time slot. Different associations apply for different burst types and cell configurations with respect to the maximum number of midambles.
+
+For timeslots employing MBSFN operation burst type 4 is used and hence DL beamforming is not applied, subclause 5.2.4. Furthermore, as this burst type contains only a single midamble, i.e. $K_{\text{Cell}}=1$ , then all physical channels in such timeslots employ the same midamble and thus default and common midamble allocation amount to the same allocation strategies.
+
+### 5.6.1 Midamble Allocation for DL Physical Channels
+
+Beacon channels shall always use the reserved midambles $m^{(1)}$ and $m^{(2)}$ , see 5.5. For DL physical channels that are located in the same time slot as the P-CCPCH, midambles shall be allocated based on the default midamble allocation scheme, using the association for burst type 1 and $K_{\text{Cell}}=8$ midambles. For all other DL physical channels, the midamble is explicitly assigned by higher layers or allocated by layer 1.
+
+#### 5.6.1.1 Midamble Allocation by signalling from higher layers
+
+UE specific midambles may be signalled by higher layers to UE's as a part of the physical channel configuration, if:
+
+- multiple UEs use the physical channels in one DL time slot; and
+- beamforming is applied to all of these DL physical channels; and
+- no closed loop TxDiversity is applied to any of these DL physical channels;
+
+or
+
+- PDSCH physical layer signalling based on the midamble is used.
+
+#### 5.6.1.2 Midamble Allocation by layer 1
+
+##### 5.6.1.2.1 Default midamble
+
+If a midamble is not explicitly assigned and the use of the common midamble allocation scheme is not signalled by higher layers, the UE shall derive the midambles from the allocated channelisation codes and shall use an individual midamble for each channelisation code group containing one primary and a set of secondary channelisation codes. The
+
+association between midambles and channelisation code groups is given in annex A.3. All the secondary channelisation codes within a set use the same midamble as the primary channelisation code to which they are associated.
+
+Higher layers shall allocate the channelisation codes in a particular order. Secondary codes shall only be allocated if the associated primary code is also allocated. If midambles are reserved for the beacon channels, all primary and secondary channelisation codes that are associated with the reserved midambles shall not be used.
+
+Channelisation codes of one channelisation code group shall not be allocated to different UE's.
+
+In the case that secondary channelisation codes are used, secondary channelisation codes of one channelisation code group shall be allocated in ascending order, with respect to their numbering, and beginning with the lowest code index in this channelisation code group.
+
+The UE shall assume different channel estimates for each of the individual midambles.
+
+The default midamble allocation shall not apply for those downlink channels that are intended for a UE which will be the only UE assigned to a given time slot or slots for the duration of the assigned channel's existence (as in the case of high rate services).
+
+#### 5.6.1.2.2 Common Midamble
+
+The use of the common midamble allocation scheme is signalled to the UE by higher layers as a part of the physical channel configuration. A common midamble may be assigned by layer 1 to all physical channels in one DL time slot, if:
+
+- a single UE uses all physical channels in one DL time slot (as in the case of high rate service);
+
+or
+
+- multiple UEs use the physical channels in one DL time slot; and
+- no beamforming is applied to any of these DL physical channels; and
+- no closed loop TxDiversity is applied to any of these DL physical channels; and
+- midambles are not used for PDSCH physical layer signalling.
+
+The number of channelisation codes currently employed in the DL time slot is associated with the use of a particular common midamble. Different associations apply for different burst types and cell configurations with respect to the maximum number of midambles, see annex B.
+
+### 5.6.2 Midamble Allocation for UL Physical Channels
+
+If the midamble is explicitly assigned by higher layers, an individual midamble shall be assigned to all UE's in one UL time slot.
+
+If no midamble is explicitly assigned by higher layers, the UE shall derive the midamble from the channelisation code that is used for the data part (except for TFCI/TPC) of the burst. Note that in the event that code hopping is employed the midamble is derived from the channelisation code actually transmitted (i.e. the code used after the hop sequence has been applied – see [9]). The associations between midamble and channelisation code are the same as for DL physical channels.
+
+## 5.7 Midamble Transmit Power
+
+There shall be no offset between the sum of the powers allocated to all midambles in a timeslot and the sum of the powers allocated to the data symbol fields. The transmit power within a timeslot is hence constant.
+
+The midamble transmit power of beacon channels is equal to the reference power. If SCTD is used for beacon channels, the reference power is equally divided between the midambles $m^{(1)}$ and $m^{(2)}$ .
+
+The midamble transmit power of all other physical channels depends on the midamble allocation scheme used. The following rules apply
+
+- In case of Default Midamble Allocation, every midamble is transmitted with the same power as the associated codes.
+
+- In case of Common Midamble Allocation in the downlink, the transmit power of this common midamble is such that there is no power offset between the data parts and the midamble part of the overall transmit signal within one time slot.
+- In case of UE Specific Midamble Allocation, the transmit power of the UE specific midamble is such that there is no power offset between the data parts and the midamble part of every user within one time slot.
+
+The following figure 18 depicts the midamble powers for the different channel types and midamble allocation schemes.
+
+Note 1: In figure 18, the codes c(1) to c(16) represent the set of usable codes and not the set of used codes.
+
+Note 2: The common midamble allocation and the midamble allocation by higher layers are not applicable in those beacon time slots, in which the P-CCPCH is located, see section 5.6.1.
+
+
+
+No Beacon Time Slots Beacon Time Slots when SCTD is not applied Beacon Time Slots when SCTD is applied
+
+x depends on the number of transmitted codes in that time slot
+
+M: Number of codes per Midamble (M=16/KCELL); in the P-CCPCH Time Slot M = 2, independent of KCELL
+KCELL : Number of usable Midamble Shifts in this Cell
+
+U: Number of CCTrCHs in this Time Slot, multiple CCTrCHs of one user may share one midamble
+KCELL : Number of usable Midamble Shifts in this Cell
+
+Figure 18: Midamble powers for the different midamble allocation schemes. The figure consists of three columns of diagrams representing different time slot scenarios: 'No Beacon Time Slots', 'Beacon Time Slots when SCTD is not applied', and 'Beacon Time Slots when SCTD is applied'. Each column contains three rows of diagrams for different midamble allocation schemes: 'Common Midamble Allocation', 'Default Midamble Allocation', and 'Midamble Allocation by Higher Layers'. Each diagram shows a power level 'P' on the y-axis and a sequence of codes and midambles on the x-axis. The 'Common Midamble Allocation' shows a single midamble 'm(x)' between codes 'c(1)' and 'c(16)'. The 'Default Midamble Allocation' shows multiple midambles 'm(1)' through 'm(K\_CELL)' interleaved with codes. The 'Midamble Allocation by Higher Layers' shows multiple CCTrCHs sharing midambles. A legend defines M as the number of codes per midamble (M=16/K\_CELL), K\_CELL as the number of usable midamble shifts, and U as the number of CCTrCHs.
+
+**Figure 18: Midamble powers for the different midamble allocation schemes**
+
+## 5.8 Physical channels for the 3.84 Mcps MBFSN IMB option
+
+Physical channels are defined by a specific carrier frequency, scrambling code, channelization code and in some cases a time start & stop (giving a duration). Scrambling and channelization codes are specified in [8]. Time durations are defined by start and stop instants, measured in integer multiples of chips. Suitable multiples of chips also used in specification are:
+
+**Radio frame:** A radio frame is a processing duration which consists of 15 slots. The length of a radio frame corresponds to 38400 chips (10 ms).
+
+**Slot:** A slot is a duration which consists of fields containing bits. The length of a slot corresponds to 2560 chips.
+
+**Sub-frame:** A sub-frame corresponds to 3 slots (2 ms).
+
+The default time duration for a physical channel is continuous from the instant when it is started to the instant when it is stopped. Physical channels that are not continuous will be explicitly described. In the case of 2 ms physical channel duration, the physical channel is active for only one 2 ms sub-frame (7680 chips) per radio frame. A physical channel of 2 ms duration may start at one of 5 start instances per radio frame. These correspond to 0 ms, 2 ms, 4 ms, 6 ms or 8 ms following the commencement of the radio frame and are denoted as sub-frames 0, 1, 2, 3 and 4 respectively.
+
+Transport channels are described (in more abstract higher layer models of the physical layer) as being capable of being mapped to physical channels. Within the physical layer itself the exact mapping is from a composite coded transport
+
+channel (CCTrCH) to the data part of a physical channel. In addition to data parts there are also channel control parts and physical signals. For the IMB option, both a continuous and a discontinuous pilot physical channel shall be transmitted using specific OVSF channelisation codes.
+
+The IMB option is only applicable for dedicated carrier MBSFN operations in which all TDD slots of the radio frame are configured in the downlink direction. All physical channels are common and downlink only.
+
+
+
+Figure 18iA: Downlink transmissions in all TDD slots. A diagram showing a 10 ms radio frame divided into 15 TDD slots. Each slot is represented by a box with a downward-pointing arrow, indicating downlink transmission in every slot.
+
+Figure 18iA: Downlink transmissions in all TDD slots
+
+## 5.8.1 Transmit diversity
+
+Transmit diversity is not applicable to IMB physical channels for MBSFN operations.
+
+## 5.8.2 Common physical channels
+
+The common physical channels used on a dedicated carrier for the IMB option are P-CPICH, T-CPICH, P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2, SCH and MICH.
+
+### 5.8.2.1 Primary Common Pilot Channel (P-CPICH)
+
+The primary common pilot channel (P-CPICH) is a fixed rate (30 kbps, SF=256) downlink physical channel using QPSK modulation and carrying a pre-defined bit sequence in which all bits are set to logical “0”. The P-CPICH is transmitted continuously on all slots of the radio frame. Figure 18iiA shows the frame structure of the P-CPICH.
+
+
+
+Figure 18iiA: Frame structure for Primary Common Pilot Channel. A diagram showing a 10 ms radio frame (Tf = 10 ms) divided into 15 slots (Slot #0 to Slot #14). A 'Pre-defined bit sequence' is shown above the slots, with lines pointing to Slot #0 and Slot #14. Below the sequence, it states 'Tslot = 2560 chips, 20 bits'.
+
+Figure 18iiA: Frame structure for Primary Common Pilot Channel
+
+The P-CPICH has the following characteristics:
+
+- The same channelization code is always used for the P-CPICH, see [8];
+- The P-CPICH is scrambled by the primary scrambling code, see [8];
+- There is one and only one P-CPICH per MBSFN cluster;
+- The P-CPICH is broadcast over the entire MBSFN cluster.
+
+### 5.8.2.2 Time-multiplexed Common Pilot Channel (T-CPICH)
+
+The time-multiplexed common pilot channel (T-CPICH) is composed of a set of 15 SF=16 physical channels using 16-QAM modulation, each carrying a pre-defined pilot bit sequence of length 64 bits. All of the channelization codes used to carry T-CPICH are OVSF codes as defined in [8] and are orthogonal to the P-CPICH. The T-CPICH chip-level sequence has a length of 256 chips and is transmitted at the end of each slot of the radio frame. The T-CPICH is not transmitted during the first 2304 chips of each slot. The structure of the T-CPICH is shown in figure 18iiiA.
+
+
+
+Figure 18iiiA: Structure of the Time-multiplexed Common Pilot Channel (T-CPICH). The diagram shows a radio frame of 10 ms duration (T\_f = 10 ms) divided into 15 slots (Slot #0 to Slot #14). Each slot has a duration of T\_slot = 2560 chips. The T-CPICH is transmitted in Slot #1 and Slot #14. In Slot #14, the T-CPICH is shown as a 'TDM pilot' block of 256 chips at the end of the slot. The rest of the slot is labeled '(Tx OFF)'.
+
+**Figure 18iiiA: Structure of the Time-multiplexed Common Pilot Channel (T-CPICH)**
+
+The T-CPICH has the following characteristics:
+
+- The T-CPICH is scrambled by the same scrambling code as P-CPICH
+- There is one and only one T-CPICH per MBSFN cluster;
+- The T-CPICH is broadcasted over the entire MBSFN cluster
+
+The UE may use the T-CPICH as the phase reference for all downlink physical channels.
+
+The pilot bit sequences carried on T-CPICH are defined as a function of the scrambling code index used for the MBSFN cluster and the slot index in which the T-CPICH is transmitted. With index $n$ of the primary scrambling code as defined in [4] and with the index $i = 0 \dots 14$ , of the slot in which the T-CPICH is transmitted, the T-CPICH pilot bit sequences $B^{(n)}_{\text{T-CPICH},0} \dots B^{(n)}_{\text{T-CPICH},959}$ are defined in table CD.1 of annex CD. For each slot index $i$ , the bit sequences $B^{(n)}_{\text{T-CPICH},0} \dots B^{(n)}_{\text{T-CPICH},959}$ are a concatenation of the 15 bit sequences $b^{(n)}_{\text{T-CPICH},0,m} \dots b^{(n)}_{\text{T-CPICH},63,m}$ carried on each OVSF code $C_{\text{ch},16,m}$ (see [8]) with $m = 1 \dots 15$ such that:
+
+$$\begin{aligned} \{ B^{(n)}_{\text{T-CPICH},0}, B^{(n)}_{\text{T-CPICH},1}, \dots, B^{(n)}_{\text{T-CPICH},959} \} = & \{ \{ b^{(n)}_{\text{T-CPICH},0,1}, b^{(n)}_{\text{T-CPICH},1,1} \dots b^{(n)}_{\text{T-CPICH},63,1} \}, \dots \\ & \{ b^{(n)}_{\text{T-CPICH},0,2}, b^{(n)}_{\text{T-CPICH},1,2} \dots b^{(n)}_{\text{T-CPICH},63,2} \}, \dots \\ & \dots \{ b^{(n)}_{\text{T-CPICH},0,15}, b^{(n)}_{\text{T-CPICH},1,15} \dots b^{(n)}_{\text{T-CPICH},63,15} \} \} \end{aligned}$$
+
+The OVSF code $C_{\text{ch},16,0}$ is not used by T-CPICH.
+
+### 5.8.2.3 Primary common control physical channel (P-CCPCH)
+
+The Primary CCPCH is a fixed rate (30 kbps, SF=256) downlink physical channels used to carry the BCH transport channel. The BCH transport channel has a fixed transport format combination, hence the Primary CCPCH does not support TFCI. The P-CCPCH uses QPSK modulation.
+
+Figure 18ivA shows the frame structure of the P-CCPCH. The P-CCPCH is not transmitted during the first and last 256 chips of each slot. Instead, Primary SCH and Secondary SCH are transmitted during first DTX period and T-CPICH is transmitted during the last DTX period.
+
+
+
+Figure 18ivA: Frame structure for Primary Common Control Physical Channel. The diagram shows a single slot structure at the top and a sequence of slots at the bottom. The top part shows a slot with a total duration of T\_slot = 2560 chips, 20 bits. It contains a 'Data' field of N\_data1 = 16 bits, flanked by two '(Tx OFF)' regions of 256 chips each. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with dashed lines indicating the continuation of the sequence.
+
+**Figure 18ivA: Frame structure for Primary Common Control Physical Channel**
+
+#### 5.8.2.4 Secondary common control physical channel (S-CCPCH)
+
+The Secondary CCPCH is used to carry FACH transport channels.
+
+For MBSFN IMB, there are two types of Secondary CCPCH:
+
+- Secondary CCPCH frame type 1; consists of 15 slots per radio frame
+- Secondary CCPCH frame type 2; consists of 3 slots (i.e. one sub-frame) per radio frame.
+
+Both of the Secondary CCPCH frame types may include TFCI in order to support multiple transport format combinations. It is the UTRAN that determines if a TFCI should be transmitted, hence making it mandatory for all UEs to support the use of TFCI. The structures of the Secondary CCPCH frame type 1 and Secondary CCPCH frame type 2 are shown in figure 18vA and figure 18viA, respectively.
+
+Physical channel bits of Secondary CCPCH frame type 1 slots are mapped to a QPSK signal point constellation whereas physical channel bits of Secondary CCPCH frame type 2 can be mapped either to QPSK or 16QAM signal point constellations. In the case of Secondary CCPCH frame type 2, the signal point constellation to be used for the data field is given by higher layer signalling.
+
+
+
+Figure 18vA: Frame structure for Secondary Common Control Physical Channel frame type 1. The diagram shows a single slot structure at the top and a sequence of slots at the bottom. The top part shows a slot with a total duration of T\_slot = 2560 chips. It contains a 'TFCI' field of N\_TFCI bits, a 'Data' field of N\_data1 bits, and a '(Tx OFF)' region of 256 chips. The total duration of the TFCI and Data fields is 18 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with dashed lines indicating the continuation of the sequence. The entire sequence of 15 slots is labeled as '1 radio frame: T\_f = 10 ms'.
+
+**Figure 18vA: Frame structure for Secondary Common Control Physical Channel frame type 1**
+
+
+
+Figure 18viA: Frame structure for Secondary Common Control Physical Channel frame type 2. The diagram shows a hierarchical view of the frame structure. At the top, a slot is shown with a TFCI field (N\_TFCI bits) and a Data field (N\_data1 bits). The total number of bits in a slot is m\*144 bits (where m = 2, 4). The slot duration is T\_slot = 2560 chips. The slot is divided into three parts: Slot #0, Slot #1, and Slot #2. The total duration of a subframe is T\_subframe = 7680 chips. The subframe is shown within a radio frame of duration T\_f = 10 ms. The radio frame is divided into subframes, with Subframe #i shown. The start position of the subframe within the radio frame is determined by the sub-frame index i. The diagram also indicates 'Tx OFF' periods at the beginning and end of the radio frame, and a gap of i\*7680 chips between the start of the radio frame and the start of Subframe #i.
+
+**Figure 18viA: Frame structure for Secondary Common Control Physical Channel frame type 2**
+
+The parameter $m$ in figure 18viA determines the total number of bits per Secondary CCPCH slot. The parameter $m$ takes the value of 2 for QPSK modulation and 4 for 16-QAM modulation. The sub-frame index $i$ in figure 18viA determines the start position of the sub-frame within the radio frame.
+
+The values for the number of bits per field are given in table 8iA in which the channel bit and symbol rates are the rates immediately before spreading.
+
+A FACH transport channel may be mapped to one Secondary CCPCH of frame type 1 or to one or more Secondary CCPCHs of frame type 2 that reside within the same sub-frame.
+
+**Table 8iA: Secondary CCPCH frame type 1 and 2 fields**
+
+| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (kbps) | SF | S-CCPCH frame type | Bits/Frame | Bits/Slot | N_data1 | N_TFCI |
+|----------------|-------------------------|----------------------------|-----|--------------------|------------|-----------|---------|--------|
+| 0 | 30 | 15 | 256 | 1 | 270 | 18 | 18 | 0 |
+| 1 | 30 | 15 | 256 | 1 | 270 | 18 | 16 | 2 |
+| 2 | 480 | 240 | 16 | 2 | 864 | 288 | 288 | 0 |
+| 3 | 480 | 240 | 16 | 2 | 864 | 288 | 272 | 16 |
+| 4* | 960 | 240 | 16 | 2 | 1728 | 576 | 576 | 0 |
+| 5* | 960 | 240 | 16 | 2 | 1728 | 576 | 560 | 16** |
+
+\* Slot formats applicable to 16QAM.
+
+\*\* This indicates that the number of modulation symbols occupied by TFCI is 4. As described in [7] and [8], QPSK modulation is applied to 8 TFCI bits per slot which results in the same number of 4 TFCI symbols
+
+For slot formats using TFCI, the TFCI value in each radio frame corresponds to a certain transport format combination of the FACHs currently in use. This correspondence is (re-)negotiated at each FACH addition/removal. The mapping of the TFCI bits onto slots for the IMB option is described in [7].
+
+In the case of S-CCPCH frame type 1, when an S-CCPCH CCTrCH carries TFCI, the TFCI field shall be present on all slots of the radio frame. In this case there is only one S-CCPCH in the CCTrCH.
+
+In the case of S-CCPCH frame type 2, when an S-CCPCH CCTrCH carries TFCI, the TFCI field shall be present on all slots of the sub-frame for the S-CCPCH with the lowest channelization code index in the CCTrCH. In this case, the TFCI field shall not be present on the other S-CCPCHs of the same CCTrCH.
+
+### 5.8.2.5 Synchronisation channel (SCH)
+
+The Synchronisation Channel (SCH) is a downlink signal used for cell search and radio frame synchronisation on the MBSFN carrier. The SCH consists of two sub channels, the Primary and Secondary SCH. The 10 ms radio frames of the Primary and Secondary SCH are divided into 15 slots, each of length 2560 chips. Figure 18viiA illustrates the structure of the SCH radio frame.
+
+
+
+Diagram of Synchronisation Channel (SCH) structure showing Primary SCH (ac\_p) and Secondary SCH (ac\_s^{i,k}) across 15 slots (Slot #0 to Slot #14) within a 10 ms radio frame. Each slot has a length of 2560 chips. The Primary SCH is transmitted in every slot, while the Secondary SCH is transmitted in parallel with the Primary SCH, with different scrambling codes per slot.
+
+Figure 18viiA: Structure of Synchronisation Channel (SCH)
+
+The Primary SCH consists of a modulated code of length 256 chips, the Primary Synchronisation Code (PSC) denoted $c_p$ in figure 18viiA, transmitted once every slot. The PSC is the same for every cell in the system.
+
+The Secondary SCH consists of repeatedly transmitting a length 15 sequence of modulated codes of length 256 chips, the Secondary Synchronisation Codes (SSC), transmitted in parallel with the Primary SCH. The SSC is denoted $c_s^{i,k}$ in figure 18viiA, where $i = 0, 1, \dots, 7$ is the number of the scrambling code group, and $k = 0, 1, \dots, 14$ is the slot number. Each SSC is chosen from a set of 16 different codes of length 256. This sequence on the Secondary SCH indicates which of the code groups the cell's downlink scrambling code belongs to.
+
+The primary and secondary synchronization codes for the MBSFN IMB option, defined in [8], are modulated by the symbol $a = -1$ .
+
+### 5.8.2.6 The MBMS indicator channel (MICH)
+
+The MBMS Indicator Channel (MICH) is a fixed rate (SF=256) physical channel used to carry the MBMS notification indicators. The MICH is always associated with an S-CCPCH frame type 1 to which a FACH transport channel carrying MBMS control data is mapped. MICH uses QPSK modulation.
+
+Figure 18viiiA illustrates the frame structure of the MICH where the 10 ms radio frames of the MICH are divided into 15 slots, each of length 2560 chips. One MICH radio frame of length 10 ms consists of 270 bits ( $b_0, b_1, \dots, b_{269}$ ). Of these, 256 bits ( $b_0, b_1, \dots, b_{255}$ ) are used to carry notification indicators. The remaining 14 bits are not formally part of the MICH and shall not be transmitted (DTX). This implies that the transmitter is turned off during the last 2048 chips of slot #14 in every radio frame.
+
+
+
+Diagram of MBMS Indicator Channel (MICH) structure showing a 10 ms radio frame divided into 15 slots (Slot #0 to Slot #14). Each slot has a length of 2560 chips (T\_slot = 2560 chips, 20 bits). The Data (N\_data1 = 18 bits) is transmitted in the first 256 chips of each slot. The last 2048 chips of Slot #14 are not transmitted (Tx OFF).
+
+**Figure 18viiiA: Frame structure for the MBMS Indicator Channel (MICH)**
+
+In each MICH frame, $N_n$ notification indicators $\{N_0, \dots, N_{N_n-1}\}$ are transmitted, where $N_n=16, 32, 64, \text{ or } 128$ .
+
+The NI calculated by higher layers is associated to the index $q$ of the notification indicator $N_q$ , where $q$ is computed as a function of the NI computed by higher layers, the SFN of the P-CCPCH radio frame during which the start of the MICH radio frame occurs, and the number of notification indicators per frame ( $N_n$ ):
+
+where $G = 2^{16}$ , $C = 25033$ and NI is the 16 bit Notification Indicator calculated by higher layers.
+
+The set of NI signalled over Iub indicates all higher layer NI values for which the associated notification indicator on MICH shall be set to 1 during the corresponding modification period. Hence, the calculation in the formula above shall be performed in the Node B every MICH frame for each NI signalled over Iub to make the association between NI and $q$ and set the related $N_q$ to 1. All other notification indicators on MICH shall be set to 0.
+
+The mapping from $\{N_0, \dots, N_{N_n-1}\}$ to the MICH bits $\{b_0, \dots, b_{255}\}$ are according to table 8iiA.
+
+**Table 8iiA: Mapping of notification indicators $N_q$ to MICH bits**
+
+| Number of notification indicators per frame ( $N_n$ ) | $N_q = 1$ | $N_q = 0$ |
+|-------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------|
+| $N_n=16$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{1, 1, \dots, 1\}$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{0, 0, \dots, 0\}$ |
+| $N_n=32$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{1, 1, \dots, 1\}$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{0, 0, \dots, 0\}$ |
+| $N_n=64$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{1, 1, \dots, 1\}$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{0, 0, \dots, 0\}$ |
+| $N_n=128$ | $\{b_{2q}, b_{2q+1}\} = \{1, 1\}$ | $\{b_{2q}, b_{2q+1}\} = \{0, 0\}$ |
+
+### 5.8.3 Timing relationship between physical channels
+
+Timing between the common physical channels is summarized in figure 18ixA. The P-CCPCH, on which the cell SFN is transmitted, is used as timing reference for all the physical channels. The SCH, P-CPICH, T-CPICH, P-CCPCH and S-CCPCH frame types 1 and 2 have identical radio frame timings. The sub-frame number $i$ of an S-CCPCH frame type 2 radio frame is signalled by higher layers. The start position of an S-CCPCH frame type 2 sub-frame is then given by, $\tau$ , chips after the start of the radio frame.
+
+The frame timing of MICH is advanced by $\tau_{MICH} = 3$ slots (7680 chips) with respect to the timings of the other physical channels.
+
+
+
+The diagram illustrates the timing of downlink physical channels across two 10 ms radio frames. The channels shown are:
+
+- Primary SCH**: Continuous bursts across both frames.
+- Secondary SCH**: Continuous bursts across both frames.
+- P-CPICH**: Continuous bursts across both frames.
+- T-CPICH**: Continuous bursts across both frames.
+- P-CCPCH**: Divided into two 10 ms frames: "Radio frame with (SFN modulo 2) = 0" and "Radio frame with (SFN modulo 2) = 1".
+- S-CCPCH frame type 1**: Continuous bursts across both frames.
+- S-CCPCH frame type 2**: Shows a subframe #i starting at an offset of $i \cdot 7680$ chips from the start of the first radio frame.
+- MICH**: Shows a midamble period of $\tau_{\text{MICH}}$ starting in the second radio frame.
+
+The total duration of the two radio frames is 20 ms, with each frame being 10 ms long.
+
+Figure 18ixA: Radio frame and sub-frame timing of downlink physical channels. The diagram shows the timing of various physical channels over two consecutive 10 ms radio frames. The channels are Primary SCH, Secondary SCH, P-CPICH, T-CPICH, P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2, and MICH. The P-CCPCH channel is divided into two 10 ms frames: 'Radio frame with (SFN modulo 2) = 0' and 'Radio frame with (SFN modulo 2) = 1'. The S-CCPCH frame type 2 channel shows a subframe #i starting at an offset of i\*7680 chips. The MICH channel shows a midamble period of tau\_MICH.
+
+Figure 18ixA: Radio frame and sub-frame timing of downlink physical channels
+
+## 5A Physical channels for the 1.28 Mcps option
+
+All physical channels take three-layer structure with respect to timeslots, radio frames and system frame numbering (SFN), see [14]. Depending on the resource allocation, the configuration of radio frames or timeslots becomes different. All physical channels need guard symbols in every timeslot. The time slots are used in the sense of a TDMA component to separate different user signals in the time and the code domain. The physical channel signal format for 1.28 Mcps TDD is presented in figure 18A.
+
+A physical channel in TDD is a burst, which is transmitted in a particular timeslot within allocated Radio Frames. The allocation can be continuous, i.e. the time slot in every frame is allocated to the physical channel or discontinuous, i.e. the time slot in a subset of all frames is allocated only. A burst is the combination of a data part, a midamble and a guard period or only a midamble for standalone midamble channel. The duration of a burst is one time slot. Note when in the entire carrier dedicated to MBSFN operation, a burst is the combination of a preamble and a data part. Several bursts can be transmitted at the same time from one transmitter. In this case, the data part must use different OVSF channelisation codes, but the same scrambling code. The midamble part has to use the same basic midamble code, but can use different midambles. In a multi-frequency cell the midamble parts in different carrier shall also have to use the same basic midamble code, but can use different midambles. Note when in MBSFN operation, a midamble or preamble is not necessarily cell-specific.
+
+
+
+The diagram illustrates the hierarchical structure of a radio frame. At the top level, a 'Radio frame (10ms)' is shown, divided into two equal parts labeled 'frame #i' and 'frame #i+1'. Below this, a 'subframe (5ms)' is shown, which is a portion of a radio frame, divided into 'subframe #1' and 'subframe #2'. Dotted lines connect the subframe level to the timeslot level. At the bottom, a series of timeslots are shown, labeled 'timeslot #0', 'timeslot #1', 'timeslot #2', and 'timeslot #6', with gaps between them.
+
+Figure 18A: Physical channel signal format for 1.28Mcps TDD option. The diagram shows a hierarchy of time intervals: a Radio frame (10ms) containing frame #i and frame #i+1; a subframe (5ms) containing subframe #1 and subframe #2; and timeslots #0, #1, #2, and #6.
+
+**Figure 18A: Physical channel signal format for 1.28Mcps TDD option**
+
+The data part of the burst is spread with a combination of channelisation code and scrambling code. The channelisation code is a OVSF code, that can have a spreading factor of 1, 2, 4, 8, or 16. The data rate of the physical channel is depending on the used spreading factor of the used OVSF code.
+
+So a physical channel is defined by frequency, timeslot, channelisation code, burst type and Radio Frame allocation. The scrambling code and the basic midamble code or preamble code are broadcast and may be constant within a cell. When a physical channel is established, a start frame is given. The physical channels can either be of infinite duration, or a duration for the allocation can be defined.
+
+### 5A.1 Frame structure
+
+The TDMA frame has duration of 10 ms and is divided into 2 sub-frames of 5ms. The frame structure for each sub-frame in the 10ms frame length is the same.
+
+
+
+The diagram shows the internal structure of a 5ms subframe, which contains 6400 chips. It is divided into 7 traffic time slots. The first slot is labeled 'DwPTS (96chips)' and contains a downward arrow. This is followed by a 'GP (96chips)' (Guard Period) section. Then 'UpPTS (160chips)' is shown with an upward arrow. The remaining 4 slots are traffic slots: the first has an upward arrow, the second has an upward arrow, the third has a downward arrow, and the fourth has a downward arrow. Labels 'Switching Point' with arrows point to the boundaries between the DwPTS/GP section and the UpPTS section, and between the UpPTS section and the first traffic slot.
+
+Figure 18B: Structure of the sub-frame for 1.28Mcps TDD option. The diagram shows a 5ms subframe (6400chip) divided into 7 traffic time slots. It labels DwPTS (96chips), GP (96chips), UpPTS (160chips), and Switching Points.
+
+**Figure 18B: Structure of the sub-frame for 1.28Mcps TDD option**
+
+- a) Time slot#n (n from 0 to 6): the nth traffic time slot, 864 chips duration;
+- b) DwPTS: downlink pilot time slot, 96 chips duration;
+- c) UpPTS: uplink pilot time slot, 160 chips duration;
+- d) GP: main guard period for TDD operation, 96 chips duration;
+
+In Figure 18B, the total number of traffic time slots for uplink and downlink is 7, and the length for each traffic time slot is 864 chips duration. Among the 7 traffic time slots, time slot#0 is always allocated as downlink while time slot#1 is always allocated as uplink. The time slots for the uplink and the downlink are separated by switching points. Between the downlink time slots and uplink time slots, the special period is the switching point to separate the uplink and
+
+downlink. In each sub-frame of 5ms for 1.28Mcps option, there are two switching points (uplink to downlink and vice versa).
+
+Using the above frame structure, the 1.28Mcps TDD option can operate on both symmetric and asymmetric mode by properly configuring the number of downlink and uplink time slots. In any configuration at least one time slot (time slot#0) has to be allocated for the downlink and at least one time slot has to be allocated for the uplink (time slot#1).
+
+In case of entire carrier dedicated to MBSFN, no uplink timeslot is used, and DwPTS, UpPTS and GP(96 chips duration) are combined into one short timeslot, the duration of which is 0.275ms.
+
+In a multi-frequency cell the traffic time slots allocated for uplink and downlink pair(s) for one UE should be on the same carrier.
+
+Examples for symmetric and asymmetric UL/DL allocations are given in figure 18C.
+
+
+
+**Symmetric DL/UL allocation**
+
+**Asymmetric DL/UL allocation**
+
+**Entire carrier dedicated to MBSFN**
+
+Figure 18C: 1.28Mcps TDD sub-frame structure examples. The diagram shows three examples of 5ms sub-frames, each divided into 10 time slots. The first example, 'Symmetric DL/UL allocation', shows 5 downlink (DL) slots and 5 uplink (UL) slots, alternating. The second example, 'Asymmetric DL/UL allocation', shows 7 DL slots and 3 UL slots. The third example, 'Entire carrier dedicated to MBSFN', shows 10 DL slots and 0 UL slots. Each sub-frame is labeled '5 ms' above it.
+
+**Figure 18C: 1.28Mcps TDD sub-frame structure examples**
+
+Note 1: In a multi-frequency cell, it is suggested the switching point configuration on secondary frequencies to be the same as that on primary frequency.
+
+## 5A.2 Dedicated physical channel (DPCH)
+
+The DCH as described in subclause 4.1.1 'Dedicated transport channels' is mapped onto the dedicated physical channel.
+
+### 5A.2.1 Spreading
+
+The spreading of physical channels is the same as in 3.84 Mcps TDD (cf. 5.2.1 'Spreading'). When there are more than two uplink physical channels to be transmitted in one timeslot, UE shall always guarantee the transmission of DPCH with data to be transmitted and non-scheduled E-PUCH.
+
+### 5A.2.2 Burst Format
+
+A traffic burst consists of two data symbol fields, a midamble of 144 chips and a guard period. The data fields of the burst are 352 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8A below. The guard period is 16 chip periods long.
+
+The burst format is shown in Figure 18D. The contents of the traffic burst fields is described in table 8B.
+
+**Table 8A: number of symbols per data field in a traffic burst**
+
+| Spreading factor (Q) | Number of symbols (N) per data field in Burst |
+|----------------------|-----------------------------------------------|
+| 1 | 352 |
+| 2 | 176 |
+| 4 | 88 |
+| 8 | 44 |
+| 16 | 22 |
+
+**Table 8B: The contents of the traffic burst format fields**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | Contents of field |
+|------------------|--------------------------|----------------------------|-------------------|
+| 0-351 | 352 | cf table 8A | Data symbols |
+| 352-495 | 144 | - | Midamble |
+| 496-847 | 352 | cf table 8A | Data symbols |
+| 848-863 | 16 | - | Guard period |
+
+
+
+| | | | |
+|---------------------------|-----------------------|---------------------------|----------------|
+| Data symbols
352 chips | Midamble
144 chips | Data symbols
352 chips | GP
16
CP |
+|---------------------------|-----------------------|---------------------------|----------------|
+
+$864 \cdot T_c$
+
+Diagram of burst structure showing four fields: Data symbols (352 chips), Midamble (144 chips), Data symbols (352 chips), and Guard Period (16 chips). A double-headed arrow below indicates the total duration is 864 \* Tc.
+
+**Figure 18D: Burst structure of the traffic burst format (GP denotes the guard period and CP the chip periods)**
+
+## 5A.2.2a Dedicated carrier MBSFN Burst Format
+
+In this case, there are two bursts, one is MBSFN Traffic burst (MT burst) for 7 normal timeslots, and the other is MBSFN Special burst (MS burst) for 1 short timeslot. Both of them consist of a preamble and a data symbol field, the lengths of which are different for the individual bursts. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 8A.a.
+
+**Table 8A.a: number of symbols per data field in a MBSFN burst**
+
+| Spreading factor (Q) | Number of symbols (N) per data field in Burst | |
+|----------------------|-----------------------------------------------|----------|
+| | MT Burst | MS Burst |
+| 1 | 768 | N/A |
+| 2 | 384 | N/A |
+| 16 | 48 | 16 |
+
+*Note: MS burst only supports SF=16.*
+
+The support of both bursts is mandatory and only used in dedicated carrier MBSFN. The both different bursts defined here are well suited for this application, as described in the following paragraphs.
+
+The MT burst can be used for the regular timeslots, the duration of which is 0.675ms. The data fields of the MT burst are 768 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8A.a above. The preamble of MT burst has a length of 96 chips. The MT burst is shown in Figure 18D.a. The contents of the burst fields are described in table 8B.a.
+
+**Table 8B.a: The contents of the MT burst**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | Contents of field |
+|------------------|--------------------------|----------------------------|-------------------|
+| 0-95 | 96 | - | Preamble |
+| 96-863 | 768 | cf table 8A.a | Data symbols |
+
+
+
+Figure 18D.a: Burst structure of the MT burst. The diagram shows a horizontal rectangle divided into two parts by a vertical line. Below the rectangle is a double-headed arrow spanning its entire length.
+
+**Figure 18D.a: Burst structure of the MT burst**
+
+The MS burst can be used for the short timeslot, the duration of which is 0.275ms. The data fields of the MS burst are 256 chips long. The corresponding number of symbols is 16, as indicated in table 8A.a above. The preamble of the MS burst has a length of 96 chips. The MS burst format is shown in Figure 18D.b. The contents of the burst fields are described in table 8B.b.
+
+**Table 8B.b: The contents of the MS burst**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | Contents of field |
+|------------------|--------------------------|----------------------------|-------------------|
+| 0-95 | 96 | - | Preamble |
+| 96-351 | 256 | cf table 8A.a | Data symbols |
+
+
+
+Figure 18D.b: Burst structure of the MS burst. The diagram shows a horizontal rectangle divided into two parts by a vertical line. Below the rectangle is a double-headed arrow spanning its entire length.
+
+**Figure 18D.b: Burst structure of the MS burst**
+
+### 5A.2.2.1 Transmission of TFCI
+
+The traffic burst format provides the possibility for transmission of TFCI in uplink and downlink.
+
+The transmission of TFCI is configured by higher Layers. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (*p*) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+The transmission of TFCI is done in the data parts of the respective physical channel, this means that TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. Hence the midamble structure and length is not changed.
+
+The TFCI code word bits are equally distributed between the two subframes and the respective data fields. The TFCI code word is to be transmitted possibly either directly adjacent to the midamble or after the SS and TPC symbols. Figure 18E shows the position of the TFCI code word in a traffic burst, if neither SS nor TPC are transmitted. Figure 18F shows the position of the TFCI code word in a traffic burst, if SS and TPC are transmitted.
+
+Error:
+
+60
+
+Error: Reference source not
+
+
+
+Figure 18E: Position of the TFCI code word in the traffic burst in case of no TPC and SS in 1.28 Mcps TDD. The diagram shows a 10ms Radio Frame divided into two 5ms Sub-frames. Each Sub-frame contains a Time slot x (864 Chips). Each Time slot x is further divided into four parts: 1st part of TFCI code word (Data symbols), 2nd part of TFCI code word (Midamble), 3rd part of TFCI code word (Data symbols), and 4th part of TFCI code word (Data symbols with GP).
+
+**Figure 18E: Position of the TFCI code word in the traffic burst in case of no TPC and SS in 1.28 Mcps TDD**
+
+
+
+Figure 18F: Position of the TFCI code word in the traffic burst in case of TPC and SS in 1.28 Mcps TDD. This diagram is similar to Figure 18E but includes SS symbols and TPC symbols. In each Time slot x, the sequence is: Data symbols (1st part of TFCI), Midamble, SS symbols, TPC symbols, Data symbols (2nd part of TFCI), GP. The same structure repeats for the 3rd and 4th parts of the TFCI code word.
+
+**Figure 18F: Position of the TFCI code word in the traffic burst in case of TPC and SS in 1.28 Mcps TDD**
+
+#### 5A.2.2.1a Transmission of TFCI for MT burst and MS burst
+
+Both MT burst and MS burst provide the possibility for transmission of TFCI in downlink. The procedure of transmitting TFCI is the same as 5A.2.2.
+
+The transmission of TFCI is done in the data parts of the respective physical channel, this means that TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. Hence the preamble structure and length is not changed.
+
+The TFCI code word bits are equally distributed among the four subframes and the respective data fields. The TFCI code word is to be transmitted directly at the beginning and at the end of data symbols. Figure 18E.a shows the position of the TFCI code word in the MT burst. Figure 18E.b shows the position of the TFCI code word in the MS burst.
+
+Note: when the modulation is 16QAM the number of the TFCI bits need be expanded. The procedure of expansion is detailed described in [7]
+
+
+
+Figure 18E.a: Position of the TFCI code word in the MT burst format in 1.28 Mcps TDD. The diagram shows four consecutive time slots. In each time slot, the TFCI code word is transmitted at the beginning and at the end of the data symbols, indicated by small rectangular blocks within the data symbol areas.
+
+**Figure 18E.a: Position of the TFCI code word in the MT burst format in 1.28 Mcps TDD**
+
+
+
+Figure 18E.b: Position of the TFCI code word in the MS burst format in 1.28 Mcps TDD. The diagram shows two identical burst structures. Each burst consists of a long horizontal rectangle with two smaller rectangles inside it, representing the TFCI code word. Arrows indicate the start and end of the TFCI code word within the burst. Below the bursts, a long double-headed arrow spans the entire width, indicating the total duration of the two bursts.
+
+Figure 18E.b: Position of the TFCI code word in the MS burst format in 1.28 Mcps TDD
+
+### 5A.2.2.2 Transmission of TPC
+
+In this section, transmission of TPC over dedicated physical channels is described. Optionally, UTRAN may configure some UL CCTrCH's to be controlled via TPC commands on PLCCH (for example in the case of HS-DSCH operation without an associated downlink DPCH). PLCCH is described in section 5A.3.13.
+
+Within the context of this subclause, only those TPC commands not borne by PLCCH (in the DL case) nor by PLCCH-controlled physical channels (in the UL case) are considered. That is to say that those UL timeslot/CCTrCH pairs controlled by PLCCH and those DL TPC commands mapped to PLCCH are excluded from consideration when deriving the mapping between UL/DL TPC commands and the UL/DL CCTrCH's they control. The association between PLCCH and UL timeslot/CCTrCH pair(s) is signalled by higher layers.
+
+The burst type for dedicated channels provides the possibility for transmission of TPC in uplink and downlink.
+
+The transmission of TPC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the SS information, which is transmitted after the midamble. Figure 18G shows the position of the TPC command in a traffic burst.
+
+For every user the TPC information is to be transmitted at least once per 5ms sub-frame. For each allocated timeslot it is signalled individually whether that timeslot carries TPC information or not. If applied in a timeslot, transmission of TPC symbols is done in the data parts of the traffic burst and they are transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+TPC symbols may also be transmitted on more than one physical channel in a time slot. For this purpose, higher layers allocate an additional number of $N_{TPC}$ physical channels, individually for each time slot. The TPC symbols shall then be transmitted using the physical channels with the $N_{TPC}+1$ lowest physical channel sequence numbers ( $p$ ) in that time slot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. If the rate matching function results in $N_{RM} < N_{TPC}+1$ remaining physical channels in this time slot, TPC symbols shall be transmitted only on the $N_{RM}$ remaining physical channels.
+
+The TPC symbols are spread with the same spreading factor (SF) and spreading code as the data parts of the respective physical channel.
+
+
+
+Figure 18G: Position of TPC information in the traffic burst in downlink and uplink. The diagram shows a traffic burst structure with five segments: 'Data symbols', 'Midamble', 'SS symbol(s)', 'TPC symbol(s)' (highlighted in yellow), and 'GP'. A double-headed arrow below the 'Midamble' segment is labeled '144 chips'. A longer double-headed arrow below the entire burst structure is labeled '864 Chips'. Arrows point from the labels 'SS symbol(s)' and 'TPC symbol(s)' to their respective segments.
+
+Figure 18G: Position of TPC information in the traffic burst in downlink and uplink
+
+For the number of TPC symbols per time slot there are 3 possibilities, that can be configured by higher layers, individually for each timeslot:
+
+- e) 1) one TPC symbol
+
+- f) 2) no TPC symbols
+- g) 3) 16/SF TPC symbols
+
+So, in case 3), when SF=1, there are 16 TPC symbols which correspond to 32 bits (for QPSK) and 48 bits (for 8PSK).
+
+In the following the uplink is described only. For the description of the downlink, downlink (DL) and uplink (UL) have to be interchanged.
+
+Each of the TPC symbols for uplink power control in the DL will be associated with an UL time slot and an UL CCTrCH pair. This association varies with
+
+- the number of allocated UL time slots and UL CCTrCHs on these time slots (time slot and CCTrCH pair) and
+- the allocated TPC symbols in the DL.
+
+In case a UE has
+
+- more than one channelisation code
+
+and/or
+
+- channelisation codes being of lower spreading factor than 16 and using 16/SF SS and 16/SF TPC symbols,
+
+the TPC commands for each UL time slot CCTrCH pair (all channelisation codes on that time slot belonging to the same time slot and CCTrCH pair have the same TPC command) will be distributed to the following rules:
+
+1. The UL time slots and CCTrCH pairs the TPC commands are intended for will be numbered from the first to the last UL time slot and CCTrCH pair allocated to the regarded UE (starting with 0). The number of a time slot and CCTrCH pair is smaller than the number of another time slot and CCTrCH pair within the same time slot if its spreading code with the lowest SC number according to the following table has a lower SC number than the spreading code with the lowest SC number of the other time slot and CCTrCH pair.
+2. The commanding TPC symbols on all DL CCTrCHs allocated to one UE are numbered consecutively starting with zero according to the following rules:
+ - a) The numbers of the TPC commands of a regarded DL time slot are lower than those of DL time slots being transmitted after that time slot
+ - b) Within a DL time slot the numbers of the TPC commands of a regarded channelisation code are lower than those of channelisation codes having a higher spreading code number
+
+The spreading code number is defined by the following table (see[8]):
+
+| SC number | SF (Q) | Walsh code number (k) |
+|-----------|--------|-----------------------|
+| 0 | 16 | $c_{Q=16}^{(k=1)}$ |
+| | ... | |
+| 15 | 16 | $c_{Q=16}^{(k=16)}$ |
+| 16 | 8 | $c_{Q=8}^{(k=1)}$ |
+| | ... | |
+| 23 | 8 | $c_{Q=8}^{(k=8)}$ |
+| 24 | 4 | $c_{Q=4}^{(k=1)}$ |
+| | ... | |
+| 27 | 4 | $c_{Q=4}^{(k=4)}$ |
+| 28 | 2 | $c_{Q=2}^{(k=1)}$ |
+| 29 | 2 | $c_{Q=2}^{(k=2)}$ |
+| 30 | 1 | $c_{Q=1}^{(k=1)}$ |
+
+Note: Spreading factors 2-8 are not used in DL
+
+- c) Within a channelisation code numbers of the TPC commands are lower than those of TPC commands being transmitted after that time
+
+The following equation is used to determine the UL time slot which is controlled by the regarded TPC symbol in the DL:
+
+,
+
+where
+
+$UL_{pos}$ is the number of the controlled uplink time slot and CCTrCH pairs.
+
+$SFN'$ is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can be derived from $SFN'$ by
+
+$SFN = SFN' \text{ div } 2$ , where div is the remainder free division operation.
+
+$N_{UL\_PCsymbols}$ is the number of UL TPC symbols in a sub-frame (excluding those on PLCCH-controlled resources).
+
+$TPC_{DLpos}$ is the number of the regarded UL TPC symbol in the DL within the sub-frame.
+
+$N_{ULslot}$ is the number of UL slots and CCTrCH pairs in a sub-frame (excluding those associated with PLCCH).
+
+When one of the above parameters is changed due to higher layer reconfiguration, the new relationship between TPC symbols and controlled UL time slots shall be valid, beginning with the radio frame, for which the new parameters are set.
+
+In Annex CB two examples of the association of TPC commands to time slots and CCTrCH pairs are shown.
+
+Coding of TPC:
+
+The relationship between the TPC Bits and the transmitter power control command for QPSK is the same as in the 3.84Meps TDD cf. [5.2.2.5 'Transmission of TPC'].
+
+The relationship between the TPC Bits and the transmitter power control command for 8PSK is given in table 8C
+
+**Table 8C: TPC Bit Pattern for 8PSK**
+
+| TPC Bits | TPC command | Meaning |
+|----------|-------------|-------------------|
+| 000 | 'Down' | Decrease Tx Power |
+| 110 | 'Up' | Increase Tx Power |
+
+### 5A.2.2.3 Transmission of SS
+
+In this section, transmission of SS over dedicated physical channels is described. Optionally, UTRAN may configure some UL CCTrCH's to be controlled via SS commands on PLCCH (for example in the case of HS-DSCH operation without an associated downlink DPCH). PLCCH is described in section 5A.3.13.
+
+Within the context of this subclause, only those SS commands not borne by PLCCH are considered. That is to say that those UL timeslots controlled exclusively by PLCCH and those SS commands carried by PLCCH are excluded from consideration when deriving the mapping between DL SS commands and the UL timeslots they control. The association between PLCCH and UL timeslot/CCTrCH pair(s) is signalled by higher layers.
+
+The burst type for dedicated channels provides the possibility for transmission of uplink synchronisation control (ULSC).
+
+The transmission of ULSC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The ULSC information is to be transmitted directly after the midamble. Figure 18H shows the position of the SS command in a traffic burst.
+
+For every user the ULSC information shall be transmitted at least once per transmitted sub-frame.
+
+For each allocated timeslot it is signalled individually whether that timeslot carries ULSC information or not. If applied in a time slot, transmission of SS symbols is done in the data parts of the traffic burst and they are transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+SS symbols may also be transmitted on more than one physical channel in a time slot. For this purpose, higher layers allocate an additional number of $N_{SS}$ physical channels, individually for each time slot. The SS symbols shall then be transmitted using the physical channels with the $N_{SS}+1$ lowest physical channel sequence numbers ( $p$ ) in that time slot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. If the rate matching function results in $N_{RM} < N_{SS}+1$ remaining physical channels in this time slot, SS symbols shall be transmitted only on the $N_{RM}$ remaining physical channels.
+
+The SS symbols are spread with the same spreading factor (SF) and spreading code as the data parts of the respective physical channel.
+
+The SS is utilised to command a timing adjustment by $(k/8) T_c$ each $M$ sub-frames, where $T_c$ is the chip period. The $k$ and $M$ values are signalled by the network. The SS, as one of L1 signals, is to be transmitted once per 5ms sub-frame.
+
+$M$ (1-8) and $k$ (1-8) can be adjusted during call setup or readjusted during the call.
+
+Note: The smallest step for the SS signalled by the UTRAN is $1/8 T_c$ . For the UE capabilities regarding the SS adjustment of the UE it is suggested to set the tolerance for the executed command to be $[1/9; 1/7] T_c$ .
+
+
+
+The diagram illustrates the structure of a traffic burst. It consists of five segments: 'Data symbols', 'Midamble', a yellow box representing 'SS symbol(s)', 'Data symbols', and 'GP'. A double-headed arrow below the 'Midamble' segment is labeled '144 chips'. A longer double-headed arrow below the entire burst structure is labeled '864 Chips'. An arrow points from the text 'SS symbol(s)' to the yellow box.
+
+Diagram of a traffic burst structure showing the position of SS symbols.
+
+**Figure 18H: Position of ULSC information in the traffic burst (downlink and uplink)**
+
+Note that for the uplink where there is no SS symbol used, the SS symbol space is reserved for future use. This can keep UL and DL slots the same structure.
+
+For the number of SS symbols per time slot there are 3 possibilities, that can be configured by higher layers individually for each time slot:
+
+- one SS symbol
+- no SS symbol
+- 16/SF SS symbols
+
+So, in case 3, when SF=1, there are 16 SS symbols which correspond to 32 bits (for QPSK) and 48 bits (for 8PSK).
+
+Each of the SS symbols in the DL will be associated with an UL time slot depending on the allocated UL time slots and the allocated SS symbols in the DL.
+
+Note: Even though the different time slots of the UE are controlled with independent SS commands, the UE is not in need to execute SS commands leading to a deviation of more than [3] chip with respect to the average timing advance applied by the UE.
+
+The synchronisation shift commands for each UL time slot (all channelisation codes on that time slot have the same SS command) will be distributed to the following rules:
+
+1. The UL time slots the SS commands are intended for will be numbered from the first to the last UL time slot occupied by the regarded UE (starting with 0) considering all CCTrCHs allocated to that UE.
+2. The commanding SS symbols on all downlink CCTrCHs allocated to one UE are numbered consecutively starting with zero according to the following rules:
+ - a) The numbers of the SS commands of a regarded DL time slot are lower than those of DL time slots being transmitted after that time slot
+ - b) Within a DL time slot the numbers of the SS commands of a regarded channelisation code are lower than those of channelisation codes having a bigger spreading code number
+
+The spreading code number is defined by the following table: (see TS 25.223)
+
+| Spreading code number | SF (Q) | Walsh code number (k) |
+|-----------------------|------------------------------------------|-----------------------|
+| 0 | 16 | $c_{Q=16}^{(k=1)}$ |
+| | ... | |
+| 15 | 16 | $c_{Q=16}^{(k=16)}$ |
+| | Spreading factors 2-8 are not used in DL | |
+| 30 | 1 | $c_{Q=1}^{(k=1)}$ |
+
+- c) Within a channelisation code numbers of the SS commands are lower than those of SS commands being transmitted after that time
+
+The following equation is used to determine the UL time slot which is controlled by the regarded SS symbol:
+
+,
+
+where
+
+$UL_{pos}$ is the number of the controlled uplink time slot.
+
+$SFN'$ is the system frame number counting the sub-frames. The system frame number of the radio frames ( $SFN$ ) can be derived from $SFN'$ by
+
+$SFN = SFN' \bmod 2$ , where $\bmod$ is the remainder free division operation.
+
+$N_{SSsymbols}$ is the number of SS symbols in a sub-frame (excluding those associated with PLCCH).
+
+$SS_{pos}$ is the number of the regarded SS symbol within the sub-frame.
+
+$N_{ULslot}$ is the number of UL slots in a sub-frame (excluding those slots exclusively controlled by PLCCH).
+
+When one of the above parameters is changed due to higher layer reconfiguration, the new relationship between SS symbols and controlled UL time slots shall be valid, beginning with the radio frame, for which the new parameters are set.
+
+The relationship between the SS Bits and the SS command for QPSK is given in table 8D:
+
+**Table 8D: Coding of the SS for QPSK**
+
+| SS Bits | SS command | Meaning |
+|---------|--------------|---------------------------------------------|
+| 00 | 'Down' | Decrease synchronisation shift by $k/8 T_c$ |
+| 11 | 'Up' | Increase synchronisation shift by $k/8 T_c$ |
+| 01 | 'Do nothing' | No change |
+
+The relationship between the SS Bits and the SS command for 8PSK is given in table 8E:
+
+**Table 8E: Coding of the SS for 8PSK**
+
+| SS Bits | SS command | Meaning |
+|---------|--------------|---------------------------------------------|
+| 000 | 'Down' | Decrease synchronisation shift by $k/8 T_c$ |
+| 110 | 'Up' | Increase synchronisation shift by $k/8 T_c$ |
+| 011 | 'Do nothing' | No change |
+
+#### 5A.2.2.4 Timeslot formats
+
+The timeslot format depends on the spreading factor, the number of the TFCI code word bits, the number of SS and TPC symbols and the applied modulation scheme (QPSK/8PSK) as depicted in the following tables.
+
+## 5A.2.2.4.1 Timeslot formats for QPSK
+
+## 5A.2.2.4.1.1 Downlink timeslot formats
+
+Table 8F : Time slot formats for the Downlink
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 | 16 | 144 | 0 | 0 & 0 | 88 | 88 | 44 | 44 |
+| 1 | 16 | 144 | 4 | 0 & 0 | 88 | 86 | 42 | 44 |
+| 2 | 16 | 144 | 8 | 0 & 0 | 88 | 84 | 42 | 42 |
+| 3 | 16 | 144 | 16 | 0 & 0 | 88 | 80 | 40 | 40 |
+| 4 | 16 | 144 | 32 | 0 & 0 | 88 | 72 | 36 | 36 |
+| 5 | 16 | 144 | 0 | 2 & 2 | 88 | 84 | 44 | 40 |
+| 6 | 16 | 144 | 4 | 2 & 2 | 88 | 82 | 42 | 40 |
+| 7 | 16 | 144 | 8 | 2 & 2 | 88 | 80 | 42 | 38 |
+| 8 | 16 | 144 | 16 | 2 & 2 | 88 | 76 | 40 | 36 |
+| 9 | 16 | 144 | 32 | 2 & 2 | 88 | 68 | 36 | 32 |
+| 10 | 1 | 144 | 0 | 0 & 0 | 1408 | 1408 | 704 | 704 |
+| 11 | 1 | 144 | 4 | 0 & 0 | 1408 | 1406 | 702 | 704 |
+| 12 | 1 | 144 | 8 | 0 & 0 | 1408 | 1404 | 702 | 702 |
+| 13 | 1 | 144 | 16 | 0 & 0 | 1408 | 1400 | 700 | 700 |
+| 14 | 1 | 144 | 32 | 0 & 0 | 1408 | 1392 | 696 | 696 |
+| 15 | 1 | 144 | 0 | 2 & 2 | 1408 | 1404 | 704 | 700 |
+| 16 | 1 | 144 | 4 | 2 & 2 | 1408 | 1402 | 702 | 700 |
+| 17 | 1 | 144 | 8 | 2 & 2 | 1408 | 1400 | 702 | 698 |
+| 18 | 1 | 144 | 16 | 2 & 2 | 1408 | 1396 | 700 | 696 |
+| 19 | 1 | 144 | 32 | 2 & 2 | 1408 | 1388 | 696 | 692 |
+| 20 | 1 | 144 | 0 | 32 & 32 | 1408 | 1344 | 704 | 640 |
+| 21 | 1 | 144 | 4 | 32 & 32 | 1408 | 1342 | 702 | 640 |
+| 22 | 1 | 144 | 8 | 32 & 32 | 1408 | 1340 | 702 | 638 |
+| 23 | 1 | 144 | 16 | 32 & 32 | 1408 | 1336 | 700 | 636 |
+| 24 | 1 | 144 | 32 | 32 & 32 | 1408 | 1328 | 696 | 632 |
+
+5A.2.2.4.1.2
+
+Uplink timeslot formats
+
+**Table 8G : Time slot formats for the Uplink**
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 | 16 | 144 | 0 | 0 & 0 | 88 | 88 | 44 | 44 |
+| 1 | 16 | 144 | 4 | 0 & 0 | 88 | 86 | 42 | 44 |
+| 2 | 16 | 144 | 8 | 0 & 0 | 88 | 84 | 42 | 42 |
+| 3 | 16 | 144 | 16 | 0 & 0 | 88 | 80 | 40 | 40 |
+| 4 | 16 | 144 | 32 | 0 & 0 | 88 | 72 | 36 | 36 |
+| 5 | 16 | 144 | 0 | 2 & 2 | 88 | 84 | 44 | 40 |
+| 6 | 16 | 144 | 4 | 2 & 2 | 88 | 82 | 42 | 40 |
+| 7 | 16 | 144 | 8 | 2 & 2 | 88 | 80 | 42 | 38 |
+| 8 | 16 | 144 | 16 | 2 & 2 | 88 | 76 | 40 | 36 |
+| 9 | 16 | 144 | 32 | 2 & 2 | 88 | 68 | 36 | 32 |
+| 10 | 8 | 144 | 0 | 0 & 0 | 176 | 176 | 88 | 88 |
+| 11 | 8 | 144 | 4 | 0 & 0 | 176 | 174 | 86 | 88 |
+| 12 | 8 | 144 | 8 | 0 & 0 | 176 | 172 | 86 | 86 |
+| 13 | 8 | 144 | 16 | 0 & 0 | 176 | 168 | 84 | 84 |
+| 14 | 8 | 144 | 32 | 0 & 0 | 176 | 160 | 80 | 80 |
+| 15 | 8 | 144 | 0 | 2 & 2 | 176 | 172 | 88 | 84 |
+| 16 | 8 | 144 | 4 | 2 & 2 | 176 | 170 | 86 | 84 |
+| 17 | 8 | 144 | 8 | 2 & 2 | 176 | 168 | 86 | 82 |
+| 18 | 8 | 144 | 16 | 2 & 2 | 176 | 164 | 84 | 80 |
+| 19 | 8 | 144 | 32 | 2 & 2 | 176 | 156 | 80 | 76 |
+| 20 | 8 | 144 | 0 | 4 & 4 | 176 | 168 | 88 | 80 |
+| 21 | 8 | 144 | 4 | 4 & 4 | 176 | 166 | 86 | 80 |
+| 22 | 8 | 144 | 8 | 4 & 4 | 176 | 164 | 86 | 78 |
+| 23 | 8 | 144 | 16 | 4 & 4 | 176 | 160 | 84 | 76 |
+| 24 | 8 | 144 | 32 | 4 & 4 | 176 | 152 | 80 | 72 |
+| 25 | 4 | 144 | 0 | 0 & 0 | 352 | 352 | 176 | 176 |
+| 26 | 4 | 144 | 4 | 0 & 0 | 352 | 350 | 174 | 176 |
+| 27 | 4 | 144 | 8 | 0 & 0 | 352 | 348 | 174 | 174 |
+| 28 | 4 | 144 | 16 | 0 & 0 | 352 | 344 | 172 | 172 |
+| 29 | 4 | 144 | 32 | 0 & 0 | 352 | 336 | 168 | 168 |
+| 30 | 4 | 144 | 0 | 2 & 2 | 352 | 348 | 176 | 172 |
+| 31 | 4 | 144 | 4 | 2 & 2 | 352 | 346 | 174 | 172 |
+| 32 | 4 | 144 | 8 | 2 & 2 | 352 | 344 | 174 | 170 |
+| 33 | 4 | 144 | 16 | 2 & 2 | 352 | 340 | 172 | 168 |
+| 34 | 4 | 144 | 32 | 2 & 2 | 352 | 332 | 168 | 164 |
+| 35 | 4 | 144 | 0 | 8 & 8 | 352 | 336 | 176 | 160 |
+| 36 | 4 | 144 | 4 | 8 & 8 | 352 | 334 | 174 | 160 |
+| 37 | 4 | 144 | 8 | 8 & 8 | 352 | 332 | 174 | 158 |
+| 38 | 4 | 144 | 16 | 8 & 8 | 352 | 328 | 172 | 156 |
+| 39 | 4 | 144 | 32 | 8 & 8 | 352 | 320 | 168 | 152 |
+| 40 | 2 | 144 | 0 | 0 & 0 | 704 | 704 | 352 | 352 |
+| 41 | 2 | 144 | 4 | 0 & 0 | 704 | 702 | 350 | 352 |
+| 42 | 2 | 144 | 8 | 0 & 0 | 704 | 700 | 350 | 350 |
+| 43 | 2 | 144 | 16 | 0 & 0 | 704 | 696 | 348 | 348 |
+| 44 | 2 | 144 | 32 | 0 & 0 | 704 | 688 | 344 | 344 |
+| 45 | 2 | 144 | 0 | 2 & 2 | 704 | 700 | 352 | 348 |
+| 46 | 2 | 144 | 4 | 2 & 2 | 704 | 698 | 350 | 348 |
+| 47 | 2 | 144 | 8 | 2 & 2 | 704 | 696 | 350 | 346 |
+| 48 | 2 | 144 | 16 | 2 & 2 | 704 | 692 | 348 | 344 |
+| 49 | 2 | 144 | 32 | 2 & 2 | 704 | 684 | 344 | 340 |
+| 50 | 2 | 144 | 0 | 16 & 16 | 704 | 672 | 352 | 320 |
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 51 | 2 | 144 | 4 | 16 & 16 | 704 | 670 | 350 | 320 |
+| 52 | 2 | 144 | 8 | 16 & 16 | 704 | 668 | 350 | 318 |
+| 53 | 2 | 144 | 16 | 16 & 16 | 704 | 664 | 348 | 316 |
+| 54 | 2 | 144 | 32 | 16 & 16 | 704 | 656 | 344 | 312 |
+| 55 | 1 | 144 | 0 | 0 & 0 | 1408 | 1408 | 704 | 704 |
+| 56 | 1 | 144 | 4 | 0 & 0 | 1408 | 1406 | 702 | 704 |
+| 57 | 1 | 144 | 8 | 0 & 0 | 1408 | 1404 | 702 | 702 |
+| 58 | 1 | 144 | 16 | 0 & 0 | 1408 | 1400 | 700 | 700 |
+| 59 | 1 | 144 | 32 | 0 & 0 | 1408 | 1392 | 696 | 696 |
+| 60 | 1 | 144 | 0 | 2 & 2 | 1408 | 1404 | 704 | 700 |
+| 61 | 1 | 144 | 4 | 2 & 2 | 1408 | 1402 | 702 | 700 |
+| 62 | 1 | 144 | 8 | 2 & 2 | 1408 | 1400 | 702 | 698 |
+| 63 | 1 | 144 | 16 | 2 & 2 | 1408 | 1396 | 700 | 696 |
+| 64 | 1 | 144 | 32 | 2 & 2 | 1408 | 1388 | 696 | 692 |
+| 65 | 1 | 144 | 0 | 32 & 32 | 1408 | 1344 | 704 | 640 |
+| 66 | 1 | 144 | 4 | 32 & 32 | 1408 | 1342 | 702 | 640 |
+| 67 | 1 | 144 | 8 | 32 & 32 | 1408 | 1340 | 702 | 638 |
+| 68 | 1 | 144 | 16 | 32 & 32 | 1408 | 1336 | 700 | 636 |
+| 69 | 1 | 144 | 32 | 32 & 32 | 1408 | 1328 | 696 | 632 |
+
+## 5A.2.2.4.2 Time slot formats for 8PSK
+
+The Downlink and the Uplink timeslot formats are described together in the following table.
+
+**Table 8H: Timeslot formats for 8PSK modulation**
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 | 1 | 144 | 0 | 0 & 0 | 2112 | 2112 | 1056 | 1056 |
+| 1 | 1 | 144 | 6 | 0 & 0 | 2112 | 2109 | 1053 | 1056 |
+| 2 | 1 | 144 | 12 | 0 & 0 | 2112 | 2106 | 1053 | 1053 |
+| 3 | 1 | 144 | 24 | 0 & 0 | 2112 | 2100 | 1050 | 1050 |
+| 4 | 1 | 144 | 48 | 0 & 0 | 2112 | 2088 | 1044 | 1044 |
+| 5 | 1 | 144 | 0 | 3 & 3 | 2112 | 2106 | 1056 | 1050 |
+| 6 | 1 | 144 | 6 | 3 & 3 | 2112 | 2103 | 1053 | 1050 |
+| 7 | 1 | 144 | 12 | 3 & 3 | 2112 | 2100 | 1053 | 1047 |
+| 8 | 1 | 144 | 24 | 3 & 3 | 2112 | 2094 | 1050 | 1044 |
+| 9 | 1 | 144 | 48 | 3 & 3 | 2112 | 2082 | 1044 | 1038 |
+| 10 | 1 | 144 | 0 | 48 & 48 | 2112 | 2016 | 1056 | 960 |
+| 11 | 1 | 144 | 6 | 48 & 48 | 2112 | 2013 | 1053 | 960 |
+| 12 | 1 | 144 | 12 | 48 & 48 | 2112 | 2010 | 1053 | 957 |
+| 13 | 1 | 144 | 24 | 48 & 48 | 2112 | 2004 | 1050 | 954 |
+| 14 | 1 | 144 | 48 | 48 & 48 | 2112 | 1992 | 1044 | 948 |
+| 15 | 16 | 144 | 0 | 0 & 0 | 132 | 132 | 66 | 66 |
+| 16 | 16 | 144 | 6 | 0 & 0 | 132 | 129 | 63 | 66 |
+| 17 | 16 | 144 | 12 | 0 & 0 | 132 | 126 | 63 | 63 |
+| 18 | 16 | 144 | 24 | 0 & 0 | 132 | 120 | 60 | 60 |
+| 19 | 16 | 144 | 48 | 0 & 0 | 132 | 108 | 54 | 54 |
+| 20 | 16 | 144 | 0 | 3 & 3 | 132 | 126 | 66 | 60 |
+| 21 | 16 | 144 | 6 | 3 & 3 | 132 | 123 | 63 | 60 |
+| 22 | 16 | 144 | 12 | 3 & 3 | 132 | 120 | 63 | 57 |
+| 23 | 16 | 144 | 24 | 3 & 3 | 132 | 114 | 60 | 54 |
+| 24 | 16 | 144 | 48 | 3 & 3 | 132 | 102 | 54 | 48 |
+
+## 5A.2.2.4.3 Time slot formats for MBSFN
+
+Downlink timeslot formats using QPSK or 16QAM modulation is dedicated for MBSFN operation and is described in the following table.
+
+Table 8Ha : Time slot formats for MBSFN
+
+| Slot Format # | Spreading Factor | Midamble /preamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|-------------------------|------------------|-----------------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0(QPSK) * | 1 | 144 | 16 | 0 & 0 | 1408 | 1404 | 702 | 702 |
+| 1(QPSK) * | 16 | 144 | 16 | 0 & 0 | 88 | 84 | 42 | 42 |
+| 2(16QAM) * | 1 | 144 | 32 | 0 & 0 | 2816 | 2808 | 1404 | 1404 |
+| 3(16QAM) * | 16 | 144 | 32 | 0 & 0 | 176 | 168 | 84 | 84 |
+| 4(QPSK) ** | 1 | 96 | 16 | 0 & 0 | 1536 | 1532 | N/A | N/A |
+| 5(QPSK) ** | 2 | 96 | 16 | 0 & 0 | 768 | 764 | N/A | N/A |
+| 6(QPSK) ** | 16 | 96 | 16 | 0 & 0 | 96 | 92 | N/A | N/A |
+| 7(16QAM) ** | 1 | 96 | 32 | 0 & 0 | 3072 | 3064 | N/A | N/A |
+| 8(16QAM) ** | 2 | 96 | 16 | 0 & 0 | 1536 | 1528 | N/A | N/A |
+| 9(16QAM) ** | 16 | 96 | 32 | 0 & 0 | 192 | 184 | N/A | N/A |
+| 10(QPSK) *** | 16 | 96 | 16 | 0 & 0 | 32 | 24 | N/A | N/A |
+| 11(QPSK) *** | 16 | 96 | 0 | 0 & 0 | 32 | 32 | N/A | N/A |
+
+NOTE: \* denotes that these timeslot formats are used in the traffic burst for mixed carrier MBSFN. \*\* denotes that these timeslot formats are used in the MT burst for dedicated carrier MBSFN. \*\*\* denotes that these timeslot formats are used in the MS burst for dedicated carrier MBSFN. The burst in the dedicated carrier MBSFN has only one data field.
+
+### 5A.2.3 Training sequences for spread bursts
+
+In this subclause, the training sequences for usage as midambles are defined. The training sequences, i.e. midambles, of different users active in the same cell and same time slot are cyclically shifted versions of one single basic midamble code. In the case of MBSFN timeslots there is only a single midamble and this is derived from a single basic midamble code which is not necessarily cell-specific. The applicable basic midamble codes are given in Annex AA.1.
+
+The basic midamble codes in Annex AA.1 are listed in hexadecimal notation. The binary form of the basic midamble code shall be derived according to table 8I below.
+
+**Table 81: Mapping of 4 binary elements $m_i$ on a single hexadecimal digit:**
+
+| 4 binary elements $m_i$ | Mapped on hexadecimal digit |
+|-------------------------|-----------------------------|
+| -1 -1 -1 -1 | 0 |
+| -1 -1 -1 1 | 1 |
+| -1 -1 1 -1 | 2 |
+| -1 -1 1 1 | 3 |
+| -1 1 -1 -1 | 4 |
+| -1 1 -1 1 | 5 |
+| -1 1 1 -1 | 6 |
+| -1 1 1 1 | 7 |
+| 1 -1 -1 -1 | 8 |
+| 1 -1 -1 1 | 9 |
+| 1 -1 1 -1 | A |
+| 1 -1 1 1 | B |
+| 1 1 -1 -1 | C |
+| 1 1 -1 1 | D |
+| 1 1 1 -1 | E |
+| 1 1 1 1 | F |
+
+For each particular basic midamble code, its binary representation can be written as a vector $\mathbf{m}_P$ :
+
+$$\mathbf{m}_P = (m_1, m_2, \dots, m_P) \quad (1)$$
+
+According to Annex AA.1, the size of this vector $\mathbf{m}_P$ is $P=128$ . As QPSK modulation is used, the training sequences are transformed into a complex form, denoted as the complex vector $\underline{\mathbf{m}}_P$ :
+
+$$\underline{\mathbf{m}}_P = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_P) \quad (2)$$
+
+The elements $\underline{m}_i$ of $\underline{\mathbf{m}}_P$ are derived from elements $m_i$ of $\mathbf{m}_P$ using equation (3):
+
+$$\underline{m}_i = (j)^i \cdot m_i \text{ for all } i = 1, \dots, P \quad (3)$$
+
+Hence, the elements $\underline{m}_i$ of the complex basic midamble code are alternating real and imaginary.
+
+To derive the required training sequences, this vector $\underline{\mathbf{m}}_P$ is periodically extended to the size:
+
+$$i_{\max} = L_m + (K - 1)W \quad (4)$$
+
+Notes on equation (4):
+
+K and W are taken from Annex AA.1
+
+So we obtain a new vector $\underline{\mathbf{m}}$ containing the periodic basic midamble sequence:
+
+$$\underline{\mathbf{m}} = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{i_{\max}}) = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{L_m + (K-1)W}) \quad (5)$$
+
+The first $P$ elements of this vector $\underline{\mathbf{m}}$ are the same ones as in vector $\underline{\mathbf{m}}_P$ , the following elements repeat the beginning:
+
+$$\underline{m}_i = \underline{m}_{i-P} \text{ for the subset } i = (P+1), \dots, i_{\max} \quad (6)$$
+
+Using this periodic basic midamble sequence $\underline{\mathbf{m}}$ for each user $k$ a midamble $\underline{\mathbf{m}}^{(k)}$ of length $L_m$ is derived, which can be written as a user specific vector:
+
+$$\underline{m}^{(k)} = (\underline{m}_1^{(k)}, \underline{m}_2^{(k)}, \dots, \underline{m}_{L_m}^{(k)}) \quad (7)$$
+
+The $L_m$ midamble elements $\underline{m}_i^{(k)}$ are generated for each midamble of the $k$ users ( $k = 1, \dots, K$ ) based on:
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K-k)W} \text{ with } i = 1, \dots, L_m \text{ and } k = 1, \dots, K \quad (8)$$
+
+The midamble sequences derived according to equations (7) to (8) have complex values and are not subject to channelisation or scrambling process, i.e. the elements $\underline{m}_i^{(k)}$ represent complex chips for usage in the pulse shaping process at modulation.
+
+The term 'a midamble code set' or 'a midamble code family' denotes $K$ specific midamble codes $\underline{m}^{(k)}$ ; $k=1, \dots, K$ , based on a single basic midamble code $\underline{m}^P$ according to (1).
+
+### 5A.2.3a Training sequences for dedicated carrier MBSFN
+
+When the entire carrier is dedicated to MBSFN, preamble is used for the training sequences in each timeslot. In this case, for all timeslots employing MBSFN operation, only a single preamble is needed, i.e. $K_{\text{Cell}}=1$ , then all physical channels in such timeslots employ the same preamble with the same allocation strategies.
+
+For dedicated carrier MBSFN, the preamble has a fixed length of $L_p=96$ , and the generation of preamble is the same as in the 1.28 Mcps TDD cf. [5A.2.3 Training sequences for spread bursts], which is corresponding to:
+
+$$W = \left\lfloor \frac{P}{K} \right\rfloor, \quad K=1, P=64$$
+
+Note: that $\lfloor x \rfloor$ denotes the largest integer number less or equal to $x$ .
+
+The preamble is generated from one of the basic preamble codes shown in table AA.1a.
+
+The mapping of these Basic Preamble Codes to MBSFN Cell Parameters is shown in [8].
+
+### 5A.2.4 Beamforming
+
+Beamforming is same as that of the 3.84Mcps TDD, cf. [5.2.4 Beamforming ].
+
+Beamforming is not applicable to DL time slots with MBSFN transmission.
+
+## 5A.3 Common physical channels
+
+### 5A.3.1 Primary common control physical channel (P-CCPCH)
+
+The BCH as described in section 4.1.2 'Common Transport Channels' is mapped onto the Primary Common Control Physical Channels (P-CCPCH1 and P-CCPCH2). The position (time slot / code) of the P-CCPCHs is fixed in the 1.28Mcps TDD. The P-CCPCHs are mapped onto the first two code channels of timeslot#0 with spreading factor of 16. When the entire carrier is dedicated to MBSFN, the P-CCPCH is mapped onto the first two code channels of MS timeslot with spreading factor of 16. The P-CCPCH is always transmitted with an antenna pattern configuration that provides whole cell coverage.
+
+In a multi-frequency cell the carrier which transmits P-CCPCH is called the primary frequency and the others are called secondary frequencies. A multi-frequency cell has only one primary frequency.
+
+#### 5A.3.1.1 P-CCPCH Spreading
+
+The P-CCPCH uses fixed spreading with a spreading factor $SF = 16$ . The P-CCPCH1 and P-CCPCH2 always use channelisation code $c_{Q=6}^{(k=1)}$ and $c_{Q=6}^{(k=2)}$ respectively.
+
+### 5A.3.1.2 P-CCPCH Burst Format
+
+The burst format as described in section 5A.2.2 is used for the P-CCPCH. No TFCI is applied for the P-CCPCH.
+
+### 5A.3.1.3 P-CCPCH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for the P-CCPCH. When the entire carrier is dedicated to MBSFN, the training sequences, i.e. preambles, as described in subclause 5A.2.3.a are used for the P-CCPCH.
+
+## 5A.3.2 Secondary common control physical channel (S-CCPCH)
+
+PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements. The time slot and codes used for the S-CCPCH are broadcast on the BCH.
+
+In a multi-frequency cell S-CCPCH shall be transmitted only on the primary frequency.
+
+### 5A.3.2.1 S-CCPCH Spreading
+
+Except for physical channels in MBSFN time slot, the S-CCPCH uses fixed spreading with a spreading factor $SF = 16$ , as described in subclause 5A.2.1. And the S-CCPCH in MBSFN time slot may use spreading with spreading factor $SF = 1, 2$ or $16$ .
+
+Note: $SF=2$ is only used on dedicated MBSFN frequency.
+
+### 5A.3.2.2 S-CCPCH Burst Format
+
+The burst format as described in section 5A.2.2 is used for the S-CCPCH. TFCI may be applied for S-CCPCHs.
+
+### 5A.3.2.3 S-CCPCH Training sequences
+
+The training sequences, i.e. midambles, as described in the subclause 5A.2.3 are also used for the S-CCPCH.
+
+## 5A.3.3 Fast Physical Access CHannel (FPACH)
+
+The Fast Physical Access CHannel (FPACH) is used by the Node B to carry, in a single burst, the acknowledgement of a detected signature with timing and power level adjustment indication to an user equipment. FPACH makes use of one code with spreading factor 16, so that its burst is composed by 44 symbols. The spreading code, training sequence and time slot position are configured by the network and signalled on the BCH.
+
+In a multi-frequency cell the FPACH is transmitted on the primary frequency. The FPACH may also be also transmitted on the secondary frequency in case of handover or E-DCH procedure.
+
+### 5A.3.3.1 FPACH burst
+
+The FPACH burst contains 32 information bits. Table 8J reports the content description of the FPACH information bits and their priority order:
+
+Table 8J: FPACH information bits description
+
+| Information field | Length (in bits) |
+|----------------------------------------------------------------------------|------------------|
+| Signature Reference Number | 3 (MSB) |
+| Relative Sub-Frame Number | 2 |
+| Received starting position of the UpPCH ( $UpPCH_{Pos}$ ) | 11 |
+| Transmit Power Level Command for RACH message | 7 |
+| Extended part of Received starting position of the UpPCH ( $UpPCH_{Pos}$ ) | 2 |
+| Reserved bits (default value: 0) | 7 (LSB) |
+
+The use and generation of the information fields is explained in [9].
+
+#### 5A.3.3.1.1 Signature Reference Number
+
+The reported number corresponds to the numbering principle for the cell signatures as described in [8].
+
+The Signature Reference Number value range is 0 – 7 coded in 3 bits such that:
+
+bit sequence(0 0 0) corresponds to the first signature of the cell; ...; bit sequence (1 1 1) corresponds to the 8th signature of the cell.
+
+#### 5A.3.3.1.2 Relative Sub-Frame Number
+
+The Relative Sub-Frame Number value range is 0 – 3 coded such that:
+
+bit sequence (0 0) indicates one sub-frame difference; ...; bit sequence (1 1) indicates 4 sub-frame difference.
+
+#### 5A.3.3.1.3 Received starting position of the UpPCH (UpPCHPos)
+
+The size of UpPCHPos is extended to be 13bits and the received starting position of the UpPCH value range is 0 – 8191 coded such that:
+
+The 11 least significant bits (LSB) of UpPCHPos are transmitted in the Received starting position of the UpPCH information field and the 2 most significant bits (MSB) of UpPCHPos are transmitted in the first 2bits of the Reserve bits information field. Bit sequence (0 0 ... 0 0 0) indicates the received starting position zero chip; ...; bit sequence (1 1 ... 1 1 1) indicates the received starting position $8191 * 1/8$ chip.
+
+#### 5A.3.3.1.4 Transmit Power Level Command for the RACH message
+
+The transmit power level command is transmitted in 7 bits.
+
+#### 5A.3.3.2 FPACH Spreading
+
+The FPACH uses only spreading factor SF=16 as described in subclause 5A.3.3. The set of admissible spreading codes for use on the FPACH is broadcast on the BCH.
+
+#### 5A.3.3.3 FPACH Burst Format
+
+The burst format as described in section 5A.2.2 is used for the FPACH.
+
+#### 5A.3.3.4 FPACH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for FPACH.
+
+#### 5A.3.3.5 FPACH timeslot formats
+
+The FPACH uses slot format #0 of the DL time slot formats given in subclause 5A.2.2.4.1.1.
+
+### 5A.3.4 The physical random access channel (PRACH)
+
+The RACH as described in subclause 4.1.2 is mapped onto one or more uplink physical random access channels (PRACH). In such a way the capacity of RACH can be flexibly scaled depending on the operators need.
+
+In a multi-frequency cell the PRACH shall be transmitted only on the primary frequency.
+
+#### 5A.3.4.1 PRACH Spreading
+
+The uplink PRACH uses either spreading factor SF=16, SF=8 or SF=4 as described in subclause 5A.2.1. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH).
+
+#### 5A.3.4.2 PRACH Burst Format
+
+The burst format as described in section 5A.2.2 is used for the PRACH.
+
+### 5A.3.4.3 PRACH Training sequences
+
+The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a single periodic basic code. The basic midamble codes as described in subclause 5A.2.3 are used for PRACH.
+
+### 5A.3.4.4 PRACH timeslot formats
+
+The PRACH uses the following time slot formats taken from the uplink timeslot formats described in sub-clause 5A.2.2.4.1.2:
+
+| Spreading Factor | Slot Format # |
+|------------------|---------------|
+| 16 | 0 |
+| 8 | 10 |
+| 4 | 25 |
+
+### 5A.3.4.5 Association between Training Sequences and Channelisation Codes
+
+The association between training sequences and channelisation codes of PRACH in the 1.28McpsTDD is same as that of the DPCH.
+
+## 5A.3.5 The synchronisation channels (DwPCH, UpPCH)
+
+There are two dedicated physical synchronisation channels —DwPCH and UpPCH in each 5ms sub-frame of the 1.28Mcps TDD. The DwPCH is used for the down link synchronisation and the UpPCH is used for the uplink synchronisation.
+
+The position and the contents of the DwPCH are equal to the DwPTS as described in the subclause 5A.1., while the position and the contents of the UpPCH are equal to the UpPTS or other uplink access position indicated by the higher layers.
+
+The DwPCH is transmitted at each sub-frame with an antenna pattern configuration which provides whole cell coverage. Furthermore it is transmitted with a constant power level which is signalled by higher layers.
+
+In a multi-frequency cell the DwPCH shall be transmitted only on the primary frequency. The UpPCH is transmitted on the primary frequency. The UpPCH may also be transmitted on the secondary frequencies in case of handover and the E-RUCCH procedure.
+
+The burst structure of the DwPCH (DwPTS) is described in the figure 18I.
+
+
+
+| | |
+|-------------|------------------|
+| 75us | |
+| GP(32chips) | SYNC_DL(64chips) |
+
+Figure 18I: burst structure of the DwPCH ( DwPTS). The diagram shows a horizontal bar representing a 75us burst. Below the bar, it is divided into two segments: GP(32chips) on the left and SYNC\_DL(64chips) on the right.
+
+**Figure 18I: burst structure of the DwPCH ( DwPTS)**
+
+Note: 'GP' for 'Guard Period'
+
+The burst structure of the UpPCH (UpPTS) is described in the figure 18J.
+
+
+
+| | |
+|-------------------|-------------|
+| 125us | |
+| SYNC_UL(128chips) | GP(32chips) |
+
+Figure 18J: burst structure of the UpPCH ( UpPTS). The diagram shows a horizontal bar representing a 125us burst. Below the bar, it is divided into two segments: SYNC\_UL(128chips) on the left and GP(32chips) on the right.
+
+**Figure 18J: burst structure of the UpPCH ( UpPTS)**
+
+The SYNC-DL code in DwPCH and the SYNC-UL code in UpPCH are not spreaded. The details about the SYNC-DL and SYNC-UL code are described in the corresponding subclause and annex in [8].
+
+### 5A.3.6 Physical Uplink Shared Channel (PUSCH)
+
+For Physical Uplink Shared Channel (PUSCH) the burst structure of DPCH as described in subclause 5A.2 and the training sequences as described in subclause 5A.2.3 shall be used. PUSCH provides the possibility for transmission of TFCI, SS, and TPC in uplink.
+
+The PUSCH is common with 3.84 Mcps TDD with respect to Spreading and UE selection, cf. [5.3.5 Physical Uplink Shared Channel (PUSCH)].
+
+### 5A.3.7 Physical Downlink Shared Channel (PDSCH)
+
+For Physical Downlink Shared Channel (PDSCH) the burst structure of DPCH as described in subclause 5A.2 and the training sequences as described in subclause 5A.2.3 shall be used. PDSCH provides the possibility for transmission of TFCI, SS, and TPC in downlink.
+
+The PDSCH is common with 3.84 Mcps TDD with respect to Spreading and UE selection, cf. [5.3.6 Physical Downlink Shared Channel (PDSCH)].
+
+### 5A.3.8 The Page Indicator Channel (PICH)
+
+The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators.
+
+The PICH may be associated with
+
+- an S-CCPCH to which a PCH transport channel is mapped, or
+ - an HS-SCCH associated with the HS-PDSCH(s) to which an HS-DSCH transport channel is mapped, or
+- an HS-PDSCH to which an HS-DSCH transport channel carrying paging message is mapped.
+
+In a multi-frequency cell the PICH shall be transmitted only on the primary frequency.
+
+#### 5A.3.8.1 Mapping of Paging Indicators to the PICH bits
+
+Figure 18K depicts the structure of a PICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2 'Burst Format'] is used for the PICH. $N_{PIB}$ bits are used to carry the paging indicators, where $N_{PIB}=352$ .
+
+
+
+Figure 18K: Transmission and numbering of paging indicator carrying bits in the PICH bursts. The diagram shows two subframes, subframe #1 and subframe #2, each containing two bursts. Each burst is divided into three parts: 'Bits for Page Indication' (bits 0 to 11), 'Midamble' (bits 12 to 15), and 'Guard Period' (bits 16 to 19). The total number of bits per burst is 20. The subframes are labeled 'Time Slot #i, subframe #1' and 'Time Slot #i, subframe #2'. The bits are numbered from 0 to 19 within each burst. The subframe numbers are indicated by 'i ∈ {0, 2, 3, 4, 5, 6}'.
+
+**Figure 18K: Transmission and numbering of paging indicator carrying bits in the PICH bursts**
+
+Each paging indicator $P_q$ (where $P_q, q = 0, \dots, N_{PI}-1, P_q \in \{0, 1\}$ ) in one radio frame is mapped to the bits $\{S_{2L_{PI} \cdot q+1}, \dots, S_{2L_{PI} \cdot (q+1)}}\}$ in subframe #1 or subframe #2.
+
+The setting of the paging indicators and the corresponding PICH bits is described in [7].
+
+$N_{PI}$ paging indicators of length $L_{PI}=2, L_{PI}=4$ or $L_{PI}=8$ symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators $N_{PI}$ per radio frame is given by the paging indicator length, which is signalled by higher layers. In table 8K this number is shown for the different possibilities of paging indicator lengths.
+
+**Table 8K: Number $N_{PI}$ of paging indicators per radio frame for different paging indicator lengths $L_{PI}$**
+
+| | $L_{PI}=2$ | $L_{PI}=4$ | $L_{PI}=8$ |
+|--------------------------|------------|------------|------------|
+| $N_{PI}$ per radio frame | 88 | 44 | 22 |
+
+### 5A.3.8.2 Structure of the PICH over multiple radio frames
+
+The structure of the PICH over multiple radio frames is common with 3.84 Mcps TDD, cf. [5.3.7.2 Structure of the PICH over multiple radio frames]
+
+### 5A.3.9 High Speed Physical Downlink Shared Channel (HS-PDSCH)
+
+The HS-DSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH). In a multi-frequency HS-DSCH cell, HS-PDSCHs may be transmitted on one or more carriers in CELL\_DCH state and on only one carrier in CELL\_FACH, CELL\_PCH and URA\_PCH state in a TTI to a UE and the carriers allocated to the UE shall be on contiguous frequencies. In CELL\_FACH state, the HS-PDSCHs shall be transmitted on a same carrier as the one on which the uplink transmission resources are allocated to the UE. This carrier can be the primary frequency or the secondary frequency. In CELL\_PCH and URA\_PCH state, HS-PDSCHs can only be transmitted on the primary frequency. For UE not supporting multi-carrier HS-DSCH reception, the HS-PDSCHs shall be allocated on a same carrier as the one on which the associated DPCH or the uplink transmission resources is allocated.
+
+#### 5A.3.9.1 HS-PDSCH Spreading
+
+For the UEs not configured in MIMO mode, the HS-PDSCH shall use either spreading factor SF = 16 or SF=1, as described in 5.2.1.1.
+
+For the UEs configured in MIMO mode, if SF=16 is configured by higher layers [19] to be not supported for dual stream transmission, the HS-PDSCH shall use spreading factor SF=1 only. Otherwise, the HS-PDSCH shall use either spreading factor SF = 16 or SF=1.
+
+Spreading of the HS-PDSCH is common with 3.84 Mcps TDD, cf. [5.3.9.1 HS-PDSCH Spreading]
+
+#### 5A.3.9.2 HS-PDSCH Burst Format
+
+The burst format as described in section 5A.2.2 shall be used for the HS-PDSCH.
+
+#### 5A.3.9.3 HS-PDSCH Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the HS-PDSCH.
+
+#### 5A.3.9.4 UE Selection
+
+UE selection is common with 3.84 Mcps TDD, cf. [5.3.9.4 UE selection].
+
+#### 5A.3.9.5 HS-PDSCH timeslot formats
+
+An HS-PDSCH may use QPSK, 16QAM or 64QAM modulation symbols. The time slot formats are shown in table 8KA.
+
+**Table 8KA: Time slot formats for the HS-PDSCH**
+
+| Slot Format # | SF | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|----|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 (QPSK) | 16 | 144 | 0 | 0 & 0 | 88 | 88 | 44 | 44 |
+| 1 (16QAM) | 16 | 144 | 0 | 0 & 0 | 176 | 176 | 88 | 88 |
+| 2 (QPSK) | 1 | 144 | 0 | 0 & 0 | 1408 | 1408 | 704 | 704 |
+| 3 (16QAM) | 1 | 144 | 0 | 0 & 0 | 2816 | 2816 | 1408 | 1408 |
+| 4 (64QAM) | 16 | 144 | 0 | 0 & 0 | 264 | 264 | 132 | 132 |
+| 5 (64QAM) | 1 | 144 | 0 | 0 & 0 | 4224 | 4224 | 2112 | 2112 |
+| 6 (QPSK) | 16 | 144 | 0 | 2 & 2 | 88 | 84 | 44 | 40 |
+| 7 (16QAM) | 16 | 144 | 0 | 2 & 2 | 172 | 168 | 88 | 80 |
+| 8 (QPSK) | 1 | 144 | 0 | 2 & 2 | 1408 | 1404 | 704 | 700 |
+| 9 (16QAM) | 1 | 144 | 0 | 2 & 2 | 2812 | 2808 | 1408 | 1400 |
+
+Note: Time slot format 6-9 are exclusively used for semi-persistent HS-PDSCH resources. Whether data field is QPSK or 16QAM modulated, QPSK modulation is used for SS and TPC symbols.
+
+### 5A.3.9.6 Transmission of SS and TPC
+
+For the transmissions on the semi-persistent HS-PDSCH resources without an HS-SCCH, the SS and TPC command for HS-SICH can be conveyed in HS-PDSCH. The transmission of SS and TPC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the SS information, which is transmitted after the midamble. The SS and TPC are transmitted using the physical channel with the lowest physical channel number and the timeslot with the lowest timeslot number.
+
+### 5A.3.10 Shared Control Channel for HS-DSCH (HS-SCCH)
+
+The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below. A number of HS-SCCH types are defined for different purpose, and the actual description is given in [7].
+
+The information on the HS-SCCH is carried by two separate physical channels (HS-SCCH1 and HS-SCCH2). The term HS-SCCH refers to the ensemble of these physical channels.
+
+In CELL\_FACH or CELL\_PCH state, HS-SCCH order may carry an uplink synchronization establishment command. The structure is the same as described above.
+
+In case of multi-carrier HS-DSCH reception, the HS-DSCH transmission on each allocated carrier is associated with its respective HS-SCCHs. The HS-SCCHs and HS-SICHs controlling the same HS-DSCH transmission on a carrier for the same UE shall be allocated on a same carrier.
+
+#### 5A.3.10.1 HS-SCCH Spreading
+
+Spreading of the HS-SCCH is common with 3.84 Mcps TDD, cf. [5.3.10.1 HS-SCCH Spreading].
+
+#### 5A.3.10.2 HS-SCCH Burst Format
+
+The burst format as described in section 5A.2.2 shall be used for the HS-SCCH.
+
+#### 5A.3.10.3 HS-SCCH Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the HS-SCCH.
+
+#### 5A.3.10.4 HS-SCCH timeslot formats
+
+HS-SCCH1 shall use time slot format #5 and HS-SCCH2 shall use time slot format #0 from table 8F, see section 5A.2.2.4.1.1, i.e. HS-SCCH shall carry TPC and SS but no TFCI.
+
+## 5A.3.11 Shared Information Channel for HS-DSCH (HS-SICH)
+
+The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. If there is associated HS-SICH to an HS-SCCH order, the HS-SICH carries the acknowledgement to the HS-SCCH order command. The HS-SICH may also used as the acknowledgement for an HS-SCCH allocating semi-persistent HS-PDSCH resources. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below.
+
+In case of multi-carrier HS-DSCH reception, the HS-DSCH transmission on each allocated carrier is related to its respective HS-SICHs. The HS-SCCHs and HS-SICHs controlling the same HS-DSCH transmission on a carrier for the same UE shall be allocated on a same carrier.
+
+### 5A.3.11.1 HS-SICH Spreading
+
+The HS-SICH shall use spreading factor $SF = 16$ , as described in 5.2.1.2.
+
+When MIMO dual-stream is transmitted, the HS-SICH shall use spreading factor $SF=8$ which shall utilize an additional $SF=16$ channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree.
+
+### 5A.3.11.2 HS-SICH Burst Format
+
+The burst format as described in section 5A.2.2 shall be used for the HS-SICH.
+
+### 5A.3.11.3 HS-SICH Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the HS-SICH.
+
+### 5A.3.11.4 HS-SICH timeslot formats
+
+The HS-SICH Type 1 shall use time slot format #5 while HS-SICH Type 2 shall use time slot format #20 from table 8G, see section 5A.2.2.4.1.2, i.e., it shall carry TPC and SS but no TFCI. For HS-SICH type 2, two identical TPC symbols denoting one TPC command are transmitted directly after the two identical SS symbols denoting one SS command, which are transmitted after the midamble.
+
+## 5A.3.12 The MBMS Indicator Channel (MICH) type1
+
+The MBMS Indicator Channel (MICH) type1 is a physical channel used to carry the MBMS notification indicators on a non MBSFN dedicated carrier. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
+
+### 5A.3.12.1 Mapping of MBMS Indicators to the type1 MICH bits
+
+Figure 18L depicts the structure of a type1 MICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2 ‘Burst Format’] is used for the MICH. $N_{NIB}$ bits are used to carry the MBMS notification indicators, where $N_{NIB}=352$ .
+
+
+
+| Bits for MBMS Notification | | | Midamble | Bits for MBMS Notification | | Guard Period |
+|----------------------------|-------|-----------|----------|----------------------------|-----------|--------------|
+| $s_1$ $s_5$ | ..... | $s_{173}$ | | $s_3$ | $s_{175}$ | |
+| $s_2$ $s_6$ | ..... | $s_{174}$ | Midamble | $s_4$ | $s_{176}$ | Guard Period |
+
+Time Slot#i, subframe #1
+
+| Bits for MBMS Notification | | | Midamble | Bits for MBMS Notification | | Guard Period |
+|----------------------------|-------|-----------|----------|----------------------------|-----------|--------------|
+| $s_{177}$ $s_{181}$ | ..... | $s_{349}$ | | $s_{179}$ | $s_{351}$ | |
+| $s_{178}$ $s_{182}$ | ..... | $s_{350}$ | Midamble | $s_{180}$ | $s_{352}$ | Guard Period |
+
+Time Slot#i, subframe #2
+
+$i \in \{0, 2, 3, 4, 5, 6\}$
+
+Figure 18L: Transmission and numbering of MBMS notification indicator carrying bits in a type1 MICH burst. The diagram shows the bit structure for two subframes, each containing bits for MBMS notification, a midamble, and a guard period.
+
+**Figure 18L: Transmission and numbering of MBMS notification indicator carrying bits in a type1 MICH burst**
+
+Each notification indicator $N_q$ (where $N_q, q = 0, \dots, N_n-1, N_q \in \{0, 1\}$ ) in one radio frame is mapped to the bits $\{s_{2LNI \cdot q + 1}, \dots, s_{2LNI \cdot (q+1)}\}$ in subframe #1 or subframe #2.
+
+The setting of the MBMS notification indicators and the corresponding type1 MICH bits is described in [7].
+
+$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each radio frame that contains the MICH. The number of MBMS notification indicators $N_{NI}$ per radio frame is given by the MBMS notification indicator length, which is signalled by higher layers. In table 8KB this number is shown for the different possibilities of MBMS notification indicator lengths.
+
+**Table 8KB: Number $N_{NI}$ of MBMS notification indicators per radio frame on type1 MICH for different MBMS notification indicator lengths $L_{NI}$**
+
+| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ |
+|-----------------------|------------|------------|------------|
+| $N_n$ per radio frame | 88 | 44 | 22 |
+
+The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ .
+
+The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH type1 should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
+
+### 5A.3.12a The MBMS Indicator Channel (MICH) type 2
+
+The MBMS Indicator Channel (MICH) type 2 is a physical channel used to carry the MBMS notification indicators and system information change indicator on a MBSTN dedicated carrier only. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
+
+#### 5A.3.12.1 Mapping of MBMS Indicators to the type 2 MICH bits
+
+Figure 18La depicts the structure of a type 2 MICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2a 'MS Burst Format'] is used for the type 2 MICH. $2 \cdot L_{NI}$ bits are used to carry the system information change indicators and $N_{NIB} - 2 \cdot L_{NI}$ bits are used to carry the MBMS notification indicators, where $N_{NIB}=128$ for 10ms long MICH type 2.
+
+
+
+Figure 18La: Transmission and numbering of MBMS notification indicator carrying bits in a type 2 MICH burst. The diagram shows two subframes, subframe #1 and subframe #2. Each subframe contains a CP (Cyclic Prefix) and a Preamble. The bits are divided into two groups: 'Bits for SI change notification' and 'Bits for MBMS Notification'. The SI change notification bits are numbered S1, S2, ..., S\_{2L\_{NI}}, S\_{2L\_{NI}}+1, S\_{2L\_{NI}}+2, ..., S\_{2L\_{NI}}+L\_{NI}-1. The MBMS notification bits are numbered S\_{2L\_{NI}}+L\_{NI}, S\_{2L\_{NI}}+L\_{NI}+1, ..., S\_{128-1}.
+
+**Figure 18La: Transmission and numbering of MBMS notification indicator carrying bits in a type 2 MICH burst**
+
+Each notification indicator $N_q$ (where $N_q, q = 0, \dots, N_n-1, N_q \in \{0, 1\}$ ) in one radio frame is mapped to the bits $\{S_{2L_{NI} \cdot q+1}, \dots, S_{2L_{NI} \cdot (q+1)}}\}$ in subframe #1 or subframe #2.
+
+The setting of the MBMS notification indicators and the corresponding MICH bits is described in [7].
+
+$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each radio frame that contains the MICH. The number of MBMS notification indicators $N_{NI}$ per MICH length is given by the MBMS notification indicator length, which is signalled by higher layers. In table 8KBa this number is shown for the different possibilities of MBMS notification indicator lengths.
+
+**Table 8KBa: Number $N_{NI}$ of MBMS notification indicators per radio frame on type 2 MICH for different MBMS notification indicator lengths $L_{NI}$**
+
+| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ |
+|-----------------------|------------|------------|------------|
+| $N_n$ per radio frame | 31 | 15 | 7 |
+
+The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ .
+
+The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on type 2 MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
+
+### 5A.3.13 Physical Layer Common Control Channel (PLCCH)
+
+The Physical Layer Common Control Channel (PLCCH) is a Node B terminated channel which may be used to carry dedicated (UE-specific) TPC and SS information to multiple UEs. The PLCCH carries TPC and SS information only. No higher layer data is mapped to PLCCH. Each uplink CCTrCH is controlled either by PLCCH or by other appropriate downlink physical channels, under the control of higher layer signalling.
+
+#### 5A.3.13.1 PLCCH Spreading
+
+The PLCCH uses only spreading factor SF=16 as described in subclause 5A.2.1. The spreading codes for use on the PLCCH are indicated by higher layers.
+
+#### 5A.3.13.2 PLCCH Burst Type
+
+The burst format as described in section 5A.2.2 is used for the PLCCH.
+
+#### 5A.3.13.3 PLCCH Training Sequence
+
+The training sequences as described in subclause 5A.2.3 are used for PLCCH.
+
+#### 5A.3.13.4 PLCCH timeslot formats
+
+The PLCCH shall use time slot format #0 from table 8G, see section 5A.2.2.4.1.2.
+
+### 5A.3.14 E-DCH Physical Uplink Channel
+
+UE may have E-PUCH on each carrier. The E-PUCH on one carrier has at least one E-UCCH and one TPC on it. The TPC on the E-PUCH is used to carry the TPC command for the associated downlink control channel on the same carrier. The E-PUCH on one carrier and the E-UCCH and TPC mapped on it obey the following description.
+
+One or more E-PUCH on one carrier are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE.
+
+#### 5A.3.14.1 E-UCCH
+
+The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is mapped to E-PUCH on the same carrier. Depending on the configuration of the number of E-UCCH instances and the number of E-PUCH timeslots, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted.
+
+One E-UCCH instance :
+
+- is of length 32 physical channel bits
+- is mapped to the data field of the E-PUCH
+
+- is spread at SF appointed by CRRI
+- uses QPSK modulation
+
+There shall be at least one E-UCCH and TPC in every E-DCH TTI. Multiple instances of the same E-UCCH information and TPC can be transmitted within an E-DCH TTI, the detailed number of instances can be set by NodeB MAC-e/i for scheduled transmissions and signalled by higher layers for non-scheduled transmissions. When an E-DCH data block is transmitted on multiple (N) timeslots in one TTI, there will be multiple E-PUCH timeslots. All repetitions of E-UCCH and TPC are evenly distributed on multiple E-PUCH timeslots. N is the number of timeslots of the E-PUCH, M is the number of E-UCCH and TPC instances in one TTI; K is the integral part of $M/N$ ; L is the residue of $M/N$ . S is the number of E-UCCHs and TPCs in one E-PUCH timeslot. S equals $K+1$ for the first L E-PUCH timeslots and equals K for the last (N-L) E-PUCH timeslots.
+
+The mapping relationship between the TPC commands on the Non-scheduled E-PUCH and the DL timeslot and CCTrCH pairs is the same as that between the TPC commands on the UL DPCH and the DL timeslot and CCTrCH pairs (see subclause 5A.2.2.2).
+
+The burst composition of the E-UCCH information and the E-DCH data is shown in figure 18M.
+
+
+
+The diagram illustrates a burst structure. It consists of a sequence of blocks: a large 'Data Symbol' block, followed by two small blocks labeled 'E-UCCH' and 'TPC', then a 'Midamble' block, followed by two more small 'E-UCCH' and 'TPC' blocks, another large 'Data Symbol' block, and a final 'GP' (Guard Period) block. Double-headed arrows below the blocks indicate timing relationships between the E-UCCH/TPC instances, and a long double-headed arrow spans the entire burst duration.
+
+Figure 18M: Multiplexing structure of E-DCH and E-UCCH
+
+Figure 18M: Multiplexing structure of E-DCH and E-UCCH
+
+An E-UCCH is composed of 32 bits: $k_0, k_1 \dots k_{31}$ . It is segmented evenly into two parts shown in figure 18N.
+
+
+
+The diagram shows a bit sequence starting with $k_0$ , continuing to $k_{15}$ , then $k_{16}$ to $k_{31}$ . Arrows point from the first half ( $k_0$ to $k_{15}$ ) to a box labeled 'First part of E-UCCH (E-UCCH part 1)' and from the second half ( $k_{16}$ to $k_{31}$ ) to a box labeled 'Second part of E-UCCH (E-UCCH part 2)'.
+
+Figure 18N: E-UCCH code composition
+
+Figure 18N: E-UCCH code composition
+
+Figures 18O and 18P show the E-PUCH data burst with and without the E-UCCH/TPC fields.
+
+
+
+This diagram is identical in structure to Figure 18M, showing the placement of E-UCCH and TPC fields within the data burst, surrounding the midamble and at the end of the data symbol blocks.
+
+Figure 18O: E-PUCH data burst with E-UCCH/TPC
+
+Figure 18O: E-PUCH data burst with E-UCCH/TPC
+
+
+
+The diagram shows a simplified burst structure without internal E-UCCH/TPC fields. It consists of a large 'Data Symbol' block, a 'Midamble' block, another large 'Data Symbol' block, and a 'GP' block. A single long double-headed arrow spans the entire burst.
+
+Figure 18P: E-PUCH data burst without E-UCCH/TPC
+
+Figure 18P: E-PUCH data burst without E-UCCH/TPC
+
+#### 5A.3.14.2 E-PUCH Spreading
+
+The spreading factors that can be applied to the E-PUCH are SF = 1, 2, 4, 8, 16 as described in subclause 5A.2.1. All E-PUCH use the same spreading factor within an E-DCH TTI. For scheduled transmissions, E-PUCHs use the spreading factor indicated by CRR1 on E-AGCH.
+
+#### 5A.3.14.3 E-PUCH Burst Types
+
+The burst types as described in subclause 5A.2.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH.
+
+In case that TPC on non-scheduled E-PUCH is not used to adjust transmitting power level of downlink DPCH, Node B should not apply TPC commands received from non-scheduled E-PUCH.
+
+#### 5A.3.14.4 E-PUCH Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the E-PUCH.
+
+#### 5A.3.14.5 UE Selection
+
+UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification.
+
+#### 5A.3.14.6 E-PUCH timeslot formats
+
+An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 8KC.
+
+Error:
+
+3
+
+Error: Reference source not
+
+**Table 8KC: Time slot formats for the E-PUCH**
+
+Error:
+
+4
+
+Error: Reference source not
+
+| Slot Format # | 0 (QPSK) | 1 (16QAM) | 2 (QPSK) | 3 (16QAM) | 4 (QPSK) | 5 (16QAM) | 6 (QPSK) | 7 (16QAM) | 8 (QPSK) | 9 (16QAM) | 10 (QPSK) | 11 (16QAM) | 12 (QPSK) | 13 (16QAM) |
+|----------------------------------------|----------|-----------|----------|-----------|----------|-----------|----------|-----------|----------|-----------|-----------|------------|-----------|------------|
+| Spreading Factor | 16 | 16 | 16 | 16 | 16 | 16 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 |
+| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 |
+| Bits/slot | 88 | 176 | 88 | 142 | 88 | 108 | 176 | 352 | 176 | 318 | 176 | 284 | 176 | 250 |
+| N Data/Slot (bits) | 88 | 176 | 54 | 108 | 20 | 40 | 176 | 352 | 142 | 284 | 108 | 216 | 74 | 148 |
+| N data/data field(1) (bits) | 44 | 88 | 28 | 56 | 12 | 24 | 88 | 176 | 72 | 144 | 56 | 112 | 40 | 80 |
+| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH4_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH3_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N EUCCH2_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N EUCCH1_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC1 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH1_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC2 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 |
+| N EUCCH2_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N TPC3 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 |
+| N EUCCH3_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N TPC4 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH4_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC5 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC6 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N data/data field(2) | 44 | 88 | 26 | 52 | 8 | 16 | 88 | 176 | 70 | 140 | 52 | 104 | 34 | 68 |
+
+Error:
+
+5
+
+Error: Reference source not
+
+| Slot Format # | 0
(QPSK) | 1
(16QAM) | 2
(QPSK) | 3
(16QAM) | 4
(QPSK) | 5
(16QAM) | 6
(QPSK) | 7
(16QAM) | 8
(QPSK) | 9
(16QAM) | 10
(QPSK) | 11
(16QAM) | 12
(QPSK) | 13
(16QAM) |
+|---------------|-------------|--------------|-------------|--------------|-------------|--------------|-------------|--------------|-------------|--------------|--------------|---------------|--------------|---------------|
+| (bits) | | | | | | | | | | | | | | |
+
+Error:
+
+6
+
+Error: Reference source not
+
+Error:
+
+7
+
+Error: Reference source not
+
+| Slot Format # | 14 (QPSK) | 15 (16QAM) | 16 (QPSK) | 17 (16QAM) | 18 (QPSK) | 19 (16QAM) | 20 (QPSK) | 21 (16QAM) | 22 (QPSK) | 23 (16QAM) | 24 (QPSK) | 25 (16QAM) | 26 (QPSK) | 27 (16QAM) |
+|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|
+| Spreading Factor | 8 | 8 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 |
+| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 |
+| Bits/slot | 176 | 216 | 352 | 704 | 352 | 670 | 352 | 636 | 352 | 602 | 352 | 568 | 352 | 534 |
+| N Data/Slot (bits) | 40 | 80 | 352 | 704 | 318 | 636 | 284 | 568 | 250 | 500 | 216 | 432 | 182 | 364 |
+| N data/data field(1) (bits) | 24 | 48 | 176 | 352 | 160 | 320 | 144 | 288 | 128 | 256 | 112 | 224 | 96 | 192 |
+| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N EUCCH4_part1 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N EUCCH3_part1 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH2_part1 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH1_part1 (bits) | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC1 (bits) | 2 | 2 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH1_part2 (bits) | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC2 (bits) | 2 | 2 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH2_part2 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC3 (bits) | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH3_part2 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC4 (bits) | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 |
+| N EUCCH4_part2 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N TPC5 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 |
+| N EUCCH5_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N TPC6 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N data/data field(2) | 16 | 32 | 176 | 352 | 158 | 316 | 140 | 280 | 122 | 244 | 104 | 208 | 86 | 172 |
+
+Error:
+
+8
+
+Error: Reference source not
+
+| Slot Format # | 14
(QPSK) | 15
(16QAM) | 16
(QPSK) | 17
(16QAM) | 18
(QPSK) | 19
(16QAM) | 20
(QPSK) | 21
(16QAM) | 22
(QPSK) | 23
(16QAM) | 24
(QPSK) | 25
(16QAM) | 26
(QPSK) | 27
(16QAM) |
+|----------------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|
+| (bits) | | | | | | | | | | | | | | |
+
+Error:
+
+9
+
+Error: Reference source not
+
+Error:
+
+10
+
+Error: Reference source not
+
+| Slot Format # | 28 (QPSK) | 29 (16QAM) | 30 (QPSK) | 31 (16QAM) | 32 (QPSK) | 33 (16QAM) | 34 (QPSK) | 35 (16QAM) | 36 (QPSK) | 37 (16QAM) | 38 (QPSK) | 39 (16QAM) | 40 (QPSK) | 41 (16QAM) |
+|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|
+| Spreading Factor | 4 | 4 | 4 | 4 | 4 | 4 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 |
+| Bits/slot | 352 | 500 | 352 | 466 | 352 | 432 | 704 | 1408 | 704 | 1374 | 704 | 1340 | 704 | 1306 |
+| N Data/Slot (bits) | 148 | 296 | 114 | 228 | 80 | 160 | 704 | 1408 | 670 | 1340 | 636 | 1272 | 602 | 1204 |
+| N data/data field(1) (bits) | 80 | 160 | 64 | 128 | 48 | 96 | 352 | 704 | 336 | 672 | 320 | 640 | 304 | 608 |
+| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH4_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH3_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N EUCCH2_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N EUCCH1_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC1 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH1_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC2 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 |
+| N EUCCH2_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N TPC3 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 |
+| N EUCCH3_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N TPC4 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH4_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC5 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC6 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC7 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N TPC8 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+| N data/data field(2) | 68 | 136 | 50 | 100 | 32 | 64 | 352 | 704 | 334 | 668 | 316 | 632 | 298 | 596 |
+
+Error:
+
+11
+
+Error: Reference source not
+
+| Slot Format # | 28
(QPSK) | 29
(16QAM) | 30
(QPSK) | 31
(16QAM) | 32
(QPSK) | 33
(16QAM) | 34
(QPSK) | 35
(16QAM) | 36
(QPSK) | 37
(16QAM) | 38
(QPSK) | 39
(16QAM) | 40
(QPSK) | 41
(16QAM) |
+|----------------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|
+| (bits) | | | | | | | | | | | | | | |
+
+Error:
+
+12
+
+Error: Reference source not
+
+Error:
+
+13
+
+Error: Reference source not
+
+| Slot Format # | 42 (QPSK) | 43 (16QAM) | 44 (QPSK) | 45 (16QAM) | 46 (QPSK) | 47 (16QAM) | 48 (QPSK) | 49 (16QAM) | 50 (QPSK) | 51 (16QAM) | 52 (QPSK) | 53 (16QAM) | 54 (QPSK) | 55 (16QAM) |
+|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|
+| Spreading Factor | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 |
+| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 |
+| Bits/slot | 704 | 1272 | 704 | 1238 | 704 | 1204 | 704 | 1170 | 704 | 1136 | 1408 | 2816 | 1408 | 2782 |
+| N Data/Slot (bits) | 568 | 1136 | 534 | 1068 | 500 | 1000 | 466 | 932 | 432 | 864 | 1408 | 2816 | 1374 | 2748 |
+| N data/data field(1) (bits) | 288 | 576 | 272 | 544 | 256 | 512 | 240 | 480 | 224 | 448 | 704 | 1408 | 688 | 1376 |
+| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH4_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH3_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH2_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N EUCCH1_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 |
+| N TPC1 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 2 | 2 |
+| N EUCCH1_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 |
+| N TPC2 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH2_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N TPC3 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH3_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N TPC4 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH4_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N TPC5 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH5_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N TPC6 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 0 | 0 |
+| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 |
+| N data/data field(2) | 280 | 560 | 262 | 524 | 244 | 488 | 226 | 452 | 208 | 416 | 704 | 1408 | 686 | 1372 |
+
+Error:
+
+14
+
+Error: Reference source not
+
+| Slot Format # | 42
(QPSK) | 43
(16QAM) | 44
(QPSK) | 45
(16QAM) | 46
(QPSK) | 47
(16QAM) | 48
(QPSK) | 49
(16QAM) | 50
(QPSK) | 51
(16QAM) | 52
(QPSK) | 53
(16QAM) | 54
(QPSK) | 55
(16QAM) |
+|----------------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|
+| (bits) | | | | | | | | | | | | | | |
+
+Error:
+
+15
+
+Error: Reference source not
+
+Error:
+
+16
+
+Error: Reference source not
+
+| Slot Format # | 56 (QPSK) | 57 (16QAM) | 58 (QPSK) | 59 (16QAM) | 60 (QPSK) | 61 (16QAM) | 62 (QPSK) | 63 (16QAM) | 64 (QPSK) | 65 (16QAM) | 66 (QPSK) | 67 (16QAM) | 68 (QPSK) | 69 (16QAM) |
+|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|
+| Spreading Factor | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
+| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 |
+| Bits/slot | 1408 | 2748 | 1408 | 2714 | 1408 | 2680 | 1408 | 2646 | 1408 | 2612 | 1408 | 2578 | 1408 | 2544 |
+| N Data/Slot (bits) | 1340 | 2680 | 1306 | 2612 | 1272 | 2544 | 1238 | 2476 | 1204 | 2408 | 1170 | 2340 | 1136 | 2272 |
+| N data/data field(1) (bits) | 672 | 1344 | 656 | 1312 | 640 | 1280 | 624 | 1248 | 608 | 1216 | 592 | 1184 | 576 | 1152 |
+| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH5_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH4_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH3_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH2_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N EUCCH1_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC1 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH1_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC2 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH2_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC3 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH3_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC4 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH4_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC5 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH5_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC6 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 |
+| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 |
+| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 |
+| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 |
+| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 |
+| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 |
+| N data/data field(2) | 668 | 1336 | 650 | 1300 | 632 | 1264 | 614 | 1228 | 596 | 1192 | 578 | 1156 | 560 | 1120 |
+
+Error:
+
+17
+
+Error: Reference source not
+
+| Slot Format # | 56
(QPSK) | 57
(16QAM) | 58
(QPSK) | 59
(16QAM) | 60
(QPSK) | 61
(16QAM) | 62
(QPSK) | 63
(16QAM) | 64
(QPSK) | 65
(16QAM) | 66
(QPSK) | 67
(16QAM) | 68
(QPSK) | 69
(16QAM) |
+|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|
+| (bits) | | | | | | | | | | | | | | |
+
+### 5A.3.15 E-DCH Random Access Uplink Control Channel (E-RUCCH)
+
+The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. It shall be mapped to the same random access physical resources defined by UTRAN.
+
+For multi-carrier E-DCH transmission, each UE is configured with only one carrier for the E-RUCCH transmission.
+
+The E-RUCCH on the configured carrier shall be mapped to the same random access physical resources defined by UTRAN on the same carrier.
+
+#### 5A.3.15.1 E-RUCCH Spreading
+
+The E-RUCCH uses spreading factor SF=16 or SF=8 as described in subclause 5A.2.1. The set of admissible spreading codes used on the E-RUCCH are based on the spreading codes of PRACH.
+
+#### 5A.3.15.2 E-RUCCH Burst Format
+
+The burst format as described in section 5A.2.2 is used for the E-RUCCH.
+
+#### 5A.3.15.3 E-RUCCH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for E-RUCCH.
+
+#### 5A.3.15.4 E-RUCCH timeslot formats
+
+The timeslot format depends on the spreading factor of the E-RUCCH:
+
+| Spreading Factor | Slot Format # |
+|------------------|---------------|
+| 16 | 0 |
+| 8 | 10 |
+
+### 5A.3.16 E-DCH Absolute Grant Channel (E-AGCH)
+
+The E-DCH Absolute Grant Channel (E-AGCH) on one carrier is a downlink physical channel carrying the uplink E-DCH absolute grant control information of the same carrier. The E-AGCH on one carrier uses two separate physical channels (E-AGCH1 and E-AGCH2). The term E-AGCH refers to the ensemble of these physical channels. The detailed description of the E-AGCH on one carrier is given below.
+
+#### 5A.3.16.1 E-AGCH Spreading
+
+Spreading of the E-AGCH is common with 3.84Mcps TDD, cf. [5.3.15.1 E-AGCH Spreading].
+
+#### 5A.3.16.2 E-AGCH Burst Types
+
+The burst structures for E-AGCH1 and E-AGCH2 are shown in figure 18Q and 18R.
+
+
+
+The diagram illustrates the E-AGCH1 burst structure. It consists of a sequence of symbols: Data symbols, Midamble, SS symbol(s), TPC symbol(s), Data symbols, and GP. The Midamble is highlighted with a double-headed arrow and labeled '144 chips'. The entire burst is indicated by a long double-headed arrow at the bottom, labeled '864 Chips'. Arrows point from the labels 'SS symbol(s)' and 'TPC symbol(s)' to their respective positions in the burst.
+
+Diagram of E-AGCH1 burst structure showing Data symbols, Midamble, SS symbol(s), TPC symbol(s), and GP. The Midamble is 144 chips long, and the total burst length is 864 chips.
+
+Figure 18Q: E-AGCH1 burst structure
+
+
+
+Figure 18R: E-AGCH2 burst structure diagram showing four segments: Data symbols (352 chips), Midamble (144 chips), Data symbols (352 chips), and GP (16 CP). A double-headed arrow below indicates a total duration of 864 \* Tc.
+
+Figure 18R: E-AGCH2 burst structure
+
+#### 5A.3.16.3 E-AGCH Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the E-AGCH.
+
+#### 5A.3.16.4 E-AGCH timeslot formats
+
+E-AGCH1 shall use time slot format #5 and E-AGCH2 shall use time slot format #0 from table 8F, see section 5A.2.2.4.1.1, i.e. E-AGCH shall carry TPC and SS for E-PUCH power control and synchronization but no TFCI.
+
+Table 8KD: Timeslot formats for the E-AGCH
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N ss &N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (1) (bits) | N data/data field (2) (bits) |
+|---------------|------------------|-------------------------|------------------------------------|------------------------------------------|-----------|-------------------------------|-----------------------------------------|-----------------------------------------|
+| 0 | 16 | 144 | 0 | 0&0 | 88 | 88 | 44 | 44 |
+| 5 | 16 | 144 | 0 | 2&2 | 88 | 84 | 44 | 40 |
+
+### 5A.3.17 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)
+
+The E-DCH HARQ Acknowledgement indicator channel (E-HICH) on one carrier is defined in terms of a SF16 downlink physical channel and a signature sequence on the same carrier.
+
+The E-HICH on one carrier carries one or multiple users' acknowledgement indicator on the same carrier. The detailed description of the E-HICH on one carrier is given below.
+
+Figure 18S illustrates the structure of the E-HICH on one carrier. The E-HICH contains 8 spare bit locations. The spare bit values are undefined. The power of each user's acknowledgement indicator may be set independently by the Node-B. The number of E-HICHs in a cell is configured by the system.
+
+The acknowledgement indicators for the E-PUCH semi-persistent scheduling operation can be transmitted on the same E-HICH carrying indicators for scheduled traffic or the E-HICH carrying indicators for non-scheduled traffic.
+
+
+
+Figure 18S: E-HICH Structure diagram showing a burst with segments: Data Symbols, Spare bits (two small grey blocks), Midamble, Data Symbols, and GP. A double-headed arrow below indicates a total duration of 864 chips.
+
+Figure 18S: E-HICH Structure
+
+For Scheduled transmissions, at most four E-HICHs can be configured for one user's scheduled transmission. Which E-HICH is used to convey the HARQ acknowledgment indicator is indicated by the 2-bit E-HICH indicator on E-AGCH. A single E-HICH may carry one or multiple HARQ acknowledgement indicator(s) which are decided by the Node-B.
+
+For Non-Scheduled transmissions, E-HICHs carry not only the HARQ acknowledgement indicators but also TPC and SS commands. The 80 signature sequences are divided into 20 groups while each group includes 4 sequences. Every non-scheduled user is assigned only one group which are signalled by higher layer. Among the 4 sequences, the first one is used to indicate ACK/NACK, and the other three are used to indicate the TPC/SS commands. The three sequences and their three reverse sequences are the six possible sequences used to indicate the TPC/SS combination state. The reverse sequence is constructed by reverse every bit of the sequence from 0 to 1 or from 1 to 0. The mapping between the index and the TPC/SS command is shown in table 8KE. The index is calculated according to the equation: $\text{index} = 2 \cdot A + B$ , ( $A=0,1,2$ ; $B=0,1$ ). A is the relative index of the selected sequence among the three assigned sequences and B equals to 1 when the reverse sequence is chosen, otherwise, B equals to 0. The power of the sequence used for TPC/SS indication can be set differently from the one used to indicate ACK/NACK.
+
+**Table 8KE: Mapping between the index and TPC/SS command**
+
+| index | TPC command | SS command |
+|-------|-------------|--------------|
+| 0 | 'DOWN' | 'DOWN' |
+| 1 | 'UP' | 'DOWN' |
+| 2 | 'DOWN' | 'UP' |
+| 3 | 'UP' | 'UP' |
+| 4 | 'DOWN' | 'Do Nothing' |
+| 5 | 'UP' | 'Do Nothing' |
+
+For the E-DCH semi-persistent scheduling operation, E-HICHs carry not only the HARQ acknowledgement indicators but also TPC and SS commands. Each user is also assigned one signature sequence group including 4 sequences whose usage is completely complying with the definition in non-scheduled transmissions.
+
+The acknowledgement indicator for an E-DCH transmission in TTI "N" is carried by the E-HICH in TTI "N+[TA]"(TA is determined according to the value of $n_{E-HICH}$ ). The E-HICH is thus synchronously related to those E-DCH transmissions for which it carries acknowledgement information.
+
+#### 5A.3.17.1 E-HICH Spreading
+
+Multiple users' signature sequences (including the inserted spare bits) sharing the same channelisation code are combined and spread using spreading factor SF=16 as described in [8].
+
+#### 5A.3.17.2 E-HICH Burst Types
+
+The burst structures for E-HICH are shown in figure 18D.
+
+#### 5A.3.17.3 E-HICH Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the E-HICH.
+
+#### 5A.3.17.4 E-HICH timeslot formats
+
+E-HICH shall use time slot format #0 from table 8F.
+
+### 5A.3.18 Standalone midamble channel
+
+#### 5A.3.18.1 Standalone midamble channel Burst Format
+
+A standalone midamble channel traffic burst consists of a midamble of 144 chips only. The burst format is shown in Figure 18T. The contents of the traffic burst fields are described in table 8KF.
+
+**Table 8KF: The contents of the standalone midamble channel traffic burst format fields**
+
+| Chip number (CN) | Length of field in chips | Contents of field |
+|------------------|--------------------------|-------------------|
+| 0-351 | 352 | NULL |
+| 352-495 | 144 | Midamble |
+| 496-863 | 368 | NULL |
+
+
+
+Figure 18T: Burst structure of the standalone midamble channel traffic burst format. The diagram shows a horizontal bar divided into three equal-width rectangular sections. Below the bar, a double-headed arrow spans the entire length, indicating the full burst duration.
+
+Figure 18T: Burst structure of the standalone midamble channel traffic burst format
+
+#### 5A.3.18.3 Standalone midamble channel Training Sequences
+
+The training sequences as described in subclause 5A.2.3 are used for the standalone midamble channel.
+
+#### 5A.3.18.4 Standalone midamble channel timeslot formats
+
+The timeslot formats for the standalone midamble channel are shown in table 8KG.
+
+**Table 8KG: Timeslot formats for the standalone midamble channel**
+
+| Slot Format # | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 | 144 | 0 | 0 & 0 | 0 | 0 | 0 | 0 |
+
+## 5A.4 Transmit Diversity for DL Physical Channels
+
+Table 8L summarizes the different transmit diversity schemes for different downlink physical channel types in 1.28Mcps TDD that are described in [9].
+
+**Table 8L: Application of Tx diversity schemes on downlink physical channel types in 1.28Mcps TDD**
+ "X" – can be applied, "-" – must not be applied
+
+| Physical channel type | Open loop TxDiversity | | Closed loop TxDiversity |
+|--------------------------------|-----------------------|------|-------------------------|
+| | TSTD | SCTD | |
+| P-CCPCH | X(†) | X(†) | – |
+| S-CCPCH | X(†) | X(†) | – |
+| DwPCH | X | – | – |
+| DPCH | X | – | X |
+| PDSCH | X | X | X |
+| PICH | X | X | – |
+| MICH | X(†) | X(†) | – |
+| PLCCH | X | X | – |
+| HS-SCCH | – | X | X |
+| HS-PDSCH (UE not in MIMO mode) | – | – | X |
+| HS-PDSCH (UE in MIMO mode) | – | – | – |
+| E-AGCH | -- | X | X |
+| E-HICH | -- | X | -- |
+
+(\*) Note: SCTD may only be applied to physical channels when they are allocated to beacon locations.
+
+(†) Note: that when the entire carrier is dedicated to MBMSFN operation, TSTD and SCTD shall not be applied.
+
+## 5A.5 Beacon characteristics of physical channels
+
+For the purpose of measurements, common physical channels that are allocated to particular locations (time slot, code) shall have particular physical characteristics, called beacon characteristics. Physical channels with beacon characteristics are called beacon channels. The location of the beacon channels is called beacon location. The beacon
+
+channels shall provide the beacon function, i.e. a reference power level at the beacon location, regularly existing in each subframe. Thus, beacon channels must be present in each subframe.
+
+### 5A.5.1 Location of beacon channels
+
+The beacon location is described as follows:
+
+The beacon function shall be provided by the physical channels that are allocated to channelisation code $c_{Q=16}^{(k=1)}$ and $c_{Q=16}^{(k=2)}$ in Timeslot#0.
+
+Note that by this definition the P-CCPCH always has beacon characteristics. In a multi-frequency cell beacon channels are always transmitted on the primary frequency.
+
+### 5A.5.2 Physical characteristics of the beacon function
+
+The beacon channels shall have the following physical characteristics.
+
+They:
+
+- are transmitted with reference power;
+- are transmitted without beamforming;
+- use midamble $m^{(1)}$ and $m^{(2)}$ exclusively in this time slot
+
+The reference power corresponds to the sum of the power allocated to both midambles $m^{(1)}$ and $m^{(2)}$ . Two possibilities exist:
+
+- If SCTD antenna diversity is not applied to beacon channels, all the reference power of any beacon channel is allocated to $m^{(1)}$ .
+- If SCTD antenna diversity is applied to beacon channels, for any beacon channel midambles $m^{(1)}$ and $m^{(2)}$ are each allocated half of the reference power.
+
+## 5A.6 Midamble Allocation for Physical Channels
+
+Midambles are part of the physical channel configuration which is performed by higher layers. Four different midamble allocation schemes exist:
+
+- UE specific midamble allocation: A UE specific midamble for DL or UL is explicitly assigned by higher layers.
+- Default midamble allocation: The midamble for DL or UL is allocated by layer 1 depending on the associated channelisation code.
+- Common midamble allocation: The midamble for the DL is allocated by layer 1 depending on the number of channelisation codes currently being present in the DL time slot.
+- Special Default midamble allocation: The midamble for DL or UL is also allocated by layer 1 depending on the associated channelisation code while the association is different from default midamble allocation.
+
+If a midamble is not explicitly assigned and the use of the common midamble allocation scheme is not signalled by higher layers, the midamble shall be allocated by layer 1, based on default or special default midamble allocation scheme. This default or special default midamble allocation scheme is given by a fixed association between midambles and channelisation codes, and shall be applied individually to all channelisation codes within one time slot. Different associations apply for different burst types and cell configurations with respect to the maximum number of midambles.
+
+The associations between channelisation codes and midambles for the default, special default and common midamble allocation differ from the 3.84 Mcps TDD option. The associations are given in Annex AA.2 [Association between Midambles and channelisation Codes for default midamble allocation], Annex AA.3 [Association between Midambles and channelisation Codes for special default midamble allocation] and BA [Signalling of the number of channelisation codes for the DL common midamble case for 1.28Mcps TDD] respectively.
+
+However, for timeslots employing MBSFN operation there is no single midamble restriction per MBSFN timeslot, i.e. $K_{\text{Cell}} \geq 1$ , whilst this does not undermine the specification that all physical channels in such timeslots employ the same midamble(s) and thus default and common midamble allocation amount to the same allocation strategies.
+
+### 5A.6.1 Midamble Allocation for DL Physical Channels
+
+Beacon channels shall always use the reserved midambles $m^{(1)}$ and $m^{(2)}$ , see 5A.5. For the other DL physical channels that are located in timeslot #0, midambles shall be allocated based on the default midamble allocation scheme, using the association for $K=8$ midambles. For all other DL physical channels, the midamble is explicitly assigned by higher layers or allocated by layer 1.
+
+#### 5A.6.1.1 Midamble Allocation by signalling from higher layers
+
+The midamble allocation by signalling is the same like in the 3.84 Mcps TDD cf. [5.6.1.1 Midamble allocation by signalling from higher layers]
+
+#### 5A.6.1.2 Midamble Allocation by layer 1
+
+##### 5A.6.1.2.1 Default midamble
+
+The default midamble allocation by layer 1 is the same like in the 3.84 Mcps TDD cf. [5.6.1.2.1 Default midamble]. The associations between midambles and channelisation codes are given in Annex AA.2 [Association between Midambles and channelisation Codes for default midamble allocation].
+
+If the variable $E\_DCH\_SPS\_STATUS = TRUE$ then two E-HICHs associated with the same midamble shift in the same timeslot can be configured.
+
+##### 5A.6.1.2.2 Common Midamble
+
+The common midamble allocation by layer 1 is the same like in the 3.84 Mcps TDD cf. [5.6.1.2.2 Common midamble]. The respective associations are given in Annex BA [Signalling of the number of channelisation codes for the DL common midamble case for 1.28 Mcps TDD].
+
+##### 5A.6.1.2.3 Special Default Midamble
+
+For MIMO dual stream transmission, there are two patterns (pattern 1 and pattern 2) of the association between midambles and channelisation codes for special default midamble allocation scheme for each cell configurations with respect to the maximum number of midambles.
+
+For MU-MIMO transmission, there are four patterns (pattern 1A, pattern 1B, pattern 2A and pattern 2B) of the association between midambles and channelisation codes for special default midamble allocation scheme for each cell configurations with respect to the maximum number of midambles.
+
+If the UE is configured in MIMO or MU-MIMO mode and the default midamble allocation scheme is signalled to the UE by higher layers, the default or special default midamble allocation scheme can be used. Whether the default or special default midamble allocation scheme is used is signalled to the UE by the related physical channel in [7]. The association between midambles and channelisation codes for the special default midamble allocation scheme for both MIMO dual stream transmission and MU-MIMO transmission are given in Annex AA.3 [Association between Midambles and channelisation Codes for special default midamble allocation].
+
+### 5A.6.2 Midamble Allocation for UL Physical Channels
+
+The midamble allocation for UL Physical Channels is the same as in the 3.84 Mcps TDD cf. [5.6.2 Midamble allocation for UL Physical Channels]
+
+## 5A.7 Midamble Transmit Power
+
+When standalone midamble channel is not transmitted, the setting of the midamble transmit power is done as in the 3.84 Mcps TDD option cf. 5.7 'Midamble Transmit Power'
+
+## 5A.7a Preamble Allocation and Preamble Transmit Power
+
+When the entire carrier is dedicated to MBSFN, for all timeslots employing MBSFN operation, only a single preamble is needed, i.e. $K_{\text{Cell}}=1$ , then all physical channels in such timeslots employ the same preamble with the same allocation strategies.
+
+There shall be no offset between the sum of the powers allocated to all preambles in a timeslot and the sum of the powers allocated to the data symbol fields. The transmit power within a timeslot is hence constant.
+
+# 5B Physical channels for the 7.68 Mcps option
+
+## 5B.1 General
+
+All physical channels take a three-layer structure with respect to timeslots, radio frames and system frame numbering (SFN). Depending on the resource allocation, the configuration of radio frames or timeslots becomes different. All physical channels need a guard period in every timeslot. The time slots are used in the sense of a TDMA component to separate different user signals in the time domain. The physical channel signal format is presented in figure 18AA.
+
+A physical channel in the 7.68 Mcps TDD option is a burst, which is transmitted in a particular timeslot within allocated Radio Frames. The allocation can be continuous, i.e. the time slot in every frame is allocated to the physical channel or discontinuous, i.e. the time slot in a subset of all frames is allocated only. A burst is the combination of two data parts, a midamble part and a guard period. The duration of a burst is one time slot. Several bursts can be transmitted at the same time from one transmitter. In this case, the data parts must use different OVSF channelisation codes, but the same scrambling code. The midamble parts are either identically or differently shifted versions of a cell-specific basic midamble code, see section 5B.3.3. Note when in MBSFN operation, a midamble is not necessarily cell-specific.
+
+
+
+Figure 18AA: Physical channel signal format. The diagram illustrates the hierarchical structure of a physical channel. At the top, a 'Radio Frame (10ms)' is shown as a horizontal bar containing 'frame #i' and 'frame #i+1'. Below this, a 'Timeslot (5120 \* Tc)' is shown as a horizontal bar containing 'timeslot #0', 'timeslot #1', 'timeslot #2', a gap, 'timeslot #13', and 'timeslot #14'. Dashed lines connect the boundaries of the radio frames to the boundaries of the timeslots, indicating that each radio frame contains 15 timeslots.
+
+Figure 18AA: Physical channel signal format
+
+The data part of the burst is spread with a combination of channelisation code and scrambling code. The channelisation code is an OVSF code, that can have a spreading factor of 1, 2, 4, 8, 16 or 32. The data rate of the physical channel depends on the used spreading factor of the used OVSF code.
+
+The midamble part of the burst can contain two different types of midambles: a short one of length 512 chips, or a long one of length 1024 chips. The data rate of the physical channel depends on the used midamble length. Additionally, when in MBSFN operation a midamble of length 640 chips is used.
+
+So a physical channel is defined by frequency, timeslot, channelisation code, burst type and Radio Frame allocation. The scrambling code and the basic midamble code are broadcast and may be constant within a cell. When a physical channel is established, a start frame is given. The physical channels can either be of infinite duration, or of a duration defined by allocation.
+
+## 5B.2 Frame structure
+
+The TDMA frame has a duration of 10 ms and is subdivided into 15 time slots (TS) of $5120 \cdot T_c$ duration each. A time slot corresponds to 5120 chips. The physical content of the time slots are the bursts of corresponding length as described in subclause 5B.3.2.
+
+Each 10 ms frame consists of 15 time slots, each allocated to either the uplink or the downlink (figure 18AB). With such a flexibility, the TDD mode can be adapted to different environments and deployment scenarios. In any configuration at least one time slot has to be allocated for the downlink and at least one time slot has to be allocated for the uplink with the exception of no uplink timeslots when the entire carrier is dedicated to MBSFN.
+
+
+
+Figure 18AB: The TDD frame structure. The diagram shows a 10ms frame divided into 15 time slots. The vertical axis is labeled 'frequency' and the horizontal axis is labeled 'time'. Each time slot is represented by a rectangle with a vertical double-headed arrow inside. Above the frame, a horizontal double-headed arrow indicates a duration of 10ms. To the right of the frame, a vertical double-headed arrow indicates a rate of 7.68Mcps. Below the frame, a horizontal double-headed arrow indicates a duration of 5120 \* T\_c.
+
+**Figure 18AB: The TDD frame structure**
+
+Examples for multiple and single switching point configurations as well as for symmetric and asymmetric UL/DL allocations are given in figure 3.
+
+## 5B.3 Dedicated physical channel (DPCH)
+
+The DCH as described in subclause 4.1.1 is mapped onto the dedicated physical channel.
+
+### 5B.3.1 Spreading
+
+Spreading is applied to the data part of the physical channels and consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. Details on channelisation and scrambling operation can be found in [8].
+
+#### 5B.3.1.1 Spreading for Downlink Physical Channels
+
+Downlink physical channels shall use SF=32 or SF=1.
+
+Multiple parallel physical channels can be used to support higher data rates. Within a timeslot, parallel physical channels shall be transmitted using different channelisation codes, see [8]. These codes with SF=32 are generated as described in [8].
+
+#### 5B.3.1.2 Spreading for Uplink Physical Channels
+
+The range of spreading factors that may be used for uplink physical channels shall range from 32 down to 1. For each physical channel an individual minimum spreading factor $SF_{min}$ is transmitted by means of the higher layers. There are two options that are indicated by UTRAN:
+
+1. The UE shall use the spreading factor $SF_{min}$ , independent of the current TFC.
+2. The UE shall autonomously increase the spreading factor depending on the current TFC.
+
+If the UE autonomously changes the SF, it shall always vary the channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree, as depicted in [8]. In the event that code hopping is configured by higher layers, the allowed OVSF sub-tree is that subtended by the effective allocated OVSF code after the hop sequence has been applied to the allocated OVSF code (see [9]).
+
+For multicode transmission a UE shall use a maximum of two physical channels per timeslot simultaneously. These two parallel physical channels shall be transmitted using different channelisation codes, see [8].
+
+### 5B.3.2 Burst Types
+
+Four types of bursts are defined. All of them consist of two data symbol fields, a midamble and a guard period, the lengths of which are different for the individual burst types. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 8AA.
+
+**Table 8AA: Number of data symbols (N) for burst type 1, 2, 3 and 4**
+
+| Spreading factor (SF) | Burst Type 1 | Burst Type 2 | Burst Type 3 | Burst Type 4 |
+|-----------------------|--------------|--------------|--------------|--------------|
+| 1 | 3904 | 4416 | 3712 | 4224 |
+| 2 | 1952 | 2208 | 1856 | N/A |
+| 4 | 976 | 1104 | 928 | N/A |
+| 8 | 488 | 552 | 464 | N/A |
+| 16 | 244 | 276 | 232 | N/A |
+| 32 | 122 | 138 | 116 | 132 |
+
+The support of burst types 1, 2 and 3 is mandatory for UEs supporting transmit and receive functions. UEs supporting transmit and receive functions and also MBSFN operation must additionally support burst type 4. UEs with receive only capability need only support burst type 4.. The three different bursts defined here are well suited for different applications, as described in the following sections.
+
+#### 5B.3.2.1 Burst Type 1
+
+Burst type 1 can be used for uplink and downlink. Due to its longer midamble field this burst type supports the construction of a larger number of training sequences. The maximum number of training sequences depends on the cell configuration. For burst type 1 this number may be 4, 8, or 16.
+
+The data fields of burst type 1 are 1952 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8AA above. The midamble of burst type 1 has a length of 1024 chips. The guard period for the burst type 1 is 192 chip periods long. Burst type 1 is shown in Figure 18AC. The contents of the burst fields are described in table 8AB.
+
+**Table 8AB: The contents of burst type 1 fields**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-1951 | 1952 | Cf table 8AA | | Data symbols |
+| 1952-2975 | 1024 | - | | Midamble |
+| 2976-4927 | 1952 | Cf table 8AA | | Data symbols |
+| 4928-5119 | 192 | - | | Guard period |
+
+
+
+| | | | |
+|-------------------------|---------------------|-------------------------|-----------------|
+| Data symbols 1952 chips | Midamble 1024 chips | Data symbols 1952 chips | GP
192
CP |
+|-------------------------|---------------------|-------------------------|-----------------|
+
+← 5120 \* $T_c$ →
+
+Diagram showing the burst structure of burst type 1. It consists of four sequential blocks: Data symbols (1952 chips), Midamble (1024 chips), Data symbols (1952 chips), and a Guard Period (GP) (192 CP). A dimension line below indicates the total length is 5120 \* Tc.
+
+**Figure 18AC: Burst structure of burst type 1. GP denotes the guard period and CP the chip periods**
+
+#### 5B.3.2.2 Burst Type 2
+
+Burst type 2 can be used for uplink and downlink. It offers a longer data field than burst type 1 at the cost of a shorter midamble. Due to the shorter midamble field the burst type 2 supports a maximum number of training sequences of 4 or 8 only, depending on the cell configuration.
+
+The data fields of the burst type 2 are 2208 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8AA above. The guard period for the burst type 2 is 192 chip periods long. Burst type 2 is shown in Figure 18AD. The contents of the burst fields are described in table 8AC.
+
+Table 8AC: The contents of burst type 2 fields
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-2207 | 2208 | cf table 8AA | | Data symbols |
+| 2208-2719 | 512 | - | | Midamble |
+| 2720-4927 | 2208 | cf table 8AA | | Data symbols |
+| 4928-5119 | 192 | - | | Guard period |
+
+
+
+Figure 18AD: Burst structure of the burst type 2. The diagram shows a horizontal bar divided into four segments: 'Data symbols 2208 chips', 'Midamble 512 chips', 'Data symbols 2208 chips', and 'GP 192 CP'. Below the bar, a double-headed arrow indicates a total length of 5120 \* Tc.
+
+Figure 18AD: Burst structure of the burst type 2. GP denotes the guard period and CP the chip periods
+
+#### 5B.3.2.3 Burst Type 3
+
+Burst type 3 is used for uplink only. Due to the longer guard period it is suitable for initial access or access to a new cell after handover. It offers the same number of training sequences as burst type 1.
+
+The data fields of the burst type 3 have a length of 1952 chips and 1760 chips, respectively. The corresponding number of symbols depends on the spreading factor, as indicated in table 8AA above. The midamble of burst type 3 has a length of 1024 chips. The guard period for the burst type 3 is 384 chip periods long. Burst type 3 is shown in Figure 18AE. The contents of the burst fields are described in table 8AD.
+
+Table 8AD: The contents of burst type 3 fields
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-1951 | 1952 | Cf table 8AA | | Data symbols |
+| 1952-2975 | 1024 | - | | Midamble |
+| 2976-4735 | 1760 | Cf table 8AA | | Data symbols |
+| 4736-5119 | 384 | - | | Guard period |
+
+
+
+Figure 18AE: Burst structure of the burst type 3. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1952 chips', 'Midamble 1024 chips', 'Data symbols 1760 chips', and 'GP 384 CP'. Below the bar, a double-headed arrow indicates a total length of 5120 \* Tc.
+
+Figure 18AE: Burst structure of the burst type 3. GP denotes the guard period and CP the chip periods
+
+#### 5B.3.2.3A Burst Type 4
+
+The burst type 4 is used for downlink MBSFN operation only and supports a single training sequence.
+
+The data fields of the burst type 4 are 2112 chips long. The corresponding number of symbols is 132 as indicated in table 8AA above. The midamble of burst type 4 has a length of 640 chips. The guard period for the burst type 4 is 256 chip periods long. The burst type 4 is shown in Figure 18AEA. The contents of the burst fields are described in table 8ADA.
+
+**Table 8ADA: The contents of burst type 4 fields**
+
+| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field |
+|------------------|--------------------------|----------------------------|--|-------------------|
+| 0-2111 | 2112 | Cf table 8AA | | Data symbols |
+| 2112-2751 | 640 | - | | Midamble |
+| 2752-4863 | 2112 | Cf table 8AA | | Data symbols |
+| 4864-5119 | 256 | - | | Guard period |
+
+
+
+Figure 18AEA: Burst structure of the burst type 4. The diagram shows a horizontal bar divided into four segments: 'Data symbols 2112 chips', 'Midamble 640 chips', 'Data symbols 2112 chips', and 'GP 256 CP'. Below the bar, a double-headed arrow indicates a total duration of 5120 \* T\_c.
+
+Figure 18AEA: Burst structure of the burst type 4. GP denotes the guard period and CP the chip periods
+
+#### 5B.3.2.4 Transmission of TFCI
+
+All burst types 1, 2, 3 and 4 provide the possibility for transmission of TFCI.
+
+The transmission of TFCI is negotiated at call setup and can be re-negotiated during the call. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied, except for the MBSFN FACH where the (16,5) bi-orthogonal code is always used for TFCI when TFCI is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (*p*) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+The transmission of TFCI is done in the data parts of the respective physical channel. In DL the TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. In DL, the modulation applied to the TFCI code word bits is the same as that applied to the data symbols. In UL, independent of the SF that is applied to the data symbols in the burst, the data in the TFCI field are always spread with SF=32 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TFCI code word is to be transmitted directly adjacent to the midamble, possibly after the TPC. Figure 18AF shows the position of the TFCI code word in a traffic burst in downlink. Figure 18AG shows the position of the TFCI code word in a traffic burst in uplink.
+
+
+
+Figure 18AF: Position of the TFCI code word in the traffic burst in case of downlink. The diagram shows a horizontal bar with segments: 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. The 'Midamble' segment is further divided into two parts labeled '1st part of TFCI code word' and '2nd part of TFCI code word'. Below the bar, a double-headed arrow indicates a duration of 1024/512 chips for the midamble section, and another double-headed arrow indicates a total duration of 5120 \* T\_c for the entire burst.
+
+Figure 18AF: Position of the TFCI code word in the traffic burst in case of downlink
+
+
+
+Figure 18AG: Position of the TFCI code word in the traffic burst in case of uplink. The diagram shows a traffic burst structure with Data symbols, a Midamble, and a GP. The TFCI code word is split into two parts: the 1st part is located at the beginning of the Midamble, and the 2nd part is located at the end of the Midamble, immediately before the Data symbols. The TPC field is located at the end of the Midamble, after the 2nd part of the TFCI code word. The total duration of the traffic burst is 5120 \* T\_c. The duration of the Midamble is 1024/512 chips.
+
+**Figure 18AG: Position of the TFCI code word in the traffic burst in case of uplink**
+
+Two examples of TFCI transmission in the case of multiple DPCHs used for a connection are given in the Figure 18AH and Figure 18AI below. Combinations of the two schemes shown are also applicable.
+
+
+
+Figure 18AH: Example of TFCI transmission with physical channels multiplexed in code domain. The diagram shows three horizontal lines representing different codes over time (t). The first code has a Midamble (vertical lines) and a TFCI (diagonal lines) section. The second code has a Midamble (vertical lines) and a TFCI (diagonal lines) section. The third code has a Midamble (vertical lines) and a TFCI (diagonal lines) section. The total duration of the traffic burst is 5120 \* T\_c. The legend indicates: Data (white), Midamble (vertical lines), and TFCI (diagonal lines).
+
+**Figure 18AH: Example of TFCI transmission with physical channels multiplexed in code domain**
+
+
+
+Figure 18AI: Example of TFCI transmission with physical channels multiplexed in time domain. The diagram shows three horizontal lines representing different codes over time (t). The first code has a TFCI (diagonal lines) section followed by a Midamble (vertical lines) section. The second code has a Midamble (vertical lines) section. The third code has a Midamble (vertical lines) section. The total duration of the traffic burst is 5120 \* T\_c. The legend indicates: Data (white), Midamble (vertical lines), and TFCI (diagonal lines).
+
+**Figure 18AI: Example of TFCI transmission with physical channels multiplexed in time domain**
+
+#### 5B.3.2.5 Transmission of TPC
+
+Burst types 1, 2 and 3 for dedicated and shared channels provide the possibility for transmission of TPC in uplink.
+
+The transmission of TPC is done in the data parts of the traffic burst. Independent of the SF that is applied to the data symbols in the burst, the data in the TPC field are always spread with $SF=32$ using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the midamble. Figure 18AJ shows the position of the TPC in a traffic burst.
+
+For every user the TPC information shall be transmitted at least once per transmitted frame. If a TFCI is applied for a CCTrCH, TPC shall be transmitted with the same channelization codes and in the same timeslots as the TFCI. If no TFCI is applied for a CCTrCH, TPC shall be transmitted using the physical channel corresponding to physical channel
+
+sequence number $p=1$ . Physical channel sequence numbering is determined by the rate matching function and is described in [7].
+
+
+
+Diagram showing the position of the TPC field in a traffic burst. The burst consists of Data symbols, a Midamble, another Data symbols section, and a GP. The TPC field is located within the Midamble. A double-headed arrow indicates the length of the Midamble is 1024/512 chips. A longer double-headed arrow at the bottom indicates the total length of the burst is 5120\*Tc.
+
+**Figure 18AJ: Position of TPC information in the traffic burst**
+
+The length of the TPC field is $N_{TPC}$ bits. The TPC field is formed via repetition encoding a single bit $b_{TPC}$ , $N_{TPC}$ times.
+
+The relationship between $b_{TPC}$ and the TPC command is shown in table 8AE.
+
+**Table 8AE: TPC bit pattern**
+
+| $b_{TPC}$ | TPC command | Meaning |
+|-----------|-------------|-------------------|
+| 0 | 'Down' | Decrease Tx Power |
+| 1 | 'Up' | Increase Tx Power |
+
+#### 5B.3.2.6 Timeslot formats
+
+##### 5B.3.2.6.1 Downlink timeslot formats
+
+The downlink timeslot format depends on the spreading factor, midamble length and on the number of TFCI code word bits, as depicted in the table 8AF. For MBSFN operation the timeslot format also depends upon the symbol modulation scheme used. Slot formats 20-27 are only applicable to MBSFN operation with burst type 4.
+
+Table 8AF: Time slot formats for the Downlink
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | $N_{TFCI}$ code word (bits) | Bits/slot | $N_{Data/Slot}$ (bits) | $N_{data/data\ field}$ (bits) |
+|---------------|------------------|-------------------------|-----------------------------|-----------|------------------------|-------------------------------|
+| 0 | 32 | 1024 | 0 | 244 | 244 | 122 |
+| 1 | 32 | 1024 | 4 | 244 | 240 | 120 |
+| 2 | 32 | 1024 | 8 | 244 | 236 | 118 |
+| 3 | 32 | 1024 | 16 | 244 | 228 | 114 |
+| 4 | 32 | 1024 | 32 | 244 | 212 | 106 |
+| 5 | 32 | 512 | 0 | 276 | 276 | 138 |
+| 6 | 32 | 512 | 4 | 276 | 272 | 136 |
+| 7 | 32 | 512 | 8 | 276 | 268 | 134 |
+| 8 | 32 | 512 | 16 | 276 | 260 | 130 |
+| 9 | 32 | 512 | 32 | 276 | 244 | 122 |
+| 10 | 1 | 1024 | 0 | 7808 | 7808 | 3904 |
+| 11 | 1 | 1024 | 4 | 7808 | 7804 | 3902 |
+| 12 | 1 | 1024 | 8 | 7808 | 7800 | 3900 |
+| 13 | 1 | 1024 | 16 | 7808 | 7792 | 3896 |
+| 14 | 1 | 1024 | 32 | 7808 | 7776 | 3888 |
+| 15 | 1 | 512 | 0 | 8832 | 8832 | 4416 |
+| 16 | 1 | 512 | 4 | 8832 | 8828 | 4414 |
+| 17 | 1 | 512 | 8 | 8832 | 8824 | 4412 |
+| 18 | 1 | 512 | 16 | 8832 | 8816 | 4408 |
+| 19 | 1 | 512 | 32 | 8832 | 8800 | 4400 |
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------|
+| 20 (QPSK) | 32 | 640 | 0 | 264 | 264 | 132 |
+| 21 (QPSK) | 32 | 640 | 16 | 264 | 248 | 124 |
+| 22 (16QAM) | 32 | 640 | 0 | 528 | 528 | 264 |
+| 23 (16QAM) | 32 | 640 | 16 | 528 | 512 | 256 |
+| 24 (QPSK) | 1 | 640 | 0 | 8448 | 8448 | 4224 |
+| 25 (QPSK) | 1 | 640 | 16 | 8448 | 8432 | 4216 |
+| 26 (16QAM) | 1 | 640 | 0 | 16896 | 16896 | 8448 |
+| 27 (16QAM) | 1 | 640 | 16 | 16896 | 16880 | 8440 |
+
+##### 5B.3.2.6.2 Uplink timeslot formats
+
+The uplink timeslot format depends on the spreading factor, midamble length, guard period length and on the number of TFCI code word bits. Due to TPC, different amount of bits are mapped to the two data fields. The timeslot formats are depicted in the table 8AG. Note that slot format #90 shall only be used for HS\_SICH.
+
+**Table 8AG: Time slot formats for the Uplink**
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 | 32 | 1024 | 192 | 0 | 0 | 244 | 244 | 122 | 122 |
+| 1 | 32 | 1024 | 192 | 0 | 2 | 244 | 242 | 122 | 120 |
+| 2 | 32 | 1024 | 192 | 4 | 2 | 244 | 238 | 120 | 118 |
+| 3 | 32 | 1024 | 192 | 8 | 2 | 244 | 234 | 118 | 116 |
+| 4 | 32 | 1024 | 192 | 16 | 2 | 244 | 226 | 114 | 112 |
+| 5 | 32 | 1024 | 192 | 32 | 2 | 244 | 210 | 106 | 104 |
+| 6 | 32 | 512 | 192 | 0 | 0 | 276 | 276 | 138 | 138 |
+| 7 | 32 | 512 | 192 | 0 | 2 | 276 | 274 | 138 | 136 |
+| 8 | 32 | 512 | 192 | 4 | 2 | 276 | 270 | 136 | 134 |
+| 9 | 32 | 512 | 192 | 8 | 2 | 276 | 266 | 134 | 132 |
+| 10 | 32 | 512 | 192 | 16 | 2 | 276 | 258 | 130 | 128 |
+| 11 | 32 | 512 | 192 | 32 | 2 | 276 | 242 | 122 | 120 |
+| 12 | 16 | 1024 | 192 | 0 | 0 | 488 | 488 | 244 | 244 |
+| 13 | 16 | 1024 | 192 | 0 | 2 | 486 | 484 | 244 | 240 |
+| 14 | 16 | 1024 | 192 | 4 | 2 | 482 | 476 | 240 | 236 |
+| 15 | 16 | 1024 | 192 | 8 | 2 | 478 | 468 | 236 | 232 |
+| 16 | 16 | 1024 | 192 | 16 | 2 | 470 | 452 | 228 | 224 |
+| 17 | 16 | 1024 | 192 | 32 | 2 | 454 | 420 | 212 | 208 |
+| 18 | 16 | 512 | 192 | 0 | 0 | 552 | 552 | 276 | 276 |
+| 19 | 16 | 512 | 192 | 0 | 2 | 550 | 548 | 276 | 272 |
+| 20 | 16 | 512 | 192 | 4 | 2 | 546 | 540 | 272 | 268 |
+| 21 | 16 | 512 | 192 | 8 | 2 | 542 | 532 | 268 | 264 |
+| 22 | 16 | 512 | 192 | 16 | 2 | 534 | 516 | 260 | 256 |
+| 23 | 16 | 512 | 192 | 32 | 2 | 518 | 484 | 244 | 240 |
+| 24 | 8 | 1024 | 192 | 0 | 0 | 976 | 976 | 488 | 488 |
+| 25 | 8 | 1024 | 192 | 0 | 2 | 970 | 968 | 488 | 480 |
+| 26 | 8 | 1024 | 192 | 4 | 2 | 958 | 952 | 480 | 472 |
+| 27 | 8 | 1024 | 192 | 8 | 2 | 946 | 936 | 472 | 464 |
+| 28 | 8 | 1024 | 192 | 16 | 2 | 922 | 904 | 456 | 448 |
+| 29 | 8 | 1024 | 192 | 32 | 2 | 874 | 840 | 424 | 416 |
+| 30 | 8 | 512 | 192 | 0 | 0 | 1104 | 1104 | 552 | 552 |
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 31 | 8 | 512 | 192 | 0 | 2 | 1098 | 1096 | 552 | 544 |
+| 32 | 8 | 512 | 192 | 4 | 2 | 1086 | 1080 | 544 | 536 |
+| 33 | 8 | 512 | 192 | 8 | 2 | 1074 | 1064 | 536 | 528 |
+| 34 | 8 | 512 | 192 | 16 | 2 | 1050 | 1032 | 520 | 512 |
+| 35 | 8 | 512 | 192 | 32 | 2 | 1002 | 968 | 488 | 480 |
+| 36 | 4 | 1024 | 192 | 0 | 0 | 1952 | 1952 | 976 | 976 |
+| 37 | 4 | 1024 | 192 | 0 | 2 | 1938 | 1936 | 976 | 960 |
+| 38 | 4 | 1024 | 192 | 4 | 2 | 1910 | 1904 | 960 | 944 |
+| 39 | 4 | 1024 | 192 | 8 | 2 | 1882 | 1872 | 944 | 928 |
+| 40 | 4 | 1024 | 192 | 16 | 2 | 1826 | 1808 | 912 | 896 |
+| 41 | 4 | 1024 | 192 | 32 | 2 | 1714 | 1680 | 848 | 832 |
+| 42 | 4 | 512 | 192 | 0 | 0 | 2208 | 2208 | 1104 | 1104 |
+| 43 | 4 | 512 | 192 | 0 | 2 | 2194 | 2192 | 1104 | 1088 |
+| 44 | 4 | 512 | 192 | 4 | 2 | 2166 | 2160 | 1088 | 1072 |
+| 45 | 4 | 512 | 192 | 8 | 2 | 2138 | 2128 | 1072 | 1056 |
+| 46 | 4 | 512 | 192 | 16 | 2 | 2082 | 2064 | 1040 | 1024 |
+| 47 | 4 | 512 | 192 | 32 | 2 | 1970 | 1936 | 976 | 960 |
+| 48 | 2 | 1024 | 192 | 0 | 0 | 3904 | 3904 | 1952 | 1952 |
+| 49 | 2 | 1024 | 192 | 0 | 2 | 3874 | 3872 | 1952 | 1920 |
+| 50 | 2 | 1024 | 192 | 4 | 2 | 3814 | 3808 | 1920 | 1888 |
+| 51 | 2 | 1024 | 192 | 8 | 2 | 3754 | 3744 | 1888 | 1856 |
+| 52 | 2 | 1024 | 192 | 16 | 2 | 3634 | 3616 | 1824 | 1792 |
+| 53 | 2 | 1024 | 192 | 32 | 2 | 3394 | 3360 | 1696 | 1664 |
+| 54 | 2 | 512 | 192 | 0 | 0 | 4416 | 4416 | 2208 | 2208 |
+| 55 | 2 | 512 | 192 | 0 | 2 | 4386 | 4384 | 2208 | 2176 |
+| 56 | 2 | 512 | 192 | 4 | 2 | 4326 | 4320 | 2176 | 2144 |
+| 57 | 2 | 512 | 192 | 8 | 2 | 4266 | 4256 | 2144 | 2112 |
+| 58 | 2 | 512 | 192 | 16 | 2 | 4146 | 4128 | 2080 | 2048 |
+| 59 | 2 | 512 | 192 | 32 | 2 | 3906 | 3872 | 1952 | 1920 |
+| 59a | 1 | 1024 | 192 | 0 | 0 | 7808 | 7808 | 3904 | 3904 |
+| 59b | 1 | 1024 | 192 | 0 | 2 | 7746 | 7744 | 3904 | 3840 |
+| 59c | 1 | 1024 | 192 | 4 | 2 | 7622 | 7616 | 3840 | 3776 |
+| 59d | 1 | 1024 | 192 | 8 | 2 | 7498 | 7488 | 3776 | 3712 |
+| 59e | 1 | 1024 | 192 | 16 | 2 | 7250 | 7232 | 3648 | 3584 |
+| 59f | 1 | 1024 | 192 | 32 | 2 | 6754 | 6720 | 3392 | 3328 |
+| 59g | 1 | 512 | 192 | 0 | 0 | 8832 | 8832 | 4416 | 4416 |
+| 59h | 1 | 512 | 192 | 0 | 2 | 8770 | 8768 | 4416 | 4352 |
+| 59i | 1 | 512 | 192 | 4 | 2 | 8646 | 8640 | 4352 | 4288 |
+| 59j | 1 | 512 | 192 | 8 | 2 | 8522 | 8512 | 4288 | 4224 |
+| 59k | 1 | 512 | 192 | 16 | 2 | 8274 | 8256 | 4160 | 4096 |
+| 59l | 1 | 512 | 192 | 32 | 2 | 7778 | 7744 | 3904 | 3840 |
+| 60 | 32 | 1024 | 384 | 0 | 0 | 232 | 232 | 122 | 110 |
+| 61 | 32 | 1024 | 384 | 0 | 2 | 232 | 230 | 122 | 108 |
+| 62 | 32 | 1024 | 384 | 4 | 2 | 232 | 226 | 120 | 106 |
+| 63 | 32 | 1024 | 384 | 8 | 2 | 232 | 222 | 118 | 104 |
+| 64 | 32 | 1024 | 384 | 16 | 2 | 232 | 214 | 114 | 100 |
+| 65 | 32 | 1024 | 384 | 32 | 2 | 232 | 198 | 106 | 92 |
+| 66 | 16 | 1024 | 384 | 0 | 0 | 464 | 464 | 244 | 220 |
+| 67 | 16 | 1024 | 384 | 0 | 2 | 462 | 460 | 244 | 216 |
+| 68 | 16 | 1024 | 384 | 4 | 2 | 458 | 452 | 240 | 212 |
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 69 | 16 | 1024 | 384 | 8 | 2 | 454 | 444 | 236 | 208 |
+| 70 | 16 | 1024 | 384 | 16 | 2 | 446 | 428 | 228 | 200 |
+| 71 | 16 | 1024 | 384 | 32 | 2 | 430 | 396 | 212 | 184 |
+| 72 | 8 | 1024 | 384 | 0 | 0 | 928 | 928 | 488 | 440 |
+| 73 | 8 | 1024 | 384 | 0 | 2 | 922 | 920 | 488 | 432 |
+| 74 | 8 | 1024 | 384 | 4 | 2 | 910 | 904 | 480 | 424 |
+| 75 | 8 | 1024 | 384 | 8 | 2 | 898 | 888 | 472 | 416 |
+| 76 | 8 | 1024 | 384 | 16 | 2 | 874 | 856 | 456 | 400 |
+| 77 | 8 | 1024 | 384 | 32 | 2 | 826 | 792 | 424 | 368 |
+| 78 | 4 | 1024 | 384 | 0 | 0 | 1856 | 1856 | 976 | 880 |
+| 79 | 4 | 1024 | 384 | 0 | 2 | 1842 | 1840 | 976 | 864 |
+| 80 | 4 | 1024 | 384 | 4 | 2 | 1814 | 1808 | 960 | 848 |
+| 81 | 4 | 1024 | 384 | 8 | 2 | 1786 | 1776 | 944 | 832 |
+| 82 | 4 | 1024 | 384 | 16 | 2 | 1730 | 1712 | 912 | 800 |
+| 83 | 4 | 1024 | 384 | 32 | 2 | 1618 | 1584 | 848 | 736 |
+| 84 | 2 | 1024 | 384 | 0 | 0 | 3712 | 3712 | 1952 | 1760 |
+| 85 | 2 | 1024 | 384 | 0 | 2 | 3682 | 3680 | 1952 | 1728 |
+| 86 | 2 | 1024 | 384 | 4 | 2 | 3622 | 3616 | 1920 | 1696 |
+| 87 | 2 | 1024 | 384 | 8 | 2 | 3562 | 3552 | 1888 | 1664 |
+| 88 | 2 | 1024 | 384 | 16 | 2 | 3442 | 3424 | 1824 | 1600 |
+| 89 | 2 | 1024 | 384 | 32 | 2 | 3202 | 3168 | 1696 | 1472 |
+| 89a | 1 | 1024 | 384 | 0 | 0 | 7424 | 7424 | 3904 | 3520 |
+| 89b | 1 | 1024 | 384 | 0 | 2 | 7362 | 7360 | 3904 | 3456 |
+| 89c | 1 | 1024 | 384 | 4 | 2 | 7238 | 7232 | 3840 | 3392 |
+| 89d | 1 | 1024 | 384 | 8 | 2 | 7114 | 7104 | 3776 | 3328 |
+| 89e | 1 | 1024 | 384 | 16 | 2 | 6866 | 6848 | 3648 | 3200 |
+| 89f | 1 | 1024 | 384 | 32 | 2 | 6370 | 6336 | 3392 | 2944 |
+| 90 | 32 | 1024 | 192 | 0 | 8 | 244 | 236 | 122 | 114 |
+
+### 5B.3.3 Training sequences for spread bursts
+
+In this subclause, the training sequences for usage as midambles in burst type 1, 2, 3 and 4 (see subclause 5B.3.2) are defined. The training sequences, i.e. midambles, of different users active in the same cell and same time slot are cyclically shifted versions of one cell-specific single basic midamble code. In the case of MBSFN timeslots there is only a single midamble and this is derived from a single basic midamble code which is not necessarily cell-specific. The applicable basic midamble codes are given in Annex AB.1, Annex AB.2 and Annex AB.2A. As different basic midamble codes are required for different burst formats, Annex AB.1 shows the basic midamble codes $\mathbf{m}_P$ for burst type 1 and 3, Annex AB.2 shows $\mathbf{m}_{PS}$ for burst type 2 and Annex AB.2A shows $\mathbf{m}_P$ for burst type 4. It should be noted that burst type 2 must not be mixed with burst type 1 or 3 in the same timeslot of one cell and furthermore burst type 4 shall not be mixed with any other burst type in the same timeslot of one cell.
+
+The basic midamble codes in Annex AB.1, Annex AB.2 and Annex AB.2A are listed in hexadecimal notation. The binary form of the basic midamble code shall be derived according to table 6 (section 5.2.3).
+
+For each particular basic midamble code, its binary representation can be written as a vector $\mathbf{m}_P$ :
+
+$$\mathbf{m}_P = (m_1, m_2, \dots, m_P) \quad (1)$$
+
+According to Annex AB.1, the size of this vector $\mathbf{m}_P$ is $P=912$ for burst type 1 and 3. According to Annex AB.2, the size of this vector $\mathbf{m}_P$ is $P=456$ for burst type 2. According to Annex AB.2A, the size of vector $\mathbf{m}_P$ is $P=384$ for burst
+
+type 4. As QPSK modulation is used, the training sequences are transformed into a complex form, denoted as the complex vector $\underline{\mathbf{m}}^P$ :
+
+$$\underline{\mathbf{m}}^P = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_P) \quad (2)$$
+
+The elements $\underline{m}_i$ of $\underline{\mathbf{m}}^P$ are derived from elements $m_i$ of $\mathbf{m}^P$ using equation (3):
+
+$$\underline{m}_i = (j)^i \cdot m_i \text{ for all } i = 1, \dots, P \quad (3)$$
+
+Hence, the elements $\underline{m}_i$ of the complex basic midamble code are alternating real and imaginary.
+
+To derive the required training sequences (different shifts), this vector $\underline{\mathbf{m}}^P$ is periodically extended to the size:
+
+$$i_{\max} = L_m + (K'-1)W + \lfloor P/K \rfloor \quad (4)$$
+
+Notes on equation (4):
+
+- $L_m$ : Midamble length
+- $K'$ : Maximum number of different midamble shifts in a cell, when no intermediate shifts are used. This value depends on the midamble length.
+- $K$ : Maximum number of different midamble shifts in a cell, when intermediate shifts are used, $K=2K'$ .
+This value depends on the midamble length.
+Note that intermediate shifts are not used for burst type 4, i.e. $K=K'=1$ for burst type 4.
+- $W$ : Shift between the midambles, when the number of midambles is $K'$ .
+- $\lfloor x \rfloor$ denotes the largest integer smaller or equal to $x$
+
+Allowed values for $L_m$ , $K'$ and $W$ are given in Annex AB.1, Annex AB.2 and Annex AB.2A.
+
+So we obtain a new vector $\underline{\mathbf{m}}$ containing the periodic basic midamble sequence:
+
+$$\underline{\mathbf{m}} = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{i_{\max}}) = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{L_m + (K'-1)W + \lfloor P/K \rfloor}) \quad (5)$$
+
+The first $P$ elements of this vector $\underline{\mathbf{m}}$ are the same ones as in vector $\underline{\mathbf{m}}^P$ , the following elements repeat the beginning:
+
+$$\underline{m}_i = \underline{m}_{i-P} \text{ for the subset } i = (P+1), \dots, i_{\max} \quad (6)$$
+
+Using this periodic basic midamble sequence $\underline{\mathbf{m}}$ for each shift $k$ a midamble $\underline{\mathbf{m}}^{(k)}$ of length $L_m$ is derived, which can be written as a shift specific vector:
+
+$$\underline{\mathbf{m}}^{(k)} = (\underline{m}_1^{(k)}, \underline{m}_2^{(k)}, \dots, \underline{m}_{L_m}^{(k)}) \quad (7)$$
+
+The $L_m$ midamble elements $\underline{m}_i^{(k)}$ are generated for each midamble of the first $K'$ shifts ( $k = 1, \dots, K'$ ) based on:
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-k)W} \text{ with } i = 1, \dots, L_m \text{ and } k = 1, \dots, K' \quad (8)$$
+
+The elements of midambles for the second $K'$ shifts ( $k = (K'+1), \dots, K = (K'+1), \dots, 2K'$ ) are generated based on a slight modification of this formula introducing intermediate shifts:
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K-k-1)W+\lfloor P/K \rfloor} \text{ with } i=1,\dots,L_m \text{ and } k=K'+1,\dots,K-1 \quad (9)$$
+
+$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-1)W+\lfloor P/K \rfloor} \text{ with } i=1,\dots,L_m \text{ and } k=K \quad (10)$$
+
+The number $K_{\text{Cell}}$ of midambles that is supported in each cell can be smaller than $K$ , depending on the cell size and the possible delay spreads, see Annex AB. The number $K_{\text{Cell}}$ is signalled by higher layers. The midamble sequences derived according to equations (7) to (10) have complex values and are not subject to channelisation or scrambling process, i.e. the elements $\underline{m}_i^{(k)}$ represent complex chips for usage in the pulse shaping process at modulation.
+
+The term 'a midamble code set' or 'a midamble code family' denotes $K$ specific midamble codes $\underline{m}^{(k)}$ ; $k=1,\dots,K$ , based on a single basic midamble code $\underline{m}^P$ according to (1).
+
+### 5B.3.4 Beamforming
+
+Support for beamforming is identical to 3.84Mcps TDD cf. [5.2.4 Beamforming].
+
+## 5B.4 Common physical channels
+
+### 5B.4.1 Primary common control physical channel (P-CCPCH)
+
+The BCH as described in subclause 4.1.2 is mapped onto the Primary Common Control Physical Channel (P-CCPCH). The position (time slot / code) of the P-CCPCH is known from the Physical Synchronisation Channel (PSCH), see subclause 5B.4.4.
+
+#### 5B.4.1.1 P-CCPCH Spreading
+
+The P-CCPCH uses fixed spreading with a spreading factor $SF = 32$ as described in subclause 5B.3.1.1. The P-CCPCH always uses channelisation code .
+
+#### 5B.4.1.2 P-CCPCH Burst Types
+
+Burst type 1 as described in subclause 5B.2.2 is used for the P-CCPCH unless the entire carrier is dedicated to MBSFN then burst type 4 is used for P-CCPCH. No TFCI is applied for the P-CCPCH.
+
+#### 5B.4.1.3 P-CCPCH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5B.3.3 are used for the P-CCPCH.
+
+### 5B.4.2 Secondary common control physical channel (S-CCPCH)
+
+PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements.
+
+#### 5B.4.2.1 S-CCPCH Spreading
+
+The S-CCPCH uses fixed spreading with a spreading factor $SF = 32$ as described in subclause 5B.3.1.1. When S-CCPCH is used for MBSFN operation the spreading factor may be $SF = 32$ or $SF = 1$ .
+
+#### 5B.4.2.2 S-CCPCH Burst Types
+
+Burst types 1, 2 or 4 as described in subclause 5B.3.2 are used for the S-CCPCHs. TFCI may be applied for S-CCPCHs.
+
+##### 5B.4.2.2A S-CCPCH Modulation
+
+When S-CCPCH is used for MBSFN operation, burst type 4 shall be used and the modulation may be QPSK or 16QAM, see table 8AF for slot formats. When S-CCPCH is used for all other purposes the modulation shall be QPSK.
+
+#### 5B.4.2.3 S-CCPCH Training sequences
+
+The training sequences, i.e. midambles, as described in subclause 5B.3.3 are used for the S-CCPCH.
+
+### 5B.4.3 The physical random access channel (PRACH)
+
+The RACH as described in subclause 4.1.2 is mapped onto one uplink physical random access channel (PRACH).
+
+#### 5B.4.3.1 PRACH Spreading
+
+The uplink PRACH uses either spreading factor $SF=32$ or $SF=16$ as described in subclause 5B.3.1.2. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH).
+
+#### 5B.4.3.2 PRACH Burst Type
+
+The UEs send uplink access bursts of type 3 randomly in the PRACH. TFCI and TPC are not applied for the PRACH.
+
+#### 5B.4.3.3 PRACH Training sequences
+
+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$ . The basic midamble codes for burst type 3 are shown in Annex AB. The necessary time shifts are obtained by choosing all $k=1,2,3,\dots,K'$ . Different cells use different periodic basic codes, i.e. different midamble sets.
+
+#### 5B.4.3.4 PRACH timeslot formats
+
+For the PRACH the timeslot format is only spreading factor dependent. The timeslot formats 60 and 66 of table 8AG are applicable for the PRACH.
+
+#### 5B.4.3.5 Association between Training Sequences and Channelisation Codes
+
+For the PRACH the fixed association between a training sequence and associated channelisation code is defined in figure 18AK. In this figure, midamble $m_j^{(k)}$ is formed from the $k^{\text{th}}$ shift of the original basic midamble code ( $j=1$ ) or of the time-inverted basic midamble code ( $j=2$ ).
+
+
+
+Figure 18AK: Association of midambles to channelisation codes for PRACH in the OVSF tree. The diagram shows a hierarchical tree structure starting from a single root on the left. The tree branches out to the right, with nodes labeled with midamble identifiers (m) and channelisation codes (c). The first level of branches leads to nodes labeled m1^(1) - c16^(1), m1^(3) - c16^(2), m1^(5) - c16^(3), and m1^(7) - c16^(4). These further branch into nodes labeled m1^(1) - c32^(1) through m1^(8) - c32^(8). The second level of branches from the root leads to nodes labeled m2^(1) - c16^(5), m2^(3) - c16^(6), m2^(5) - c16^(7), and m2^(7) - c16^(8). These further branch into nodes labeled m2^(1) - c32^(9) through m2^(8) - c32^(16). The third level of branches from the root leads to nodes labeled m1^(2) - c16^(9), m1^(4) - c16^(10), m1^(6) - c16^(11), and m1^(8) - c16^(12). These further branch into nodes labeled m1^(1) - c32^(1) through m1^(8) - c32^(8). The fourth level of branches from the root leads to nodes labeled m2^(2) - c16^(13), m2^(4) - c16^(14), m2^(6) - c16^(15), and m2^(8) - c16^(16). These further branch into nodes labeled m2^(1) - c32^(9) through m2^(8) - c32^(16).
+
+Figure 18AK: Association of midambles to channelisation codes for PRACH in the OVSF tree
+
+### 5B.4.4 The synchronisation channel (SCH)
+
+The code group of a cell can be derived from the synchronisation channel. In order not to limit uplink/downlink asymmetry, the SCH is mapped on one or two downlink slots per frame only.
+
+There are two cases of SCH and P-CCPCH allocation as follows:
+
+- Case 1) SCH and P-CCPCH allocated in TS#k, k=0...14
+- Case 2) SCH allocated in two TS: TS#k and TS#k+8, k=0...6; P-CCPCH allocated in TS#k.
+
+The position of SCH (value of k) in the frame can change on a long term basis in any case.
+
+Due to this SCH scheme, the position of P-CCPCH is known from the SCH.
+
+Figure 18AL is an example for transmission of SCH, k=0, of Case 2.
+
+
+
+Figure 18AL: Scheme for Synchronisation channel SCH. The diagram shows a frame structure at the top with 15 slots, where 1 frame = 10ms. Two slots are highlighted with a shaded pattern. Below, a detailed view of a single time slot is shown, labeled 'Time slot = 5120 x Tc'. The slot contains four code sequences: a primary sequence C\_p and three parallel secondary sequences b\_1 C\_{s,1}, b\_2 C\_{s,2}, and b\_3 C\_{s,3}. Each sequence is 512 chips long. The primary sequence C\_p starts at a time offset t\_offset,n from the beginning of the slot. The power of the primary sequence is P\_p, and the total power of the three secondary sequences is P\_s. Each secondary sequence has a power of P\_s/3. Vertical double-headed arrows indicate the power levels for each sequence.
+
+$b_i \in \{\pm 1, \pm j\}$ , $C_{s,i} \in \{C_0, C_1, C_3, C_4, C_5, C_6, C_8, C_{10}, C_{12}, C_{13}, C_{14}, C_{15}\}$ , $i = 1, 2, 3$ ; see section 8.4
+
+**Figure 18AL: Scheme for Synchronisation channel SCH consisting of one primary sequence $C_p$ and 3 parallel secondary sequences $C_{s,i}$ in slot $k$ and $k+8$ (example for $k=0$ in Case 2)**
+
+As depicted in figure 18AL, the SCH consists of a primary and three secondary code sequences each 512 chips long. The primary and secondary code sequences are defined in [8].
+
+Due to mobile to mobile interference, it is mandatory for public TDD systems to keep synchronisation between base stations. As a consequence of this, a capture effect concerning SCH can arise. The time offset $t_{offset,n}$ enables the system to overcome the capture effect.
+
+The time offset $t_{offset,n}$ is one of 32 values, depending on the code group of the cell, $n$ , [8]. Note that the cell parameter will change from frame to frame, but the cell will belong to only one code group and thus have one time offset $t_{offset,n}$ . The exact value for $t_{offset,n}$ , is given by:
+
+### 5B.4.5 Physical Uplink Shared Channel (PUSCH)
+
+The USCH as described in subclause 4.1.2 is mapped onto one or more physical uplink shared channels (PUSCH). Timing advance, as described in [9], is applied to the PUSCH.
+
+#### 5B.4.5.1 PUSCH Spreading
+
+The spreading factors that can be applied to the PUSCH are $SF = 1, 2, 4, 8, 16$ or $32$ as described in subclause 5B.3.1.2.
+
+#### 5B.4.5.2 PUSCH Burst Types
+
+Burst types 1, 2 or 3 as described in subclause 5B.3.2 can be used for PUSCH. TFCI and TPC can be transmitted on the PUSCH.
+
+#### 5B.4.5.3 PUSCH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the PUSCH.
+
+#### 5B.4.5.4 UE Selection
+
+The UE that shall transmit on the PUSCH is selected by higher layer signalling.
+
+### 5B.4.6 Physical Downlink Shared Channel (PDSCH)
+
+The DSCH as described in subclause 4.1.2 is mapped onto one or more physical downlink shared channels (PDSCH).
+
+#### 5B.4.6.1 PDSCH Spreading
+
+The PDSCH uses either spreading factor $SF = 32$ or $SF = 1$ as described in subclause 5B.3.1.1.
+
+#### 5B.4.6.2 PDSCH Burst Types
+
+Burst types 1 or 2 as described in subclause 5B.3.2 can be used for PDSCH. TFCI can be transmitted on the PDSCH.
+
+#### 5B.4.6.3 PDSCH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the PDSCH.
+
+#### 5B.4.6.4 UE Selection
+
+To indicate to the UE that there is data to decode on the DSCH, higher layer signalling is used.
+
+### 5B.4.7 The Paging Indicator Channel (PICH)
+
+The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators.
+
+#### 5B.4.7.1 Mapping of Paging Indicators to the PICH bits
+
+Figure 18AM depicts the structure of a PICH burst and the numbering of the bits within the burst. The same burst type is used for the PICH in every cell. $N_{PIB}$ bits in a normal burst of type 1 or 2 are used to carry the paging indicators, where $N_{PIB}$ depends on the burst type: $N_{PIB}=240$ for burst type 1 and $N_{PIB}=272$ for burst type 2. The bits $s_{N_{PIB}+1}, \dots, s_{N_{PIB}+4}$ adjacent to the midamble are reserved for possible future use.
+
+
+
+The diagram illustrates the bit structure of a PICH burst within a single time slot. The burst is composed of several bit groups and a midamble. On the left, the 'Bits for Page Indication' section includes bits $s_1, s_3, \dots, s_{N_{PIB}-1}$ . This is followed by a 'Reserved Bits' section containing bits $s_{N_{PIB}+1}, s_{N_{PIB}+3}$ . The central part of the burst is the 'Midamble'. To the right of the midamble, another 'Reserved Bits' section contains bits $s_{N_{PIB}+2}, s_{N_{PIB}+4}$ . The final 'Bits for Page Indication' section on the right includes bits $s_2, s_4, \dots, s_{N_{PIB}}$ . The burst concludes with a 'Guard Period'. A horizontal double-headed arrow at the bottom indicates the total duration of the burst as '1 Time Slot'.
+
+Diagram of a PICH burst structure within a 1 Time Slot. The burst is divided into three main sections: 'Bits for Page Indication' (left), 'Reserved Bits' (middle), and 'Bits for Page Indication' (right). The 'Bits for Page Indication' sections contain bits s1, s3, ..., s\_{N\_{PIB}-1}, s\_{N\_{PIB}+1}, s\_{N\_{PIB}+3} on the left and s\_{N\_{PIB}+2}, s\_{N\_{PIB}+4}, s2, s4, ..., s\_{N\_{PIB}} on the right. The 'Reserved Bits' section contains the 'Midamble'. The entire burst is followed by a 'Guard Period'. The total duration is labeled '1 Time Slot'.
+
+**Figure 18AM: Transmission and numbering of paging indicator carrying bits in a PICH burst**
+
+Each paging indicator $P_q$ in one time slot is mapped to the bits $\{s_{2L_{pi} \cdot q + 1}, \dots, s_{2L_{pi} \cdot (q+1)}}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each paging indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part; an example is shown in figure 18AN for a paging indicator length $L_{pi}$ of 4 symbols.
+
+
+
+Figure 18AN: Example of mapping of paging indicators on PICH bits for L\_Pi=4. The diagram shows two radio frame structures. The left frame has a total duration of 5120 T\_c and contains a Midamble of 512 Chips. It shows P\_0 and P\_33 as paging indicators, with 2 unused symbols. The right frame also has a total duration of 5120 T\_c and contains a Midamble of 1024 Chips. It shows P\_0 and P\_29 as paging indicators, with 2 unused symbols. Both frames include a GP (Guard Period) at the end.
+
+**Figure 18AN: Example of mapping of paging indicators on PICH bits for $L_{Pi}=4$**
+
+The setting of the paging indicators and the corresponding PICH bits (including the reserved ones) is described in [4].
+
+$N_{Pi}$ paging indicators of length $L_{Pi}=2$ , $L_{Pi}=4$ or $L_{Pi}=8$ symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators $N_{Pi}$ per radio frame is given by the paging indicator length and the burst type, which are both known by higher layer signalling. In table 8AH this number is shown for the different possibilities of burst types and paging indicator lengths.
+
+**Table 8AH: Number $N_{Pi}$ of paging indicators per time slot for the different burst types and paging indicator lengths $L_{Pi}$**
+
+| | $L_{Pi}=2$ | $L_{Pi}=4$ | $L_{Pi}=8$ |
+|--------------|-------------|-------------|-------------|
+| Burst Type 1 | $N_{Pi}=60$ | $N_{Pi}=30$ | $N_{Pi}=15$ |
+| Burst Type 2 | $N_{Pi}=68$ | $N_{Pi}=34$ | $N_{Pi}=17$ |
+
+#### 5B.4.7.2 Structure of the PICH over multiple radio frames
+
+The structure of PICH over multiple radio frames is identical to the structure of PICH in 3.84Mcps TDD cf [section 5.3.7.2].
+
+#### 5B.4.7.3 PICH Training sequences
+
+The training sequences, i.e. midambles for the PICH, are generated as described in subclause 5B.3.3. The allocation of midambles depends on whether SCTD is applied to the PICH.
+
+- If no antenna diversity is applied the PICH the midambles can be allocated as described in subclause 5B.7.
+- If SCTD antenna diversity is applied to the PICH the allocation of midambles shall be as described in [9].
+
+### 5B.4.8 High Speed Physical Downlink Shared Channel (HS-PDSCH)
+
+The HS-PDSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH).
+
+#### 5B.4.8.1 HS-PDSCH Spreading
+
+The HS-PDSCH shall use either spreading factor $SF = 32$ or $SF=1$ , as described in 5B.3.1.1.
+
+#### 5B.4.8.2 HS-PDSCH Burst Types
+
+Burst types 1 or 2 as described in subclause 5B.3.2 can be used for PDSCH. TFCI shall not be transmitted on the HS-PDSCH. The TF of the HS-PDSCH is derived from the associated HS-SCCH.
+
+#### 5B.4.8.3 HS-PDSCH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the HS-PDSCH.
+
+#### 5B.4.8.4 UE Selection
+
+To indicate to the UE that there is data to decode on the HS-DSCH, the UE id on the associated HS-SCCH shall be used.
+
+#### 5B.4.8.5 HS-PDSCH timeslot formats
+
+An HS-PDSCH may use QPSK or 16QAM modulation symbols. The time slot formats are shown in table 8AI.
+
+Table 8AI: Time slot formats for the HS-PDSCH
+
+| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) |
+|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------|
+| 0 (QPSK) | 32 | 1024 | 0 | 244 | 244 | 122 |
+| 1 (16QAM) | 32 | 1024 | 0 | 488 | 488 | 244 |
+| 2 (QPSK) | 32 | 512 | 0 | 276 | 276 | 138 |
+| 3 (16QAM) | 32 | 512 | 0 | 552 | 552 | 276 |
+| 4 (QPSK) | 1 | 1024 | 0 | 7808 | 7808 | 3904 |
+| 5 (16QAM) | 1 | 1024 | 0 | 15616 | 15616 | 7808 |
+| 6 (QPSK) | 1 | 512 | 0 | 8832 | 8832 | 4416 |
+| 7(16QAM) | 1 | 512 | 0 | 17664 | 17664 | 8832 |
+
+### 5B.4.9 Shared Control Channel for HS-DSCH (HS-SCCH)
+
+The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below.
+
+#### 5B.4.9.1 HS-SCCH Spreading
+
+The HS-SCCH shall use spreading factor SF = 32, as described in 5B.3.1.1.
+
+#### 5B.4.9.2 HS-SCCH Burst Types
+
+Burst type 1 as described in subclause 5B.3.2 can be used for HS-SCCH. TFCI shall not be transmitted on the HS-SCCH.
+
+#### 5B.4.9.3 HS-SCCH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the HS-SCCH.
+
+#### 5B.4.9.4 HS-SCCH timeslot formats
+
+The HS-SCCH always uses time slot format #0 from table 8AF, see section 5B.3.2.6.1.
+
+### 5B.4.10 Shared Information Channel for HS-DSCH (HS-SICH)
+
+The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below.
+
+#### 5B.4.10.1 HS-SICH Spreading
+
+The HS-SICH shall use spreading factor SF = 32, as described in 5B.3.1.2.
+
+#### 5B.4.10.2 HS-SICH Burst Types
+
+Burst type 1 as described in subclause 5B.3.2 can be used for HS-SICH. TFCI shall not be transmitted on the HS-SICH, however, the HS-SICH shall carry TPC information.
+
+#### 5B.4.10.3 HS-SICH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the HS-SICH.
+
+#### 5B.4.10.4 HS-SICH timeslot formats
+
+The HS-SICH shall use time slot format #90 from table 8AF, see section 5B.3.2.6.2.
+
+### 5B.4.11 The MBMS Indicator Channel (MICH)
+
+The MBMS Indicator Channel (MICH) is a physical channel used to carry the MBMS notification indicators. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
+
+#### 5B.4.11.1 Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2
+
+Figure 18AO depicts the structure of a MICH burst and the numbering of the bits within the burst. The same burst type is used for the MICH in every cell. $N_{NIB}$ bits in a normal burst of type 1 or 2 are used to carry the MBMS notification indicators, where $N_{NIB}$ depends on the burst type: $N_{NIB}=240$ for burst type 1 and $N_{NIB}=272$ for burst type 2. The bits $s_{NNIB+1}, …, s_{NNIB+4}$ adjacent to the midamble are reserved for possible future use.
+
+
+
+The diagram illustrates a single time slot containing a MICH burst. The structure is as follows:
+
+- Bits for Notification Indication (Part 1):** Contains bits $s_1, s_3, …, s_{NNIB-1}$ .
+- Reserved Bits (Part 1):** Bits $s_{NNIB+1}$ and $s_{NNIB+3}$ , shown with diagonal hatching, immediately preceding the midamble.
+- Midamble:** A central block labeled 'Midamble'.
+- Reserved Bits (Part 2):** Bits $s_{NNIB+2}$ and $s_{NNIB+4}$ , shown with diagonal hatching, immediately following the midamble.
+- Bits for Notification Indication (Part 2):** Contains bits $s_2, s_4, …, s_{NNIB}$ .
+- Guard Period:** A final block at the end of the slot.
+
+Arrows indicate the span of 'Bits for Notification Indication', 'Reserved Bits', and the total '1 Time Slot'.
+
+Diagram of a MICH burst structure within 1 Time Slot. It shows two main data parts labeled 'Bits for Notification Indication' separated by a central 'Midamble' and 'Reserved Bits'.
+
+**Figure 18AO: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2**
+
+Each notification indicator $N_q$ in one time slot is mapped to the bits $\{s_{2L_{NI} \cdot q+1}, \dots, s_{2L_{NI} \cdot (q+1)}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each MBMS notification indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part: an example is shown in figure 18AP for a MBMS notification indicator length $L_{NI}$ of 4 symbols.
+
+
+
+The diagram shows two burst structures, both with a total length of $5120 T_c$ :
+
+- Left (Burst Type 2):** Shows mapping for indicators $N_0$ and $N_{33}$ . It includes a 'Midamble (256 Chips)' flanked by '2 unused symbols' (hatched blocks) and a 'GP' (Guard Period) at the end.
+- Right (Burst Type 1):** Shows mapping for indicators $N_0$ and $N_{29}$ . It includes a 'Midamble (512 Chips)' flanked by '2 unused symbols' (hatched blocks) and a 'GP' at the end.
+
+In both cases, the indicators are split between the two data portions of the burst.
+
+Diagram showing mapping examples for burst types 2 and 1 with L\_NI = 4.
+
+**Figure 18AP: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst types 2 and 1 respectively**
+
+The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7].
+
+$N_n$ MBMS notification indicators of length $L_{NI}=2, L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type,
+
+which are both known by higher layer signalling. In table 18AJ this number is shown for burst types 1 and 2 and differing MBMS notification indicator lengths.
+
+**Table 18AJ: Number $N_n$ of MBMS notification indicators per time slot for burst types 1 and 2 and differing MBMS notification indicator lengths $L_{NI}$**
+
+| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ |
+|--------------|------------|------------|------------|
+| Burst Type 1 | $N_n=60$ | $N_n=30$ | $N_n=15$ |
+| Burst Type 2 | $N_n=68$ | $N_n=34$ | $N_n=17$ |
+
+The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ .
+
+The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
+
+##### 5B.4.11.1A Mapping of MBMS Indicators to the MICH bits for burst type 4
+
+When an entire carrier is dedicated to MBSFN operation, the MICH shall use burst type 4. In this case $N_{NIB}=256$ and there are 8 reserved/unused bits adjacent to the midamble reserved for possible future use. The transmission and numbering of MBMS notification indicator carrying bits in a MICH burst is similar to that of figure 18AO with the exception of 4 reserved bits either side of the midamble as opposed to 2 for burst types 1 and 2. An example mapping is shown in figure 18AP.1 for a MBMS notification indicator length $L_{NI}$ of 4 symbols.
+
+
+
+Diagram of a MICH burst structure for burst type 4. The total length is 5120 Tc. The burst contains a central 'Midamble (640 Chips)' block. To the left and right of the midamble are '4 unused symbols' (hatched). The remaining bits are divided into segments for MBMS notification indicators. The first segment is labeled N0 and the last segment is labeled N31. The diagram shows the mapping of these indicators to the MICH bits.
+
+**Figure 18AP.1: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst type 4**
+
+The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7].
+
+$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 18AK this number is shown for the different possibilities of burst types and MBMS notification indicator lengths.
+
+**Table 18AK: Number $N_n$ of MBMS notification indicators per time slot for burst type 4 and differing MBMS notification indicator lengths $L_{NI}$**
+
+| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ |
+|--------------|------------|------------|------------|
+| Burst Type 4 | $N_n=64$ | $N_n=32$ | $N_n=16$ |
+
+The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ .
+
+The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
+
+#### 5B.4.11.2 MICH Training sequences
+
+The training sequences, i.e. midambles for the MICH, are generated as described in subclause 5B.3.3. The allocation of midambles depends on whether SCTD is applied to the MICH.
+
+- If no antenna diversity is applied the MICH the midambles can be allocated as described in subclause 5B.7.
+- If SCTD antenna diversity is applied to the MICH the allocation of midambles shall be as described in [9].
+
+Note that when the entire carrier is dedicated to MBSFN operation MICH employs burst type 4 as described in subclause 5B.4.11.1A. Burst type 4 supports a single midamble and hence SCTD is precluded from operation in such a scenario.
+
+### 5B.4.12 E-DCH Physical Uplink Channel (E-PUCH)
+
+One or more E-PUCH are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE. No other physical channels may be transmitted by a UE in an E-PUCH timeslot.
+
+Timing advance, as described in [9], subclause 4.3, is applied to the E-PUCH.
+
+#### 5B.4.12.1 E-UCCH
+
+The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is carried within indicator fields mapped to E-PUCH. Depending on the configuration by higher layers, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted.
+
+Higher layers shall indicate the maximum number of timeslots ( $N_{E-UCCH}$ ) that may contain E-UCCH/TPC in the E-DCH TTI. For an allocation of $n_{TS}$ E-PUCH timeslots, the UE shall transmit E-UCCH and TPC on the first $m$ allocated timeslots of the E-DCH TTI, where $m = \min(n_{TS}, N_{E-UCCH})$ .
+
+The E-UCCH comprises two parts, E-UCCH part 1 and E-UCCH part 2.
+
+E-UCCH part 1:
+
+- is of length 32 physical channel bits
+- is mapped to the TFCI field of the E-PUCH (16 bits either side of the midamble)
+- is spread at SF=32 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]
+- uses QPSK modulation
+
+E-UCCH part 2:
+
+- is of length 32 physical channel bits
+- is spread using the same spreading factor as the data payloads
+- uses the same modulation as the data payloads
+
+Figures 18APA and 18APB show the E-PUCH data burst with and without the E-UCCH/TPC fields.
+
+
+
+The diagram shows an E-PUCH data burst structure. It consists of a sequence of blocks: Data symbols, a Midamble (labeled 1024/512 chips), Data symbols, and a GP. Above the first Data symbols block, 'E-UCCH part 1' and 'E-UCCH part 2' are indicated. Within the Midamble block, 'TPC' is indicated. A horizontal double-headed arrow at the bottom indicates the total length of the burst is 5120 \* Tc.
+
+Diagram of E-PUCH data burst with E-UCCH part 1, E-UCCH part 2, and TPC. The burst consists of Data symbols, a Midamble (1024/512 chips), Data symbols, and a GP. E-UCCH part 1 and part 2 are located within the Data symbols, and TPC is located within the Midamble.
+
+Figure 18APA: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst
+
+
+
+The diagram shows an E-PUCH data burst structure without E-UCCH/TPC. It consists of a sequence of blocks: Data symbols, a Midamble (labeled 1024/512 chips), Data symbols, and a GP. A horizontal double-headed arrow at the bottom indicates the total length of the burst is 5120 \* Tc.
+
+Diagram of E-PUCH data burst without E-UCCH/TPC. The burst consists of Data symbols, a Midamble (1024/512 chips), Data symbols, and a GP. No E-UCCH or TPC are present.
+
+Figure 18APB: E-PUCH data burst without E-UCCH/TPC
+
+#### 5B.4.12.2 E-PUCH Spreading
+
+The spreading factors that can be applied to the E-PUCH are SF = 1, 2, 4, 8, 16, 32 as described in subclause 5B.3.1.2.
+
+#### 5B.4.12.3 E-PUCH Burst Types
+
+Burst types 1, 2 or 3 as described in subclause 5B.3.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH.
+
+#### 5B.4.12.4 PUSCH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the E-PUCH.
+
+#### 5B.4.12.5 UE Selection
+
+UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification.
+
+#### 5B.4.12.6 E-PUCH timeslot formats
+
+An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 19.
+
+Table 19: Timeslot formats for E-PUCH
+
+| slot format # | SF | Midamble Length (chips) | GP (chips) | N EUCCH1 (bits) | N EUCCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 0 (QPSK) | 32 | 1024 | 192 | 0 | 0 | 0 | 244 | 244 | 122 | 122 |
+| 1 (16QAM) | 32 | 1024 | 192 | 0 | 0 | 0 | 488 | 488 | 244 | 244 |
+
+| slot format # | SF | Midamble Length (chips) | GP (chips) | N UECCH1 (bits) | N UECCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 2 (QPSK) | 32 | 1024 | 192 | 32 | 32 | 2 | 244 | 178 | 90 | 88 |
+| 3 (16QAM) | 32 | 1024 | 192 | 32 | 32 | 2 | 454 | 388 | 196 | 192 |
+| 4 (QPSK) | 32 | 512 | 192 | 0 | 0 | 0 | 276 | 276 | 138 | 138 |
+| 5 (16QAM) | 32 | 512 | 192 | 0 | 0 | 0 | 552 | 552 | 276 | 276 |
+| 6 (QPSK) | 32 | 512 | 192 | 32 | 32 | 2 | 276 | 210 | 106 | 104 |
+| 7 (16QAM) | 32 | 512 | 192 | 32 | 32 | 2 | 518 | 452 | 228 | 224 |
+| 8 (QPSK) | 16 | 1024 | 192 | 0 | 0 | 0 | 488 | 488 | 244 | 244 |
+| 9 (16QAM) | 16 | 1024 | 192 | 0 | 0 | 0 | 976 | 976 | 488 | 488 |
+| 10 (QPSK) | 16 | 1024 | 192 | 32 | 32 | 2 | 454 | 388 | 196 | 192 |
+| 11 (16QAM) | 16 | 1024 | 192 | 32 | 32 | 2 | 874 | 808 | 408 | 400 |
+| 12 (QPSK) | 16 | 512 | 192 | 0 | 0 | 0 | 552 | 552 | 276 | 276 |
+| 13 (16QAM) | 16 | 512 | 192 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 |
+| 14 (QPSK) | 16 | 512 | 192 | 32 | 32 | 2 | 518 | 452 | 228 | 224 |
+| 15 (16QAM) | 16 | 512 | 192 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 |
+| 16 (QPSK) | 8 | 1024 | 192 | 0 | 0 | 0 | 976 | 976 | 488 | 488 |
+| 17 (16QAM) | 8 | 1024 | 192 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 |
+| 18 (QPSK) | 8 | 1024 | 192 | 32 | 32 | 2 | 874 | 808 | 408 | 400 |
+| 19 (16QAM) | 8 | 1024 | 192 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 |
+| 20 (QPSK) | 8 | 512 | 192 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 |
+| 21 (16QAM) | 8 | 512 | 192 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 |
+| 22 (QPSK) | 8 | 512 | 192 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 |
+| 23 (16QAM) | 8 | 512 | 192 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 |
+| 24 (QPSK) | 4 | 1024 | 192 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 |
+| 25 (16QAM) | 4 | 1024 | 192 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 |
+| 26 (QPSK) | 4 | 1024 | 192 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 |
+| 27 (16QAM) | 4 | 1024 | 192 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 |
+| 28 (QPSK) | 4 | 512 | 192 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 |
+| 29 (16QAM) | 4 | 512 | 192 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 |
+| 30 (QPSK) | 4 | 512 | 192 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 |
+| 31 (16QAM) | 4 | 512 | 192 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 |
+| 32 (QPSK) | 2 | 1024 | 192 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 |
+| 33 (16QAM) | 2 | 1024 | 192 | 0 | 0 | 0 | 7808 | 7808 | 3904 | 3904 |
+| 34 (QPSK) | 2 | 1024 | 192 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 |
+| 35 (16QAM) | 2 | 1024 | 192 | 32 | 32 | 2 | 6754 | 6688 | 3376 | 3312 |
+| 36 (QPSK) | 2 | 512 | 192 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 |
+| 37 (16QAM) | 2 | 512 | 192 | 0 | 0 | 0 | 8832 | 8832 | 4416 | 4416 |
+| 38 (QPSK) | 2 | 512 | 192 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 |
+| 39 (16QAM) | 2 | 512 | 192 | 32 | 32 | 2 | 7778 | 7712 | 3888 | 3824 |
+| 40 (QPSK) | 1 | 1024 | 192 | 0 | 0 | 0 | 7808 | 7808 | 3904 | 3904 |
+| 41 (16QAM) | 1 | 1024 | 192 | 0 | 0 | 0 | 15616 | 15616 | 7808 | 7808 |
+| 42 (QPSK) | 1 | 1024 | 192 | 32 | 32 | 2 | 6754 | 6688 | 3376 | 3312 |
+| 43 (16QAM) | 1 | 1024 | 192 | 32 | 32 | 2 | 13474 | 13408 | 6768 | 6640 |
+| 44 (QPSK) | 1 | 512 | 192 | 0 | 0 | 0 | 8832 | 8832 | 4416 | 4416 |
+| 45 (16QAM) | 1 | 512 | 192 | 0 | 0 | 0 | 17664 | 17664 | 8832 | 8832 |
+| 46 (QPSK) | 1 | 512 | 192 | 32 | 32 | 2 | 7778 | 7712 | 3888 | 3824 |
+| 47 (16QAM) | 1 | 512 | 192 | 32 | 32 | 2 | 15522 | 15456 | 7792 | 7664 |
+| 48 (QPSK) | 32 | 1024 | 384 | 0 | 0 | 0 | 232 | 232 | 122 | 110 |
+| 49 (16QAM) | 32 | 1024 | 384 | 0 | 0 | 0 | 464 | 464 | 244 | 220 |
+| 50 (QPSK) | 32 | 1024 | 384 | 32 | 32 | 2 | 232 | 166 | 90 | 76 |
+
+| slot format # | SF | Midamble Length (chips) | GP (chips) | N UECCH1 (bits) | N UECCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) |
+|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------|
+| 51 (16QAM) | 32 | 1024 | 384 | 32 | 32 | 2 | 430 | 364 | 196 | 168 |
+| 52 (QPSK) | 16 | 1024 | 384 | 0 | 0 | 0 | 464 | 464 | 244 | 220 |
+| 53 (16QAM) | 16 | 1024 | 384 | 0 | 0 | 0 | 928 | 928 | 488 | 440 |
+| 54 (QPSK) | 16 | 1024 | 384 | 32 | 32 | 2 | 430 | 364 | 196 | 168 |
+| 55 (16QAM) | 16 | 1024 | 384 | 32 | 32 | 2 | 826 | 760 | 408 | 352 |
+| 56 (QPSK) | 8 | 1024 | 384 | 0 | 0 | 0 | 928 | 928 | 488 | 440 |
+| 57 (16QAM) | 8 | 1024 | 384 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 |
+| 58 (QPSK) | 8 | 1024 | 384 | 32 | 32 | 2 | 826 | 760 | 408 | 352 |
+| 59 (16QAM) | 8 | 1024 | 384 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 |
+| 60 (QPSK) | 4 | 1024 | 384 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 |
+| 61 (16QAM) | 4 | 1024 | 384 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 |
+| 62 (QPSK) | 4 | 1024 | 384 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 |
+| 63 (16QAM) | 4 | 1024 | 384 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 |
+| 64 (QPSK) | 2 | 1024 | 384 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 |
+| 65 (16QAM) | 2 | 1024 | 384 | 0 | 0 | 0 | 7424 | 7424 | 3904 | 3520 |
+| 66 (QPSK) | 2 | 1024 | 384 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 |
+| 67 (16QAM) | 2 | 1024 | 384 | 32 | 32 | 2 | 6370 | 6304 | 3376 | 2928 |
+| 68 (QPSK) | 1 | 1024 | 384 | 0 | 0 | 0 | 7424 | 7424 | 3904 | 3520 |
+| 69 (16QAM) | 1 | 1024 | 384 | 0 | 0 | 0 | 14848 | 14848 | 7808 | 7040 |
+| 70 (QPSK) | 1 | 1024 | 384 | 32 | 32 | 2 | 6370 | 6304 | 3376 | 2928 |
+| 71 (16QAM) | 1 | 1024 | 384 | 32 | 32 | 2 | 12706 | 12640 | 6768 | 5872 |
+
+### 5B.4.13 E-DCH Random Access Uplink Control Channel (E-RUCCH)
+
+The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. The characteristics of the E-RUCCH physical channel are identical to those of PRACH (see subclause 5B.4.3).
+
+Physical resources available for E-RUCCH are configured by higher layers. E-RUCCH may be mapped to the same physical resources that are assigned for PRACH.
+
+### 5B.4.14 E-DCH Absolute Grant Channel (E-AGCH)
+
+The E-DCH Absolute Grant Channel (E-AGCH) is a downlink physical channel carrying the uplink E-DCH absolute grant control information. Unlike other downlink physical channel types, E-AGCH also carries a TPC field (located immediately after the midamble and spread using SF32) which is used to control the E-PUCH power. Figure 18APC illustrates the burst structure of the E-AGCH.
+
+
+
+Figure 18APC: Burst structure of E-AGCH. The diagram shows a horizontal bar representing the burst structure. From left to right, it consists of 'Data symbols', 'Midamble', a shaded 'TPC field', 'Data symbols', and 'GP'. A double-headed arrow below the 'Midamble' and 'TPC field' section is labeled '1024/512 chips'. A longer double-headed arrow at the bottom, spanning the entire length of the bar, is labeled '5120\*Tc'.
+
+Figure 18APC: Burst structure of E-AGCH
+
+One E-DCH absolute grant for a UE shall be transmitted over one E-AGCH.
+
+#### 5B.4.14.1 E-AGCH Spreading
+
+The E-AGCH shall use spreading factor $SF = 32$ , as described in 5B.3.1.1.
+
+#### 5B.4.14.2 E-AGCH Burst Types
+
+Burst types 1 and 2 as described in subclause 5B.3.2 can be used for E-AGCH. TPC shall be transmitted on E-AGCH whereas TFCI shall not be transmitted.
+
+#### 5B.4.14.3 E-AGCH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the E-AGCH.
+
+#### 5B.4.15.4 E-AGCH timeslot formats
+
+The E-AGCH uses the timeslot formats of Table 20. These augment downlink slot formats 0...19 of table 8AF, see subclause 5B.3.2.6.1.
+
+Table 20: Time slot formats for E-AGCH
+
+| Slot Format # | SF | Midamble length (chips) | $N_{TFCI}$ code word (bits) | $N_{TPC}$ (bits) | Bits/slot | $N_{Data/Slot}$ (bits) | $N_{data/data\ field\ (1)}$ (bits) | $N_{data/data\ field\ (2)}$ (bits) |
+|---------------|----|-------------------------|-----------------------------|------------------|-----------|------------------------|------------------------------------|------------------------------------|
+| 20 | 32 | 1024 | 0 | 2 | 244 | 242 | 122 | 120 |
+| 21 | 32 | 512 | 0 | 2 | 276 | 274 | 138 | 136 |
+
+### 5B.4.15 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)
+
+The E-DCH HARQ Acknowledgement indicator channel (E-HICH) is defined in terms of a SF32 downlink physical channel and a signature sequence. The E-HICH carries the uplink E-DCH hybrid ARQ acknowledgement indicator. Figure 18APD illustrates the structure of the E-HICH.
+
+
+
+The diagram illustrates the E-HICH structure across multiple users and timeslots. At the top, three users are shown: user #H, user #1, and user #0. Each user's data is represented by a sequence of bits: $b_{i,0}, b_{i,1}, \dots, b_{i,119}, \dots, b_{i,120}, b_{i,121}, \dots, b_{i,239}$ . The bits $b_{i,119}$ and $b_{i,120}$ are highlighted with boxes. Above these boxes, the label "spare bits" points to them. Between the bits $b_{i,119}$ and $b_{i,120}$ is a "midamble" section. To the right of the bits is a "GP" (Guard Period) section. A bracket on the right side of the user data indicates a total length of $1 \times SF32$ . Below the user data, a horizontal axis shows timeslots: Slot #0, Slot #1, Slot #2, ..., Slot #n, ..., Slot #14. A double-headed arrow below this axis is labeled "1 radio frame, 10ms".
+
+Diagram illustrating the E-HICH structure across multiple users and timeslots.
+
+Figure 18APD – E-HICH Structure
+
+A single channelisation code may carry one or multiple signature sequences. Each signature sequence conveys a HARQ acknowledgement indicator. A maximum of one indicator may be transmitted to a UE. Each acknowledgement indicator is coded to form a signature sequence of 240 bits ( $b_0, b_1, \dots, b_{239}$ ) as defined in [7] and is transmitted within a single E-HICH timeslot. The E-HICH also contains $U$ spare bit locations, where $U=4$ for burst type 1 and $U=36$ for burst type 2. The spare bit values are not defined.
+
+#### 5B.4.15.1 E-HICH Spreading
+
+Signature sequences (including spare bits inserted) that share the same channelisation code are combined and spread using spreading factor $SF=32$ as described in [8].
+
+#### 5B.4.15.2 E-HICH Burst Types
+
+Burst types 1 and 2 as described in subclause 5B.3.2 can be used for E-HICH. Neither TFCI nor TPC shall be transmitted on the E-HICH.
+
+#### 5B.4.15.3 E-HICH Training Sequences
+
+The training sequences as described in subclause 5B.3.3 are used for the E-HICH.
+
+## 5B.5 Transmit Diversity for DL Physical Channels
+
+Support for transmit diversity is the same as that for the 3.84 Mcps TDD option cf. [5.4 Transmit Diversity]..
+
+## 5B.6 Beacon characteristics of physical channels
+
+For the purpose of measurements, common physical channels that are allocated to particular locations (time slot, code) shall have particular physical characteristics, called beacon characteristics. Physical channels with beacon characteristics are called beacon channels. The locations of the beacon channels are called beacon locations. The ensemble of beacon channels shall provide the beacon function, i.e. a reference power level at the beacon locations, regularly existing in each radio frame. Thus, beacon channels must be present in each radio frame, the only exception is when idle periods are used to support time difference measurements for location services [9]. Then it may be possible that the beacon channels occur in the same frame and time slot as the idle periods. In this case, the beacon channels will not be transmitted in that particular frame and time slot.
+
+### 5B.6.1 Location of beacon channels
+
+The beacon locations are determined by the SCH and depend on the SCH allocation case, see subclause 5B.4.4:
+
+- Case 1) The beacon function shall be provided by the physical channels that are allocated to channelisation code and to $TS\#k$ , $k=0, \dots, 14$ .
+- Case 2) The beacon function shall be provided by the physical channels that are allocated to channelisation code and to $TS\#k$ and $TS\#k+8$ , $k=0, \dots, 6$ .
+
+Note that by this definition the P-CCPCH always has beacon characteristics.
+
+### 5B.6.2 Physical characteristics of beacon channels
+
+The beacon channels shall have the following physical characteristics. They:
+
+- are transmitted with reference power;
+- are transmitted without beamforming;
+- use burst type 1 or burst type 4 when MBSFN is applied to beacon channels;
+- use midamble $m^{(1)}$ and $m^{(2)}$ exclusively in this time slot; and
+- midambles $m^{(9)}$ and $m^{(10)}$ are always left unused in this time slot, if 16 midambles are allowed in that cell.
+
+Note that in the time slot where the P-CCPCH is transmitted only the midambles $m^{(1)}$ to $m^{(8)}$ shall be used, see 5B.7.1. Thus, midambles $m^{(9)}$ and $m^{(10)}$ are always left unused in this time slot.
+
+Note that when MBSFN is applied to beacon channels there is a single midamble and hence midamble $m^{(1)}$ is exclusively used in the timeslot.
+
+The reference power corresponds to the sum of the power allocated to both midambles $m^{(1)}$ and $m^{(2)}$ . Two possibilities exist:
+
+- If SCTD antenna diversity is not applied to beacon channels all the reference power of any beacon channel is allocated to $m^{(1)}$ .
+- If SCTD antenna diversity is applied to beacon channels, for any beacon channel midambles $m^{(1)}$ and $m^{(2)}$ are each allocated half of the reference power.
+
+## 5B.7 Midamble Allocation for Physical Channels
+
+Midamble allocation for physical channels is identical to 3.84Mcps TDD [section 5.6]. The association between midambles and channelisation codes is given in Annex AB.3.
+
+## 5B.8 Midamble Transmit Power
+
+There shall be no offset between the sum of the powers allocated to all midambles in a timeslot and the sum of the powers allocated to the data symbol fields. The transmit power within a timeslot is hence constant.
+
+The midamble transmit power of beacon channels is equal to the reference power. If SCTD is used for beacon channels, the reference power is equally divided between the midambles $m^{(1)}$ and $m^{(2)}$ .
+
+The midamble transmit power of all other physical channels depends on the midamble allocation scheme used. The following rules apply
+
+- In case of Default Midamble Allocation, every midamble is transmitted with the same power as the associated codes.
+- In case of Common Midamble Allocation in the downlink, the transmit power of this common midamble is such that there is no power offset between the data parts and the midamble part of the overall transmit signal within one time slot.
+- In case of UE Specific Midamble Allocation, the transmit power of the UE specific midamble is such that there is no power offset between the data parts and the midamble part of every user within one time slot.
+
+The following figure 18AQ depicts the midamble powers for the different channel types and midamble allocation schemes.
+
+Note 1: In figure 18AQ, the codes $c(1)$ to $c(32)$ represent the set of usable codes and not the set of used codes.
+
+Note 2: The common midamble allocation and the midamble allocation by higher layers are not applicable in those beacon time slots, in which the P-CCPCH is located, see section 5B.7.
+
+
+
+**No Beacon Time Slots**
+
+**Beacon Time Slots when SCTD is not applied**
+
+**Beacon Time Slots when SCTD is applied**
+
+Common Midamble Allocation
+
+P ↑
+
+
+| | | |
+|-------|---------------|------------|
+| c(1) | Midamble m(x) | Code c(1) |
+| ... | | ... |
+| c(32) | | Code c(32) |
+
+x depends on the number of transmitted codes in that time slot
+
+P ↑
+
+
+| | | |
+|-----------------|---------------|-----------------|
+| Beacon Channels | Midamble m(1) | Beacon Channels |
+| Code c(n) | Midamble m(x) | Code c(n) |
+| ... | | ... |
+| Code c(32) | | Code c(32) |
+
+P ↑
+
+
+| | | |
+|-----------------|---------------|-----------------|
+| Beacon Channels | Midamble m(1) | Beacon Channels |
+| | Midamble m(2) | |
+| Code c(n) | Midamble m(x) | Code c(n) |
+| ... | | ... |
+| Code c(32) | | Code c(32) |
+
+Default Midamble Allocation
+
+P ↑
+
+
+| | | |
+|-----------|--------------------------------|----------------|
+| c(1) | Midamble m(1) | Code c(1) |
+| ... | | ... |
+| c(M) | | Code c(M) |
+| c(M+1) | Midamble m(2) | c(M+1) |
+| ... | | ... |
+| c(2M) | | c(2M) |
+| ... | ... | ... |
+| c(32-M+1) | Midamble m(K CELL ) | Code c(32-M+1) |
+| ... | | ... |
+| c(32) | | Code c(32) |
+
+P ↑
+
+
+| | | |
+|-----------------|--------------------------------|-----------------|
+| Beacon Channels | Midamble m(1) | Beacon Channels |
+| c(2M+1) | Midamble m(3) | c(2M+1) |
+| ... | | ... |
+| c(3M) | | c(3M) |
+| ... | ... | ... |
+| Code c(32-M+1) | Midamble m(K CELL ) | Code c(32-M+1) |
+| ... | | ... |
+| Code c(32) | | Code c(32) |
+
+P ↑
+
+
+| | | |
+|-----------------|--------------------------------|-----------------|
+| Beacon Channels | Midamble m(1) | Beacon Channels |
+| | Midamble m(2) | |
+| c(2M+1) | Midamble m(3) | c(2M+1) |
+| ... | | ... |
+| c(3M) | | c(3M) |
+| ... | ... | ... |
+| Code c(32-M+1) | Midamble m(K CELL ) | Code c(32-M+1) |
+| ... | | ... |
+| Code c(32) | | Code c(32) |
+
+M: Number of codes per Midamble (M=32/KCELL); in the P-CCPCH Time Slot M = 2, independent of KCELL
+KCELL: Number of usable Midamble Shifts in this Cell
+
+Midamble Allocation by Higher Layers
+
+P ↑
+
+
+| | | |
+|-------------------|--------------------------------|-------------------|
+| Codes of CCTrCH 1 | Midamble m(1) | Codes of CCTrCH 1 |
+| Codes of CCTrCH 2 | Midamble m(2) | Codes of CCTrCH 2 |
+| ... | ... | ... |
+| Codes of CCTrCH U | Midamble m(K CELL ) | Codes of CCTrCH U |
+
+P ↑
+
+
+| | | |
+|-------------------|--------------------------------|-------------------|
+| Beacon Channels | Midamble m(1) | Beacon Channels |
+| Codes of CCTrCH 1 | Midamble m(3) | Codes of CCTrCH 1 |
+| ... | ... | ... |
+| Codes of CCTrCH U | Midamble m(K CELL ) | Codes of CCTrCH U |
+
+P ↑
+
+
+| | | |
+|-------------------|--------------------------------|-------------------|
+| Beacon Channels | Midamble m(1) | Beacon Channels |
+| | Midamble m(2) | |
+| Codes of CCTrCH 1 | Midamble m(3) | Codes of CCTrCH 1 |
+| ... | ... | ... |
+| Codes of CCTrCH U | Midamble m(K CELL ) | Codes of CCTrCH U |
+
+U: Number of CCTrCHs in this Time Slot, multiple CCTrCHs of one user may share one midamble
+KCELL: Number of usable Midamble Shifts in this Cell
+
+**Figure 18AQ: Midamble powers for the different midamble allocation schemes**
+
+# 6 Mapping of transport channels to physical channels for the 3.84 Mcps option
+
+This clause describes the way in which transport channels are mapped onto physical resources, see figure 19. Sub-clauses 6.1 and 6.2 do not apply to 3.84 Mcps MBSFN IMB. Mappings between transport channels and physical resources for 3.84 Mcps MBSFN IMB are described in sub-clause 6.3.
+
+| Transport Channels | Physical Channels |
+|--------------------|--------------------------------------------------------|
+| 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) |
+| | Physical Node B Synchronisation Channel (PNBSCH) |
+| 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 19: Transport channel to physical channel mapping
+
+## 6.1 Dedicated Transport Channels
+
+### 6.1.1 The Dedicated Channel (DCH)
+
+A dedicated transport channel is mapped onto one or more physical channels. An interleaving period is associated with each allocation. The frame is subdivided into slots that are available for uplink and downlink information transfer. The mapping of transport blocks on physical channels is described in TS 25.222 ("multiplexing and channel coding").
+
+
+
+Figure 20: Mapping of Transport Blocks onto the physical bearer. The diagram shows four radio frames (Frame 1, Frame 2, Frame 3, Frame 4). Each frame is represented by a grid of 10 columns and 2 rows. In each frame, a 'Transport Block(s)' box points to a 'Coded bits' box, which in turn points to a specific cell in the grid. In Frame 1, the arrow points to the 3rd cell. In Frame 2, it points to the 4th cell. In Frame 3, it points to the 3rd cell. In Frame 4, it points to the 4th cell.
+
+**Figure 20: Mapping of Transport Blocks onto the physical bearer**
+
+For NRT packet data services, shared channels (USCH and DSCH) can be used to allow efficient allocations for a short period of time.
+
+### 6.1.2 The Enhanced Uplink Dedicated Channel (E-DCH)
+
+The enhanced uplink dedicated channel is mapped on one or several E-PUCH, see subclause 5.3.13.
+
+#### 6.1.2.1 E-DCH/E-AGCH Association and Timing
+
+The E-DCH is always associated with a number of E-DCH Absolute Grant Channels (E-AGCH) and one hybrid ARQ indicator channel (E-HICH). A grant of E-DCH transmission resources may be transmitted to the UE on any one of the associated E-AGCH. All relevant Layer 1 control information related to an E-DCH TTI is transmitted in the associated E-AGCH and E-HICH.
+
+The E-DCH related time slot information that is carried on the E-AGCH refers to the next valid E-PUCH allocation, which is given by the following limitation: There shall be an offset of $n_{E-AGCH} \geq 6$ time slots between the E-AGCH carrying the E-DCH related information and the first indicated E-PUCH (in time) for a given UE. The E-DCH related time slot information shall not refer to two subsequent radio frames but shall always refer to either the same or the following radio frame, as illustrated in figure 20a. Note that the figure only shows the E-AGCH that carries the E-DCH related information for the given UE.
+
+
+
+Figure 20a: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+1. Each frame has 14 slots. In Radio Frame #n, the 4th slot is labeled 'E-AGCH' and the 10th slot is labeled '1st E-PUCH'. A horizontal arrow labeled n\_{E-AGCH} starts from the beginning of the E-AGCH slot and ends at the beginning of the 1st E-PUCH slot. In Radio Frame #n+1, the 4th slot is also labeled 'E-AGCH' and the 10th slot is labeled '1st E-PUCH'. A horizontal arrow labeled n\_{E-AGCH} starts from the beginning of the E-AGCH slot and ends at the beginning of the 1st E-PUCH slot. A vertical dashed line separates the two frames between the 7th and 8th slots.
+
+**Figure 20a: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE**
+
+#### 6.1.2.2 E-DCH/E-HICH Association and Timing
+
+All E-DCH operations within the cell are associated with the same E-HICH channelisation code. A single E-HICH channelisation code exists in the cell per E-DCH TTI (10ms). For a given UE, a HARQ acknowledgement indicator is synchronously linked with the E-DCH TTI transmission to which it relates. There is thus a one-to-one association between an E-DCH TTI transmission and its respective HARQ acknowledgment indicator on the associated E-HICH.
+
+The associated E-HICH shall reside on the first instance of the E-HICH channelisation code to occur after $n_{E-HICH}$ timeslots have elapsed since the start of the last E-PUCH of the corresponding E-DCH TTI (see examples of figure 20b). The value of $n_{E-HICH}$ is configurable by higher layers within the range 4 to 44 timeslots.
+
+
+
+Figure 20b: Timing for E-DCH and E-HICH for a given UE. The diagram shows two horizontal timelines representing radio frames. The top timeline is labeled 'Radio Frame #n' and contains 15 slots. The 4th slot is labeled 'Last E-PUCH' and the 8th slot is labeled 'E-HICH'. A double-headed arrow below the frame, spanning from the start to the beginning of the E-HICH slot, is labeled n\_E-HICH. The bottom timeline shows a transition between 'Radio Frame #n' and 'Radio Frame #n+M'. 'Radio Frame #n' contains a 'last E-PUCH' slot followed by a dashed area. 'Radio Frame #n+M' contains an 'E-HICH' slot. A double-headed arrow below the frames, spanning from the start of the 'last E-PUCH' slot to the beginning of the 'E-HICH' slot, is labeled n\_E-HICH.
+
+Figure 20b: Timing for E-DCH and E-HICH for a given UE
+
+The HARQ acknowledgement indicator associated with an E-DCH transmission is transmitted using one of 240 signature sequences carried by the associated E-HICH channelisation code. Which signature sequence $r = 0, 1, 2, \dots, 239$ is used is calculated for each E-DCH resource allocation using the information signalled on the associated E-AGCH as follows:
+
+- where:
+
+- $t_0$ is the bit position ( $1 \dots n_{\text{TRRI}}$ ) of the first active timeslot in the timeslot resource related information bitmap (see [7]) on E-AGCH and where bit position 1 corresponds to the lowest-numbered timeslot
+- $q_0$ is the allocated channelisation code index ( $1, 2, 3, \dots, Q_0$ )
+- $Q_0$ is the spreading factor of the allocated uplink channelisation code
+
+## 6.2 Common Transport Channels
+
+### 6.2.1 The Broadcast Channel (BCH)
+
+The BCH is mapped onto the P-CCPCH. The secondary SCH codes indicate in which timeslot a mobile can find the P-CCPCH containing BCH.
+
+### 6.2.2 The Paging Channel (PCH)
+
+The PCH is mapped onto one or several S-CCPCHs so that capacity can be matched to requirements. The location of the PCH is indicated on the BCH. It is always transmitted at a reference power level.
+
+To allow an efficient DRX, the PCH is divided into PCH blocks, each of which comprising $N_{\text{PCH}}$ paging sub-channels. $N_{\text{PCH}}$ is configured by higher layers. Each paging sub-channel is mapped onto 2 consecutive PCH frames within one PCH block. Layer 3 information to a particular UE is transmitted only in the paging sub-channel, that is assigned to the UE by higher layers, see [15]. The assignment of UEs to paging sub-channels is independent of the assignment of UEs to page indicators.
+
+#### 6.2.2.1 PCH/PICH Association
+
+As depicted in figure 21, a paging block consists of one PICH block and one PCH block. If a paging indicator in a certain PICH block is set to '1' it is an indication that UEs associated with this paging indicator shall read their
+
+corresponding paging sub-channel within the same paging block. The value $N_{GAP} > 0$ of frames between the end of the PICH block and the beginning of the PCH block is configured by higher layers.
+
+
+
+The diagram illustrates the structure of a Paging Block. At the top, a long double-headed arrow labeled 'Paging Block' spans the entire width. Below this, the block is divided into two main sections: 'PICH Block' on the left and 'PCH Block' on the right, each indicated by a double-headed arrow. The PICH Block contains a series of slots, with the first four shown and an ellipsis indicating more. The PCH Block is divided into sub-channels labeled 'Sub-Channel #0', 'Sub-Channel #1', and 'Sub-Channel #NPCH-1', with an ellipsis between #1 and #NPCH-1. Below the sub-channel labels, a row of slots is shown for the PCH. At the bottom, three double-headed arrows indicate time durations: $N_{PICH}$ for the PICH block, $N_{GAP}$ for the gap between blocks, and $2 \cdot N_{PCH}$ for the PCH block.
+
+Diagram of a Paging Block structure showing PICH and PCH blocks and their sub-channels.
+
+Figure 21: Paging Sub-Channels and Association of PICH and PCH blocks
+
+### 6.2.3 The Forward Channel (FACH)
+
+The FACH is mapped onto one or several S-CCPCHs. The location of the FACH is indicated on the BCH and both, capacity and location can be changed, if required. FACH may or may not be power controlled.
+
+### 6.2.4 The Random Access Channel (RACH)
+
+The RACH has intraslot interleaving only and is mapped onto PRACH. The same slot may be used for PRACH by more than one cell. Multiple transmissions using different spreading codes may be received in parallel. More than one slot per frame may be administered for the PRACH. The location of slots allocated to PRACH is broadcast on the BCH. The PRACH uses open loop power control. The details of the employed open loop power control algorithm may be different from the corresponding algorithm on other channels.
+
+### 6.2.5 The Uplink Shared Channel (USCH)
+
+The uplink shared channel is mapped on one or several PUSCH, see subclause 5.3.5.
+
+### 6.2.6 The Downlink Shared Channel (DSCH)
+
+The downlink shared channel is mapped on one or several PDSCH, see subclause 5.3.6.
+
+### 6.2.7 The High Speed Downlink Shared Channel (HS-DSCH)
+
+The high speed downlink shared channel is mapped on one or several HS-PDSCH, see subclause 5.3.9.
+
+#### 6.2.7.1 HS-DSCH/HS-SCCH Association and Timing
+
+The HS-DSCH is always associated with a number of High Speed Shared Control Channels (HS-SCCH). The number of HS-SCCHs that are associated with an HS-DSCH for one UE can range from a minimum of one HS-SCCH ( $M=1$ ) to a maximum of four HS-SCCH ( $M=4$ ). All relevant Layer 1 control information is transmitted in the associated HS-SCCH i.e. the HS-PDSCH does not carry any Layer 1 control information.
+
+The HS-DSCH related time slot information that is carried on the HS-SCCH refers to the next valid HS-PDSCH allocation, which is given by the following limitation: There shall be an offset of $n_{HS-SCCH} \geq 4$ time slots between the HS-SCCH carrying the HS-DSCH related information and the first indicated HS-PDSCH (in time) for a given UE. The HS-DSCH related time slot information shall not refer to two subsequent radio frames but shall always refer to either the same or the following radio frame, as illustrated in figure 21A. Note that the figure only shows the HS-SCCH that carries the HS-DSCH related information for the given UE.
+
+
+
+Figure 21A: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE. The diagram shows two cases. The top case shows a single radio frame #n containing an HS-SCCH and a 1st HS-PDSCH, with a timing offset n\_HS-SCCH indicated. The bottom case shows the HS-SCCH in radio frame #n and the 1st HS-PDSCH in radio frame #n+1, also with a timing offset n\_HS-SCCH indicated.
+
+**Figure 21A: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE**
+
+#### 6.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing
+
+The HS-SCCH is always associated with one HS-SICH. The association between the HS-SCCH in DL and HS-SICH in UL shall be pre-defined by higher layers and is common for all UEs.
+
+The UE shall transmit the HS-DSCH related ACK / NACK on the next available associated HS-SICH with the following limitation: There shall be an offset of $n_{\text{HS-SICH}} \geq 17$ time slots between the last allocated HS-PDSCH (in time) and the HS-SICH for the given UE. Hence, the HS-SICH transmission shall be made in the next or next but one radio frame, following the HS-DSCH transmission, as illustrated in figure 21B. Note that the figure only shows the HS-SICH that carries the HS-DSCH related ACK / NACK for the given UE.
+
+
+
+Figure 21B: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows two cases. The top case shows the last HS-PDSCH in radio frame #n and the HS-SICH in radio frame #n+2, with a timing offset n\_HS-SICH indicated. The bottom case shows the last HS-PDSCH in radio frame #n and the HS-SICH in radio frame #n+1, also with a timing offset n\_HS-SICH indicated.
+
+**Figure 21B: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE**
+
+## 6.3 Mapping of TrCHs for the 3.84 Mcps MBSFN IMB option
+
+The following mappings are supported:
+
+- BCH mapped to P-CCPCH.
+- FACH mapped to S-CCPCH
+
+- MICH (no transport channel is mapped to MICH)
+
+# 7 Mapping of transport channels to physical channels for the 1.28 Mcps option
+
+This clause describes the way in which the transport channels are mapped onto physical resources, see figure 22.
+
+| Transport channels | Physical channels |
+|--------------------|--------------------------------------------------------|
+| DCH | Dedicated Physical Channel (DPCH) |
+| BCH | Primary Common Control Physical Channels (P-CCPCH) |
+| PCH | Secondary Common Control Physical Channels (S-CCPCH) |
+| FACH | Secondary Common Control Physical Channels (S-CCPCH) |
+| | PICH |
+| | MICH |
+| | PLCCH |
+| RACH | Physical Random Access Channel (PRACH) |
+| USCH | Physical Uplink Shared Channel (PUSCH) |
+| DSCH | Physical Downlink Shared Channel (PDSCH) |
+| | Down link Pilot Channel (DwPCH) |
+| | Up link Pilot Channel (UpPCH) |
+| | FPACH |
+| 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 Uplink Control Physical Channel (E-UCCH) |
+| | 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 22: Transport channel to physical channel mapping for 1.28Mcps TDD
+
+## 7.1 Dedicated Transport Channels
+
+### 7.1.1 The Dedicated Channel (DCH)
+
+The mapping of transport blocks to physical bearers is in principle the same as in 3.84 Mcps TDD but due to the subframe structure the coded bits are mapped onto each of the subframes within the given TTI.
+
+
+
+Diagram illustrating the mapping of Transport Blocks onto the physical bearer. It shows two radio frames, Radio frame n and Radio frame n+1. Each frame contains subframes 2n, 2n+1, 2(n+1), and 2(n+1)+1. Arrows indicate the flow from Transport Block(s) to Coded Bits, and then to the subframes. Specifically, Transport Block(s) are mapped to Coded Bits, which are then distributed across the subframes of Radio frame n and Radio frame n+1. The subframes are labeled as Sub-frame 2n, Sub-frame 2n+1, Sub-frame 2(n+1), and Sub-frame 2(n+1)+1.
+
+Figure 23 : Mapping of Transport Blocks onto the physical bearer ( TTI= 20ms )
+
+### 7.1.2 The Enhanced Uplink Dedicated Channel (E-DCH)
+
+The enhanced uplink dedicated channel is mapped on one or several E-PUCH, see subclause 5A.3.14.
+
+For multi-carrier E-DCH transmission, the E-DCH on one carrier is always associated with a number of E-AGCH and up to four E-HICHs on the same carrier. The E-DCH, E-AGCH and E-HICH on the same carrier obey the following timing relationships.
+
+#### 7.1.2.1 E-DCH/E-AGCH Association and Timing
+
+The E-DCH is always associated with a number of E-DCH Absolute Grant Channels (E-AGCH) and up to four hybrid ARQ Indicator Channel (E-HICH). A grant of E-DCH transmission resources may be transmitted to the UE on any one of the associated E-AGCH. All relevant Layer 1 control information related to an E-DCH TTI is transmitted in the associated E-AGCH and E-HICH.
+
+The E-DCH related timeslot information that is carried on the E-AGCH refers to the next valid E-PUCH allocation, which is given by the following limitation: There shall be an offset of $n_{E-AGCH} \geq 7$ time slots between the E-AGCH carrying the E-DCH related information and the first indicated E-PUCH (in time) for a given UE. DwPTS and UpPTS shall not be taken into account in this limitation as illustrated in figure 23A. Note that the figure only shows the E-AGCH that carries the E-DCH related information for the given UE and that DwPTS and UpPTS are not considered in this figure.
+
+
+
+Figure 23A: Timing for E-AGCH and E-PUCH for different radio frame configurations for a given UE. The diagram shows two horizontal bars representing radio frames. The top bar is solid black. The bottom bar is divided into 10 equal segments by vertical lines. A single vertical line in the bottom bar is highlighted, representing the E-AGCH. The E-PUCH is represented by a segment in the bottom bar that starts after the E-AGCH line, illustrating the timing offset.
+
+**Figure 23A: Timing for E-AGCH and E-PUCH for different radio frame configurations for a given UE**
+
+When E-AGCH is allocated in TS0, the timing between E-AGCH and the associated E-PUCH is defined as: E-AGCH is sent in the n-th sub-frame while the E-PUCH is sent in the (n+2)-th sub-frame.
+
+For the semi-persistent E-DCH resources, the timing between E-AGCH and the first E-PUCH can also use the same limitation: There shall be an offset of $n_{E-AGCH} \geq 7$ time slots between the E-AGCH carrying the semi-persistent E-DCH related information and the first indicated semi-persistent E-PUCH (in time) for a given UE. Once the semi-persistent resources are assigned to UE, UE can use these resources continuously until the semi-persistent resources have been released or reconfigured by Node B or RNC.
+
+#### 7.1.2.2 E-DCH/E-HICH Association and Timing
+
+For a given UE, a HARQ acknowledgement indicator (E-HICH) is synchronously linked with the E-DCH TTI transmission to which it relates.
+
+The associated E-HICH shall reside on the first E-HICH instance of the E-HICH channelisation code to occur after $n_{E-HICH}$ timeslots have elapsed since the start of the last E-PUCH of the corresponding E-DCH TTI (see examples of figure 23B). DwPTS and UpPTS are not considered in the figure. The value of $n_{E-HICH}$ is configurable by higher layers within the range 4 to 15 timeslots. DwPTS and UpPTS shall not be taken into account in this limitation.
+
+
+
+Figure 23B: Timing for E-DCH and E-HICH for a given UE. The diagram shows two horizontal timelines. The top timeline consists of seven adjacent rectangular blocks representing timeslots. Above these blocks is a long double-headed arrow spanning all seven. Below the blocks is a shorter double-headed arrow starting from the second block and ending at the fourth block. The bottom timeline also consists of seven adjacent rectangular blocks. Above these blocks is a double-headed arrow starting from the third block and ending at the fifth block. Below the blocks is a long double-headed arrow spanning all seven blocks.
+
+Figure 23B: Timing for E-DCH and E-HICH for a given UE
+
+## 7.2 Common Transport Channels
+
+### 7.2.1 The Broadcast Channel (BCH)
+
+There are two P-CCPCHs, P-CCPCH 1 and P-CCPCH 2 which are mapped onto timeslot#0 using the channelisation codes $C_{Q=16}^{(k=1)}$ and $C_{Q=16}^{(k=2)}$ with spreading factor 16. The BCH is mapped onto the P-CCPCH1+P-CCPCH2.
+
+The position of the P-CCPCHs is indicated by the relative phases of the bursts in the DwPTS with respect to the P-CCPCHs midamble sequences, see [8]. One special combination of the phase differences of the burst in the DwPTS with respect to the P-CCPCH midamble indicates the position of the P-CCPCH in the multi-frame and the start position of the interleaving period.
+
+### 7.2.2 The Paging Channel (PCH)
+
+If the PICH is associated with an S-CCPCH to which a PCH transport channel is mapped, the mapping of Paging Channels onto S-CCPCHs and the association between PCHs and Paging Indicator Channels is the same as in the 3.84 Mcps TDD option, cf. 6.2.2 'The paging Channel' and 6.2.2.1 'PCH/PICH Association' respectively.
+
+### 7.2.3 The Forward Channel (FACH)
+
+The FACH is mapped onto one or several S-CCPCHs. The location of the FACH is indicated on the BCH and both, capacity and location can be changed, if required. FACH may or may not be power controlled.
+
+### 7.2.4 The Random Access Channel (RACH)
+
+The RACH is mapped onto PRACH. More than one slot per frame may be administered for the PRACH. The location of slots allocated to PRACH is broadcast on the BCH. The uplink sync codes (SYNC-UL sequences) used by the UEs for UL synchronisation have a well known association with the P-RACHs, as broadcast on the BCH. On the PRACH, both power control and uplink synchronisation control are used.
+
+### 7.2.5 The Uplink Shared Channel (USCH)
+
+The uplink shared channel is mapped onto one or several PUSCH, see subclause 5A.3.6 'Physical Uplink Shared Channel (PUSCH)'
+
+### 7.2.6 The Downlink Shared Channel (DSCH)
+
+The downlink shared channel is mapped onto one or several PDSCH, see subclause 5A.3.7 'Physical Downlink Shared Channel (PDSCH)'
+
+### 7.2.7 The High Speed Downlink Shared Channel (HS-DSCH)
+
+The high speed downlink shared channel is mapped on one or several HS-PDSCH, see subclause 5A.3.9.
+
+#### 7.2.7.1 HS-DSCH/HS-SCCH Association and Timing
+
+The HS-DSCH can be associated with a number of High Speed Shared Control Channels (HS-SCCH). In a multi-frequency HS-DSCH cell, HS-DSCH may be mapped on HS-PDSCHs on one or more carrier in CELL\_DCH state and on only one carrier in CELL\_FACH, CELL\_PCH and URA\_PCH state for UE supporting multi-carrier HS-DSCH reception configured by higher layers. HS-DSCH transmission on each carrier is associated with a HS-SCCH subset and the number of HS-SCCHs in one HS-SCCH subset can range from a minimum of one HS-SCCH ( $M=1$ ) to a maximum of four HS-SCCH ( $M=4$ ). All the HS-SCCH subsets for one UE constitute a HS-SCCH set. For UE not supporting multi-carrier HS-DSCH reception, only one HS-SCCH subset is allocated by higher layers. All relevant Layer 1 control information is transmitted in the associated HS-SCCH i.e. the HS-PDSCH does not carry any Layer 1 control information.
+
+The HS-DSCH related time slot information that is carried on the HS-SCCH refers to the next valid HS-PDSCH allocation, which is given by the following limitation: The indicated HS-PDSCH shall be on the sub-frame next to the HS-SCCH carrying the HS-DSCH related information. The HS-DSCH related time slot information shall not refer to two subsequent sub-frames but shall always refer to the following sub-frame, as illustrated in figure 24. Note that the figure only shows the HS-SCCH that carries the HS-DSCH related information for the given UE and that DwPTS and UpPTS are not considered in this figure. In case of multi-carrier HS-DSCH reception, the timing for HS-DSCH transmission on each carrier and its associated HS-SCCH applies the same rule.
+
+When the indicated HS-PDSCH includes TS0, the timing between HS-SCCH and HS-PDSCH including TS0 is defined as: HS-SCCH is sent in the n-th sub-frame while HS-PDSCH is sent in the (n+1)-th sub-frame, where the included TS0 is sent in TS0 of the (n+2)-th sub-frame.
+
+For the semi-persistent HS-DSCH resources, the timing between HS-SCCH and the first HS-PDSCH applies the rule that, if the HS-SCCH is transmitted in subframe N, then the first HS-PDSCH is transmitted in subframe N+2, as illustrated in figure 24A. Once the semi-persistent resources are assigned to UE, UE can use these resources continuously until the semi-persistent resources have been released or reconfigured by Node B or RNC.
+
+
+
+Figure 24: Timing diagram for HS-SCCH and HS-DSCH. It shows two sub-frames, Sub-Frame #n and Sub-Frame #n+1. In Sub-Frame #n, the third slot is labeled HS-SCCH. In Sub-Frame #n+1, the sixth slot is labeled 1st HS-PDSCH. A double-headed arrow above the sub-frames indicates the timing relationship between them.
+
+**Figure 24: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE**
+
+
+
+Figure 24A: Timing diagram for HS-SCCH and first semi-persistent HS-PDSCH. It shows a sequence of sub-frames. A vertical dashed line marks the start of a sub-frame. To the left of this line, the third slot is labeled HS-SCCH. To the right of the line, the sixth slot is labeled 1st HS-PDSCH. A double-headed arrow above the sub-frames indicates the timing relationship between them.
+
+**Figure 24A: Timing for HS-SCCH and first semi-persistent HS-DSCH for different radio frame configurations for a given UE**
+
+#### 7.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing
+
+The HS-SCCH is always associated with one HS-SICH, carrying the ACK/NACK and Channel Quality information (CQI). The association between the HS-SCCH in DL and HS-SICH in UL shall be pre-defined by higher layers and is common for all UEs. For the HS-DSCH semi-persistent scheduling operation, the associated HS-SICH to the HS-DSCH is conveyed by HS-SICH Indicator on HS-SCCH.
+
+The UE in CELL\_DCH state and in CELL\_FACH state with a dedicated UE identity shall transmit the HS-DSCH related ACK / NACK on the next available associated HS-SICH with the following limitation: There shall be an offset of $n_{\text{HS-SICH}} \geq 9$ time slots between the last allocated HS-PDSCH (in time) and the HS-SICH for the given UE. DwPTS and UpPTS shall not be taken into account in this limitation. Hence, the HS-SICH transmission shall always be made in the next but one sub-frame, following the HS-DSCH transmission, as illustrated in figure 25. Note that the figure only shows the HS-SICH that carries the HS-DSCH related ACK / NACK for the given UE and that DwPTS and UpPTS are not considered in this figure. In case of multi-carrier HS-DSCH reception, the timing for HS-DSCH transmission on each carrier and its related HS-SICH applies the same rule. For the HS-SCCH order which is an uplink synchronization establishment order for UEs in CELL\_FACH and CELL\_PCH state, the UE shall not transmit associated HS-SICH.
+
+
+
+Figure 25: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows three sub-frames: Sub-Frame #n, Sub-Frame #n+1, and Sub-Frame #n+2. In Sub-Frame #n, the 'last HS-PDSCH' is transmitted. In Sub-Frame #n+1, there is a gap indicated by '.....'. In Sub-Frame #n+2, the 'HS-SICH' is transmitted. A horizontal arrow below the sub-frames indicates the offset n\_HS-SICH between the end of the last HS-PDSCH in Sub-Frame #n and the start of the HS-SICH in Sub-Frame #n+2.
+
+**Figure 25: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE**
+
+When the indicated HS-PDSCH includes TS0, the timing between HS-PDSCH including TS0 and HS-SICH is defined as: HS-PDSCH is sent in the n-th sub-frame while HS-SICH is sent in the (n+2)-th sub-frame, where the included TS0 is sent in TS0 of the (n+1)-th sub-frame and there shall be an offset of $n_{\text{HS-SICH}} \geq 9$ time slots between the last allocated HS-PDSCH (in time) and the HS-SICH.
+
+There shall be an associated HS-SICH for the HS-SCCH command for allocation or release of the semi-persistent HS-PDSCH resources and HS-SCCH command for activation or deactivation of DRX. There shall also be an associated HS-SICH for HS-SCCH type 1 or HS-SCCH type 4 or HS-SCCH type 8 with transport block size information set to all zeros. There is no associated HS-PDSCH in these cases. The timing between the HS-SCCH and the HS-SICH for the given UE as illustrated in figure 25A. The UE shall transmit the HS-SCCH related ACK on the next available associated HS-SICH with the following limitation: There shall be an offset of $n'_{\text{HS-SICH}} \geq 14$ time slots between the HS-SCCH (in time) and the HS-SICH for the given UE. DwPTS and UpPTS shall not be taken into account in this limitation.
+
+
+
+Figure 25A: Timing for HS-SCCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows a horizontal arrow pointing to the right, representing the timing offset n'\_HS-SICH between the HS-SCCH and the HS-SICH.
+
+**Figure 25A: Timing for HS-SCCH and HS-SICH for different radio frame configurations for a given UE**
+
+When HS-SCCH is allocated in TS0, the timing between HS-SCCH for the HS-SCCH command and the associated HS-SICH is defined as: HS-SCCH is sent in the n-th sub-frame while HS-SICH is sent in the (n+3)-th sub-frame.
+
+#### 7.2.7.3 PICH/HS-SCCH/HS-DSCH Association and Timing
+
+When the UE in CELL\_PCH state with a dedicated UE identity detects the PICH identifying DCCH/DTCH/BCCH transmission, the UE shall receive the corresponding HS-SCCH subframes. The association and timing between PICH and HS-SCCH is depicted in figure 25A. If a paging indicator in a certain PICH block is set to '1' it is an indication that UEs associated with this paging indicator shall read their corresponding HS-SCCH in the M frames where M is Reception window size configured by higher layers. The value $N_{\text{GAP}} > 0$ of frames between the end of the PICH block and the beginning of the HS-SCCH is configured by higher layers. Note: for DCCH/DTCH transmission, HS-SCCH shall be HS-SCCH order; while for BCCH transmission, the association and timing between HS-SCCH and HS-DSCH is the same as described in subclause 7.2.7.1.
+
+
+
+Timing diagram for PICH and HS-SCCH for different radio frame configurations for a given UE. The diagram shows two sets of radio frames. The first set consists of four frames, with a double-headed arrow above it indicating a duration. The second set consists of six frames, also with a double-headed arrow above it. Below these sets is a thick black horizontal bar with a right-pointing arrow, representing a timeline or sequence of events.
+
+Figure 25A: Timing for PICH and HS-SCCH for different radio frame configurations for a given UE
+
+#### 7.2.7.4 PICH/ HS-DSCH Association and Timing
+
+When the UE in URA\_PCH or CELL\_PCH state without a dedicated UE identity detects the PICH identifying PCCH transmission, the UE shall receive the corresponding HS-DSCH TTIs. The association and timing between PICH and HS-DSCH is depicted in figure 25B. If a paging indicator in a certain PICH block is set to '1' it is an indication that UEs associated with this paging indicator shall read their corresponding sub-channel and consider that paging message is retransmitted in $2^m$ subframes where $m$ denotes Paging Sub-Channel Size configured by higher layers which is the number of frames that each paging sub-channel occupies. The value $N_{\text{GAP}} > 0$ of frames between the end of the PICH block and the beginning of the HS-DSCH is configured by higher layers.
+
+
+
+Timing diagram for PICH and HS-DSCH for different radio frame configurations for a given UE. The diagram shows a single set of four frames. Above the frames is a double-headed arrow indicating a duration. Below the frames is a thick black horizontal bar with a right-pointing arrow, representing a timeline or sequence of events.
+
+Figure 25B: Timing for PICH and HS-DSCH for different radio frame configurations for a given UE
+
+# 8 Mapping of transport channels to physical channels for the 7.68 Mcps option
+
+This clause describes the way in which transport channels are mapped onto physical resources, see figure 26.
+
+| Transport Channels | Physical Channels |
+|--------------------|--------------------------------------------------------|
+| 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 26: Transport channel to physical channel mapping
+
+## 8.1 Dedicated Transport Channels
+
+### 8.1.1 The Dedicated Channel (DCH)
+
+Mapping of dedicated transport channels to physical channels is identical to 3.84Mcps TDD cf. [6.1 Dedicated Transport Channels].
+
+### 8.1.2 The Enhanced Uplink Dedicated Channel (E-DCH)
+
+The enhanced uplink dedicated channel is mapped on one or several E-PUCH, see subclause 5B.4.12.
+
+#### 8.1.2.1 E-DCH/E-AGCH Association and Timing
+
+The E-DCH is always associated with a number of E-DCH Absolute Grant Channels (E-AGCH) and with one or two hybrid ARQ indicator channels (E-HICH). A grant of E-DCH transmission resources may be transmitted to the UE on any one of the associated E-AGCH. All relevant Layer 1 control information related to an E-DCH TTI is transmitted in the associated E-AGCH and one of the E-HICHs.
+
+The E-DCH related time slot information that is carried on the E-AGCH refers to the next valid E-PUCH allocation, which is given by the following limitation: There shall be an offset of $n_{E-AGCH} \geq 6$ time slots between the E-AGCH carrying the E-DCH related information and the first indicated E-PUCH (in time) for a given UE. The E-DCH related time slot information shall not refer to two subsequent radio frames but shall always refer to either the same or the following radio frame, as illustrated in figure 27. Note that the figure only shows the E-AGCH that carries the E-DCH related information for the given UE.
+
+
+
+Figure 27: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+1. In Radio Frame #n, an E-AGCH is shown in the 4th time slot. In Radio Frame #n, the 1st E-PUCH is shown in the 10th time slot. The offset between the E-AGCH and the 1st E-PUCH is labeled n\_E-AGCH. In Radio Frame #n+1, the 1st E-PUCH is shown in the 10th time slot. The offset between the E-AGCH in Radio Frame #n and the 1st E-PUCH in Radio Frame #n+1 is also labeled n\_E-AGCH.
+
+Figure 27: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE
+
+#### 8.1.2.2 E-DCH/E-HICH Association and Timing
+
+E-DCH operations within the cell are associated with one or two channelisation codes carrying E-HICH (E-HICH1 and E-HICH2). If the number of timeslots configured for E-DCH use is 7 or more (this corresponds to the length of the timeslot resource related information field on E-AGCH – see [7]), both E-HICH1 and E-HICH2 channelisation codes shall be configured by higher layers, otherwise only the channelisation code E-HICH1 is configured.
+
+A single instance of E-HICH1 (and E-HICH2 if configured) channelisation codes exist in the cell per E-DCH TTI (10ms). For a given UE, a HARQ acknowledgement indicator is synchronously linked with the E-DCH TTI transmission to which it relates. There is thus a one-to-one association between an E-DCH TTI transmission and its respective HARQ acknowledgment indicator on one of the associated E-HICHs.
+
+For each channelisation code carrying E-HICH, the associated instance shall be the first instance of that channelisation code to occur after $n_{E-HICH}$ timeslots have elapsed since the start of the last E-PUCH of the corresponding E-DCH TTI (see examples of figure 28). The value of $n_{E-HICH}$ is configurable by higher layers within the range 4 to 44 timeslots.
+
+
+
+Figure 28: Timing for E-DCH and E-HICH for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+M. In Radio Frame #n, the last E-PUCH is shown in the 4th time slot. In Radio Frame #n, an E-HICH is shown in the 8th time slot. The offset between the last E-PUCH and the E-HICH is labeled n\_E-HICH. In Radio Frame #n+M, the last E-PUCH is shown in the 2nd time slot. In Radio Frame #n+M, an E-HICH is shown in the 7th time slot. The offset between the last E-PUCH and the E-HICH is also labeled n\_E-HICH.
+
+Figure 28: Timing for E-DCH and E-HICH for a given UE
+
+The HARQ acknowledgement indicator associated with an E-DCH transmission is transmitted using one of 240 signature sequences carried by one of the associated E-HICH channelisation codes. Which signature sequence $r = 0, 1, 2, \dots, 239$ and (in the case that two channelisation codes are configured for E-HICH) which channelisation code is used are calculated for each E-DCH resource allocation using the following information signalled on the associated E\_AGCH:
+
+- $t_0$ is the bit position ( $1 \dots n_{\text{TRR}}$ ) of the first active timeslot in the timeslot resource related information bitmap (see [7]) on E-AGCH and where bit position 1 corresponds to the lowest-numbered timeslot
+- $q_0$ is the allocated channelisation code index ( $1, 2, 3, \dots, Q_0$ )
+- $Q_0$ is the spreading factor of the allocated uplink channelisation code
+
+The value $r'$ is first calculated as:
+
+Then:
+
+- if $r' \leq 239$ , $r = r'$ and channelisation code E-HICH1 is used
+- if $r' > 239$ , $r = (r' - 240)$ and channelisation code E-HICH2 is used.
+
+## 8.2 Common Transport Channels
+
+### 8.2.1 The Broadcast Channel (BCH)
+
+The mapping of the broadcast channel (BCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.1 The Broadcast Channel (BCH)].
+
+### 8.2.2 The Paging Channel (PCH)
+
+The mapping of the paging channel (PCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.2 The Paging Channel (PCH)].
+
+### 8.2.3 The Forward Channel (FACH)
+
+The mapping of the forward access channel (FACH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.3 The Forward Access Channel (FACH)].
+
+### 8.2.4 The Random Access Channel (RACH)
+
+The mapping of the random access channel (RACH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.4 The Random Access Channel (RACH)].
+
+### 8.2.5 The Uplink Shared Channel (USCH)
+
+The mapping of the uplink shared channel (USCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.5 The Uplink Shared Channel (USCH)].
+
+### 8.2.6 The Downlink Shared Channel (DSCH)
+
+The mapping of the downlink shared channel (DSCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.6 The Downlink Shared Channel (DSCH)].
+
+### 8.2.7 The High Speed Downlink Shared Channel (HS-DSCH)
+
+The high speed downlink shared channel is mapped on one or several HS-PDSCH, see subclause 5B.4.8.
+
+#### 8.2.7.1 HS-DSCH/HS-SCCH Association and Timing
+
+The HS-DSCH/HS-SCCH association and timing is identical to 3.84Mcps TDD cf. [section 6.2.7.1 HS-DSCH/HS-SCCH Association and Timing] with the exception that the number of HS-SCCHs that are associated with an HS-DSCH for one UE can range from a minimum of one HS-SCCH ( $M=1$ ) to a maximum of eight HS-SCCH ( $M=8$ ).
+
+#### 8.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing
+
+The HS-SCCH/HS-DSCH/HS-SICH association and timing is identical to 3.84Mcps TDD cf. [6.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing].
+
+# --- Annex A (normative): Basic Midamble Codes for the 3.84 Mcps option
+
+## A.1 Basic Midamble Codes for Burst Type 1 and 3
+
+In the case of burst type 1 or 3 (see subclause 5.2.2) the midamble has a length of $L_m=512$ , which is corresponding to:
+
+$K'=8$ ; $W=57$ ; $P=456$ .
+
+Depending on the possible delay spread timeslots are configured to use $K_{Cell}$ midambles which are generated from the Basic Midamble Codes (see table A.1)
+
+- for all $k=1,2,\dots,K$ ; $K=2K'$ or
+- for $k=1,2,\dots,K'$ , only, or
+- for odd $k=1,3,5,\dots,\leq K'$ , only.
+
+In the beacon slot # $k$ , where the P-CCPCH is located, the number of midambles $K_{Cell}=8$ (cf section 5.6.1). In all of the other timeslots that use burst type 1 or 3, $K_{Cell}$ is individually configured from higher layers.
+
+Depending on the cell size midambles for PRACH are generated from the Basic Midamble Codes (see table A.1)
+
+- for $k=1,2,\dots,K'$ or
+- for odd $k=1,3,5,\dots,\leq K'$ , only.
+
+The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223.
+
+**Table A.1: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5.2.3 for case of burst type 1 and 3**
+
+| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ |
+|------------|---------------------------------------------------------------------------------------------------------------------|
+| $m_{PL0}$ | 8DF65B01E4650910A4BF89992E48F43860B07FE55FA0028E454EDCD1F0A09A6F029668F55427253FB8A71E5EF2EF360E539C489584413C6DC4 |
+| $m_{PL1}$ | 4C63F9BC3FD7B655D5401653BE75E1018DC26D271AADA1CF13FD348386759506270F2F953E93A44468E0A76605EAE8526225903B1201077602 |
+| $m_{PL2}$ | 8522611FFCAEB55A5F07D966036C852E7B15B893B3ABA9672C327380283D168564B8E1200F0E2205AF1BB23A58679899785CFA2A6C131CFDC4 |
+| $m_{PL3}$ | F58107E6B777C221999BDE9340E192DC6C31AB8AE85E70AA9BBEB39727435412A5A27C0EF73AB453ED0D28E5B032B94306EC1304736C91E922 |
+| $m_{PL4}$ | 89670985013DFD2223164B68A63BD58C7867E97316742D3ABD6CBDA4FC4E08C0B0CBE44451575C72F887507956BD1F27C466681800B4B016EE |
+| $m_{PL5}$ | FCDEF63500D6745CDB962594AF171740241E982E9210FC238C4DD85541F08C1A010F7B3161A7F4DF19BAD916FD308AB1CED2A32538C184E92C |
+| $m_{PL6}$ | DB04CE77A5BA7C0E09B6D3551072B11A7A43B6A355C1D6FDCF725D587874999895748DD09832ABC35CEC3008338249612E6FE5005E13B03103 |
+| $m_{PL7}$ | D2F61A622D0BA9E448CD29587D398EF8CDC3B6582B6CDD50E9E20BF5FE2B3258041E14D60821DC6725132C22D787CD5D497780D4241E3B420D |
+| $m_{PL8}$ | 7318524E62D806FA149ECC5435058A2B74111524B84727FE9A7923B4A1F0D8FCD89208F34BE55CADEB90130F9954BB30605A98C11045FF173D |
+| $m_{PL9}$ | 8E832B4FA1A11E0BF318E84F54725C8052E0D099EF0AF54BC342BEE44976C9F38DE701623C7BF6474DF90D2E2222A4915C8080E7CD3EC84DAC |
+| $m_{PL10}$ | CFA5BAC90780876C417933C43103B55699A8AD51164E590AF9DA6AF0C18804E1F74862F00CE7ECC899C85B6ABB0CAD5E50836AD7A39878FE2F |
+| $m_{PL11}$ | AD539094A19858A75458F1B98E286A4F7DC3A117083D04724CBE83F34102817C5531329CDB437FFF712241B644BDF0C1FEC8598A63C2F21BD17 |
+| $m_{PL12}$ | BEB8483139529BDE23E42DA6AB8170DD0BFB30CE28A4502FAF3C8EDA219B9A6D5B849D9C9E4451F74E2408EA046061201E0C1D69CF48F3A94 |
+| $m_{PL13}$ | C482462CA7846266060D21688BA00B72E1EC84A3D5B7194C8DA39E21A3CE12BF512C8AAB6A7079F73C0D3E4F40AC555A4BCC453F1DFE3F6C82 |
+| $m_{PL14}$ | 9663373935FD5C213AC58C0670206683D579D2526C05B0A81030DDF61A221D8A68EAD8D6F7A0D662C07C6DCD0115A54D39F03F7122B0675AC |
+| $m_{PL15}$ | 387397AE5CD3F2B3912C26B8F87CE82CEFE55507DB08FB0C4CF2FD6858896201ACA7264281D0298440DD3481E5E9DDDB24C16F30EB7A22948A |
+| $m_{PL16}$ | AFE9266843C892571B6230D808788C63B9065EA3BDFF687B92B8734A8D7099559FEA22C9416576D0C087EB4503E87E356471B330182A24A3E6 |
+| $m_{PL17}$ | 6E6C550A4CB74010F6C3E0328651DF421C456D9A5E8AE9D3946C10189D72B579184552EE3E799970969C870FE8A37B6C4BA890992103486DC0 |
+| $m_{PL18}$ | D803CA71B6F99CFB3105D40F4695D61EB0B62E803F79302EE3D2A6BF12EA70D304B181E8B38B3B74F5022B67EB8109808C62532688C563D4BE |
+| $m_{PL19}$ | E599ED48D01772055DBE9D343A4EA5EABE643DA38F06904FC7523B08C4101F021B199AF759A00D9AC298881D79413A77470992A75C771492D0 |
+| $m_{PL20}$ | 9F30AC4162CE5D185953705F3D45F026F38E9B5721AEFE07370214D526A2C4B344B508B57BFB2492320C05903C79CBEE08C6E7F218B57E14D6 |
+| $m_{PL21}$ | B5971060DA84685B4D042ED0189FAF13C961B2EF61CC164E363B22AAB14AC8AF607906C1C6E04F2054C687AA6741A9E70639857DA02B6FFFFA |
+| $m_{PL22}$ | 97135FC2226C4B4A5CBA5FCA3732763B87455F73A1148006F3DF214BD4C936D061E04045160E2CE33B9CD09D08FDE2A37F4E998322B4401D27 |
+| $m_{PL23}$ | 4D256D57C861B9791151A78D5299C56D116B6178B2A2D04BB95FB76540AF28341DC6EC4E7ED3BF9E508478D9C8F44914805DA82429E1CF320E |
+| $m_{PL24}$ | 858EF5C84CE32D18D9ABA110EEA7474CF0CD70254D2928C3F4DFF6BB3A518587CADA19029078AC90A8336C8178203BE3289E601F07D089CB64 |
+| $m_{PL25}$ | 920A8796A511650AEF32F93DD3C39C624E07AE03CE8C96139973F54DCB9803C5164ADB502D4FF561564D607037FCD172921F1982B102C3312C |
+| $m_{PL26}$ | 485C5DAE76B360A9C56E20B8422EA3E6ACF07CB093B5587CB0E6A5498A4714081EA98DBCD0482B26E0D097C03444473D233BEF3C8E440DEBF |
+| $m_{PL27}$ | 565A9D54EA789892B024F97E728E8E112411942C48BD0C5BC8AA457D8DC9941F0F7424B38643FFE6521CD306FBC56FE10F1428D4C245B5606 |
+| $m_{PL28}$ | 5AEF2C0C2C378179A1AC36242E6B3EDB72C42D3624437674F8D51260C0898C201837CBA14E9E23D1EF6451C4ACF27AB031F457A8A1BFD148AE |
+| $m_{PL29}$ | 87D8FE685417822A23D925307E6C11081ADAC4702BCCD9BE448E78984D109B50DEF5B7C58BC71EA1F0A6826BA8AD1978843E7697F3E416ADA |
+
+| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ |
+|------------|---------------------------------------------------------------------------------------------------------------------|
+| $m_{PL30}$ | 84802B72AF27B5BE724D1FB629E0E627BDB0D9061292562F98350C1D0C9D4B9D8E2BF71123C82EBB161003AE9829E07244D78F19926F8847A2 |
+| $m_{PL31}$ | 8CCB5128238BCB088E30972D62792AEF02B9BDDCAD68C9916C00BF91CBE788B0F03851FAAF88605534FD73436C259D270B1013CB14226F658 |
+| $m_{PL32}$ | 62F4E6FAC2BF1979CE6854AA2D33534BFB2F946519101A6589131C3640707D40E67ED804AF8736AD213CAF5935741900061967E8285C27E34C |
+| $m_{PL33}$ | 4095E5B4EEAFCDF68A34B267EEA28D8444FA533900F41499E260D2E65C256A52E1DD5861F5227C98E00687D107233F51A1167BCF72FB184654 |
+| $m_{PL34}$ | 5630E9A79FCAD303404D9E5A802299162657AAC734761C6E90DA8BCE4F61A763E0BB48D3FEB3F78468C828ABA4828DAD06E0F904CFD40421DC |
+| $m_{PL35}$ | CD12B24C0BCA8AAC1FCBF0500A3BC684A180E863D888F2506B48C68ECF17F76CB285991FBA18EB6397211FAD002F482D57A258CD45DE3FF1A6 |
+| $m_{PL36}$ | AFCF2A50877286CD3405442730C45514F082D9EC296B367C0F64F04C4E0007DCA9E50BEED5C102126E319ACBC64F1729272F2F72C9397029FE |
+| $m_{PL37}$ | 18F89EE8589D20882A72A44DCDF0050F0A3D88DBA6531614973D26905FDF41E3F779FF0648E8AF1540928511BCF4C25D9C64AF34AC31B8965 |
+| $m_{PL38}$ | F890D550F33F032ECDA3A51FED427D634F64EB29AF1332A23CD961258E4BAED040E7B336918E250EC272A12816B9EBFFA1E0AE401185F08C10 |
+| $m_{PL39}$ | ACE5DD61506047E80FB7D41BD3992DF4D7F18EB46CC145C0E9105428C2F8F299141F5D66691904A7DC2513A3B83994ACB1292246B32818FE9D |
+| $m_{PL40}$ | 150680FF900C9B46E1E24D54BE2238CB950A934E5CCDE9BC3939EB51CB0AE202B7D339EEC2018B33A0AB9B63DA5D512D64FB58C0E51A1C82C2 |
+| $m_{PL41}$ | 51A579EED2663A002D32D10A0753173612F4D5BA167D1807C61F25C4D42C063682E8E9DD019F79D446A046EB3F75E50FEB228DC52F08E694B6 |
+| $m_{PL42}$ | CDC644FE4C0C6897604F9D14D714123BF16FFF0E49F35F674908CA60653702FE27BCCA2A47098453AF8661055C8C549EB6A951A8396AD4B94D |
+| $m_{PL43}$ | 750A10366C595373C5001CA3E4239764B1409D602CF6052B39BC6A3255A15FE06C782C4C5F847026A7E79838A2933A61C77BB6CBF5915B2DA5 |
+| $m_{PL44}$ | B7490686D78E409082C4C48FE18D4C35429C20AADF96076B92FC4E85490664753DB0891A0B27FD849BB7FCA99E3B38F22F8C662852COD35AA6 |
+| $m_{PL45}$ | D86E1B575B47D23DA811806A54C231281F03317830E7BD305D3CAA7D6382A5233104CFD54D22DF9F34535E5B390D9040CF1375FEA44CEC29E2 |
+| $m_{PL46}$ | 828655960C026EC67B683480992AC2ED2C43ABC606F5220C2945F373470BE7ED5BCCF7C1AA0986BBCC84F11F1658AA568FAA0A60C5F0B5BFA |
+| $m_{PL47}$ | D76230E02C8533653AAB99B288AA2ADE25A1C1BF28516C04239240EAF1EFC0B98974B51F886861D8A1E9F5D62CFFEC309F071A9716B325101B |
+| $m_{PL48}$ | EA207662865B8A07D69648964DED818EE474A90B94473408871880E63EF0596B9FCFEC3C06B86EA6AD2B06C91672EFB33C70241A5450B59B8A |
+| $m_{PL49}$ | 9CB5459549909835FAB22F0D99298C120ACF479F814CCE749079D40688F28101037762F125C776DA9C5FA1FCE0E76E452F8185354FDCDE94E2 |
+| $m_{PL50}$ | 227506304AEC1D6F93569B51FDC3405A0F38194F65BE17163A3CB9827A35AECEA757D020FE249377ECD561428A38FEED004EC859C272563185 |
+| $m_{PL51}$ | 96B9AEC9938910F0E533422A3977519B05CD4AD3909BC15A7502D48D49C124FA192A8E57027CFEB11DF542010603CE5C9FDF8E626D4FBF8CF4 |
+| $m_{PL52}$ | A6AAD06E095A9BE0BD9F8A2ED40C3CBDABE91C700CBB778C8696CC06F3A675C16BDB2918E5F2111005A8727206DC6A9684E05655185C398EEB |
+| $m_{PL53}$ | CD168D384A78DA172991AD333EE2A9880905AFE59E2A2A4AC4414C40F82874F98A3CBE7B44F4C7F4710B35FD88AFC0399FAEB070EB9CA4D30A |
+| $m_{PL54}$ | 22016CA87AD1549174A8699DD65599697871091457E83E0912E7E77A06531C209394D283D18A38662B73681DD9C5BF330FED978BDA7D487CA8 |
+| $m_{PL55}$ | B9401B0843AA6F7827A13BD66C922287E8886C31EB5B90B82B472CCD6DA3D8D4FBF78B8F8496DFA8252B06429D5DD17142F1C908ACCD70EA0C |
+| $m_{PL56}$ | E42B9EFD5C5D09AC27B3C7DA28D02493A70521223B9D7A76A9D13E9C171017964D16A70C08EAD02C3DC948889C23E365AFCF01BF20B89B0BF5C |
+| $m_{PL57}$ | 9DA0180168DB915E9F3597B59312198E1B5CC00D743C2ECB0DBAADA3E35A2465ED1EAA9D74734D49A313CE4DFF020D0760E3153DC485603943 |
+| $m_{PL58}$ | B6C966619ECB98191D719C187C07BD503425650CAA3A2D1F2DF5212B1441D7A0C1D36A4C9C2550240AD17CA43BB3943DFFFBF1E283D81299CC |
+| $m_{PL59}$ | DB0E8C41F08A03D477C1AA548799274C4BF3EB68F2636166FDC8D4B1E7132539930297E228BA232BB5C279FA5ECA3AC10E24361AF050A453B8 |
+| $m_{PL60}$ | 89BC2E2E7974EEBA833CF32F224C85A289148478527DB48FA6EAEA84C5E288CC3914CB54ADA0476278750187F68FBEA41017E1E58DF1A5A3D |
+| $m_{PL61}$ | 70A457D1314A278625443EEB52520815EC92CEF17417B97440DCB531BC1CE83212F63270418D0FBDE71F6DB9E0EA88772E1E4535B6633E4425 |
+| $m_{PL62}$ | C388460AD54B36C4452CF0433BD347100ACC24C79C535AD3E1F23FE0425E93A044C553BFA |
+
+| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ |
+|---------|-------------------------------------------------|
+| | 116E09AA4BB32F13CFA76FBA1BC17520F45EFD44 |
+
+| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ |
+|------------|-------------------------------------------------------------------------------------------------------------------------|
+| $m_{PL63}$ | 0BAFCADCDF9AA2846681782CD3B90CA036A863C78EE1507620BC394D0C6804B4C97A15BC9
C0D7B79E6892EA1BFF1A0DD9573A9213AB140DD0D2 |
+| $m_{PL64}$ | 833B0226789A62882FCD27A30885E67872B1A1C2FA484AD498011599DD57E8E2A07A560B4716
7AA5F60EF47177DBB1632D5387A2896348640B |
+| $m_{PL65}$ | 8F52820323ABA5E6C6B465821B621600B980E59F53A599DA5646BA103214336836CF17E3386C
E4FB2BC5F25CCB30CF7F500546828EC8786B8E |
+| $m_{PL66}$ | E2E9A29C3C8207B9A4508FD2F667A159F068EEE8D00686F46EA904C3692C1D79DFF1B32E510
3720D47B4B58AC35384A26087027E141B3126A8 |
+| $m_{PL67}$ | 70E7C39FD2D3AE1DCE341699A544D801A8688A6EE47C5CB3630022147DDC06241FC5337A34
8A462B2472DEC5E104DD520ADA5114DB065D4B0D |
+| $m_{PL68}$ | 9E3483CAB164BD053C4971D4D87494CC689033D589EF80E5453376E4A8DCC02183B98C36B0
FF7DDC0AD07FCE8B4D5164371BD03A2110AD1247 |
+| $m_{PL69}$ | 04DA1C649B0608938DAADD3FE920A4F681690C54505429DBDCDCF10067AB5714BCDDFE1F2
8692710F794765781C1D233344E119BEE8A8416DC |
+| $m_{PL70}$ | 7A18D6D30BDF44410714C3DCA27D8F9EA8542D87122205640B98313C91AD9A0B993A5A7BC
3E035F93B8BBE6D4204BC82A9FA8D4C1A7618CF |
+| $m_{PL71}$ | EB9525E10265A48733C8E0E77E459310112A71DCA680F68AC044B64BC0A31D02EEA0F7ACAA
AB7F1E574E94FEA2D1301CB14B03263DA8122B76 |
+| $m_{PL72}$ | E706C6ED2D6F89153835079BE0C6D45310845EF2F9F6C6AE91B7419810508BA501C0148BF09
955BAD90D6391BA8EBA5CEFB23221CC75143D7 |
+| $m_{PL73}$ | DF071A10AC4120CD1431590BEDCFF9483CA7047B19590D035D309240BDB4264E9A3A2761402
EC97FD8BC51B4AF32E37FBC47162A2357D18751 |
+| $m_{PL74}$ | F0F952B2238139F46D8254D1A2C1C22A16BA71EC0C0C900ED1442452D7F44C798BC65FF4067
1B88074BA0B74C6510996EEAC495C5B49C37DEB |
+| $m_{PL75}$ | 1C86BD82EDA81FD65418D3837B5552A853791456D93B06C62C650D86CFBEC269AFFD772763
064062C03751B9428C6DA2E60383025F9E404B70 |
+| $m_{PL76}$ | B390978DD2552C88AABA7838489A6F5A8E9C41E95FFA2215819FB8A5BFE39C8A706CC658E5
49E966611B843A1468406C41C09D1560BEDA4F1B |
+| $m_{PL77}$ | 1A69EC9D053C7E84BAE7A48CCC71857D0C6B06D1065E3EA4633B133AA022B8104F6EE7C69B
6184B746C8822958B0A16686F27C8A0E3B4EFEAD |
+| $m_{PL78}$ | C95B2070816DC97C6D8DD2583263E73F9AAAFD13F0548D2EBD835824418F11E54111005FB71
3AB234BE412347358281C7DE331EDD21B8BEA52 |
+| $m_{PL79}$ | 56D6408399F23C2ED85EE0F68111D69A91A3AD9A732AC57CA08F86CC28B3CF4E4B02EBBA0
BCE5CAE5BACC4D5200407079C04093A84BB18DBA |
+| $m_{PL80}$ | E662E7043867BE250764DA0596D34A582A619B408B505E6211DD6286E93A37F95B1EA680C0C
5F3E777E3F71E8D75495D59043217FC0E222E16 |
+| $m_{PL81}$ | 27D5E681C222297AD478A079EF12F1A98F744B66335303322EF8880B931FEBF8322F4302944E
80BED468A0A516D410B183D863795992DA7DDB |
+| $m_{PL82}$ | 5100336C05F9E5BF35201906C1C588858E0DAF56130DF5554B9AB21CA15311A90290624CD63
E03F5EDA49DB7A0C32AB5F1CA427A2D5635FDA5 |
+| $m_{PL83}$ | C696DC993BFAE9A61B781B9C5C3F5CFAA4C8339D8B03A9B0387883D0482A41AC78D652242
5959846E561D26A30FF79A205C801A85889736B2 |
+| $m_{PL84}$ | D562297561AFF42D3168296C1153E4E39BE7B2EB0348BC704625AA08391235075EE0DE0A79A
B03222FEDB27218C56F96EAC2F91CC8FCE64B12 |
+| $m_{PL85}$ | DD0B6768FC01CC0A551F8ACC36907129623E975AB8B3FF58037F1859E2FA8C62C2D9D1E850
6916029A2C3F8CAD9A26AE2CC652F48800859F5C |
+| $m_{PL86}$ | 923920696EB3AB413786C41854822282BB83F6900D33A232D470BE198BBF086067B72613300C
593B74251E2F079857ADBBBCD86583A9DCAA6DC |
+| $m_{PL87}$ | B8EF30C797D8D2C4EF11244F137D806E556A436626D0115A621C92C34D166A68BCEDFA0040
DA8FD6F987B1CD5C2AA1C1B045E64475F0F8DABD |
+| $m_{PL88}$ | E1887001D414405ED6419E9EE1D1D346D924ED57ADF04B31B7948099976B2D1501A60DFFB28
7AD44C8783DF0C1EA5AA5D273D1389C8EA22DCC |
+| $m_{PL89}$ | 8C2E379A58AA96748141CA84C35987905F984A49D3AD9BFF7807AC244C16C1DF74343C2E1F2
5514F5A0954CFBB3C92E25EF783136844998AC5 |
+| $m_{PL90}$ | 78F8A99E0A54E27F51C0726FE7A11EB26B1E29FE65F55AC8AC58011465900B958488A90F6DF
614A58431DC8B6C6B9A6F032EE0E0B1306EC4B4 |
+| $m_{PL91}$ | 88F7A31B7B20E0F05CA26E729B4F8A1933962D7BD7BE3E1EB130B28C794C0B4D01CADE0900
6FF97E80117509733F3A9DC225413A0AE08CA662 |
+| $m_{PL92}$ | BE4DFCEAC18905AC8D5DA27A794F88A4D3058D2EFA3B075A819DEAE688EAF8940A653ED71
04E7B403D490F0A9030264E1F12B8922C75775E61 |
+| $m_{PL93}$ | 5BA4B79FC4550234D8922963BF3537485E3C8745A5DB90D3E2E454B30FF61112F508155B7C2B
3C4C628AF846240C2021ACDE547E5A41F666B8 |
+| $m_{PL94}$ | 00556D35649F7610AB24A43C4F16D6AC0571FD126F11880C5CD72100D730E4E4D6BB73C33F8
37FAF1072743B249ADA2E09598B1EB23F1180A7 |
+| $m_{PL95}$ | 7A0CC9F21BD69CF3023E944545C2176EF0D4F450B765C28359FB8A32137D043D0E5713E67B3 |
+
+| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ |
+|-------------|---------------------------------------------------------------------------------------------------------------------|
+| | F61320985D2C6106605081F87D2296321468A2F |
+| $m_{PL96}$ | DA669880995B0671201172BABFF141D5854A245E211879EF3038A7C84170DABDB368455F24653161E7886E15B253F93E3A3C568EFB17CDEB1A |
+| $m_{PL97}$ | 4E294E53D1661C1F6F748302A7723DA951C00FDB8BEBBF67A68710BA0F1A255DFB1627059D41A23D3961726DE6FEB10E5D209CC4505B209812 |
+| $m_{PL98}$ | 73385DF701414E144768A67EF72924B1653479E962FB1554B7E54BC5284D9B3E41C0C133F878972230721918AA425501B920B204FECE0C7F8A |
+| $m_{PL99}$ | F4492160805F258CE592DF4D1200566F81D173458D78EA3ABED79A14AF88170DB1D4A9A5931D2B80C58C27FE17D806E3E6A66CDAAD09F118D4 |
+| $m_{PL100}$ | 44D562D9012D8B07B8F44596467C11A163982BB7EAEAC184078B6B8CE46B5D7E17C39CEF576A025491183017FA09931D070B307B86524B03FF |
+| $m_{PL101}$ | FCAEEFCC49A13B4FFA12C0CC6A2B90CF4F57D78B1E98294B04675C2F0991661FDC61A452A247F8C29E0284AA21026F368307375AA2C3F1E12C |
+| $m_{PL102}$ | C486DF0510DCAD5AB86E178A686D398E11A0ECFAC5A326C10129257E5456B22FB8E147E9190D9929A5DFFE44715FA47D62F04CFC9B1C201414 |
+| $m_{PL103}$ | C10AF383DC708E257E15A8AB337BCE684A2F4AC7A22DC2C25C277F8E8D0858E79317CDDDD9AA2EA6CBE604D24AC0945026103E7B4126FD361A4 |
+| $m_{PL104}$ | A5C60A181148D9A931B2DDDB9D169648BA54F366B4EFAE88F6861909EE0F07C037EE349D0EC59A823286E366CA3943589EEA7F828C3728085F |
+| $m_{PL105}$ | 96136AEBD5E28462B0421DF292BA899FFA660D80EA01620D2C7490E5347127884AA3C3D1FF44BCEEF6C29EC589CDEF200C5742C5964F8B2B52 |
+| $m_{PL106}$ | 40F63C04ACAD986255D1E16B769A6D4C11A1D075E804BDC0AC61923E9A67F5D7417756328072455F6E22B1C64E06F367D1B0808295C2D90E22 |
+| $m_{PL107}$ | F4882D413578C4888C5F002CF6D0E03778134A860436551FD57537E4CED334B3C9CEBACE615238271717AA762448B86FA53D2074BCE35658A7 |
+| $m_{PL108}$ | BCCC92D72C920E685530591FC351743D1E23DE044BF81D32650406113E23ECC757FDE4E386B6E2E7195EE4969717A7BD0812AC312B33A54308 |
+| $m_{PL109}$ | 6ED59DE0D44370A861CE2B42CF5E578E764A682AB5777905EE027D7160490EDC6C28989B23805AA697FCD215CB401BC5E4D430624C01B16192 |
+| $m_{PL110}$ | DE80C0E273B92CC3C5034F7A20DB3914643C430B425C8B9249EAF73ACE8C3BCF17957242CF534D87A67D4DC0252275262E737F4095450CFA14 |
+| $m_{PL111}$ | 9505C4FEF2A397D5059F4729D013292A8321FFF929ACB0A210D0A13E13061227C44A68FBD8CE6B66CE3D783363CD039AB35EE52603E09B758 |
+| $m_{PL112}$ | E8BE90D7F954B14D8002A4AC20765ABEED80634498C836D79B0F9338DBC17B28F05CF4E79136779E1C55AA30B6215F890882887B3B53C23E2 |
+| $m_{PL113}$ | 9F4B622C1358AE5468DC31E4B2CA320E5E20458C1DE5405BF4F9AD7D45A5BCAA39EC0626FFFC698C16A009CCCB7A18A64E85E70BA71731BA24 |
+| $m_{PL114}$ | B91B2624843CF48299AFC2B1442570B41F28F578530D1E322E0B54282372131C71ACB924E70768A243EEC3200E7A5EBFA77111D9FB07FEA8AE |
+| $m_{PL115}$ | 965F42DDA3A4650FE2F5103932B68F166FA424B9F0F7045311D962C2A9F66B9BC6C66FB480F9800354E0C54A72251071422CF1DFC44F94C00C |
+| $m_{PL116}$ | 08ADCE48699FC30FA0788073BDAADB9177BBB4C1CED41F93085218364B8BAD8488561EF0FE1B0DDAA403C602494CB35697D62AA0A2B93A64CF |
+| $m_{PL117}$ | 9A313BED80B1220D77C8ADA4B2E0B3D284A5120A94B741380923C78D3AD32BC3E71EC6EEA520E9D447D8727697598BB987F17506F482003ABD |
+| $m_{PL118}$ | 24C9AD4C14EFEC002A3473FCAB04E492F2E269161A2960BA8AF09FD710B444A40C4E8B138418E62301E91FBA97AFDC58759A76D00F676736C7 |
+| $m_{PL119}$ | 6514C7733711CE4942CD2123AB37186EB7FECB7E78ABB28744864942FCF4C0F810054AF55B1042EB53064F0857C61D85B2CF0D2DC5826AF22F |
+| $m_{PL120}$ | B2C80CDC83E48C36BC6FDA8661208EAD392F3A0571BE41DFAD765E744932ADEA50061E66C05498A5381B2A1F1B446587089DC4E4A2DF03D82 |
+| $m_{PL121}$ | 639368BA75CC709A3D9F28EDA237E32C2017A9BF1E382045B9426AEE0A4049DCB4E1D7EBE4647B855212824557497CFA039885A3BA42F98F63 |
+| $m_{PL122}$ | 6A70DDC17D0C8024B1C853F0C1948561EF32510151BE0C63BCA9171F20217891D1021EE72586CAFF557F8973336913A94A2A699B8740B054B8 |
+| $m_{PL123}$ | 2E32E3A35CCD001172CE310B63B4E406126045A0FA3795BE3E3D9B56F72405FC94FD89946818BAECD24A61BABBEBE2D23052AB01EF73CA0CF4A |
+| $m_{PL124}$ | 829395C35205A480AC1351C25E234BF52D384A3DE1C5138A650A6F82F739757D812D9C38231AB9FD81AA0648B11F6F6113F9312C57624FC746 |
+| $m_{PL125}$ | D98FFE19C0AAAAB0571A9075ECDFD3E7373F5255DC669116A8C6913F0123E598F930934C5F6A601C37C529C371A0C391B59AC5A9E286D04011 |
+| $m_{PL126}$ | C1A108192BCE6C2430A63C189BB33856BE6B8B524703FCB205DAEF37EF544CD43CA09B6181B417398083FF2F781BA4AE89A5CA291DB928D71 |
+| $m_{PL127}$ | 42568DF9F61849BF9E7DEE750604BE2E0BC16CC464B1CDE15015E01D6498E9F3E6D6950E5824651F212BA0057CE9529B9CCAB88D8136B8545E |
+
+## --- A.2 Basic Midamble Codes for Burst Type 2 and 4
+
+In the case of burst type 2 (see subclause 5.2.2) the midamble has a length of $L_m=256$ , which is corresponding to:
+
+$K'=3$ ; $W=64$ ; $P=192$ .
+
+Depending on the possible delay spread timeslots are configured to use $K_{\text{Cell}}$ midambles which are generated from the Basic Midamble Codes (see table A.2)
+
+- for all $k=1,2,\dots,K$ ; $K=2K'$ or
+- for $k=1,2,\dots,K'$ , only.
+
+In all timeslots that use burst type 2, $K_{\text{Cell}}$ is individually configured from higher layers.
+
+In the case of burst type 4 (see subclause 5.2.2) the midamble has a length of $L_m=320$ , which corresponds to:
+
+$K=K'=1$ ; $W=128$ ; $P=192$ .
+
+Thus for burst type 4, $K_{\text{Cell}}$ shall have a value of 1 and the midamble is generated from the Basic Midamble Codes (see table A.2).
+
+The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223.
+
+**Table A.2: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5A.2.3 for case of burst types 2 and 4**
+
+| Code ID | Basic Midamble Codes $m_{ps}$ of length $P=192$ |
+|------------|--------------------------------------------------|
+| $m_{ps0}$ | 5D253744435A24EF0ECC21F43AA5B8144FBDB348C746080C |
+| $m_{ps1}$ | 9D7174187201B5CE0136B7A6D85D39A9DD8D4B00E23835E4 |
+| $m_{ps2}$ | AE90B477C294E55D28467476C6011029CDE29B7325DF0683 |
+| $m_{ps3}$ | BC8A44125F823E51E568641EC12A6C68EAFDFA2350E3233C |
+| $m_{ps4}$ | 898B7317B830D207C9BC7B521D5715680824DC08347B2943 |
+| $m_{ps5}$ | 466C7482C8827655BC13F479C7C1417290679A9841297C4A |
+| $m_{ps6}$ | AC0734C27C7DC1B818A8492744290DFE866B0EBA62B0B56E |
+| $m_{ps7}$ | 0A92106325B15A8C15FC3764724CE67A5056D50A77F9360E |
+| $m_{ps8}$ | AE69F62E23035083E6094B89493D33E06FDB6532D473A280 |
+| $m_{ps9}$ | B485D4E3614C9C373EA1365FA6FA890E9844084EBA90EB0C |
+| $m_{ps10}$ | 66182885E2D28360D2FEAB842C65304FFC956CE8DC8A90C7 |
+| $m_{ps11}$ | CC30A9B0A742FCC1E9A408415368391F1299AEA3CB6509FE |
+| $m_{ps12}$ | 673928915886947F464FDDAAD29A07D182328EBC5839089A |
+| $m_{ps13}$ | 4418861C14D62B46EE6D70D4BF05A3ED801A01BD6CDC5235 |
+| $m_{ps14}$ | DAD62DC88F52F2D140062C2330BE6540E6F86192322AFB04 |
+| $m_{ps15}$ | A2122BAF24529CEA9855FB43CE40923E7CA7B30D92E40702 |
+| $m_{ps16}$ | 6C44AB41E11F54B0929DF65673BD231F92A380132D9F1712 |
+| $m_{ps17}$ | 1DC2742E756CDA6421340D0087DD087A615E4B8688CB2F75 |
+| $m_{ps18}$ | 2E0105328B56E9E07D9B5A62F38B08AF8D8C2817B54F3302 |
+| $m_{ps19}$ | 88315EC30A94CA4EDB2C77079D9BD810A2E280B50DABB213 |
+| $m_{ps20}$ | 440E0093D28CB2B2B0A95D18CEB4AB934C33FA45C1CFC7B0 |
+| $m_{ps21}$ | CC9BF85D41A96A6EC314F9611D5E1C0672556C8850801BB4 |
+| $m_{ps22}$ | 1ABEA04C99BC26972715F01957C0B6B959CC71CD88120817 |
+| $m_{ps23}$ | EC5A33DA0BA4470442C5CB324A8E47B0A9F7968FC8108EE8 |
+| $m_{ps24}$ | F82086290271DB446B5B1DC15D9BE96414B19B3D5E0F540C |
+| $m_{ps25}$ | 11A1A790D6958FD3A9157DF1E05D1378248CA201EBCC7592 |
+| $m_{ps26}$ | AA8564882231907BCE78092DC6C9DD4F5A0E4A34AFCFB809 |
+| $m_{ps27}$ | 912EE2238212F87BC7CDA7F30441ED184A6AA954EC4D20C8 |
+| $m_{ps28}$ | 2D200D8B8891B804673E380A1AF5AB875986E29D37D3FDC9 |
+| $m_{ps29}$ | 75E086B6C818423491BF9D6365C52FD1C5E42A576E268170 |
+| $m_{ps30}$ | 50ADBF27DA2A3701470186B699118E16DDB0D10F705607B1 |
+| $m_{ps31}$ | 656C0692B4E22023590A906D2A74DFD471C883A7B1E0B3A2 |
+| $m_{ps32}$ | C21FDACD09A3CDCE74C4794010A3E45769B142505C56A0E6 |
+| $m_{ps33}$ | CD9392A87C2D4D7CE5801CDDA8A76339B6F900F008B290E2 |
+| $m_{ps34}$ | 956426FEFD8B8D52073E87984E10C4D255064E1372C04A24 |
+| $m_{ps35}$ | C4F4D6DF1B754AD6063FD10C331C1428ABB27B0700134B94 |
+| $m_{ps36}$ | B65548082B34E9FAF43F33C4070F79099758CFD41B491A11 |
+| $m_{ps37}$ | C8317EA111A82B04E78B88B864B1EF5D711BBEB4A0527036 |
+| $m_{ps38}$ | 8FB7AD1188E8D1A5219845013672560FD38904E70537403B |
+| $m_{ps39}$ | B41A324E0D80AA0598A8D391C1D7FFC82B4A075218E98EC3 |
+| $m_{ps40}$ | 49A6350A62E208B011E86528B9A481A0E76D723F6675FF82 |
+| $m_{ps41}$ | C344C8C23C42A7B7442E6022E95AE4B08A4BFA786F35F911 |
+| $m_{ps42}$ | 28F430CF67D69C9DF60E25656413BC5F932A022DB1406C44 |
+| $m_{ps43}$ | 2FA5D70CF0FED4213F32116051450391C2A627D9B670C428 |
+| $m_{ps44}$ | 959537D988FDD4F1360B4E84701AE5409229C30EDF8BC404 |
+| $m_{ps45}$ | CDD2E0450F9EC12F81391AD4633CB29F315B4A0A890A9A22 |
+| $m_{ps46}$ | 158776A20B4B82C563EC08F086830EA66DBD2DCCB4DF6026 |
+| $m_{ps47}$ | 431FCACBE48208975950342709D11F19AD5FB047F3B440C9 |
+| $m_{ps48}$ | 86B141AC571BA6B42653B12FF04D4F0E6C81F3EB608660A2 |
+| $m_{ps49}$ | 86D297ABD34E8510F6CDB0EA617F1F1051C8799117B02211 |
+| $m_{ps50}$ | 80B2D9530B34E781311D95CFA3857F277CC07014D324AF5A |
+| $m_{ps51}$ | 2B607B93FD8B45601C1E574E14CFC6912C22AEC1045ADC49 |
+| $m_{ps52}$ | D234C5C45E105A837E6DD74BC4E534523A20317BA0625A29 |
+| $m_{ps53}$ | 768CCDB3E2A7A2B863128382590946B25472BE2BFFC40641 |
+| $m_{ps54}$ | 3DA38212E0A987EE1F665D4E13C2AA4446E00A76C948A073 |
+| $m_{ps55}$ | 09173135E4A2CFC8F2678750AB5257110906F013587BDE82 |
+| $m_{ps56}$ | 522E070B266F35E99C1F3C42D2017F8E415550492B72F086 |
+| $m_{ps57}$ | D63E4BD805262A3DEF05C7D86C422E5048921E5531784132 |
+| $m_{ps58}$ | 564AF806E28131611E5F884229265D446A50E1E488EAFBBA |
+| $m_{ps59}$ | A2603E009D3D30147727B750C35C62299AF754D3E4A54E1C |
+| $m_{ps60}$ | 938504B02599D33E28246E4271C375AE81A3BBE8D3F8A920 |
+| $m_{ps61}$ | 461516B2CAC6FC42A4B707CC6073BBE573C014892C811776 |
+| $m_{ps62}$ | 29186DE4CCAAB2CD0100BB19EA595879D63F0F0CFA881AA5 |
+
+| Code ID | Basic Midamble Codes $m_{ps}$ of length $P=192$ |
+|-------------|--------------------------------------------------|
+| $m_{ps63}$ | A064B449CB784A91B803369CDC5EF61A670AAAC044BA3E68 |
+| $m_{ps64}$ | 8719C454D88FF5149DB943CB6CADA01D0B9664B357A18203 |
+| $m_{ps65}$ | A27EC68720F00A714AA2C45A7EF232286984D7B193F5C916 |
+| $m_{ps66}$ | AC8361676AB424E48F0789082B0CD2EFB8D2E627D041DD66 |
+| $m_{ps67}$ | ABA1BEB0064733A0620906BF2B29C95883F069D7E4C35D39 |
+| $m_{ps68}$ | 9E22EEDED47D92CA1D0B7530EC6062287BD83A04874AE00C |
+| $m_{ps69}$ | 0BADEF288B20F5686C5DE3A71219AC2172054326BE831696 |
+| $m_{ps70}$ | 953801EB2AF58C2F80E49A6CC46085CB554243E3B3BBEC8C |
+| $m_{ps71}$ | 333A504C51C8FAC5025994565C3F600F154F64FAEF4EA484 |
+| $m_{ps72}$ | A6583E19647662005474153A6F8DD88A473853E94B720CE7 |
+| $m_{ps73}$ | 90ACAF707D18AF34F5848C58166830AF620ACDC1B2DFDDA8 |
+| $m_{ps74}$ | 39C5C598A374EA82F3F83378258248DAD3808812DD0E74BB |
+| $m_{ps75}$ | F79525DE694629346D73F6256CC0F140F82603197AAA1844 |
+| $m_{ps76}$ | B8C2A8F139097699A693022E78588D4058DB0A65FF52F813 |
+| $m_{ps77}$ | 449B50C2A52996FA5A828A907F30F9F460EE3D99930DF890 |
+| $m_{ps78}$ | 62CEC9574D30184BCB4F94EECF0CC23D2D2A8D0003F0AA33 |
+| $m_{ps79}$ | B56D258889703F76A0738EE3A7D355994159A4851833E198 |
+| $m_{ps80}$ | 65894AA54C0F6C9A206521C9FC379A8AAF6E621C03CF849C |
+| $m_{ps81}$ | 2D47F3414E30CC02C6835D95C9BA204488F0FFCB4852677D |
+| $m_{ps82}$ | 12BE4DD8B906B584010F8A330AB67B278E8642FA33D51B68 |
+| $m_{ps83}$ | BC928A90A4B10906CAEE638BF768E08542F48F1676006DF0 |
+| $m_{ps84}$ | 30C544E437C8ADA143566CD1BC4E9E7BA84139A08505C2F4 |
+| $m_{ps85}$ | 84FD5B05506192B753FBA2C719B584E0EDA01814999867D2 |
+| $m_{ps86}$ | 191F14DD00034E03AB5BB4342F1138B2CD33784E60CFD75A |
+| $m_{ps87}$ | B8ACE7990B6A98A80A61162C4D2D5F88F24E8F7DE4207590 |
+| $m_{ps88}$ | EC1DBE72E8EED0C61054FC2695422AC0AD2D888265B21AB0 |
+| $m_{ps89}$ | 9A1B4CA467AB7E082AF4278E44D177EA78424508C23E8B08 |
+| $m_{ps90}$ | 999EE541C608164AC975214F3A37A677FC2CA03E2C2A4B20 |
+| $m_{ps91}$ | 1BDCC20265031432917A2EB828FB356A22DF9CB609C0F8F3 |
+| $m_{ps92}$ | EB4A81859C93338B8A1B87C02C815AE09D765F6F2249B958 |
+| $m_{ps93}$ | E6A5D1629F4CF09A1F280DE0C480D4C73B26ADE321A50AEE |
+| $m_{ps94}$ | BAAB7286DD24C80B15A7958039B904F1CA83C310C8C7AFF2 |
+| $m_{ps95}$ | 12220F72619E983717C68FFE1C4148F2354B7B1955B65620 |
+| $m_{ps96}$ | A198706E24FAA08BD09EE392414816038E667BB34307D6B2 |
+| $m_{ps97}$ | 30B3493B4C035881A7A722E4546527AAE787FA2C0893AC46 |
+| $m_{ps98}$ | 5A7318126522843DCB7F00A2D9F9BA8F88963E4152BC923C |
+| $m_{ps99}$ | 844844B0CACA702C332CE2692B4166F4B0C63E62BF151BF |
+| $m_{ps100}$ | B8297389526410313692F861DC60DA86A23607F7DDE24755 |
+| $m_{ps101}$ | 6C1144CF8BC01538D655D29ED62DE6E74A3180EC905BF1E0 |
+| $m_{ps102}$ | E9DB3221FACFC5C88691A7013EF09672A130D52C3413AAE2 |
+| $m_{ps103}$ | 2FD0508615EC4CD4BF18ADD46D777078869130C8921A4F0E |
+| $m_{ps104}$ | 40911B4E0525AC874228F6EF642E59154730CB187C7E417A |
+| $m_{ps105}$ | 2034C6A027D4D850F5184AA64C3153231F4651B616BBFCF9 |
+| $m_{ps106}$ | 57833235451525A1DFA213FCE0B419B6494BC7B99F488410 |
+| $m_{ps107}$ | 6DC3D57F2E39158D036825F8804810D77CA1ECA610ECD894 |
+| $m_{ps108}$ | F5C50DE43AA7B731CAB7683524021701F97650499A7070E4 |
+| $m_{ps109}$ | F2184D2699785442E09FA22CC2D60A5A13FFF22AE660A470 |
+| $m_{ps110}$ | EF0029DE0D79207205458CF4D7328E81A93518D93C9A74BD |
+| $m_{ps111}$ | 9D6D8992482FB885AA5E878C3BA2045538B09886C23CDC2D |
+| $m_{ps112}$ | C0A5AB67D1CEA126F6476C75443F0A11CBE749412EF03104 |
+| $m_{ps113}$ | 1853A5C20CDF968C5A180D8EB5E72BF15517D06680D98412 |
+| $m_{ps114}$ | 8CEA1223227ADF37D0DAAB320906E1C79029F480D25181A7 |
+| $m_{ps115}$ | 5561038E96A658EF3EC665612FF92B064065D1ACC1F54812 |
+| $m_{ps116}$ | C55A6263F08D664A1E53584560DFF5E611640D8281D9A843 |
+| $m_{ps117}$ | 4386A8EA59124D043F29056A4598735A4FC7BC11119B90C1 |
+| $m_{ps118}$ | D6571B20668BED50BD7C80388C162632BCB069AA67C7FC22 |
+| $m_{ps119}$ | 4F9F09ABBC1391EC2CCA5359FB52250E533BF04324154106 |
+| $m_{ps120}$ | 662659F42188C9453F6E6DF00C579627045DA1461A3A0EA5 |
+| $m_{ps121}$ | 8DCC9274C0C2A9BA6096BF27FACA542CD01CA8653D60A80F |
+| $m_{ps122}$ | 5C1210A1E50E505F6B73C90156C9D9F19AE2310BBD820DF0 |
+| $m_{ps123}$ | B1E0A7CE26202E223D4FC06D5C9BBA4E5F6D98204D2D5286 |
+| $m_{ps124}$ | DB506776958E34552F7E60E4B400D836153218F918E22FA6 |
+| $m_{ps125}$ | ECAA60300439B2360B2AC3C43FB6241ACDE5055B295FA71C |
+
+| Code ID | Basic Midamble Codes $m_{PS}$ of length $P=192$ |
+|-------------|--------------------------------------------------|
+| $m_{PS126}$ | BF1E6D9AA9CA4AC092BE60500C77D0DC7A6A236520F86722 |
+| $m_{PS127}$ | 051C5FA122845A30B4EC306B38016B45667C7754F92F13A0 |
+
+## A.3 Association between Midambles and Channelisation Codes
+
+The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. Secondary channelisation codes are marked with a \*. These associations apply both for UL and DL.
+
+### A.3.1 Association for Burst Type 1/3 and $K_{Cell}=16$ Midambles
+
+
+
+A hierarchical tree diagram showing the association of 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^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. m^{(1)} - c\_4^{(1)} branches into m^{(1)} - c\_8^{(1)} and m^{(2)} - c\_8^{(2)}. m^{(3)} - c\_4^{(2)} branches into m^{(3)} - c\_8^{(3)} and m^{(6)} - c\_8^{(4)}. m^{(5)} - c\_4^{(3)} branches into m^{(5)} - c\_8^{(5)} and m^{(4)} - c\_8^{(6)}. m^{(7)} - c\_4^{(4)} branches into m^{(7)} - c\_8^{(7)} and m^{(8)} - c\_8^{(8)}. Finally, each of the eight m^{(i)} - c\_8^{(j)} nodes branches into two leaf nodes, resulting in 16 leaf nodes labeled m^{(1)} - c\_{16}^{(1)}, m^{(9)} - c\_{16}^{(2)}, m^{(2)} - c\_{16}^{(3)}, m^{(10)} - c\_{16}^{(4)}, m^{(3)} - c\_{16}^{(5)}, m^{(11)} - c\_{16}^{(6)}, m^{(6)} - c\_{16}^{(7)}, m^{(14)} - c\_{16}^{(8)}, m^{(5)} - c\_{16}^{(9)}, m^{(13)} - c\_{16}^{(10)}, m^{(4)} - c\_{16}^{(11)}, m^{(12)} - c\_{16}^{(12)}, m^{(7)} - c\_{16}^{(13)}, m^{(15)} - c\_{16}^{(14)}, m^{(8)} - c\_{16}^{(15)}, and m^{(16)} - c\_{16}^{(16)}.
+
+Figure A.1: Association of Midambles to Spreading Codes for Burst Type 1/3 and $K_{Cell}=16$
+
+### A.3.2 Association for Burst Type 1/3 and $K_{\text{Cell}}=8$ Midambles
+
+
+
+Figure A.2: Association of Midambles to Spreading Codes for Burst Type 1/3 and K\_Cell=8. A tree diagram starting from m^{(1)} - c\_1^{(1)} and branching out to 16 spreading codes c\_{16}^{(1)} to c\_{16}^{(16)} with midambles m^{(1)} to m^{(8)} assigned to various levels of the hierarchy.
+
+Figure A.2: Association of Midambles to Spreading Codes for Burst Type 1/3 and $K_{\text{Cell}}=8$
+
+### A.3.3 Association for Burst Type 1/3 and $K_{\text{Cell}}=4$ Midambles
+
+
+
+Figure A.3: Association of Midambles to Spreading Codes for Burst Type 1/3 and K\_Cell=4. A tree diagram starting from m^{(1)} - c\_1^{(1)} and branching out to 16 spreading codes c\_{16}^{(1)} to c\_{16}^{(16)} with midambles m^{(1)}, m^{(3)}, m^{(5)}, and m^{(7)} assigned to various levels of the hierarchy.
+
+Figure A.3: Association of Midambles to Spreading Codes for Burst Type 1/3 and $K_{\text{Cell}}=4$
+
+### A.3.4 Association for Burst Type 2 and $K_{\text{Cell}}=6$ Midambles
+
+
+
+```
+
+graph LR
+ A["m(1) - c1(1)"] --> B1["m(1) - c2(1)"]
+ A --> B2["m(2) - c2(2)"]
+
+ B1 --> C1["m(1) - c4(1)"]
+ B1 --> C2["m(3) - c4(2)"]
+
+ C1 --> D1["m(1) - c8(1)"]
+ C1 --> D2["m(5) - c8(2)"]
+
+ D1 --> E1["m(1) - c16(1)"]
+ D1 --> E2["m(1) - c16(2)*"]
+ D2 --> E3["m(5) - c16(3)"]
+ D2 --> E4["m(5) - c16(4)*"]
+
+ C2 --> D3["m(3) - c8(3)"]
+ C2 --> D4["m(3) - c8(4)*"]
+
+ D3 --> E5["m(3) - c16(5)"]
+ D3 --> E6["m(3) - c16(6)*"]
+ D4 --> E7["m(3) - c16(7)*"]
+ D4 --> E8["m(3) - c16(8)*"]
+
+ B2 --> C3["m(2) - c4(3)"]
+ B2 --> C4["m(4) - c4(4)"]
+
+ C3 --> D5["m(2) - c8(5)"]
+ C3 --> D6["m(6) - c8(6)"]
+
+ D5 --> E9["m(2) - c16(9)"]
+ D5 --> E10["m(2) - c16(10)*"]
+ D6 --> E11["m(6) - c16(11)"]
+ D6 --> E12["m(6) - c16(12)*"]
+
+ C4 --> D7["m(4) - c8(7)"]
+ C4 --> D8["m(4) - c8(8)*"]
+
+ D7 --> E13["m(4) - c16(13)"]
+ D7 --> E14["m(4) - c16(14)*"]
+ D8 --> E15["m(4) - c16(15)*"]
+ D8 --> E16["m(4) - c16(16)*"]
+
+```
+
+Figure A.4: Association of Midambles to Spreading Codes for Burst Type 2 and $K_{\text{Cell}}=6$
+
+### A.3.5 Association for Burst Type 2 and $K_{\text{Cell}}=3$ Midambles
+
+
+
+```
+
+graph LR
+ A["m(1) - c1(1)"] --> B1["m(1) - c2(1)"]
+ A --> B2["m(2) - c2(2)"]
+
+ B1 --> C1["m(1) - c4(1)"]
+ B1 --> C2["m(3) - c4(2)"]
+
+ C1 --> D1["m(1) - c8(1)"]
+ C1 --> D2["m(1) - c8(2)*"]
+
+ D1 --> E1["m(1) - c16(1)"]
+ D1 --> E2["m(1) - c16(2)*"]
+ D2 --> E3["m(1) - c16(3)*"]
+ D2 --> E4["m(1) - c16(4)*"]
+
+ C2 --> D3["m(3) - c8(3)"]
+ C2 --> D4["m(3) - c8(4)*"]
+
+ D3 --> E5["m(3) - c16(5)"]
+ D3 --> E6["m(3) - c16(6)*"]
+ D4 --> E7["m(3) - c16(7)*"]
+ D4 --> E8["m(3) - c16(8)*"]
+
+ B2 --> C3["m(2) - c4(3)"]
+ B2 --> C4["m(2) - c4(4)*"]
+
+ C3 --> D5["m(2) - c8(5)"]
+ C3 --> D6["m(2) - c8(6)*"]
+
+ D5 --> E9["m(2) - c16(9)"]
+ D5 --> E10["m(2) - c16(10)*"]
+ D6 --> E11["m(2) - c16(11)*"]
+ D6 --> E12["m(2) - c16(12)*"]
+
+ C4 --> D7["m(2) - c8(7)*"]
+ C4 --> D8["m(2) - c8(8)*"]
+
+ D7 --> E13["m(2) - c16(13)*"]
+ D7 --> E14["m(2) - c16(14)*"]
+ D8 --> E15["m(2) - c16(15)*"]
+ D8 --> E16["m(2) - c16(16)*"]
+
+```
+
+Figure A.5: Association of Midambles to Spreading Codes for Burst Type 2 and $K_{\text{Cell}}=3$
+
+Note that the association for burst type 2 can be derived from the association for burst type 1 and 3, using the following table:
+
+| | | | | | | | | |
+|----------------|------|------|------|------|------|------|------|------|
+| Burst Type 1/3 | m(1) | m(2) | m(3) | m(4) | m(5) | m(6) | m(7) | m(8) |
+| Burst Type 2 | m(1) | m(5) | m(3) | m(6) | m(2) | m(4) | - | - |
+
+### A.3.6 Association for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble
+
+For burst type 4 there is only a single midamble defined, thus all channelisation codes are associated with the same midamble.
+
+# --- Annex AA (normative): Basic Midamble Codes for the 1.28 Mcps option
+
+## AA.1 Basic Midamble Codes
+
+The midamble has a length of $L_m=144$ , which is corresponding to:
+
+$$K=2, 4, 6, 8, 10, 12, 14, 16, \quad W = \left\lfloor \frac{P}{K} \right\rfloor, P=128$$
+
+Note: that $\lfloor x \rfloor$ denotes the largest integer number less or equal to $x$ .
+
+Depending on the possible delay spread timeslots are configured to use $K$ midambles. In timeslot 0 the number of midambles $K=8$ (cf section 6.6.1). In all of the other timeslots, $K$ is individually configured from higher layers.
+
+The $K$ midambles are generated from one of the basic midamble codes shown in table AA.1.
+
+The mapping of these Basic Midamble Codes to Cell Parameters is shown in [8].
+
+**Table AA.1: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5A.2.3**
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=128$ |
+|-----------|----------------------------------------------|
+| $m_{P0}$ | B2AC420F7C8DEBFA69505981BCD028C3 |
+| $m_{P1}$ | 0C2E988E0DBA046643F57B0EA6A435E2 |
+| $m_{P2}$ | D5CEC680C36A4454135F86DD37043962 |
+| $m_{P3}$ | E150D08CAC2A00FF9B32592A631CF85B |
+| $m_{P4}$ | E0A9C3A8F6E40329B2F2943246003D44 |
+| $m_{P5}$ | FE22658100A3A683EA759018739BD690 |
+| $m_{P6}$ | B46062F89BB2A1139D76A1EF32450DA0 |
+| $m_{P7}$ | EE63D75CC099092579400D956A90C3E0 |
+| $m_{P8}$ | D9C0E040756D427A2611DAA35E6CD614 |
+| $m_{P9}$ | EB56D03A498EC4FEC98AE220BC390450 |
+| $m_{P10}$ | F598703DB0838112ED0BABB98642B665 |
+| $m_{P11}$ | A0BC26A992D4558B9918986C14861EFF |
+| $m_{P12}$ | 541350D109F1DD68099796637B824F88 |
+| $m_{P13}$ | 892D344A962314662F01F9455F7BC302 |
+| $m_{P14}$ | 49F270E29CCD742A40480DD4215E1632 |
+| $m_{P15}$ | 6A5C0410C6C39AA04E77423C355926DE |
+| $m_{P16}$ | 7976615538203103D4DBCC219B16A9E1 |
+| $m_{P17}$ | A6C3C3175845400BD2B738C43EE2645F |
+| $m_{P18}$ | A0FD56258D228642C6F641851C3751ED |
+| $m_{P19}$ | EFA48C3FC84AC625783C6C9510A2269A |
+| $m_{P20}$ | 62A8EB1A420334B23396E8D76BC19740 |
+| $m_{P21}$ | 9E96235699D5D41C9816C921023BC741 |
+| $m_{P22}$ | 4362AE4CAE0DCC32D60A3FED1341A848 |
+| $m_{P23}$ | 454C068E6C4F190942E0904B95D61DFB |
+| $m_{P24}$ | 607FEEA6E2E99206718A49C0D6A25034 |
+| $m_{P25}$ | E1D1BCDA39A09095B5C81645103A077C |
+| $m_{P26}$ | 994B445E558344DE211C8286DDD3D1A3 |
+| $m_{P27}$ | C15233273581417638906ADB61FDCA3C |
+| $m_{P28}$ | 8B79A274D542F096FB1388098230F8A1 |
+| $m_{P29}$ | DF58AC1C5F44B2A40266385CE1DA5640 |
+| $m_{P30}$ | B5949A1CC69962C464401D05FF5C1A7A |
+| $m_{P31}$ | 85AC489841ED3EAA2D83BBB0039CC707 |
+| $m_{P32}$ | AE371CC144BC95923CA8108D8B49FE82 |
+| $m_{P33}$ | 7F188484A649D1C22BDA1F09D49B5117 |
+| $m_{P34}$ | ADAA3C657089DEF7C0284903A491C9B0 |
+| $m_{P35}$ | C3F96893C7504DC3B51488604AF64F4C |
+| $m_{P36}$ | B4002F5AE0CE8623AC979D368E9148C1 |
+| $m_{P37}$ | 0EEBCC0C795C02A106C24ABB36D08C6E |
+| $m_{P38}$ | 4B0F537E384A893F58971580D9894433 |
+| $m_{P39}$ | 08E0035AB29B7ECC53C15DAA0687CC8F |
+| $m_{P40}$ | 8611ACBC4C82781D77654EE862506D60 |
+| $m_{P41}$ | 63315261A8F1CB02549802DBFD197C07 |
+| $m_{P42}$ | 9A2609A434F43E7DCADC0E22B2EF4012 |
+| $m_{P43}$ | F4C9F0A127A88461209ABF8C69CE4D00 |
+| $m_{P44}$ | C79124EE3FFC28C5C4524D2B01670D42 |
+| $m_{P45}$ | C91985C4FED53D09361914354BA80E79 |
+| $m_{P46}$ | 82AA517260779ECFF26212C1A10BDC29 |
+| $m_{P47}$ | 561DE2040ACB458E0DBD354E43E111D9 |
+| $m_{P48}$ | 2E58C7202D17392BC1235782CEFABB09 |
+| $m_{P49}$ | C4FAA121C698047650F6503126A577C1 |
+| $m_{P50}$ | E7B75206A9B410E44346E0DAE842A23C |
+| $m_{P51}$ | 3F8B1C32682B28D098D3805ED130EA7F |
+| $m_{P52}$ | 8D5FC2C1C6715F824B401434C8D4BB82 |
+| $m_{P53}$ | 0B2A43453ACC028FE6EB6E1CB0740B59 |
+| $m_{P54}$ | BC56948FC700BA4883262EE73E12D82A |
+| $m_{P55}$ | 558D136710272912FA4F183D1189A7FD |
+| $m_{P56}$ | 5709E7F82DC6500B7B12A3072D182645 |
+| $m_{P57}$ | 86D4F161C844AE5E20EE39FD5493B044 |
+| $m_{P58}$ | 8729B6EDC382B152185885F013DAE222 |
+| $m_{P59}$ | 154C45B50720F4C362C14C77FE8335A1 |
+| $m_{P60}$ | C6A0962890351F4EB802DE43A7662C9E |
+| $m_{P61}$ | D19D69D6B380B4B22457CB80033519F0 |
+| $m_{P62}$ | C7D89509FB0DAE9255998E0A00C2B262 |
+
+| | |
+|-------------------|----------------------------------|
+| m P63 | DFD481C652C0C905D61D66F1732C4AA2 |
+| m P64 | 06C848619AF1D6C910A8EAC4B622FC06 |
+| m P65 | 0635E29D4E7AC8ABC189890241F45ECA |
+| m P66 | B272B020586AAD7B093AC2F459076638 |
+| m P67 | B608ACE46E1A6BC96181EEDD88B54140 |
+| m P68 | 0A516092B3ED7849B168AFE223B8670E |
+| m P69 | D1A658C5009E04D0D7D5E9205EE663E8 |
+| m P70 | AC316DC39B91EB60B1AABD8280740432 |
+| m P71 | E3F06825476A026CD287625E514519FC |
+| m P72 | A56D092080DDE8994F387C175CC56833 |
+| m P73 | 15EA799DE587C506D0CD99A408217B05 |
+| m P74 | A59C020BAB9AF6D3F813C391CA244CD2 |
+| m P75 | 74B0101EB9F3167434B94BABC8378882 |
+| m P76 | CE752975C8DA9B0100386DB82A8C3D20 |
+| m P77 | BBB38DCDB1E9118570AC147DC05241A4 |
+| m P78 | 944ABBF0866098101F6971731AB2E986 |
+| m P79 | 2BB147B2A30C68B4853F90481A166EB6 |
+| m P80 | 444840ACCF3F23C45B56D7704BF18283 |
+| m P81 | 87604F7450D1AD188C452981A5C7FC9B |
+| m P82 | 8C3842EBC948A65BC4C8B387F11B7090 |
+| m P83 | 10B4767D071CF5DB2288E4029576135A |
+| m P84 | 6F07AAB697CD0089572C6B062E2018E4 |
+| m P85 | D3D65B442057E613A8655060C8D29E27 |
+| m P86 | 5EDA330514C604BF4E0894E09EC57A74 |
+| m P87 | B0899CD094060724DED82AE85F18A43A |
+| m P88 | B2D999B86DF902BC25015CAE3A0823C4 |
+| m P89 | C23CD40F04242B92D46EED82CD9A9A18 |
+| m P90 | D22DDCC5CB82960125DD24655F3C8788 |
+| m P91 | 54987218FBD99AE4340FD4C9458E9850 |
+| m P92 | BE4341822997A7B11EA1E8A1A2767005 |
+| m P93 | 255200FBA6EE48E6DE0A82B0461B8D0F |
+| m P94 | 6FBD58A663932423503690CF9C171701 |
+| m P95 | D215033A4AA87EC1C232BAC7EDA09370 |
+| m P96 | CA0959B01AE48E80204F1E4A3F29CE55 |
+| m P97 | 582043413B9B825903E3A3545ED59463 |
+| m P98 | 5016541922971C703D16E284CBDF633B |
+| m P99 | 7347EF160A1733CA98D43608A83A920B |
+| m P100 | 908B22AD433CCA00B3FD47C691F1A290 |
+| m P101 | BB22A272FC6923DF1B43BA4118806570 |
+| m P102 | 0FA75C87474836B47DC7624D61193802 |
+| m P103 | A22EBA0658A4D0FF1E9CA5030A65CC06 |
+| m P104 | 6C9C51CA15F1F4981F4C46180A6A6697 |
+| m P105 | 4C847ACF8BC15359C405322851C9BDE2 |
+| m P106 | C1D29499C0082C9DE473ED15B14D63E0 |
+| m P107 | 7E85ECC98AC761005076C5572869A431 |
+| m P108 | D8F11121595B8F49F78A7039E44126A0 |
+| m P109 | 1A0BC814445FD71C8E5B1A9163ED2059 |
+| m P110 | A7591F27F8B0C00C68CC41697954FA04 |
+| m P111 | 6CA2CE595E7406D79C4840183D41B9D0 |
+| m P112 | C093D3CC701FC20E66F5AB22516C5460 |
+| m P113 | D0E0CDE9B595546B96C4F8066B469020 |
+| m P114 | E99F743A451431C8B427054A4E6F2007 |
+| m P115 | C0D21A344A2C07DF2A6EBE6250C7B91E |
+| m P116 | F031223E282CF7A4D8EF174A908668AE |
+| m P117 | E4BD244AC16C55C7137FB068FD44280C |
+| m P118 | C44920DE2028F19FC2AAB36A0DCFDAD0 |
+| m P119 | 3FA7054E77135250699E6C8A11600742 |
+| m P120 | D5740B4D8870C1C5B5A214C4266FC537 |
+| m P121 | F0B7942D43BB6F38446442EB8126AB80 |
+| m P122 | 83DB9534EAD6238FA8968798CDF04848 |
+| m P123 | EB9663CDDC2B291690703125BABCB800 |
+| m P124 | 84D547225D4BBD20DEF1A583240C6E0F |
+| m P125 | B51F6A771838BE934724AE6A2669802 |
+| m P126 | D92AC05E10496794BBD115233B1C068 |
+
+| | |
+|-------------------|----------------------------------|
+| m P127 | D3ACF0078EDA9856BBB0AF8651132103 |
+|-------------------|----------------------------------|
+
+###### **Table AA.1a: Basic Preamble Codes**
+
+| Code ID | Basic Preamble Codes of length P=64 |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $p_{P0}$ | 1.000000+j0.000000, 0.989177+j0.146730, 0.923880+j0.382683, 0.740951+j0.671559, 0.382683+j0.923880, -0.146730+j0.989177, -0.707107+j0.707107, -0.998795+j0.049068, -0.707107-j0.707107, 0.146731-j0.989176, 0.923880-j0.382683, 0.740951+j0.671559, -0.382684+j0.923879, -0.989176-j0.146731, 0.000000-j1.000000, 0.998795-j0.049067, 0.000000+j1.000000, -0.989176-j0.146731, 0.382684-j0.923879, 0.740951+j0.671559, -0.923880+j0.382683, 0.146731-j0.989176, 0.707107+j0.707107, -0.998795+j0.049067, 0.707107-j0.707106, -0.146731+j0.989176, -0.382683-j0.923880, 0.740951+j0.671559, -0.923879-j0.382684, 0.989176+j0.146731, -1.000000-j0.000001, 0.998795-j0.049067, -1.000000-j0.000001, 0.989176+j0.146731, -0.923879-j0.382684, 0.740950+j0.671560, -0.382683-j0.923880, -0.146732+j0.989176, 0.707108-j0.707106, -0.998796+j0.049067, 0.707106+j0.707108, 0.146732-j0.989176, -0.923880+j0.382682, 0.740950+j0.671560, 0.382685-j0.923879, -0.989176-j0.146732, -0.000002+j1.000000, 0.998796-j0.049066, 0.000002-j1.000000, -0.989176-j0.146732, -0.382685+j0.923879, 0.740950+j0.671560, 0.923880-j0.382682, 0.146733-j0.989176, -0.707105-j0.707108, -0.998796+j0.049065, -0.707108+j0.707105, -0.146733+j0.989176, 0.382681+j0.923880, 0.740949+j0.671561, 0.923879+j0.382686, 0.989176+j0.146733, 1.000000+j0.000003, 0.998796-j0.049065 |
+| $p_{P1}$ | 1.000000+j0.000000, 0.903989+j0.427555, 0.382683+j0.923880, -0.595699+j0.803208, -0.923880-j0.382683, 0.427555-j0.903989, 0.707107+j0.707107, -0.989177+j0.146730, 0.707107-j0.707107, -0.427555+j0.903989, 0.382684-j0.923879, -0.595700+j0.803207, 0.923880-j0.382683, -0.903989-j0.427555, 0.000001-j1.000000, -0.903989-j0.427556, -0.923880+j0.382683, -0.595700+j0.803207, -0.382684+j0.923879, -0.427556+j0.903989, -0.707108+j0.707106, -0.989177+j0.146729, -0.707106-j0.707108, 0.427556-j0.903989, 0.923879+j0.382685, -0.595701+j0.803207, -0.382682-j0.923880, 0.903988+j0.427557, -1.000000-j0.000002, 0.989177-j0.146728, -1.000000-j0.000002, 0.903988+j0.427557, -0.382681-j0.923881, -0.595702+j0.803206, 0.923878+j0.382686, 0.427558-j0.903988, -0.707104-j0.707109, -0.989177+j0.146727, -0.707109+j0.707104, -0.427559+j0.903988, -0.382687+j0.923878, -0.595703+j0.803205, -0.923881+j0.382679, -0.903987-j0.427559, 0.000005-j1.000000, 0.989177-j0.146726, -0.000005+j1.000000, -0.903987-j0.427560, 0.923882-j0.382678, -0.595704+j0.803204, 0.382689-j0.923877, -0.427561+j0.903987, 0.707111-j0.707102, -0.989178+j0.146724, 0.707102+j0.707112, 0.427562-j0.903986, -0.923877-j0.382690, -0.595706+j0.803203, 0.382676+j0.923883, 0.903986+j0.427563, 1.000000+j0.000009, 0.989178-j0.146722 |
+| $p_{P2}$ | 1.000000+j0.000000, 0.740951+j0.671559, -0.382683+j0.923880, -0.857729-j0.514103, 0.923880-j0.382683, -0.671559+j0.740951, 0.707107-j0.707107, -0.970031+j0.242980, 0.707107+j0.707107, 0.671559-j0.740951, -0.382683-j0.923880, -0.857728-j0.514103, -0.923879-j0.382684, -0.740951-j0.671559, 0.000001-j1.000000, 0.970031-j0.242979, -0.000001+j1.000000, -0.740950-j0.671560, 0.923879+j0.382685, -0.857728-j0.514104, 0.382682+j0.923880, 0.671560-j0.740950, -0.707105-j0.707108, -0.970032+j0.242978, -0.707108+j0.707105, -0.671561+j0.740949, -0.923881+j0.382681, -0.857727-j0.514105, 0.382686-j0.923878, 0.740949+j0.671561, -1.000000-j0.000003, 0.970032-j0.242977, -1.000000-j0.000004, 0.740948+j0.671562, 0.382688-j0.923878, -0.857726-j0.514107, -0.923881+j0.382679, -0.671563+j0.740948, -0.707111+j0.707103, -0.970033+j0.242975, -0.707102-j0.707111, 0.671564-j0.740947, 0.382677+j0.923882, -0.857725-j0.514109, 0.923877+j0.382690, -0.740946-j0.671565, -0.000008+j1.000000, 0.970033-j0.242972, 0.000009-j1.000000, -0.740945-j0.671566, -0.923876-j0.382692, -0.857724-j0.514111, -0.382674-j0.923883, 0.671567-j0.740944, 0.707099+j0.707115, -0.970034+j0.242969, 0.707115-j0.707098, -0.671568+j0.740943, 0.923884-j0.382672, -0.857722-j0.514114, -0.382696+j0.923874, 0.740942+j0.671569, 1.000000+j0.000014, 0.970035-j0.242966 |
+| $p_{P3}$ | 1.000000+j0.000000, 0.514103+j0.857729, -0.923880+j0.382683, 0.427555-j0.903989, -0.382684+j0.923879, 0.857729-j0.514103, -0.707107-j0.707107, -0.941544+j0.336890, -0.707107+j0.707106, -0.857729+j0.514102, -0.923879-j0.382684, 0.427556-j0.903989, 0.382683+j0.923880, -0.514102-j0.857729, -0.000001+j1.000000, 0.941545-j0.336889, 0.000001-j1.000000, -0.514101-j0.857729, -0.382682-j0.923880, 0.427557-j0.903988, 0.923879+j0.382685, -0.857730+j0.514101, 0.707109-j0.707105, -0.941545+j0.336887, 0.707105+j0.707109, 0.857730-j0.514100, 0.382687-j0.923878, 0.427559-j0.903988, 0.923881-j0.382679, 0.514099+j0.857731, -1.000000-j0.000005, 0.941546-j0.336885, -1.000000-j0.000006, 0.514098+j0.857732, 0.923882-j0.382678, 0.427561-j0.903986, 0.382690-j0.923877, 0.857732-j0.514096, 0.707101+j0.707112, -0.941547+j0.336882, 0.707113-j0.707101, -0.857733+j0.514095, 0.923876+j0.382692, 0.427564-j0.903985, -0.382674-j0.923883, -0.514094-j0.857734, 0.000011-j1.000000, 0.941548-j0.336879, -0.000012+j1.000000, -0.514092-j0.857735, 0.382671+j0.923885, 0.427567-j0.903983, -0.923874-j0.382697, -0.857736+j0.514090, -0.707118+j0.707096, -0.941549+j0.336875, -0.707095-j0.707118, 0.857737-j0.514088, -0.382700+j0.923873, 0.427572-j0.903981, -0.923887+j0.382666, 0.514086+j0.857739, 1.000000+j0.000020, 0.941551-j0.336870 |
+| $p_{P4}$ | 1.000000+j0.000000, 0.242980+j0.970031, -0.923880-j0.382683, 0.941544+j0.336890, -0.382683-j0.923880, -0.970031+j0.242980, -0.707107+j0.707107, -0.903989+j0.427555, -0.707106-j0.707107, 0.970031-j0.242980, -0.923880+j0.382683, 0.941544+j0.336891, 0.382684-j0.923879, -0.242979-j0.970032, 0.000001-j1.000000, 0.903990-j0.427554, -0.000002+j1.000000, -0.242978-j0.970032, -0.382686+j0.923879, 0.941543+j0.336892, 0.923881-j0.382681, 0.970032-j0.242977, |
+
+| |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0.707104+j0.707109, -0.903991+j0.427552, 0.707110-j0.707104, -0.970032+j0.242976,
0.382679+j0.923881, 0.941542+j0.336895, 0.923877+j0.382688, 0.242974+j0.970033, -1.000000-
j0.000006, 0.903992-j0.427549, -1.000000-j0.000007, 0.242973+j0.970033, 0.923876+j0.382691,
0.941541+j0.336898, 0.382675+j0.923883, -0.970034+j0.242971, 0.707114-j0.707100,
-0.903994+j0.427546, 0.707099+j0.707115, 0.970034-j0.242969, 0.923884-j0.382672,
0.941540+j0.336902, -0.382696+j0.923874, -0.242967-j0.970035, -0.000014+j1.000000, 0.903996-
j0.427542, 0.000016-j1.000000, -0.242964-j0.970035, 0.382699-j0.923873, 0.941538+j0.336906,
-0.923887+j0.382667, 0.970036-j0.242962, -0.707093-j0.707121, -0.903998+j0.427537,
-0.707122+j0.707092, -0.970037+j0.242959, -0.382662-j0.923888, 0.941536+j0.336912, -0.923870-
j0.382706, 0.242956+j0.970037, 1.000000+j0.000026, 0.904001-j0.427531 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $p_{P5}$ | 1.000000+j0.000000, -0.049068+j0.998795, -0.382683-j0.923880, -0.242980+j0.970031, 0.923879+j0.382684, 0.998795+j0.049068, 0.707107+j0.707107, -0.857729+j0.514102, 0.707107-j0.707106, -0.998795-j0.049068, -0.382684+j0.923879, -0.242981+j0.970031, -0.923880+j0.382682, 0.049069-j0.998795, -0.000002+j1.000000, 0.857730-j0.514101, 0.000002-j1.000000, 0.049070-j0.998795, 0.923881-j0.382681, -0.242983+j0.970030, 0.382687-j0.923878, -0.998795-j0.049072, -0.707110+j0.707104, -0.857731+j0.514099, -0.707103-j0.707110, 0.998795+j0.049073, -0.923877-j0.382689, -0.242986+j0.970030, 0.382677+j0.923882, -0.049075+j0.998795, -1.000000-j0.000008, 0.857733-j0.514096, -1.000000-j0.000009, -0.049077+j0.998795, 0.382674+j0.923883, -0.242990+j0.970029, -0.923875-j0.382694, 0.998795+j0.049079, -0.707098-j0.707115, -0.857735+j0.514092, -0.707116+j0.707097, -0.998795-j0.049082, 0.382697-j0.923874, -0.242995+j0.970028, 0.923886-j0.382669, 0.049085-j0.998795, 0.000018-j1.000000, 0.857738-j0.514087, -0.000019+j1.000000, 0.049088-j0.998794, -0.923887+j0.382664, -0.243001+j0.970026, -0.382704+j0.923871, -0.998794-j0.049091, 0.707124-j0.707090, -0.857741+j0.514081, 0.707088+j0.707125, 0.998794+j0.049094, 0.923869+j0.382709, -0.243008+j0.970024, -0.382656-j0.923891, -0.049098+j0.998794, 1.000000+j0.000032, 0.857745-j0.514075 |
+| $p_{P6}$ | 1.000000+j0.000000, -0.336890+j0.941544, 0.382684-j0.923880, -0.989176-j0.146731, -0.923880+j0.382683, -0.941544-j0.336890, 0.707107-j0.707106, -0.803208+j0.595699, 0.707106+j0.707107, 0.941544+j0.336891, 0.382682+j0.923880, -0.989176-j0.146732, 0.923879+j0.382685, 0.336892-j0.941543, 0.000002-j1.000000, 0.803209-j0.595697, -0.000003+j1.000000, 0.336893-j0.941543, -0.923878-j0.382687, -0.989176-j0.146734, -0.382680-j0.923881, 0.941543+j0.336894, -0.707103-j0.707110, -0.803211+j0.595695, -0.707111+j0.707103, -0.941542-j0.336896, 0.923882-j0.382677, -0.989175-j0.146738, -0.382691+j0.923877, -0.336898+j0.941541, -1.000000-j0.000009, 0.803213-j0.595692, -1.000000-j0.000010, -0.336900+j0.941540, -0.382694+j0.923875, -0.989175-j0.146743, 0.923884-j0.382672, -0.941539-j0.336903, -0.707117+j0.707097, -0.803217+j0.595687, -0.707096-j0.707118, 0.941538+j0.336906, -0.382667-j0.923886, -0.989174-j0.146749, -0.923872-j0.382701, 0.336909-j0.941537, -0.000021+j1.000000, 0.803220-j0.595682, 0.000023-j1.000000, 0.336912-j0.941536, 0.923870+j0.382706, -0.989173-j0.146756, 0.382659+j0.923890, 0.941535+j0.336916, 0.707087+j0.707127, -0.803225+j0.595676, 0.707128-j0.707085, -0.941533-j0.336920, -0.923892+j0.382653, -0.989172-j0.146764, 0.382716-j0.923866, -0.336924+j0.941532, 1.000000+j0.000037, 0.803231-j0.595668 |
+| $p_{P7}$ | 1.000000+j0.000000, -0.595699+j0.803208, 0.923880-j0.382683, 0.049068-j0.998795, 0.382684-j0.923879, 0.803207+j0.595700, -0.707106-j0.707107, -0.740952+j0.671558, -0.707107+j0.707106, 0.803207-j0.595712, 0.923879+j0.382685, -0.049069-j0.998795, -0.382682-j0.923880, 0.595701-j0.803206, -0.000002+j1.000000, 0.740953-j0.671557, 0.000003-j1.000000, 0.595702-j0.803205, 0.382680+j0.923881, 0.049072-j0.998795, -0.923878-j0.382688, -0.803204-j0.595704, 0.707111-j0.707103, -0.740955+j0.671554, 0.707102+j0.707112, 0.803203+j0.595705, -0.382691+j0.923877, 0.049076-j0.998795, -0.923883+j0.382675, -0.595707+j0.803202, -1.000000-j0.000010, 0.740959-j0.671551, -1.000000-j0.000012, -0.595709+j0.803200, -0.923885+j0.382671, 0.049082-j0.998795, -0.382697+j0.923874, 0.803198+j0.595712, 0.707095+j0.707118, -0.740963+j0.671546, 0.707120-j0.707094, -0.803196-j0.595715, -0.923872-j0.382702, 0.049089-j0.998794, 0.382663+j0.923888, 0.595718-j0.803194, 0.000024-j1.000000, 0.740968-j0.671540, -0.000026+j1.000000, 0.595721-j0.803191, -0.382657-j0.923890, 0.049097-j0.998794, 0.923868+j0.382712, -0.803189-j0.595725, -0.707130+j0.707084, -0.740974+j0.671534, -0.707082-j0.707132, 0.803186+j0.595729, 0.382718-j0.923865, 0.049107-j0.998794, 0.923895-j0.382646, -0.595733+j0.803183, 1.000000+j0.000043, 0.740981-j0.671526 |
+| $p_{P8}$ | 1.000000+j0.000000, -0.803208+j0.595699, 0.923879+j0.382684, 0.998795-j0.049067, 0.382683+j0.923880, -0.595699-j0.803208, -0.707107+j0.707106, -0.671560+j0.740951, -0.707106-j0.707107, 0.595698+j0.803208, 0.923880-j0.382682, 0.998796-j0.049066, -0.382685+j0.923879, 0.803209-j0.595697, 0.000003-j1.000000, 0.671561-j0.740949, -0.000004+j1.000000, 0.803210-j0.595696, 0.382688-j0.923878, 0.998796-j0.049063, -0.923882+j0.382678, 0.595695+j0.803211, 0.707102+j0.707111, -0.671564+j0.740946, 0.707112-j0.707101, -0.595693-j0.803212, -0.382675-j0.923883, 0.998796-j0.049058, -0.923876-j0.382693, -0.803214+j0.595690, -1.000000-j0.000012, 0.671568-j0.740943, -1.000000-j0.000013, -0.803216+j0.595688, -0.923874-j0.382697, 0.998796-j0.049052, -0.382668-j0.923886, -0.595685-j0.803218, 0.707120-j0.707094, -0.671574+j0.740938, 0.707092+j0.707121, 0.595682+j0.803220, -0.923888+j0.382662, 0.998797-j0.049044, 0.382706-j0.923870, 0.803223-j0.595678, -0.000027+j1.000000, 0.671580-j0.740932, 0.000030-j1.000000, 0.803226-j0.595675, -0.382713+j0.923867, 0.998797-j0.049034, 0.923893-j0.382651, 0.595670+j0.803229, -0.707080-j0.707133, -0.671588+j0.740925, -0.707135+j0.707078, -0.595666-j0.803232, 0.382644+j0.923896, 0.998798-j0.049023, 0.923862+j0.382726, -0.803236+j0.595661, 1.000000+j0.000049, 0.671596-j0.740917 |
+| $p_{P9}$ | 1.000000+j0.000000, -0.941544+j0.336890, 0.382683+j0.923880, 0.146730+j0.989177, -0.923879-j0.382684, 0.336889+j0.941544, 0.707106+j0.707107, -0.595700+j0.803207, 0.707108-j0.707106, -0.336889-j0.941545, 0.382685-j0.923879, 0.146729+j0.989177, 0.923880-j0.382681, 0.941545-j0.336887, -0.000003+j1.000000, 0.595702-j0.803205, 0.000004-j1.000000, 0.941546-j0.336886, -0.923881+j0.382679, 0.146725+j0.989177, |
+
+| |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| -0.382689+j0.923877, -0.336884-j0.941546, -0.707112+j0.707102, -0.595706+j0.803203, -0.707101-j0.707113, 0.336881+j0.941547, 0.923876+j0.382693, 0.146720+j0.989178, -0.382673-j0.923884, -0.941548+j0.336878, -1.000000-j0.000013, 0.595711-j0.803199, -1.000000-j0.000015, -0.941549+j0.336875, -0.382668-j0.923886, 0.146713+j0.989179, 0.923872+j0.382701, 0.336871+j0.941551, -0.707092-j0.707122, -0.595717+j0.803194, -0.707123+j0.707090, -0.336867-j0.941552, -0.382707+j0.923870, 0.146704+j0.989180, -0.923890+j0.382658, 0.941554-j0.336862, 0.000030-j1.000000, 0.595725-j0.803189, -0.000033+j1.000000, 0.941556-j0.336857, 0.923893-j0.382650, 0.146694+j0.989182, 0.382719-j0.923865, -0.336852-j0.941558, 0.707136-j0.707077, -0.595734+j0.803182, 0.707075+j0.707138, 0.336846+j0.941560, -0.923861-j0.382728, 0.146681+j0.989184, 0.382636+j0.923899, -0.941562+j0.336840, 1.000000+j0.000055, 0.595745-j0.803174
|
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $p_{P10}$ | 1.000000+j0.000000, -0.998795+j0.049068, -0.382684+j0.923879, -0.970031+j0.242980, 0.923880-j0.382683, -0.049067-j0.998795, 0.707107-j0.707106, -0.514104+j0.857728, 0.707106+j0.707108, 0.049066+j0.998796, -0.382682-j0.923880, -0.970032+j0.242978, -0.923879-j0.382686, 0.998796-j0.049065, 0.000003-j1.000000, 0.514106-j0.857727, -0.000004+j1.000000, 0.998796-j0.049063, 0.923877+j0.382688, -0.970033+j0.242974, 0.382677+j0.923882, 0.049060+j0.998796, -0.707101-j0.707112, -0.514110+j0.857724, -0.707114+j0.707100, -0.049057-j0.998796, -0.923884+j0.382673, -0.970034+j0.242969, 0.382695-j0.923875, -0.998796+j0.049054, -1.000000-j0.000015, 0.514116-j0.857721, -1.000000-j0.000017, -0.998796+j0.049050, 0.382701-j0.923872, -0.970036+j0.242961, -0.923888+j0.382664, -0.049046-j0.998797, -0.707123+j0.707090, -0.514124+j0.857716, -0.707089-j0.707125, 0.049041+j0.998797, 0.382657+j0.923890, -0.970038+j0.242952, 0.923868+j0.382712, 0.998797-j0.049036, -0.000034+j1.000000, 0.514133-j0.857711, 0.000037-j1.000000, 0.998797-j0.049030, -0.923864-j0.382720, -0.970041+j0.242940, -0.382644-j0.923896, 0.049023+j0.998798, 0.707074+j0.707139, -0.514144+j0.857704, 0.707142-j0.707072, -0.049017-j0.998798, 0.923900-j0.382634, -0.970045+j0.242927, -0.382736+j0.923858, -0.998798+j0.049009, 1.000000+j0.000060, 0.514156-j0.857697 |
+| $p_{P11}$ | 1.000000+j0.000000, -0.970031-j0.242980, -0.923880+j0.382683, -0.336890-j0.941544, -0.382684+j0.923879, -0.242981+j0.970031, -0.707106-j0.707107, -0.427556+j0.903989, -0.707108+j0.707106, 0.242982-j0.970031, -0.923879-j0.382685, -0.336888-j0.941545, 0.382681+j0.923881, 0.970030+j0.242983, -0.000004+j1.000000, 0.427559-j0.903987, 0.000005-j1.000000, 0.970030+j0.242985, -0.382678-j0.923882, -0.336884-j0.941546, 0.923877+j0.382690, 0.242988-j0.970029, 0.707113-j0.707101, -0.427564+j0.903985, 0.707099+j0.707114, -0.242991+j0.970029, 0.382695-j0.923875, -0.336878-j0.941548, 0.923885-j0.382670, -0.970028-j0.242995, -1.000000-j0.000016, 0.427571-j0.903982, -1.000000-j0.000018, -0.970027-j0.242999, 0.923887-j0.382665, -0.336870-j0.941551, 0.382705-j0.923871, -0.243004+j0.970025, 0.707089+j0.707125, -0.427579+j0.903978, 0.707127-j0.707087, 0.243009-j0.970024, 0.923868+j0.382712, -0.336859-j0.941555, -0.382652-j0.923892, 0.970023+j0.243014, 0.000037-j1.000000, 0.427590-j0.903973, -0.000040+j1.000000, 0.970021+j0.243021, 0.382643+j0.923896, -0.336847-j0.941559, -0.923862-j0.382727, 0.243027-j0.970019, -0.707142+j0.707071, -0.427602+j0.903967, -0.707068-j0.707145, -0.243035+j0.970018, -0.382737+j0.923857, -0.336833-j0.941564, -0.923903+j0.382626, -0.970016-j0.243042, 1.000000+j0.000066, 0.427617-j0.903960 |
+| $p_{P12}$ | 1.000000+j0.000000, -0.857729-j0.514103, -0.923879-j0.382684, 0.903989-j0.427555, -0.382683-j0.923880, 0.514103-j0.857728, -0.707107+j0.707106, -0.336891+j0.941544, -0.707106-j0.707108, -0.514104+j0.857728, -0.923880+j0.382681, 0.903990-j0.427553, 0.382686-j0.923878, 0.857727+j0.514106, 0.000004-j1.000000, 0.336894-j0.941543, -0.000005+j1.000000, 0.857726+j0.514136, -0.382689+j0.923877, 0.903992-j0.427549, 0.923883-j0.382676, -0.514110+j0.857724, 0.707100+j0.707114, -0.336900+j0.941541, 0.707115-j0.707099, 0.514113-j0.857722, 0.382671+j0.923885, 0.903995-j0.427542, 0.923874+j0.382698, -0.857720-j0.514117, -1.000000-j0.000017, 0.336907-j0.941538, -1.000000-j0.000020, -0.857718-j0.514121, 0.923871+j0.382704, 0.903999-j0.427534, 0.382661+j0.923889, 0.514125-j0.857715, 0.707126-j0.707087, -0.336917+j0.941534, 0.707085+j0.707128, -0.514130+j0.857712, 0.923892-j0.382652, 0.904004-j0.427523, -0.382717+j0.923865, 0.857709+j0.514138, -0.000040+j1.000000, 0.336929-j0.941530, 0.000044-j1.000000, 0.857705+j0.514142, 0.382727-j0.923861, 0.904010-j0.427511, -0.923899+j0.382636, -0.514148+j0.857701, -0.707068-j0.707146, -0.336943+j0.941525, -0.707148+j0.707065, 0.514155-j0.857697, -0.382625-j0.923904, 0.904017-j0.427496, -0.923854-j0.382746, -0.857693-j0.514163, 1.000000+j0.000072, 0.336960-j0.941519 |
+| $p_{P13}$ | 1.000000+j0.000000, -0.671559-j0.740951, -0.382683-j0.923880, 0.514102+j0.857729, 0.923879+j0.382684, -0.740952+j0.671558, 0.707106+j0.707107, -0.242981+j0.970031, 0.707108-j0.707106, 0.740952-j0.671558, -0.382686+j0.923879, 0.514100+j0.857730, -0.923881+j0.382680, 0.671556+j0.740954, -0.000004+j1.000000, 0.242985-j0.970030, 0.000006-j1.000000, 0.671554+j0.740955, 0.923882-j0.382677, 0.514096+j0.857733, 0.382691-j0.923876, 0.740957-j0.671552, -0.707114+j0.707099, -0.242991+j0.970029, -0.707098-j0.707115, -0.740960+j0.671549, -0.923874-j0.382697, 0.514090+j0.857736, 0.382668+j0.923886, -0.671546-j0.740963, -1.000000-j0.000019, 0.243000-j0.970026, -1.000000-j0.000021, -0.671542-j0.740966, 0.382661+j0.923889, 0.514081+j0.857742, -0.923869-j0.382708, -0.740970+j0.671538, -0.707086-j0.707128, -0.243011+j0.970024, -0.707130+j0.707084, 0.740974-j0.671533, 0.382717-j0.923866, 0.514070+j0.857748, 0.923895-j0.382647, 0.671528+j0.740979, 0.000043-j1.000000, 0.243024-j0.970020, -0.000047+j1.000000, 0.671523+j0.740984, -0.923899+j0.382636, 0.514057+j0.857756, -0.382734+j0.923858, 0.740989-j0.671517, 0.707149-j0.707065, -0.243040+j0.970016, 0.707062+j0.707152, -0.740995+j0.671510, 0.923853+j0.382746, 0.514042+j0.857765, -0.382616-j0.923907, -0.671503-j0.741002, 1.000000+j0.000078, 0.243058-j0.970012 |
+| $p_{P14}$ | 1.000000+j0.000000, -0.427555-j0.903989, 0.382684-j0.923879, -0.803208+j0.595699, -0.923880+j0.382683, 0.903990-j0.427554, 0.707107-j0.707106, -0.146732+j0.989176, 0.707106+j0.707108, -0.903990+j0.427553, 0.382681+j0.923880, -0.803209+j0.595697, 0.923878+j0.382687, 0.427551+j0.903991, 0.000005-j1.000000, 0.146736-j0.989176, -0.000006+j1.000000, 0.427549+j0.903992, -0.923877-j0.382690, -0.803213+j0.595693, -0.382675-j0.923883, -0.903994+j0.427546, -0.707099-j0.707115, -0.146742+j0.989175, -0.707116+j0.707098, |
+
+| |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0.903995-j0.427542, 0.923885-j0.382669, -0.803217+j0.595686, -0.382700+j0.923873, -0.427538-j0.903997, -1.000000-j0.000020, 0.146752-j0.989173, -1.000000-j0.000023, -0.427533-j0.904000, -0.382707+j0.923870, -0.803224+j0.595677, 0.923891-j0.382657, 0.904002-j0.427528, -0.707129+j0.707084, -0.146764+j0.989172, -0.707082-j0.707132, -0.904005+j0.427522, -0.382648-j0.923894, -0.803232+j0.595667, -0.923863-j0.382723, 0.427515+j0.904008, -0.000046+j1.000000, 0.146778-j0.989169, 0.000050-j1.000000, 0.427508+j0.904012, 0.923859+j0.382734, -0.803241+j0.595654, 0.382629+j0.923902, -0.904016+j0.427500, 0.707062+j0.707152, -0.146796+j0.989167, 0.707155-j0.707058, 0.904020-j0.427491, -0.923908+j0.382616, -0.803253+j0.595639, 0.382756-j0.923850, -0.427482-j0.904024, 1.000000+j0.000083, 0.146816-j0.989164 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| P P15 | 1.000000+j0.000000, -0.146730-j0.989177, 0.923880-j0.382683, -0.671559-j0.740951, 0.382684-j0.923879, -0.989177+j0.146730, -0.707106-j0.707108, -0.049069+j0.998795, -0.707108+j0.707106, 0.989177-j0.146728, 0.923879+j0.382686, -0.671557-j0.740953, -0.382680-j0.923881, 0.146726+j0.989177, -0.000005+j1.000000, 0.049073-j0.998795, 0.000006-j1.000000, 0.146723+j0.989178, 0.382676+j0.923883, -0.671552-j0.740957, -0.923876-j0.382693, 0.989178-j0.146720, 0.707115-j0.707098, -0.049081+j0.998795, 0.707097+j0.707117, -0.989179+j0.146715, -0.382699+j0.923873, -0.671546-j0.740963, -0.923887+j0.382666, -0.146710-j0.989179, -1.000000-j0.000022, 0.049091-j0.998794, -1.000000-j0.000024, -0.146705-j0.989180, -0.923890+j0.382658, -0.671537-j0.740971, -0.382712+j0.923868, -0.989181+j0.146698, 0.707083+j0.707131, -0.049104+j0.998794, 0.707133-j0.707080, 0.989182-j0.146691, -0.923864-j0.382722, -0.671527-j0.740980, 0.382641+j0.923897, 0.146683+j0.989183, 0.000050-j1.000000, 0.049119-j0.998793, -0.000054+j1.000000, 0.146675+j0.989185, -0.382629-j0.923902, -0.671514-j0.740992, 0.923855+j0.382742, 0.989186-j0.146666, -0.707155+j0.707059, -0.049138+j0.998792, -0.707055-j0.707158, -0.989188+j0.146656, 0.382756-j0.923850, -0.671499-j0.741005, 0.923912-j0.382606, -0.146645-j0.989189, 1.000000+j0.000089, 0.049160-j0.998791 |
+| P P16 | 1.000000+j0.000000, 0.146731-j0.989176, 0.923879+j0.382684, 0.671559-j0.740951, 0.382683+j0.923880, 0.989176+j0.146731, -0.707108+j0.707106, 0.049066+j0.998796, -0.707105-j0.707108, -0.989176-j0.146733, 0.923881-j0.382681, 0.671561-j0.740949, -0.382687+j0.923878, -0.146735+j0.989176, 0.000005-j1.000000, -0.049062-j0.998796, -0.000007+j1.000000, -0.146738+j0.989175, 0.382691-j0.923876, 0.671566-j0.740945, -0.923884+j0.382674, -0.989175-j0.146742, 0.707098+j0.707116, 0.049054+j0.998796, 0.707117-j0.707096, 0.989174+j0.146746, -0.382667-j0.923886, 0.671573-j0.740939, -0.923872-j0.382702, 0.146752-j0.989173, -1.000000-j0.000023, -0.049043-j0.998797, -1.000000-j0.000026, 0.146758-j0.989172, -0.923868-j0.382710, 0.671582-j0.740930, -0.382653-j0.923892, 0.989171+j0.146765, 0.707133-j0.707081, 0.049029+j0.998797, 0.707078+j0.707135, -0.989170-j0.146772, -0.923896+j0.382643, 0.671593-j0.740920, 0.382728-j0.923861, -0.146781+j0.989169, -0.000053+j1.000000, -0.049013-j0.998798, 0.000057-j1.000000, -0.146790+j0.989168, -0.382741+j0.923856, 0.671607-j0.740908, 0.923905-j0.382621, -0.989166-j0.146799, -0.707056-j0.707158, 0.048993+j0.998799, -0.707162+j0.707052, 0.989165+j0.146810, 0.382606+j0.923911, 0.671623-j0.740893, 0.923845+j0.382766, 0.146821-j0.989163, 1.000000+j0.000095, -0.048970-j0.998800 |
+| P P17 | 1.000000+j0.000000, 0.427555-j0.903989, 0.382683+j0.923880, 0.803207+j0.595700, -0.923879-j0.382684, -0.903989-j0.427556, 0.707106+j0.707108, 0.146729+j0.989177, 0.707108-j0.707105, 0.903988+j0.427557, 0.382686-j0.923878, 0.803205+j0.595702, 0.923881-j0.382679, -0.427560+j0.903987, -0.000006+j1.000000, -0.146724-j0.989177, 0.000007-j1.000000, -0.427563+j0.903986, -0.923883+j0.382675, 0.803201+j0.595707, -0.382694+j0.923875, 0.903984+j0.427566, -0.707116+j0.707097, 0.146716+j0.989179, -0.707096-j0.707118, -0.903982-j0.427571, 0.923872+j0.382701, 0.803196+j0.595715, -0.382664-j0.923888, 0.427576-j0.903980, -1.000000-j0.000024, -0.146705-j0.989180, -1.000000-j0.000028, 0.427582-j0.903977, -0.382655-j0.923891, 0.803188+j0.595726, 0.923866+j0.382716, -0.903974-j0.427588, -0.707080-j0.707134, 0.146690+j0.989182, -0.707137+j0.707077, 0.903970+j0.427596, -0.382727+j0.923862, 0.803178+j0.595739, -0.923899+j0.382636, -0.427604+j0.903966, 0.000056-j1.000000, -0.146673-j0.989185, -0.000061+j1.000000, -0.427612+j0.903962, 0.923905-j0.382622, 0.803167+j0.595754, 0.382749-j0.923852, 0.903958+j0.427622, 0.707161-j0.707053, 0.146652+j0.989188, 0.707048+j0.707165, -0.903953-j0.427632, -0.923846-j0.382765, 0.803153+j0.595773, 0.382596+j0.923916, 0.427643-j0.903948, 1.000000+j0.000101, -0.146628-j0.989192 |
+| P P18 | 1.000000+j0.000000, 0.671559-j0.740951, -0.382684+j0.923879, -0.514103+j0.857728, 0.923880-j0.382683, 0.740950+j0.671560, 0.707108-j0.707106, 0.242979+j0.970032, 0.707105+j0.707108, -0.740949-j0.671561, -0.382680-j0.923881, -0.514106+j0.857727, -0.923878-j0.382688, -0.671563+j0.740948, 0.000006-j1.000000, -0.242974-j0.970033, -0.000008+j1.000000, -0.671565+j0.740945, 0.923876+j0.382692, -0.514112+j0.857723, 0.382673+j0.923884, -0.740942-j0.671569, -0.707097-j0.707117, 0.242965+j0.970035, -0.707119+j0.707095, 0.740939+j0.671572, -0.923887+j0.382665, -0.514121+j0.857718, 0.382704-j0.923871, 0.671577-j0.740935, -1.000000-j0.000026, -0.242954-j0.970038, -1.000000-j0.000029, 0.671582-j0.740930, 0.382714-j0.923867, -0.514133+j0.857711, -0.923894+j0.382650, 0.740925+j0.671588, -0.707136+j0.707078, 0.242939+j0.970042, -0.707075-j0.707139, -0.740919-j0.671594, 0.382638+j0.923899, -0.514147+j0.857702, 0.923859+j0.382734, -0.671601+j0.740913, -0.000059+j1.000000, -0.242920-j0.970046, 0.000064-j1.000000, -0.671609+j0.740906, -0.923853-j0.382748, -0.514165+j0.857691, -0.382614-j0.923908, -0.740899-j0.671617, 0.707049+j0.707164, 0.242899+j0.970052, 0.707168-j0.707045, 0.740891+j0.671626, 0.923915-j0.382597, -0.514186+j0.857679, -0.382776+j0.923841, 0.671635-j0.740882, 1.000000+j0.000106, -0.242874-j0.970058 |
+| P P19 | 1.000000+j0.000000, 0.857729-j0.514103, -0.923880+j0.382683, -0.903989-j0.427555, -0.382684+j0.923879, -0.514102-j0.857729, -0.707106-j0.707108, 0.336888+j0.941545, -0.707108+j0.707105, 0.514100+j0.857730, -0.923878-j0.382687, -0.903988-j0.427559, 0.382679+j0.923881, -0.857731+j0.514098, -0.000006+j1.000000, -0.336883-j0.941546, 0.000008-j1.000000, -0.857733+j0.514095, -0.382674-j0.923883, -0.903984-j0.427565, 0.923875+j0.382695, 0.514091+j0.857736, 0.707117-j0.707096, 0.336875+j0.941550, 0.707094+j0.707119, -0.514086-j0.857738, 0.382702-j0.923872, -0.903980-j0.427575, 0.923889-j0.382661, 0.857742-j0.514081, -1.000000-j0.000027, -0.336863-j0.941554, -1.000000-j0.000031, 0.857745-j0.514075, 0.923893-j0.382657 |
+
+| |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| j0.382651, -0.903974-j0.427588,
0.382719-j0.923865, -0.514068-j0.857750, 0.707076+j0.707137, 0.336847+j0.941559, 0.707140-
j0.707073, 0.514060+j0.857754, 0.923860+j0.382732, -0.903966-j0.427605, -0.382631-j0.923901,
-0.857759+j0.514051, 0.000062-j1.000000, -0.336829-j0.941566, -0.000068+j1.000000,
-0.857765+j0.514042, 0.382615+j0.923908, -0.903957-j0.427624, -0.923849-j0.382757,
0.514032+j0.857771, -0.707167+j0.707046, 0.336806+j0.941574, -0.707042-j0.707172, -0.514021-
j0.857778, -0.382774+j0.923842, -0.903946-j0.427647, -0.923920+j0.382586, 0.857784-j0.514010,
1.000000+j0.000112, -0.336781-j0.941583 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $P_{P20}$ | 1.000000+j0.000000, 0.970031-j0.242980, -0.923879-j0.382684, 0.336890-j0.941544, -0.382683-j0.923880, 0.242979+j0.970032, -0.707108+j0.707106, 0.427553+j0.903990, -0.707105-j0.707108, -0.242977-j0.970032, -0.923881+j0.382680, 0.336894-j0.941543, 0.382688-j0.923878, -0.970033+j0.242975, 0.000007-j1.000000, -0.427548-j0.903993, -0.000009+j1.000000, -0.970034+j0.242971, -0.382693+j0.923875, 0.336901-j0.941540, 0.923885-j0.382671, -0.242966-j0.970035, 0.707096+j0.707118, 0.427540+j0.903997, 0.707120-j0.707094, 0.242961+j0.970036, 0.382663+j0.923888, 0.336912-j0.941536, 0.923870+j0.382707, 0.970038-j0.242954, -1.000000-j0.000029, -0.427528-j0.904002, -1.000000-j0.000032, 0.970040-j0.242947, 0.923866+j0.382717, 0.336926-j0.941531, 0.382646+j0.923895, 0.242939+j0.970042, 0.707139-j0.707075, 0.427512+j0.904010, 0.707071+j0.707142, -0.242929-j0.970044, 0.923901-j0.382633, 0.336944-j0.941525, -0.382739+j0.923857, -0.970047+j0.242919, -0.000066+j1.000000, -0.427493-j0.904019, 0.000071-j1.000000, -0.970049+j0.242908, 0.382755-j0.923850, 0.336966-j0.941517, -0.923911+j0.382606, -0.242896-j0.970052, -0.707043-j0.707170, 0.427471+j0.904029, -0.707175+j0.707038, 0.242883+j0.970056, -0.382588-j0.923919, 0.336991-j0.941508, -0.923837-j0.382786, 0.970059-j0.242869, 1.000000+j0.000118, -0.427445-j0.904041 |
+| $P_{P21}$ | 1.000000+j0.000000, 0.998795+j0.049068, -0.382683-j0.923880, 0.970031+j0.242981, 0.923879+j0.382684, 0.049069-j0.998795, 0.707106+j0.707108, 0.514101+j0.857730, 0.707109-j0.707105, -0.049071+j0.998795, -0.382687+j0.923878, 0.970030+j0.242985, -0.923882+j0.382679, -0.998795-j0.049074, -0.000007+j1.000000, -0.514096-j0.857733, 0.000009-j1.000000, -0.998795-j0.049078, 0.923884-j0.382673, 0.970028+j0.242992, 0.382696-j0.923874, -0.049083+j0.998795, -0.707118+j0.707095, 0.514087+j0.857738, -0.707093-j0.707121, 0.049089-j0.998794, -0.923871-j0.382704, 0.970025+j0.243004, 0.382659+j0.923890, 0.998794+j0.049096, -1.000000-j0.000030, -0.514075-j0.857745, -1.000000-j0.000034, 0.998794+j0.049104, 0.382648+j0.923894, 0.970021+j0.243019, -0.923863-j0.382723, 0.049113-j0.998793, -0.707073-j0.707140, 0.514060+j0.857754, -0.707144+j0.707070, -0.049123+j0.998793, 0.382737-j0.923857, 0.970017+j0.243039, 0.923904-j0.382625, -0.998792-j0.049134, 0.000069-j1.000000, -0.514041-j0.857766, -0.000075+j1.000000, -0.998792-j0.049146, -0.923911+j0.382609, 0.970011+j0.243062, -0.382764+j0.923846, -0.049158+j0.998791, 0.707173-j0.707040, 0.514019+j0.857779, 0.707035+j0.707178, 0.049172-j0.998790, 0.923838+j0.382784, 0.970004+j0.243089, -0.382576-j0.923924, 0.998790+j0.049187, 1.000000+j0.000124, -0.513993-j0.857794 |
+| $P_{P22}$ | 1.000000+j0.000000, 0.941544+j0.336890, 0.382684-j0.923879, -0.146731+j0.989176, -0.923880+j0.382683, -0.336891+j0.941544, 0.707108-j0.707106, 0.595698+j0.803209, 0.707105+j0.707109, 0.336893-j0.941543, 0.382680+j0.923881, -0.146735+j0.989176, 0.923877+j0.382688, -0.941542-j0.336896, 0.000007-j1.000000, -0.595693-j0.803212, -0.000009+j1.000000, -0.941541-j0.336900, -0.923875-j0.382694, -0.146743+j0.989175, -0.382670-j0.923885, 0.336905-j0.941539, -0.707095-j0.707119, 0.595684+j0.803219, -0.707121+j0.707092, -0.336911+j0.941537, 0.923889-j0.382661, -0.146756+j0.989173, -0.382709+j0.923869, 0.941534+j0.336917, -1.000000-j0.000031, -0.595672-j0.803227, -1.000000-j0.000036, 0.941531+j0.336925, -0.382720+j0.923864, -0.146772+j0.989170, 0.923897-j0.382642, -0.336934+j0.941528, -0.707142+j0.707072, 0.595657+j0.803239, -0.707068-j0.707146, 0.336944-j0.941525, -0.382628-j0.923903, -0.146793+j0.989167, -0.923854-j0.382744, -0.941521-j0.336955, -0.000072+j1.000000, -0.595639-j0.803252, 0.000078-j1.000000, -0.941517-j0.336967, 0.923847+j0.382762, -0.146818+j0.989164, 0.382599+j0.923915, 0.336979-j0.941512, 0.707037+j0.707177, 0.595617+j0.803268, 0.707182-j0.707032, -0.336993+j0.941507, -0.923923+j0.382579, -0.146847+j0.989159, 0.382796-j0.923833, 0.941502+j0.337008, 1.000000+j0.000129, -0.595592-j0.803287 |
+| $P_{P23}$ | 1.000000+j0.000000, 0.803207+j0.595699, 0.923880-j0.382683, -0.998795-j0.049068, 0.382684-j0.923879, 0.595700-j0.803207, -0.707106-j0.707108, 0.671557+j0.740953, -0.707109+j0.707105, -0.595702+j0.803206, 0.923878+j0.382687, -0.998795-j0.049073, -0.382678-j0.923882, -0.803204-j0.595705, -0.000008+j1.000000, -0.671553-j0.740957, 0.000010-j1.000000, -0.803201-j0.595708, 0.382672+j0.923884, -0.998795-j0.049081, -0.923874-j0.382697, -0.595713+j0.803198, 0.707120-j0.707094, 0.671544+j0.740964, 0.707092+j0.707122, 0.595718-j0.803194, -0.382706+j0.923870, -0.998794-j0.049094, -0.923890+j0.382657, 0.803189+j0.595724, -1.000000-j0.000033, -0.671533-j0.740975, -1.000000-j0.000037, 0.803184+j0.595731, -0.923895+j0.382645, -0.998793-j0.049112, -0.382727+j0.923862, 0.595739-j0.803178, 0.707070+j0.707143, 0.671519+j0.740988, 0.707147-j0.707066, -0.595748+j0.803172, -0.923855-j0.382742, -0.998792-j0.049134, 0.382620+j0.923906, -0.803165-j0.595757, 0.000075-j1.000000, -0.671501-j0.741004, -0.000082+j1.000000, -0.803157-j0.595768, -0.382602-j0.923913, -0.998791-j0.049160, 0.923843+j0.382772, -0.595779+j0.803148, -0.707180+j0.707034, 0.671480+j0.741023, -0.707029-j0.707185, 0.595791-j0.803139, 0.382793-j0.923834, -0.998789-j0.049190, 0.923928-j0.382566, 0.803130+j0.595805, 1.000000+j0.000135, -0.671456-j0.741045 |
+| $P_{P24}$ | 1.000000+j0.000000, 0.595699+j0.803208, 0.923879+j0.382684, -0.049067-j0.998795, 0.382683+j0.923880, -0.803208+j0.595698, -0.707108+j0.707106, 0.740950+j0.671561, -0.707105-j0.707109, 0.803210-j0.595696, 0.923881-j0.382679, -0.049063-j0.998796, -0.382689+j0.923877, -0.595694-j0.803212, 0.000008-j1.000000, -0.740945-j0.671566, -0.000010+j1.000000, -0.595690-j0.803214, 0.382695-j0.923875, -0.049054-j0.998796, -0.923886+j0.382669, 0.803218-j0.595686, 0.707094+j0.707120, 0.740937+j0.671574, 0.707122-j0.707091, -0.803222+j0.595680, -0.382660- |
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| j0.923889, -0.049040-j0.998797, -0.923868-j0.382711, 0.595674+j0.803227, -1.000000-j0.000034,
-0.740927-j0.671586, -1.000000-j0.000039, 0.595666+j0.803232, -0.923863-j0.382724, -0.049022-
j0.998798, -0.382639-j0.923898, -0.803238+j0.595658, 0.707145-j0.707069, 0.740913+j0.671601,
0.707065+j0.707149, 0.803245-j0.595649, -0.923905+j0.382623, -0.048999-j0.998799, 0.382750-
j0.923852, -0.595639-j0.803252, -0.000078+j1.000000, -0.740896-j0.671620, 0.000085-j1.000000,
-0.595628-j0.803260, -0.382769+j0.923844, -0.048972-j0.998800, 0.923918-j0.382591, 0.803269-
j0.595616, -0.707031-j0.707183, 0.740876+j0.671641, -0.707188+j0.707025, -0.803279+j0.595603,
0.382569+j0.923927, -0.048940-j0.998802, 0.923829+j0.382806, 0.595590+j0.803289,
1.000000+j0.000141, -0.740853-j0.671667 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $P_{P25}$ | 1.000000+j0.000000, 0.336890+j0.941544, 0.382683+j0.923880, 0.989177-j0.146730, -0.923879-j0.382684, 0.941545-j0.336889, 0.707106+j0.707108, 0.803206+j0.595701, 0.707109-j0.707105, -0.941545+j0.336886, 0.382688-j0.923878, 0.989177-j0.146725, 0.923882-j0.382678, -0.336883-j0.941546, -0.000008+j1.000000, -0.803202-j0.595707, 0.000011-j1.000000, -0.336879-j0.941548, -0.923885+j0.382671, 0.989179-j0.146716, -0.382698+j0.923873, -0.941550+j0.336873, -0.707121+j0.707093, 0.803195+j0.595716, -0.707090-j0.707123, 0.941552-j0.336866, 0.923869+j0.382708, 0.989181-j0.146702, -0.382655-j0.923891, 0.336859+j0.941555, -1.000000-j0.000036, -0.803185-j0.595730, -1.000000-j0.000040, 0.336850+j0.941558, -0.382642-j0.923897, 0.989184-j0.146683, 0.923860+j0.382730, 0.941562-j0.336840, -0.707067-j0.707147, 0.803172+j0.595747, -0.707151+j0.707063, -0.941566+j0.336828, -0.382747+j0.923853, 0.989187-j0.146660, -0.923908+j0.382614, -0.336816-j0.941570, 0.000082-j1.000000, -0.803157-j0.595768, -0.000089+j1.000000, -0.336803-j0.941575, 0.923916-j0.382595, 0.989191-j0.146632, 0.382779-j0.923840, -0.941580+j0.336788, 0.707186-j0.707028, 0.803138+j0.595792, 0.707022+j0.707192, 0.941586-j0.336773, -0.923830-j0.382802, 0.989196-j0.146599, 0.382556+j0.923932, 0.336756+j0.941592, 1.000000+j0.000147, -0.803117-j0.595821 |
+| $P_{P26}$ | 1.000000+j0.000000, 0.049068+j0.998795, -0.382684+j0.923879, 0.242980+j0.970031, 0.923880-j0.382683, -0.998796+j0.049066, 0.707108-j0.707105, 0.857727+j0.514105, 0.707105+j0.707109, 0.998796-j0.049064, -0.382679-j0.923881, 0.242975+j0.970033, -0.923877-j0.382689, -0.049060-j0.998796, 0.000009-j1.000000, -0.857724-j0.514111, -0.000011+j1.000000, -0.049055-j0.998796, 0.923874+j0.382696, 0.242965+j0.970035, 0.382668+j0.923886, 0.998796-j0.049049, -0.707092-j0.707121, 0.857717+j0.514122, -0.707124+j0.707090, -0.998797+j0.049042, -0.923890+j0.382658, 0.242951+j0.970039, 0.382713-j0.923867, 0.049033+j0.998797, -1.000000-j0.000037, -0.857708-j0.514136, -1.000000-j0.000042, 0.049023+j0.998798, 0.382727-j0.923862, 0.242932+j0.970043, -0.923900+j0.382635, -0.998798+j0.049012, -0.707148+j0.707065, 0.857697+j0.514155, -0.707061-j0.707152, 0.998799-j0.049000, 0.382618+j0.923907, 0.242908+j0.970049, 0.923850+j0.382755, -0.048986-j0.998799, -0.000085+j1.000000, -0.857683-j0.514179, 0.000092-j1.000000, -0.048972-j0.998800, -0.923841-j0.382776, 0.242879+j0.970056, -0.382584-j0.923921, 0.998801-j0.048956, 0.707025+j0.707189, 0.857667+j0.514206, 0.707195-j0.707019, -0.998802+j0.048939, 0.923931-j0.382560, 0.242846+j0.970065, -0.382816+j0.923825, 0.048920+j0.998803, 1.000000+j0.000153, -0.857648-j0.514238 |
+| $P_{P27}$ | 1.000000+j0.000000, -0.242980+j0.970031, -0.923880+j0.382683, -0.941544+j0.336889, -0.382684+j0.923879, 0.970031+j0.242982, -0.707105-j0.707108, 0.903988+j0.427557, -0.707109+j0.707105, -0.970030-j0.242984, -0.923878-j0.382688, -0.941546+j0.336884, 0.382677+j0.923882, 0.242988-j0.970029, -0.000009+j1.000000, -0.903985-j0.427564, 0.000011-j1.000000, 0.242993-j0.970028, -0.382670-j0.923885, -0.941549+j0.336875, 0.923873+j0.382700, -0.970027-j0.242999, 0.707122-j0.707092, 0.903979+j0.427576, 0.707089+j0.707124, 0.970025+j0.243006, 0.382710-j0.923868, -0.941555+j0.336860, 0.923892-j0.382652, -0.243015+j0.970023, -1.000000-j0.000038, -0.903972-j0.427592, -1.000000-j0.000043, -0.243025+j0.970020, 0.923898-j0.382638, -0.941561+j0.336841, 0.382734-j0.923859, 0.970017+j0.243036, 0.707064+j0.707150, 0.903962+j0.427613, 0.707154-j0.707059, -0.970014-j0.243048, 0.923851+j0.382752, -0.941570+j0.336817, -0.382609-j0.923910, 0.242962-j0.970011, 0.000088-j1.000000, -0.903950-j0.427638, -0.000096+j1.000000, 0.243077-j0.970007, 0.382588+j0.923919, -0.941580+j0.336788, -0.923837-j0.382787, -0.970003-j0.243093, -0.707192+j0.707021, 0.903936+j0.427668, -0.707015-j0.707198, 0.969999+j0.243110, -0.382812+j0.923826, -0.941592+j0.336755, -0.923936+j0.382546, -0.243129+j0.969994, 1.000000+j0.000158, -0.903919-j0.427703 |
+| $P_{P28}$ | 1.000000+j0.000000, -0.514103+j0.857729, -0.923879-j0.382684, -0.427555-j0.903990, -0.382683-j0.923880, -0.857728-j0.514104, -0.707108+j0.707105, 0.941543+j0.336892, -0.707104-j0.707109, 0.857727+j0.514106, -0.923881+j0.382679, -0.427550-j0.903992, 0.382690-j0.923877, 0.514110-j0.857724, 0.000009-j1.000000, -0.941541-j0.336900, -0.000012+j1.000000, 0.514114-j0.857722, -0.382697+j0.923874, -0.427540-j0.903996, 0.923886-j0.382667, 0.857718+j0.514120, 0.707091+j0.707122, 0.941536+j0.336912, 0.707125-j0.707089, -0.857714-j0.514127, 0.382656+j0.923891, -0.427526-j0.904003, 0.923866+j0.382716, -0.514135+j0.857710, -1.000000-j0.000040, -0.941530-j0.336930, -1.000000-j0.000045, -0.514144+j0.857704, 0.923860+j0.382730, -0.427507-j0.904012, 0.382631+j0.923901, -0.857698-j0.514154, 0.707151-j0.707062, 0.941522+j0.336952, 0.707058+j0.707156, 0.857691+j0.514165, 0.923909-j0.382613, -0.427483-j0.904023, -0.382761+j0.923848, 0.514178-j0.857684, -0.000091+j1.000000, -0.941512-j0.336979, 0.000099-j1.000000, 0.514191-j0.857676, 0.382783-j0.923838, -0.427454-j0.904037, -0.923924+j0.382576, 0.857667+j0.514206, -0.707018-j0.707195, 0.941500+j0.337012, -0.707202+j0.707012, -0.857657-j0.514222, -0.382551-j0.923935, -0.427421-j0.904053, -0.923821-j0.382825, -0.514239+j0.857647, 1.000000+j0.000164, -0.941487-j0.337049 |
+| $P_{P29}$ | 1.000000+j0.000000, -0.740951+j0.671559, -0.382683-j0.923880, 0.857729-j0.514102, 0.923879+j0.382684, 0.671558+j0.740952, 0.707105+j0.707108, 0.970031+j0.242983, 0.707109-j0.707104, -0.671556-j0.740954, -0.382688+j0.923878, 0.857732-j0.514097, -0.923882+j0.382677, 0.740957-j0.671553, -0.000010+j1.000000, -0.970029-j0.242991, 0.000012-j1.000000, 0.740960-j0.671549, 0.923885-j0.382669, 0.857737-j0.514088, 0.382701-j0.923872, -0.671544-j0.740965, -0.707123+j0.707091, 0.970025+j0.243004, -0.707088- |
+
+| | |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | j0.707126, 0.671538+j0.740971, -0.923868-j0.382712, 0.857746-j0.514074, 0.382650+j0.923893, -0.740977+j0.671530, -1.000000-j0.000041, -0.970021-j0.243023, -1.000000-j0.000047, -0.740984+j0.671522, 0.382635+j0.923900, 0.857757-j0.514055, -0.923857-j0.382738, 0.671513+j0.740993, -0.707061-j0.707153, 0.970015+j0.243047, -0.707158+j0.707056, -0.671503-j0.741002, 0.382756-j0.923849, 0.857771-j0.514032, 0.923913-j0.382603, 0.741012-j0.671492, 0.000094-j1.000000, -0.970007-j0.243076, -0.000103+j1.000000, 0.741023-j0.671480, -0.923922+j0.382581, 0.857788-j0.514004, -0.382794+j0.923834, -0.671467-j0.741035, 0.707198-j0.707015, 0.969999+j0.243110, 0.707009+j0.707205, 0.671452+j0.741048, 0.923823+j0.382821, 0.857808-j0.513971, -0.382536-j0.923940, -0.741062+j0.671437, 1.000000+j0.000170, -0.969989-j0.243150 |
+| P P30 | 1.000000+j0.000000, -0.903989+j0.427555, 0.382684-j0.923879, 0.595699+j0.803208, -0.923880+j0.382682, -0.427554-j0.903990, 0.707108-j0.707105, 0.989176+j0.146733, 0.707104+j0.707109, 0.427551+j0.903991, 0.382679+j0.923882, 0.595694+j0.803211, 0.923877+j0.382690, 0.903993-j0.427547, 0.000010-j1.000000, -0.989175-j0.146742, -0.000013+j1.000000, 0.903995-j0.427542, -0.923873-j0.382698, 0.595685+j0.803218, -0.382665-j0.923887, 0.427536+j0.903998, -0.707090-j0.707123, 0.989173+j0.146756, -0.707126+j0.707087, -0.427528-j0.904002, 0.923892-j0.382654, 0.595671+j0.803228, -0.382718+j0.923865, -0.904006+j0.427519, -1.000000-j0.000042, -0.989170-j0.146775, -1.000000-j0.000048, -0.904011+j0.427509, -0.382733+j0.923859, 0.595653+j0.803242, 0.923903-j0.382628, -0.427497-j0.904017, -0.707154+j0.707059, 0.989166+j0.146800, -0.707054-j0.707159, 0.427485+j0.904023, -0.382608-j0.923911, 0.595631+j0.803259, -0.923845-j0.382766, 0.904029-j0.427471, -0.000098+j1.000000, -0.989162-j0.146831, 0.000106-j1.000000, 0.904037-j0.427455, 0.923836+j0.382790, 0.595603+j0.803279, 0.382569+j0.923927, 0.427439+j0.904044, 0.707012+j0.707201, 0.989156+j0.146868, 0.707208-j0.707005, -0.427421-j0.904053, -0.923938+j0.382541, 0.595571+j0.803302, 0.382835-j0.923817, -0.904062+j0.427401, 1.000000+j0.000176, -0.989150-j0.146910 |
+| P P31 | 1.000000+j0.000000, -0.989177+j0.146730, 0.923880-j0.382683, -0.740952+j0.671558, 0.382684-j0.923879, 0.146729+j0.989177, -0.707105-j0.707108, 0.998795+j0.049071, -0.707109+j0.707104, -0.146726-j0.989177, 0.923877+j0.382688, -0.740956+j0.671554, -0.382676-j0.923882, 0.989178-j0.146722, -0.000010+j1.000000, -0.998795-j0.049079, 0.000013-j1.000000, 0.989179-j0.146716, 0.382668+j0.923886, -0.740963+j0.671545, -0.923872-j0.382702, -0.146709-j0.989180, 0.707124-j0.707090, 0.998794+j0.049094, 0.707087+j0.707127, 0.146700+j0.989181, -0.382714+j0.923867, -0.740975+j0.671532, -0.923894+j0.382648, -0.989183+j0.146690, -1.000000-j0.000044, -0.998793-j0.049114, -1.000000-j0.000050, -0.989184+j0.146678, -0.923901+j0.382632, -0.740991+j0.671515, -0.382741+j0.923856, 0.146665+j0.989186, 0.707058+j0.707156, 0.998792+j0.049141, 0.707161-j0.707053, -0.146651-j0.989188, -0.923847-j0.382761, -0.741010+j0.671493, 0.382598+j0.923915, 0.989191-j0.146635, 0.000101-j1.000000, -0.998790-j0.049173, -0.000110+j1.000000, 0.989193-j0.146618, -0.382574-j0.923925, -0.741034+j0.671467, 0.923830+j0.382802, -0.146599-j0.989196, -0.707204+j0.707009, 0.998788+j0.049211, -0.707002-j0.707212, 0.146578+j0.989199, 0.382830-j0.923819, -0.741062+j0.671437, 0.923945-j0.382526, -0.989202+j0.146557, 1.000000+j0.000181, -0.998786-j0.049255 |
+
+## AA.2 Association between Midambles and Channelisation Codes for default midamble allocation
+
+The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. Secondary channelisation codes are marked with \*. These associations apply for both UL and DL.
+
+### AA.2.1 Association for K=16 Midambles
+
+
+
+A hierarchical tree diagram showing the association of 16 Midambles to spreading codes for K=16. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). These further branch into m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(13) - c\_4^(4). Each of these then branches into m^(1) - c\_8^(1), m^(3) - c\_8^(2), m^(5) - c\_8^(3), m^(7) - c\_8^(4), m^(9) - c\_8^(5), m^(11) - c\_8^(6), m^(13) - c\_8^(7), and m^(15) - c\_8^(8). Finally, each of these branches into two leaf nodes representing spreading codes c\_16^(1) through c\_16^(16).
+
+Figure AA.1: Association of Midambles to Spreading Codes for K=16
+
+### AA.2.2 Association for K=14 Midambles
+
+
+
+A hierarchical tree diagram showing the association of 14 Midambles to spreading codes for K=14. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). These further branch into m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(13) - c\_4^(4). Each of these then branches into m^(1) - c\_8^(1), m^(3) - c\_8^(2), m^(5) - c\_8^(3), m^(7) - c\_8^(4), m^(9) - c\_8^(5), m^(11) - c\_8^(6), m^(13) - c\_8^(7), and m^(14) - c\_8^(8). Finally, each of these branches into two leaf nodes representing spreading codes c\_16^(1) through c\_16^(14) and c\_16^(14)\* through c\_16^(16)\*.
+
+Figure AA.2: Association of Midambles to Spreading Codes for K=14
+
+### AA.2.3 Association for K=12 Midambles
+
+
+
+Tree diagram showing the association of 12 Midambles to spreading codes for K=12. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. Further branches lead to intermediate nodes like m^{(1)} - c\_4^{(1)}, m^{(5)} - c\_4^{(2)}, m^{(9)} - c\_4^{(3)}, and m^{(11)} - c\_4^{(4)}, which then lead to leaf nodes representing spreading codes such as m^{(1)} - c\_{16}^{(1)}, m^{(2)} - c\_{16}^{(2)}, etc.
+
+Figure AA.3: Association of Midambles to Spreading Codes for K=12
+
+### AA.2.4 Association for K=10 Midambles
+
+
+
+Tree diagram showing the association of 10 Midambles to spreading codes for K=10. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(7)} - c\_2^{(2)}. Further branches lead to intermediate nodes like m^{(1)} - c\_4^{(1)}, m^{(5)} - c\_4^{(2)}, m^{(7)} - c\_4^{(3)}, and m^{(9)} - c\_4^{(4)}, which then lead to leaf nodes representing spreading codes such as m^{(1)} - c\_{16}^{(1)}, m^{(2)} - c\_{16}^{(2)}, etc.
+
+Figure AA.4: Association of Midambles to Spreading Codes for K=10
+
+### AA.2.5 Association for K=8 Midambles
+
+
+
+Tree diagram for K=8 showing the association of midambles m to spreading codes c. The root is m^{(1)} - c\_1^{(1)}. It splits into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. These split into c\_4 nodes: m^{(1)} - c\_4^{(1)}, m^{(3)} - c\_4^{(2)}, m^{(5)} - c\_4^{(3)}, and m^{(7)} - c\_4^{(4)}. These split into c\_8 nodes: m^{(1)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(3)} - c\_8^{(3)}, m^{(4)} - c\_8^{(4)}, m^{(5)} - c\_8^{(5)}, m^{(6)} - c\_8^{(6)}, m^{(7)} - c\_8^{(7)}, and m^{(8)} - c\_8^{(8)}. Finally, each c\_8 node splits into two c\_{16} nodes, where the second node in each pair is marked with an asterisk: (m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}), (m^{(2)} - c\_{16}^{(3)}, m^{(2)} - c\_{16}^{(4)\*}), (m^{(3)} - c\_{16}^{(5)}, m^{(3)} - c\_{16}^{(6)\*}), (m^{(4)} - c\_{16}^{(7)}, m^{(4)} - c\_{16}^{(8)\*}), (m^{(5)} - c\_{16}^{(9)}, m^{(5)} - c\_{16}^{(10)\*}), (m^{(6)} - c\_{16}^{(11)}, m^{(6)} - c\_{16}^{(12)\*}), (m^{(7)} - c\_{16}^{(13)}, m^{(7)} - c\_{16}^{(14)\*}), (m^{(8)} - c\_{16}^{(15)}, m^{(8)} - c\_{16}^{(16)\*}).
+
+Figure AA.5: Association of Midambles to Spreading Codes for K=8
+
+### AA.2.6 Association for K=6 Midambles
+
+
+
+Tree diagram for K=6 showing the association of midambles m to spreading codes c. The root is m^{(1)} - c\_1^{(1)}. It splits into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. These split into c\_4 nodes: m^{(1)} - c\_4^{(1)}, m^{(3)} - c\_4^{(2)}, m^{(5)} - c\_4^{(3)}, and m^{(6)} - c\_4^{(4)}. These split into c\_8 nodes: m^{(1)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(3)} - c\_8^{(3)}, m^{(4)} - c\_8^{(4)}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(6)} - c\_8^{(7)}, and m^{(6)} - c\_8^{(8)\*}. Finally, each c\_8 node splits into two c\_{16} nodes: (m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}), (m^{(2)} - c\_{16}^{(3)}, m^{(2)} - c\_{16}^{(4)\*}), (m^{(3)} - c\_{16}^{(5)}, m^{(3)} - c\_{16}^{(6)\*}), (m^{(4)} - c\_{16}^{(7)}, m^{(4)} - c\_{16}^{(8)\*}), (m^{(5)} - c\_{16}^{(9)}, m^{(5)} - c\_{16}^{(10)\*}), (m^{(5)} - c\_{16}^{(11)\*}, m^{(5)} - c\_{16}^{(12)\*}), (m^{(6)} - c\_{16}^{(13)}, m^{(6)} - c\_{16}^{(14)\*}), (m^{(6)} - c\_{16}^{(15)\*}, m^{(6)} - c\_{16}^{(16)\*}).
+
+Figure AA.6: Association of Midambles to Spreading Codes for K=6
+
+### AA.2.7 Association for K=4 Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=4. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(3)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(2)} - c\_4^{(2)}. m^{(3)} - c\_2^{(2)} branches into m^{(3)} - c\_4^{(3)} and m^{(4)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(2)} - c\_8^{(3)}, m^{(2)} - c\_8^{(4)\*}, m^{(3)} - c\_8^{(5)}, m^{(3)} - c\_8^{(6)\*}, m^{(4)} - c\_8^{(7)}, m^{(4)} - c\_8^{(8)\*}. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(1)} - c\_{16}^{(1)} through m^{(4)} - c\_{16}^{(16)\*}.
+
+Figure AA.7: Association of Midambles to Spreading Codes for K=4
+
+### AA.2.8 Association for K=2 Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=2. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(2)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(1)} - c\_4^{(2)\*}. m^{(2)} - c\_2^{(2)} branches into m^{(2)} - c\_4^{(3)} and m^{(2)} - c\_4^{(4)\*}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(1)} - c\_8^{(3)\*}, m^{(1)} - c\_8^{(4)\*}, m^{(2)} - c\_8^{(5)}, m^{(2)} - c\_8^{(6)\*}, m^{(2)} - c\_8^{(7)\*}, m^{(2)} - c\_8^{(8)\*}. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(1)} - c\_{16}^{(1)} through m^{(2)} - c\_{16}^{(16)\*}.
+
+Figure AA.8: Association of Midambles to Spreading Codes for K=2
+
+## AA.3 Association between Midambles and Channelisation Codes for special default midamble allocation
+
+The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. Secondary channelisation codes are marked with \*. These associations apply for both UL and DL.
+
+### AA.3.1 Association for K=16 Midambles
+
+
+
+Figure AA.3.1a: Association of Midambles to Spreading Codes for K=16 pattern 1. This tree diagram shows the hierarchical association of midambles to spreading codes. It starts with m^{(1)} - c\_1^{(1)} at the root, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. These further branch into m^{(1)} - c\_4^{(1)}, m^{(5)} - c\_4^{(2)}, m^{(9)} - c\_4^{(3)}, and m^{(13)} - c\_4^{(4)}. Each of these then branches into two m^{(i)} - c\_8^{(j)} nodes, which finally branch into pairs of spreading codes m^{(i)} - c\_{16}^{(j)} and m^{(i)} - c\_{16}^{(j)\*}.
+
+Figure AA.3.1a: Association of Midambles to Spreading Codes for K=16 pattern 1
+
+
+
+Figure AA.3.1aa: Association of Midambles to Spreading Codes for K=16 pattern 1A. This tree diagram is similar to Figure AA.3.1a but with a different branching structure for the secondary channelisation codes. It starts with m^{(1)} - c\_1^{(1)} at the root, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. These further branch into m^{(1)} - c\_4^{(1)}, m^{(5)} - c\_4^{(2)}, m^{(9)} - c\_4^{(3)}, and m^{(13)} - c\_4^{(4)}. Each of these then branches into two m^{(i)} - c\_8^{(j)} nodes, which finally branch into pairs of spreading codes m^{(i)} - c\_{16}^{(j)} and m^{(i)} - c\_{16}^{(j)\*}.
+
+Figure AA.3.1aa: Association of Midambles to Spreading Codes for K=16 pattern 1A
+
+Error:
+
+103
+
+Error: Reference source not
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 1B. The root node is m^{(3)} - c\_1^{(1)}, which branches into m^{(3)} - c\_2^{(1)} and m^{(11)} - c\_2^{(2)}. m^{(3)} - c\_2^{(1)} branches into m^{(3)} - c\_4^{(1)} and m^{(7)} - c\_4^{(2)}. m^{(11)} - c\_2^{(2)} branches into m^{(11)} - c\_4^{(3)} and m^{(15)} - c\_4^{(4)}. Further branches lead to m^{(3)} - c\_8^{(1)}, m^{(3)} - c\_8^{(2)\*}, m^{(7)} - c\_8^{(3)}, m^{(7)} - c\_8^{(4)\*}, m^{(11)} - c\_8^{(5)}, m^{(11)} - c\_8^{(6)\*}, m^{(15)} - c\_8^{(7)}, and m^{(15)} - c\_8^{(8)\*}. Each of these nodes branches into two final spreading codes, such as m^{(3)} - c\_{16}^{(1)} and m^{(3)} - c\_{16}^{(2)\*}.
+
+Figure AA.3.1ab: Association of Midambles to Spreading Codes for K=16 pattern 1B
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(6)} - c\_4^{(2)}. m^{(10)} - c\_2^{(2)} branches into m^{(10)} - c\_4^{(3)} and m^{(14)} - c\_4^{(4)}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(6)} - c\_8^{(3)}, m^{(8)} - c\_8^{(4)\*}, m^{(10)} - c\_8^{(5)}, m^{(12)} - c\_8^{(6)\*}, m^{(14)} - c\_8^{(7)}, and m^{(16)} - c\_8^{(8)\*}. Each of these nodes branches into two final spreading codes, such as m^{(2)} - c\_{16}^{(1)} and m^{(2)} - c\_{16}^{(2)\*}.
+
+Figure AA.3.1b: Association of Midambles to Spreading Codes for K=16 pattern 2
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=16 pattern 2A. The tree structure shows the hierarchical decomposition of the root node $m^{(2)} - c_1^{(1)}$ into various sub-nodes, eventually leading to leaf nodes representing the association with spreading codes $c_{16}^{(i)}$ .
+
+Root node: $m^{(2)} - c_1^{(1)}$
+
+First level branches:
+
+- $m^{(2)} - c_2^{(1)}$
+- $m^{(10)} - c_2^{(2)}$
+
+Second level branches (from $m^{(2)} - c_2^{(1)}$ ):
+
+- $m^{(2)} - c_4^{(1)}$
+- $m^{(6)} - c_4^{(2)}$
+
+Second level branches (from $m^{(10)} - c_2^{(2)}$ ):
+
+- $m^{(10)} - c_4^{(3)}$
+- $m^{(14)} - c_4^{(4)}$
+
+Third level branches (from $m^{(2)} - c_4^{(1)}$ ):
+
+- $m^{(2)} - c_8^{(1)}$
+- $m^{(2)} - c_8^{(2)*}$
+
+Third level branches (from $m^{(6)} - c_4^{(2)}$ ):
+
+- $m^{(6)} - c_8^{(3)}$
+- $m^{(6)} - c_8^{(4)*}$
+
+Third level branches (from $m^{(10)} - c_4^{(3)}$ ):
+
+- $m^{(10)} - c_8^{(5)}$
+- $m^{(10)} - c_8^{(6)*}$
+
+Third level branches (from $m^{(14)} - c_4^{(4)}$ ):
+
+- $m^{(14)} - c_8^{(7)}$
+- $m^{(14)} - c_8^{(8)*}$
+
+Final level branches (leaf nodes):
+
+- From $m^{(2)} - c_8^{(1)}$ : $m^{(2)} - c_{16}^{(1)}$ , $m^{(2)} - c_{16}^{(2)*}$
+- From $m^{(2)} - c_8^{(2)*}$ : $m^{(2)} - c_{16}^{(3)*}$ , $m^{(2)} - c_{16}^{(4)*}$
+- From $m^{(6)} - c_8^{(3)}$ : $m^{(6)} - c_{16}^{(5)}$ , $m^{(6)} - c_{16}^{(6)*}$
+- From $m^{(6)} - c_8^{(4)*}$ : $m^{(6)} - c_{16}^{(7)*}$ , $m^{(6)} - c_{16}^{(8)*}$
+- From $m^{(10)} - c_8^{(5)}$ : $m^{(10)} - c_{16}^{(9)}$ , $m^{(10)} - c_{16}^{(10)*}$
+- From $m^{(10)} - c_8^{(6)*}$ : $m^{(10)} - c_{16}^{(11)*}$ , $m^{(10)} - c_{16}^{(12)*}$
+- From $m^{(14)} - c_8^{(7)}$ : $m^{(14)} - c_{16}^{(13)}$ , $m^{(14)} - c_{16}^{(14)*}$
+- From $m^{(14)} - c_8^{(8)*}$ : $m^{(14)} - c_{16}^{(15)*}$ , $m^{(14)} - c_{16}^{(16)*}$
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. Further sub-nodes include m^{(2)} - c\_4^{(1)}, m^{(6)} - c\_4^{(2)}, m^{(10)} - c\_4^{(3)}, and m^{(14)} - c\_4^{(4)}, leading to leaf nodes such as m^{(2)} - c\_{16}^{(1)} through m^{(14)} - c\_{16}^{(16)}.
+
+Figure AA.3.1ba: Association of Midambles to Spreading Codes for K=16 pattern 2A
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=16 pattern 2B. The tree structure shows the hierarchical decomposition of the root node $m^{(4)} - c_1^{(1)}$ into various sub-nodes, eventually leading to leaf nodes representing the association with spreading codes $c_{16}^{(i)}$ .
+
+Root node: $m^{(4)} - c_1^{(1)}$
+
+First level branches:
+
+- $m^{(4)} - c_2^{(1)}$
+- $m^{(12)} - c_2^{(2)}$
+
+Second level branches (from $m^{(4)} - c_2^{(1)}$ ):
+
+- $m^{(4)} - c_4^{(1)}$
+- $m^{(8)} - c_4^{(2)}$
+
+Second level branches (from $m^{(12)} - c_2^{(2)}$ ):
+
+- $m^{(12)} - c_4^{(3)}$
+- $m^{(16)} - c_4^{(4)}$
+
+Third level branches (from $m^{(4)} - c_4^{(1)}$ ):
+
+- $m^{(4)} - c_8^{(1)}$
+- $m^{(4)} - c_8^{(2)*}$
+
+Third level branches (from $m^{(8)} - c_4^{(2)}$ ):
+
+- $m^{(8)} - c_8^{(3)}$
+- $m^{(8)} - c_8^{(4)*}$
+
+Third level branches (from $m^{(12)} - c_4^{(3)}$ ):
+
+- $m^{(12)} - c_8^{(5)}$
+- $m^{(12)} - c_8^{(6)*}$
+
+Third level branches (from $m^{(16)} - c_4^{(4)}$ ):
+
+- $m^{(16)} - c_8^{(7)}$
+- $m^{(16)} - c_8^{(8)*}$
+
+Final level branches (leaf nodes):
+
+- From $m^{(4)} - c_8^{(1)}$ : $m^{(4)} - c_{16}^{(1)}$ , $m^{(4)} - c_{16}^{(2)*}$
+- From $m^{(4)} - c_8^{(2)*}$ : $m^{(4)} - c_{16}^{(3)*}$ , $m^{(4)} - c_{16}^{(4)*}$
+- From $m^{(8)} - c_8^{(3)}$ : $m^{(8)} - c_{16}^{(5)}$ , $m^{(8)} - c_{16}^{(6)*}$
+- From $m^{(8)} - c_8^{(4)*}$ : $m^{(8)} - c_{16}^{(7)*}$ , $m^{(8)} - c_{16}^{(8)*}$
+- From $m^{(12)} - c_8^{(5)}$ : $m^{(12)} - c_{16}^{(9)}$ , $m^{(12)} - c_{16}^{(10)*}$
+- From $m^{(12)} - c_8^{(6)*}$ : $m^{(12)} - c_{16}^{(11)*}$ , $m^{(12)} - c_{16}^{(12)*}$
+- From $m^{(16)} - c_8^{(7)}$ : $m^{(16)} - c_{16}^{(13)}$ , $m^{(16)} - c_{16}^{(14)*}$
+- From $m^{(16)} - c_8^{(8)*}$ : $m^{(16)} - c_{16}^{(15)*}$ , $m^{(16)} - c_{16}^{(16)*}$
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(12)} - c\_2^{(2)}. Further sub-nodes include m^{(4)} - c\_4^{(1)}, m^{(8)} - c\_4^{(2)}, m^{(12)} - c\_4^{(3)}, and m^{(16)} - c\_4^{(4)}, leading to leaf nodes such as m^{(4)} - c\_{16}^{(1)} through m^{(16)} - c\_{16}^{(16)}.
+
+Figure AA.3.1bb: Association of Midambles to Spreading Codes for K=16 pattern 2B
+
+### AA.3.2 Association for K=14 Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. Further branches lead to m^{(1)} - c\_4^{(1)}, m^{(5)} - c\_4^{(2)}, m^{(9)} - c\_4^{(3)}, and m^{(13)} - c\_4^{(4)}. These then branch into m^{(1)} - c\_8^{(1)}, m^{(3)} - c\_8^{(2)}, m^{(5)} - c\_8^{(3)}, m^{(7)} - c\_8^{(4)}, m^{(9)} - c\_8^{(5)}, m^{(11)} - c\_8^{(6)}, m^{(13)} - c\_8^{(7)}, and m^{(13)} - c\_8^{(8)}. Finally, each of these branches into two leaf nodes representing spreading codes, such as m^{(1)} - c\_{16}^{(1)} and m^{(1)} - c\_{16}^{(2)\*}.
+
+Figure AA.3.2a: Association of Midambles to Spreading Codes for K=14 pattern 1
+
+
+
+A hierarchical tree diagram similar to Figure AA.3.2a, but with rectangular boxes around each node label. The structure is identical, starting from m^{(1)} - c\_1^{(1)} and branching through various midamble and code levels to the final spreading codes like m^{(1)} - c\_{16}^{(1)} and m^{(1)} - c\_{16}^{(2)\*}.
+
+Figure AA.3.2aa: Association of Midambles to Spreading Codes for K=14 pattern 1A
+
+Error:
+
+106
+
+Error: Reference source not
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(11) - c\_2^(2). Further sub-nodes include m^(3) - c\_4^(1), m^(7) - c\_4^(2), m^(11) - c\_4^(3), and m^(11) - c\_4^(4), which further branch into m^(3) - c\_8^(1), m^(3) - c\_8^(2), m^(7) - c\_8^(3), m^(7) - c\_8^(4), m^(11) - c\_8^(5), m^(11) - c\_8^(6), m^(11) - c\_8^(7), and m^(11) - c\_8^(8). Each of these nodes finally branches into two spreading codes, such as m^(3) - c\_16^(1) and m^(3) - c\_16^(2)\*.
+
+Figure AA.3.2ab: Association of Midambles to Spreading Codes for K=14 pattern 1B
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(10) - c\_2^(2). Further sub-nodes include m^(2) - c\_4^(1), m^(6) - c\_4^(2), m^(10) - c\_4^(3), and m^(14) - c\_4^(4), which further branch into m^(2) - c\_8^(1), m^(4) - c\_8^(2), m^(6) - c\_8^(3), m^(8) - c\_8^(4), m^(10) - c\_8^(5), m^(12) - c\_8^(6), m^(14) - c\_8^(7), and m^(14) - c\_8^(8). Each of these nodes finally branches into two spreading codes, such as m^(2) - c\_16^(1) and m^(2) - c\_16^(2)\*.
+
+Figure AA.3.2b: Association of Midambles to Spreading Codes for K=14 pattern 2
+
+
+
+```
+
+graph LR
+ Root["m^(2) - c_1^(1)"] --> N1["m^(2) - c_2^(1)"]
+ Root --> N2["m^(10) - c_2^(2)"]
+ N1 --> N3["m^(2) - c_4^(1)"]
+ N1 --> N4["m^(6) - c_4^(2)"]
+ N2 --> N5["m^(10) - c_4^(3)"]
+ N2 --> N6["m^(14) - c_4^(4)"]
+ N3 --> N7["m^(2) - c_8^(1)"]
+ N3 --> N8["m^(2) - c_8^(2)*"]
+ N4 --> N9["m^(6) - c_8^(3)"]
+ N4 --> N10["m^(6) - c_8^(4)*"]
+ N5 --> N11["m^(10) - c_8^(5)"]
+ N5 --> N12["m^(10) - c_8^(6)*"]
+ N6 --> N13["m^(14) - c_8^(7)"]
+ N6 --> N14["m^(14) - c_8^(8)*"]
+ N7 --> C1["m^(2) - c_16^(1)"]
+ N7 --> C2["m^(2) - c_16^(2)*"]
+ N8 --> C3["m^(2) - c_16^(3)*"]
+ N8 --> C4["m^(2) - c_16^(4)*"]
+ N9 --> C5["m^(6) - c_16^(5)"]
+ N9 --> C6["m^(6) - c_16^(6)*"]
+ N10 --> C7["m^(6) - c_16^(7)*"]
+ N10 --> C8["m^(6) - c_16^(8)*"]
+ N11 --> C9["m^(10) - c_16^(9)"]
+ N11 --> C10["m^(10) - c_16^(10)*"]
+ N12 --> C11["m^(10) - c_16^(11)*"]
+ N12 --> C12["m^(10) - c_16^(12)*"]
+ N13 --> C13["m^(14) - c_16^(13)"]
+ N13 --> C14["m^(14) - c_16^(14)*"]
+ N14 --> C15["m^(14) - c_16^(15)*"]
+ N14 --> C16["m^(14) - c_16^(16)*"]
+
+```
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 2A. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(10) - c\_2^(2). Further sub-nodes include m^(2) - c\_4^(1), m^(6) - c\_4^(2), m^(10) - c\_4^(3), m^(14) - c\_4^(4), and finally spreading codes c\_8^(1) through c\_8^(8) leading to c\_16^(1) through c\_16^(16).
+
+Figure AA.3.2ba: Association of Midambles to Spreading Codes for K=14 pattern 2A
+
+
+
+```
+
+graph LR
+ Root["m^(4) - c_1^(1)"] --> N1["m^(4) - c_2^(1)"]
+ Root --> N2["m^(12) - c_2^(2)"]
+ N1 --> N3["m^(4) - c_4^(1)"]
+ N1 --> N4["m^(8) - c_4^(2)"]
+ N2 --> N5["m^(12) - c_4^(3)"]
+ N2 --> N6["m^(12) - c_4^(4)"]
+ N3 --> N7["m^(4) - c_8^(1)"]
+ N3 --> N8["m^(4) - c_8^(2)*"]
+ N4 --> N9["m^(8) - c_8^(3)"]
+ N4 --> N10["m^(8) - c_8^(4)*"]
+ N5 --> N11["m^(12) - c_8^(5)"]
+ N5 --> N12["m^(12) - c_8^(6)*"]
+ N6 --> N13["m^(12) - c_8^(7)"]
+ N6 --> N14["m^(12) - c_8^(8)*"]
+ N7 --> C1["m^(4) - c_16^(1)"]
+ N7 --> C2["m^(4) - c_16^(2)*"]
+ N8 --> C3["m^(4) - c_16^(3)*"]
+ N8 --> C4["m^(4) - c_16^(4)*"]
+ N9 --> C5["m^(8) - c_16^(5)"]
+ N9 --> C6["m^(8) - c_16^(6)*"]
+ N10 --> C7["m^(8) - c_16^(7)*"]
+ N10 --> C8["m^(8) - c_16^(8)*"]
+ N11 --> C9["m^(12) - c_16^(9)"]
+ N11 --> C10["m^(12) - c_16^(10)*"]
+ N12 --> C11["m^(12) - c_16^(11)*"]
+ N12 --> C12["m^(12) - c_16^(12)*"]
+ N13 --> C13["m^(12) - c_16^(13)*"]
+ N13 --> C14["m^(12) - c_16^(14)*"]
+ N14 --> C15["m^(12) - c_16^(15)*"]
+ N14 --> C16["m^(12) - c_16^(16)*"]
+
+```
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 2B. The root node is m^(4) - c\_1^(1), which branches into m^(4) - c\_2^(1) and m^(12) - c\_2^(2). Further sub-nodes include m^(4) - c\_4^(1), m^(8) - c\_4^(2), m^(12) - c\_4^(3), m^(12) - c\_4^(4), and finally spreading codes c\_8^(1) through c\_8^(8) leading to c\_16^(1) through c\_16^(16).
+
+Figure AA.3.2bb: Association of Midambles to Spreading Codes for K=14 pattern 2B
+
+### AA.3.3 Association for K=12 Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=12 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} and m^{(11)} - c\_4^{(4)}. Further nodes include m^{(1)} - c\_8^{(1)}, m^{(3)} - c\_8^{(2)}, m^{(5)} - c\_8^{(3)}, m^{(7)} - c\_8^{(4)}, m^{(9)} - c\_8^{(5)}, m^{(9)} - c\_8^{(6)}, m^{(11)} - c\_8^{(7)}, and m^{(11)} - c\_8^{(8)}. The final nodes are m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, m^{(3)} - c\_{16}^{(3)}, m^{(3)} - c\_{16}^{(4)\*}, m^{(5)} - c\_{16}^{(5)}, m^{(5)} - c\_{16}^{(6)\*}, m^{(7)} - c\_{16}^{(7)}, m^{(7)} - c\_{16}^{(8)\*}, m^{(9)} - c\_{16}^{(9)}, m^{(9)} - c\_{16}^{(10)\*}, m^{(9)} - c\_{16}^{(11)\*}, m^{(9)} - c\_{16}^{(12)\*}, m^{(11)} - c\_{16}^{(13)}, m^{(11)} - c\_{16}^{(14)\*}, m^{(11)} - c\_{16}^{(15)\*}, and m^{(11)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.3a: Association of Midambles to Spreading Codes for K=12 pattern 1
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=12 pattern 1A. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} and m^{(9)} - c\_4^{(4)}. Further nodes include m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(5)} - c\_8^{(3)}, m^{(5)} - c\_8^{(4)\*}, m^{(9)} - c\_8^{(5)}, m^{(9)} - c\_8^{(6)\*}, m^{(9)} - c\_8^{(7)\*}, and m^{(9)} - c\_8^{(8)\*}. The final nodes are m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, m^{(1)} - c\_{16}^{(3)\*}, m^{(1)} - c\_{16}^{(4)\*}, m^{(5)} - c\_{16}^{(5)}, m^{(5)} - c\_{16}^{(6)\*}, m^{(5)} - c\_{16}^{(7)\*}, m^{(5)} - c\_{16}^{(8)\*}, m^{(9)} - c\_{16}^{(9)}, m^{(9)} - c\_{16}^{(10)\*}, m^{(9)} - c\_{16}^{(11)\*}, m^{(9)} - c\_{16}^{(12)\*}, m^{(9)} - c\_{16}^{(13)\*}, m^{(9)} - c\_{16}^{(14)\*}, m^{(9)} - c\_{16}^{(15)\*}, and m^{(9)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.3aa: Association of Midambles to Spreading Codes for K=12 pattern 1A
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=12 pattern 1B. The tree structure shows the hierarchical decomposition of the initial midamble $m^{(3)} - c_1^{(1)}$ into various sub-midambles and their corresponding spreading codes.
+
+- $m^{(3)} - c_1^{(1)}$
+ - $m^{(3)} - c_2^{(1)}$
+ - $m^{(3)} - c_4^{(1)}$
+ - $m^{(3)} - c_8^{(1)}$
+ - $m^{(3)} - c_{16}^{(1)}$
+ - $m^{(3)} - c_{16}^{(2)*}$
+ - $m^{(3)} - c_8^{(2)*}$
+ - $m^{(3)} - c_{16}^{(3)*}$$
+ - $m^{(3)} - c_{16}^{(4)*}$$
+ - $m^{(7)} - c_4^{(2)}$
+ - $m^{(7)} - c_8^{(3)}$
+ - $m^{(7)} - c_{16}^{(5)}$
+ - $m^{(7)} - c_{16}^{(6)*}$
+ - $m^{(7)} - c_8^{(4)*}$
+ - $m^{(7)} - c_{16}^{(7)*}$
+ - $m^{(7)} - c_{16}^{(8)*}$
+ - $m^{(11)} - c_2^{(2)}$
+ - $m^{(11)} - c_4^{(3)}$
+ - $m^{(11)} - c_8^{(5)}$
+ - $m^{(11)} - c_{16}^{(9)}$
+ - $m^{(11)} - c_{16}^{(10)*}$
+ - $m^{(11)} - c_8^{(6)*}$
+ - $m^{(11)} - c_{16}^{(11)*}$
+ - $m^{(11)} - c_{16}^{(12)*}$
+ - $m^{(11)} - c_4^{(4)*}$
+ - $m^{(11)} - c_8^{(7)*}$$
+ - $m^{(11)} - c_{16}^{(13)*}$$
+ - $m^{(11)} - c_{16}^{(14)*}$$
+ - $m^{(11)} - c_8^{(8)*}$$
+ - $m^{(11)} - c_{16}^{(15)*}$$
+ - $m^{(11)} - c_{16}^{(16)*}$$
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 1B.
+
+**Figure AA.3.3ab: Association of Midambles to Spreading Codes for K=12 pattern 1B**
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=12 pattern 2. The tree structure shows the hierarchical decomposition of the initial midamble $m^{(2)} - c_1^{(1)}$ into various sub-midambles and their corresponding spreading codes.
+
+- $m^{(2)} - c_1^{(1)}$
+ - $m^{(2)} - c_2^{(1)}$
+ - $m^{(2)} - c_4^{(1)}$
+ - $m^{(2)} - c_8^{(1)}$
+ - $m^{(2)} - c_{16}^{(1)}$
+ - $m^{(2)} - c_{16}^{(2)*}$
+ - $m^{(4)} - c_8^{(2)}$
+ - $m^{(4)} - c_{16}^{(3)}$
+ - $m^{(4)} - c_{16}^{(4)*}$
+ - $m^{(6)} - c_4^{(2)}$
+ - $m^{(6)} - c_8^{(3)}$
+ - $m^{(6)} - c_{16}^{(5)}$
+ - $m^{(6)} - c_{16}^{(6)*}$
+ - $m^{(8)} - c_8^{(4)}$
+ - $m^{(8)} - c_{16}^{(7)}$
+ - $m^{(8)} - c_{16}^{(8)*}$
+ - $m^{(10)} - c_2^{(2)}$
+ - $m^{(10)} - c_4^{(3)}$
+ - $m^{(10)} - c_8^{(5)}$
+ - $m^{(10)} - c_{16}^{(9)}$
+ - $m^{(10)} - c_{16}^{(10)*}$
+ - $m^{(10)} - c_8^{(6)*}$
+ - $m^{(10)} - c_{16}^{(11)*}$
+ - $m^{(10)} - c_{16}^{(12)*}$
+ - $m^{(12)} - c_4^{(4)}$
+ - $m^{(12)} - c_8^{(7)}$
+ - $m^{(12)} - c_{16}^{(13)}$
+ - $m^{(12)} - c_{16}^{(14)*}$
+ - $m^{(12)} - c_8^{(8)*}$
+ - $m^{(12)} - c_{16}^{(15)*}$
+ - $m^{(12)} - c_{16}^{(16)*}$
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2.
+
+**Figure AA.3.3b: Association of Midambles to Spreading Codes for K=12 pattern 2**
+
+Error:
+
+110
+
+Error: Reference source not
+
+
+
+```
+graph LR; m2c1["m^{(2)} - c_1^{(1)}"] --> m2c2["m^{(2)} - c_2^{(1)}"]; m2c1 --> m10c2["m^{(10)} - c_2^{(2)}"]; m2c2 --> m2c4["m^{(2)} - c_4^{(1)}"]; m2c2 --> m6c4["m^{(6)} - c_4^{(2)}"]; m10c2 --> m10c4_3["m^{(10)} - c_4^{(3)}"]; m10c2 --> m10c4_4["m^{(10)} - c_4^{(4)}"]; m2c4 --> m2c8_1["m^{(2)} - c_8^{(1)}"]; m2c4 --> m2c8_2["m^{(2)} - c_8^{(2)*}"]; m6c4 --> m6c8_3["m^{(6)} - c_8^{(3)}"]; m6c4 --> m6c8_4["m^{(6)} - c_8^{(4)*}"]; m10c4_3 --> m10c8_5["m^{(10)} - c_8^{(5)}"]; m10c4_3 --> m10c8_6["m^{(10)} - c_8^{(6)*}"]; m10c4_4 --> m10c8_7["m^{(10)} - c_8^{(7)*}"]; m10c4_4 --> m10c8_8["m^{(10)} - c_8^{(8)*}"]; m2c8_1 --> m2c16_1["m^{(2)} - c_{16}^{(1)}"]; m2c8_1 --> m2c16_2["m^{(2)} - c_{16}^{(2)*}"]; m2c8_2 --> m2c16_3["m^{(2)} - c_{16}^{(3)*}"]; m2c8_2 --> m2c16_4["m^{(2)} - c_{16}^{(4)*}"]; m6c8_3 --> m6c16_5["m^{(6)} - c_{16}^{(5)}"]; m6c8_3 --> m6c16_6["m^{(6)} - c_{16}^{(6)*}"]; m6c8_4 --> m6c16_7["m^{(6)} - c_{16}^{(7)*}"]; m6c8_4 --> m6c16_8["m^{(6)} - c_{16}^{(8)*}"]; m10c8_5 --> m10c16_9["m^{(10)} - c_{16}^{(9)}"]; m10c8_5 --> m10c16_10["m^{(10)} - c_{16}^{(10)*}"]; m10c8_6 --> m10c16_11["m^{(10)} - c_{16}^{(11)*}"]; m10c8_6 --> m10c16_12["m^{(10)} - c_{16}^{(12)*}"]; m10c8_7 --> m10c16_13["m^{(10)} - c_{16}^{(13)*}"]; m10c8_7 --> m10c16_14["m^{(10)} - c_{16}^{(14)*}"]; m10c8_8 --> m10c16_15["m^{(10)} - c_{16}^{(15)*}"]; m10c8_8 --> m10c16_16["m^{(10)} - c_{16}^{(16)*}"];
+```
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(6)} - c\_4^{(2)}. m^{(10)} - c\_2^{(2)} branches into m^{(10)} - c\_4^{(3)} and m^{(10)} - c\_4^{(4)}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(6)} - c\_8^{(3)}, m^{(6)} - c\_8^{(4)}, m^{(10)} - c\_8^{(5)}, m^{(10)} - c\_8^{(6)}, m^{(10)} - c\_8^{(7)}, and m^{(10)} - c\_8^{(8)}. Each of these nodes branches into two spreading codes, resulting in 16 codes: m^{(2)} - c\_{16}^{(1)}, m^{(2)} - c\_{16}^{(2)\*}, m^{(2)} - c\_{16}^{(3)\*}, m^{(2)} - c\_{16}^{(4)\*}, m^{(6)} - c\_{16}^{(5)}, m^{(6)} - c\_{16}^{(6)\*}, m^{(6)} - c\_{16}^{(7)\*}, m^{(6)} - c\_{16}^{(8)\*}, m^{(10)} - c\_{16}^{(9)}, m^{(10)} - c\_{16}^{(10)\*}, m^{(10)} - c\_{16}^{(11)\*}, m^{(10)} - c\_{16}^{(12)\*}, m^{(10)} - c\_{16}^{(13)\*}, m^{(10)} - c\_{16}^{(14)\*}, m^{(10)} - c\_{16}^{(15)\*}, and m^{(10)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.3ba: Association of Midambles to Spreading Codes for K=12 pattern 2A
+
+
+
+```
+graph LR; m4c1["m^{(4)} - c_1^{(1)}"] --> m4c2["m^{(4)} - c_2^{(1)}"]; m4c1 --> m12c2["m^{(12)} - c_2^{(2)}"]; m4c2 --> m4c4["m^{(4)} - c_4^{(1)}"]; m4c2 --> m8c4["m^{(8)} - c_4^{(2)}"]; m12c2 --> m12c4_3["m^{(12)} - c_4^{(3)}"]; m12c2 --> m12c4_4["m^{(12)} - c_4^{(4)}"]; m4c4 --> m4c8_1["m^{(4)} - c_8^{(1)}"]; m4c4 --> m4c8_2["m^{(4)} - c_8^{(2)*}"]; m8c4 --> m8c8_3["m^{(8)} - c_8^{(3)}"]; m8c4 --> m8c8_4["m^{(8)} - c_8^{(4)*}"]; m12c4_3 --> m12c8_5["m^{(12)} - c_8^{(5)}"]; m12c4_3 --> m12c8_6["m^{(12)} - c_8^{(6)*}"]; m12c4_4 --> m12c8_7["m^{(12)} - c_8^{(7)*}"]; m12c4_4 --> m12c8_8["m^{(12)} - c_8^{(8)*}"]; m4c8_1 --> m4c16_1["m^{(4)} - c_{16}^{(1)}"]; m4c8_1 --> m4c16_2["m^{(4)} - c_{16}^{(2)*}"]; m4c8_2 --> m4c16_3["m^{(4)} - c_{16}^{(3)*}"]; m4c8_2 --> m4c16_4["m^{(4)} - c_{16}^{(4)*}"]; m8c8_3 --> m8c16_5["m^{(8)} - c_{16}^{(5)}"]; m8c8_3 --> m8c16_6["m^{(8)} - c_{16}^{(6)*}"]; m8c8_4 --> m8c16_7["m^{(8)} - c_{16}^{(7)*}"]; m8c8_4 --> m8c16_8["m^{(8)} - c_{16}^{(8)*}"]; m12c8_5 --> m12c16_9["m^{(12)} - c_{16}^{(9)}"]; m12c8_5 --> m12c16_10["m^{(12)} - c_{16}^{(10)*}"]; m12c8_6 --> m12c16_11["m^{(12)} - c_{16}^{(11)*}"]; m12c8_6 --> m12c16_12["m^{(12)} - c_{16}^{(12)*}"]; m12c8_7 --> m12c16_13["m^{(12)} - c_{16}^{(13)*}"]; m12c8_7 --> m12c16_14["m^{(12)} - c_{16}^{(14)*}"]; m12c8_8 --> m12c16_15["m^{(12)} - c_{16}^{(15)*}"]; m12c8_8 --> m12c16_16["m^{(12)} - c_{16}^{(16)*}"];
+```
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(12)} - c\_2^{(2)}. m^{(4)} - c\_2^{(1)} branches into m^{(4)} - c\_4^{(1)} and m^{(8)} - c\_4^{(2)}. m^{(12)} - c\_2^{(2)} branches into m^{(12)} - c\_4^{(3)} and m^{(12)} - c\_4^{(4)}. Further branches lead to m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(8)} - c\_8^{(3)}, m^{(8)} - c\_8^{(4)\*}, m^{(12)} - c\_8^{(5)}, m^{(12)} - c\_8^{(6)\*}, m^{(12)} - c\_8^{(7)\*}, and m^{(12)} - c\_8^{(8)\*}. Each of these nodes branches into two spreading codes, resulting in 16 codes: m^{(4)} - c\_{16}^{(1)}, m^{(4)} - c\_{16}^{(2)\*}, m^{(4)} - c\_{16}^{(3)\*}, m^{(4)} - c\_{16}^{(4)\*}, m^{(8)} - c\_{16}^{(5)}, m^{(8)} - c\_{16}^{(6)\*}, m^{(8)} - c\_{16}^{(7)\*}, m^{(8)} - c\_{16}^{(8)\*}, m^{(12)} - c\_{16}^{(9)}, m^{(12)} - c\_{16}^{(10)\*}, m^{(12)} - c\_{16}^{(11)\*}, m^{(12)} - c\_{16}^{(12)\*}, m^{(12)} - c\_{16}^{(13)\*}, m^{(12)} - c\_{16}^{(14)\*}, m^{(12)} - c\_{16}^{(15)\*}, and m^{(12)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.3bb: Association of Midambles to Spreading Codes for K=12 pattern 2B
+
+### AA.3.4 Association for K=10 Midambles
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(7)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(7)} - c\_2^{(2)} branches into m^{(7)} - c\_4^{(3)} and m^{(9)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(3)} - c\_8^{(2)}, m^{(5)} - c\_8^{(3)}, m^{(5)} - c\_8^{(4)}, m^{(7)} - c\_8^{(5)}, m^{(7)} - c\_8^{(6)}, m^{(9)} - c\_8^{(7)}, and m^{(9)} - c\_8^{(8)}. Each of these nodes branches into two spreading codes, such as m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, m^{(3)} - c\_{16}^{(3)}, m^{(3)} - c\_{16}^{(4)\*}, m^{(5)} - c\_{16}^{(5)}, m^{(5)} - c\_{16}^{(6)\*}, m^{(5)} - c\_{16}^{(7)\*}, m^{(5)} - c\_{16}^{(8)\*}, m^{(7)} - c\_{16}^{(9)}, m^{(7)} - c\_{16}^{(10)\*}, m^{(7)} - c\_{16}^{(11)\*}, m^{(7)} - c\_{16}^{(12)\*}, m^{(9)} - c\_{16}^{(13)}, m^{(9)} - c\_{16}^{(14)\*}, m^{(9)} - c\_{16}^{(15)\*}, and m^{(9)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.4a: Association of Midambles to Spreading Codes for K=10 pattern 1
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1A. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} and m^{(9)} - c\_4^{(4)\*}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)}, m^{(5)} - c\_8^{(3)}, m^{(5)} - c\_8^{(4)}, m^{(9)} - c\_8^{(5)}, m^{(9)} - c\_8^{(6)}, m^{(9)} - c\_8^{(7)}, and m^{(9)} - c\_8^{(8)\*}. Each of these nodes branches into two spreading codes, such as m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, m^{(1)} - c\_{16}^{(3)\*}, m^{(1)} - c\_{16}^{(4)\*}, m^{(5)} - c\_{16}^{(5)}, m^{(5)} - c\_{16}^{(6)\*}, m^{(5)} - c\_{16}^{(7)\*}, m^{(5)} - c\_{16}^{(8)\*}, m^{(9)} - c\_{16}^{(9)}, m^{(9)} - c\_{16}^{(10)\*}, m^{(9)} - c\_{16}^{(11)\*}, m^{(9)} - c\_{16}^{(12)\*}, m^{(9)} - c\_{16}^{(13)\*}, m^{(9)} - c\_{16}^{(14)\*}, m^{(9)} - c\_{16}^{(15)\*}, and m^{(9)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.4aa: Association of Midambles to Spreading Codes for K=10 pattern 1A
+
+Error:
+
+112
+
+Error: Reference source not
+
+
+
+The diagram is a hierarchical tree structure showing the mapping of midambles \$m^{(k)}\$ to spreading codes \$c\_{Q}^{(n)}\$.
+
+- Level 1: \$m^{(3)} - c\_{1}^{(1)}\$
+- Level 2 branches:
+ - \$m^{(3)} - c\_{2}^{(1)}\$ branches to:
+ - \$m^{(3)} - c\_{4}^{(1)}\$ branches to \$m^{(3)} - c\_{8}^{(1)}\$ and \$m^{(3)} - c\_{8}^{(2)\*}\$
+ - \$m^{(3)} - c\_{4}^{(2)\*}\$ branches to \$m^{(3)} - c\_{8}^{(3)\*}\$ and \$m^{(3)} - c\_{8}^{(4)\*}\$
+ - \$m^{(7)} - c\_{2}^{(2)}\$ branches to:
+ - \$m^{(7)} - c\_{4}^{(3)}\$ branches to \$m^{(7)} - c\_{8}^{(5)}\$ and \$m^{(7)} - c\_{8}^{(6)\*}\$
+ - \$m^{(7)} - c\_{4}^{(4)\*}\$ branches to \$m^{(7)} - c\_{8}^{(7)\*}\$ and \$m^{(7)} - c\_{8}^{(8)\*}\$
+- Level 16 leaf nodes (from top to bottom): \$m^{(3)} - c\_{16}^{(1)}\$, \$m^{(3)} - c\_{16}^{(2)\*}\$, \$m^{(3)} - c\_{16}^{(3)\*}\$, \$m^{(3)} - c\_{16}^{(4)\*}\$, \$m^{(3)} - c\_{16}^{(5)\*}\$, \$m^{(3)} - c\_{16}^{(6)\*}\$, \$m^{(3)} - c\_{16}^{(7)\*}\$, \$m^{(3)} - c\_{16}^{(8)\*}\$, \$m^{(7)} - c\_{16}^{(9)}\$, \$m^{(7)} - c\_{16}^{(10)\*}\$, \$m^{(7)} - c\_{16}^{(11)\*}\$, \$m^{(7)} - c\_{16}^{(12)\*}\$, \$m^{(7)} - c\_{16}^{(13)\*}\$, \$m^{(7)} - c\_{16}^{(14)\*}\$, \$m^{(7)} - c\_{16}^{(15)\*}\$, \$m^{(7)} - c\_{16}^{(16)\*}\$.
+
+Tree diagram showing the association of midambles to spreading codes for K=10 pattern 1B.
+
+**Figure AA.3.4ab: Association of Midambles to Spreading Codes for K=10 pattern 1B**
+
+
+
+The diagram is a hierarchical tree structure showing the mapping of midambles \$m^{(k)}\$ to spreading codes \$c\_{Q}^{(n)}\$ for pattern 2.
+
+- Level 1: \$m^{(2)} - c\_{1}^{(1)}\$
+- Level 2 branches:
+ - \$m^{(2)} - c\_{2}^{(1)}\$ branches to:
+ - \$m^{(2)} - c\_{4}^{(1)}\$ branches to \$m^{(2)} - c\_{8}^{(1)}\$ and \$m^{(4)} - c\_{8}^{(2)}\$
+ - \$m^{(6)} - c\_{4}^{(2)}\$ branches to \$m^{(6)} - c\_{8}^{(3)}\$ and \$m^{(6)} - c\_{8}^{(4)\*}\$
+ - \$m^{(8)} - c\_{2}^{(2)}\$ branches to:
+ - \$m^{(8)} - c\_{4}^{(3)}\$ branches to \$m^{(8)} - c\_{8}^{(5)}\$ and \$m^{(8)} - c\_{8}^{(6)\*}\$
+ - \$m^{(10)} - c\_{4}^{(4)}\$ branches to \$m^{(10)} - c\_{8}^{(7)}\$ and \$m^{(10)} - c\_{8}^{(8)\*}\$
+- Level 16 leaf nodes (from top to bottom): \$m^{(2)} - c\_{16}^{(1)}\$, \$m^{(2)} - c\_{16}^{(2)\*}\$, \$m^{(4)} - c\_{16}^{(3)}\$, \$m^{(4)} - c\_{16}^{(4)\*}\$, \$m^{(6)} - c\_{16}^{(5)}\$, \$m^{(6)} - c\_{16}^{(6)\*}\$, \$m^{(6)} - c\_{16}^{(7)\*}\$, \$m^{(6)} - c\_{16}^{(8)\*}\$, \$m^{(8)} - c\_{16}^{(9)}\$, \$m^{(8)} - c\_{16}^{(10)\*}\$, \$m^{(8)} - c\_{16}^{(11)\*}\$, \$m^{(8)} - c\_{16}^{(12)\*}\$, \$m^{(10)} - c\_{16}^{(13)}\$, \$m^{(10)} - c\_{16}^{(14)\*}\$, \$m^{(10)} - c\_{16}^{(15)\*}\$, \$m^{(10)} - c\_{16}^{(16)\*}\$.
+
+Tree diagram showing the association of midambles to spreading codes for K=10 pattern 2.
+
+**Figure AA.3.4b: Association of Midambles to Spreading Codes for K=10 pattern 2**
+
+
+
+This tree diagram illustrates the association of Midambles to Spreading Codes for K=10 pattern 2A. The root node is $m^{(2)} - c_1^{(1)}$ . It branches into two main paths: $m^{(2)} - c_2^{(1)}$ and $m^{(10)} - c_2^{(2)}$ . The $m^{(2)} - c_2^{(1)}$ path further branches into $m^{(2)} - c_4^{(1)}$ and $m^{(6)} - c_4^{(2)}$ . The $m^{(2)} - c_4^{(1)}$ path leads to $m^{(2)} - c_8^{(1)}$ and $m^{(2)} - c_8^{(2)}$ , which further lead to spreading codes $c_{16}^{(1)}$ , $c_{16}^{(2)*}$ , $c_{16}^{(3)*}$ , and $c_{16}^{(4)*}$ . The $m^{(6)} - c_4^{(2)}$ path leads to $m^{(6)} - c_8^{(3)}$ and $m^{(6)} - c_8^{(4)*}$ , which further lead to spreading codes $c_{16}^{(5)}$ , $c_{16}^{(6)*}$ , $c_{16}^{(7)*}$ , and $c_{16}^{(8)*}$ . The $m^{(10)} - c_2^{(2)}$ path branches into $m^{(10)} - c_4^{(3)}$ and $m^{(10)} - c_4^{(4)*}$ . The $m^{(10)} - c_4^{(3)}$ path leads to $m^{(10)} - c_8^{(5)}$ and $m^{(10)} - c_8^{(6)*}$ , which further lead to spreading codes $c_{16}^{(9)}$ , $c_{16}^{(10)*}$ , $c_{16}^{(11)*}$ , and $c_{16}^{(12)*}$ . The $m^{(10)} - c_4^{(4)*}$ path leads to $m^{(10)} - c_8^{(7)*}$ and $m^{(10)} - c_8^{(8)*}$ , which further lead to spreading codes $c_{16}^{(13)*}$ , $c_{16}^{(14)*}$ , $c_{16}^{(15)*}$ , and $c_{16}^{(16)*}$ .
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2A. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(10) - c\_2^(2). Further sub-nodes include m^(2) - c\_4^(1), m^(6) - c\_4^(2), m^(10) - c\_4^(3), and m^(10) - c\_4^(4), leading to various spreading codes c\_16.
+
+**Figure AA.3.4ba: Association of Midambles to Spreading Codes for K=10 pattern 2A**
+
+
+
+This tree diagram illustrates the association of Midambles to Spreading Codes for K=10 pattern 2B. The root node is $m^{(4)} - c_1^{(1)}$ . It branches into two main paths: $m^{(4)} - c_2^{(1)}$ and $m^{(8)} - c_2^{(2)}$ . The $m^{(4)} - c_2^{(1)}$ path further branches into $m^{(4)} - c_4^{(1)}$ and $m^{(4)} - c_4^{(2)*}$ . The $m^{(4)} - c_4^{(1)}$ path leads to $m^{(4)} - c_8^{(1)}$ and $m^{(4)} - c_8^{(2)*}$ , which further lead to spreading codes $c_{16}^{(1)}$ , $c_{16}^{(2)*}$ , $c_{16}^{(3)*}$ , and $c_{16}^{(4)*}$ . The $m^{(4)} - c_4^{(2)*}$ path leads to $m^{(4)} - c_8^{(3)*}$ and $m^{(4)} - c_8^{(4)*}$ , which further lead to spreading codes $c_{16}^{(5)*}$ , $c_{16}^{(6)*}$ , $c_{16}^{(7)*}$ , and $c_{16}^{(8)*}$ . The $m^{(8)} - c_2^{(2)}$ path branches into $m^{(8)} - c_4^{(3)}$ and $m^{(8)} - c_4^{(4)*}$ . The $m^{(8)} - c_4^{(3)}$ path leads to $m^{(8)} - c_8^{(5)}$ and $m^{(8)} - c_8^{(6)*}$ , which further lead to spreading codes $c_{16}^{(9)}$ , $c_{16}^{(10)*}$ , $c_{16}^{(11)*}$ , and $c_{16}^{(12)*}$ . The $m^{(8)} - c_4^{(4)*}$ path leads to $m^{(8)} - c_8^{(7)*}$ and $m^{(8)} - c_8^{(8)*}$ , which further lead to spreading codes $c_{16}^{(13)*}$ , $c_{16}^{(14)*}$ , $c_{16}^{(15)*}$ , and $c_{16}^{(16)*}$ .
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2B. The root node is m^(4) - c\_1^(1), which branches into m^(4) - c\_2^(1) and m^(8) - c\_2^(2). Further sub-nodes include m^(4) - c\_4^(1), m^(4) - c\_4^(2), m^(8) - c\_4^(3), and m^(8) - c\_4^(4), leading to various spreading codes c\_16.
+
+**Figure AA.3.4bb: Association of Midambles to Spreading Codes for K=10 pattern 2B**
+
+### AA.3.5 Association for K=8 Midambles
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=8 pattern 1. The hierarchy starts with $m^{(1)} - c_1^{(1)}$ , which branches into $m^{(1)} - c_2^{(1)}$ and $m^{(5)} - c_2^{(2)}$ .
+ The $m^{(1)} - c_2^{(1)}$ branch splits into $m^{(1)} - c_4^{(1)}$ and $m^{(3)} - c_4^{(2)}$ .
+ The $m^{(5)} - c_2^{(2)}$ branch splits into $m^{(5)} - c_4^{(3)}$ and $m^{(7)} - c_4^{(4)}$ .
+ At the next level, nodes like $m^{(1)} - c_8^{(1)}$ and $m^{(1)} - c_8^{(2)*}$ appear, eventually leading to 16 leaf nodes representing spreading codes $c_{16}^{(1)}$ through $c_{16}^{(16)*}$ associated with midambles $m^{(1)}, m^{(3)}, m^{(5)},$ and $m^{(7)}$ .
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(3)} - c\_8^{(3)}, m^{(3)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(7)} - c\_8^{(7)}, m^{(7)} - c\_8^{(8)\*}. Each of these leads to two spreading codes at the c\_{16} level.
+
+Figure AA.3.5a: Association of Midambles to Spreading Codes for K=8 pattern 1
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=8 pattern 1A. The hierarchy starts with $m^{(1)} - c_1^{(1)}$ , which branches into $m^{(1)} - c_2^{(1)}$ and $m^{(5)} - c_2^{(2)}$ .
+ The $m^{(1)} - c_2^{(1)}$ branch splits into $m^{(1)} - c_4^{(1)}$ and $m^{(1)} - c_4^{(2)*}$ .
+ The $m^{(5)} - c_2^{(2)}$ branch splits into $m^{(5)} - c_4^{(3)}$ and $m^{(5)} - c_4^{(4)*}$ .
+ This pattern continues, with the upper half of the tree associated with midamble $m^{(1)}$ and the lower half with $m^{(5)}$ , leading to leaf nodes $c_{16}^{(1)}$ through $c_{16}^{(16)*}$ .
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 1A. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(1)} - c\_4^{(2)\*}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(5)} - c\_4^{(4)\*}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(1)} - c\_8^{(3)\*}, m^{(1)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(5)} - c\_8^{(7)\*}, m^{(5)} - c\_8^{(8)\*}. Each of these leads to two spreading codes at the c\_{16} level.
+
+Figure AA.3.5aa: Association of Midambles to Spreading Codes for K=8 pattern 1A
+
+Error:
+
+115
+
+Error: Reference source not
+
+
+
+```
+graph LR; m3c11["m^(3) - c_1^(1)"] --> m3c21["m^(3) - c_2^(1)"]; m3c11 --> m7c22["m^(7) - c_2^(2)"]; m3c21 --> m3c41["m^(3) - c_4^(1)"]; m3c21 --> m3c42["m^(3) - c_4^(2)"]; m7c22 --> m7c43["m^(7) - c_4^(3)"]; m7c22 --> m7c44["m^(7) - c_4^(4)"]; m3c41 --> m3c81["m^(3) - c_8^(1)"]; m3c41 --> m3c82["m^(3) - c_8^(2)"]; m3c42 --> m3c83["m^(3) - c_8^(3)"]; m3c42 --> m3c84["m^(3) - c_8^(4)"]; m7c43 --> m7c85["m^(7) - c_8^(5)"]; m7c43 --> m7c86["m^(7) - c_8^(6)"]; m7c44 --> m7c87["m^(7) - c_8^(7)"]; m7c44 --> m7c88["m^(7) - c_8^(8)"]; m3c81 --> m3c16_1["m^(3) - c_16^(1)"]; m3c81 --> m3c16_2["m^(3) - c_16^(2)*"]; m3c82 --> m3c16_3["m^(3) - c_16^(3)*"]; m3c82 --> m3c16_4["m^(3) - c_16^(4)*"]; m3c83 --> m3c16_5["m^(3) - c_16^(5)*"]; m3c83 --> m3c16_6["m^(3) - c_16^(6)*"]; m3c84 --> m3c16_7["m^(3) - c_16^(7)*"]; m3c84 --> m3c16_8["m^(3) - c_16^(8)*"]; m7c85 --> m7c16_9["m^(7) - c_16^(9)"]; m7c85 --> m7c16_10["m^(7) - c_16^(10)*"]; m7c86 --> m7c16_11["m^(7) - c_16^(11)*"]; m7c86 --> m7c16_12["m^(7) - c_16^(12)*"]; m7c87 --> m7c16_13["m^(7) - c_16^(13)*"]; m7c87 --> m7c16_14["m^(7) - c_16^(14)*"]; m7c88 --> m7c16_15["m^(7) - c_16^(15)*"]; m7c88 --> m7c16_16["m^(7) - c_16^(16)*"];
+```
+
+Tree diagram showing the association of midambles to spreading codes for K=8 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(7) - c\_2^(2). Further sub-nodes include m^(3) - c\_4^(1), m^(3) - c\_4^(2), m^(7) - c\_4^(3), m^(7) - c\_4^(4), m^(3) - c\_8^(1), m^(3) - c\_8^(2), m^(3) - c\_8^(3), m^(3) - c\_8^(4), m^(7) - c\_8^(5), m^(7) - c\_8^(6), m^(7) - c\_8^(7), m^(7) - c\_8^(8), and finally 16 spreading codes c\_16^(1) through c\_16^(16) with their respective midamble associations.
+
+Figure AA.3.5ab: Association of Midambles to Spreading Codes for K=8 pattern 1B
+
+
+
+```
+graph LR; m2c11["m^(2) - c_1^(1)"] --> m2c21["m^(2) - c_2^(1)"]; m2c11 --> m6c22["m^(6) - c_2^(2)"]; m2c21 --> m2c41["m^(2) - c_4^(1)"]; m2c21 --> m4c42["m^(4) - c_4^(2)"]; m6c22 --> m6c43["m^(6) - c_4^(3)"]; m6c22 --> m8c44["m^(8) - c_4^(4)"]; m2c41 --> m2c81["m^(2) - c_8^(1)"]; m2c41 --> m2c82["m^(2) - c_8^(2)"]; m4c42 --> m4c83["m^(4) - c_8^(3)"]; m4c42 --> m4c84["m^(4) - c_8^(4)"]; m6c43 --> m6c85["m^(6) - c_8^(5)"]; m6c43 --> m6c86["m^(6) - c_8^(6)"]; m8c44 --> m8c87["m^(8) - c_8^(7)"]; m8c44 --> m8c88["m^(8) - c_8^(8)"]; m2c81 --> m2c16_1["m^(2) - c_16^(1)"]; m2c81 --> m2c16_2["m^(2) - c_16^(2)*"]; m2c82 --> m2c16_3["m^(2) - c_16^(3)*"]; m2c82 --> m2c16_4["m^(2) - c_16^(4)*"]; m4c83 --> m4c16_5["m^(4) - c_16^(5)"]; m4c83 --> m4c16_6["m^(4) - c_16^(6)*"]; m4c84 --> m4c16_7["m^(4) - c_16^(7)*"]; m4c84 --> m4c16_8["m^(4) - c_16^(8)*"]; m6c85 --> m6c16_9["m^(6) - c_16^(9)"]; m6c85 --> m6c16_10["m^(6) - c_16^(10)*"]; m6c86 --> m6c16_11["m^(6) - c_16^(11)*"]; m6c86 --> m6c16_12["m^(6) - c_16^(12)*"]; m8c87 --> m8c16_13["m^(8) - c_16^(13)"]; m8c87 --> m8c16_14["m^(8) - c_16^(14)*"]; m8c88 --> m8c16_15["m^(8) - c_16^(15)*"]; m8c88 --> m8c16_16["m^(8) - c_16^(16)*"];
+```
+
+Tree diagram showing the association of midambles to spreading codes for K=8 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(6) - c\_2^(2). Further sub-nodes include m^(2) - c\_4^(1), m^(4) - c\_4^(2), m^(6) - c\_4^(3), m^(8) - c\_4^(4), m^(2) - c\_8^(1), m^(2) - c\_8^(2), m^(4) - c\_8^(3), m^(4) - c\_8^(4), m^(6) - c\_8^(5), m^(6) - c\_8^(6), m^(8) - c\_8^(7), m^(8) - c\_8^(8), and finally 16 spreading codes c\_16^(1) through c\_16^(16) with their respective midamble associations.
+
+Figure AA.3.5b: Association of Midambles to Spreading Codes for K=8 pattern 2
+
+
+
+```
+graph LR; m2c1["m^{(2)} - c_1^{(1)}"] --> m2c2_1["m^{(2)} - c_2^{(1)}"]; m2c1 --> m6c2_2["m^{(6)} - c_2^{(2)}"]; m2c2_1 --> m2c4_1["m^{(2)} - c_4^{(1)}"]; m2c2_1 --> m2c4_2["m^{(2)} - c_4^{(2)*}"]; m6c2_2 --> m6c4_3["m^{(6)} - c_4^{(3)}"]; m6c2_2 --> m6c4_4["m^{(6)} - c_4^{(4)*}"]; m2c4_1 --> m2c8_1["m^{(2)} - c_8^{(1)}"]; m2c4_1 --> m2c8_2["m^{(2)} - c_8^{(2)*}"]; m2c4_2 --> m2c8_3["m^{(2)} - c_8^{(3)*}"]; m2c4_2 --> m2c8_4["m^{(2)} - c_8^{(4)*}"]; m6c4_3 --> m6c8_5["m^{(6)} - c_8^{(5)}"]; m6c4_3 --> m6c8_6["m^{(6)} - c_8^{(6)*}"]; m6c4_4 --> m6c8_7["m^{(6)} - c_8^{(7)*}"]; m6c4_4 --> m6c8_8["m^{(6)} - c_8^{(8)*}"]; m2c8_1 --> m2c16_1["m^{(2)} - c_{16}^{(1)}"]; m2c8_1 --> m2c16_2["m^{(2)} - c_{16}^{(2)*}"]; m2c8_2 --> m2c16_3["m^{(2)} - c_{16}^{(3)*}"]; m2c8_2 --> m2c16_4["m^{(2)} - c_{16}^{(4)*}"]; m2c8_3 --> m2c16_5["m^{(2)} - c_{16}^{(5)*}"]; m2c8_3 --> m2c16_6["m^{(2)} - c_{16}^{(6)*}"]; m2c8_4 --> m2c16_7["m^{(2)} - c_{16}^{(7)*}"]; m2c8_4 --> m2c16_8["m^{(2)} - c_{16}^{(8)*}"]; m6c8_5 --> m6c16_9["m^{(6)} - c_{16}^{(9)}"]; m6c8_5 --> m6c16_10["m^{(6)} - c_{16}^{(10)*}"]; m6c8_6 --> m6c16_11["m^{(6)} - c_{16}^{(11)*}"]; m6c8_6 --> m6c16_12["m^{(6)} - c_{16}^{(12)*}"]; m6c8_7 --> m6c16_13["m^{(6)} - c_{16}^{(13)*}"]; m6c8_7 --> m6c16_14["m^{(6)} - c_{16}^{(14)*}"]; m6c8_8 --> m6c16_15["m^{(6)} - c_{16}^{(15)*}"]; m6c8_8 --> m6c16_16["m^{(6)} - c_{16}^{(16)*}"];
+```
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(6)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(2)} - c\_4^{(2)\*}. m^{(6)} - c\_2^{(2)} branches into m^{(6)} - c\_4^{(3)} and m^{(6)} - c\_4^{(4)\*}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)\*}, m^{(2)} - c\_8^{(3)\*}, m^{(2)} - c\_8^{(4)\*}, m^{(6)} - c\_8^{(5)}, m^{(6)} - c\_8^{(6)\*}, m^{(6)} - c\_8^{(7)\*}, and m^{(6)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes: m^{(2)} - c\_{16}^{(1)}, m^{(2)} - c\_{16}^{(2)\*}, m^{(2)} - c\_{16}^{(3)\*}, m^{(2)} - c\_{16}^{(4)\*}, m^{(2)} - c\_{16}^{(5)\*}, m^{(2)} - c\_{16}^{(6)\*}, m^{(2)} - c\_{16}^{(7)\*}, m^{(2)} - c\_{16}^{(8)\*}, m^{(6)} - c\_{16}^{(9)}, m^{(6)} - c\_{16}^{(10)\*}, m^{(6)} - c\_{16}^{(11)\*}, m^{(6)} - c\_{16}^{(12)\*}, m^{(6)} - c\_{16}^{(13)\*}, m^{(6)} - c\_{16}^{(14)\*}, m^{(6)} - c\_{16}^{(15)\*}, and m^{(6)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.5ba: Association of Midambles to Spreading Codes for K=8 pattern 2A
+
+
+
+```
+graph LR; m4c1["m^{(4)} - c_1^{(1)}"] --> m4c2_1["m^{(4)} - c_2^{(1)}"]; m4c1 --> m8c2_2["m^{(8)} - c_2^{(2)}"]; m4c2_1 --> m4c4_1["m^{(4)} - c_4^{(1)}"]; m4c2_1 --> m4c4_2["m^{(4)} - c_4^{(2)*}"]; m8c2_2 --> m8c4_3["m^{(8)} - c_4^{(3)}"]; m8c2_2 --> m8c4_4["m^{(8)} - c_4^{(4)*}"]; m4c4_1 --> m4c8_1["m^{(4)} - c_8^{(1)}"]; m4c4_1 --> m4c8_2["m^{(4)} - c_8^{(2)*}"]; m4c4_2 --> m4c8_3["m^{(4)} - c_8^{(3)*}"]; m4c4_2 --> m4c8_4["m^{(4)} - c_8^{(4)*}"]; m8c4_3 --> m8c8_5["m^{(8)} - c_8^{(5)}"]; m8c4_3 --> m8c8_6["m^{(8)} - c_8^{(6)*}"]; m8c4_4 --> m8c8_7["m^{(8)} - c_8^{(7)*}"]; m8c4_4 --> m8c8_8["m^{(8)} - c_8^{(8)*}"]; m4c8_1 --> m4c16_1["m^{(4)} - c_{16}^{(1)}"]; m4c8_1 --> m4c16_2["m^{(4)} - c_{16}^{(2)*}"]; m4c8_2 --> m4c16_3["m^{(4)} - c_{16}^{(3)*}"]; m4c8_2 --> m4c16_4["m^{(4)} - c_{16}^{(4)*}"]; m4c8_3 --> m4c16_5["m^{(4)} - c_{16}^{(5)*}"]; m4c8_3 --> m4c16_6["m^{(4)} - c_{16}^{(6)*}"]; m4c8_4 --> m4c16_7["m^{(4)} - c_{16}^{(7)*}"]; m4c8_4 --> m4c16_8["m^{(4)} - c_{16}^{(8)*}"]; m8c8_5 --> m8c16_9["m^{(8)} - c_{16}^{(9)}"]; m8c8_5 --> m8c16_10["m^{(8)} - c_{16}^{(10)*}"]; m8c8_6 --> m8c16_11["m^{(8)} - c_{16}^{(11)*}"]; m8c8_6 --> m8c16_12["m^{(8)} - c_{16}^{(12)*}"]; m8c8_7 --> m8c16_13["m^{(8)} - c_{16}^{(13)*}"]; m8c8_7 --> m8c16_14["m^{(8)} - c_{16}^{(14)*}"]; m8c8_8 --> m8c16_15["m^{(8)} - c_{16}^{(15)*}"]; m8c8_8 --> m8c16_16["m^{(8)} - c_{16}^{(16)*}"];
+```
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(8)} - c\_2^{(2)}. m^{(4)} - c\_2^{(1)} branches into m^{(4)} - c\_4^{(1)} and m^{(4)} - c\_4^{(2)\*}. m^{(8)} - c\_2^{(2)} branches into m^{(8)} - c\_4^{(3)} and m^{(8)} - c\_4^{(4)\*}. Further branches lead to m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(4)} - c\_8^{(3)\*}, m^{(4)} - c\_8^{(4)\*}, m^{(8)} - c\_8^{(5)}, m^{(8)} - c\_8^{(6)\*}, m^{(8)} - c\_8^{(7)\*}, and m^{(8)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes: m^{(4)} - c\_{16}^{(1)}, m^{(4)} - c\_{16}^{(2)\*}, m^{(4)} - c\_{16}^{(3)\*}, m^{(4)} - c\_{16}^{(4)\*}, m^{(4)} - c\_{16}^{(5)\*}, m^{(4)} - c\_{16}^{(6)\*}, m^{(4)} - c\_{16}^{(7)\*}, m^{(4)} - c\_{16}^{(8)\*}, m^{(8)} - c\_{16}^{(9)}, m^{(8)} - c\_{16}^{(10)\*}, m^{(8)} - c\_{16}^{(11)\*}, m^{(8)} - c\_{16}^{(12)\*}, m^{(8)} - c\_{16}^{(13)\*}, m^{(8)} - c\_{16}^{(14)\*}, m^{(8)} - c\_{16}^{(15)\*}, and m^{(8)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.5bb: Association of Midambles to Spreading Codes for K=8 pattern 2B
+
+### AA.3.6 Association for K=6 Midambles
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=6 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(5)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(3)} - c\_8^{(3)}, m^{(3)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(5)} - c\_8^{(7)\*}, and m^{(5)} - c\_8^{(8)\*}. Each of these leads to two spreading codes, such as m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, etc.
+
+Figure AA.3.6a: Association of Midambles to Spreading Codes for K=6 pattern 1
+
+
+
+Tree diagram showing the association of Midambles to Spreading Codes for K=6 pattern 1A. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(1)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(5)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(1)} - c\_8^{(3)\*}, m^{(1)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(5)} - c\_8^{(7)\*}, and m^{(5)} - c\_8^{(8)\*}. Each of these leads to two spreading codes, such as m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, etc.
+
+Figure AA.3.6aa: Association of Midambles to Spreading Codes for K=6 pattern 1A
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=6 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(3) - c\_2^(2). m^(3) - c\_2^(1) branches into m^(3) - c\_4^(1) and m^(3) - c\_4^(2). m^(3) - c\_4^(1) branches into m^(3) - c\_8^(1) and m^(3) - c\_8^(2). m^(3) - c\_8^(1) branches into m^(3) - c\_16^(1) and m^(3) - c\_16^(2)\*. m^(3) - c\_8^(2) branches into m^(3) - c\_16^(3)\* and m^(3) - c\_16^(4)\*. m^(3) - c\_4^(2) branches into m^(3) - c\_8^(3)\* and m^(3) - c\_8^(4)\*. m^(3) - c\_8^(3)\* branches into m^(3) - c\_16^(5)\* and m^(3) - c\_16^(6)\*. m^(3) - c\_8^(4)\* branches into m^(3) - c\_16^(7)\* and m^(3) - c\_16^(8)\*. m^(3) - c\_2^(2) branches into m^(3) - c\_4^(3)\* and m^(3) - c\_4^(4)\*. m^(3) - c\_4^(3)\* branches into m^(3) - c\_8^(5)\* and m^(3) - c\_8^(6)\*. m^(3) - c\_8^(5)\* branches into m^(3) - c\_16^(9)\* and m^(3) - c\_16^(10)\*. m^(3) - c\_8^(6)\* branches into m^(3) - c\_16^(11)\* and m^(3) - c\_16^(12)\*. m^(3) - c\_4^(4)\* branches into m^(3) - c\_8^(7)\* and m^(3) - c\_8^(8)\*. m^(3) - c\_8^(7)\* branches into m^(3) - c\_16^(13)\* and m^(3) - c\_16^(14)\*. m^(3) - c\_8^(8)\* branches into m^(3) - c\_16^(15)\* and m^(3) - c\_16^(16)\*.
+
+Figure AA.3.6ab: Association of Midambles to Spreading Codes for K=6 pattern 1B
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=6 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(6) - c\_2^(2). m^(2) - c\_2^(1) branches into m^(2) - c\_4^(1) and m^(4) - c\_4^(2). m^(2) - c\_4^(1) branches into m^(2) - c\_8^(1) and m^(2) - c\_8^(2). m^(2) - c\_8^(1) branches into m^(2) - c\_16^(1) and m^(2) - c\_16^(2)\*. m^(2) - c\_8^(2) branches into m^(2) - c\_16^(3)\* and m^(2) - c\_16^(4)\*. m^(4) - c\_4^(2) branches into m^(4) - c\_8^(3) and m^(4) - c\_8^(4). m^(4) - c\_8^(3) branches into m^(4) - c\_16^(5) and m^(4) - c\_16^(6)\*. m^(4) - c\_8^(4) branches into m^(4) - c\_16^(7)\* and m^(4) - c\_16^(8)\*. m^(6) - c\_2^(2) branches into m^(6) - c\_4^(3) and m^(6) - c\_4^(4)\*. m^(6) - c\_4^(3) branches into m^(6) - c\_8^(5) and m^(6) - c\_8^(6)\*. m^(6) - c\_8^(5) branches into m^(6) - c\_16^(9) and m^(6) - c\_16^(10)\*. m^(6) - c\_8^(6)\* branches into m^(6) - c\_16^(11)\* and m^(6) - c\_16^(12)\*. m^(6) - c\_4^(4)\* branches into m^(6) - c\_8^(7)\* and m^(6) - c\_8^(8)\*. m^(6) - c\_8^(7)\* branches into m^(6) - c\_16^(13)\* and m^(6) - c\_16^(14)\*. m^(6) - c\_8^(8)\* branches into m^(6) - c\_16^(15)\* and m^(6) - c\_16^(16)\*.
+
+Figure AA.3.6b: Association of Midambles to Spreading Codes for K=6 pattern 2
+
+
+
+```
+graph LR; m2c1["m^{(2)} - c_1^{(1)}"] --> m2c2_1["m^{(2)} - c_2^{(1)}"]; m2c1 --> m6c2_2["m^{(6)} - c_2^{(2)}"]; m2c2_1 --> m2c4_1["m^{(2)} - c_4^{(1)}"]; m2c2_1 --> m2c4_2["m^{(2)} - c_4^{(2)*}"]; m6c2_2 --> m6c4_3["m^{(6)} - c_4^{(3)}"]; m6c2_2 --> m6c4_4["m^{(6)} - c_4^{(4)*}"]; m2c4_1 --> m2c8_1["m^{(2)} - c_8^{(1)}"]; m2c4_1 --> m2c8_2["m^{(2)} - c_8^{(2)*}"]; m2c4_2 --> m2c8_3["m^{(2)} - c_8^{(3)*}"]; m2c4_2 --> m2c8_4["m^{(2)} - c_8^{(4)*}"]; m6c4_3 --> m6c8_5["m^{(6)} - c_8^{(5)*}"]; m6c4_3 --> m6c8_6["m^{(6)} - c_8^{(6)*}"]; m6c4_4 --> m6c8_7["m^{(6)} - c_8^{(7)*}"]; m6c4_4 --> m6c8_8["m^{(6)} - c_8^{(8)*}"]; m2c8_1 --> m2c16_1["m^{(2)} - c_{16}^{(1)}"]; m2c8_1 --> m2c16_2["m^{(2)} - c_{16}^{(2)*}"]; m2c8_2 --> m2c16_3["m^{(2)} - c_{16}^{(3)*}"]; m2c8_2 --> m2c16_4["m^{(2)} - c_{16}^{(4)*}"]; m2c8_3 --> m2c16_5["m^{(2)} - c_{16}^{(5)*}"]; m2c8_3 --> m2c16_6["m^{(2)} - c_{16}^{(6)*}"]; m2c8_4 --> m2c16_7["m^{(2)} - c_{16}^{(7)*}"]; m2c8_4 --> m2c16_8["m^{(2)} - c_{16}^{(8)*}"]; m6c8_5 --> m6c16_9["m^{(6)} - c_{16}^{(9)*}"]; m6c8_5 --> m6c16_10["m^{(6)} - c_{16}^{(10)*}"]; m6c8_6 --> m6c16_11["m^{(6)} - c_{16}^{(11)*}"]; m6c8_6 --> m6c16_12["m^{(6)} - c_{16}^{(12)*}"]; m6c8_7 --> m6c16_13["m^{(6)} - c_{16}^{(13)*}"]; m6c8_7 --> m6c16_14["m^{(6)} - c_{16}^{(14)*}"]; m6c8_8 --> m6c16_15["m^{(6)} - c_{16}^{(15)*}"]; m6c8_8 --> m6c16_16["m^{(6)} - c_{16}^{(16)*}"];
+```
+
+Tree diagram showing the association of midambles to spreading codes for K=6 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(6)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(2)} - c\_4^{(2)\*}. m^{(6)} - c\_2^{(2)} branches into m^{(6)} - c\_4^{(3)} and m^{(6)} - c\_4^{(4)\*}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)\*}, m^{(2)} - c\_8^{(3)\*}, m^{(2)} - c\_8^{(4)\*}, m^{(6)} - c\_8^{(5)\*}, m^{(6)} - c\_8^{(6)\*}, m^{(6)} - c\_8^{(7)\*}, and m^{(6)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(2)} - c\_{16}^{(1)} through m^{(6)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.6ba: Association of Midambles to Spreading Codes for K=6 pattern 2A
+
+
+
+```
+graph LR; m4c1["m^{(4)} - c_1^{(1)}"] --> m4c2_1["m^{(4)} - c_2^{(1)}"]; m4c1 --> m4c2_2["m^{(4)} - c_2^{(2)*}"]; m4c2_1 --> m4c4_1["m^{(4)} - c_4^{(1)}"]; m4c2_1 --> m4c4_2["m^{(4)} - c_4^{(2)*}"]; m4c2_2 --> m4c4_3["m^{(4)} - c_4^{(3)}"]; m4c2_2 --> m4c4_4["m^{(4)} - c_4^{(4)*}"]; m4c4_1 --> m4c8_1["m^{(4)} - c_8^{(1)}"]; m4c4_1 --> m4c8_2["m^{(4)} - c_8^{(2)*}"]; m4c4_2 --> m4c8_3["m^{(4)} - c_8^{(3)*}"]; m4c4_2 --> m4c8_4["m^{(4)} - c_8^{(4)*}"]; m4c4_3 --> m4c8_5["m^{(4)} - c_8^{(5)*}"]; m4c4_3 --> m4c8_6["m^{(4)} - c_8^{(6)*}"]; m4c4_4 --> m4c8_7["m^{(4)} - c_8^{(7)*}"]; m4c4_4 --> m4c8_8["m^{(4)} - c_8^{(8)*}"]; m4c8_1 --> m4c16_1["m^{(4)} - c_{16}^{(1)}"]; m4c8_1 --> m4c16_2["m^{(4)} - c_{16}^{(2)*}"]; m4c8_2 --> m4c16_3["m^{(4)} - c_{16}^{(3)*}"]; m4c8_2 --> m4c16_4["m^{(4)} - c_{16}^{(4)*}"]; m4c8_3 --> m4c16_5["m^{(4)} - c_{16}^{(5)*}"]; m4c8_3 --> m4c16_6["m^{(4)} - c_{16}^{(6)*}"]; m4c8_4 --> m4c16_7["m^{(4)} - c_{16}^{(7)*}"]; m4c8_4 --> m4c16_8["m^{(4)} - c_{16}^{(8)*}"]; m4c8_5 --> m4c16_9["m^{(4)} - c_{16}^{(9)*}"]; m4c8_5 --> m4c16_10["m^{(4)} - c_{16}^{(10)*}"]; m4c8_6 --> m4c16_11["m^{(4)} - c_{16}^{(11)*}"]; m4c8_6 --> m4c16_12["m^{(4)} - c_{16}^{(12)*}"]; m4c8_7 --> m4c16_13["m^{(4)} - c_{16}^{(13)*}"]; m4c8_7 --> m4c16_14["m^{(4)} - c_{16}^{(14)*}"]; m4c8_8 --> m4c16_15["m^{(4)} - c_{16}^{(15)*}"]; m4c8_8 --> m4c16_16["m^{(4)} - c_{16}^{(16)*}"];
+```
+
+Tree diagram showing the association of midambles to spreading codes for K=6 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(4)} - c\_2^{(2)\*}. m^{(4)} - c\_2^{(1)} branches into m^{(4)} - c\_4^{(1)} and m^{(4)} - c\_4^{(2)\*}. m^{(4)} - c\_2^{(2)\*} branches into m^{(4)} - c\_4^{(3)} and m^{(4)} - c\_4^{(4)\*}. Further branches lead to m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(4)} - c\_8^{(3)\*}, m^{(4)} - c\_8^{(4)\*}, m^{(4)} - c\_8^{(5)\*}, m^{(4)} - c\_8^{(6)\*}, m^{(4)} - c\_8^{(7)\*}, and m^{(4)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(4)} - c\_{16}^{(1)} through m^{(4)} - c\_{16}^{(16)\*}.
+
+Figure AA.3.6bb: Association of Midambles to Spreading Codes for K=6 pattern 2B
+
+### AA.3.7 Association for K=4 Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=4 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(3)} - c\_2^{(2)}. These further branch into m^{(1)} - c\_4^{(1)}, m^{(1)} - c\_4^{(2)}, m^{(3)} - c\_4^{(3)}, and m^{(3)} - c\_4^{(4)}. Each of these branches into m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)}, m^{(1)} - c\_8^{(3)}, m^{(1)} - c\_8^{(4)}, m^{(3)} - c\_8^{(5)}, m^{(3)} - c\_8^{(6)}, m^{(3)} - c\_8^{(7)}, and m^{(3)} - c\_8^{(8)}. Finally, each of these branches into two spreading codes, m^{(1)} - c\_{16}^{(1)} through m^{(1)} - c\_{16}^{(8)} and m^{(3)} - c\_{16}^{(9)} through m^{(3)} - c\_{16}^{(16)}.
+
+Figure AA.3.7a: Association of Midambles to Spreading Codes for K=4 pattern 1
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=4 pattern 1A. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(1)} - c\_2^{(2)}. These further branch into m^{(1)} - c\_4^{(1)}, m^{(1)} - c\_4^{(2)}, m^{(1)} - c\_4^{(3)}, and m^{(1)} - c\_4^{(4)}. Each of these branches into m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)}, m^{(1)} - c\_8^{(3)}, m^{(1)} - c\_8^{(4)}, m^{(1)} - c\_8^{(5)}, m^{(1)} - c\_8^{(6)}, m^{(1)} - c\_8^{(7)}, and m^{(1)} - c\_8^{(8)}. Finally, each of these branches into two spreading codes, m^{(1)} - c\_{16}^{(1)} through m^{(1)} - c\_{16}^{(16)}.
+
+Figure AA.3.7aa: Association of Midambles to Spreading Codes for K=4 pattern 1A
+
+Error:
+
+121
+
+Error: Reference source not
+
+
+
+Tree structure for Figure AA.3.7ab:
+ - Root: \$m^{(3)} - c\_{1}^{(1)}\$
+ - Level 1: \$m^{(3)} - c\_{2}^{(1)}\$, \$m^{(3)} - c\_{2}^{(2)\*}\$
+ - Level 2: \$m^{(3)} - c\_{4}^{(1)}\$, \$m^{(3)} - c\_{4}^{(2)\*}\$, \$m^{(3)} - c\_{4}^{(3)\*}\$, \$m^{(3)} - c\_{4}^{(4)\*}\$
+ - Level 3: \$m^{(3)} - c\_{8}^{(1)}\$, \$m^{(3)} - c\_{8}^{(2)\*}\$, \$m^{(3)} - c\_{8}^{(3)\*}\$, \$m^{(3)} - c\_{8}^{(4)\*}\$, \$m^{(3)} - c\_{8}^{(5)\*}\$, \$m^{(3)} - c\_{8}^{(6)\*}\$, \$m^{(3)} - c\_{8}^{(7)\*}\$, \$m^{(3)} - c\_{8}^{(8)\*}\$
+ - Level 4 (Leaves): \$m^{(3)} - c\_{16}^{(1)}\$ through \$m^{(3)} - c\_{16}^{(16)\*}\$
+
+Tree diagram for Figure AA.3.7ab showing the association of midamble m^(3) to spreading codes c\_Q^(k). The tree starts at m^(3)-c\_1^(1) and branches into 16 leaf nodes: m^(3)-c\_16^(1), m^(3)-c\_16^(2)\*, ..., m^(3)-c\_16^(16)\*. All nodes in this tree use midamble m^(3).
+
+**Figure AA.3.7ab: Association of Midambles to Spreading Codes for K=4 pattern 1B**
+
+
+
+Tree structure for Figure AA.3.7b:
+ - Root: \$m^{(2)} - c\_{1}^{(1)}\$
+ - Level 1: \$m^{(2)} - c\_{2}^{(1)}\$, \$m^{(4)} - c\_{2}^{(2)}\$
+ - Level 2: \$m^{(2)} - c\_{4}^{(1)}\$, \$m^{(2)} - c\_{4}^{(2)\*}\$, \$m^{(4)} - c\_{4}^{(3)}\$, \$m^{(4)} - c\_{4}^{(4)\*}\$
+ - Level 3: \$m^{(2)} - c\_{8}^{(1)}\$, \$m^{(2)} - c\_{8}^{(2)\*}\$, \$m^{(2)} - c\_{8}^{(3)\*}\$, \$m^{(2)} - c\_{8}^{(4)\*}\$, \$m^{(4)} - c\_{8}^{(5)}\$, \$m^{(4)} - c\_{8}^{(6)\*}\$, \$m^{(4)} - c\_{8}^{(7)\*}\$, \$m^{(4)} - c\_{8}^{(8)\*}\$
+ - Level 4 (Leaves): \$m^{(2)} - c\_{16}^{(1)}\$ through \$m^{(2)} - c\_{16}^{(8)\*}\$ and \$m^{(4)} - c\_{16}^{(9)}\$ through \$m^{(4)} - c\_{16}^{(16)\*}\$
+
+Tree diagram for Figure AA.3.7b showing the association of midambles m^(2) and m^(4) to spreading codes. The upper half of the tree (codes 1-8) uses midamble m^(2), while the lower half (codes 9-16) uses midamble m^(4).
+
+**Figure AA.3.7b: Association of Midambles to Spreading Codes for K=4 pattern 2**
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=4 pattern 2A. The tree structure shows the hierarchical decomposition of the initial midamble $m^{(2)} - c_1^{(1)}$ into subsequent levels of midambles and spreading codes.
+
+- Root: $m^{(2)} - c_1^{(1)}$
+ - Level 1: $m^{(2)} - c_2^{(1)}$ , $m^{(2)} - c_2^{(2)}$
+ - Level 2: $m^{(2)} - c_4^{(1)}$ , $m^{(2)} - c_4^{(2)}$ , $m^{(2)} - c_4^{(3)}$ , $m^{(2)} - c_4^{(4)}$
+ - Level 3: $m^{(2)} - c_8^{(1)}$ , $m^{(2)} - c_8^{(2)}$ , $m^{(2)} - c_8^{(3)}$ , $m^{(2)} - c_8^{(4)}$ , $m^{(2)} - c_8^{(5)}$ , $m^{(2)} - c_8^{(6)}$ , $m^{(2)} - c_8^{(7)}$ , $m^{(2)} - c_8^{(8)}$
+ - Level 4: $m^{(2)} - c_{16}^{(1)}$ , $m^{(2)} - c_{16}^{(2)*}$ , $m^{(2)} - c_{16}^{(3)*}$ , $m^{(2)} - c_{16}^{(4)*}$ , $m^{(2)} - c_{16}^{(5)*}$ , $m^{(2)} - c_{16}^{(6)*}$ , $m^{(2)} - c_{16}^{(7)*}$ , $m^{(2)} - c_{16}^{(8)*}$ , $m^{(2)} - c_{16}^{(9)*}$ , $m^{(2)} - c_{16}^{(10)*}$ , $m^{(2)} - c_{16}^{(11)*}$ , $m^{(2)} - c_{16}^{(12)*}$ , $m^{(2)} - c_{16}^{(13)*}$ , $m^{(2)} - c_{16}^{(14)*}$ , $m^{(2)} - c_{16}^{(15)*}$ , $m^{(2)} - c_{16}^{(16)*}$
+
+Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(2)} - c\_2^{(2)}. Each of these branches into two m^{(2)} - c\_4 nodes, which in turn branch into four m^{(2)} - c\_8 nodes, finally leading to 16 m^{(2)} - c\_{16} nodes.
+
+Figure AA.3.7ba: Association of Midambles to Spreading Codes for K=4 pattern 2A
+
+
+
+Diagram illustrating the association of Midambles to Spreading Codes for K=4 pattern 2B. The tree structure shows the hierarchical decomposition of the initial midamble $m^{(4)} - c_1^{(1)}$ into subsequent levels of midambles and spreading codes.
+
+- Root: $m^{(4)} - c_1^{(1)}$
+ - Level 1: $m^{(4)} - c_2^{(1)}$ , $m^{(4)} - c_2^{(2)}$
+ - Level 2: $m^{(4)} - c_4^{(1)}$ , $m^{(4)} - c_4^{(2)}$ , $m^{(4)} - c_4^{(3)}$ , $m^{(4)} - c_4^{(4)}$
+ - Level 3: $m^{(4)} - c_8^{(1)}$ , $m^{(4)} - c_8^{(2)}$ , $m^{(4)} - c_8^{(3)}$ , $m^{(4)} - c_8^{(4)}$ , $m^{(4)} - c_8^{(5)}$ , $m^{(4)} - c_8^{(6)}$ , $m^{(4)} - c_8^{(7)}$ , $m^{(4)} - c_8^{(8)}$
+ - Level 4: $m^{(4)} - c_{16}^{(1)}$ , $m^{(4)} - c_{16}^{(2)*}$ , $m^{(4)} - c_{16}^{(3)*}$ , $m^{(4)} - c_{16}^{(4)*}$ , $m^{(4)} - c_{16}^{(5)*}$ , $m^{(4)} - c_{16}^{(6)*}$ , $m^{(4)} - c_{16}^{(7)*}$ , $m^{(4)} - c_{16}^{(8)*}$ , $m^{(4)} - c_{16}^{(9)*}$ , $m^{(4)} - c_{16}^{(10)*}$ , $m^{(4)} - c_{16}^{(11)*}$ , $m^{(4)} - c_{16}^{(12)*}$ , $m^{(4)} - c_{16}^{(13)*}$ , $m^{(4)} - c_{16}^{(14)*}$ , $m^{(4)} - c_{16}^{(15)*}$ , $m^{(4)} - c_{16}^{(16)*}$
+
+Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(4)} - c\_2^{(2)}. Each of these branches into two m^{(4)} - c\_4 nodes, which in turn branch into four m^{(4)} - c\_8 nodes, finally leading to 16 m^{(4)} - c\_{16} nodes.
+
+Figure AA.3.7bb: Association of Midambles to Spreading Codes for K=4 pattern 2B
+
+### AA.3.8 Association for K=2 Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=2 pattern 1. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(1) - c\_2^(2). Each of these branches into two m^(1) - c\_4 nodes (labeled (1) and (2) for the first branch, (3) and (4) for the second). Each m^(1) - c\_4 node further branches into two m^(1) - c\_8 nodes (labeled (1) through (8)). Finally, each m^(1) - c\_8 node branches into two leaf nodes representing spreading codes, labeled m^(1) - c\_16^(1) through m^(1) - c\_16^(16).
+
+Figure AA.3.8a: Association of Midambles to Spreading Codes for K=2 pattern 1
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K=2 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(2) - c\_2^(2). Each of these branches into two m^(2) - c\_4 nodes (labeled (1) and (2) for the first branch, (3) and (4) for the second). Each m^(2) - c\_4 node further branches into two m^(2) - c\_8 nodes (labeled (1) through (8)). Finally, each m^(2) - c\_8 node branches into two leaf nodes representing spreading codes, labeled m^(2) - c\_16^(1) through m^(2) - c\_16^(16).
+
+Figure AA.3.8b: Association of Midambles to Spreading Codes for K=2 pattern 2
+
+# --- Annex AB (normative): Basic Midamble Codes for the 7.68 Mcps option
+
+## AB.1 Basic Midamble Codes for Burst Type 1 and 3
+
+In the case of burst type 1 or 3 (see subclause 5B.3.2) the midamble has a length of $L_m=1024$ , which corresponds to:
+
+$K'=8$ ; $W=114$ ; $P=912$ .
+
+Depending on the possible delay spread cells are configured to use $K_{\text{Cell}}$ midambles which are generated from the Basic Midamble Codes of length 912 defined in table AB.1 below
+
+- for all $k=1,2,\dots,K$ ; $K=2K'$ or
+- for $k=1,2,\dots,K'$ , only, or
+- for odd $k=1,3,5,\dots,\leq K'$ , only.
+
+In the beacon slot #k, where the P-CCPCH is located, the number of midambles $K_{\text{Cell}}=8$ (cf section 5B.7). In all of the other timeslots that use burst type 1 or 3, $K_{\text{Cell}}$ is individually configured from higher layers.
+
+The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223.
+
+**Table AB.1: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5B.3.3 for case of burst type 1 and 3**
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{p0}$ | 9E57CC4EFF411BC3A56568FCBECB53005A3A19CA729C922826FB5E2F55D4A0C6D57335B055
188F2274154ED0F61107BD34023FDC3887072689755E733FABEED9B7967C46E9452F78E0CBE
97CAFB92DD44C90E40E3CFE9DB4054AC45EB8F260FDF8CFB5C3C23733F7344633F26CB092
AC89F4 |
+| $m_{p1}$ | 3AC41CCDCEB89F45AA67884536D0B796A5E048D76D2F9531E2E31516496B3B76196D68FB7F6
CFD8C5EA232B5C012953FFCF4C1CA7A2BDEB236426E422FD4F050C4022188D8068F47441FC
31B005F8F53452DB8D72839DF021A45D8BC51D1CF440A665D1F751145D2F04CA352BF2C0BC
F589E |
+| $m_{p2}$ | 4241DBD18BB9C42E335530533B27F0411A0588156421FA0F306C2598CD9C2D3F7D954C64E4E
EC699B2414356F1D47E2A3D09A56EA850ED4319AFE7AF07538A9499206DD943AE990F43FA33
FAB6CA8E6B3615D16D17B7FF914377BC59870C269E851B4E012B107EF92542B3A2B458E10DA
709 |
+| $m_{p3}$ | CCF886D4B65C6CEC0E3F8D8186F6CEA1FCFFEE878506F22EF69AAD6F51FDF2071B34E4ACB
CD2545866C36B31C3235DD38361403E53DE6CD4FB1DC91752BF5F6C3AB442E292A90471F2A
5B9FE7599CEB4651D235D505052C22F54F868C18AB14205FD41FD468375B661BE35F0AA67E5
F33693 |
+| $m_{p4}$ | F95E0D6F5101D3D7BBB354646818EAED147E3E4CB0249F696738B3F3A65192F5F012868C190
BCB967DEB112D907A85F33161C68B9E425A3F5EA26022F6C40ED01B8DE7FF6A6F75F313FAC
3DCD47C7EAAC32A9AE47D633CA6F47AAB8EA282B467D8CE21B1352FFCD36966F0A9B2EDE
ODF6252 |
+| $m_{p5}$ | 6FCD348CB614E6C68534737B6AB3F693A7256A85D5C28C6A77DBEA1ED62E1813E7CC88AE99
0BE4432387ED43C60FBA6556C5DBD7111B1B53FF5FBAFAF86CB761F15EE2782C7616C816A1
C77E27F197DAE6BCBD028F37E5DA7906198C98F72207A0A8FF108EAA66C84D976049E4BA42
E0C27D |
+| $m_{p6}$ | 94503C230B52660711010625B04D9B98ABD0872DE470F3323F1D4120F46518715929FFF471421
2C26EC813F9B0601B573A3B38F8833BBCB57390D8E16A8561C54E6FEF9D8A64B2E06C07E417
B426671CDFAC9C7FA20D15B556CB39FADF128560A57D26B0C9354C1CFA5334A7C5F96B9528
1A |
+| $m_{p7}$ | 92B52AE0D72D7559C4A277EC57995B7B8BF3CBDA1DF8FA7D6A96DD02F93B28F84C18E6F905
D87A12D923E38C4DD659819F1CECFDB48DB8EB129DD472A2718045ACDE58C35A273FECA71
365FA35130215FD801BFA471D27ECBA3A8CA946E83060465BFA9A1F3C8888133D22BF43E1C8
9F26F2 |
+| $m_{p8}$ | BD71D9BF8F8250A64EC5131043F2B0E7424A365508E4E268A4A9857BAE4E3360058B8AF6FB4
A10B3C2BFAD8ED116229056B01F7E59E3D9D4120089EB213106B920925EB2422196AF8FA999
8389664E80DA294E1B4B7D6807FF3743EAE53276AB634EA1B080FD55425C318B1EF670E9783
EF0 |
+| $m_{p9}$ | D61ABD7705BAB371765DE3FD732D2C5A51D5DA1BA0BF789170F01936183A55CD1693685BD1
BEC7BF691144BE24A8B74D7FCF1830425997806FE10C49E98F73BBE07835ACE5F2E6E083294
BA4048D8AD59A4E6EFE538B6D1991C21BD130D25555985D5E8AC1623FAC93663C5E1CCC77
A2B3FA |
+| $m_{p10}$ | 652DE6FBD477D92AFC5424953C64A722EAA5D5CB0E6A04CB43273841F71525016D8DD83708
11E3F38851E973D8EC2CEF3180D1462E6530623B004813C1E154B6CF790BE4C712573ED7348
9BC2952048A5C17F51A25604A6CA660EA480618F8DA78470580CA9B987BE33F3EC6485AF440
ADC3 |
+| $m_{p11}$ | 49AADFAED5D1C27455F2FE9D2C66B31E3792F088E20562C3B6DB2E4F2C67445690164E34043
B5C98819236020C15264BAD09CD75608EE4BF2F62D3671611443D541DA129FF475E26214AFE
00419D12EDFDC443A4F7A6DD38B2BF62F64294A80937969E9920FC3A33DE7B131C61F20C195
621 |
+| $m_{p12}$ | 6D408E783793B8F8B438F512CC4AA7F94B296885D9F59505F339C5C1F7FDB8F2567866B876F1
6614BB6E3788E1B237DD8BB955341911ABADD6E7D3276F7068DCAD08737243631C42CB77CC
CFF7FD7A03B52D5D4C73F8716A83B6094827098095F19F136491EB1405992E3ADB80B685FEC
B2A |
+| $m_{p13}$ | 349BA9F2D6B07CC41DDBDBB446F844D77A86E96C9C2F191F1BA42D0402754B40DFE76BAF4
DBEF3DFC28E426ACCEA6327FA51C4DAD1B6F2A9082332FA4E0BC21FCF10CA9822CDDEAEC
38760194855253E3E3D46C8565CE9EE86761B7E28BBF5C4958A3EE709B8FE9CDD0CF9560A1
DAF6CF971 |
+| $m_{p14}$ | 033E68B1E9D433BC88119CCAB47004E20B6E1B8F0E4C2756DD549EBDBC5243BC898694426A
3EDECEAAF00A7AD02D4AD1F0189A1E99B0B1D796E8BB8C5EE977280408DA0F772EA3A1AD7
44CC0C78C39070BFD324269BF86D67916D157A9BE63D9E94B76F690050368150867198BD0A6
8031CA |
+| $m_{p15}$ | C08FA672B545FA416E4856DF87BA5CBFBBD64EC62A2A294427A563F691A28EF5610A0CCA37
ABA21BD98535B4BC3F0C009CAA962384B5004063D16083C93D1A7C6002BD1D51A27B671EBB
C4860092DF3B3C389A0E909E664FC4B99E5B1A39B72500335491372956E1782EDC5330CBEAB
7A636 |
+| $m_{p16}$ | F8AB480C79497D13EF846E58F4D6A0B52CF2A71AB1236661B0D84D8CCA603B157BC07C0000
306487C41A7CFC6A3A58C1276E8BBB592F9341C298E17886E3A2AA2A08576FA2380C710422F |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|---------|-------------------------------------------------------------------------------------|
+| | CC0B1AB50B13D6B676EA102B6A035449A77652524F3D79B05F9EB24C286D7A8E4AFA1596788
C987 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{p17}$ | 53F0FFFAEB51656B7DC819B749FB5DF94E4A9545B669AFA52F385C5869C4D9A2F3BB5FC874B
9DE055EAD1159C47E7BAE8F08C7F3A202D18AF084CB9DA377C3BF8F9B710F9262855E5E04F
9C92C11E4B03DCBDFDF06311DFB839969036DD115654AD90E2096862B37338272506327E3D3
9D189 |
+| $m_{p18}$ | BA58B8BE4FB00B6122DA4EB61BFB9B775811B88EE9444BD8400CC9866193AD636A86A23588
F59E176DA8A18B856E8FFB41A8D7E91A9E874AB50B89E971AB36050058BC70C84220ED0D568
1F7CD84CD493A65B41B42E10D38B18598C63F73163EAAC1C93CF3A3CAA3BDFB29D02521777
14756 |
+| $m_{p19}$ | 0C0769A781CC98EDFB93319AC2BEB03C8475C874CA1AFF16BEDE90B07D5C6EA8ECB401916
B5688AD4C0D97DF085CB0A16CA4D678A0AC1E00F9737B4CAA93A163F827B39AFF1AFB831C
EDB26EF565102DB24ECC2B6BAF72B44FF5EB88574B38ACF3EEFD87E4F6173846B151271DD1
E1466DC4 |
+| $m_{p20}$ | 132C03285553D9205AA3746EAF108D92461B3DBA03866E70A2F47360DF17502559E5AFAA2EE
6C7DC800D8F620A3294A3E2B1FFFC17AA6634D6B7F3353A652CB0825A4E13A3CE5E91F7225
181A0678F53B3D038BACAFE214FD4BB4C2D80EF35D42A2F19B69CA2162E30543BE9BD85481
85D0D |
+| $m_{p21}$ | C2E92D3AA8981AE97C3325B1FC1843CB0E8C5E394C201981A8DD8D1BEBF8F649166508A5A1
7819D02EB0A8EF797D8C51DADBCA9A66D949A4C7E6B37ACCE1A2E578469D1B9D8D1A47E7
BEA9DD0002FF7D64BF6519A63D9084C0841A8841E183973644DF590AD107E852F3357A70A2A
5637E22 |
+| $m_{p22}$ | 9BEF2F948ABC4CAC809972EA52EFE03907142A44F3053F970445B1EDF5D1FC9F03B6EE30F7
CD74C04B68389D5826E85E763653ED75D1469A240E406B3989EDA065BD84E34F790D74D2D17
D7ABCEC25CF7FF130C4BDA979BB5A9133CF3E79B3558E921EAF013A0CC4B87C5FDC4AA9
F245E15 |
+| $m_{p23}$ | 6DE4817165AAC324EA17347B78FB4E1D642F74E15F292880975C42F405D440B1FB101E64DBF
0A0ABDDCDDDB388672248D2BE9431F7BD77CEF1583F04680865B315E8551A232547A807CEF
C742E529CCE892EE7FB2F312E96EF7372AB4F7310F87912793FCF2BAE5DC0E6DE2CE9FB40F
53513 |
+| $m_{p24}$ | FF5034A2747FF78F34664125AD31AB2ADD077839D8CC44372D13589649381A2198631F1454BC
450ECD0AC8D8695034CA8130B5E5DABB9EDF7A4AFC0738D82B7BAC7086FE813289092AF218
F5D04BCBCF98A07F4C2E0F8BC9C52F45C5813A693EF555A2B1EF308908FC993B2266B2AA09
C3DA |
+| $m_{p25}$ | FE1DBAC430C3B1815990B234583A86EB45EDCB32A38C92C3502B5611819701B1F545410092C
AD7E962D3D6E232059CF0C9E8DEA6F7DA21D89F611EFE129D854C5B957FC810E0730EA0C56
03B035DD9D19686BD7BD8FF0C9979C900E955A649616DA71D0FAFF079176E541F1AA27F024E
669E |
+| $m_{p26}$ | 8C0A6F60BEF5DA92E8702CEF3563B50B8C1C2D29DC82B97FDEFBE322024205726A0E5B9E6C
BE0F9F02FEFB264E62FF99955B536091CEFE5C6986957149C2954E0EC43C73650855376E0A8
A4ED9873AA8AED98D10579ADFB05A8713C37851692C3B4405D9D86E6BDA0EA9A4BD0CEB7C
79E6FD |
+| $m_{p27}$ | 205BB79C6DEFF102C2FEDA5301BC5B6D62957A3A02B486DD6BEB878558827499DFC1DC79E
C55241B208599E32B99959F9589624E2C0AAF11E3C8CCCFA7EB88AE7B844B483BE360CF3441
1EF739BF073AAAF3F84E516CFA10992D606789A20F15686F54CBCE8A1305BEBF7EFE8EBA95
F723B5 |
+| $m_{p28}$ | F32AE20D70B2FDB523682A5AE7A83307F740DFAAE0DBB58F828DF0ED20AC79C85E2FCAE3E
C342E79F0EC8054231A541952736CFFED94A4F44FB7DF473C476FFB3CC87BF18A0938AC776
A26DEB32BF906D2C90F57ED192BC33F1312746B143AF383C972A2B61AD8D46F3C4E56026150
6CC87B |
+| $m_{p29}$ | 8F6A99C81370432B4D05459359C92D87DC3D10E82454B911EAD9E80AF07F26B198C6ED71E72
F608118B67C61E8C64EA654B7BB0ED91A3DAB2B77C5CCF92AEEA8D6DB9E9AFC142F6FA9D
2E79E443DD42D0F66BFE92D9BAE58113B8811E50FF8796E13C43BB210076AE2F8FD0A1FDF3
D5B2AFE |
+| $m_{p30}$ | 3BE3E2BD5546AFE1933CDBEA679EC8FBAB69C0ACFD5B2DF9A72CC5B4132123D6EFE9F907
CB187DB647C6C7E59F71E830DB84472B40C011CB418DACED36025BEF7289FA803D1E32FA2
D35F667D2AF8B78985D469532B5FA8336072B7FC74A515B8700CAEFCB625AC212AE335E6EB
C37207FA3 |
+| $m_{p31}$ | 2642A80A8DD998C3198E6EF691B68257560C5E875A32F8C101478B24F9150883476B03F26B6A
137E117057B525F37E3749D1C1DFFC2BD059C6F4FBA8765D58493C87894E819EBC1172A62D
D6F3DFF2B18A5987B0841FE85BC85575B0B1048A9138E6C9181017A501CBE76337926BD9AC7
78F |
+| $m_{p32}$ | 362817D18ED89453CFAAB83B0D182FC12F3E90C124514F404743D223487FD2A2026603D3CEC
04AADB26D2DD8123B2D18C4ADF6A95260FC8055D29B0EC561FC355BEA5E97CA030B0187
773B726299C2CB91CD7E0EE28B89C63EBE333F316DB6209B012A230FAAA29C52D41F9DBC6B
66F7BF |
+| $m_{p33}$ | 6E92DBCC6445EDBDAE1D566F99C4FA5AD9823981B71A883BCD14967C2358711A59B856EC48
90697E030009682A332D0F7CD85FA7E509CB2538BF395306603EE229C950D749D3A4EC4172F |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|---------|-------------------------------------------------------------------------------------|
+| | 8400B1E1BA5479098A79F48F3F977C400D54135F75DBC6CF97019E30954AAA550D95ED4E08F
C2AE |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{p34}$ | 82B02C0023B142BFFF4C2EAC7E5F83D3C76A7A18EAC7B621A0F9B65152E475C8F8E2A30479
EC3EE9263F73426722E9A96DC53EC42D7C0BC50A643E66E9B8C0BDE8E893A7562CA33856D4
219A5A59F599590164B4015BB9EDCD26904B9716449FD02CA7380C6A50CE22A40E0CDB787D
109122 |
+| $m_{p35}$ | CF2673929413ED857B0DC9894D8AE460C19CEEA9CBEDB810388C0ED13E11FB7201ED5A686
5ADA459DC8E5023C73FC13D159A7A540F64FBF586A2504C18843F42714D4699DF6591944AB4
4126A4A83D175E8C41EFB28D34048E2EBEF454150F4878F6A02A874B1BE46CCBF8577A5EBF3
77578 |
+| $m_{p36}$ | E0FAEF096093575ADD91187D72DDB6E6401BC189A5014D6149E092146BF879450EFC3E504C3
06D0151ED465840ED503FF3BF92CE33E411A17AA7DADB365731D271791B8C21BED3557892C
4D0B3795A24EB61566C3143A54797B8BF25194A9F8CE20C5C991FA29BBA64211B4807066A45
B9E8 |
+| $m_{p37}$ | 234F19C1B17B1C403171712FDB575CB8FCBFE15B39F548E682452117597AB24B8E7E51834F22
2508ADF3260AEC2246AE84359DC0130229580F98275BD036F82BCCACBFDA34391C556EE7E4
C90A2C67252C2614175A2D0C37D5C861A0D735DA8E05D2E7712332C0BC0B33FDFED4FD90A
61D2F |
+| $m_{p38}$ | 415B84B33D1F23316B8C7DE312EBDA1091AA5BA44319C7289C78701DD437028F8CBCA30C53
4FFF1875A230EF762F1293A9C9BFB32856DBE06EE915D1AD66417474A705B7BFF4EC8DD4488
34789AE9BBBA1D2D99080CF03841DA0242E0204D3B80680C1AA6935F3F6E9F0AA2B51E5A7A
227D0 |
+| $m_{p39}$ | FF16F0619F5A297CC40FC2F97DA2A92A9D144C2D1C1043F53DA05909FB7F23DD82ECE70545
330C327A097FBB2F93A0E7970DC64768F76FCA0E5D255B4116550E838664791055B8D24A5837
B6DE3CA65C522A50CC25284D68C3BF61440DEA011345F3127A802234B66E5FCB893830BD39
C6E3 |
+| $m_{p40}$ | E9EF50791AEFDCEA8D5FCE9398C3FD7A8AFBB50F2268234F62FD799FCA3BE94285C92BEE0
44A546DBC29319E983C6FDA5431BCB78AED499872F24F228FA4782FEBEB6AA13606239E56F7
D19107CFA441C2004192386AD0BB6DB381ECACE4D153DD844F9179263E899DB195F16D9581
248259 |
+| $m_{p41}$ | C310A1E57CDA2246752056F432E5808F423AE04F5757F6B3D2E798FBCAF12517BA77CACCDF
11B18D6A04CB37D80A077C8F90FDED0D33F8739312401B6889E16B8665ACA75075210424AB7
BB2516828B2CAF89ADD0B8CD223FA9850B170D465125723D43C5DCFB7264F4247B4C0F5D32
83C15 |
+| $m_{p42}$ | DF2A1C8FF69CFDEB8D36F67744F0C94A6028C7FFC376E4F32AE818557C2F017F040D8809614
1C90B1F4F55A22AC386BC40ED96EA1B7BFAC91AA0BF97E36F60E225E167D926536AA22BB1C
E36BB9B42C53CD1A56B2354F23807B350BDCE7C9B01CE6AC7AF212C050F8E827CBC3AFF71
D50E97 |
+| $m_{p43}$ | 88F8ED04165EA0D34E412F8C7175D3C387A9B18E0316E00DB2F6BB74CB24BA74EDDA374036
FA0A4224F6434752B67462C8445EA3E51884BB5C079A862E7711AAEBE14C50DA149B032066C
88E38CD0FA85AA6213F28E5BB2D67BB1E000E16B6330BDDDB9796AFA27EEBB6A0A7A1395DF
FF1588 |
+| $m_{p44}$ | 5439C5FF080A258601EDAB8A0B54F51AC7C66B6D8165AEA5BE1E15AD85DFAAE4F908AC8404
DA4CAEB3FA93AD698C835F3B60205DCDE971BE63D570267B04CC26A8CF3D5051B22D9B0F4
099CA151A89508E1838185F90D7BE73161CA5CC3950E2E848B26F85B98331398AFFEFEB9A04
6A5A3E |
+| $m_{p45}$ | 9D26B1376B5C4F5F586486CF35762FF481842D6353D6006AC191D1157CC39678F0B4D31A1668
AF65E2B78B5D7ADDB45621DAE6A3E4B0322FE0D5713485234392040C32551461A0749B5362
7F0364A998A18CC02EE708732DCA8189E523D588EF5D3CF70E87EA5140007BF84AEC5BC1BB
391 |
+| $m_{p46}$ | 89530DB4E7FEC9DB64622E6FB8F0879B24F3D023C83AD69D674189910F1EE52BED4FCCC501
EA81E122E8336A89D209FACD7F6A89F65611A470C16B12CFCB84AE475E6B82895CDA52F564
DA7726210D073B38342F6BAA22014A7D0EAFD6202DE5B03CAACA0610884223E4C787E06F84
A8CBFB |
+| $m_{p47}$ | A9E83B98E0C2ED7950FEB892BCAC4ECD503CDBD193D143BD03F2459DC6895A81314861930
CBD9ECFF114865CFECFBF025075D3FD471558FB7C6A6CEF8547E937CF52DA324E4EA04319
B78376D2F4BFFE8E467DD8C29DD0D44135ADF1D179886A82320FC35AABE4957641C9762F7C
3AA7D970 |
+| $m_{p48}$ | E113DC0ACF1E85730EA81E964487D1D8263A186C5B627B8F96D95244284FAF1E9D8351D1DD
7957D205C15F26F3919B34196FBEDED8E88D96C00441A438D27B215AB448B6F6D9DA895FFF1
0EB3D4FEB44468F21E77CE64757F6D8A627C4A2BF0DD9D67684F80F3C1BDDADAD192EF32B
AE5479 |
+| $m_{p49}$ | 687C6FAAB36FF9C20DDBCF1CBB7AE82F334E48CC6C10B988D8154DA5D18746F3E9153A551
0C2B026F5CC7B6A7562644E5936CEF2A023F40BF239A1F2A6DC75782F2D056174E8A904A7A1
1D3E301C0842F8BEAAA3D36C86F240309635A90E10E766FD8149844F8B42A9C4A59FE4863AD
0E285 |
+| $m_{p50}$ | FFDBD37063D55715CEC274D716DB7DEDAB90ED8808952BEDA0E75599D5A29C13C483FB97D
3A0822F46F2E1F4ABB756A7FD4710DE7333B488203F7152FE1D1DECBE5AB17EDB806681DED |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|---------|---------------------------------------------------------------------------------------|
+| | C8CC12C11753418E2B2A5C95D60FD2DC9970DF38C84CE7864833B69046AD039D261DC1C14
CF056DC8 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{p51}$ | F1748076429321CABC98153CA2C18D3ECD24CAF8B22CD97C1674F6A3EE26C016CC1B8E8C3
D0BBB98482D09ADB2B06CAAAFD73FEA2203F8A2B791ADE9C14A5DA7015A442392535CC10A
10399B2F80D818DF180707211A8D858ADD9DB1EE10BBD6F92F2DA9CC03512EAAE5BE18F7A
A87573FDC |
+| $m_{p52}$ | 81DDF8E2BBAD0D040EF4796A5EA19DFA9C0CA8067068909896A83C2E1E239D83D2B858E086
4A7BDD2962AD001EB19665E4414BE81FBA6D7BBB1787AEDB0C81913D5C86E3905B20DBA6C
9DAC555B4BA05574F3120FE8F3326B336B61BBC2068BCE2788641CD59032731BFA73E58869A
11E4B7 |
+| $m_{p53}$ | 0F59625A8BBF1E83A906E5EB9E5E1CF85DADC7BCF7736DC02DDEADC8736F7399E4CE10601
DD832D32AEA53AC895EB92DF5FFB409985EED5BC9C775C7A655102E644435ED2EB84DDF30
130F101FBF2A93FE65D473593FF3A4134A41C4C7EA6A50448F8B2FE1F91F1E9E84C95818D2C
A340C59 |
+| $m_{p54}$ | 3AA62BAC2BB34A4B7D06A968E20E16A1C79D865C1F87DCA2B3DE6F3D49D962175B4D7FACE
8EB162E9E0FFF9FABD6F57305051838A7D5A370DB79F9246B3ABF10719EF9EFD86664DEC9B
06137911903AFE43D00DC992F9F8FAD1C017CBB7591E1A02BDE56B75B2F82FE61234ADCE34
AFA8017 |
+| $m_{p55}$ | 1682757D7852076B78872B235412EA5CE2AA997BD66C8689DB605F04779E70F61A4E5AB75C6
5F1BD3D9948C2442D9AF89EEAE6609E7E1DFC95294C318AAE8FBOC2E025713BE5B38A08F8
A8463D12081EF250C482A2DD9803628B07C9076CACFFEF49EDD6A3440A6952C73493E0DEA0
DB112 |
+| $m_{p56}$ | 016B428AAA41A03CB6BAEB518F27D34CD9F4E0A7F0C149D3B8F35B9481274E4258C01E6D1F
0EF01256E48B00C7D4F9FFC242273890A4D5BF9338A1F5D74F01BF56EB2E5DE461AD46F7844
6DC2B56667E8732E73E95768CC05615752A8D2C88DF077277F026CA1A1057DA0C15D10CD609
3DAA |
+| $m_{p57}$ | 68C2F3594AD2A41BFD7BBF60702C5581B3F75E54CE7D1B3A598400306FAA22783335DAC415A
F939C4596A104724F53953BB51239BEB77D2574FDC37CA1B07C5E7AAC2774DC35DFD6B83DC
CEFC3C0A9B3EACE9A6052C44E8C327B24D173A760BF9535EF8095F35D9DA3E289F636521ED
06584 |
+| $m_{p58}$ | BC27B7917AA3ECA9ACE1F94A1A917FE1CE6754E906AD4645719CB3818FC58A48F8CBBF3293
8D18D68203507A4D2205C049AA7741E089777205F1EDA69439984BA8DFFE45C210253D528305
BFAD36FCC90683801A0F19022923E45DD0A52F6E2E3F9A49333250F76A8BA8C325A39B362D9
F2F |
+| $m_{p59}$ | 057CA87F217E30182A60109027005CEF36F98571B1C11A6525308632CD39232853177DB25A639
192FB65EA70A70D90CCAA34FBF7C2E6233A362F46345F15CC5B2565DD7537010E1BCC22AAD
D2C7BB05EB6BC05A5DF289A8AE249EAC10F21666C742A09462FE8F1D38B5860CDEFCFAE2FE
BDB0 |
+| $m_{p60}$ | A2AD4999053CFAA50A1093DB07AEABCF6F80C293E00D8ECCB12B56CE7FBA3F62D686C15B3
E1A941AB480ADD6F2176C537686F770D73ED366086E67F2C46B8AC06B870880AAA2D9B44421
7504ED74C7B90390485AFC46A63F15CAD9251C638278707D46A384DB62A7BA27245A5E16D62
31908 |
+| $m_{p61}$ | A196D99A227C44C27BF2BB0B6029557118925061AC9ECE965EA7AC380CFE1C0C33E5B7567E
4FB77B7AC7DF34E4557545366A943D375E4D8A211CF03FB7F37620E9EE47267D78ED1D0A247
8A353D2217AD5AD76892388EE7F0144ECD69CE3B5B04928CFA6A68C9FD0FE817942FF143D9
C2DD3 |
+| $m_{p62}$ | 2968ADAЕ21E52DC8AE811AD840AB7600A5C6FACB2F3BF707D0DE018178B5FF73BB31F5C88
E9B6C02C54B8D7B1A049E39CD7960F7109AA5EE9A18E9C3E9F0E8359952E144169870381391
E3761E3137204CA71CCC4DB38CE4394068303F088A2497FD49DF4864CBEFA1675AAA8950685
77AD0 |
+| $m_{p63}$ | AF21B04CE4B418B9A0AD80221A9C47978750483A83E9096D9F09069C3065E8F6F1FA68EAD50
B78736311BDD70F72D97290C06888ACDEA4FBCA3B25FFBC5C8E91676C4384EC68C5D3C40C
CD5AC3E75116CDC28C05F08B479A73E2AF7D380F69CEDA810A60B6FD6609CFB8A7D4E98DE
0596C4A |
+| $m_{p64}$ | 56BC72E0F1CB9DA84FBABFF84FA635E1AF9B60BEA6C22F8953156C90691F44D2B4078EBD8E
A8BF6760BCE5217E2B0C2E19D4470D3321083486339AFD6D57FF66E21C149B40FCFC5CDAC8
0F7B6ED2AE576F3ECD4D14A5C56DCE7CD04147F9D725A783D9915D2E7A036FC854CC373EE
8333305 |
+| $m_{p65}$ | EDF8D061318EC3126958D38D4E0A0C71460B5F46E16CB7FD7A4084D174F900BC8A79C672C6
12E46E2AECD FCF3C744F40510FB20D15FD9C2E696F8FCCFBF80FA6A435369889E17A612EB2
22D50A6B88BA06408DE022EBF4EA74295F5B921AE86029D376E2D51250B79053EB3AA58B4C6
F3199 |
+| $m_{p66}$ | B86E98A32DEB7FB6F9A120725EC9C07CF1864670A9D5082D7DB7FC7656AE8EFA05D661E63
A06D436DEA5CB02E5F29F4B3D364701B1481BCACF306804FC14EE48A19CB8095F9C456502B
39A08593AE258DBC12B358D6918C3EB8546F9F3E36646282E08142CFA309CECC823549E0294
6606A |
+| $m_{p67}$ | 070850FC776EF3F88456CC9841604D144CDD4B58247B2938AA074009F128682E25FE0E6DF2C
3991A5029A7E4EECA22C5718D6C457F3B529702EF34C7CBE96B6EC2A2391DD6079A21941855 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|---------|------------------------------------------------------------------------------------|
+| | B5BAE1729CEDE009BFE8CBA54C25E7F0960990B004755A647D568D290A645C4C3B8E7262C3
47B5 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{p68}$ | D96CD3FAF18CE3B8D470CCA2567E54544F4F9FC471F02F6441AB5F786DC9099E16C9482468
A2BF0DD84C87E36C8A7D39500538FECCF76B03086065EBF38819530458E0D4B3ADF3C66C06
6A0651D3E8A84BBF6A4697C05DE066B112A8B6118977923DC3A01F43014B02C525663748B4F6
5E79 |
+| $m_{p69}$ | F660B66151AC70269D9405C9A987C3FF25DFB65AEA14E5EB2A699BFA335AB16974D00112062
12F3A3FEA6F0A6971FB3C6F4D73A6D44543FF1FA0775D57D13AEF2E470177C55F1D823299B1
DCFE4CA851D7E9075CE9B8D6344B47354DA209DCE4EA6C0EB1F43ED231C04DBB510C68B2
D2F336 |
+| $m_{p70}$ | 88C9890A01B550D44B635B0D4C01C20AEC17B0EA42389FFFB0D70386CC2BAD4D5A8E021A22
8BBD4059FD12854187F2F0DB1D6CF7AB654AEC2877D2B1A3A8C508CD9329A096F161B8DE72
866C2C99BB67024C9261A24AFCFAFF3A483E8D71BA7AD985E9DD0CEC2A4B31E088A7CCB7C4
F39CDC8 |
+| $m_{p71}$ | 1309529E28E71D99D501350D9662F3BF5E3D54AC16408117F0083FBA22F1AAD9CC29552590B
051B725B81B56E33E36C72F8EEFDA5F3EEF4629885BF827E05A4B918B831FCFDAACC9656FC4
1D30FAC255D2C931D3E090897C3E75CCA520061DE330C60AFA9545148B27A1377300B064389
7976 |
+| $m_{p72}$ | AAB7E27B83CD46F2EF18B91FFE9D9C69BB92327B0DDE3664C8974EF7BCBC77234772C02007
B344BB99DDF344F7E5A6C3CA3F01B0F28DCD566BE913C274F296F056A74CEDD7680CA7969
A34CD785597008543208DFC63DB6C847BD364BAFE11751515287B210554A5610D7035A374E02
43E72 |
+| $m_{p73}$ | 7972CD5FFC6AF3780BB7A88BD4BF9799AC403D1976D8B4ABEAEF4888BF0C269C96572D81B3
BB55E33D30900CBEAAF1969F08E4EFC7CFE7F99DB9A184869DCB18A3D143AC725E46F01B11
EEF3940932A7AFA30E87E156428EA927872FB64CFD072106F00811359CB146C957C15C3E920
DA96B |
+| $m_{p74}$ | D62ABF2E9F79492FD2A22FF60CAA94DBEC39C380F12290B133DE53F18B1914DB0555BF6AAF
47539337FDFAEADC58B320D67644408C4F5105F8907F2254731D319FC3CA221974D5E9006979B
CA2BD89C04F2D1E1FF2D4C51F3BBF2CA5BB2FE8FD34CF05AB45599BCD6DCE5C2BC53E114
A723DC |
+| $m_{p75}$ | A0D97790B621153CF61E6DF09D07FABB17CD0EDFD030E300ADB777FE3569C35F747E4DD156
6196305DA32BDE5BF26E395D6836254BFF3DAC9FE2BBACC4A5900A14E2E72E0D4D05D09A7
A3BCF211D1E2F7E36CA379B52BC21D937BC628D6686F59171C5DC4A223D9AB1B8F89019FD
D50683ED |
+| $m_{p76}$ | A133814EC7D9BA19C3BF38946484310280B2333E631F2A29137230EF8B8F9A30A958D8AEE03
A5578EA40ADC014AB6D8204C396AD7EAB3C17B1325D7D55FFE946525ADD5CBE28F3DA392D
8873C82C6CB6CB65760DB5B0D985786A7B04237C0D0C5F43C903E9CC3126AEBF3BC5CD434
9FE2602 |
+| $m_{p77}$ | 89D74B62E35F853EC718FE7A32C7B39AFC27A41C87CA9BC76FF6640DA6ADADA997562B010
AA1841DB918E947989291BDCB50C9F40FFF623CCB0336FAAF878FD49BE092804AA73A3A419
07D5CD32A375C898373D93FCC4C9EA84A2DB9802521FD5376F9635EE1D0C3E8DC34849369A
757F5C |
+| $m_{p78}$ | 2DDE87087BDB66B5DF7744CB16AE7164D2E5AA7B7B2CD8BB46C6A602DC9A108752DB6967F
1728B12FEEEB1FCB681DDC48ED7C1C3DA5536AD84CFD9F5E94E6148F4DD3D9CF3C830F3B
6401C8206B0ADF952AD505B96C74C615FC6F70381949B2E6E25F42D3E6563041FA5F501CAAA
A93C519D |
+| $m_{p79}$ | ACD35DB85397D81E1124B62A60CE35E4E8214318527F96F273AB6718822971BA76448B3A6E66
2FAFF4D37BB2176934F80AFB3E03FF494AEE2F7C5B1D0B723E316AC0D67AE53A1C0637E155
729422E7F78F5FE19BB9DCF674D13157B2F8994C5DC03780B6EEC2AA0E57FB7F8A6FC0EC81
AF87 |
+| $m_{p80}$ | 43FCF00452F2E93D9A4110003601467549D08A20E4DE27F025843FAE54D9E2E5820D890558C7
541FC771CDDECEA6648984D63183ADD8E5BA52F6E56956B6F1CBCD93374F34F4709DBB812
D155528403D364CA2E54BF1F6828FB342B3D378185A6E3E8572B2F28EF6AB194C184ACF4FC4
09FC |
+| $m_{p81}$ | B130A5C2EC864C8FF71CFDC347DB4CEE38259F34A8F9CBD143763AA9DE869CA25E1A6A49D
7A6FE1DC029DB9076FB6F111351C6FDBF0D1C1DDE412B835FCF0B97ADEEE7AE09241C2FD6
20D63F894BB09E839021D4D81932BE52926A33AC9C81AB3D9586AD2E8AE53CFEDB55D43965
CA9EE422 |
+| $m_{p82}$ | 7AE9E0D3F5D0295917B116C28DC20E9B305296A3FF02339C1BBA86CD3D566D0C8948839C2D
4751730DB66179EEDF5B04404B7D867219715C87F9A18408284F0C0894E1864A55596DB9851D
0DB68B8AF7EEBAC5C01DA3284E6B42F7FCE8877AF04713C98274FB93FC8C8D421B0B572B5
DD1F0 |
+| $m_{p83}$ | 9737D9C29C179CA57976D04DF9597432A763D93B69B799EC14FFEF6F84A2F56EA0EAFD13FD
6D2C69462FFB551A58C17B06E32C59E605C34CA287EF8EA38F99C45D93A922C50B19FD02B1
30F5E704BF435A8998BE97F76181B64C56760D8A5B0043F290C1637783FBE77E9D113955431B
6F21 |
+| $m_{p84}$ | 29FE9F4CB903F8BFFB5134A5D8A2B3D7A8936A3311BB1905D9ADBA1E3467AC5D3F5F6A7758
130E4445856422CE094D85B620611E7D8F5B3C0CF386490214FB6DED5CF761BD2BC87CBB0F |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|---------|--------------------------------------------------------------------------------------|
+| | 4171B566FA32761C9CF11147417F50C47BD1986AFB9EC129CDA74EB0947C06B935F5A175D22
E2E35 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{p85}$ | 50D3795F988F865B3A9739FB23047D301913B7BDA5F87D0A3EAC478002A20C571D553EA1903
93D404E1718BDE3C780D26BC9FB48EB555A9228C323036F000CEC60AF43E23F734B104A4998
B4662D1770B46B1643EE6A9B4D8D9308F4410821FDB39403652D53952D5CDE7903BEB66FDA2
596 |
+| $m_{p86}$ | F84F4D2894AFF4B26CF0FB72DE03D5C43D98F7A13C95FCAFA16D9AD2DEE38EBA7CE7CCD5
1F02DDEA932436451B6AF185E2C27173FC5DC4D5217E0451F4864933F7D829691994CD982D
2D7D7B302333F13CAE7DAF6EC9E67188955207AC461AC2AC124FF94ABD2705560E5DCFC6F9
8C8AF0E |
+| $m_{p87}$ | 058C6EE106A2DCE93EF5220D1BDFDF725CBC4DB869698A72F89A886AD38A0F42ABEDC4966
FADF33AD0C39388055421F2D4D22FF5E698C4B1F002633C051582D899A9CC51973000BC3D43
E64BB0E080F392DAA65ED11D081DB55BAA3AE3EF2B5B135136E2BBBF81F17A926D9293233C
08F58A |
+| $m_{p88}$ | 600EE81F7C9864F1B8C7337A7C1582B1A038B8461F5381276E514C27A86B1C96F61A3DFC489
0023AA73A8F8FAD7750B3A632BF745881704C91198D40F0C6DE51293656203E4545EC660659E
FDE97CB52C4540AD7E6942B475BF5C8C2047E38E3F79731AB972F64B519B4DF44BF25254FB2
8A |
+| $m_{p89}$ | FDDF8C811955AA732713A5973F621C8A763E4057047D3CE2791D20A49250C5BCAB0FC702FA6
563274372D03275D6B3FDFB4E981D7D35A7EEA2D99F607E88CB38D7D4B35A40934EA67B3EC
9E7FE2ABFED68969E0534FC6720346D8C07CDEFC5173554F14E05BD81DCA647C355AB8379B
EE206 |
+| $m_{p90}$ | 62451F8749EFD5DCF5729A3D5BF4AB67A5854398C8D6A2CCB07F2BE0D676221F764716E0A
EF70515873645A9F438C1250072FA65A167AEB30CF099AFC2C2504E129D7FF2BDB28B78A36A
0D621F74FDD36D5EEC9BC4625EFEC4AF6CDCDC496B747134E6D94D87F7141481DEEB83B84
1C0E33 |
+| $m_{p91}$ | F8DF107B028097DB928CF7A03F0157BC3B50EACC30063934EE28413D7764CDDA46D17EF91C
A7205516B76933B3D50D385D871357AEFA2E34D1E3E929FCD08B940AD54762D21B73B0C144
C4C2309A26AD3EBEDBDBDCBB0B1A49AF796DC5D8F62F479A6CC739D6B391D97C39FA017E
F2D85855 |
+| $m_{p92}$ | A45FCBE0688A55D051B057C34508507010F607661BA244DB1A7CE599CB4ABC6F3575A765E41
C2EB8B5BC49E61162478CEB07461787BOEB6AD14CEAC878DC9257E48418C2F3292BD087FF3
B4CB7758B00BC5380427E620776FFF7128254CAEF743129B317B8C21D0ED02B3B94785048B3
B274 |
+| $m_{p93}$ | 432250D31BCDC883439F92FFA76470DE1B6689465A0FBD3A12AB4D165012AB32B7EDEBC859
68CB1BA84C24321CDDCAADB0175DC6C2FE2EBA78EB788E049F8ED34A3AF1F42519957C748
96872C3BC6C0A7A210E8438EC84085A3C4E3884E8B79AA57F85937D815C493C044B80519F76
EAC075 |
+| $m_{p94}$ | 4E3834426643F2C419007C48053C6B7AEA54D231D68631D5CE305FC33C155405B2566ADF0BC
3E4D70B498B3CB2981425D610559C2EB63213F07AAF3E240653230436ABF9D823799A05D78D
4D5A45A67F6637C9D9A4BEF410BC0290BCFB47E206A64FB6EADA1CCFC9B77023EC705670A
9439C |
+| $m_{p95}$ | B655DDE80717690057C86FB8C2F94A922D4965624E527B42C080EDC3114472B5D58E3076EE6
06A6513515FF6FE1F5C6CC4F6A34AD865C7EAF03558BDDA4A96A838B1D13543B87E382A4C
EC3383E4F2EC960D9707CC52624905326B32B0F6C8F3CB3FE7D912B8040518E61C0C1D0BE6
135F4 |
+| $m_{p96}$ | D3817A6FD2936F4738A55F19CFBD1EE3801CB86F9B9656D39BB4CCE5EC930CB801BA371A05
876F63F2A9919BF8E769F140338176169439309841D43FC304EED8D80164D2EFABDE83DBBAE
A927748597DC553E6A2EC52E3D7340FFBEAF817484A7558B59753BD8661596C940CA6F16570
D6F3 |
+| $m_{p97}$ | OCCD1503DBC6DB746E369372930B18BEC1C972C30D3BAC9547590AA432AA5280492851CF89
35F74A5431E97169A3322586719FD703B122B70A0394D784A010D6B9BCA2A9C7284B8368127F
2C00BB31CFC8EC1B3A31EF6EE148114BC0867C1182A742FA26A2EF1F62F948762C3FC6DF7E
1E4C |
+| $m_{p98}$ | 68AD9382C2FB0471F415D72240613B24F019FD981423501796E76898F2D423801EA8321E01CF
EB9DCE4AADE7CBDF0C10F94F98E6C9A561204D4051487E5326173030FBE760C28D8BE6815F
CE78805E9C55CF7994AC8482B6A13254CE7FD3ACCD6D96CC35913962F57965D2BA905D50F4
F7F4 |
+| $m_{p99}$ | 965AD6AFCF7A822E2D0A7F3F8B23BDD9DA7667882789C85A010B0CD095E2BD43919DD6BC
8F290FD5FB7B1F0A4F8C47C348EEC37F483875721352856568DFCFC16AA1168E1D948E9861A
5E693AA0AC4F26225CC888DF6F326DF4D5014C892ED9A6A8E99C4140BAF7C03873532F0CB1
EDB7EF |
+| $m_{p100}$ | 11514B31D4E01ABB0202CD8B26B4F3610886058BA519EF4C9701EDF8ED2E935F65AFC454C0
B672B14B06672BB742640EA5BDBDA47FA5F87BE583F65331E2A30CD850B4619637DD7B84646
06F10236714131E1D2AB4EC55654D05A93050E6F8748B4DC83C6202B7FD63CA1FC0EA00DBD
48538 |
+| $m_{p101}$ | F6FE8BDAEBB7FAA334EC95ADC619F8A04171707C84C79A7C96F973392176EB7AC5626FB24D
0F88EE8D5FC99DA5F03C381A93ED455B13DAAA4DA3EF7A092D114316F6D25F319473BFA8EF |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|---------|--------------------------------------------------------------------------------------|
+| | 025438B0A510DB7F4E8436A38B16606150D2B35B2872DC206AFB17732FD16219BA58CBA1CE4
02B9A |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $m_{P102}$ | 912FF3C82D2B7FDA4703DAE6E349E1844212B4672DB02A4D0D4465220C1A4CF0E7D56C945A
DA538D465A76C7DC3AE272BCBBAA4FB9D9925EC41FAE0735380C1126E36EBEE55270F99A0
D851FEB280B103E3F51080B99496B2E3027F6EC16D91EF42C58E4089AAE68CE075D323C4A2
D409CE0 |
+| $m_{P103}$ | 4789D7468124CE0AB731772154704A07BDD14C319DAA60E9E3B55E30D61616301AC560BB31B
6341FA629F630204D057A74B8226EDE4A4696159DF3BC7DC3597072A1A95464142AF23103CB7
C28AA69A7D2CB990967427F9EADF3EB65FB95DD72CEA804DEEE0924307794D99FF406F0AC4
0F6 |
+| $m_{P104}$ | 9A5C8700EF68EFCF28CD6552C267515F58593EA84FD48BB5D63EA028DA77F92787FECA4FED
AAC04591502198A10725B62AA7361C932B58C6F4D431103A56AF5A8400E8DE5AD26788F28526
387908EE52B030B639DEBA260A321B09BD60E7BF3C54E1D8264A04B0F65D81F9473622CC05C
3AC |
+| $m_{P105}$ | 9F6A2D1D54D09A6A3AF7BF514DC754301A164602D531807186D9930FCFAF112D40F72D17DC
E9C40E9EEE8FD2E5D1D3BA4543ED609DAF163CED9BD0074D3E5F7E17F5AC7B4FC4CA0690
977DA3533AFDBA5BD328BA079BF2335364035D68673B98330B92AF5E3C26A9AB596986EFE96
65219F8 |
+| $m_{P106}$ | FFEDAA9F3DC1F267C121D6303743286B1AB1094A1790B58B1E4DDA9D16303A3289BC4440987
775D6491383589C96181AE093289D42230FD88BA098F3575FC393246726C9EAF6955EF135EF
07E862915734A5994D2CA7301FE844DE7B4BA9417CF10045BEF5F4D4C5BC044A347E5C9E998
21 |
+| $m_{P107}$ | 644CA39E3F93C4AC795EFCF5B8BD90228E2638BAE24CF4C3DE75697823DF4AEDD3253E980
81C4BD215DC64A9E6BC0115027F6BA4E4FE2A93FC726DBA4D9D21DACDBC76B45377B68863
F9FD426E4F89625657EF97C03D277C373E15D21EB721AFEAD246ADF1A0A2A0CEA730BCA98
CDD4CB808 |
+| $m_{P108}$ | AF16DD60C5458A3D27E36850281E401B10116D5B0BCEA1B159C97487584652047981333D5573
686F4C0A063E1186306FD02DEFE2C61722C5BBED60249AA2D9260ACDF870B3B5F5CFD75815
80DE486D8D9F332A6C6B6464AB0E9D54159CCCD03D6F9CA12C13DE34145B34FA40703FDC7
6AEE7 |
+| $m_{P109}$ | 33FC7C9D9FF74A2FF009240C3AF398937D078012219BA54C6B0B0D9448391CD1D4017CBDB5
4AA59355EF05A9712779D71761D96F650EE10546C39694938AEE89F7CE6FCCF4BF987D0E9DD
584992F2732D5838A92E537559EDE2FCEE82302D7FD8B1C9CF8215B67BE61D4EF4523EF9032
B1E2 |
+| $m_{P110}$ | DDAC8DB73BF5A8FD9A74561DE805959C2ADC755274740993616B3771D10C6F5B0B8E4939A4
44F280B39CFD29EA0F562FEE0405451D8D9DAEF8B1E0C8D69CBEDD6D23D8A56A3A9B87B
D6EDE46FBCCC135D70B8FD4619C35F9A72E93E8954FA787B8452347E4B209013736D0EC059
A243803B |
+| $m_{P111}$ | 516913696CB4D961C939529F64585F08C42D1FD1DCDC78F16DFD5BCE287434ED251FA1AABF
676006D75FC455DDE30C8840BE6AEAD10F8A12C641800C35B8CECC9BB54037AB1075190EE3
D2D8D81F675898FC442A57B3A7B18B0AF90528DA8019245182E920B926AE569D656E3BB03A9
75CD9 |
+| $m_{P112}$ | B2419222199441C48BB085E7982DFC0FAEB16D39DBFD22270AB8EA6A802DF3580ED6A68A9
0E3AF03281B48ED3FAA2DC45371E3733539E70B137ED82D5A2CCC2031BE3D6A4786EE9D9A9
153658EA0B483EDD49F9D1E189F3D418B73825CAF3B4D05A805F80FCCC5949704252390DD3
E86EF6 |
+| $m_{P113}$ | 04D96F94A767AB70BE85D6EBFF3831E2825595CAF1583CAF2B75010816DF65757F4BB4BC58E
011FC5CC50F220EC72ABF672E8C9A29821D4A106603187276492C366618C68CECF60AA6D4B4
F03505EE0BEB591336E130EF4593C5C11749CC3D2974B1AACD0DF19672F9330457241E201DB
7CC |
+| $m_{P114}$ | 12CE52D22E8BDFC665F49D86AC6C488C9012088FA091E5EE13B7C45A9A5CB156F147D6ACB
FF87C4817350AD15C5FC3773F3C58FD0D3B88242CC46DD43A5288933ABE5A6055FD67B1159
3C900A9654D82BE40200E38C7A9643BF25419861A2D674B84995301121FB34389CC5AC83E94
CCC738 |
+| $m_{P115}$ | 3831B0AED8C54E6F5F348C22351E35AB1099C47149117A40521B30D005DB13A81337A7EF75B
0A6FDEE2012E394935C2D61C0BAED3B65D4FC768C30F654E97BD33A54F49A2753915CAA137
F8B99861872F00F6C019DA1A2727E1FD648608CC108EFA2D85490980F7570C37619D5F4785E
A45 |
+| $m_{P116}$ | 2D7BDCD4C93F3175F441994A9B188976A7F4F714A80AF693139FBB757C1D0D71274167EEF2C
36F891612ABF8B3504FB2A1F0BC1DF24186A6C2B79A4EF118F67FF477AFD650F6BD208599D3
31C3B5ECFBD173C25D7CBB9A0C9D4E0F455509A8BEFD805201429E3192D82477E4E85D606C
53AC |
+| $m_{P117}$ | 01E085F900F58E7769F8C8A24DCA26984EE56F2D8CF0A0726508094A20ACAEF0703351EBF8E
DDC1C59012F9A3032B11D5BB260FAD321280BE48642CE84C0D3681E57784332A87DA3C06C2
CCF0993A6EC2BE1A979414EFADEEF3CEC8E12C41F55DE52D48F0B851EA968C159B9CB2D51
4CF4C5 |
+| $m_{P118}$ | 32814E789480CDAF8D0E09BF65DC4863B99B8542F0693D77ADAF6F32D0173110789E26F1BB8
F9A8A71D09DAB03FD52935945D7A4EC68C8B043B27AA81200CCA1DA23A9833217CFCAB5D6 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ |
+|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 2E0C488EA2DA2C73DB031F205D7F960E9D8918A5C652C1501EE93204D273464BEF438A94DF4496AE |
+| $m_{P119}$ | 15DD44EF0204B908795A090C32188643FBE7366EBF30DADCFB2C41953A854FEE39EAA7E9E4E58E30B45409B72AD05B43BAE11095FB1D20FB2A73E04448DEC973926BD7BA0EC291A29AA7EBDA5783A2A253649F036962A0E4525A07C66653394116352439A2520891F8E18D2CD360FFE0B111 |
+| $m_{P120}$ | 89217691E99FDDDE0598092D7413C6946390C718299455B5B455CFDE3E2E15CAE056389BE60C836B500053044568990C9EE40582F6978F91EE5ABD501408EFD805F4F64FCE2FAA5607976AC016633E12FED435EDC627548B79898DE3B5FA8B246196CB2F4289A0E3FBC7A4A911274D4CCC980 |
+| $m_{P121}$ | B3047C6EC9C960702C122202B7BA48D54A1015C1F9CA22D879FF5435C6EF930FC5EF8FD8113B48BE47D794B87E5194F8E7B4525B4CEE45FF5D0D70CCC00C67496943EBDC878DE4F9BC8849A24CFB05282B117F140A4B1967B8F4E38A0637A4E8C916914CFAC15D399174B1AA65C86DA472EA |
+| $m_{P122}$ | CED19A2B452FB08A4E677AE137AD75601BD7824CE59E4FA627A3C5AD101920FFD89328B3A917782F05781BA0292EEB18193BC1C3C02B48D272D449F381CA20B12B1C27A480C628A33AC472F2EBEEB775D3D3681A365C728DB9476CBF8744D84448FC6303BDD28BC38413277F6B61CCD4A913 |
+| $m_{P123}$ | EA7FD3D0732484865089964AFD0181F0A64E0B9BF58C20C3F34D45739C01ECDD11681E3B4D175D237A19C2800C8024FB7D3A14DDDA53180B10E8F1C569DD9CE06FF19EC958989AE43ED26E96DCA2E954BCBB6EB502F0C269EA75F5CF002BF49B383A00159C0D39AC71D502B557163616B66E |
+| $m_{P124}$ | D08DC6EE2CB2EB2D3890230CF7411F51F71024C8F05CDA7F958CBCB81B12C0CF27342431CCD1BBF61DEF50298E87ECB4A98C489D3CABDB55CE95EEAFF850BA13C0F772CD9F2943F961227078A05FA3AEE18E61657D04AA37B7F98BF5B6DDEF0F87ACAA5B4D1D2CE0622DF6B8816EFAA2F448 |
+| $m_{P125}$ | 70C1FC8BAE04C07CD256269A02056B79CD0014D188197B4BE89AF8A460026EA8FBC7C13A7793F2822A94A4A7234727516D44A5BA521E3E28C34396C69BEC8233FD0D82FA8D5B2C4F12F9284962A6F19C2E655AC44BA85F064E8D134F28F9EC479FDBFBA74223466D185CA34C7188C6E7E515 |
+| $m_{P126}$ | 82323B03B81937932EF44D0BB2A22DF5F8803080618940A4F1DED2778230FBE3D04545B86B1AAC4AFD43A90DA09148456DD81684F7C143C48C710076ED7A60BD6128BB9C4717DB97331CFB667E9EC1D4B03191B3A218B12CC957A3F5182A452694FDE1A4241B1410DD104BE1551F1E85F8A5 |
+| $m_{P127}$ | BE616513AE32C4143C92A7CECDB56F082F7907098FF61403161D95CA3767AAF7F46A8D60D66C6195D27F25FC5D0D840F7DDDD67A3E492FD9FB85A805CA0438F822BDE583BC11B74C760ED2FBC9DAC6F361EDF71B17B96B065D5E2E43A9A87A7CD561FC8F4BC809F474D68E6C4B6A7542065A |
+
+## AB.2 Basic Midamble Codes for Burst Type 2
+
+In the case of burst type 2 (see subclause 5B.3.2) the midamble has a length of $L_m=512$ , which corresponds to:
+
+$$K'=8; W=57; P=456.$$
+
+Depending on the possible delay spread cells are configured to use $K_{\text{cell}}$ midambles which are generated from the Basic Midamble Codes of length $P$ defined in Annex A.1.
+
+- for $k=1,2,\dots,K'$ , only, or
+- for odd $k=1,3,5,\dots,\leq K'$ , only.
+
+## AB.2A Basic Midamble Codes for Burst Type 4
+
+In the case of burst type 4 (see subclause 5B.3.2.3A) the midamble has a length of $L_m=640$ , which corresponds to:
+
+$$K=K'=1; W=256; P=384.$$
+
+Thus for burst type 4, $K_{\text{cell}}$ shall have a value of 1 and the midamble is generated from the Basic Midamble Codes (see table AB.2).
+
+The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223.
+
+**Table AB.2: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5B.3.3 for the case of burst type 4**
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ |
+|-----------|---------------------------------------------------------------------------------------------------|
+| $m_{p0}$ | A88E403803494ACD25F9E40A2DCDD572F13461ABE91E3931AE9BAA94CB6250B33216EC49AE028C3BBC10389C97F8652F |
+| $m_{p1}$ | CC81718FE2E076D4CF6787847831AAD28E7B131136D8F6BA65B6F32240918434A3F445405562FB1449F10E152DAF8E57 |
+| $m_{p2}$ | F40249685685DC493F2F7B8FA91E3373C9CC902C0BD54963EB4661355AE6F0CAA345E3043FD5943520360E136708D755 |
+| $m_{p3}$ | 7699416BBFC40E597656AB7B319EBEA4B6B898BA357DC20BF01A36A2FCBBC1191012836E532F0F16EDF1B1CEF8C8B8CF |
+| $m_{p4}$ | FAEFD4A1EAB45332B43D34DD877032192973A4D6F3DF1394E26FCB2FE608A777FBACAFB87B8598AFEC0387456274D828 |
+| $m_{p5}$ | D7E24FEBBDDEE2558FD4B77BE0F9C79D86192A829A93A8B8B4D93322B1ED2C5D8408D9F64E75390B7FA9E471EE94503C8 |
+| $m_{p6}$ | 419C96CBF5D07CF7E8CA5F0F768F635EDB2AC91013955685FC464F533BC0A7258D1F820E79FB4E3D64AAC88DCDBB3089 |
+| $m_{p7}$ | E3A9C7C56BD042B22E63B7A593F95A82FF67F59F50DF76D419022A69C986F86F98C0D3981B3297BA8844BB0E9CFD7C81 |
+| $m_{p8}$ | 6D15CF45BA384523320B323033CAD89B6738F7AB22D252DC51AE9EE06F290819C6BE3F7F9A07DE5BB70E57E8F878BDE4 |
+| $m_{p9}$ | D8EEF2FB18D658B7C0BB3A1186FCCB4F5EFC5768F6989946D7858A678EE850D90BBF2520B92A7131143B9F7EB9F92E8A |
+| $m_{p10}$ | 13C613CF8AB1ADBB998FA7E415710C87FB2C4C64B040E153FD2A8FD05DB395B4BC4BBF5611855AD3F354DB99F1A7364C |
+| $m_{p11}$ | 64B93D117F33C1FB4BDCF82823C977CD7F749512ED50B51D9399EEDEADF57C39B1EEFD1823272C26121F74967803ADD4 |
+| $m_{p12}$ | E9757EF85FFC178DD991A01C81AE8A36E47B1450E6DA60C96967E798E47B43C3BABE4AE7FEF186B305E6AEDDC8D0A4A2 |
+| $m_{p13}$ | D83562B863CAECEB41458179A04E4D90DA7B6F15C627A81480ACF210A3403E7E60506E859665EB6AE94BB2079988DBCF |
+| $m_{p14}$ | 54D018301703F6E38A1DB4496DB91650AA4715A51D4D1807401CEC4AFEB6368B9AD50A15FB7238935963FB0987671C8 |
+| $m_{p15}$ | 20176660D98A8C4D0442BDF1F0EE3FB4D1684B7A93684FA4395B784D1CA8838A238F28AFE9003C4D3EC0562C5E79DEA6 |
+| $m_{p16}$ | C5771FEDE124CE07C75F48321D8B0EEF34275CFFDD49F7D59685CCA298D09D36A558C903E2EE5C74A20EB02E50FFBF9A |
+| $m_{p17}$ | 7B2AD0AA898419CE863FA812CF47B32F369C9A404A936648F0DBBFBF521E822635E7A87B17C138E2357E957737F4D67F |
+| $m_{p18}$ | 0005E4C456A52687FB8C38217E39A6CBCD18EC8AC6951F7482CC19BACE70BA1E6E116AA6A5780F656C72B49EAFCD0312 |
+| $m_{p19}$ | F7561674AA43738CC1EFE9434061CF17B8FC55792BFFBEEA2B61F5E1A46BB14B19926DC98BD4B747166044BC0F652693 |
+| $m_{p20}$ | C1F98B595BFB89F7F40B1D84965981E7035455112C337DA389E04D8146B6F40D83352895247E53142A8D7BF7063A0E88 |
+| $m_{p21}$ | 2374B1EB35DE57B4114DA547D25C39887663800D53E7C0A4A8A97525E7E364FA011B23A113A4C1067763DA770E58CAEC |
+| $m_{p22}$ | D3E5382DF383595C983C2CC2369703A5867C84AB2EBD9C72044EDD8CD5683BDF4CDF10ED04D4DEB1D3D459020247A206 |
+| $m_{p23}$ | 7344E4A74618745A817E7036FF6535629AF647E852129F6F70887CEAA8393DC859725FC7BD52CDF241B31FA7BEDF9BD4 |
+| $m_{p24}$ | E1EAA999935A9C04CE360B3077241EF63FE1103A3C15AFB1CFB7AEFB93CCD5357B0068E70F28EDA990B6906AAFFA4D2 |
+| $m_{p25}$ | 39BF69ED889CD875DA83108FEF691ACD1FFAD5B5E76218318EB45DEAB2022D82455B592C1FC550FE197165A07E346D5D |
+| $m_{p26}$ | B817C216E9A0A224D8E5A4DF3F68D53BBB89B156261C5FD877FA96352A073B6B0E53BCF0765093DB7AF0C6E13AD98BE8 |
+| $m_{p27}$ | 075DCFDE008B110F56C59A61219770846DAA58B896D4914047EF786F03E13F985B03BBE4FB3B352A19548163C5144B69 |
+| $m_{p28}$ | 913AFDAD21CDAB1D363C8FFEE158E9EB5EB699D54DE5E65770A963D349744BC935C4ED0C49903CFA0F13EEFEE3BDD511 |
+| $m_{p29}$ | B6C348E72A210714B90035C905F22D6777849F28C0922E3356DF84F655896C2E8E8DAD0C1AABD7CC81633CEA68E8AC47 |
+| $m_{p30}$ | 51813E8CB9F2259B52C62FA1955034D0BD52B39C108EC46D3AFF6F8F8C3BDD1ACB3725345CE83C0AD7DCDBEC4547FC96 |
+| $m_{p31}$ | CD1DDE061856436714BEDDE2EE9DE7A9A2D795125FBE023A13AE1DE727EAF0B6265AAD72BA3BF4C40C82996F486A50EE |
+| $m_{p32}$ | 1690CBF556A6D9268773D5840033E9DF832FFBE2BD0F09D93DFC18E92340EF9CFD11BB6331 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ |
+|---------|----------------------------------------------|
+| | D7D572D7D17CECAC6D2D23 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ |
+|-----------|------------------------------------------------------------------------------------------------------|
+| $m_{p33}$ | 244048BA6D32A3793E12532E670BAA42EE28BF58116F67B9EDD184E1861476D928447A874A1
EB0A6A43F1760EB19B83C |
+| $m_{p34}$ | 81FE8B4F56FC4BCB5E1366CF41E6C559FC109846FFF538636862AA52A5F12E1F974B656D381
1C882A30D56CF2775E473 |
+| $m_{p35}$ | 921F5B3F5FC92ECE95B09141BAFC214696D1E534E711856E327FD1D8823D4854C510E6C381B
ABC0B29C600B193F9130A |
+| $m_{p36}$ | 50A3DF0CC1B0A1BB8573F7F973106FBC94504D86DFDA067C119072D8745FA8D6A263D07DAD
DA3723ADB439BDE5DB539E |
+| $m_{p37}$ | C3C0412A03C79A6A77AE17DFD4C56963BB56550C3745C9A5DF8E68855CCB60290CDC0F314E
260AFF330194A62CD4DB44 |
+| $m_{p38}$ | 66B2C238B87005022F58273FA04E2C590C6D710ADE4549E735E99E17D1170A1244AED82D51
465FF3FB6416C179C246C |
+| $m_{p39}$ | CC0D235E5D80947EB754EFC63F6EECA6F0B9D9197C24C7A14CD72CAAB26A8F5386A231B77
A3AE0D204369C57DF0D8E6B |
+| $m_{p40}$ | 6CBC1D14CFB4B14362940B67BFFE9B3C333F1DD8A97D9F947292EC91A3D01BE0FCED3529F
78AFA2A2F74213B87218E6C |
+| $m_{p41}$ | C3119C5FF33FC2CB957EBB2E9B993A85BD70BB99E3A6CDA07E4343ED282293A5F4E7F9C9E
D356B322C38259FE10EEFD4 |
+| $m_{p42}$ | B684A2F64D90CAB23140481057AED62E36315FD5759ED05747E4A149E784C78C52FC09EF812
32BD1C1647C95CE10CCC3 |
+| $m_{p43}$ | A70B5E173176C74A6CD11BA10D026B8C86BB44814CD7C27C0A03137CAB8725AF6CE05F7A6B
2BA9BCFB1072A8152843A6 |
+| $m_{p44}$ | 9257486C5A5AEA7B21B9D736FA20C34C22AA3FBC1EC9B66CAB8F8625DE7F4522DDFD8D7A5
22F6AC31AD7B03463310C1E |
+| $m_{p45}$ | 1FAEF03FD59EC8BF1FA57595018F1F7EF9F4517CD0F1AC5B82FED8877AD34E7333F06C3D5B
CB3592B2B1084036664A51 |
+| $m_{p46}$ | F838C88284898DDA2EBE40972DA884AFE7912367CBCF5453894E639EA54A053653E888038530
BC516737C43786A5F2C0 |
+| $m_{p47}$ | 1171FDDE14B8A432BAA6401868CEA05A02572C83FFA26E16444B0AD21C67B3F190D9C3A61C
3F123523266BD232BC4BB5 |
+| $m_{p48}$ | 6055579BEFD3E751073BE2EF913BE962643CA37C14A172E607C7A8A8C57B521D34B121ACF6
AFE419DC7E4DE665239251 |
+| $m_{p49}$ | 5D9DA3875FF37C084F7917873538EB73E66B62B74B82EF127855AAF990DF7D2D06FEFB33168
1846B928BDE429E01551C |
+| $m_{p50}$ | 24A63008BB9355A32892C8BB5F50D6B1B0007563BB7E2526DF1C9D4C2439630E9EA3E8FC6FF
A34E297324EF00AD1D063 |
+| $m_{p51}$ | 2E64310629FBDD2F27B3487A7882789B23B833273D1E7AF4E7DF99E26555DA45AAA7BAD244F
A71B00B6155C0CA50EFE9 |
+| $m_{p52}$ | E47949C3577D92C3635CB7A96E8D63A778815DB1324053579BA12560B46E7EF7B935183E3DE
0A79FE88FF857B90DF2A8 |
+| $m_{p53}$ | D11CD2FCD449E3504A3CB8A92650B9376A927F882231507D9FC7A851AF31AD0977E1DBD594
52532C0E841E82501CF8B1 |
+| $m_{p54}$ | D9173DEB459627122EB6F6E27B11FFFF944AD65E9F2729FD0F340486AA4F2E58CA7647C25DE
C30FF55530922C46314F9 |
+| $m_{p55}$ | 70ED8ABA76E26BC7C9E8748930944691EC16B7F70204273306D10824DA33E8A2EF190FA80E
D616212F2926A8457C7DC |
+| $m_{p56}$ | D7CB3386C837EF00E8E56C07A3620AA239E182929956B9423B364E3117D2E6165EDE6FAF13A
009C4304AF6F3A5154ECA |
+| $m_{p57}$ | E1671C07DDCF6CF5DF9A9E0CD9E6FE5C56E21CBF48028EEF2DC57993E44A46C1D32B0DAF
DA39695EEB5D8AE603315355 |
+| $m_{p58}$ | 036B1806C6F2E9C263C0470BCDE197D43C8B9A2046A26B8FDAAC49FFA1E6096A7E87229574
A67B7BB7FBEB9754A7EDB |
+| $m_{p59}$ | BE3B978749D105923F6B5D8FB00F96D7C9B6C50989513D7197FE2C5DF74BEF6B328B9E884C6
BF848A9C57D0C42613CE5 |
+| $m_{p60}$ | 54195927E67F3D1A28EA929625B6FD934EBF60662A37D64B2BCCFD8A3C806E5EDEBE9BCFC
37F7EEA5026E071C2F10CEB |
+| $m_{p61}$ | 088C7E3F08322F71C5234A2DC35A19E385FE21BEE0CC9C2E6DF7E9F4BE424B86A583F64A9C
EABA6FE76E0A9D9DAC9545 |
+| $m_{p62}$ | 2BD321E1A7ABFAAC6CF26EE71D2EC4373C05FA907BFDD3C929446FCE9714F98A89A0F41260
E658C8BDEEA291EDF5ED3F |
+| $m_{p63}$ | 0CACCF6119FFB876DC319D3F95AB34899FEA7DA7C264A8B897087F5D58776F4978D9F4A8DF
40E0858655C82E7974F3C0 |
+| $m_{p64}$ | 370B1A0FA2DA6E5F8B79D567C59404BB5DCF7584C3193BD37CBF1CFE465FC28EF6F15634E4
6B7620CC3AFE5482ADCD40 |
+| $m_{p65}$ | C4EF59CE4C46245B85E50AAEBDA987F51614860DBF05A0BF66706D08B2CBEF9306A9A3A811 |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ |
+|---------|----------------------------------------------|
+| | 7682CD40A02C394DA8563B |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ |
+|-----------|---------------------------------------------------------------------------------------------------|
+| $m_{P66}$ | 3C77FF11EA6861254F844E393C6D8856939780A8A1F86148AE88E8C09320627CE6176936FF96ED6642AE7E33A82C5599 |
+| $m_{P67}$ | A5AD10EFCF9DE41D6436B38590FFF5C582B9AA60ED65FE5596DE566CED7E8E41C11156B5418926875F06DBA319CCDA1A |
+| $m_{P68}$ | 82B543431DDF83D2647C3778A41BCAD41295CDDD0A496D133E2F5F4577582F7D377AB993CF18516298EADFB3BE01AE7B |
+| $m_{P69}$ | 027F6793D64483CF5569FEF03190B2190CD0A210AAED5C13D8A726433660F8095A6A46715276050C77B2FBA0DCF5A3C5 |
+| $m_{P70}$ | B37EECA1A844DA19736EF3C5FDC6E3571BC7E04FB0A1E2522D1A39E21A0BF2D1D066BB9C0B99F6CA0D3A82FB7561272E |
+| $m_{P71}$ | AB07BD3A4F83028263156FF5E307FD5D253689D76A8AE789691F339258EE9BD1EED8DF3C3E625E325B28A96A467FA181 |
+| $m_{P72}$ | 2A7DA74C4C39B7BEE0CFC2C9F22E00910EC527B3515F486A767FD63B4C72C24F87EEAA337E3357B868D6B88C6A19FE2D |
+| $m_{P73}$ | 21008CAA6C91705013C5753F1400B994BB1F197327B09D0E7DC7DA0A6436DEB19835E26A949051EF75DAE4BF7864250F |
+| $m_{P74}$ | 3CB53B21CF1908B000B5675EA9FDC8DD3501FD7C5CB77A3C48C6EDA3F4D6133E9EC68374E708978B296CCD708C75DFDA |
+| $m_{P75}$ | 6F9CF0F9C735DAEEE85F6EEB096A163D18DFB7D165F2A9BBECBE152C8CEEBFA32CEA5816A4966469DDC92CC095728360 |
+| $m_{P76}$ | 597EC8A534D095769B15D0337343CCDCA78E696E9C7F18E7BE1C4C474FCFFCBA2E4EB257C04012BD7094ABAC47842FB5 |
+| $m_{P77}$ | 333D73827842A2203FEB548072C28C290492A2B355EDD78C1B65E0ED270680E67B98929EE5C89743A78FC342CCD00AFE |
+| $m_{P78}$ | 5BF3C14AB0643D1DBAE821BACFFD1A47A6FE901F2338162624331AFC25A2A66E38EA958114398D13E4FB4699A4051AC2 |
+| $m_{P79}$ | C99275C3D2108C1C9BAFD62AD68C51DC57ACBBE8B263A18868F4A1A89823C914FE19C85B4163B4B10177A2B0513FBC2C |
+| $m_{P80}$ | 4C66765966E60CB0B1D25566FFD085EBE34571B31C820D42F30A53BA4BB2C3C220DB0B717C7D3961DED7902B25FFF67D |
+| $m_{P81}$ | 1602E7FB6ADDE8FE385D43E33322D734D8E7B920CFAD9F71ACAD855C71A57B8B40CEC5ACA32E073B642E070B6A6A2AC |
+| $m_{P82}$ | 5B43BD325ECE4E2DFAE4DB8C861F5A7445897406EBCC625E075184D18440B395DC4EDABBC20E29518A41F7F1652003A9 |
+| $m_{P83}$ | 3FF81A8A1493C202BB1062C49D88395F74DAF53A69BA63896571383099CA5F8B915E0670867C61EC8A794FAAC0A44A17 |
+| $m_{P84}$ | FF8DBBA2E6C93F02CA775F8510E975E825AF2F43D3818746BB4BF930D54E84EF5E34B447CC375DE50CF61436C62DDDDCD |
+| $m_{P85}$ | 40D95EFAD7A7D2B1E00839BD4892ADB5CD1F93B8BAF7CFE528BAB563AF711CE5A6A4C1C9019FC705FE07A8364B9BC866 |
+| $m_{P86}$ | 531F4E313FB8FAF0B40B70B65DD7414C4CD9028D34CE27730690B5BF05FA3C7E5F0FDE11AE A05A450BB358433FFABAF3 |
+| $m_{P87}$ | A2FF0392249EB69A3EE41A07D50AAB42B1786988D5C3569D31238B86320529825A03432995CCF599561A6E728C1077FE |
+| $m_{P88}$ | 6FDB10A9B40B83D1D5335E99DFDCA540CB0AF54157145634F60AD3690EDED4688BFFBB1C36F38D95ECAFFC363D1C32DC |
+| $m_{P89}$ | 92E6BBCDAD4D50572520D0FA4D6957A844180CE6B56814CDAC0D01FCD45973860CCF95D0438D2E99740EB6247F362BBF |
+| $m_{P90}$ | 64F199A6673EEBEE362837001ED5CB04C787CA34B5812D1EB9ACDFC26BD8CF7D6837A3E175776E47EA7BA8A185BAEE02 |
+| $m_{P91}$ | 677B0CDD0AA2362F9FE396A86105F98DF40DA2F6F9056BEC59D4F58FDF9F8B3C96CB75691229298B087CECCE960FF58A |
+| $m_{P92}$ | DEF9FAEEDFEFE2419FA4B449D1B89B5682E2737893D73861E8896751C98EDB97FE420C49B47BD5C613C6FA4975D45C9E1 |
+| $m_{P93}$ | 1726AFC63875C59FE90AAC65B025B474391B5260DC7CE6BB922B02ECBFA91C53B9110C02AA5251ACF6E8C1360B26A00E |
+| $m_{P94}$ | 35312E77E51F7B5DE09F130BB39C8EAF2CEB52F25D1E212FF6ED76A1FF24B777C40887143C8A62794595D0B1D0BF2CD8 |
+| $m_{P95}$ | 5D24F5A606D43E707271201EFA13E6895BA4F2902A20A40D58E238E601644ADA7CD86D9E99C5656ABF1202B6CC8E43B1 |
+| $m_{P96}$ | F80DF53DF2589FF24B7B328D55FC7F0D48FB86C29C29621C6A430B08AAFB7D5AA85198373A77F7B12892E881C3926E7A |
+| $m_{P97}$ | D052486802107E23E728599BB13AF620978666D0D7754F5865C0D22E9360DA73D581D8C4438EBC5C2C3D56C74222297D |
+| $m_{P98}$ | C31DC3517E333297B221A9F7CE515A937E73E7CA83267C2E9F5EBEAE1B2560FE08ACEDF23F |
+
+| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ |
+|------------|-------------------------------------------------------------------------------------------------------|
+| | 36BC3ADE463F2D54D20846 |
+| $m_{P99}$ | 88A39E4C76F47734449643EEDA50D53FF03257408630A124DF37A3E1CEE6CE99774A8D4F4BB
C051610E8678D178102C1 |
+| $m_{P100}$ | F97DF22FC49643368615CF1AE6D533DF665526FF687D6700FDABAE8508387A0F3C8CC570095
33C6CB4E6BE4745BD79D9 |
+| $m_{P101}$ | CA8B772CF3F8D8DDA7F6F150055AC969C3DD65E9877C874BF8FF647059C4F72A73571B46913
EC206CAC682EDDCB01563 |
+| $m_{P102}$ | 211E6E505E3B7C4BDC9DFAF1EB0457627847593C0557E1426A1DA992CDF40CCADA7C9FA6D
ECDF1D3CCB9C23DFCFA6B1 |
+| $m_{P103}$ | 548D9792FE5C5707FB28B1277DB9735FA78847F0DA1D6C153EC719BBDD5187C496F72579E6
C74405859C218A03B9FEA3 |
+| $m_{P104}$ | 49FCBC2408159269EE42A32A5F0F44D1D30DC91756E274E573DF961E7B05DA1C532AF3036B
B31BFE77AEBC37051FC96A |
+| $m_{P105}$ | 09C767858FB0AA0BCFBA1FE6BBEBEC75765BDA2456959A84FE9161E2E5F4260666D3FEBA71
924E26447BAD5B92E58E79 |
+| $m_{P106}$ | 622AF5FCD674D2C2D87205243E19B1C65726D78513C8FB88945A5F38D1C6400411753F63402F
6280CF702ECD6852E4BD |
+| $m_{P107}$ | B53353D78D382A74373C16B36888D56575DD25E5701E7F8C8619DB360B422632E7002905B16B
1B6D9BD5023B815C2C6C |
+| $m_{P108}$ | E183A082E8344992730B23036E315AED6E156FA27045DF86B067A99FB68D2DFA3201205457D3
BD31A88F0BD88BF8C32D |
+| $m_{P109}$ | 9AB97BB759FDDE364A61F5158E6938AE346A03F6D073D0C4ED838015ECF56477D736A487650
670FDD6D0AB1245EB60FC |
+| $m_{P110}$ | 08C36A4F926400AF9A17D43CAF2613A9D639549C94EED7CD6FF00E60D985DAFC394AB8BA4
CCC9EBFC7939D5C3AB27FEA |
+| $m_{P111}$ | 9881A3B723E688515287243A605FA52838AE13E94BFBF4D97D6E04530C2EE43906F7F81019E8
6AE4B32504A92F399AA1 |
+| $m_{P112}$ | 2807EC91A1E3CC4847A758D16EAFE7E3AB0DB5180A978BFF7450F06778DA79CAA15E467B1B
CCBF6992DEC69AE88D89D3 |
+| $m_{P113}$ | 9E9A5527723F3A4F339E828920D2556D21CD5E6FDC89B6575AF9FFA38233BBC05E8F2AE7052
AC7DBF622BF369A76F0E2 |
+| $m_{P114}$ | 71812CEECEAC08C71C633D4C815AD805555A6ED7A778FD5F4D4810E5D92DA662B6836015E8
F9303A79798493E4166CC0 |
+| $m_{P115}$ | 4147CB2F5C019034CADC1EBB6331B3DE37197611A6635B0784B4BF0DBBF12AEEAEA3D2E794
B9C1B6BB97FCC9D408DAAF |
+| $m_{P116}$ | 445499D892AE276B0C2CE2BD81924E91B6A8D072EA3E63503F2287EB5F5E639EDE88082C164
18FC294E08D069F4CC127 |
+| $m_{P117}$ | 66EE0C821076D702D1D5C35D37F25F0DCE3C8692B9CB65C4CEA5579F5AC3EF25CB06691B7
6DE6D972AF370A27F1415EC |
+| $m_{P118}$ | D60A097019B8C9171A344854DDDCF6472F39DE9B9447956F78B60763A80EF6CF93B650E7B0A
81D59DD4B0FCBCD25FB0E |
+| $m_{P119}$ | 7244FEA50F90D284132D7DFE7E93C0EF16DA1A10765118691471255518CB76C44AE6B274C0
D3BC5C143B06AEE07615B |
+| $m_{P120}$ | 8D6B45351ABE278271368F0E2DA5EE5BD014746202478243DAC30EB011326BF99845BDAADF74
3D54214C193A2DF54F991 |
+| $m_{P121}$ | 42B80322CDB54071258B9B6911523E063CFC88AF918ACBBADDFE89EB7C261003E32931C3FC
BA525A48553A533458E872 |
+| $m_{P122}$ | 3E1A4867271132EB25B853FEB3B44F80F69D57BF796D71F53C46D598E5BD2D22F8347B64559
1FAC08AFCFDFE5C838317 |
+| $m_{P123}$ | 91AB7E8D6CB2EBCB099F275B1BA0C7D8D18E8A6FA2EFF169100AE4FF0ECB94F79FDDDA7F5
AD42EAC766741C96E608D6F |
+| $m_{P124}$ | E16CC4455F92D7F7AAC7D83A63E94A286AE4B9CFDBC3181FFB94CC26CFDB43DCA63A169A
20BE959E65062A5524DCCB86 |
+| $m_{P125}$ | 9E1BEC0CB9835F5FAFEB3C4A27D32A982346ADC4215F5A7237C4D1009CB2DECB9C1C486DD
ACDADEAE123F958666B0EE7 |
+| $m_{P126}$ | CB04C57E4069E0CF9D4AD9D71567C2D243A9FB0DEDEECBA8D77EBF02CCFA77B4C491915B
039FE851A4B8D9197D577A16 |
+| $m_{P127}$ | 7CB3DEC05A1E73C703BF610AC8914E2F4D63329FEFB69E1B35E86F92AB87EB27EEBC098B5
B1119CC8BD1B149B2A01946 |
+
+## AB.3 Association between Midambles and Channelisation Codes
+
+The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. These mapping schemes apply for all burst types 1, 2 and 3. Secondary channelisation codes are marked with a \*. These associations apply both for UL and DL.
+
+### AB.3.1 Association for $K_{\text{Cell}} = 16$ Midambles
+
+
+
+A hierarchical tree diagram showing the association between midambles and channelisation codes for K\_Cell = 16. 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 into m^(1) - c\_4^(1), m^(3) - c\_4^(2), m^(5) - c\_4^(3), and m^(7) - c\_4^(4). Each of these branches into m^(1) - c\_8^(1), m^(2) - c\_8^(2), m^(3) - c\_8^(3), m^(6) - c\_8^(4), m^(5) - c\_8^(5), m^(4) - c\_8^(6), m^(7) - c\_8^(7), and m^(8) - c\_8^(8). Each of these branches into m^(1) - c\_16^(1), m^(9) - c\_16^(2), m^(2) - c\_16^(3), m^(10) - c\_16^(4), m^(3) - c\_16^(5), m^(11) - c\_16^(6), m^(6) - c\_16^(7), m^(14) - c\_16^(8), m^(5) - c\_16^(9), m^(13) - c\_16^(10), m^(4) - c\_16^(11), m^(12) - c\_16^(12), m^(7) - c\_16^(13), m^(15) - c\_16^(14), m^(8) - c\_16^(15), and m^(16) - c\_16^(16). Finally, each of these branches into two channelisation codes: 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)\*.
+
+Figure AB.1: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 16$
+
+### AB.3.2 Association for $K_{\text{Cell}} = 8$ Midambles
+
+
+
+The diagram illustrates the association of midambles to spreading codes for $K_{\text{Cell}} = 8$ . It is a hierarchical tree structure starting from the root node $m^{(1)} - c_1^{(1)}$ .
+
+- $m^{(1)} - c_1^{(1)}$ branches into:
+ - $m^{(1)} - c_2^{(1)}$
+ - $m^{(1)} - c_2^{(1)}$ branches into $m^{(1)} - c_4^{(1)}$ and $m^{(3)} - c_4^{(2)}$ .
+ - $m^{(1)} - c_4^{(1)}$ branches into $m^{(1)} - c_8^{(1)}$ and $m^{(2)} - c_8^{(2)}$ .
+ - $m^{(1)} - c_8^{(1)}$ branches into $m^{(1)} - c_{16}^{(1)}$ and $m^{(1)} - c_{16}^{(2)*}$ .
+ - $m^{(1)} - c_{16}^{(1)}$ branches into $m^{(1)} - c_{32}^{(1)}$ and $m^{(1)} - c_{32}^{(2)*}$ .
+ - $m^{(1)} - c_{16}^{(2)*}$ branches into $m^{(1)} - c_{32}^{(3)*}$ and $m^{(1)} - c_{32}^{(4)*}$ .
+ - $m^{(2)} - c_8^{(2)}$ branches into $m^{(2)} - c_{16}^{(3)}$ and $m^{(2)} - c_{16}^{(4)*}$ .
+ - $m^{(2)} - c_{16}^{(3)}$ branches into $m^{(2)} - c_{32}^{(5)}$ and $m^{(2)} - c_{32}^{(6)*}$ .
+ - $m^{(2)} - c_{16}^{(4)*}$ branches into $m^{(2)} - c_{32}^{(7)*}$ and $m^{(2)} - c_{32}^{(8)*}$ .
+ - $m^{(3)} - c_4^{(2)}$ branches into $m^{(3)} - c_8^{(3)}$ and $m^{(6)} - c_8^{(4)}$ .
+ - $m^{(3)} - c_8^{(3)}$ branches into $m^{(3)} - c_{16}^{(5)}$ and $m^{(3)} - c_{16}^{(6)*}$ .
+ - $m^{(3)} - c_{16}^{(5)}$ branches into $m^{(3)} - c_{32}^{(9)}$ and $m^{(3)} - c_{32}^{(10)*}$ .
+ - $m^{(3)} - c_{16}^{(6)*}$ branches into $m^{(3)} - c_{32}^{(11)*}$ and $m^{(3)} - c_{32}^{(12)*}$ .
+ - $m^{(6)} - c_8^{(4)}$ branches into $m^{(6)} - c_{16}^{(7)}$ and $m^{(6)} - c_{16}^{(8)*}$ .
+ - $m^{(6)} - c_{16}^{(7)}$ branches into $m^{(6)} - c_{32}^{(13)}$ and $m^{(6)} - c_{32}^{(14)*}$ .
+ - $m^{(6)} - c_{16}^{(8)*}$ branches into $m^{(6)} - c_{32}^{(15)*}$ and $m^{(6)} - c_{32}^{(16)*}$ .
+ - $m^{(5)} - c_2^{(2)}$
+ - $m^{(5)} - c_2^{(2)}$ branches into $m^{(5)} - c_4^{(3)}$ and $m^{(7)} - c_4^{(4)}$ .
+ - $m^{(5)} - c_4^{(3)}$ branches into $m^{(5)} - c_8^{(5)}$ and $m^{(4)} - c_8^{(6)}$ .
+ - $m^{(5)} - c_8^{(5)}$ branches into $m^{(5)} - c_{16}^{(9)}$ and $m^{(5)} - c_{16}^{(10)*}$ .
+ - $m^{(5)} - c_{16}^{(9)}$ branches into $m^{(5)} - c_{32}^{(17)}$ and $m^{(5)} - c_{32}^{(18)*}$ .
+ - $m^{(5)} - c_{16}^{(10)*}$ branches into $m^{(5)} - c_{32}^{(19)*}$ and $m^{(5)} - c_{32}^{(20)*}$ .
+ - $m^{(4)} - c_8^{(6)}$ branches into $m^{(4)} - c_{16}^{(11)}$ and $m^{(4)} - c_{16}^{(12)*}$ .
+ - $m^{(4)} - c_{16}^{(11)}$ branches into $m^{(4)} - c_{32}^{(21)}$ and $m^{(4)} - c_{32}^{(22)*}$ .
+ - $m^{(4)} - c_{16}^{(12)*}$ branches into $m^{(4)} - c_{32}^{(23)*}$ and $m^{(4)} - c_{32}^{(24)*}$ .
+ - $m^{(7)} - c_4^{(4)}$ branches into $m^{(7)} - c_8^{(7)}$ and $m^{(8)} - c_8^{(8)}$ .
+ - $m^{(7)} - c_8^{(7)}$ branches into $m^{(7)} - c_{16}^{(13)}$ and $m^{(7)} - c_{16}^{(14)*}$ .
+ - $m^{(7)} - c_{16}^{(13)}$ branches into $m^{(7)} - c_{32}^{(25)}$ and $m^{(7)} - c_{32}^{(26)*}$ .
+ - $m^{(7)} - c_{16}^{(14)*}$ branches into $m^{(7)} - c_{32}^{(27)*}$ and $m^{(7)} - c_{32}^{(28)*}$ .
+ - $m^{(8)} - c_8^{(8)}$ branches into $m^{(8)} - c_{16}^{(15)}$ and $m^{(8)} - c_{16}^{(16)*}$ .
+ - $m^{(8)} - c_{16}^{(15)}$ branches into $m^{(8)} - c_{32}^{(29)}$ and $m^{(8)} - c_{32}^{(30)*}$ .
+ - $m^{(8)} - c_{16}^{(16)*}$ branches into $m^{(8)} - c_{32}^{(31)*}$ and $m^{(8)} - c_{32}^{(32)*}$ .
+
+A hierarchical tree diagram showing the association of midambles to spreading codes. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. The diagram continues to branch out to the right, showing associations with codes c\_4, c\_8, c\_{16}, and c\_{32} across different midamble indices (1 through 8).
+
+Figure AB.2: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 8$
+
+### AB.3.3 Association for $K_{\text{Cell}} = 4$ Midambles
+
+
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for K\_Cell = 4. The tree starts with a root node m^(1) - c\_1^(1) on the left. It branches into two main paths: m^(1) - c\_2^(1) and m^(5) - c\_2^(2). The m^(1) - c\_2^(1) path 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 further branches into m^(i) - c\_8^(j) and m^(i) - c\_8^(j)\*. Each of these eight nodes further branches into m^(i) - c\_16^(k) and m^(i) - c\_16^(k)\*. Finally, each of these sixteen nodes branches into two spreading codes: m^(i) - c\_32^(l) and m^(i) - c\_32^(l)\*. The indices i, j, k, and l vary according to the path in the tree.
+
+Figure AB.3: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 4$
+
+### AB.3.4 Association for Burst Types 4 and $K_{\text{Cell}} = 1$ Midamble
+
+For burst type 4 there is only a single midamble defined, thus all channelisation codes are associated with the same midamble.
+
+# Annex B (normative): Signalling of the number of channelisation codes for the DL common midamble case for 3.84Mcps TDD
+
+The following mapping schemes shall apply for the association between the number of channelisation codes employed in a timeslot and the use of a particular midamble shift in the DL common midamble case. In the following tables the presence of a particular midamble shift is indicated by '1'. Midamble shifts marked with '0' are left unused. Mapping schemes B.4, B.5 and B.6 are not applicable to beacon timeslots where a P-CCPCH is present, because the default midamble allocation scheme is applied to these timeslots. Note that in mapping schemes B.4, B.5 and B.6, the fixed and pre-allocated channelisation code for the beacon channel is included into the number of indicated channelisation codes.
+
+## B.1 Mapping scheme for Burst Type 1 and $K_{Cell}=16$ Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | m9 | m10 | m11 | m12 | m13 | m14 | m15 | m16 | |
+|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|----------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 10 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 11 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 12 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 13 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 14 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 16 codes |
+
+## B.2 Mapping scheme for Burst Type 1 and $K_{Cell}=8$ Midambles
+
+| M1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | |
+|----|----|----|----|----|----|----|----|---------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code or 9 codes |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes or 10 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 3 codes or 11 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 4 codes or 12 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 5 codes or 13 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 6 codes or 14 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 7 codes or 15 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 8 codes or 16 codes |
+
+## B.3 Mapping scheme for Burst Type 1 and $K_{Cell}=4$ Midambles
+
+| m1 | m3 | m5 | m7 | |
+|----|----|----|----|--------------------------|
+| 1 | 0 | 0 | 0 | 1 or 5 or 9 or 13 codes |
+| 0 | 1 | 0 | 0 | 2 or 6 or 10 or 14 codes |
+| 0 | 0 | 1 | 0 | 3 or 7 or 11 or 15 codes |
+| 0 | 0 | 0 | 1 | 4 or 8 or 12 or 16 codes |
+
+## B.4 Mapping scheme for beacon timeslots and $K_{Cell}=16$ Midambles
+
+| m1 | m2 | m3 | M4 | m5 | m6 | m7 | M8 | m9 | m10 | m11 | M12 | m13 | m14 | m15 | m16 | |
+|----|-----------|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|--------------------------------------------------------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) |
+| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) |
+| 1 | $x^{(1)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 codes |
+| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD not applied to beacon in this time slot) or 14 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes or 15 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes or 16 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 7 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 8 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 9 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 10 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 11 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 12 codes |
+
+(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna.
+
+Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used.
+
+Note 2: If SCTD is applied to the beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used.
+
+## B.5 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=8$ Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | M8 | |
+|----|-----------|----|----|----|----|----|----|-------------------------------------------------------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) |
+| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) |
+| 1 | $x^{(1)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 7 or 13 codes |
+| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 (SCTD not applied to beacon in this time slot) or 8 or 14 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 5 codes or 11 codes |
+| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 6 codes or 12 codes |
+
+(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna.
+
+Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used.
+
+Note 2: If SCTD is applied to beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used.
+
+## B.6 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=4$ Midambles
+
+| m1 | m3 | m5 | m7 | |
+|----|----|----|----|--------------------------------|
+| 1 | 0 | 0 | 0 | 1code (see note 1) |
+| 1 | 1 | 0 | 0 | 4 or 7 or 10 or 13 or 16 codes |
+| 1 | 0 | 1 | 0 | 2 or 5 or 8 or 11 or 14 codes |
+| 1 | 0 | 0 | 1 | 3 or 6 or 9 or 12 or 15 codes |
+
+Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble shall be used.
+
+## B.7 Mapping scheme for Burst Type 2 and $K_{\text{Cell}}=6$ Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | |
+|----|----|----|----|----|----|---------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 1 or 7 or 13 codes |
+| 0 | 1 | 0 | 0 | 0 | 0 | 2 or 8 or 14 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 5 or 11 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 6 or 12 codes |
+
+## --- B.8 Mapping scheme for Burst Type 2 and $K_{\text{Cell}}=3$ Midambles
+
+| m1 | m2 | m3 | |
+|----|----|----|-------------------------------------|
+| 1 | 0 | 0 | 1 or 4 or 7 or 10 or 13 or 16 codes |
+| 0 | 1 | 0 | 2 or 5 or 8 or 11 or 14 codes |
+| 0 | 0 | 1 | 3 or 6 or 9 or 12 or 15 codes |
+
+## --- B.9 Mapping scheme for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble
+
+| m1 | |
+|----|---------------------------------------------------------------|
+| 1 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 or 16 codes |
+
+# Annex BA (normative): Signalling of the number of channelisation codes for the DL common midamble case for 1.28Mcps TDD
+
+The following mapping schemes shall apply for the association between the number of channelisation codes employed in a timeslot and the use of a particular midamble shift in the DL common midamble case. In the following tables the presence of a particular midamble shift is indicated by '1'. Midamble shifts marked with '0' are left unused.
+
+## BA.1 Mapping scheme for K=16 Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | m9 | m10 | m11 | m12 | m13 | m14 | m15 | m16 | |
+|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|----------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 10 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 11 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 12 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 13 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 14 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 16 codes |
+
+## BA.2 Mapping scheme for K=14 Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | m9 | m10 | m11 | m12 | m13 | m14 | |
+|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 15 code(s) |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 16 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 8 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 9 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 10 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 11 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 12 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 13 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 14 codes |
+
+## BA.3 Mapping scheme for K=12 Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | M7 | M8 | m9 | m10 | m11 | m12 | |
+|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 13 code(s) |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 14 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 15 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 16 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 7 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 8 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 9 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 10 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 11 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 12 codes |
+
+## BA.4 Mapping scheme for K=10 Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | M7 | M8 | m9 | m10 | |
+|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 11 code(s) |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 12 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 13 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 14 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 5 or 15 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 6 or 16 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 7 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 8 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 9 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 10 codes |
+
+## BA.5 Mapping scheme for K=8 Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | |
+|----------|----------|----------|----------|----------|----------|----------|----------|----------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 9 code(s) |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 10 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 3 or 11 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 4 or 12 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 5 or 13 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 6 or 14 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 7 or 15 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 8 or 16 codes |
+
+## --- BA.6 Mapping scheme for K=6 Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | |
+|----|----|----|----|----|----|----------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 1 or 7 or 13 code(s) |
+| 0 | 1 | 0 | 0 | 0 | 0 | 2 or 8 or 14 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 5 or 11 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 6 or 12 codes |
+
+## --- BA.7 Mapping scheme for K=4 Midambles
+
+| m1 | m2 | m3 | m4 | |
+|----|----|----|----|---------------------------|
+| 1 | 0 | 0 | 0 | 1 or 5 or 9 or 13 code(s) |
+| 0 | 1 | 0 | 0 | 2 or 6 or 10 or 14 codes |
+| 0 | 0 | 1 | 0 | 3 or 7 or 11 or 15 codes |
+| 0 | 0 | 0 | 1 | 4 or 8 or 12 or 16 codes |
+
+## --- BA.8 Mapping scheme for K=2 Midambles
+
+| m1 | m2 | |
+|----|----|-------------------------------------------------|
+| 1 | 0 | 1 or 3 or 5 or 7 or 9 or 11 or 13 or 15 code(s) |
+| 0 | 1 | 2 or 4 or 6 or 8 or 10 or 12 or 14 or 16 codes |
+
+# Annex BB (normative): Signalling of the number of channelisation codes for the DL common midamble case for 7.68Mcps TDD
+
+The following mapping schemes shall apply for the association between the number of channelisation codes employed in a timeslot and the use of a particular midamble shift in the DL common midamble case. In the following tables the presence of a particular midamble shift is indicated by '1'. Midamble shifts marked with '0' are left unused. Mapping schemes in section BB.4, BB.5 and BB.6 are not applicable to beacon timeslots where a P-CCPCH is present, because the default midamble allocation scheme is applied to these timeslots. Note that in the mapping schemes of sections BB.4, BB.5 and BB.6, the fixed and pre-allocated channelisation code for the beacon channel is included into the number of indicated channelisation codes.
+
+## BB.1 Mapping scheme for $K_{\text{Cell}}=16$ Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | M8 | m9 | m10 | m11 | m12 | m13 | m14 | m15 | m16 | |
+|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 17 code |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 18 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 19 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 20 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 or 21 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 or 22 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 or 23 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 or 24 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 or 25 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 10 or 26 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 11 or 27 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 12 or 28 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 13 or 29 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 14 or 30 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 or 31 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 16 or 32 codes |
+
+## BB.2 Mapping scheme for $K_{\text{Cell}}=8$ Midambles
+
+| M1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | |
+|----------|----------|----------|----------|----------|----------|----------|----------|---------------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 9 or 17 or 25 codes |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 10 or 18 or 26 codes |
+| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 3 or 11 or 19 or 27 codes |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 4 or 12 or 20 or 28 codes |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 5 or 13 or 21 or 29 codes |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 6 or 14 or 22 or 30 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 7 or 15 or 23 or 31 codes |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 8 or 16 or 24 or 32 codes |
+
+## BB.3 Mapping scheme for $K_{\text{Cell}}=4$ Midambles
+
+| m1 | m3 | m5 | m7 | |
+|----|----|----|----|--------------------------------------------------|
+| 1 | 0 | 0 | 0 | 1 or 5 or 9 or 13 or 17 or 21 or 25 or 29 codes |
+| 0 | 1 | 0 | 0 | 2 or 6 or 10 or 14 or 18 or 22 or 26 or 30 codes |
+| 0 | 0 | 1 | 0 | 3 or 7 or 11 or 15 or 19 or 23 or 27 or 31 codes |
+| 0 | 0 | 0 | 1 | 4 or 8 or 12 or 16 or 20 or 24 or 28 or 32 codes |
+
+## BB.4 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=16$ Midambles
+
+| m1 | m2 | m3 | M4 | m5 | m6 | m7 | M8 | m9 | m10 | m11 | M12 | m13 | m14 | m15 | m16 | |
+|----|-----------|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|--------------------------------------------------------------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) |
+| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) |
+| 1 | $x^{(*)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 or 25 codes |
+| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD not applied to beacon in this time slot) or 14 or 26 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 15 or 27 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 16 or 28 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 or 17 or 29 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 or 18 or 30 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 7 or 19 or 31 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 8 or 20 or 32 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 9 or 21 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 10 or 22 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 11 or 23 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 12 or 24 codes |
+
+(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna.
+
+Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used.
+
+Note 2: If SCTD is applied to the beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used.
+
+## BB.5 Mapping scheme for beacon timeslots and $K_{Cell}=8$ Midambles
+
+| m1 | m2 | m3 | m4 | m5 | m6 | m7 | M8 | |
+|----|-----------|----|----|----|----|----|----|-------------------------------------------------------------------------------------|
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) |
+| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) |
+| 1 | $x^{(*)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 7 or 13 or 19 or 25 or 31 codes |
+| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 (SCTD not applied to beacon in this time slot) or 8 or 14 or 20 or 26 or 32 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 or 21 or 27 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 or 22 or 28 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 5 or 11 or 17 or 23 or 29 codes |
+| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 6 or 12 or 18 or 24 or 30 codes |
+
+(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna.
+
+Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used.
+
+Note 2: If SCTD is applied to beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used.
+
+## BB.6 Mapping scheme for beacon timeslots and $K_{Cell}=4$ Midambles
+
+| m1 | m3 | m5 | m7 | |
+|----|----|----|----|-------------------------------------------------------------------|
+| 1 | 0 | 0 | 0 | 1code (see note 1) |
+| 1 | 1 | 0 | 0 | 4 or 7 or 10 or 13 or 16 or 19 or 22 or 25 or 28 or 31 codes |
+| 1 | 0 | 1 | 0 | 2 or 5 or 8 or 11 or 14 or 17 or 20 or 23 or 26 or 29 or 32 codes |
+| 1 | 0 | 0 | 1 | 3 or 6 or 9 or 12 or 15 or 18 or 21 or 24 or 27 or 30 codes |
+
+Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble shall be used.
+
+## BB.7 Mapping scheme for Burst Type 4 and $K_{Cell}=1$ Midamble
+
+| m1 | |
+|----|-------------------------------------------------------------------------------------------------------------------------------|
+| 1 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31 or 32 codes |
+
+# --- Annex C (informative): CCPCH Multiframe Structure for the 3.84 Mcps option
+
+In the following figures C.1 to C.3 some examples for Multiframe Structures on Primary and Secondary CCPCH are given. The figures show the placement of Common Transport Channels on the Common Control Physical Channels. Additional S-CCPCH capacity can be allocated on other codes and timeslots of course, e.g. FACH capacity is related to overall cell capacity and can be configured according to the actual needs. Channel capacities in the annex are derived using bursts with long midambles (Burst format 1). Every TrCH-box in the figures is assumed to be valid for two frames (see row 'Frame #'), i.e. the transport channels in CCPCHs have an interleaving time of 20msec.
+
+The actual CCPCH Multiframe Scheme used in the cell is described and broadcast on BCH. Thus the system information structure has its roots in this particular transport channel and allocations of other Common Channels can be handled this way, i.e. by pointing from BCH.
+
+| Frame # | 0
1 | 2
3 | 4
5 | 6
7 | 8
9 | 10
11 | 12
13 | 14
15 | 16
17 | 18
19 | 20
21 | 22
23 | 24
25 | 26
27 | 28
29 | 30
31 | 32
33 | 34
35 | 36
37 | 38
39 | 40
41 | 42
43 | 44
45 | 46
47 | 48
49 | 50
51 | 52
53 | 54
55 | 56
57 | 58
59 | 60
61 | 62
63 |
+|--------------------------|--------|--------|--------|--------|--------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|
+| CCPCHs in TS k, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CCPCHs in TS k+8, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+The diagram shows a horizontal sequence of four channels: **BCH 12,2 kbps**, **FACH 25,93 kbps**, **PCH 9,15 kbps**, and **PICH 1,53 kbps**. Each channel name is enclosed in a rectangular box, and they are separated by small gray vertical bars.
+
+Timing diagram showing the sequence of channels: BCH 12,2 kbps, FACH 25,93 kbps, PCH 9,15 kbps, and PICH 1,53 kbps.
+
+Figure C.1: Example for a multiframe structure for CCPCHs and PICH that is repeated every 64th frame
+
+| Frame # | 0
1 | 2
3 | 4
5 | 6
7 | 8
9 | 10
11 | 12
13 | 14
15 | 16
17 | 18
19 | 20
21 | 22
23 | 24
25 | 26
27 | 28
29 | 30
31 | 32
33 | 34
35 | 36
37 | 38
39 | 40
41 | 42
43 | 44
45 | 46
47 | 48
49 | 50
51 | 52
53 | 54
55 | 56
57 | 58
59 | 60
61 | 62
63 |
+|--------------------------|--------|--------|--------|--------|--------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|
+| CCPCHs in TS k, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CCPCHs in TS k+8, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CCPCHs in TS k+8, Code n | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+The diagram shows a horizontal sequence of four channels: **BCH 22,88 kbps**, **FACH 36,6 kbps**, **PCH 12,2 kbps**, and **PICH 1,53 kbps**. Each channel name is enclosed in a rectangular box, and they are separated by small gray vertical bars.
+
+Timing diagram showing the sequence of channels: BCH 22,88 kbps, FACH 36,6 kbps, PCH 12,2 kbps, and PICH 1,53 kbps.
+
+Figure C.2: Example for a multiframe structure for CCPCHs and PICH that is repeated every 64th frame, n=1...7
+
+# Annex CA (informative): CCPCH Multiframe Structure for the 1.28 Mcps option
+
+| Frame # | 0 1 | 2 3 | 4 5 | 6 7 | 8 9 | 10 11 | 12 13 | 14 15 | 16 17 | 18 19 | 20 21 | 22 23 | 24 25 | 26 27 | 28 29 | 30 31 | 32 33 | 34 35 | 36 37 | 38 39 | 40 41 | 42 43 | 44 45 | 46 47 | 48 49 | 50 51 | 52 53 | 54 55 | 56 57 | 58 59 | 60 61 | 62 63 |
+|-----------------------------------|-----|-----|-----|-----|-----|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|
+| CCPCH1 in TS 0, $c_{Q=6}^{(k=1)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CCPCH2 in TS 0, $c_{Q=6}^{(k=2)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+| | | | |
+|--------------|-------------|-------------|--------------|
+| BCH 13.2kbps | PCH 8.8kbps | FACH 11kbps | PICH 2.2kbps |
+|--------------|-------------|-------------|--------------|
+
+Figure CA.1: Example for a multiframe structure for CCPCHs and PICH that is repeated every 64th frame (128 sub-frame)
+
+| Frame # | 0 1 | 2 3 | 4 5 | 6 7 | 8 9 | 10 11 | 12 13 | 14 15 | 16 17 | 18 19 | 20 21 | 22 23 | 24 25 | 26 27 | 28 29 | 30 31 | 32 33 | 34 35 | 36 37 | 38 39 | 40 41 | 42 43 | 44 45 | 46 47 | 48 49 | 50 51 | 52 53 | 54 55 | 56 57 | 58 59 | 60 61 | 62 63 |
+|-----------------------------------|-----|-----|-----|-----|-----|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|
+| CCPCH1 in TS k, $c_{Q=6}^{(k=i)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CCPCH2 in TS k, $c_{Q=6}^{(k=j)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+| | | |
+|--------------|---------------|--------------|
+| PCH 13.2kbps | FACH 19.8kbps | PICH 2.2kbps |
+|--------------|---------------|--------------|
+
+Figure CA.2: Example for a multiframe structure for S-CCPCHs and PICH that is repeated every 64th frame, $i,j=1 \dots 16$ ( $i \neq j$ ), $k \neq 0, 1$ , (128 sub-frame)
+
+# Annex CB (informative): Examples of the association of UL TPC commands to UL uplink time slots and CCTrCH pairs for 1.28 Mcps TDD
+
+In the following two examples of the association of UL TPC commands to UL time slots and CCTrCHs are shown (see 5A.2.2.2):
+
+**Table CB.1 Two examples of the association of UL TPC commands to UL uplink time slots and CCTrCH pairs with NULslot=3**
+
+Case 1: $N_{UL\_TPCsymbols}=2$ ; Case 2: $N_{UL\_TPCsymbols}=4$
+
+| Sub-Frame Number | Case 1
(2 UL TPC symbols) | | The order of the served UL time slot and CCTrCH pairs (UL time slot and CCTrCH number) | Case 2
(4 UL TPC symbols) | |
+|------------------|------------------------------------|-----|----------------------------------------------------------------------------------------|------------------------------|------------------------------------|
+| | The order of UL TPC symbols | | | The order of UL TPC symbols | |
+| SFN'=0 | (1 st
$UL_{pos}=0$ ) | 0 → | 0 (TS3) ← | 0 → | (1 st
$UL_{pos}=0$ ) |
+| | | 1 → | 1 (TS4) ← | 1 → | |
+| | | | 2 (TS5) ← | 2 → | |
+| | | | 1 (TS4) ← | 3 → | |
+| SFN'=1 | (1 st
$UL_{pos}=2$ ) | 0 ↘ | 0 (TS3) ← | 0 ↖ | (1 st
$UL_{pos}=2$ ) |
+| | | 1 → | 1 (TS4) ← | 1 ↖ | |
+| | | | 2 (TS5) ← | 2 → | |
+| | | | 0 (TS3) ← | 3 → | |
+| SFN'=2 | (1 st
$UL_{pos}=2$ ) | 0 ↘ | 0 (TS3) ← | 0 ↖ | (1 st
$UL_{pos}=1$ ) |
+| | | 1 ↘ | 1 (TS4) ← | 1 ↖ | |
+| | | | 2 (TS5) ← | 2 ↖ | |
+| | | | 0 (TS3) ← | 3 ↖ | |
+| ... | ... | ... | ... | ... | ... |
+
+# Annex CC (informative): Examples of the association of UL SS commands to UL uplink time slots
+
+In the following two examples of the association of UL SS commands to UL uplink time slots are shown (see 5A.2.2.3):
+
+**Table CC.1 Two examples of the association of UL SS commands to UL uplink time slots with $N_{ULslot}=3$**
+
+Case 1: $N_{SSsymbols}=2$ ; Case 2: $N_{SSsymbols}=4$
+
+| Sub-Frame Number | Case 1
(2 UL SS symbols) | | The order of the served UL time slot (UL time slot number) | Case 2
(4 UL SS symbols) | |
+|------------------|------------------------------------|-----|------------------------------------------------------------|-----------------------------|------------------------------------|
+| | The order of UL SS symbols | | | The order of UL SS symbols | |
+| SFN'=0 | (1 st
$UL_{pos}=0$ ) | 0 → | 0 (TS3) ← | 0 | (1 st
$UL_{pos}=0$ ) |
+| | | 1 → | 1 (TS4) ← | 1 | |
+| | | | 2 (TS5) ← | 2 | |
+| | | | 1 (TS4) ← | 3 | |
+| SFN'=1 | (1 st
$UL_{pos}=2$ ) | 0 → | 0 (TS3) ← | 0 | (1 st
$UL_{pos}=2$ ) |
+| | | 1 → | 1 (TS4) ← | 1 | |
+| | | | 2 (TS5) ← | 2 | |
+| | | | 0 (TS3) ← | 3 | |
+| SFN'=2 | (1 st
$UL_{pos}=2$ ) | 0 → | 0 (TS3) ← | 0 | (1 st
$UL_{pos}=1$ ) |
+| | | 1 → | 1 (TS4) ← | 1 | |
+| | | | 2 (TS5) ← | 2 | |
+| | | | 0 (TS3) ← | 3 | |
+| ... | ... | ... | ... | ... | ... |
+
+# --- Annex CD (normative): T-CPICH bit sequences for the 3.84 Mcps MBSFN IMB option
+
+**Table CD.1: T-CPICH pilot bit sequences for the 3.84 Mcps MBSFN IMB option**
+
+| Primary scrambling code index $n$ | Slot index $i$ | T-CPICH pilot bit sequences $B^{(n)}_{T-CPICH,0} \dots B^{(n)}_{T-CPICH,959}$ in hexadecimal representation (reading from left to right, then from top to bottom) |
+|-----------------------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0 | 0 | B8BC9229F99056BF241881D6EDFD552DDED31C7E5CB4830D2C88B7949337D640E518702906868AE4
F0D2E4EF09DCE5CD845CAF825488880EC5FC89408420FFD854389FE54E5AEB782B4447049A3B1810
C3574F0DB9C88A8F0DCF11ECE48ECC5A872D9EB65270EB5113004A8500E6B7EEB46A79CD5B9E1742 |
+| | 1 | A619B3A7F98FAD8EB1C5A49B826DF7E600A2A26565B4B31079586E83F864340538C2BA87E957A7B8
FC30E32CFB648F8529110A492AB99CD6820E84064C6F8C1E08CBCAF8492D97A0CF135BCE0ED9C484
5ADDE53A1545C943D4982F0D1CAD790BD7B349959C840C4B1798CC9C666EC934EC544A4E42AFF00 |
+| | 2 | 4248448A60CDC808CEE8DA329AD54888F3B74035717A9ADE41A2EC0AEE4DFD006D4EC2EB5D72D50D
9DC8A76D9646749EDC6003918938455DAE0A5C008A008C3074A58F00D88FAB9B12936CC672528C36
24B9CF484EA0E91AE617B94A9B4144C9D1FB321B16184187FDAC28C5495CB94F41C819096626641F |
+| | 3 | E7D15E21FAEEAEDE08C75EC4CC49C9C30BE4098C1AEDC781D99C13575248A207D51525A52964D8
FF62E2D64FCA2CF838A96FAB92397AC4B48CE614A8EDEAA0736CEE29275951CC189A2012D292E433
E098AF3C01B43D10B946355CCC55C1F85BBA6C80794FEF080793AD070F104C10CAA8828B02E7B4A |
+| | 4 | 64EF0E94CE9129C86724EB94583C257C647D63548480D9344CBFE1A9D28163E549AF594EA6D25AAC
1F3E72FFC18109095600C2DA848D2382AEDBEF410C374C20C10AA2DCA53A7983842DF2CE81F57051
8299D57D9E97D4C90AEEDCEF16646A0416C968841E12B7672C94FD4816FE154EE990290849C2EE56 |
+| | 5 | 1D922F3889C4D6606EB1D622E65EA16F4F28B40B49E90C49B62E84F1E4C04D2D4345220E9008E1A5
C45C8AD0872E626FAABA048CBF75D0082C3A706C99842A9B6B1E0ADD4A5820402C43535768650B38
0B80594224E7B531A46CC15BAF3A18E913C2C43EA15A9CB716636CDDF76BE4C8488CB8F8847080F0 |
+| | 6 | CE94A497F0BF9CBADEC3C49D4D94B076889E24B55C0583851C30787A2427044AF3B8CE94EF101D4E
2A4008557E924862E1116261C4C4D4F89A8262C757EDE1B71EC054983482618B288D698E48FD6329
C213076CE28C85B0D1EC918782C5B0083868600C9FAD0469CDE6915FB2481A4966E71B2B6838E023 |
+| | 7 | 63B60CAB008C3BD59577111A4818BB84A61C99D08A2C84CE954818DCAFE4999EAED0BDE9078234D7
92CC2F9839BE4AE418D65B0392C10D58501E4967E3445315900C2691B27D23751594BF21820D2D31
0509EE6A4222B21F0A212EC8453E8C4AE9158DD1BD4A8A9D98284A55313CA8ED508896A2A8C522D5 |
+| | 8 | A6D910704AFC9CD24324B764913B7E20DD71E4F4DAB12543658168AC14CA9095E9C8B54FD1C00A8E
1051A1CF30A363E4F8F749AC48A1828B92A6EC411925D2F1E7F1D63410C93E2DA43ACD696E6D0674
9547E387DA5BF4C0024DF044A71354CC74E7CE9B92647216ABCC16BC26EF0ECD8CB8C806BB4E3D9 |
+| | 9 | 4088C20812CEC1246ABE6AE55EA2C842C7F56E1B9E4BA6C8CEFE187C56D48637CC1A83064504478A
741674C048EB018A12BA6C5CB790EB0382ADB2E9E689ED79D3C262917D4B9DE30C5F05ECE97CDCEE
42C80CE72CF0D1DFB1CE4D9A85DDB46879CC8009DCF84D62BCC489A14D49D949852E32A6C468F154 |
+| | 10 | 24FB5A5C09ECD46F410A52349BC0C4E080F5579B29C3EA418407794AC8FE45495564F48703EDC180
D059288DC674217AD2EF00A6C6FE44A296FA485B0928CD88ACDCFCF9F9C254E23D9D1E849764A9
82DC83ACBCDDF8F2FAA074A26F48A52F27A16D2970C0BF4DCFC123CAABB6D3C66EA68C1D551BDA6A |
+| | 11 | C93DD61EA5D6D473E29B8422C8D14D8A035B692327D6492F888B42A6578B01E9061DED09237CC071
31A1F992665078CAA72C7F51C7F00EC64E28989E56E2C97902B88D226446B46A26AE4C68CC4F1A0D
1B1AD23242F9484AD0F0C1CD4C8863784138C48D6F711DDE890409D9A5ECC2001A828929D93247FF |
+| | 12 | CD0E265B8DF204AFDC655FB7CECAF603B4E0EA685E97BE4E64B85C01A414C490C565485A19EFA8F5
C10B1A31A9E841369502CB0E0D5B32D3E120ADA0EE07DD7422A5808386EC474CE750C88624090129
6A12600AD616E1463C8B3BAF6AE08C4A2B585700B028DD0C440DE4B06CA8856DAFBF1D17E5478B67 |
+| | 13 | 36F087C42AE04202FC029EA0A8098749966E394ED214846821196EEFEA23185C79A68584351BAF40
0F03B5ACED8CE7FADC884485B448900C4C1E5C79B15CE489213C66580F35CD155516FCD7845AB694
49D48040E2E8EC17C2EC8510E1AF70377E0A26E3EA354AC35F5588C386ABB6A0213082D7E7245545 |
+| | 14 | C5E241B1C1F6F78AE0192A590FC25DE1AE529BE5F554806451197AE4B65EDFC26200CD0BBCB95B70
F0A4D31F48E4B411EA390D821A1BD31428BBB50CC99B03CA194BC9E4BACCEE6A2DE614614E1C
F550D55989A18FE8E5C36AAEFDDAC6C2A50CC2898E8348175387D8FF15C2D618418826911EE07E17 |
+| 128 | 0 | 6A1E8328A92DD0BC88C805C2C69604C3DE84E19DF5AA89942E66F9FCC41A8C26B604E4D8458A576
0CEE09C8822CC068075318E1B50263DAC873E02347FBD25191D5859C285866CD8E80BD27B7604AA2
2DC6DC7F8D8953A52B00D9C896CB5CD62388FA050175EFA0BC2ED888FB9550DB0F5819F90186C6C |
+| | 1 | 5EA97D8C6A17B02A01BBE2C589943DDE2FB17E827FE400F6DF582700B244865CF8D4D20C912F380D
6494D81AD350219C1EC7A5FCF8504B81B89BCE12D845A38032682C9BC6C5585AEEE47F4A1F95B968
84C01446E2A46DC0013453FDF6300F67840231CC8D53C7A447420A28C999EF3866C12B084C0C3D45 |
+| | 2 | C63FA876D54C06CA8D1198252AA2D79AFE579FAC8E39954EAF5CE8CB1B680C49B24000C042C4C36
EFC64961BF69A09688900125B82654479A95C4704E950C9C5E4136E5AC3B31CFB4261D12D6686E2A
6C1D68C1A923C0D1610CB56EC46D78086D22448D5C08FA75C077525BC58173996904524A6CE04198 |
+| | 3 | A009CC8B8EABE248CC2E612E7F3408BEAFF1FBC3C8E7F6048A2AB9DAC3056D6A93C6ECC927A835C3
5718CC12983D4AF24FAD84989E7D5CEC29DF607CF0B68141955B107C098AE83CAACC03C0258140A9
E477D338028C96A84A9D5B00E94A45A1D0A09CED0072060DA0C0CC8206D35D880984959B1CD8827B |
+| | 4 | 8ED0C874B6109F08704C51D4788AD52A4915B3E75542BC421C882E94F3C82A6A6C9CC02E1018B41F
0A1D70B96FCA55DC66E5D04688A638C22088AE85ADDF422F1E5E101F6208056B4209A83F7499258
B05197BDA6F2A2D37B412C98860DC0DF388FA8BE1CFDD87646FCB888BA8479D296D77C4DCDB4E9809F7 |
+| | 5 | C65CA06C3386A8845C5284202B80FD53F9D56FC4A54C4A762867552906E48EED2C742C34D9262624
4DA4BD86AC5E1F1764878A675C024777D8CF3DB9AF9D75728061A47F58BBC28CC6A54E8909C495D8
97E324C96C3427CA493EB68DD5D744DFA80A9710D60FEC963EC0894AC1D736CC0F1DD7029CD569CA |
+
+| | | |
+|-----|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6 | | 5878BC84924406251337E2C101D84ACF291C08CDA72B0405FF40C2B944357D330A3A6E144028E0C02B00C63BA0310CC392AAC2626A9D80BF18540DDE00152CCAE6689814861085F54CCBBEC97753EF03A4C2558DFE7F1081C5F2B9149E4784A8F8ED5403D1D311DB0AC221E974DE792C198802D927EC98E1C |
+| 7 | | 654C6915BE1ED93C9278589710E51E0C6F26348A30A01BC69D1CC02DEFB4304AA631CA84C2235C2BCD45420C0560CDBDB4F016483361C8A1C57A396756D654BEA337EA6808CA66913CB495ECF071CCA085978CFD284A2AAC1885917A9121A8ED4658EC3A1AA6D06C28E9441C133CD50A3052C06582784EEB |
+| 8 | | 60C55B146D808554AECFB07F70AEC905B8BF094D58248CF860ACB4194920C87C0CCD07BC228ED5275BBF8AED0D7C1B8125441062B4D4F3FBC9E0EC788441F58856A9A3A040C14D65CC8C2D200FC76538472048F0B5D13E4A225D552380CA8858D304C2CC26782EA0D4307FCEA84163A4CE5418188F932C5E |
+| 9 | | 2B13B8061528965ADEA41890CB013D05CB7397F94B15A0804D40001E862841633D6E58B36B9CD443195DCB78648B2845C378AB4986FFEB6AFEE86FE63C103CDE561C852963C069625001706904726EB4CD843C6536894F9E69C855A2D88FD0F93C6D822673E45A1A1A80E14DC0D5B0192CCDA80FF89CD026 |
+| 10 | | 2F6B2858CA8C56A2836437CE778F7470C0C286295973C4CC1DEEE48A3D1C7CC948CCE5C6484BDBF2C5803AFEC5AE810065F856091588948C084001346C5478323156E684296E28CB49398D4C0432CB8B27272F5A42B8C2657B24C30D9AE088B0FC499CE05DE5BAC9ACEBD869CAA8A3F5741552BEA0FA0710 |
+| 11 | | 6FBA060A03BE2A87137F5B5510FA0490E0D8C2EE9C885A250DCF187DBA65C273308C940E1850AE317C9060AC5F11218F88C8022D26EA61AE274B80ABDE0F4C9D05C4A5CCB99A6972940E5CA60D298C5C1E0A03E48146AE0F9AF74EEB81E10905BFD0F93116860EC4D16E951F6E6184EDC8BD94A67549F3C1 |
+| 12 | | 471C41321B7A781EA0DD019A625510A9DA4062C40B58869809C6850376C3083E4E39266DC0A8E331112FB1076E0A2A7ECE985821DA78AB47D7D7BE8102A07A89CD50F0A01087B299E6872DE1AF81F1D0EE40CA8C514ED08840AA41358D86C72B90A0D4338D20B0C4BFF651ACCCA247A61E46E65848B98488 |
+| 13 | | 8DDCB00E9018344546E7CA400C406C49153D96D5618B99CF4C6C2496312481AF50580E231CA78629222A3BD7B08A1FD03CDB20889C4F00DA2AA917C7897814EAA650186C5FC7224E91D7A688A1F2946409504F35CD1895281123290499466248A68A839DD529DFDB81E85C23403D5B51EDCDA8002B5FB14E |
+| 14 | | 414AAE5011E04AC64414FCAB8D1E95034A260A46A68B6CE4738D4017B108D401314BF0882067AD38A5287430C302BC2F9258E69080FE0980777B004EA9B094BA49ACA9295DB3ED6DD413427A960CC6B666B5DF1F0350CF9A987A854424D4CCEAC5D5C8A0FDACD9E1ECA43954F9FB30CC53DB1959E7D65668 |
+| 256 | 0 | D044A6AB0F1C9ECA900C30E034CC9D959D8184E5DCFC1802C9632670AD00454532D2DF0CBADADAFCA04888F7653E1DE6D14A07743E335FC4DAA2F81D4C6AAC34AC0BC84B290B516FCA5BEF098943E94BB241505E8A58C59AAC6A8B900581EB749A6C8162D0889300ABB9520DBF3A063D2B4B85B384312BA |
+| | 1 | 80B3E7A74638FB6C82A56750986490B09810DD707010A2866C9DC0C0A4589AA1D7A1498EDF5D0A0FC84DCB61661B45D87BC2429CF2E4589445093F4A95E8C58CC7447E94AAD5EB3191134C0880E1194FB0F5B869C07E34D09900D044C86CE5F8EE9783F5E7492652091210581305B0CC0D2E1FC99E29D4D |
+| | 2 | 994D84D955E8FC9DC68C92048D8166DF29667A405AA21CADBA065CE1374463E0991144542BDF265BA2FE87476CC9CC403D28009E6D0A2C850A42AA626D51ED009F5B31710AAAB4B842F3FD98A664CE0EC121E64E8CCAD2E542E2CCE301274149FB05F8ABE3FC78654D8D44C5D44E88CC100CE0412D63F45F |
+| | 3 | 2C5ACD90BD4CF469B5AC940A80D0EB94DA8F692DAE674F8CC38C413210C30DB185DDBE819D5158A281AD8785CD88D63A479575B1453B9D38C10EC87404055D80C45182C1C54C225AA3F05D1DD746C82F4099E68ED0BE251578A07931F87E9413748DEC9A355501D47C4386D81BE9CAC39624C9511590254A |
+| | 4 | ABF8D9044BD4668241634E4482C8B9A87C9DC3D784D344024310DF08811F6C9FECC46694FB025E14F206DD80777D29D81578752E28F3CF24FA3E975AEBBF3ED0EE9C8402115CC95C024F76A9767E8BC460DAF86423888C988B3984DF0D08980BE3EE88DC52EE1CEFF2F0201E762A570B554EC24E4AAC9804 |
+| | 5 | BD8AB598AF9356E9E507887B61641A61CE52D7E890AEACF894CB8BCD924F789FED400B8540A48B82BCE1774E61D784EC5FEAB2C81BC82F4CCEEC65F0079A4E406EA44E1E0C988383C3A3866A93FD4C8A8B7C8424D69BE067E0884003E0263AB90C0ADBF8A8EC9A0F10AA73429079A4D31CB5DE0CE463FDF67 |
+| | 6 | EEEEDC95D80C8CDF39CE2FFD2C7A6A19E6068998EDA4C33023D53A8900A243C026E28B0746FAF6CE64C858EF2E0E0102865C35DC71E2A6A2998A88187872D407060D75F7A1246684157D8886982989E9811C1E1808621D867D7A3EF94ABB1AF434A81423947B142680525984A8BB079D1E92E4E490D54CFF45 |
+| | 7 | 674544848D9002DC1A287053CB96138EBDBB57F30FB731D9E1D54F9EF05A8DE688A874996D139062B6A74CD48E0A289444FE7D0100D93847C20FC491ED4486E2001E88CCED206C8E574F11281ACA56162DEC4842BAC11D2D6B17D72453C9A9A5834D06D5A2A77094F0932487645E106E9A9CF6CBFAA4EA77 |
+| | 8 | C3CEA9FAC99F2BDD54D5000C10CC46C03DE62A71918AB8D66DE719D0686805526241948C3E4F44BA84C5F1DE2E819CE9483B130846706114A5B89AE4DE3369C9652C1A4AE25000925DE2802349EABA0C53B671FA15CDEBE68C8D0D86A64E59E88A4C282C47A3110DEB435FCC6C7BAADCDCDD8155BA1A60CA |
+| | 9 | 3DB54E7AA4402CA90D875E552EF99CD92A523B6D98898748F702DE0D00C1DD9A6383E2B2591DF213DDC7A9A60B49954734B88245DF995B9299AE8B48241B245BEAAD9FDC6C26526A0A8061815611DD9510280288F8D28620484797498FFDCDCDE4B8840967C358DFB048D8051FC8D586BBAAC260DAD471145C6 |
+| | 10 | D4210A71B6C588CE83D139ACB4A3AB659121C05470E699823D6CE3838A5C585458AC1659AB8C4EA93C8DE470A8D08EA138B9C230AE4E489447FEC3064AE3F4D4D3C3214A19AB40CD8400905FF13AE3B71407A92442538E97E2A858C00B002B380294F2728F76EDBF5EC546F751242AA489116FF8246A7B95 |
+| | 11 | A99D574B117A9BA535132EB469C28172B50C036EED0F9D9D38654064D067FDB05A9EEB54655E886DC11409F94C6D615B5CA487367A2A8480ED48C9AC8D004F47C4B01BC997C10CE3C4434C25CC029E3E4EFC962A3EE6CBC20EFC4F8509E238AC167C663B8C2D0C6DF0BA7F76EBC4E05D2C408198C65C3F5 |
+| | 12 | 23E00B8501CFD6D758E51B1ED1BED045F4F1C4D3340462980C14C9E2C8428502838B5C27D685B6E6B684D1121AB2061428D3B6D167CEEE0FBD496C5C9FE8F5A4FA79C6A8D4BEDA90E8F9F7609F7AD0FC720760CE30E9C4830CABADE4C8EDB81FB8A2DE6DD54103222834D055989C96988CEC406978A6A8 |
+| | 13 | 9275CCA48B80849F30DFA3DB846549A1C700A701AA30A5DCF00F83A5F3B5926F70205105FFC41C1 |
+
+| | |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | CC78D0D109A4E08A36345C4F6A0C79FF7B8ED121DC6B41040A92792B74580CCC4DA8A2C5C48FD6EA
CF2B0B17A5A47F43A46430D612C562BAB8508C3BD74964C639ADD147316A91D3898FA6412225B4C3 |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | | |
+|-----|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 14 | B8900BE8712BF48612ED498C3CEC079540D665C1D95D2970994870402592ABBD7DBEA58188002A06
3A65E56C9CF8E8185ED2B4806B2EEA8427158F720650FA28640A393C8C5126CD51167FBD164A6E0D
8810CE4882F42DF908FBFC66AAA7F445CEDB914E20080840867C90737C169EE529035A854E15A79B |
+| 384 | 0 | 6FC11D043CA2EE8AAC696BCC440C1DC19A8D1C8BAAE89E3444EE1747A10509DBA5CD08C2516FF63A
A202D8B5E2A1BEADCF50CA2CAA56A54CD5407C7211ABCD5443BEBFEA089B44072542373B11C6803
9F9CC8C64DC898ECB40534A5834C98AD84C7412FCE87287B8CCC3F6F6EDA1D791CD470A508250279 |
+| | 1 | 4356D82DAE59E70BD63014AF5E91D9ECAFD9AA081D1E2817750BD6B6D5D2CFC00D080480A9CC110
618766D0641B98410CC552497311ACF8523AE4E94136C1C13C56C43A0354D8ED16B0064A6D1D65BD
2A4C29D9D8C806915F6FE660371C202BCC8F735970E9362A524BC3C1188DEBEA0C0ACA1881A546CB |
+| | 2 | 32C51B2C81FF8885C46086A8203A8A8796BF97F254DF2C467234E62E86ACC4F96149BC4EBC382CB2
5531186CFA341A80BE7907D808DAA38072ACB4A118727536396A40368748094E59384028F3843994
82FB8041D35123E0B814D0743638041CD8429B42A804118DA259B764336F6AFC025CE3C1B34FDBF0 |
+| | 3 | 09C344BD38CD92139C421B41C5A5B3C18B8CEFFA2ADD35395036304A0B670145A6CC758AA5EAE292
7ACC9EA9276C48271B8D3D29A81CAD510124BA4C4A82822E856B0A6DC5DB747C6AAEE97F92C129E8
53589FCC969E6C2265D1FC710FC3C5CB4EC94120AC4254FA5E434C1D5785BD74029F5865A58660CC |
+| | 4 | 871150B0CA021EF37F00AE694702483E9A073B8F05C0480456872F6101143702A02F4A031F5D88F
FE10E5CDDE0F375ADEC824462743D350D26D15D20B513C02C91148914C6459746C80EDFEA9F0663A
8F7ACCF85158BC28BF99CA5CD9719A3756F662CF4399DE84A9A52C8E77980DADD5787A282CD81AB5 |
+| | 5 | C051D44AD1858A14F6DE75BA4D1586B544B9C407847C59C13862577A4F99ECB66904943E4EE010CB
C4CB9831D547C06B4DD2861CCD5FD8407095375291523DB911C1EA622006C317FA19D287DC36B0D6
89C8DD105C05DAB54854202C8C0CEBEE8D210132050712F853441F1DC4863B24D516D6EB4B642EC |
+| | 6 | 084ECE527E41486B8BEB2A07D43DC1048DC10E0E79F4CFAD0BEFD19F6AD5F34B59EE02ECBEA02B5
88341A0E89159C5CF8C78958B995D1E58BAAE55994525F0CFA45123FCEE42BCD2B849553427A59E1
2674A48D28A4C9A4775D80156C6B99A02CA9CBE53854C732F0424B500BB746817CD384D88903004D |
+| | 7 | 0D9E4E66F4ADB1ECD516D7395C9BAADA958E0D051A86C4BED16A5D210DC624933825490496A8C92C
3802B2894FBC47208A0A22ACE2EC1A58BAA5950003882B1C0665C7600600C2967C2E9B7D464AF76A
8F605EFC1D30E72DC5927AD50B9AB55C32555D17A4B78565F578D5852069994F8B6CC62E6E01732D |
+| | 8 | 0B2229462DAB2EFA7A02DC728CA3847DCD5684DEE3E8FD2B666098C54C80A268C49B837976125812
856170220B87A5C104FBE5666CB985194AFC194D84F3695EB0481415A960806F0C583A9ACA309C01
AE7C7D608C603A4DB9A82844A7FED0E0FCD1D44876D0A09CCCB278CF79CECB84E56BB8D4EDFB8CD5B |
+| | 9 | 7E893EC40E9AAF294ED51D5A4089F8643F9A9664D8D6CE85A0D8334652DE947A29C2C5E5F3799BCEF
2490E7C953092F649B21A4A5190478D1C5E4FCADCBD0B58B5A0A120479ADD98017180BAF4B70C1C6
856068A9EFB1851657E4A7644C41B018D86A3B2A0A2DC15000E9D074A8EC95DAA28AE4D69D142651 |
+| | 10 | 00C83EA49E22CEF2C2617432C2881412DC5662AAC2E20D7EAA92542068DC54508445E1C6584D812C
08F544B9FA8E4E1CCBF7870FE8A712E52040D5C5032072BA70864CADC454C44102004C7798726FAA
11C6989093E4664F501C1951A002B59E26A5D74064C596D6E75A9C2C4490D4E3A8C087FB06F6D9E7 |
+| | 11 | 9AB5192C271160AF894BD66A82E8CF2C8E56FD967DFCBEC00024E0294DC5BE594F2F13A2EB62EA03
4706096DC0DA2F286A86CA4D4C93AA25610A43F498DA0541DE643C839784867492FA676C4380D8CC
41BA06006DC5A81E3F14D800217F8546914D2E7D67860131550807B4AEC550B45A8AC43E04DDFAD8 |
+| | 12 | 5D7C8C8401EC80E085C20278DCC82274409816447951F9633350648E60B892BD544A2023A79B81D0
15E816F3EC492523158285CD7146480E48E5F46C10E8A11F36131C5DCA42D823C088FC600E5FFA7C
D00E04CFD789953C6B45BC1EE58CE99B8EDC0BE95145C0C59294D5F50E34ACB17F47A2BBD144D9DF |
+| | 13 | 8269EF0305623CD2CC821CE0BF62F0CE623B2CBF9C128A6688CC41E8A4C1B5104D838891ECE47310
A9A65D47442A50B4B30C3966268A416F9282D6D84A07572DA675C7DA920B0E553B4C9E889840DA89
170C6750F5C06EA808A084FC324624FE1C14691D6590C8C92041B5B721126B6EFE439E48A6E4866F |
+| | 14 | 15A1CFCC0521A6C215C64A614BEC6AB6BA045FA73D04567B9C10087A245A22C50CAC7D82B70A1F
C1A6776860921B34A49924102CC4446ECB82D40B4D7B818E7FC08A6EA18E4DEF86B69689FDF5520
16DDF41B6440DB86BCD0A84A64049E306B5F91D5DBC70ED954029F986369DED22CD0C3470E88E |
+| 512 | 0 | A6947FC6947CD99887AB40E8AD774B46D83460455CBC1C436FDBB2B40F07857EAF0C404AC808E3B7
F8A2DAFE8351E8EC00B981124E42F251F80C68578F5D9081EFD88460F05473220B53E99279A2782F
48D4B8F799F861D2CB38A24993B1C0E710C0C09C4364110514FBC3E182925458CEB1E08630060834 |
+| | 1 | 36128D8F37226E79801042EBC4C1298822846E63425B8711D53140341823B4CDB864800484270C5E
4B04E92D63B135919F9D302D047294A4DFE55984890D7DCF6F8376D727C001542A7F077C6BB829C0
60057B456B1867FCA98DEE94F5E5C4B0C895C4ECB08763DB0B7DD5A0E58CA8D93DEFD6601D10D9BC |
+| | 2 | 97C1501D8FA00E2076149253FB3868876809EE49DF4D84AC77F4BAC6A1C48D2E246A1540F8C5B795
ACE0A47C1EF42504C0CFDE218E4D370289550C8AEA6F58E6C445C3C8462A4C6729CF83B2E048CE5C
756038C19478B0429B6C91B3CD0857ED42B3694658B3195C809C141CBA86BEE76DAD731EC16890E01 |
+| | 3 | 89F88DAAE1BC3D0B4ACC34FAC79096B6615A2085F60B0C2511DE676A0F6EC080AF446C45C390A2EC
0A2106E48E88C0257E565284D298C4298B9CDD6EF400EE8D1325D0962BD991512F0799FAF2DFDB02
260CA0E7E54DFA29A4956BD480ACDE9930341ED66B17EAFACE485ADDD160A7C830A15D8FF0D09C20 |
+| | 4 | 1E946C4D2694B885FC254FB6546B2C4AF5987994F51AC90827E08798E0C0D5750FDD8CAB9F58A895
448BF01E4BC8CE37477291C425D52E3E41D526888CBC3225664D649106EB907AF8F4C96B3704B887
041119AD0C5A8FBACFC457F3AFC74D12E7C9ECB5E5304B48206A421122EAC2287C499D8C2C455D40 |
+| | 5 | B00870C4D8804598D27D8EE6194E1CFE276B65D82B737C3E2AC399829FA17CD1E52CA77E172B86F15
18904129A62589E694D0D4E988089EFD8A8414808F58E5D9FD8B84DB89C35D4D0DE51B24DCDA8AAA
D3616BB57CA3D30826F2015C35976EA8CDF614CA5AE45C8E68062605A07460C9252438F969905526 |
+| | 6 | 1DCB60F29CC421E385F9F5715B67C11C053064C824B3C471C026DECAC799861FEE000D54C4CCE68B |
+
+| | |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 4E9ACD08C8522E5407600F8F7DA30D4CC8A104CE023BEF8AFCD28C34CF607422AE6FC4CBEF6D9B54
2DC7ABD8B4A5E8884232AB0180DBE049EA42AB968D805162798F67DFCA1DCCA5055620C86D7236C6 |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | | |
+|-----|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 7 | 988678E7C0C19CFCC345B71BECC27DF0624C5B4F024786DE864860E19F121DC9D529444581A92710
67F280EC1A8E4E4AC623069C3F14808FB402DF516CAFECC3A4FFDE5D478D5CE8C3AEFE59024C2CE22
10ACD2D48D60E9073526278D2DD88BEB4154386C37E81C1661ABCE24A47E73C81C9C5C1065352FD4 |
+| | 8 | C156599A4E4F06B2990C9FEEA46D8884D110019DBD470E7FF4C9CC38D610ADCEF94A4E14199BF9E9
1E96C44C2F01316BB6CFE6E33264D5C0EB408B54CEA6D7EC45F6E84B0CED84F7A0F064201C5DC406
B4CCD8862FA907AB04FF72588B6B92A08B4300175C9489F28691C8A5BBC08A186FBEB6A501767805 |
+| | 9 | 1865FAB7D45A3E60D484CC9EDAB1CA690144E1CC26D0B39A2432C50EB00162D6FFC01DE80A1D8826
DFC0209A0E90BA6828C5D62590414FCB6ACF50A7902484055708662D3F024EC0E8E89A1C6605BB6E
5ED888B8AF447029BD3F0267F6ACFC2E00567995C3016CD01D909A6971ADC6A2A360774840FC32D9 |
+| | 10 | AC4815F7471DD1C96AF1CB089465C6ECE675CCCC410EA64AD3DE0B66E75C909178E079E8A672E2E5
D47BA1C3CCB2CC8118F208EC3373380C15047801045CDC6E4D9E14032A243EA3269E24004512E328
2823F4F064A0BEAA8D43DCFE2C49449E5541BE52BEE63C8857FB2694C0A2DC9A568CA4519CCD48F1 |
+| | 11 | A2BBD1D1D4450CCD20779B04E41A644D924C4048F6AE3C851CE2CC5E947B8583A921B06DCF4E6F31
CCCB1E5E800D0EC2411A449C6E1F981E17A8B0C08AA5470E9E520169DADC9239CDAE1C42058DFB6BA
0EA13AE7782F667C69C6ACCB20D6FC60C8239726E215158946BD951C4E0640E685C5E7C5C9A8B804 |
+| | 12 | 57DCB22ECE4C2182C6CABF2E8BA04011929C4761CB725C0D044448C0A6CBB48994A2920E789006B9
78D2E0E2C08094CAA88D532D9CACCCA711BDF8942325BD64F706D82EF8D2D0B85EE2B08D98EB2F4C
41C929301298AAE829608C8A3220CEA607946E9B7CDADFBCC5684ACCB0A20E3845224C3C491B1E5 |
+| | 13 | 878F97E1620BD906CD79D015D0D2A53EE4124E845AD4852028690366812E8AD5FAB1056E48F0970D
CCE62A55AF13C2EAEFD936268469B0286D42E0C03F240E42653CB8130104F2486962CC2047229E6
80157DE209710C1DE6944E4E5E4168AD4D309DF41BA46FCD8DA85921C9EDBBC75D7920F0BB36B6C8 |
+| | 14 | CD1869AE1100EC1E8680C64AC48489843C69E045301598608D4D899CC9D9F1C23CD84B3C3205D90F
CD2C38C93E299148BD9B0B5ED1789ED478A0093C1E846DE7D8E8659055EB5CBFE884BDB95DD04E0C
A28DD51E580CAC3473A8C087907602BA9A627CC966D5E3801553D986E2842C10E2C9E6ADFEA60645 |
+| 640 | 0 | 138D98B4815C8984B7DC08B87C868127445149E316DBB49C1C9F4B226E0A02385A5CD2A895F97CDD
801FE39DD4EAE41CCA8CF6FD693C7300E8E641094808A5A6007ACF62CB91A3C87D571F0094424EF5
E12E7EC5417B9825CDBEF6D9E59F654953DC8C988008CEA2706FD4E797AF0508088A2828F10B1D2D |
+| | 1 | E158EBAD648F1D4C89883C537A89DFF151E344C8AC521AC0F48971508627D1C5A546B16F134CF4CA
BEACA EA628E4F845DA66D45C14983F90100F94FF9400507A8D6239405EB186A504653D2AED633CD9
72049290CFB9E81C54E04828A9C0DC9998C6950C1BD9D70D85375D115049F2231AA7C1F592CB4A7D |
+| | 2 | 2020F33A1F67956340CC43E28A18418A6B0ED400EC0EE9B3C94689DEFE632204EC51A80C5FC9F089
8455BA6D54949B67A5D0704A7988723007E088C1C3E104D42F28687400EC2D2BCEA9C359C61CFDC8
4B185DAAC7BD8FF7A544EDABDFD640A7D72BADE148E481002EBE64568D7D70C2678E37EA1685D6B0 |
+| | 3 | 871CACD6880544988157EAA226AD8D020C75CD109222C8CE55C894248E8C6D8F68249D63F1CA3CB9
5541BD1F88B52CA2D5C62681C4260161B544A569AEC0CCEAD52E14B7CB06607CE415194DD2377DCB
0375005DCB1639D983C67150534E94DCE0099C4CE6C17430A68108C1D1BC4596DB774D797E12ADEC |
+| | 4 | C5BA82C4171A25CAAF1D53C5480D8C500E8588258090F38155BD0D9401F45E2700C99C4808776EE0
284B58F4345DBB851782FD0F4E891C3D4C5CB9A98D595866152E88C3148C94068B61863603C224E2
084020C0F6E78D1500A8323741217AF7808D7E85975BC3461DA398C70D55590E32F6E6403A5C8A8C |
+| | 5 | 13CAE785764E1AD020828D0119416C58DC8C6BCBE3B8B664CB2E4D80EBFC46CCCFE27CC10D4A25C
557543509C7D8BACAC5BC4AACF51645CB8C408B820C015666C3B14A3149B2884620840C926D90B56
0A307884C63CA66B582919A8A18A39071B89770C5C44E20C39AA30CD68C11D4FBAD87E9A026AB421 |
+| | 6 | 064202ACE41AD49CA9D068826CC22D13F055A83D18BB52D9B0A056252450140CFB1E89C70BC9B4D1
EC05D9723C448399171FA4A4558C420A60001C70A9CB355B0794E580562A50C024680BA7B3F02BB0
98AD1CE1114022723DCE739CBA16DE70C04725AAE9EE4C671C586DF064A5CA295C8E66C4EC86D9D6 |
+| | 7 | 21B78C8061BB57C01FE591F46223220A9E062D422589987082CEAB141BFF921D4B21C8C90E7E0A80
20B9E3C9026D12590C42197287948F22D3FD977BAD2B90B74DEB6C098647AE55002D953E48C434EE
C78E4D5547838014EB8066644C209A4E4A1229FC121DF6CAB62B14AF9888E376B1D3DD1D3506832 |
+| | 8 | 4A0E3441EC8A5AD6D5C1D21DC4890C06E39E018039A7C56E81291DA4805D096DD1C16064959910E8
5ECEEA5713B07F41502328006178ACBA0FDBCBC6B457A786EAA50E1A87A4A84C5C8DA06A8B4747D7
264997C84F0FD440DBA49EFD3D4AA8A8AE67DB122700A2D805DCA170856C5273FD3C8C82DB05A192 |
+| | 9 | B1523862484C051A901F2A80FD1CDEE46483649324090D944CDC65E8E37BF50C249E399C829A4CB
3358A8AA5CEE1C2A66AEA1CF3007885E12E73CC5D7599801D600A749666321E39BF0CBCA77581B93
89C725322799B7E4155CCE85C484D0D5EE426D5005C4E10C25A81DCE699EFDCA1EFC61FC1FA813A5 |
+| | 10 | 0439C8F3B954205BF68C434E9480E4473441E16D83CCF12EA54179BC7E14FBFA4137AC232D2D57B2E
807CBAE831A4A1E1A1DA1003E0DA48A256E760A3E60F00406C21F85DE87E9D914E6590D809166A4
1742E7ADCA8E48D7CEBC9643497DB20A426A5591840F5089458430346444E5AA904460298824C144 |
+| | 11 | B469FC749052A6838980075486A7533B9914550CD2A8BC78BCED04478C6BDD5864DE1ECC826C4D45
42AC1D7AFE1864ED85CDEC6FBA2D4C9B8FE42F601DA00F86AC4F5BA88280A9A52072D95B2A7103AD
9C8E5BDE0AE91498A6ECC8B08C825B42DD8DE4D7AC1D30BA295B2DAAFD024BB04A54C212309CA3CE |
+| | 12 | 68A5B8D8DDFC53E64D4C9D4A45A6C88A9B314A2E66F214187D7A98DD9931463BD2BC0B58DCA01688
5779FA4E61E421151028B74C8D583DDB698818142BE6E130A74D875C0E415C8DE484CE81854C2440
CA36C879F2A9949241C06EE51759BF6D882FFEC19A4F022D6485AE129E8C4665DDEE8857206B28EF |
+| | 13 | C748FC01802B268F11044E28658E35B74845A9C35FA5029673EBACAD8F838F664857F9ABF888EC0
180DB550E6F27E60E5B4AFEC6D7C34E0A12052D7F008EC9422A2E8012E97063B80D24648D3AEAD42
D0F8E392BA037894A805DA01E887F8DE1ACCAA98B5C2AEDAC1C5D8202509D8E9FD16CA499080607 |
+| | 14 | 5C02AE4063C16081D918F0A5249B7A64C5EAB1D6A77CE405447E2C1C121F919C0D3B073082129A85 |
+
+| | | |
+|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | 7E4A7091B0006CF059C2682980468EFE09B56A8DCE6BC5D880046CC62288A590C9AC0A08CC5DAE52
09C24AEC94759DC9A2E05C79C0ED09F05B2BD660C91E054BEBB5294F09D93DE85AC60A99ED6E1845 |
+|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+**Error:**
+
+173
+
+**Error: Reference source not**
+
+| | | |
+|-----|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 768 | 0 | 15E21E6B24200F1FFA8985625F766D026C46898996945FC504D8499C468728735C756CBD6A92155BBD6CFA674CBC9D0B090A9ECDE54587ACB0688F9666C0686EB217BEA2754AA65EA264C9198199E2644B02CAADEC1D45DC892774385A904F643C66EC14BAE65C3267F0B2413C22A921C6804F85026014C1 |
+| | 1 | C50F328B4C5C48022A8E0CE14393A8456D8EE9DA6DE5A36223B41D9C0ABA3B4820D92D29369CC90D77866629041BCED58A2AEC947C8815781E94C49639CE44DD125887A49321CC1ECF841D55880B7FD508854192A444D9FC042E45C19FA92B6FB94EA5B8CB521BE1E06BE2CDDD0048DE095FE0EA26CB5434 |
+| | 2 | B77D70563885A1E0E502B45E9847643BB0C22B44B4050F5CB47ADD09C2072E60F8E1ACE002F65A6ACDE91B545D6C7E685D02F29216D84B248C6C9D47DA8B7ABB09F08CA601B0C51C64CE8DD9C3A8304066A825E685E9A15F4C3BE47B1385AA8A8F8916FDDADD94B22108DA69774C6608D9246A9C61436C2 |
+| | 3 | 20046C0E3801B9CEA71B0DCB5CADC5C51ABC028D114C036CA5D06FB44A428F36CDAD37A4CB548759864B94712C2043F51D84E740B8DFE64E158018A41A17D0F5CD3FCC41CF0B44D16880F51C81680045214998AA2D2A5B02F914C696A7D6E49300C7A70CA788200D5AC8F82B59C4625E91002FAD8605DC58 |
+| | 4 | 1F169F9838CD517840B079EDEE61F3CDD2751B3409492D7B2DCCB625CC18744E59FC42C838FE40F61A963C616A087DEB046FE80095BCBC28A06C44AECEC504016940924EF6AE1AF545B6180E9C4DBF8499EC85F857C6958CD8C4D5E7F710240BABCEEF22565524CABD1FE6367E9EE50FE6F087CCB9C69F5615 |
+| | 5 | 6346FC9AEE28C0048951272E3A64960D4A1510DC1BD9715F6ECC7C3B88EFAF1D915819491A935A676940CDCE1C34EDC5E5284B8797B5016D18DF8D7C0FC80504A4F63AA51EA5389880B99548C4A04455954C245D1C649AF8B133C108601C09431D0FD63E7E41FD0F3116BDCE16CD77B62BE9D85EFB959266 |
+| | 6 | 9728C4C4DC66F2709EE622543B509EB6302006F0EEF939B5CD09268FBF0300A380842677F0609609D582B8B052A8D4DA9601399284A43C4874A5059104292489FD1F78AD52120F152C69F0A1459D709B537050E421CCD096309CAE0E8E8C6752AA10589A2281487ED001D9D111006D955D841C5A1C6D201F |
+| | 7 | E9A00C8880DF2784030486E650254748640AD06C0ECD914F0A73AB904CB8085074070021024FC612896272B5068BA10EA50E2B66909CDC5BC3AB7920567019EDD44C7B119B8E404D08B0DACA34561E7FE85A251CE166E4C259F1848866F9A7F4DA644C7C4C2A85341465924BD705214F5A8509A7E5003428 |
+| | 8 | B21CA5DB7DCDEF97D50219CAE77EC242AA58DC4378E11874A50D0FCA45805366C82927F51CA428091C404D4821FCCDE34052463089FB320F541181E698D64C2F1D5AE7DA8A9B9D4716902815545FC8452E72A869E8ABACA4E812BBDFC80AC1B4DEAB64AAA1803B392501068E6418A8F418A7C8AA29C84C8C |
+| | 9 | 02F0AD8E99A24D3CD4C02B3CFCB0D5349EAD59114B05752129002406633AF9A069F69D6032C10D9E4C424D16B016FA58D6CB40804E90601CA4595FC0BBDD87C8FB7C0BB4C21C841155D46938A888CF98F12650E61C6EC4C1FACFB542D6E5CCF3096A402DEF5AA31E133CCF15C9A45B0CAA485250E041C461 |
+| | 10 | 6189B50C25863E82FC3D5A843CE8F4D84D4373C2CA5C8BC0C0A389ABB478CD52DF9C4EB448481DC0D4150643A2DA896F51742A82BA0986F1662914B2926593A1510E077026C51F8A7F88DEEEED4F16B3E50E8630AE03FA570AC753D18551D2D9C64005A2954D604DAD9D798E4A589760076A3D41921603B9 |
+| | 11 | 8049797BDA828C0012FAAA3266E044397F57E538CE3C0C174248D00E2D89FBA46884A549684D1E24C8AAB885A1176797446874282042880A62534D840EFA909C86EC4C6BCEB48DE1BF80B3AED94C71AF94D6C750E402DB698744787B0A6CB4A664690C07CFAF56A4B6DC7BE55407B6C52AB19CD559483F7E |
+| | 12 | 40591C4191A1E8E0B853A463A7D805940800F389ABD07003599D4092041CD4C93D10CCA3E4C6EF1A1784AB914E8CB729DE6BFF0847A1DCE6C8C046D317D29495316AED1B6FB1891CA890C818D6CE0283B2043D4E02ACD68A74EB66ADA9F941A99D525AC04F9CEA086F578D1A6C5B8B30985A187E8CC7DC |
+| | 13 | 504E99F104FF9FE0C9A78CF29682C49B0E2E74FB2E20EC419DA401208F6C993D03E8148A3297A485C4E18A2D3A9CA7ACF940F7DA50DA3474FAE9BB5B35AA7CC2C17F652E728200799B7EEA89C4B04E56DDA5DC588F89CEC1E280CD48000B13165D9AF495EE672829C5ADC42CAE6901A4F910A4DC406CFE61 |
+| | 14 | 15C15542F044CC049F0E6550AE45EFA5DBD76D5298C34AE8D6CCC62440DA4543CA78058186A06C53F4C74BCE7B4AC9F12E2D4DB884A6EE6E6CE79996035A2964E40A22F1F6CE3BB19F841279354B228C5C1C95CD29A13884102378E180B5A489B064FD0050875ED44849108FA1A09218DF61A21A8FCB6B6A |
+| 896 | 0 | 400A0A000B9A5DA2C21814C6FE024101E699344E89C46C773CEE08D14D5E225A94C5AECC6C120060B152FD950CDBA552F2A85CE418D2CAA864D827503F49C2E2EDF02243A088E5A187E5968019E45D57FC96845C39057BC419B3B69BB6970F8FD4E035DA0C914BD4E4C5A280FAC030800F14ADA8CEA |
+| | 1 | 4455C04B07B8A84F81A05237092273284397638305F91971C9E867A0C86341AA5219F4DE9EB420D9ECE4D4E2C2CCD5BCC2CE155591D2EE949D2B3149D411C1C7A145E439875A7E3F8704C53E4C098284CC86FD4151C768EF771F840C4C477E019FC249436C267118646D4A07468864DEA4CA781825C505B |
+| | 2 | 41A9C458FAEC095BE34D11978C96344F340205907066B8ABFC6EB6F53719583F96D0861C774129A84BC4F94C5EC2C1C44EA5908FB4DF46456992425E119C86E0A467EE436008DB4657B6D68892FD3886548DF6781740991D7828A5B39452ACD101CCA411C4410AA0E880D38C0CD8A37C6B6D6477CC20B9ED |
+| | 3 | 0C0660753C1A2C8DE6CEC2AC4C03F541CBA8CF27078D5E582BD62E3B87DD0C624543534410437383809E0C066F1A2C676C352BFC7D35EC6E86CBF3E1CB0572E2D293B60A5C5334DE4790BB6C7C43EB841839C0CABD205B060185069D842AD5CB9226659EACA8FFD5C16D2908678CDA4EBEED04C4D35C9E7821 |
+| | 4 | 65CD384F2B9666D909DF68CDD637C33C1696F5E819784A8A2AD6CD9823EE1E40DE62CD1272440E5A524A2603CC24EE6498CCFA1C919F870458140D851A0CD0E571196974BDC30ED8918CAAEC12446ACA CE0F4F080A6C9887D96703CD88C7E49AC3648D7F0BC72B7DC9B1A1D4B1CAF3A46943A680F849ED9A |
+| | 5 | E52994D6BDC01558000D3F22E416BB651A5E194EEE823A4C05793E665C5A6BA77960FC1081B6355A BA480753A0EE860434D01AC81DE4092403D05E12B0468A65A800C8244797C814A52326415FBE568 IBA286727FF095384C288DEAD496C4E41E99C62DA8B62102D420184487A48043E97B81C053041C72 |
+| | 6 | 28ACC0A9E893A55F1CBBCA24BDB83295E813168BEE80AA22148CD06F0F608B8AEF2E4C424004EEA5 B000E8C90CDBD46ACC5385110D1E470F8F66E6012706C025292C8D1F302955D2E1B64AC11B65AC0F 9124D981E19DC8129B6C2928687541187FDBAF6F5B7FA9544F523464FB138A54488970EB455C0D5 |
+| | 7 | BDBB40572F15AA8050CD6F44E23D8A1A9D9157A909716E41BBFD6C0E884E10E58A4E27FCCC45091 |
+
+| | | |
+|--|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | E689CC84D458D14B12FAF47CC4C0CA9DCA15873FD4FEC05AD00989BC06E24F6D4F82400EAF0B43C5
E285E2CF365E63448D42B0E20F89F461807055CCAADFDA123374CDC3B364F858064CD30C67710330 |
+| | 8 | A1CDC0AC064A07BDE5F496CCAF3A3C91A98CFE182DD0C54F9ECCE25E981D129A8A23B630E8C78E0DA
58742533BB3D2A2FEEC1C139AC9DD60CE2083846F4B0C303E9E5999DB105E7E9C6F35326BE895580
4BC4AE86C4155D02966887724BCD8FC0E44DC118546BA6AF2F82EA4EE80447A418B8CE492CF49ECA |
+| | 9 | EC1C57AADEC8FBB0B4140BC8C1D38DAC1416C48D5B482C839C469803288B6454FA8718D80FE92AF
81BDE6EE147C5EBEDD8730D582C141C001730D43021360E25DC1769AEEDABD44F4E6F75CDC9018
74A2E6C88B460A49501CD946E5FE0725EC9C68F6DFAB1D74CD55CE3C909E9065863022100A8C2F03 |
+| | 10 | 1CCD864CA6FDC0FD6AA18EE7B48A1F6B214645141D07AF691CD58C8F82DA596FC931023DBF026C0E
0282A1798C069848668CE08E82902E72BD6D46A381D8AA922DDA785A6858D85CCCF8F28FB8CDEF98
9B04606D9B08B8ACDD09CD5545EA4DDA4E548E5B587D1E894D50725E0968C0F949EEA3D5DBEC826D |
+| | 11 | 9BD4603A5C0BAA644862019295B6F09CC05CAAEE86306DF955307116D1852005A98C8EFE844ED14C4
A49DC462F596130E492C7DCCC47D64FC0045EAFFD1E01CEAAF6C38255CB7ECB4446174CACA116ED8
5A7050B48ED5B178B8F2A722544C90720DC9961E0AD6B868AE9DB5E045C6CA35DEEEE08B9E6E58D |
+| | 12 | C0A81E46262DE865209B11883FC6ECD70E049C8341EABAC7D8B8E615C2027A820887866E12B86F2A
FA70A8BD50A049203A1D7188006422598E461C27749329C00090916AFD453874AD4EAC9150B8C4AD
C5E25FD38AE19C8CA6A4CA1244BD37383AB8BE81181944579F93C3D3CB7E04C7977CC0600CBC6FFD |
+| | 13 | 7124526DAED23B9E828FDD9B9E8B3D4C214E87148BE9DF3AE1890EEACB11569EAC09E5955A160CCE
A0A9EAD06B3C96B5A395A6B32A8CF1F1EED05ADB4EDDCF49882B202D1CD4BA67E248730D2280CC27
02D100406641C0E6B7F0910566C1AD0461A807CFE1BAE09EEE4660B55A4EEBC4EE122B0ECE694E8D |
+| | 14 | C3AE1C4C5C0BF009AA4D4171F41786A49CC55A01C5C5CD9A56F342E9B870650E88A1A48D0AD96F66
8448A9210D83A655448F7AA2024D1DBCDB49ACC485C3EBCDD7494D5406D590FE5B74ED031C076588
168BC607880040641BB6D65E0F5FDA160C32C671639FA86DE4E36A1D7454B40C900A93DEE3B4E10F |
+
+# --- Annex D (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 14/01/00 | RAN_05 | RP-99591 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 |
+| 14/01/00 | RAN_06 | RP-99691 | 001 | 02 | Primary and Secondary CCPCH in TDD | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99691 | 002 | 02 | Removal of Superframe for TDD | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99691 | 006 | - | Corrections to TS25.221 | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99691 | 007 | 1 | Clarifications for Spreading in UTRA TDD | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99691 | 008 | - | Transmission of TFCI bits for TDD | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99691 | 009 | - | Midamble Allocation in UTRA TDD | 3.0.0 | 3.1.0 |
+| 14/01/00 | RAN_06 | RP-99690 | 010 | - | Introduction of the timeslot formats to the TDD specifications | 3.0.0 | 3.1.0 |
+| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 |
+| 31/03/00 | RAN_07 | RP-000067 | 003 | 2 | Cycling of cell parameters | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 011 | - | Correction of Midamble Definition for TDD | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 012 | - | Introduction of the timeslot formats for RACH to the TDD specifications | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 013 | - | Paging Indicator Channel reference power | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 014 | 1 | Removal of Synchronisation Case 3 in TDD | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 015 | 1 | Signal Point Constellation | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 016 | - | Association between Midambles and Channelisation Codes | 3.1.1 | 3.2.0 |
+| 31/03/00 | RAN_07 | RP-000067 | 017 | - | Removal of ODMA from the TDD specifications | 3.1.1 | 3.2.0 |
+| 26/06/00 | RAN_08 | RP-000271 | 018 | 1 | Removal of the reference to ODMA | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000271 | 019 | - | Editorial changes in transport channels section | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000271 | 020 | 1 | TPC transmission for TDD | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000271 | 021 | - | Editorial modification of 25.221 | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000271 | 023 | - | Clarifications on TxDiversity for UTRA TDD | 3.2.0 | 3.3.0 |
+| 26/06/00 | RAN_08 | RP-000271 | 024 | - | Clarifications on PCH and PICH in UTRA TDD | 3.2.0 | 3.3.0 |
+| 23/09/00 | RAN_09 | RP-000344 | 022 | 1 | Correction to midamble generation in UTRA TDD | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000344 | 026 | 2 | Some corrections for TS25.221 | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000344 | 028 | - | Terminology regarding the beacon function | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000344 | 030 | 1 | TDD Access Bursts for HOV | 3.3.0 | 3.4.0 |
+| 23/09/00 | RAN_09 | RP-000344 | 031 | 1 | Number of codes signalling for the DL common midamble case | 3.3.0 | 3.4.0 |
+| 15/12/00 | RAN_10 | RP-000542 | 034 | - | Correction on TFCI & TPC Transmission | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000542 | 035 | 1 | Clarifications on Midamble Associations | 3.4.0 | 3.5.0 |
+| 15/12/00 | RAN_10 | RP-000542 | 036 | - | Clarification on PICH power setting | 3.4.0 | 3.5.0 |
+| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 033 | 2 | Correction to SCH section | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 037 | 1 | Bit Scrambling for TDD | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 039 | 1 | Corrections of PUSCH and PDSCH | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 040 | - | Alteration of SCH offsets to avoid overlapping Midamble | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 041 | - | Clarifications & Corrections for TS25.221 | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 045 | 1 | Corrections on the PRACH and clarifications on the midamble generation and the behaviour in case of an invalid TFI combination on the DCHs | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 046 | - | Clarification of TFCI transmission | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010062 | 048 | - | Corrections to Table 5.1b "Timeslot formats for the Uplink" | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010073 | 042 | 2 | Introduction of the Physical Node B Synchronization Channel | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010071 | 043 | 1 | Inclusion of 1.28Mcps TDD in TS 25.221 | 3.5.0 | 4.0.0 |
+| 16/03/01 | RAN_11 | RP-010072 | 044 | - | Correction of beacon characteristics due to IPDLs | 3.5.0 | 4.0.0 |
+| 15/06/01 | RAN_12 | RP-010336 | 051 | - | Clarification of Midamble Usage in TS25.221 | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010336 | 053 | - | Addition to the abbreviation list, correction of references to tables and figures | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010342 | 049 | - | Correction of spelling in definition of beacon characteristics | 4.0.0 | 4.1.0 |
+| 15/06/01 | RAN_12 | RP-010342 | 055 | - | Correction of Note for PDSCH signalling methods | 4.0.0 | 4.1.0 |
+| 21/09/01 | RAN_13 | RP-010522 | 057 | - | TFCI Terminology | 4.1.0 | 4.2.0 |
+| 21/09/01 | RAN_13 | RP-010522 | 063 | - | Clarification of notations in TS25.221 and TS25.223 | 4.1.0 | 4.2.0 |
+| 21/09/01 | RAN_13 | RP-010522 | 062 | - | Addition and correction of the reference | 4.1.0 | 4.2.0 |
+| 21/09/01 | RAN_13 | RP-010528 | 058 | 1 | Corrections for TS 25.221 | 4.1.0 | 4.2.0 |
+| 14/12/01 | RAN_14 | RP-010741 | 065 | 1 | Transmit Diversity for P-CCPCH and PICH | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010741 | 067 | - | Clarification of midamble transmit power in TS25.221 | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010746 | 059 | - | Bit Scrambling for 1.28 Mcps TDD | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010746 | 068 | - | Transmit Diversity for P-CCPCH and PICH | 4.2.0 | 4.3.0 |
+| 14/12/01 | RAN_14 | RP-010746 | 069 | - | Corrections of reference numbers in TS 25.221 | 4.2.0 | 4.3.0 |
+| 08/03/02 | RAN_15 | RP-020049 | 071 | 2 | Clarification of spreading for UL physical channels | 4.3.0 | 4.4.0 |
+| 08/03/02 | RAN_15 | RP-020049 | 073 | 1 | Common midamble allocation for beacon time slot | 4.3.0 | 4.4.0 |
+| 08/03/02 | RAN_15 | RP-020049 | 075 | 3 | Correction to a transmission of paging indicators bits | 4.3.0 | 4.4.0 |
+| 08/03/02 | RAN_15 | RP-020058 | 076 | 1 | CR to include HSDPA in TS25.221 | 4.3.0 | 5.0.0 |
+| 07/06/02 | RAN_16 | RP-020434 | 080 | 2 | Clarification of shared channel functionality for TDD | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020313 | 082 | - | Clarification of shared channel functionality for TDD | 5.0.0 | 5.1.0 |
+| 07/06/02 | RAN_16 | RP-020317 | 081 | - | TxDiversity for HSDPA in TDD | 5.0.0 | 5.1.0 |
+| 19/09/02 | RAN_17 | RP-020559 | 092 | 1 | Corrections to channelisation code mapping for 1.28 Mcps TDD | 5.1.0 | 5.2.0 |
+| 19/09/02 | RAN_17 | RP-020576 | 094 | - | Correction to S-CCPCH description for 1.28 Mcps TDD | 5.1.0 | 5.2.0 |
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|------|-----|----------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 19/09/02 | RAN_17 | RP-020579 | 104 | 2 | Corrections to transmit diversity mode for TDD beacon-function physical channels | 5.1.0 | 5.2.0 |
+| 19/09/02 | RAN_17 | RP-020569 | 090 | 1 | Corrections to channelisation code mappings for 3.84 Mcps TDD | 5.1.0 | 5.2.0 |
+| 19/09/02 | RAN_17 | RP-020572 | 097 | 2 | Corrections to transmit diversity mode for TDD beacon-function physical channels | 5.1.0 | 5.2.0 |
+| 21/12/02 | RAN_18 | RP-020848 | 105 | - | Correction of the number of transport channels in clause 4.1 | 5.2.0 | 5.3.0 |
+| 21/12/02 | RAN_18 | RP-020852 | 107 | - | Editorial modification to the section numberings | 5.2.0 | 5.3.0 |
+| 26/03/03 | RAN_19 | RP-030138 | 109 | 3 | Clarification of number of midamble shifts in different time slots | 5.3.0 | 5.4.0 |
+| 26/03/03 | RAN_19 | RP-030138 | 110 | 1 | Correction to applicable HS-SICH burst types and timeslot formats | 5.3.0 | 5.4.0 |
+| 26/03/03 | RAN_19 | RP-030138 | 111 | - | Correction to HS-SCCH minimum timing requirement for UTRA TDD (3.84 Mcps Option) | 5.3.0 | 5.4.0 |
+| 26/03/03 | RAN_19 | RP-030138 | 112 | 3 | Miscellaneous Corrections | 5.3.0 | 5.4.0 |
+| 26/03/03 | RAN_19 | RP-030138 | 113 | - | HSDPA timing requirements | 5.3.0 | 5.4.0 |
+| 24/06/03 | RAN_20 | RP-030275 | 114 | 1 | Corrections to field coding of TPC for support of HS-SICH (3.84Mcps TDD) | 5.4.0 | 5.5.0 |
+| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.5.0 | 6.0.0 |
+| 09/06/04 | RAN_24 | RP-040235 | 116 | 2 | Addition of TSTD for S-CCPCH in 3.84Mcps TDD | 6.0.0 | 6.1.0 |
+| 13/12/04 | RAN_26 | RP-040451 | 117 | - | Introduction of MICH | 6.1.0 | 6.2.0 |
+| 14/03/05 | RAN_27 | RP-050089 | 118 | - | Release 6 HS-DSCH operation without a DL DPCH for 3.84Mcps TDD | 6.2.0 | 6.3.0 |
+| 16/06/05 | RAN_28 | RP-050240 | 124 | 1 | Correction to transmission of SS for 1.28Mcps TDD | 6.3.0 | 6.4.0 |
+| 16/06/05 | RAN_28 | RP-050255 | 127 | 1 | Correction to the examples of the association of UL SS commands to UL uplink time slots | 6.3.0 | 6.4.0 |
+| 16/06/05 | RAN_28 | RP-050239 | 130 | 1 | Correction to transmission of TPC for 1.28Mcps TDD | 6.3.0 | 6.4.0 |
+| 16/06/05 | RAN_28 | RP-050255 | 133 | 1 | Correction to the examples of the association of UL TPC commands to UL uplink time slot and CCTrCH pairs | 6.3.0 | 6.4.0 |
+| 29/06/05 | - | - | - | - | Editorial revision to the incorrect implementation of CR127r1 and CR133r1 | 6.4.0 | 6.4.1 |
+| 26/09/05 | RAN_29 | RP-050448 | 0134 | - | Change of burst type to burst format | 6.4.1 | 6.5.0 |
+| 20/03/06 | RAN_31 | RP-060078 | 0135 | - | Introduction of the Physical Layer Common Control Channel (PLCCH) | 6.5.0 | 7.0.0 |
+| 20/03/06 | RAN_31 | RP-060079 | 0136 | - | Introduction of 7.68Mcps TDD option | 6.5.0 | 7.0.0 |
+| 29/09/06 | RAN_33 | RP-060492 | 0138 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.0.0 | 7.1.0 |
+| 09/03/07 | RAN_35 | RP-070118 | 0139 | 2 | Introduction of E-DCH for 1.28Mcps TDD | 7.1.0 | 7.2.0 |
+| 30/05/07 | RAN_36 | RP-070385 | 0140 | 2 | Support for MBSFN operation | 7.2.0 | 7.3.0 |
+| 30/05/07 | RAN_36 | RP-070386 | 0142 | - | Support for LCR TDD MBSFN operation | 7.2.0 | 7.3.0 |
+| 30/05/07 | RAN_36 | RP-070386 | 0143 | - | Addition of spreading factor 2 for MBSFN time slot for 1.28Mcps TDD | 7.2.0 | 7.3.0 |
+| 11/09/07 | RAN_37 | RP-070650 | 0144 | - | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.3.0 | 7.4.0 |
+| 11/09/07 | RAN_37 | RP-070647 | 0145 | - | TFCI mapping for S-CCPCH and 16QAM for 1.28Mcps TDD MBSFN | 7.3.0 | 7.4.0 |
+| 27/11/07 | RAN_38 | RP-070943 | 0148 | 2 | More improvement on dedicated carrier for 1.28Mcps TDD MBMS | 7.4.0 | 7.5.0 |
+| 04/03/08 | RAN_39 | RP-080140 | 0150 | - | Clarification of uplink multicode capability for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 |
+| 04/03/08 | RAN_39 | RP-080140 | 0151 | - | EUL power control improvements for 1.28Mcps TDD | 7.5.0 | 7.6.0 |
+| 04/03/08 | RAN_39 | RP-080140 | 0152 | - | E-AGCH timing for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 |
+| 04/03/08 | RAN_39 | RP-080140 | 0153 | - | Clarification of the description about E-PUCH for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 |
+| 04/03/08 | RAN_39 | - | - | - | Creation of Release 8 further to RAN_39 decision | 7.6.0 | 8.0.0 |
+| 28/05/08 | RAN_40 | RP-080356 | 0155 | - | Introduction of 64QAM for 1.28 Mcps TDD HSDPA | 8.0.0 | 8.1.0 |
+| 28/05/08 | RAN_40 | RP-080348 | 0157 | - | Applicability of sync case 2 | 8.0.0 | 8.1.0 |
+| 09/09/08 | RAN_41 | RP-080663 | 0161 | - | Modification of the timing requirement between HS-SCCH and HS-PDSCH for 1.28Mcps TDD | 8.1.0 | 8.2.0 |
+| 09/09/08 | RAN_41 | RP-080662 | 0163 | - | Correction on the time slot format for LCR TDD MBSFN | 8.1.0 | 8.2.0 |
+| 03/12/08 | RAN_42 | RP-080977 | 166 | - | Correction on FPACH misalignment for 1.28Mcps TDD | 8.2.0 | 8.3.0 |
+| 03/12/08 | RAN_42 | RP-080976 | 168 | - | Correction of E-PUCH TPC description for 1.28Mcps TDD | 8.2.0 | 8.3.0 |
+| 03/12/08 | RAN_42 | RP-080987 | 169 | 1 | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.2.0 | 8.3.0 |
+| 03/12/08 | RAN_42 | RP-081118 | 170 | 1 | Support for 3.84 Mcps MBSFN IMB operation | 8.2.0 | 8.3.0 |
+| 03/03/09 | RAN_43 | RP-090230 | 172 | - | Clarification of uplink multicode transmission for 1.28Mcps TDD | 8.3.0 | 8.4.0 |
+| 03/03/09 | RAN_43 | RP-090239 | 173 | - | TFI for Secondary CCPCH frame type 2 with 16QAM | 8.3.0 | 8.4.0 |
+| 03/03/09 | RAN_43 | RP-090241 | 174 | - | Introducing of MIMO for 1.28Mcps TDD | 8.3.0 | 8.4.0 |
+| 03/03/09 | RAN_43 | RP-090240 | 175 | 1 | Introduction CPC for 1.28Mcps TDD | 8.3.0 | 8.4.0 |
+| 03/03/09 | RAN_43 | RP-090231 | 177 | - | Editorial correction for annex CB & CC | 8.3.0 | 8.4.0 |
+| 03/03/09 | RAN_43 | RP-090239 | 178 | - | Specification of T-CPICH sequences for MBSFN IMB | 8.3.0 | 8.4.0 |
+| 26/05/09 | RAN_44 | RP-090531 | 179 | - | Minor corrections for MBSFN IMB | 8.4.0 | 8.5.0 |
+| 26/05/09 | RAN_44 | RP-090533 | 180 | - | Corrections of HS-PDSCH timeslot formats for 1.28Mcps TDD | 8.4.0 | 8.5.0 |
+| 26/05/09 | RAN_44 | RP-090526 | 182 | - | E-PUCH timeslot format parameter corrections for 1.28Mcps TDD | 8.4.0 | 8.5.0 |
+| 15/09/09 | RAN_45 | RP-090893 | 184 | - | Clarification of the transmission of SS and TPC in CPC for 1.28Mcps TDD | 8.5.0 | 8.6.0 |
+| 15/09/09 | RAN_45 | RP-090893 | 185 | 1 | Change of the timing definition in CELL-PCH for 1.28Mcps TDD | 8.5.0 | 8.6.0 |
+
+| Change history | | | | | | | |
+|----------------|--------|-----------|-----|-----|-----------------------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 01/12/09 | RAN_46 | RP-091166 | 189 | 1 | Correction on E-AGCH and SPS E-PUCH Association and Timing for 1.28Mcps TDD | 8.6.0 | 8.7.0 |
+| 01/12/09 | RAN_46 | RP-091166 | 197 | - | Timing association between HS-SCCH and SPS HS-PDSCH for LCR TDD | 8.6.0 | 8.7.0 |
+| 01/12/09 | RAN_46 | RP-091176 | 195 | 1 | Modification to HSPA timing relationship for TS0 for 1.28Mcps TDD | 8.7.0 | 9.0.0 |
+| 16/03/10 | RAN_47 | RP-100202 | 200 | 1 | Clarification of timing association between HS | 9.0.0 | 9.1.0 |
+| 16/03/10 | RAN_47 | RP-100203 | 202 | 1 | Clarification of TPC and SS transmission on HS | 9.0.0 | 9.1.0 |
+| 01/06/10 | RAN_48 | RP-100586 | 204 | - | Clarification of HS-SCCH/HS-DSCH/HS-SICH association for HS-SCCH order | 9.1.0 | 9.2.0 |
+| 01/06/10 | RAN_48 | RP-100588 | 206 | 1 | Resource sharing between scheduled and non-scheduled E-HICHs for LCR TDD | 9.1.0 | 9.2.0 |
+| 01/06/10 | RAN_48 | RP-100587 | 208 | 1 | Clarification for support of an E-HICH pair for 1.28Mcps TDD | 9.1.0 | 9.2.0 |
+| 20/07/10 | - | - | - | - | Correction of version references in change history table | 9.2.0 | 9.2.1 |
+| 14/09/10 | RAN_49 | RP-100895 | 210 | - | Correction of E-DCH Physical Uplink Channel for 1.28Mcps TDD | 9.2.1 | 9.3.0 |
+| 07/12/10 | RAN_50 | RP-101317 | 211 | 2 | Introduction of MC-HSUPA for 1.28Mcps TDD | 9.3.0 | 10.0.0 |
+| 07/12/10 | RAN_50 | RP-101319 | 212 | 1 | Introduction of MU-MIMO for 1.28Mcps TDD | 9.3.0 | 10.0.0 |
+| 15/09/11 | RAN_53 | RP-111227 | 220 | 2 | Clarifications on HSUPA for LCR TDD | 10.0.0 | 10.1.0 |
+| 05/12/11 | RAN_54 | RP-111664 | 224 | - | TPC on Non-scheduled E-PUCH for LCR TDD | 10.1.0 | 10.2.0 |
+| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25322/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/25_series/25322/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7637a5ed53007a98fc57b3805a3421c2204e2200
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f2cd5f94217bf8ea580b9bbd1e8866b3164642eb40753450813c2a9a3303484
+size 277508
diff --git a/marked/Rel-11/25_series/25322/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg b/marked/Rel-11/25_series/25322/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b78849c264e295ed76bf7f86e52571e48bd643b9
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8bb5dc5945d0d8b66c0b83a4931687e13ae5aeabf6e2dc30bc678837335e9fb5
+size 24445
diff --git a/marked/Rel-11/25_series/25322/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/25_series/25322/32ff77da4286b58c4778033acaa10836_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69110578ef7d192bae532d87c5de393c81431f1d
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/32ff77da4286b58c4778033acaa10836_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d70eb7629b1877911d30712ead23f4984627bee63e3094d80a3716bf3e6e270
+size 72271
diff --git a/marked/Rel-11/25_series/25322/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-11/25_series/25322/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b56d6c5ed3584bf8248a6086dc0c50397a4a965
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:deac6e192f7bb03d723ef36f6e6ed8164fefad2ba58f93238a75dbccf1a5ad71
+size 30773
diff --git a/marked/Rel-11/25_series/25322/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-11/25_series/25322/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29c0e1e42d6a55783e5cf7d775beaefbe545e9e1
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9d83a224b12d6f5e8a1237ad13f6528fb85821bb53ac548422e53853cede27d
+size 86294
diff --git a/marked/Rel-11/25_series/25322/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg b/marked/Rel-11/25_series/25322/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..211e589293c851ebfdc126e1a495ffe1cf8f74e5
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1698744af3acc28d5e61da6e1bda12d57ad32010eedcad12f569fa634b8d432
+size 10573
diff --git a/marked/Rel-11/25_series/25322/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/25_series/25322/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44f9979fd41f22ab1e667900aac7aae09938361f
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b99e53938a50c356a8540b6c977cb303e03436d183a8a36ce7d46a086d3a305b
+size 90528
diff --git a/marked/Rel-11/25_series/25322/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-11/25_series/25322/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..528e54a861f3c7e3f75c3c75625838da493d6c24
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb76b4765409323251ac807de501fc68b87b9034a9fb68cd4048fad92baaa51f
+size 10894
diff --git a/marked/Rel-11/25_series/25322/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-11/25_series/25322/759c7d62402f0b4651ddce292be5bdef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a99645c30139885e3ba62349f04e21bb1a14694
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/759c7d62402f0b4651ddce292be5bdef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58c2aeb6e84534567e70dabc285bd20f9330900e867127eae7b99d76cdf47af9
+size 15801
diff --git a/marked/Rel-11/25_series/25322/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-11/25_series/25322/7f17c430b9598e4d748a8041457810b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e774162c2ea6c77e60d8457b82b609227b5e8006
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/7f17c430b9598e4d748a8041457810b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:828bf395685799e7c0bcfeeb7042c0d33fcb8bf1cc2fcb38a012d04941acae1a
+size 84761
diff --git a/marked/Rel-11/25_series/25322/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg b/marked/Rel-11/25_series/25322/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe99483acac52ecadd86db278e9e10bc5a6ee340
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:316d41eb8aca1b11a8e56693ea451ff0162c7863f4a1200df8105fafb819037d
+size 14532
diff --git a/marked/Rel-11/25_series/25322/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-11/25_series/25322/9b686adccf125267a013fa25721231a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..776aae446d119fee9e6b6de5b2504f9f93701305
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/9b686adccf125267a013fa25721231a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccce0f0bf5492256be4f1c3d8f567653e75b760edd3d0e1df47c68fe3dd551da
+size 2946
diff --git a/marked/Rel-11/25_series/25322/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-11/25_series/25322/9b9262a549828579ab904148450734f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5ff3c9932d460bd128a6f450e25c867528acb4e
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/9b9262a549828579ab904148450734f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb4b0f1ee77563639863a6eaf8f757ce17ea54b193d2bf38836a570ce0b500f5
+size 10807
diff --git a/marked/Rel-11/25_series/25322/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-11/25_series/25322/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93b819b0cc05278e387826ddb1c5743b85588322
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d74d0ae44322692919f3a0a1fc4e2abff5a36b268834eac4b89b4583626b25d0
+size 15784
diff --git a/marked/Rel-11/25_series/25322/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/25_series/25322/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e0483d3e42c2b885014c64aef99de72b95c77c2
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b1daa1129ba1ed3237f5136d4fcfa57c3b48065d661c25646a9f691310ca4f3
+size 63545
diff --git a/marked/Rel-11/25_series/25322/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-11/25_series/25322/b5987d63203a5fa601921039922ac520_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..124a5fd8607ae26b367dce64d0b30cc1a24fc36b
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/b5987d63203a5fa601921039922ac520_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f65151a822ed35b7dc4a2591eeb01dd2c6799fc8fae7e6b73735f1bd2a3bb391
+size 36567
diff --git a/marked/Rel-11/25_series/25322/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/Rel-11/25_series/25322/bb3063a33c89b248574f64b6d8dfc404_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5f1bf39986906eb1b530f8bfa783801ee4f5e65
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/bb3063a33c89b248574f64b6d8dfc404_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02c94a2430458124b3cb96af2c93c02b46a42acd361445488798e6cf04fbd682
+size 11589
diff --git a/marked/Rel-11/25_series/25322/d6015fcef74bce83d04acd2e17b4fc15_img.jpg b/marked/Rel-11/25_series/25322/d6015fcef74bce83d04acd2e17b4fc15_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69dd6b82ebf6f86a2cadea8a3e2edad2dfdbbc6a
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/d6015fcef74bce83d04acd2e17b4fc15_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4cd09b5ce3ce32f71564a41c6c937b9de1c2d432f4dd27c3396aaf5cbfd21a90
+size 116108
diff --git a/marked/Rel-11/25_series/25322/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-11/25_series/25322/db5ab5d386827a5d5f5fad0f45612b90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f7a932ae09091835ec76fc2de9b7bbc1a451088
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/db5ab5d386827a5d5f5fad0f45612b90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:887674700b45cf1f56c3c15e47b880d2e9e43ebd4072cc3f11f31f26b7c033a7
+size 15581
diff --git a/marked/Rel-11/25_series/25322/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-11/25_series/25322/e05c1a13b44ab41505609d82b00cf4df_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33e273709ea689e19f61bddf6611dbcdb66c7e4e
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/e05c1a13b44ab41505609d82b00cf4df_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8bd9f833a1688eaa5e5013cece55ddae5b1ca5b74d577daa74dea9dda2b0995
+size 26849
diff --git a/marked/Rel-11/25_series/25322/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-11/25_series/25322/e7010c66da16316c2935dfbbef5056b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ae2dbce851105550cea77f3499fd1b16f80aec5
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/e7010c66da16316c2935dfbbef5056b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f416bddb2e1185f87955a4c8864fc3b612bfbc9aa2981e52bffbe46a6e7b571
+size 19617
diff --git a/marked/Rel-11/25_series/25322/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-11/25_series/25322/e90987faabad6a6665cd8ed1151dc474_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..706ec5ae668b0eedf26768164c7c420577529ff2
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/e90987faabad6a6665cd8ed1151dc474_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53b56d46fcf95f91241fb35cfd341779687b4aa79d0f6c5f944008a259212f8
+size 31605
diff --git a/marked/Rel-11/25_series/25322/raw.md b/marked/Rel-11/25_series/25322/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e6668517f6e8a23173109b72cd50729fa3296d74
--- /dev/null
+++ b/marked/Rel-11/25_series/25322/raw.md
@@ -0,0 +1,3731 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|---------------------------------------------------------------|----|
+| Foreword ..... | 7 |
+| 1 Scope..... | 8 |
+| 2 References..... | 8 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 General..... | 9 |
+| 4.1 Objective ..... | 9 |
+| 4.2 Overview of the RLC sublayer architecture..... | 10 |
+| 4.2.1 Model of the RLC sublayer ..... | 10 |
+| 4.2.1.1 Transparent mode (TM) RLC entities ..... | 12 |
+| 4.2.1.1.1 Transmitting TM RLC entity ..... | 12 |
+| 4.2.1.1.2 Receiving TM RLC entity..... | 12 |
+| 4.2.1.2 Unacknowledged mode (UM) RLC entities ..... | 13 |
+| 4.2.1.2.1 Transmitting UM RLC entity..... | 14 |
+| 4.2.1.2.2 Receiving UM RLC entity ..... | 15 |
+| 4.2.1.3 Acknowledged mode (AM) RLC entity ..... | 15 |
+| 4.2.1.3.1 Transmitting side..... | 16 |
+| 4.2.1.3.2 Receiving side ..... | 17 |
+| 5 Functions..... | 17 |
+| 6 Services provided to upper layers ..... | 18 |
+| 6.1 Mapping of services/functions onto logical channels ..... | 19 |
+| 7 Services expected from MAC ..... | 21 |
+| 8 Elements for layer-to-layer communication ..... | 21 |
+| 8.1 Primitives between RLC and upper layers..... | 21 |
+| 8.2 Primitive parameters ..... | 23 |
+| 9 Elements for peer-to-peer communication..... | 24 |
+| 9.1 Protocol data units ..... | 24 |
+| 9.1.1 Data PDUs ..... | 24 |
+| 9.1.2 Control PDUs ..... | 25 |
+| 9.2 Formats and parameters ..... | 25 |
+| 9.2.1 Formats ..... | 25 |
+| 9.2.1.1 General..... | 26 |
+| 9.2.1.2 TMD PDU..... | 26 |
+| 9.2.1.3 UMD PDU ..... | 26 |
+| 9.2.1.4 AMD PDU ..... | 27 |
+| 9.2.1.5 STATUS PDU ..... | 27 |
+| 9.2.1.6 Piggybacked STATUS PDU..... | 28 |
+| 9.2.1.7 RESET, RESET ACK PDU..... | 28 |
+| 9.2.2 Parameters ..... | 28 |
+| 9.2.2.1 D/C field ..... | 29 |
+| 9.2.2.2 PDU Type ..... | 29 |
+| 9.2.2.3 Sequence Number (SN) ..... | 29 |
+| 9.2.2.4 Polling bit (P)..... | 29 |
+| 9.2.2.5 Extension bit (E) ..... | 29 |
+| 9.2.2.6 Reserved 1 (R1)..... | 30 |
+| 9.2.2.7 Header Extension Type (HE)..... | 30 |
+| 9.2.2.8 Length Indicator (LI) ..... | 30 |
+| 9.2.2.9 Data field..... | 34 |
+| 9.2.2.10 Padding (PAD)..... | 36 |
+| 9.2.2.11 SUFI..... | 36 |
+| 9.2.2.11.1 The No More Data super-field ..... | 37 |
+| 9.2.2.11.2 The Acknowledgement super-field ..... | 37 |
+
+| | | |
+|------------|-----------------------------------------------------------------------------------|----|
+| 9.2.2.11.3 | The Window Size super-field..... | 37 |
+| 9.2.2.11.4 | The List super-field..... | 38 |
+| 9.2.2.11.5 | The Bitmap super-field..... | 38 |
+| 9.2.2.11.6 | The Relative List super-field..... | 39 |
+| 9.2.2.11.7 | The Move Receiving Window Acknowledgement super-field..... | 40 |
+| 9.2.2.11.8 | The Move Receiving Window (MRW) super-field ..... | 40 |
+| 9.2.2.11.9 | The Poll (POLL) super-field ..... | 41 |
+| 9.2.2.12 | Reserved 2 (R2) ..... | 41 |
+| 9.2.2.13 | Reset Sequence Number (RSN)..... | 41 |
+| 9.2.2.14 | Hyper Frame Number Indicator (HFNI)..... | 42 |
+| 9.3 | Protocol states ..... | 42 |
+| 9.3.1 | State model for transparent mode entities ..... | 42 |
+| 9.3.1.1 | NULL State..... | 42 |
+| 9.3.1.2 | DATA_TRANSFER_READY State ..... | 42 |
+| 9.3.2 | State model for unacknowledged mode entities ..... | 42 |
+| 9.3.2.1 | NULL State..... | 42 |
+| 9.3.2.2 | DATA_TRANSFER_READY State ..... | 43 |
+| 9.3.2.3 | LOCAL_SUSPEND State ..... | 43 |
+| 9.3.3 | State model for acknowledged mode entities ..... | 44 |
+| 9.3.3.1 | NULL State..... | 44 |
+| 9.3.3.2 | DATA_TRANSFER_READY State ..... | 44 |
+| 9.3.3.3 | RESET_PENDING State..... | 44 |
+| 9.3.3.4 | LOCAL_SUSPEND State ..... | 46 |
+| 9.3.3.5 | RESET_AND_SUSPEND State ..... | 46 |
+| 9.4 | State variables ..... | 46 |
+| 9.5 | Timers..... | 49 |
+| 9.6 | Protocol Parameters..... | 51 |
+| 9.7 | Specific functions..... | 52 |
+| 9.7.1 | Polling function for acknowledged mode..... | 52 |
+| 9.7.2 | STATUS transmission for acknowledged mode ..... | 54 |
+| 9.7.3 | SDU discard function for acknowledged, unacknowledged, and transparent mode ..... | 55 |
+| 9.7.3.1 | Timer based discard, with explicit signalling ..... | 55 |
+| 9.7.3.2 | Timer based discard, without explicit signalling ..... | 56 |
+| 9.7.3.3 | SDU discard after MaxDAT number of transmissions..... | 56 |
+| 9.7.3.4 | No_discard after MaxDAT number of transmissions..... | 56 |
+| 9.7.3.5 | SDU discard not configured ..... | 56 |
+| 9.7.4 | Void..... | 57 |
+| 9.7.5 | Local Suspend function for acknowledged and unacknowledged mode..... | 57 |
+| 9.7.6 | RLC Stop, RLC Continue function for acknowledged and unacknowledged mode..... | 57 |
+| 9.7.7 | RLC re-establishment function for acknowledged and unacknowledged mode ..... | 58 |
+| 9.7.8 | Ciphering for acknowledged and unacknowledged mode..... | 60 |
+| 9.7.9 | Reconfiguration of RLC parameters by upper layers ..... | 60 |
+| 9.7.10 | Duplicate avoidance and reordering for unacknowledged mode ..... | 61 |
+| 10 | Handling of unknown, unforeseen and erroneous protocol data ..... | 63 |
+| 10.1 | Erroneous Sequence Number ..... | 63 |
+| 10.2 | Inconsistent status indication ..... | 63 |
+| 10.3 | Invalid PDU format..... | 63 |
+| 10.4 | RLC PDU with CRC error ..... | 63 |
+| 11 | Elementary procedures..... | 63 |
+| 11.1 | Transparent mode data transfer procedure ..... | 64 |
+| 11.1.1 | General ..... | 64 |
+| 11.1.2 | Transmission of TMD PDU ..... | 64 |
+| 11.1.2.1 | TMD PDU contents to set..... | 64 |
+| 11.1.2.2 | Submission of TMD PDUs to the lower layer ..... | 64 |
+| 11.1.3 | Reception of TMD PDU..... | 65 |
+| 11.1.4 | Abnormal cases ..... | 65 |
+| 11.1.4.1 | Void ..... | 65 |
+| 11.1.4.2 | SDU discard without explicit signalling ..... | 65 |
+| 11.2 | Unacknowledged mode data transfer procedure ..... | 65 |
+| 11.2.1 | General ..... | 65 |
+
+| | | |
+|------------|------------------------------------------------------------------------------------------------|----|
+| 11.2.2 | Transmission of UMD PDU ..... | 66 |
+| 11.2.2.1 | UMD PDU contents to set ..... | 66 |
+| 11.2.2.2 | Submission of UMD PDUs to the lower layer ..... | 66 |
+| 11.2.3 | Reception of UMD PDU ..... | 67 |
+| 11.2.3.1 | SDU discard and re-assembly ..... | 67 |
+| 11.2.3.2 | Out of sequence SDU delivery ..... | 68 |
+| 11.2.4 | Abnormal cases ..... | 69 |
+| 11.2.4.1 | Length Indicator value reserved for UMD PDU ..... | 69 |
+| 11.2.4.2 | Invalid length indicator value ..... | 69 |
+| 11.2.4.3 | SDU discard without explicit signalling ..... | 69 |
+| 11.2.4.4 | Invalid PDU size ..... | 69 |
+| 11.3 | Acknowledged mode data transfer procedure ..... | 69 |
+| 11.3.1 | General ..... | 69 |
+| 11.3.2 | Transmission of AMD PDU ..... | 70 |
+| 11.3.2.1 | AMD PDU contents to set ..... | 71 |
+| 11.3.2.1.1 | Setting of the Polling bit ..... | 72 |
+| 11.3.2.1.2 | Void ..... | 72 |
+| 11.3.2.2 | Submission of AMD PDUs to lower layer ..... | 72 |
+| 11.3.3 | Reception of AMD PDU by the Receiver ..... | 72 |
+| 11.3.3a | Reached maximum number of attempts ..... | 73 |
+| 11.3.4 | Abnormal cases ..... | 73 |
+| 11.3.4.1 | Void ..... | 73 |
+| 11.3.4.2 | Receiving an AMD PDU outside the reception window ..... | 73 |
+| 11.3.4.3 | Timer_Discard timeout ..... | 74 |
+| 11.3.4.3.1 | SDU discard with explicit signalling ..... | 74 |
+| 11.3.4.4 | Void ..... | 74 |
+| 11.3.4.5 | Invalid length indicator value ..... | 74 |
+| 11.3.4.6 | Length Indicator value reserved for AMD PDU ..... | 74 |
+| 11.3.4.7 | Void ..... | 74 |
+| 11.3.4.8 | Receiving an AMD PDU within the reception window more than once (Handling of Duplicates) ..... | 74 |
+| 11.3.4.9 | Full Buffer Behavior ..... | 74 |
+| 11.3.4.10 | Invalid PDU size ..... | 75 |
+| 11.3.5 | Transmission of POLL SUFI ..... | 75 |
+| 11.4 | RLC reset procedure ..... | 75 |
+| 11.4.1 | General ..... | 75 |
+| 11.4.2 | Initiation ..... | 75 |
+| 11.4.2.1 | RESET PDU contents to set ..... | 76 |
+| 11.4.3 | Reception of the RESET PDU by the Receiver ..... | 76 |
+| 11.4.3.1 | RESET ACK PDU contents to set ..... | 77 |
+| 11.4.4 | Reception of the RESET ACK PDU by the Sender ..... | 77 |
+| 11.4.4a | Reached maximum number of attempts ..... | 78 |
+| 11.4.5 | Abnormal cases ..... | 78 |
+| 11.4.5.1 | Timer_RST timeout ..... | 78 |
+| 11.4.5.2 | Void ..... | 78 |
+| 11.4.5.3 | Reception of the RESET PDU by the Sender ..... | 78 |
+| 11.5 | STATUS report transfer procedure ..... | 79 |
+| 11.5.1 | General ..... | 79 |
+| 11.5.2 | Initiation ..... | 79 |
+| 11.5.2.1 | Piggybacked STATUS PDU ..... | 79 |
+| 11.5.2.2 | STATUS PDU contents to set ..... | 79 |
+| 11.5.2.3 | Submission of STATUS PDUs to the lower layer ..... | 80 |
+| 11.5.3 | Reception of the STATUS PDU by the Sender ..... | 81 |
+| 11.5.4 | Abnormal cases ..... | 81 |
+| 11.5.4.1 | Void ..... | 81 |
+| 11.6 | SDU discard with explicit signalling procedure ..... | 81 |
+| 11.6.1 | General ..... | 81 |
+| 11.6.2 | Initiation ..... | 82 |
+| 11.6.2.1 | Void ..... | 82 |
+| 11.6.2.2 | STATUS PDU contents to set ..... | 83 |
+| 11.6.3 | Reception of the STATUS PDU by the Receiver ..... | 84 |
+| 11.6.3.1 | STATUS PDU contents to set ..... | 84 |
+| 11.6.4 | Termination ..... | 85 |
+
+11.6.5 Expiration of timer Timer\_MRW..... 85
+11.6.6 Abnormal cases ..... 85
+11.6.6.1 Reception of obsolete/corrupted MRW SUFI by the Receiver ..... 85
+11.6.6.2 Void ..... 86
+11.6.6.3 Reception of obsolete/corrupted MRW\_ACK SUFI by the Sender ..... 86
+11.7 Void..... 86
+11.8 Void..... 86
+Annex A (informative): Change history..... 87
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the Radio Link Control protocol for the UE-UTRAN radio interface.
+
+Features for the current Release:
+
+- Transparent mode.
+- Unacknowledged mode.
+- Acknowledged mode.
+
+# --- 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 25.990: "Vocabulary for UTRAN".
+- [3] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [4] 3GPP TS 25.302: "Services provided by the Physical Layer".
+- [5] 3GPP TS 25.303: "Interlayer procedures in Connected Mode".
+- [6] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode".
+- [7] 3GPP TS 25.321: "Medium Access Control (MAC); protocol specification".
+- [8] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification".
+- [9] 3GPP TS 33.102: "3G security; Security architecture".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in [2] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|------|---------------------------|
+| AM | Acknowledged Mode |
+| AMD | Acknowledged Mode Data |
+| ARQ | Automatic Repeat Request |
+| BCCH | Broadcast Control CHannel |
+| BCH | Broadcast CHannel |
+| C- | Control- |
+| CCCH | Common Control CHannel |
+
+| | |
+|--------|---------------------------------------------|
+| CCH | Control CHannel |
+| CCTrCH | Coded Composite Transport CHannel |
+| CRC | Cyclic Redundancy Check |
+| CTCH | Common Traffic CHannel |
+| DCCH | Dedicated Control CHannel |
+| DCH | Dedicated CHannel |
+| DL | DownLink |
+| DSCH | Downlink Shared CHannel |
+| DTCH | Dedicated Traffic CHannel |
+| FACH | Forward link Access CHannel |
+| FDD | Frequency Division Duplex |
+| L1 | Layer 1 (physical layer) |
+| L2 | Layer 2 (data link layer) |
+| L3 | Layer 3 (network layer) |
+| LI | Length Indicator |
+| LSB | Least Significant Bit |
+| MAC | Medium Access Control |
+| MBMS | Multimedia Broadcast Multicast Service |
+| MCCH | MBMS point-to-multipoint Control CHannel |
+| MRW | Move Receiving Window |
+| MSB | Most Significant Bit |
+| MSCH | MBMS point-to-multipoint Scheduling CHannel |
+| MTCH | MBMS point-to-multipoint Traffic CHannel |
+| PCCH | Paging Control CHannel |
+| PCH | Paging CHannel |
+| PDU | Protocol Data Unit |
+| PHY | PHYsical layer |
+| PhyCH | Physical CHannels |
+| RACH | Random Access CHannel |
+| RLC | Radio Link Control |
+| RRC | Radio Resource Control |
+| SAP | Service Access Point |
+| SDU | Service Data Unit |
+| SHCCH | SHared channel Control CHannel |
+| SN | Sequence Number |
+| SUFI | SUPER Field |
+| TCH | Traffic CHannel |
+| TDD | Time Division Duplex |
+| TFI | Transport Format Indicator |
+| TM | Transparent Mode |
+| TMD | Transparent Mode Data |
+| TTI | Transmission Time Interval |
+| U- | User- |
+| UE | User Equipment |
+| UL | UpLink |
+| UM | Unacknowledged Mode |
+| UMD | Unacknowledged Mode Data |
+| UMTS | Universal Mobile Telecommunications System |
+| UTRA | UMTS Terrestrial Radio Access |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+# --- 4 General
+
+## 4.1 Objective
+
+This subclause describes the architecture of the RLC sublayer.
+
+## 4.2 Overview of the RLC sublayer architecture
+
+The model presented in this subclause is intended to support the definition of the RLC sublayer only, and is not meant to specify or constrain the implementation of the protocol. The RLC sublayer consists of RLC entities, of which there are three types: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM) RLC entities.
+
+### 4.2.1 Model of the RLC sublayer
+
+Figure 4.1 illustrates different RLC entities in the RLC model.
+
+An UM and a TM RLC entity can be configured to be a transmitting RLC entity or a receiving RLC entity. The transmitting RLC entity transmits RLC PDUs and the receiving RLC entity receives RLC PDUs. An AM RLC entity consists of a transmitting side, and a receiving side, where the transmitting side of the AM RLC entity transmits RLC PDUs and the receiving side of the AM RLC entity receives RLC PDUs.
+
+Elementary procedures (see clause 11) are defined between a "Sender" and a "Receiver". In UM and TM, the transmitting RLC entity acts as a Sender and the peer RLC entity acts as a Receiver. An AM RLC entity acts either as a Sender or as a Receiver depending on the elementary procedure. The Sender is the transmitter of AMD PDUs and the Receiver is the receiver of AMD PDUs. A Sender or a Receiver can reside at either the UE or the UTRAN.
+
+There is one transmitting and one receiving RLC entity for each transparent mode (TM) and unacknowledged mode (UM) service. There is one combined, transmitting and receiving entity for the acknowledged mode (AM) service.
+
+In the present document, "transmitted" is equivalent to "submitted to the lower layer" unless otherwise explicitly stated. Each RLC UM, and TM entity uses one logical channel to send or receive data PDUs. An AM RLC entity can be configured to use one or two logical channels to send or receive data and control PDUs. If two logical channels are configured, they are of the same type (DCCH or DTCH). In figure 4.1, the dashed lines between the AM-Entities illustrate the possibility to send and receive RLC PDUs on separate logical channels, e.g. control PDUs on one and data PDUs on the other. A more detailed description of the different entities is given in subclauses 4.2.1.1, 4.2.1.2 and 4.2.1.3.
+
+
+
+The diagram illustrates the RLC sublayer architecture across the Radio Interface between the MS (Mobile Station) and the UTRAN (UTRA Network). The RLC sublayer is shown as a shaded gray area containing various entities: AM-Entity, Receiv. UM-Entity, Receiv. Tr-Entity, Transm. UM-Entity, and Transm. Tr-Entity. On the MS side, there is one AM-Entity, one Receiv. UM-Entity, one Receiv. Tr-Entity, one Transm. UM-Entity, and one Transm. Tr-Entity. On the UTRAN side, there is one AM-Entity, two Receiv. UM-Entities, two Receiv. Tr-Entities, one Transm. UM-Entity, and one Transm. Tr-Entity. The diagram is divided into 'Receiving side' and 'Transmitting side' by vertical labels. Arrows indicate data flow from 'Upper Layers' into the RLC entities and from RLC entities down to the 'MAC' layer. Dashed lines represent logical connections between corresponding entities on the MS and UTRAN sides.
+
+Overview model of the RLC sublayer diagram showing MS and UTRAN components with RLC entities (AM, UM, Tr) and their connections to Upper Layers and MAC.
+
+Figure 4.1: Overview model of the RLC sublayer
+
+#### 4.2.1.1 Transparent mode (TM) RLC entities
+
+Figure 4.2 below shows the model of two transparent mode peer RLC entities. The logical channels used to communicate with the lower layer are described in the figure below.
+
+
+
+Figure 4.2: Model of two transparent mode peer entities. The diagram shows two RLC entities, 'Transmitting TM- RLC entity' on the left and 'Receiving TM- RLC entity' on the right, connected by a 'Radio Interface (Uu)'. The transmitting entity receives data from 'UE/UTRAN' via 'TM-SAP', stores it in a 'Transmission buffer', and then processes it through 'Segmentation' before sending it to the lower layer. The receiving entity receives data from the lower layer through 'Reception buffer', reassembles it in 'Reassembly', and then sends it to 'UTRAN/UE' via 'TM-SAP'. The lower layer is connected to logical channels: 'CCCH/DTCH/SHCH - UE' and 'BCCH/PCCH/DCCH/DTCH - UTRAN' on the left, and 'CCCH/DTCH/SHCH - UTRAN' and 'BCCH/PCCH/DCCH/DTCH - UE' on the right.
+
+**Figure 4.2: Model of two transparent mode peer entities**
+
+##### 4.2.1.1.1 Transmitting TM RLC entity
+
+The transmitting TM-RLC entity receives RLC SDUs from upper layers through the TM-SAP.
+
+All received RLC SDUs must be of a length that is a multiple of one of the valid TMD PDU lengths.
+
+If segmentation has been configured by upper layers and a RLC SDU is larger than the TMD PDU size used by the lower layer for that TTI, the transmitting TM RLC entity segments RLC SDUs to fit the TMD PDUs size without adding RLC headers. All the TMD PDUs carrying one RLC SDU are sent in the same TTI, and no segment from another RLC SDU are sent in this TTI.
+
+If segmentation has not been configured by upper layers, then more than one RLC SDU can be sent in one TTI by placing one RLC SDU in one TMD PDU. All TMD PDUs in one TTI must be of equal length.
+
+When the processing of a RLC SDU is complete, the resulting one or more TMD PDU(s) are/is submitted to the lower layer through either a BCCH, DCCH, PCCH, CCCH, SHCH or a DTCH logical channel.
+
+##### 4.2.1.1.2 Receiving TM RLC entity
+
+The receiving TM-RLC entity receives TMD PDUs through the configured logical channels from the lower layer. If segmentation is configured by upper layers, all TMD PDUs received within one TTI are reassembled to form the RLC SDU.
+
+If segmentation is not configured by upper layers, each TMD PDU is treated as a RLC SDU.
+
+The receiving TM RLC entity delivers RLC SDUs to upper layers through the TM-SAP.
+
+#### 4.2.1.2 Unacknowledged mode (UM) RLC entities
+
+Figure 4.3 below shows the model of two unacknowledged mode peer RLC entities when duplicate avoidance and reordering is not configured. The different functions shown in Figure 4.3 below apply to different logical channel types as described in subclause 6.1.
+
+
+
+The diagram illustrates the model of two unacknowledged mode (UM) RLC entities connected via a Radio Interface (Uu). The entities are labeled as 'Transmitting UM RLC entity' on the left and 'Receiving UM RLC entity' on the right.
+
+**Left Side (UE/UTRAN):**
+
+- Data enters from the top through a UM-SAP.
+- The Transmitting UM RLC entity contains the following functions in a vertical stack:
+ - Transmission buffer
+ - Segmentation & Concatenation
+ - Add RLC header
+ - Ciphering
+- Data exits the bottom of the entity through another UM-SAP.
+
+**Right Side (UTRAN/UE):**
+
+- Data enters from the bottom through a UM-SAP.
+- The Receiving UM RLC entity contains the following functions in a vertical stack:
+ - Deciphering
+ - Reception buffer
+ - Remove RLC header
+ - Reassembly
+- Data exits from the top through a UM-SAP.
+
+**Radio Interface (Uu):**
+
+- The interface is represented by a vertical line between the two entities.
+- Below the interface, the logical channel types are listed:
+ - DCCH/DTCH – UE
+ - CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UTRAN
+ - DCCH/DTCH – UTRAN
+ - CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UE
+
+Diagram of two unacknowledged mode (UM) RLC entities connected via a Radio Interface (Uu). The left side (UE/UTRAN) shows the Transmitting UM RLC entity with functions: Transmission buffer, Segmentation & Concatenation, Add RLC header, and Ciphering. The right side (UTRAN/UE) shows the Receiving UM RLC entity with functions: Reassembly, Remove RLC header, Reception buffer, and Deciphering. Data flows from the Transmitting entity to the Receiving entity via the Radio Interface (Uu).
+
+**Figure 4.3: Model of two unacknowledged mode peer entities configured for use without duplicate avoidance and reordering**
+
+Figure 4.3a below shows the model of two unacknowledged mode peer RLC entities configured for duplicate avoidance and reordering. Because duplicate avoidance and reordering is only specified for MTCH/CCCH in this release, ciphering/ deciphering is omitted.
+
+
+
+Figure 4.3a: Model of two unacknowledged mode peer entities configured for use with duplicate avoidance and reordering. The diagram shows the flow of data between UTRAN and UE across the Radio Interface (Uu). On the UTRAN side, data enters through the UM-SAP, passes through a Transmission buffer, Segmentation & Concatenation, and Add RLC header blocks, then exits via MTCH/CCCH - UTRAN. On the UE side, data enters via MTCH/CCCH - UE, passes through Duplicate avoidance and reordering, Reception buffer, Remove RLC header, and Reassembly blocks, then exits through the UM-SAP. The Transmitting UM RLC entity is on the UTRAN side, and the Receiving UM RLC entity is on the UE side.
+
+**Figure 4.3a: Model of two unacknowledged mode peer entities configured for use with duplicate avoidance and reordering**
+
+##### 4.2.1.2.1 Transmitting UM RLC entity
+
+The transmitting UM-RLC entity receives RLC SDUs from upper layers through the UM-SAP.
+
+The transmitting UM RLC entity segments the RLC SDU into UMD PDUs of appropriate size, if the RLC SDU is larger than the length of available space in the UMD PDU. The size of the UMD PDUs after segmentation and/or concatenation shall be smaller than or equal to the largest UL UMD PDU size. If MAC-i/s has been configured and the RLC PDU size is set to "flexible size", the size of the UMD PDUs after segmentation and/or concatenation shall be larger than or equal to the Minimum UL RLC PDU size. If data to be transmitted is not enough to create a UMD PDU of the minimum size, it is allowed to create a UMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. The UMD PDU may contain segmented and/or concatenated RLC SDUs. UMD PDU may also contain padding to ensure that it is of a valid length. Length Indicators are used to define boundaries between RLC SDUs within UMD PDUs unless the "Extension bit" already indicates that a UMD PDU contains exactly one complete SDU. Length Indicators are also used to define whether Padding is included in the UMD PDU.
+
+If ciphering is configured and started, an UMD PDU is ciphered (except for the UMD PDU header) before it is submitted to the lower layer.
+
+The transmitting UM RLC entity submits UMD PDUs to the lower layer through either a CCCH, SHCCH, DCCH, CTCH, DTCH, MCCH, MSCH or an MTCH logical channel.
+
+##### 4.2.1.2.2 Receiving UM RLC entity
+
+The receiving UM-RLC entity receives UMD PDUs through the configured logical channels from the lower layer. When duplicate avoidance and reordering is configured there may be one or more than one input from the lower layer. Inputs can be added or removed without changing the buffer contents, state variables or timers within the receiving UM RLC entity. Where duplicate avoidance and reordering is not configured there is only one input from the lower layer and it is not reconfigured.
+
+When configured, duplicate avoidance and reordering is the first receive function that is applied to the input UMD PDU streams in the receiving UM RLC entity. It can only be configured in a UE, it is not used in UTRAN. It completes
+
+duplicate detection and re-ordering of the UMD PDUs that are received from the one or more inputs to produce a single ordered sequence of PDUs that is passed to the next in sequence RLC receiver function.
+
+The receiving UM RLC entity deciphers (if ciphering is configured and started) the received UMD PDUs (except for the UMD PDU header). It removes RLC headers from received UMD PDUs, and reassembles RLC SDUs (if segmentation and/or concatenation has been performed by the transmitting UM RLC entity).
+
+If a receiving UM RLC entity is configured for out of sequence SDU delivery, it will reassemble SDUs and transfer them to the upper layers as soon as all PDUs that contain the SDU have been received even if earlier PDUs have not yet been received. It will store PDUs pending the retransmission of missing PDUs by the transmitting UM RLC. PDUs are removed from storage after recovery of all of its associated SDUs, or by a sequence number window function or a storage timer. Out of sequence SDU delivery is configured only in the UE and is only used with MCCH.
+
+RLC SDUs are delivered by the receiving UM RLC entity to the upper layers through the UM-SAP. If SN\_Delivery is configured, the sequence number of RLC PDU in which RLC SDU is mapped to is also delivered to the upper layers through the UM-SAP.
+
+#### 4.2.1.3 Acknowledged mode (AM) RLC entity
+
+Figure 4.4 below shows the model of an acknowledged mode RLC entity.
+
+The AM RLC entity can be configured to utilise one or two logical channels. The figure 4.4 shows the model of the AM RLC entity when one logical channel (shown as a solid line) and when two logical channels (shown as dashed lines) are used.
+
+If one logical channel is configured, the transmitting side of the AM RLC entity submits AMD and Control PDUs to the lower layer on that logical channel. If fixed RLC PDU size is configured the RLC PDU size shall be the same for AMD PDUs and control PDUs. If flexible RLC PDU size is configured the AMD PDU size is variable up to a maximum RLC PDU size.
+
+In case two logical channels are configured in the uplink, AMD PDUs and control PDUs except acknowledgement status report, MRW ACK SUFI and WINDOW SUFI shall be transmitted on the first logical channel, and acknowledgement status reports, MRW ACK SUFI and WINDOW SUFI shall be transmitted on the second logical channel. In case two logical channels are configured in the downlink, AMD and Control PDUs can be transmitted on any of the two logical channels.
+
+
+
+Figure 4.4: Model of an acknowledged mode entity. This diagram illustrates the internal architecture of an AM-RLC entity, divided into Transmitting and Receiving sides by a central dashed line. On the Transmitting side, data flows from the AM-SAP through Segmentation/Concatenation and Add RLC header blocks, then into a Retransmission buffer & management block. It then passes through a MUX, a Transmission buffer, and a block for setting fields in the PDU Header (including poll bits and piggybacked STATUS PDU), followed by Ciphering (only for AMD PDU). The data is then sent to the DCCH/DTCH\*\* channels. The RLC Control Unit, which receives Piggybacked status Optional information, sends Acknowledgements to the Retransmission buffer. On the Receiving side, data from DCCH/DTCH\* channels goes through Demux/Routing, then Deciphering, then Reception buffer & Retransmission management, then Remove RLC header & Extract Piggybacked information, and finally Reassembly, which outputs to the AM-SAP. The RLC Control Unit also receives Received acknowledgements from the Reception buffer.
+
+**Figure 4.4: Model of an acknowledged mode entity**
+
+##### 4.2.1.3.1 Transmitting side
+
+The transmitting side of the AM-RLC entity receives RLC SDUs from upper layers through the AM-SAP.
+
+If fixed RLC PDU size is configured, RLC SDUs are segmented and/or concatenated into AMD PDUs of a fixed length. The segmentation is performed if the received RLC SDU is larger than the length of available space in the AMD PDU. The uplink AMD PDU size is a semi-static value that is configured by upper layers and can only be changed through re-establishment of the AM RLC entity by upper layers.
+
+If flexible RLC PDU size is configured, RLC SDUs are segmented and/or concatenated to create RLC PDUs larger than or equal to the Minimum UL RLC PDU size and smaller than or equal to the largest UL AMD PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to create an AMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size.
+
+**NOTE:** In downlink, if flexible RLC PDU size is configured, RLC SDUs are segmented if the SDU is larger than the maximum RLC PDU size. Concatenation may be performed up to the maximum RLC PDU size.
+
+The AMD PDU may contain segmented and/or concatenated RLC SDUs. The AMD PDU may also contain Padding to ensure that it is of a valid size. If fixed RLC PDU size is configured, Length Indicators or a special value of the HE field can be used to define boundaries between RLC SDUs within AMD PDUs. Length Indicators are also used to define whether Padding or Piggybacked STATUS PDU is included in the AMD PDU. If flexible RLC PDU size is configured,
+
+the Length Indicator size is configured by upper layers. The use of the special value of the HE field is configured by higher layers.
+
+After the segmentation and/or concatenation are performed, the AMD PDUs are placed in the Retransmission buffer and at the MUX.
+
+AMD PDUs buffered in the Retransmission buffer are deleted or retransmitted based on the status report found within a STATUS PDU or Piggybacked STATUS PDU sent by the peer AM RLC entity. This status report may contain positive or negative acknowledgements of individual AMD PDUs received by the peer AM RLC entity.
+
+The MUX multiplexes AMD PDUs from the Retransmission buffer that need to be retransmitted, and the newly generated AMD PDUs delivered from the Segmentation/Concatenation function.
+
+The PDUs are delivered to the function that completes the AMD PDU header and potentially replaces padding with piggybacked status information. A Piggybacked STATUS PDUs can be of variable size in order to match the amount of free space in the AMD PDU. The AMD PDU header is completed based on the input from the RLC Control Unit that indicates the values to set in various fields (e.g. Polling Bit). The function also multiplexes, if required, Control PDUs received from the RLC Control Unit (RESET and RESET ACK PDUs), and from the Reception buffer (Piggybacked STATUS and STATUS PDUs), with AMD PDUs.
+
+The ciphering (if configured) is then applied to the AMD PDUs. The AMD PDU header is not ciphered. Piggybacked STATUS PDU and Padding in AMD PDU (when present) are ciphered. Control PDUs (i.e. STATUS PDU, RESET PDU, and RESET ACK PDU) are not ciphered.
+
+The transmitting side of the AM RLC entity submits AMD PDUs to the lower layer through either one or two DCCH or DTCH logical channels.
+
+##### 4.2.1.3.2 Receiving side
+
+The receiving side of the AM-RLC entity receives AMD and Control PDUs through the configured logical channels from the lower layer.
+
+If fixed RLC PDU size is configured, the AMD PDU size is a semi-static value that is configured by upper layers and can only be changed through re-establishment of the AM RLC entity by upper layers. In the case where the AMD PDU size is not configured, it is determined based on the first PDU received. The downlink and uplink AMD PDU sizes need not be the same.
+
+If flexible RLC PDU size is configured, the AMD PDU size is variable up to the maximum RLC PDU size, and the Length Indicator size is configured by upper layers.
+
+AMD PDUs are routed to the Deciphering Unit, where AMD PDUs (minus the AMD PDU header) are deciphered (if ciphering is configured and started), and then delivered to the Reception buffer.
+
+The AMD PDUs are placed in the Reception buffer until a complete RLC SDU has been received. The Receiver acknowledges successful reception or requests retransmission of the missing AMD PDUs by sending one or more STATUS PDUs to the AM RLC peer entity, through its transmitting side. If a Piggybacked STATUS PDU is found in an AMD PDU, it is delivered to the Retransmission buffer & Management Unit at the transmitting side of the AM RLC entity, in order to purge the buffer of positively acknowledged AMD PDUs, and to indicate which AMD PDUs need to be retransmitted.
+
+Once a complete RLC SDU has been received, the associated AMD PDUs are reassembled by the Reassembly Unit and delivered to upper layers through the AM-SAP.
+
+RESET and RESET ACK PDUs are delivered to the RLC Control Unit for processing. If a response to the peer AM RLC entity is needed, an appropriate Control PDU is delivered, by the RLC Control Unit to the transmitting side of the AM RLC entity. The received STATUS PDUs are delivered to the Retransmission buffer and Management Unit at the transmitting side of the AM RLC entity, in order to purge the buffer of positively acknowledged AMD PDUs, and to indicate which AMD PDUs need to be retransmitted.
+
+# --- 5 Functions
+
+The following functions are supported by RLC sublayer. For an overall description of the following functions see [3]:
+
+- Segmentation and reassembly.
+
+- Concatenation.
+- Padding.
+- Transfer of user data.
+- Error correction.
+- In-sequence delivery of upper layer PDUs.
+- Duplicate detection.
+- Flow control.
+- Sequence number check.
+- Protocol error detection and recovery.
+- Ciphering.
+- SDU discard.
+- Out of sequence SDU delivery.
+- Duplicate avoidance and reordering.
+
+# --- 6 Services provided to upper layers
+
+This clause describes the different services provided by RLC sublayer to upper layers. It also includes the mapping of RLC functions to different RLC services. For a detailed description of the RLC services see [3].
+
+## - **Transparent data transfer Service:**
+
+The following functions are needed to support transparent data transfer:
+
+- Segmentation and reassembly.
+- Transfer of user data.
+- SDU discard.
+
+## - **Unacknowledged data transfer Service:**
+
+The following functions are needed to support unacknowledged data transfer:
+
+- Segmentation and reassembly.
+- Concatenation.
+- Padding.
+- Transfer of user data.
+- Ciphering.
+- Sequence number check.
+- SDU discard.
+- Out of sequence SDU delivery.
+- Duplicate avoidance and reordering.
+- Provisioning of sequence number.
+
+## - **Acknowledged data transfer Service:**
+
+The following functions are needed to support acknowledged data transfer:
+
+- Segmentation and reassembly.
+- Concatenation.
+- Padding.
+- Transfer of user data.
+- Error correction.
+- In-sequence delivery of upper layer PDUs.
+- Duplicate detection.
+- Flow Control.
+- Protocol error detection and recovery.
+- Ciphering.
+- SDU discard.
+- **Maintenance of QoS as defined by upper layers.**
+- **Notification of unrecoverable errors.**
+
+## 6.1 Mapping of services/functions onto logical channels
+
+The following tables show the applicability of services and functions to the logical channels in UL/DL and UE/UTRAN. A '+' in a column denotes that the service/function is applicable for the logical channel in question whereas a '-' denotes that the service/function is not applicable.
+
+**Table 6.1: RLC modes and functions in UE uplink side**
+
+| Service | Functions | CCCH | SHCC H | DCCH | DTCH |
+|-------------------------------|-------------------------------------|------|--------|------|------|
+| Transparent Service | Applicability | + | + | - | + |
+| | Segmentation | - | - | - | + |
+| | Transfer of user data | + | + | - | + |
+| | SDU Discard | - | - | - | + |
+| Unacknowledged Service | Applicability | - | - | + | + |
+| | Segmentation | - | - | + | + |
+| | Concatenation | - | - | + | + |
+| | Padding | - | - | + | + |
+| | Transfer of user data | - | - | + | + |
+| | Ciphering | - | - | + | + |
+| | SDU Discard | - | - | + | + |
+| Acknowledged Service | Applicability | - | - | + | + |
+| | Segmentation | - | - | + | + |
+| | Concatenation | - | - | + | + |
+| | Padding | - | - | + | + |
+| | Transfer of user data | - | - | + | + |
+| | Flow Control | - | - | + | + |
+| | Error Correction | - | - | + | + |
+| | Protocol error detection & recovery | - | - | + | + |
+| | Ciphering | - | - | + | + |
+| | SDU Discard | - | - | + | + |
+
+**Table 6.2: RLC modes and functions in UE downlink side**
+
+| Service | Functions | BCC H | PCC H | SHCC H | CCC H | DCC H | DTC H | CTC H | MCC H | MTCH | MSCH |
+|-------------------------------|-------------------------------------|-------|-------|--------|-------|-------|-------|-------|-------|------|------|
+| Transparent Service | Applicability | + | + | - | - | + | + | - | - | - | - |
+| | Reassembly | - | - | - | - | + | + | - | - | - | - |
+| | Transfer of user data | + | + | - | - | + | + | - | - | - | - |
+| Unacknowledged Service | Applicability | - | - | + | + | + | + | + | + | + | + |
+| | Reassembly | - | - | + | + | + | + | + | + | + | + |
+| | Deciphering | - | - | - | - | + | + | - | - | - | - |
+| | Sequence number check | - | - | + | + | + | + | + | + | + | + |
+| | Transfer of user data | - | - | + | + | + | + | + | + | + | + |
+| | Duplicate avoidance and reordering | - | - | - | + | - | - | - | - | + | - |
+| | Out of sequence SDU delivery | - | - | - | - | - | - | - | + | - | - |
+| Acknowledged Service | Applicability | - | - | - | - | + | + | - | - | - | - |
+| | Reassembly | - | - | - | - | + | + | - | - | - | - |
+| | Error correction | - | - | - | - | + | + | - | - | - | - |
+| | Flow Control | - | - | - | - | + | + | - | - | - | - |
+| | In sequence delivery | - | - | - | - | + | + | - | - | - | - |
+| | Duplicate detection | - | - | - | - | + | + | - | - | - | - |
+| | Protocol error detection & recovery | - | - | - | - | + | + | - | - | - | - |
+| | Deciphering | - | - | - | - | + | + | - | - | - | - |
+| | Transfer of user data | - | - | - | - | + | + | - | - | - | - |
+| | SDU Discard | - | - | - | - | + | + | - | - | - | - |
+
+NOTE: Duplicate avoidance and reordering function is optional in UE.
+
+**Table 6.3: RLC modes and functions in UTRAN downlink side**
+
+| Service | Functions | BCCH | PCC H | CCCH | SHCC H | DCC H | DTC H | CTC H | MCC H | MTCH | MSCH |
+|-------------------------------|-------------------------------------|------|-------|------|--------|-------|-------|-------|-------|------|------|
+| Transparent Service | Applicability | + | + | - | - | + | + | - | - | - | - |
+| | Segmentation | - | - | - | - | + | + | - | - | - | - |
+| | Transfer of user data | + | + | - | - | + | + | - | - | - | - |
+| | SDU Discard | - | - | - | - | + | + | - | - | - | - |
+| Unacknowledged Service | Applicability | - | - | + | + | + | + | + | + | + | + |
+| | Segmentation | - | - | + | + | + | + | + | + | + | + |
+| | Concatenation | - | - | + | + | + | + | + | + | + | + |
+| | Padding | - | - | + | + | + | + | + | + | + | + |
+| | Ciphering | - | - | - | - | + | + | - | - | - | - |
+| | Transfer of user data | - | - | + | + | + | + | + | + | + | + |
+| | SDU Discard | - | - | - | - | + | + | - | + | + | + |
+| Acknowledged Service | Applicability | - | - | - | - | + | + | - | - | - | - |
+| | Segmentation | - | - | - | - | + | + | - | - | - | - |
+| | Concatenation | - | - | - | - | + | + | - | - | - | - |
+| | Padding | - | - | - | - | + | + | - | - | - | - |
+| | Transfer of user data | - | - | - | - | + | + | - | - | - | - |
+| | Flow Control | - | - | - | - | + | + | - | - | - | - |
+| | Error Correction | - | - | - | - | + | + | - | - | - | - |
+| | Protocol error detection & recovery | - | - | - | - | + | + | - | - | - | - |
+| | Ciphering | - | - | - | - | + | + | - | - | - | - |
+| | SDU Discard | - | - | - | - | + | + | - | - | - | - |
+
+**Table 6.4: RLC modes and functions in UTRAN uplink side**
+
+| Service | Functions | CCCH | SHCC H | DCCH | DTCH |
+|-------------------------------|-------------------------------------|------|--------|------|------|
+| Transparent Service | Applicability | + | + | - | + |
+| | Reassembly | - | - | - | + |
+| | Transfer of user data | + | + | - | + |
+| Unacknowledged Service | Applicability | - | - | + | + |
+| | Reassembly | - | - | + | + |
+| | Deciphering | - | - | + | + |
+| | Sequence number check | - | - | + | + |
+| | Transfer of user data | - | - | + | + |
+| Acknowledged Service | Applicability | - | - | + | + |
+| | Reassembly | - | - | + | + |
+| | Error correction | - | - | + | + |
+| | Flow Control | - | - | + | + |
+| | In sequence delivery | - | - | + | + |
+| | Duplicate detection | - | - | + | + |
+| | Protocol error detection & recovery | - | - | + | + |
+| | Deciphering | - | - | + | + |
+| | Transfer of user data | - | - | + | + |
+| | SDU Discard | - | - | + | + |
+
+# 7 Services expected from MAC
+
+For a detailed description of the service provided by the MAC sublayer to upper layers see [3].
+
+- Data transfer.
+
+# 8 Elements for layer-to-layer communication
+
+The interaction between the RLC sublayer and other layers are described in terms of primitives where the primitives represent the logical exchange of information and control between the RLC sublayer and other layers. The primitives shall not specify or constrain the implementation.
+
+## 8.1 Primitives between RLC and upper layers
+
+The primitives between RLC and upper layers are shown in table 8.1.
+
+**Table 8.1: Primitives between RLC and upper layers**
+
+| Generic Name | Parameters | | | |
+|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|-----------------------------------|
+| | Req. | Ind. | Resp. | Conf. |
+| RLC-AM-DATA | Data, CNF, DiscardReq, MUI, UE-ID type indicator | Data, DiscardInfo | Not Defined | Status, MUI |
+| RLC-UM-DATA | Data, UE-ID type indicator, DiscardReq, MUI | Data, Sequence_Number | Not Defined | MUI |
+| RLC-TM-DATA | Data, UE-ID type indicator, DiscardReq, MUI | Data, Error_Indicator | Not Defined | MUI |
+| CRLC-CONFIG | E/R, Stop (UM/AM only), Continue (UM/AM only), Ciphering Elements (UM/AM only), TM_parameters (TM only), UM_parameters (UM only), AM_parameters (AM only), SN_Delivery (UM only) | Not Defined | Not Defined | Not Defined |
+| CRLC-SUSPEND (UM/AM only) | N | Not Defined | Not Defined | VT(US) (UM only), VT(S) (AM only) |
+| CRLC-RESUME (UM/AM only) | No Parameter | Not Defined | Not Defined | Not Defined |
+| CRLC-STATUS | Not Defined | EVC | Not Defined | Not Defined |
+
+Each Primitive is defined as follows:
+
+### **RLC-AM-DATA-Req/Ind/Conf**
+
+- RLC-AM-DATA-Req is used by upper layers to request transmission of an RLC SDU in acknowledged mode.
+- RLC-AM-DATA-Ind is used by the AM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in acknowledged mode and to indicate to upper layers of the discarded RLC SDU in the peer RLC AM entity.
+- RLC-AM-DATA-Conf is used by the AM RLC entity to confirm to upper layers the reception of an RLC SDU by the peer-RLC AM entity or to inform the upper layers of a discarded SDU.
+
+### **RLC-UM-DATA-Req/Ind/Conf**
+
+- RLC-UM-DATA-Req is used by upper layers to request transmission of an RLC SDU in unacknowledged mode.
+- RLC-UM-DATA-Ind is used by the UM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in unacknowledged mode. If SN\_Delivery is configured, RLC-UM-DATA-Ind is used by the UM RLC entity to deliver to upper layers also Sequence\_Number.
+- RLC-UM-DATA-Conf is used by the UM RLC entity to inform the upper layers of a discarded SDU.
+
+### **RLC-TM-DATA-Req/Ind/Conf**
+
+- RLC-TM-DATA-Req is used by upper layers to request transmission of an RLC SDU in transparent mode.
+- RLC-TM-DATA-Ind is used by the TM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in transparent mode.
+- RLC-TM-DATA-Conf is used by the TM RLC entity to inform the upper layers of a discarded SDU.
+
+### **CRLC-CONFIG-Req**
+
+This primitive is used by upper layers to establish, re-establish, release, stop, continue or modify the RLC. Ciphering elements are included for UM and AM operation.
+
+### **CRLC-SUSPEND-Req/Conf**
+
+- CRLC-SUSPEND-Req is used by upper layers to suspend the UM or AM RLC entity.
+- CRLC-SUSPEND-Conf is used by the UM or AM RLC entity to confirm that the entity is suspended.
+
+### **CRLC-RESUME-Req**
+
+This primitive is used by upper layers to resume the UM or AM RLC entity after the UM or AM RLC entity has been suspended.
+
+### **CRLC-STATUS-Ind**
+
+It is used by an RLC entity to send status information to upper layers.
+
+## **8.2 Primitive parameters**
+
+Following parameters are used in the primitives:
+
+- 1) The parameter **Data** is the RLC SDU that is mapped onto the Data field in RLC PDUs. When AM or UM RLC entities are used, the length of the Data parameter is a multiple of 8 bits, otherwise (TM RLC entity) the length of Data parameter is a bit-string whose length may not be a multiple of 8 bits.
+- 2) The parameter **Confirmation Request (CNF)** indicates whether the transmitting side of the AM RLC entity needs to confirm the reception of the RLC SDU by the peer-RLC AM entity. If required, once all AMD PDUs that make up the RLC SDU are positively acknowledged by the receiving AM RLC entity, the transmitting AM RLC entity notifies upper layers.
+- 3) The parameter **Message Unit Identifier (MUI)** is an identity of the RLC SDU, which is used to indicate which RLC SDU that is confirmed with the RLC-AM-DATA-Conf. primitive, or discarded with the RLC-AM/UM/TM-DATA-Conf. Primitive.
+- 4) The parameter **E/R** indicates establishment, re-establishment, release or modification of an RLC entity, where re-establishment is applicable to AM and UM RLC entities only. If re-establishment is requested, the state variables and configurable parameters are initialised according to subclause 9.7.7. If release is requested, all protocol parameters, variables and timers are released and the RLC entity enters the NULL state. If modification is requested, the protocol parameters indicated by upper layers (e.g. ciphering parameters) are only modified, while keeping the other protocol parameters, such as the protocol variables, protocol timers and protocol state unchanged. AM RLC entities are always re-established if any of the uplink or downlink AMD PDU size is changed. The modification of other protocol parameters does not require a re-establishment.
+- 5) The parameter **Event Code (EVC)** indicates the reason for the CRLC-STATUS-Ind e.g., unrecoverable errors such as data link layer loss or recoverable status events such as reset.
+- 6) The parameter **Ciphering Elements** are only applicable for UM and AM operations. These parameters are Ciphering Mode, Ciphering Key, Transmitting Activation Time (Sequence Number to activate a new ciphering configuration at the Sender), Receiving Activation Time (Sequence Number to activate a new ciphering configuration at the Receiver) and HFN (Hyper Frame Number).
+- 7) The **AM\_parameters** are only applicable for AM operation. These parameters are AMD PDU size, which can be either a fixed value or set to flexible size, largest UL AMD PDU size (only used when flexible PDU size is configured by upper layers, see subclause 9.2.2.8), Length Indicator Size, In-sequence Delivery Indication (indicating that RLC SDUs are delivered to upper layers in sequence or that they can be delivered out of sequence), Timer values (see subclause 9.5), Use of a special value of the HE field (see subclause 9.2.2.7), Protocol parameter values (see subclause 9.6), Polling triggers (see subclause 9.7.1), Status triggers (see subclause 9.7.2), Periodical Status blocking configuration (see subclause 9.7.2), SDU discard mode (see subclause 9.7.3), Minimum WSN (see subclause 9.2.2.11.3), and Send MRW. The Minimum WSN is always greater than or equal to the number of transport blocks in the smallest transport block set. The Send MRW indicates that the information of each discarded RLC SDU is sent to the Receiver, and the MRW SUFI is sent to the Receiver even if no segments of the RLC SDU to be discarded were submitted to a lower layer.
+- 8) The parameter **DiscardInfo** indicates to upper layer the discarded RLC SDU in the peer-RLC AM entity. It is applicable only when in-sequence delivery is configured and it is to be used when upper layers require the reliable data transfer.
+
+- 9) The Stop parameter is applicable to AM and UM RLC entities only and indicates to the RLC entity to (see subclause 9.7.6):
+- not transmit nor receive any RLC PDUs.
+- 10) The Continue parameter is applicable to AM and UM RLC entities only and indicates to the RLC entity to continue transmission and reception of RLC PDUs.
+- 11) The UM\_parameters are only applicable for UM operation. It contains Timer\_Discard value (see subclause 9.5), use Alternative E-bit interpretation (see subclause 9.2.2.5), largest UL UMD PDU size (see subclause 9.2.2.8), DL RLC UM LI size (see subclause 9.2.2.8) and SN\_Delivery. For a receiving UM RLC in a UE, an additional parameter indicating use/ no use of out of sequence SDU delivery is included (see subclause 11.2.3.2). If out of sequence SDU delivery is used, the parameters OSD\_Window\_Size (see subclause 9.6) and the timeout value of Timer\_OSD (see subclause 9.5) are included. For a receiving UM RLC in a UE, an additional parameter indicating use/ no use of duplicate avoidance and reordering is included (see subclause 9.7.10). If duplicate avoidance and reordering is used, the parameters DAR\_Window\_Size (see subclause 9.6) and the timeout value of Timer\_DAR (see subclause 9.5) are included. If out-of-sequence support is configured, the parameter Configured\_Rx\_Window\_Size is included. If SN\_Delivery parameter is configured, the receiving RLC entity delivers an RLC SDU with Sequence\_Number to the upper layers. When SN\_Delivery parameter is configured, the DL transmitting RLC entity should neither concatenate nor segment RLC SDUs, the UL transmitting RLC entity shall not concatenate RLC SDUs and may segment RLC SDUs.
+- 12) The TM\_parameters are only applicable for TM operation. It contains e.g. segmentation indication (see subclauses 9.2.2.9 and 11.1.2.1), Timer\_Discard value (see subclause 9.5) and delivery of erroneous SDU indication (see subclause 11.1.3).
+- 13) The N parameter indicates that an RLC entity will not send a PDU with "Sequence Number">=VT(S)+N for AM and "Sequence Number">=VT(US)+N for UM, where N is a non-negative integer.
+- 14) The VT(S) parameter indicates the value of the Send State Variable for the case of the AM.
+- 15) The VT(US) parameter indicates the value of the UM Data State Variable, for the case of the UM.
+- 16) The Error\_Indicator parameter indicates that the RLC SDU is erroneous (see subclause 11.1.3).
+- 17) The parameter UE-ID type indicator indicates the RNTI type (U-RNTI or C-RNTI) to be used for the associated RLC SDU. This parameter is not required at the UE.
+- 18) The parameter DiscardReq indicates whether the transmitting RLC entity needs to inform the upper layers of the discarded RLC SDU. If required, the transmitting RLC entity notifies upper layers when the SDU is discarded.
+- 19) The parameter Status is only applicable for AM operation. This parameter indicates whether a RLC SDU is successfully transmitted or discarded.
+- 20) The parameter Sequence\_Number is the value that is mapped onto the Sequence Number (SN) field in an RLC PDU. It is applicable only for UM operation when SN\_Delivery is configured for the UMD RLC entity.
+- 21) The parameter Minimum UL PDU size is applicable for AM and UM operation in the uplink. The Minimum UL PDU size determines the smallest size of the RLC AMD or UMD PDU after segmentation or concatenation (see section 9.2.2.9). If data to be transmitted is not enough to create a PDU of the minimum size, it is allowed to create a PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size.
+
+# --- 9 Elements for peer-to-peer communication
+
+## 9.1 Protocol data units
+
+The structures defined in this subclause are normative.
+
+### 9.1.1 Data PDUs
+
+- a) TMD PDU (Transparent Mode Data PDU).
+
+The TMD PDU is used to convey RLC SDU data without adding any RLC overhead. The TMD PDU is used by RLC when it is in transparent mode.
+
+#### b) UMD PDU (Unacknowledged Mode Data PDU).
+
+The UMD PDU is used to convey sequentially numbered PDUs containing RLC SDU data. UMD PDUs are used by RLC when it is configured for unacknowledged data transfer.
+
+#### c) AMD PDU (Acknowledged Mode Data PDU).
+
+The AMD PDU is used to convey sequentially numbered PDUs containing RLC SDU data. AMD PDUs are used by RLC when it is configured for acknowledged data transfer.
+
+### 9.1.2 Control PDUs
+
+Control PDUs are only used in acknowledged mode.
+
+#### a) STATUS PDU and Piggybacked STATUS PDU.
+
+The STATUS PDU and the Piggybacked STATUS PDU are used:
+
+- by the Receiver to inform the Sender about missing and received AMD PDUs in the Receiver;
+- by the Receiver to inform the Sender about the size of the allowed transmission window;
+- by the Sender to request the Receiver to move the reception window; and
+- by the Receiver to acknowledge the Sender about the reception of the request to move the reception window.
+
+#### b) RESET PDU.
+
+The RESET PDU is used to reset all protocol states, protocol variables and protocol timers of the peer RLC entity in order to synchronise the two peer entities. It is sent by the Sender to the Receiver.
+
+#### c) RESET ACK PDU.
+
+The RESET ACK PDU is an acknowledgement to the RESET PDU. It is sent by the Receiver to the Sender.
+
+**Table 9.1: RLC PDU names and descriptions**
+
+| Data Transfer Mode | PDU name | Description |
+|-----------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| Transparent | TMD | Transparent mode data |
+| Unacknowledged | UMD | Sequenced unacknowledged mode data |
+| Acknowledged | AMD | Sequenced acknowledged mode data |
+| | STATUS | Solicited or Unsolicited Status Report, Change window size command, SDU discard command, or SDU discard acknowledgement |
+| | Piggybacked STATUS | Piggybacked Solicited or Unsolicited Status Report, Change window size command, SDU discard command, or SDU discard acknowledgement |
+| | RESET | Reset Command |
+| | RESET ACK | Reset Acknowledgement |
+
+## 9.2 Formats and parameters
+
+The formats of RLC PDUs and their parameters defined in this subclause are normative.
+
+### 9.2.1 Formats
+
+This subclause specifies the format of the RLC PDUs. The parameters of each RLC PDU are explained in subclause 9.2.2.
+
+#### 9.2.1.1 General
+
+An RLC PDU is a bit string. In the figures in subclause 9.2, bit strings are represented by tables in which the first bit is the leftmost one on the first line of the table, the last bit is the rightmost one on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines.
+
+Depending on the provided service, RLC SDUs are bit strings, with any non-null length, or bit strings with a multiple of 8 bits in length. An RLC SDU is included into an RLC PDU from first bit onward.
+
+#### 9.2.1.2 TMD PDU
+
+The TMD PDU is used to transfer user data when RLC is operating in transparent mode. No overhead is added to the SDU by RLC. The data length is not constrained to be a multiple of 8 bits.
+
+
+
+| |
+|------|
+| Data |
+|------|
+
+**Figure 9.1: TMD PDU**
+
+#### 9.2.1.3 UMD PDU
+
+The UMD PDU is used to transfer user data when RLC is operating in unacknowledged mode. The length of the data part shall be a multiple of 8 bits. The UMD PDU header consists of the first octet, which contains the "Sequence Number". The RLC header consists of the first octet and all the octets that contain "Length Indicators".
+
+
+
+| | | |
+|------------------|---|----------------|
+| Sequence Number | E | Oct1 |
+| Length Indicator | E | (Optional) (1) |
+| ⋮ | | |
+| Length Indicator | E | (Optional) |
+| Data | | |
+| PAD | | (Optional) |
+| | | Last Octet |
+
+**Figure 9.2: UMD PDU**
+
+NOTE (1): The "Length Indicator" may be 15 bits.
+
+#### 9.2.1.4 AMD PDU
+
+The AMD PDU is used to transfer user data, piggybacked status information and the Polling bit when RLC is operating in acknowledged mode. The length of the data part shall be a multiple of 8 bits. The AMD PDU header consists of the
+
+first two octets, which contain the "Sequence Number". The RLC header consists of the first two octets and all the octets that contain "Length Indicators".
+
+
+
+| | | | | |
+|---------------------------------|-----------------|---|----|---------------------|
+| D/C | Sequence Number | | | Oct1 |
+| Sequence Number | | P | HE | Oct2 |
+| Length Indicator | | | E | Oct3 (Optional) (1) |
+| ⋮ | | | | |
+| Length Indicator | | | E | |
+| Data | | | | |
+| PAD or a piggybacked STATUS PDU | | | | OctN |
+
+**Figure 9.3: AMD PDU**
+
+NOTE (1): The "Length Indicator" may be 15 bits.
+
+#### 9.2.1.5 STATUS PDU
+
+The STATUS PDU is used to exchange status information between two RLC AM entities.
+
+The format of the STATUS PDU is given in figure 9.4 below. The length of each super field (SUF) is dependent on its type and contents.
+
+
+
+| | | | |
+|------------------|----------|------------------|-------|
+| D/C | PDU type | SUF 1 | Oct 1 |
+| SUF 1 | | | Oct2 |
+| ⋮ | | | |
+| SUF k | | | |
+| PAD | | | OctN |
+
+**Figure 9.4: STATUS PDU**
+
+A STATUS PDU can include super-fields of different types. The size of a STATUS PDU is variable and upper bounded by the maximum RLC PDU size used by the logical channel on which the control PDUs are sent. If fixed RLC PDU size has been configured by upper layers, padding shall be included to match one of the PDU sizes used by the logical channel on which the control PDUs are sent. The length of the STATUS PDU shall be a multiple of 8 bits. If flexible RLC PDU size has been configured by upper layers padding is only included to make the length of the STATUS PDU a multiple of 8 bits.
+
+#### 9.2.1.6 Piggybacked STATUS PDU
+
+The format of the piggybacked STATUS PDU is the same as for the STATUS PDU except that the D/C field is replaced by a reserved bit (R2). This PDU can be piggybacked in an AMD PDU if the data leaves out enough room in the AMD PDU. The PDU Type field is set to "000" and all other values are invalid for this version of the protocol.
+
+
+
+| | | | |
+|-------------------|----------|-------------------|------|
+| R2 | PDU Type | SUFI 1 | Oct1 |
+| SUFI 1 | | | Oct2 |
+| ... | | | |
+| SUFI k | | | |
+| PAD | | | OctN |
+
+**Figure 9.5: Piggybacked STATUS PDU**
+
+#### 9.2.1.7 RESET, RESET ACK PDU
+
+The RESET PDU includes a one-bit sequence number field (RSN). The value of this bit is carried over in the RESET ACK PDU sent in response in order to allow the peer entity to identify which RESET PDU it was sent in response to.
+
+
+
+| | | | | |
+|------|----------|-----|----|------|
+| D/C | PDU Type | RSN | R1 | Oct1 |
+| HFNI | | | | |
+| HFNI | | | | |
+| HFNI | | | | |
+| PAD | | | | OctN |
+
+**Figure 9.6: RESET, RESET ACK PDU**
+
+The size of a RESET or RESET ACK PDU is variable and upper bounded by the maximum RLC PDU size used by the logical channel on which the control PDUs are sent. If fixed RLC PDU size has been configured by upper layers, padding shall be included to match one of the PDU sizes used by the logical channel on which the control PDUs are sent. The length of the RESET or RESET ACK PDU shall be a multiple of 8 bits. If flexible RLC PDU size has been configured by upper layers padding is only included to make the length of the RESET or RESET ACK PDU a multiple of 8 bits.
+
+### 9.2.2 Parameters
+
+If not otherwise mentioned in the definition of each field, the bits in the parameters shall be interpreted as follows: the left-most bit string is the first and most significant and the right most bit is the last and least significant bit.
+
+Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases, including when a value extends over more than one octet as shown in the tables, the bits appear ordered from MSB to LSB when read in the RLC PDU.
+
+#### 9.2.2.1 D/C field
+
+Length: 1bit.
+
+The D/C field indicates the type of an AM PDU. It can be either data or control PDU.
+
+| Bit | Description |
+|-----|-------------|
+| 0 | Control PDU |
+| 1 | Data PDU |
+
+#### 9.2.2.2 PDU Type
+
+Length: 3 bit.
+
+The PDU type field indicates the Control PDU type.
+
+| Bit | PDU Type |
+|---------|----------------------------------------------------------------------------------------|
+| 000 | STATUS |
+| 001 | RESET |
+| 010 | RESET ACK |
+| 011-111 | Reserved
(PDUs with this coding will be discarded by this version of the protocol). |
+
+#### 9.2.2.3 Sequence Number (SN)
+
+This field indicates the "Sequence Number" of the RLC PDU, encoded in binary.
+
+| PDU type | Length | Notes |
+|----------|---------|----------------------------------------|
+| AMD PDU | 12 bits | Used for retransmission and reassembly |
+| UMD PDU | 7 bits | Used for reassembly |
+
+#### 9.2.2.4 Polling bit (P)
+
+Length: 1bit.
+
+This field is used to request a status report (one or several STATUS PDUs) from the Receiver.
+
+| Bit | Description |
+|-----|-----------------------------|
+| 0 | Status report not requested |
+| 1 | Request a status report |
+
+#### 9.2.2.5 Extension bit (E)
+
+Length: 1bit.
+
+The interpretation of this bit depends on RLC mode and higher layer configuration:
+
+- In the UMD PDU, the "Extension bit" in the first octet has either the normal E-bit interpretation or the alternative E-bit interpretation depending on higher layer configuration. The "Extension bit" in all the other octets always has the normal E-bit interpretation.
+- In the AMD PDU, the "Extension bit" always has the normal E-bit interpretation.
+
+**Normal E-bit interpretation:**
+
+| Bit | Description |
+|-----|-----------------------------------------------------------|
+| 0 | The next field is data, piggybacked STATUS PDU or padding |
+| 1 | The next field is Length Indicator and E bit |
+
+Alternative E-bit interpretation:
+
+| Bit | Description |
+|-----|-----------------------------------------------------------------------------------|
+| 0 | The next field is a complete SDU, which is not segmented, concatenated or padded. |
+| 1 | The next field is Length Indicator and E bit |
+
+#### 9.2.2.6 Reserved 1 (R1)
+
+Length: 3 bits.
+
+This field in the RESET PDU and RESET ACK PDU is used to have a multiple of 8 bits in length. It shall always be coded to "000". Other values are reserved and will be considered invalid for this version of the protocol.
+
+#### 9.2.2.7 Header Extension Type (HE)
+
+Length: 2 bits.
+
+This two-bit field indicates if the next octet is data or a "Length Indicator" and E bit.
+
+| Value | Description |
+|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 00 | The succeeding octet contains data |
+| 01 | The succeeding octet contains a length indicator and E bit |
+| 10 | This value is the special value of HE field and indicates that the succeeding octet contains data and the last octet of the PDU is the last octet of an SDU. |
+| 11 | Reserved (PDUs with this coding will be discarded by this version of the protocol). |
+
+#### 9.2.2.8 Length Indicator (LI)
+
+Unless the "Extension bit" indicates that a UMD PDU contains a complete SDU which is not segmented, concatenated or padded, or the HE field indicates that an AMD PDU contains the last octet of the RLC SDU, a "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU. If the "Extension bit" indicates that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded, or the HE field indicates that an AMD PDU contains the last octet of the SDU, no LIs are present in this RLC PDU.
+
+Except for the predefined values reserved for special purposes and listed in the tables below, the "Length Indicator" shall:
+
+- be set to the number of octets between the end of the RLC header and up to and including the last octet of an RLC SDU segment;
+- be included in the PDUs that they refer to.
+
+The size of the "Length Indicator" may be either 7 bits or 15 bits. The "Length Indicator" size is determined independently for uplink and downlink. The value of a "Length Indicator" shall not exceed the values specified in subclauses 11.2.4.2 and 11.3.4.5 respectively for UMD and AMD PDUs.
+
+The "Length Indicators" which refer to the same PDU shall:
+
+- not be reordered in case of retransmission;
+- be in the same order as the RLC SDUs that they refer to.
+
+For AM uplink and for AM downlink when "Fixed RLC PDU size" is configured:
+
+- if the "AMD PDU size" is $\leq 126$ octets:
+ - 7-bit "Length Indicators" shall be used.
+- else:
+ - 15-bit "Length Indicators" shall be used.
+- the size of the "Length Indicator" is always the same for all AMD PDUs, for one RLC entity.
+
+For AM downlink and AM uplink when "Flexible RLC PDU size" is configured:
+
+- if "Length Indicator size" is set to 7 bits:
+ - 7-bit "Length Indicators" shall be used.
+- else:
+ - 15-bit "Length Indicators" shall be used.
+
+For UM uplink:
+
+- if the "largest UL UMD PDU size" is $\leq 125$ octets:
+ - 7-bit "Length Indicators" shall be used.
+- else:
+ - 15-bit "Length Indicators" shall be used.
+
+For UM downlink:
+
+- the "Length Indicator" size provided in "DL RLC UM LI size" shall be used.
+
+For UM:
+
+- between modifications of the "largest UMD PDU size", the size of the "Length Indicator" is the same for all UMD PDUs;
+- if the RLC SDU begins in the beginning of the RLC PDU; and
+- if the RLC PDU is transmitted in uplink; and
+- if the "Length Indicators" indicating that a RLC SDU ended exactly in the end or one octet short (only when 15-bit "Length Indicators" is used) of the previous RLC PDU are not present; and
+- if the "Extension bit" does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded; and
+- if the "Length Indicator" indicating that the first data octet in this RLC PDU is the first octet of an RLC SDU and the last octet in this RLC PDU is the last octet of the same RLC SDU is not present; and
+- if the "Length Indicator" indicating that the first data octet in this RLC PDU is the first octet of an SDU and the same RLC SDU is one octet short of exactly filling the PDU (only when 15-bit "Length Indicators" is used) is not present:
+ - if 7-bit "Length Indicator" is used:
+ - the "Length Indicator" with value "111 1100" shall be used.
+ - if 15-bit "Length Indicator" is used:
+ - the "Length Indicator" with value "111 1111 1111 1100" shall be used.
+- in downlink:
+ - if 7-bit "Length Indicator" is used:
+
+- the Receiver shall be prepared to receive the "Length Indicator" with value "111 1100";
+- the Receiver shall follow the discard rules in subclause 11.2.3 both when the "Length Indicator" with value "111 1100" is present and when it is absent.
+- if 15-bit "Length Indicator" is used:
+ - the Receiver shall be prepared to receive the "Length Indicator" with value "111 1111 1111 1100";
+ - the Receiver shall follow the discard rules in subclause 11.2.3 both when the "Length Indicator" with value "111 1111 1111 1100" is present and when it is absent.
+
+In the case where the end of the last segment of an RLC SDU exactly ends at the end of a PDU and there is no "Length Indicator" that indicates the end of the RLC SDU, and the HE field of the PDU does not indicate that the last octet of the AMD PDU is the last octet of an SDU, and the "Extension bit" of the following PDU does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded, and the "Length Indicator" of the following PDU does not indicate that the first data octet in that PDU is the first octet of an SDU and the last octet in that PDU is the last octet of the same SDU, and the "Length Indicator" of the following PDU does not indicate that the first data octet in that RLC PDU is the first octet of an SDU and the same RLC SDU is one octet short of exactly filling the PDU (only when 15-bit "Length Indicators" is used):
+
+- if 7-bit "Length Indicator" is used:
+ - a "Length Indicator" with value "000 0000" shall be placed as the first "Length Indicator" in the following PDU;
+- if 15-bit "Length Indicator" is used:
+ - a "Length Indicator" with value "000 0000 0000 0000" shall be placed as the first "Length Indicator" in the following PDU.
+
+In the case where a PDU contains a 15-bit "Length Indicator" indicating that an RLC SDU ends with one octet left in the PDU, the last octet of this PDU shall:
+
+- be padded by the Sender and ignored by the Receiver though there is no "Length Indicator" indicating the existence of Padding; and
+- not be filled with the first octet of the next RLC SDU data.
+
+In the case where 15-bit "Length Indicators" are used in a PDU and the last segment of an RLC SDU is one octet short of exactly filling the PDU and there is no "Length Indicator" that indicates the end of the RLC SDU:
+
+- if a 15-bit "Length Indicator" is used for the following PDU:
+ - the "Length Indicator" with value "111 1111 1111 1011" shall be placed as the first "Length Indicator" in the following PDU;
+ - the remaining one octet in the current PDU shall be padded by the Sender and ignored at the Receiver though there is no "Length Indicator" indicating the existence of Padding;
+- if a 7-bit "Length Indicator" size is configured for the following PDU:
+ - if RLC is configured for UM mode:
+ - if the "Extension bit" of that PDU does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded, and the "Length Indicator" of that PDU does not indicate that the first data octet in that PDU is the first octet of an SDU and the last octet in that PDU is the last octet of the same SDU:
+ - the "Length Indicator" with value "000 0000" shall be placed as the first "Length indicator" in the following PDU;
+ - the "Sequence Number" shall be incremented by 2 before it is transmitted.
+
+For UM and AM RLC:
+
+- if a 7 bit "Length Indicator" is used in a RLC PDU and one or more padding octets are present in the RLC PDU after the end of the last RLC SDU:
+ - indicate the presence of padding by including a "Length Indicator" with value "1111111" as the last "Length Indicator" in the PDU.
+- if a 15 bit "Length Indicator" is used in a RLC PDU and two or more padding octets are present in the RLC PDU after the end of the last RLC SDU:
+ - indicate the presence of padding by including a "Length Indicator" with value "111 1111 1111 1111" as the last "Length Indicator" in the PDU.
+
+NOTE: After the "Length Indicator" indicating the presence of padding has been included in the RLC PDU, the length of the padding may be zero.
+
+In the case where the "alternative E-bit interpretation" is configured for UM RLC and an RLC PDU contains a segment of an SDU but neither the first octet nor the last octet of this SDU:
+
+- if a 7-bit "Length Indicator" is used:
+ - the "Length Indicator" with value "111 1110" shall be used.
+- if a 15-bit "Length Indicator" is used:
+ - the "Length Indicator" with value "111 1111 1111 1110" shall be used.
+
+In the case where the "alternative E-bit interpretation" is configured for UM RLC and the first data octet in this RLC PDU is the first octet of an SDU and the last octet in this RLC PDU is the last octet of the same SDU:
+
+- if a 7-bit "Length Indicator" is used:
+ - the "Length Indicator" with value "111 1101" shall be used.
+- if a 15-bit "Length Indicator" is used:
+ - the "Length Indicator" with value "111 1111 1111 1101" shall be used.
+
+In the case where the "alternative E-bit interpretation" is configured for UM RLC and the first data octet in this RLC PDU is the first octet of an SDU and the same RLC SDU is one octet short of exactly filling the PDU and a 15-bit "Length Indicator" is used:
+
+- the "Length Indicator" with value "111 1111 1111 1010" shall be used.
+
+If a "Length Indicator" is still awaiting transmission and there is no RLC SDU available, an RLC PDU consisting of this "Length Indicator", the appropriate padding "Length Indicator" and padding may be transmitted.
+
+Predefined values of the "Length Indicator" are used to indicate padding. The values that are reserved for special purposes are listed in the tables below depending on the size of the "Length Indicator". Only predefined "Length Indicator" values can refer to the padding space. These values shall only be placed after all other "Length Indicators" for a PDU.
+
+STATUS PDUs can be piggybacked on the AMD PDU by using part or all of the padding space. A predefined "Length Indicator" shall be used to indicate the presence of a piggybacked STATUS PDU. This "Length Indicator" replaces the padding "Length Indicator". The piggybacked STATUS PDU shall be appended immediately following the PDU data. When only part of the padding space is used, the end of the piggybacked STATUS PDU is indicated by one of the SUFI fields NO\_MORE or ACK. Thus no additional "Length Indicator" is required to show that there is still padding in the AMD PDU.
+
+If "SDU discard with explicit signalling" is configured:
+
+- an AMD PDU can contain a maximum number of 15 "Length Indicators" indicating the end of 15 corresponding SDUs; and
+- the rest of the AMD PDU space shall be used as padding or as piggybacked STATUS PDU.
+
+Length: 7 bits
+
+| Bit | Description |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0000000 | The previous RLC PDU was exactly filled with the last segment of an RLC SDU and there is no "Length Indicator" that indicates the end of the RLC SDU in the previous RLC PDU. |
+| 1111100 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). |
+| 1111101 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU and the last octet in this RLC PDU is the last octet of the same RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). |
+| 1111110 | AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU. UMD PDU: The RLC PDU contains a segment of an SDU but neither the first octet nor the last octet of this SDU. |
+| 1111111 | The rest of the RLC PDU is padding. The padding length can be zero. |
+
+Length: 15bits
+
+| Bit | Description |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 000000000000000 | The previous RLC PDU was exactly filled with the last segment of an RLC SDU and there is no "Length Indicator" that indicates the end of the RLC SDU in the previous RLC PDU. |
+| 111111111111010 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU and the second last octet in this RLC PDU is the last octet of the same RLC SDU. The remaining one octet in the RLC PDU is ignored. |
+| 111111111111011 | The last segment of an RLC SDU was one octet short of exactly filling the previous RLC PDU and there is no "Length Indicator" that indicates the end of the RLC SDU in the previous RLC PDU. The remaining one octet in the previous RLC PDU is ignored. |
+| 111111111111100 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). |
+| 111111111111101 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU and the last octet in this RLC PDU is the last octet of the same RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). |
+| 111111111111110 | AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU. UMD PDU: The RLC PDU contains a segment of an SDU but neither the first octet nor the last octet of this SDU. |
+| 111111111111111 | The rest of the RLC PDU is padding. The padding length can be zero. |
+
+#### 9.2.2.9 Data field
+
+RLC SDUs or segments of RLC SDUs are mapped to this field in transparent, unacknowledged and acknowledged modes.
+
+Transparent mode data:
+
+- the length of RLC SDUs is not constrained to a multiple of 8 bits;
+- if "Segmentation" is configured:
+ - all the RLC PDUs carrying segments of a RLC SDU shall be sent in one TTI;
+ - only RLC PDUs carrying segments from a single RLC SDU shall be sent in one TTI;
+- otherwise (Segmentation is not configured):
+ - TMD PDU size is fixed within a single TTI and is equal to the RLC SDU size.
+
+Unacknowledged mode data and Acknowledged mode data:
+
+- the length of RLC SDUs is constrained to a multiple of 8 bits;
+- if "Fixed RLC PDU size" is configured:
+ - the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field completely and avoid unnecessary padding unless otherwise specified in subclause 9.2.2.8 or subclause 11.2.2.2. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8).
+- if "Flexible RLC PDU size" is configured:
+ - in downlink, the last segment of an RLC SDU may be concatenated with the first segment of the next RLC SDU in order to fill the data field up to a maximum RLC PDU size. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8).
+ - in uplink, the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. It is allowed to concatenate up to the largest UL AMD PDU size for Acknowledged mode data and largest UMD PDU size for Unacknowledged mode data. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8). If data to be transmitted is not enough to create a UMD PDU of the minimum size, it is allowed to create a UMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size.
+ - in uplink, if MAC-i/is has been configured:
+ - if the UE pre-generates RLC PDUs for transmission in a later TTI and there is only one activated uplink frequency:
+ - provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen so that each RLC PDU to be multiplexed to the MAC-i/is PDU matches the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI.
+ - RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to four times the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI.
+ - else if the UE pre-generates RLC PDUs for transmission in a later TTI and there are two activated uplink frequencies for FDD or more than one scheduled uplink frequencies for 1.28 Mcps TDD:
+ - provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen so that each RLC PDU to be multiplexed to the MAC-i/is PDU matches the minimum of the following:
+ - For FDD,
+ - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) on the primary uplink frequency for the current TTI.
+ - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) on the secondary uplink frequency for the current TTI.
+ - For 1.28 Mcps TDD,
+ - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) on the each scheduled uplink frequency for the current TTI.
+ - For FDD, RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to eight times the minimum of the following:
+ - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) on the primary uplink frequency for the current TTI.
+
+- maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) on the secondary uplink frequency for the current TTI.
+- For 1.28 Mcps TDD, RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to 4N times the minimum of the following:
+ - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) of each uplink frequency for the current TTI.
+
+NOTE: N is the number of configured uplink frequencies.
+
+- else:
+ - the size of the data field of the RLC PDU shall be chosen so that the RLC PDU size matches the data requested for this logical channel by the current E-TFC selection.
+- if "Flexible RLC PDU size" is configured, the maximum size of the data field of the RLC PDU is 1503 octets.
+
+#### 9.2.2.10 Padding (PAD)
+
+All unused space in a PDU shall be located at the end of the PDU and is referred to as padding. Padding shall have a length such that the PDU as a whole has one of the predefined total lengths.
+
+Padding may have any value and the Receiver and the Sender shall disregard it.
+
+#### 9.2.2.11 SUFI
+
+Which SUFI fields to use is implementation dependent, but when a STATUS PDU includes information about which AMD PDUs have been received and which are detected as missing, information shall not be included about AMD PDUs with "Sequence Number" $\ge VR(H)$ or "Sequence Number" $\ge VR(MR)$ , i.e. AMD PDUs that have not yet reached the Receiver or are above the receiving window. Information about AMD PDUs with "Sequence Number" $< VR(R)$ shall not be given except when this is necessary in order to use the BITMAP SUFI, see subclause 9.2.2.11.5.
+
+Length: variable number of bits.
+
+The SUFI can include three sub-fields: type information (type of super-field, e.g. list, bitmap, acknowledgement, etc), length information (providing the length of a variable length field within the following value field) and a value.
+
+Figure 9.7 shows the structure of the super-field. The size of the type sub-field is non-zero but the size of the other sub-fields may be zero.
+
+| |
+|--------|
+| Type |
+| Length |
+| Value |
+
+**Figure 9.7: The Structure of a Super-Field**
+
+The length of the type field is 4 bits and it may have any of following values.
+
+| Bit | Description |
+|-----------|---------------------------------------------------------------------------------|
+| 0000 | No More Data ( NO_MORE ) |
+| 0001 | Window Size ( WINDOW ) |
+| 0010 | Acknowledgement ( ACK ) |
+| 0011 | List ( LIST ) |
+| 0100 | Bitmap ( BITMAP ) |
+| 0101 | Relative list ( Rlist ) |
+| 0110 | Move Receiving Window ( MRW ) |
+| 0111 | Move Receiving Window Acknowledgement ( MRW_ACK ) |
+| 1000 | Poll ( POLL ) |
+| 1001-1111 | Reserved (PDUs with this encoding are invalid for this version of the protocol) |
+
+The size and presence of the sub-fields "Length" and "Value" depend on the super-field type and is specified for each super field separately.
+
+##### 9.2.2.11.1 The No More Data super-field
+
+The 'No More Data' super-field indicates the end of the data part of a STATUS PDU and is shown in Figure 9.8 below. It shall always be placed as the last SUFI if it is included in a STATUS PDU. All data after this SUFI shall be regarded as padding and shall be neglected.
+
+| |
+|----------------------|
+| Type= NO_MORE |
+|----------------------|
+
+**Figure 9.8: NO\_MORE field in a STATUS PDU**
+
+##### 9.2.2.11.2 The Acknowledgement super-field
+
+The 'Acknowledgement' super-field consists of a type identifier field (ACK) and a sequence number (LSN) as shown in figure 9.9 below. The acknowledgement super-field is also indicating the end of the data part of a STATUS PDU. Thus, no 'NO\_MORE' super-field is needed in the STATUS PDU when the 'ACK' super-field is present. The ACK SUFI shall always be placed as the last SUFI if it is included in a STATUS PDU. All data after this SUFI shall be regarded as padding and shall be neglected.
+
+| |
+|-------------------|
+| Type = ACK |
+| LSN |
+
+**Figure 9.9: The ACK fields in a STATUS PDU**
+
+###### LSN
+
+Length: 12 bits
+
+Acknowledges the reception of all AMD PDUs with "Sequence Number" < LSN (Last Sequence Number) that are *not* indicated to be erroneous in earlier parts of the STATUS PDU. This means that if the LSN is set to a value greater than VR(R), all erroneous AMD PDUs shall be included in the same STATUS PDU and if the LSN is set to VR(R), the erroneous AMD PDUs can be split into several STATUS PDUs. At the transmitter, if the value of the LSN =< the value of the first error indicated in the STATUS PDU, VT(A) will be updated according to the LSN, otherwise VT(A) will be updated according to the first error indicated in the STATUS PDU. VT(A) is only updated based on STATUS PDUs where ACK SUFI (or MRW\_ACK SUFI) is included. The LSN shall not be set to a value > VR(H) nor < VR(R).
+
+##### 9.2.2.11.3 The Window Size super-field
+
+The Window Size super-field consists of a type identifier (WINDOW) and a window size number (WSN) as shown in Figure 9.10 below. The Receiver is always allowed to change the transmission window size of the peer entity during a connection, but the minimum and the maximum allowed value is given by upper layers configuration. The reception window size of the Receiver is not changed.
+
+| |
+|----------------------|
+| Type = WINDOW |
+| WSN |
+
+**Figure 9.10: The WINDOW fields in a STATUS PDU**
+
+###### WSN
+
+Length: 12 bits
+
+The value of VT(WS) to be used by the transmitter. The range of the WSN is [0, 212-1]. The minimum value of VT(WS) is 1. If WSN is zero the SUFI shall be discarded by this version of the protocol. The variable VT(WS) is set equal to WSN upon reception of this SUFI. If WSN is greater than Configured\_Tx\_Window\_Size, VT(WS) shall be set equal to Configured\_Tx\_Window\_Size.
+
+##### 9.2.2.11.4 The List super-field
+
+The List Super-Field consists of a type identifier field (LIST), a list length field (LENGTH) and a list of LENGTH number of pairs as shown in figure 9.11 below:
+
+| |
+|----------------------|
+| Type = LIST |
+| LENGTH |
+| SN 1 |
+| L 1 |
+| SN 2 |
+| L 2 |
+| ... |
+| SN LENGTH |
+| L LENGTH |
+
+Figure 9.11: The List fields in a STATUS PDU
+
+###### LENGTH
+
+Length: 4 bits
+
+The number of (SNi, Li)-pairs in the super-field of type LIST. The value "0000" is invalid and the STATUS PDU is discarded.
+
+###### SNi
+
+Length: 12 bits
+
+"Sequence Number" of AMD PDU, which was not correctly received.
+
+###### Li
+
+Length: 4 bits
+
+Number of consecutive AMD PDUs not correctly received following AMD PDU with "Sequence Number" SNi.
+
+##### 9.2.2.11.5 The Bitmap super-field
+
+The Bitmap Super-Field consists of a type identifier field (BITMAP), a bitmap length field (LENGTH), a first sequence number (FSN) and a bitmap as shown in figure 9.12 below:
+
+| |
+|----------------------|
+| Type = BITMAP |
+| LENGTH |
+| FSN |
+| Bitmap |
+
+Figure 9.12: The Bitmap fields in a STATUS PDU
+
+###### LENGTH
+
+Length: 4 bits
+
+The size of the bitmap in octets equals LENGTH+1, i.e. LENGTH="0000" means that the size of the bitmap is one octet and LENGTH="1111" gives the maximum bitmap size of 16 octets.
+
+###### FSN
+
+Length: 12 bits
+
+The "Sequence Number" for the first bit in the bitmap. FSN shall not be set to a value lower than VR(R)-7 when the reception window size is less than half the maximum RLC AM "Sequence Number". If the reception window size is larger, FSN shall not be set to a value lower than VR(R).
+
+###### Bitmap
+
+Length: Variable number of octets given by the LENGTH field.
+
+Status of the "Sequence Number" fields in the interval $[FSN, FSN + (LENGTH+1)*8 - 1]$ indicated in the bitmap where each position (from left to right) can have two different values (0 and 1) with the following meaning ( $bit\_position \in [0, (LENGTH+1)*8 - 1]$ ):
+
+1: Sequence Number = (FSN + bit\_position) has been correctly received.
+
+0: Sequence Number = (FSN + bit\_position) has not been correctly received.
+
+The UE may remove AMD PDUs from the transmitter that have been indicated to be correctly received by a BITMAP SUFI.
+
+NOTE: The transmission window is not advanced based on BITMAP SUFIs, see subclause 9.4.
+
+##### 9.2.2.11.6 The Relative List super-field
+
+The Relative List super-field consists of a type identifier field (RLIST), a list length field (LENGTH), the first sequence number (FSN) and a list of LENGTH number of codewords (CW) as shown in figure 9.13 below.
+
+| |
+|----------------------|
+| Type = RLIST |
+| LENGTH |
+| FSN |
+| CW 1 |
+| CW 2 |
+| ... |
+| CW LENGTH |
+
+Figure 9.13: The RList fields in a STATUS PDU
+
+###### LENGTH
+
+Length: 4 bits
+
+The number of codewords (CW) in the super-field of type RLIST.
+
+###### FSN
+
+Length: 12 bits
+
+The "Sequence Number" for the first erroneous AMD PDU in the RLIST, i.e. LENGTH="0000" means that only FSN is present in the SUFI.
+
+###### CW
+
+Length: 4 bits
+
+The CW consists of 4 bits where the three first bits are part of a number and the last bit is a status indicator and it shall be interpreted as follows:
+
+| Code Word | Description |
+|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| X1X2X3 0 | Next 3 bits of the number are X 1 X 2 X 3 and the number continues in the next CW. The most significant bit within this CW is X 1 . |
+| X1X2X3 1 | Next 3 bits of the number are X 1 X 2 X 3 and the number is terminated. The most significant bit within this CW is X 1 . This is the most significant CW within the number. |
+
+By default, the number given by the CWs represents a distance between the previous indicated erroneous AMD PDU up to and including the next erroneous AMD PDU.
+
+One special value of CW is defined:
+
+**000 1** 'Error burst indicator'.
+
+The error burst indicator means that the next CWs will represent the number of subsequent erroneous AMD PDUs (not counting the already indicated error position). After the number of errors in a burst is terminated with XXX 1, the next codeword will again by default be the least significant bits (LSB) of the distance to the next error.
+
+If the last CW, as indicated by the value of the LENGTH field, does not contain a "1" in its rightmost position, or the last CW, as indicated by the value of the LENGTH field does contain a "1" in its rightmost position, but is a special "error burst indicator" CW, the encoding of the RLIST SUFI is invalid, and the STATUS PDU is discarded.
+
+##### 9.2.2.11.7 The Move Receiving Window Acknowledgement super-field
+
+The 'Move Receiving Window Acknowledgement' super-field acknowledges the reception of a MRW SUFI. The format is given in figure 9.14 below.
+
+| |
+|-----------------------|
+| Type = MRW_ACK |
+| N |
+| SN_ACK |
+
+Figure 9.14: The MRW\_ACK fields in a STATUS PDU
+
+N
+
+Length: 4 bits
+
+The N field shall be set equal to the NLENGTH field in the received MRW SUFI if the SN\_ACK field is equal to the SN\_MRLENGTH field. Otherwise N shall be set to 0.
+
+With the aid of this field in combination with the SN\_ACK field, it can be determined if the MRW\_ACK corresponds to a previously transmitted MRW SUFI.
+
+SN\_ACK
+
+Length: 12 bits
+
+The SN\_ACK field indicates the updated value of VR(R) after the reception of the MRW SUFI. With the aid of this field in combination with the N field, it can be determined if the MRW\_ACK corresponds to a previously transmitted MRW SUFI.
+
+##### 9.2.2.11.8 The Move Receiving Window (MRW) super-field
+
+The 'Move Receiving Window' super-field is used to request the Receiver to move its reception window and optionally to indicate the set of discarded RLC SDUs, as a result of an RLC SDU discard in the Sender. The format is given in figure 9.15 below.
+
+| |
+|--------------------------|
+| Type = MRW |
+| LENGTH |
+| SN_MR W1 |
+| SN_MR W2 |
+| ... |
+| SN_MR WLENGTH |
+| N LENGTH |
+
+Figure 9.15: The MRW fields in a STATUS PDU
+
+LENGTH
+
+Length: 4 bits
+
+The number of SN\_MRWi fields in the super-field of type MRW.
+
+The values "0001" through "1111" indicate 1 through 15 SN\_MRWi respectively. The value "0000" indicates that one SN\_MRWi field is present and that the RLC SDU to be discarded in the Receiver extends above the configured transmission window in the Sender.
+
+SN\_MRWi
+
+Length: 12 bits
+
+When "Send MRW" is configured, an $SN\_MRW_i$ shall be used to indicate the end of each discarded RLC SDU, i.e. the number of $SN\_MRW_i$ fields shall equal the number of RLC SDUs discarded by that MRW SUFI. When "Send MRW" is not configured, an $SN\_MRW_i$ field shall be used to indicate the end of the last RLC SDU to be discarded in the Receiver and additional ones may optionally be used to indicate the end of other discarded RLC SDUs. $SN\_MRW_i$ is the "Sequence Number" of the AMD PDU that contains the "Length Indicator" or the special value of the HE field of the i:th RLC SDU to be discarded in the Receiver (except for $SN\_MRW_{LENGTH}$ when $N_{LENGTH} = 0$ , see definition of $N_{LENGTH}$ ). The order of the $SN\_MRW_i$ shall be in the same sequential order as the RLC SDUs that they refer to.
+
+Additionally $SN\_MRW_{LENGTH}$ requests the Receiver to discard all not yet successfully received SDUs that have segments or "Length Indicators" indicating the end of the SDUs in the AMD PDUs with "Sequence Number" $< SN\_MRW_{LENGTH}$ , and to move the reception window accordingly. In addition, when $N_{LENGTH} > 0$ , the Receiver has to discard the not yet successfully received SDUs that have segments or "Length Indicators" indicating the end of the SDUs in the AMD PDU with sequence number $SN\_MRW_{LENGTH}$ up to and including the octet indicated by the $N_{LENGTH}$ :th "Length Indicator" field of the PDU with sequence number $SN\_MRW_{LENGTH}$ .
+
+$N_{LENGTH}$
+
+Length: 4 bits
+
+$N_{LENGTH}$ is used together with $SN\_MRW_{LENGTH}$ to indicate the end of the last RLC SDU to be discarded in the Receiver.
+
+$N_{LENGTH}$ indicates which "Length Indicator" in the AMD PDU with "Sequence Number" $SN\_MRW_{LENGTH}$ corresponds to the last RLC SDU to be discarded in the Receiver. $N_{LENGTH} = 0$ indicates that the end of the last RLC SDU was indicated in the AMD PDU with "Sequence Number" $SN\_MRW_{LENGTH} - 1$ and that the first data octet in the AMD PDU with "Sequence Number" $SN\_MRW_{LENGTH}$ is the first data octet to be reassembled next.
+
+##### 9.2.2.11.9 The Poll (POLL) super-field
+
+The 'Poll' super-field is used to request a status report (one or several STATUS PDUs) from the receiver. The poll super-field in downlink can only be used if flexible RLC PDU size is configured in the downlink. The poll super-field in uplink can only be used if flexible RLC PDU size is configured in the uplink. The format is given in figure 9.15b below.
+
+| |
+|--------------------|
+| Type = POLL |
+| Poll SN |
+
+**Figure 9.15b: The POLL fields in a STATUS PDU**
+
+**Poll\_SN**
+
+Length: 12 bits
+
+When "Poll" is configured, the $Poll\_SN$ field shall be set to $VT(S)-1$ .
+
+#### 9.2.2.12 Reserved 2 (R2)
+
+Length: 1 bit
+
+This bit in the Piggybacked STATUS PDU is used to make the Piggybacked STATUS PDU a multiple of 8 bits in length and for this purpose it is coded as 0. Otherwise the PDU is treated as invalid and hence shall be discarded by this version of the protocol.
+
+#### 9.2.2.13 Reset Sequence Number (RSN)
+
+Length: 1 bit
+
+This field is used to indicate the sequence number of the transmitted RESET PDU. If this RESET PDU is a retransmission of the original RESET PDU then the retransmitted RESET PDU would have the same RSN value as the original RESET PDU. Otherwise it will have the next RSN value. The initial value of this field is zero. The value of this field shall be reinitialised when the RLC is re-established. It shall not be reinitialised when the RLC is reset.
+
+#### 9.2.2.14 Hyper Frame Number Indicator (HFNI)
+
+Length: 20 bit
+
+This field is used to indicate the hyper frame number (HFN) to the peer entity. With the aid of this field the HFN in UE and UTRAN can be synchronised.
+
+## 9.3 Protocol states
+
+The content presented in this subclause is intended to support the definition of the RLC protocol states only, and is not meant to specify or constrain the implementation of the protocol.
+
+### 9.3.1 State model for transparent mode entities
+
+Figure 9.16 illustrates the state model for transparent mode RLC entities (both transmitting and receiving). A transparent mode entity can be in one of the following states.
+
+#### 9.3.1.1 NULL State
+
+In the NULL state the RLC entity does not exist and therefore it is not possible to transfer any data through it.
+
+Upon reception of a CRLC-CONFIG-Req from upper layers indicating establishment, the RLC entity:
+
+- is created; and
+- enters the DATA\_TRANSFER\_READY state.
+
+#### 9.3.1.2 DATA\_TRANSFER\_READY State
+
+In the DATA\_TRANSFER\_READY state, transparent mode data can be exchanged between the entities according to subclause 11.1.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+
+
+```
+
+stateDiagram-v2
+ state "1. NULL" as NULL
+ state "2. DATA_TRANSFER_READY" as DTR
+ NULL --> DTR : CRLC-CONFIG-Req
+ DTR --> NULL : CRLC-CONFIG-Req
+
+```
+
+The diagram illustrates the state transitions for transparent mode RLC entities. It consists of two circular states: '1. NULL' on the left and '2. DATA\_TRANSFER\_READY' on the right. A curved arrow points from the NULL state to the DATA\_TRANSFER\_READY state, labeled 'CRLC-CONFIG-Req'. Another curved arrow points from the DATA\_TRANSFER\_READY state back to the NULL state, also labeled 'CRLC-CONFIG-Req'. To the right of the states, there is a legend:
+Received signal
+ Sent signal
+
+State model diagram for transparent mode entities showing two states: 1. NULL and 2. DATA\_TRANSFER\_READY. Transitions are triggered by CRLC-CONFIG-Req signals.
+
+**Figure 9.16: The state model for transparent mode entities**
+
+### 9.3.2 State model for unacknowledged mode entities
+
+Figure 9.17 illustrates the state model for unacknowledged mode RLC entities (both transmitting and receiving). An unacknowledged mode entity can be in one of the following states.
+
+#### 9.3.2.1 NULL State
+
+In the NULL state the RLC entity does not exist and therefore it is not possible to transfer any data through it.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating establishment the RLC entity:
+
+- is created; and
+- enters the DATA\_TRANSFER\_READY state.
+
+#### 9.3.2.2 DATA\_TRANSFER\_READY State
+
+In the DATA\_TRANSFER\_READY state, unacknowledged mode data can be exchanged between the entities according to subclause 11.2.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating modification, the RLC entity:
+
+- stays in the DATA\_TRANSFER\_READY state;
+- modifies only the protocol parameters and timers as indicated by upper layers.
+
+Upon reception of a CRLC-SUSPEND-Req from upper layers, the RLC entity:
+
+- enters the LOCAL\_SUSPEND state.
+
+#### 9.3.2.3 LOCAL\_SUSPEND State
+
+In the LOCAL\_SUSPEND state, the RLC entity is suspended, i.e. it does not send UMD PDUs with "Sequence Number" greater than or equal to a certain specified value (see subclause 9.7.5).
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+Upon reception of a CRLC-RESUME-Req from upper layers, the RLC entity:
+
+- enters the DATA\_TRANSFER\_READY state; and
+- resumes the data transmission.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating modification, the RLC entity:
+
+- stays in the LOCAL\_SUSPEND state;
+- modifies only the protocol parameters and timers as indicated by upper layers.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> 1.NULL
+ 1.NULL --> 2.DATA_TRANSFER_READY : CRLC-CONFIG-Req
+ 2.DATA_TRANSFER_READY --> 2.DATA_TRANSFER_READY : CRLC-CONFIG-Req
+ 2.DATA_TRANSFER_READY --> 3.LOCAL_SUSPEND : CRLC-SUSPEND-Req
+ 3.LOCAL_SUSPEND --> 2.DATA_TRANSFER_READY : CRLC-RESUME-Req
+ 3.LOCAL_SUSPEND --> 1.NULL : CRLC-CONFIG-Req
+ 3.LOCAL_SUSPEND --> 3.LOCAL_SUSPEND : Received signal
+ 3.LOCAL_SUSPEND --> 3.LOCAL_SUSPEND : Sent signal
+ 3.LOCAL_SUSPEND --> 2.DATA_TRANSFER_READY : CRLC-SUSPEND-Conf
+
+```
+
+Figure 9.17: The state model for unacknowledged mode entities. The diagram shows three states: 1. NULL, 2. DATA\_TRANSFER\_READY, and 3. LOCAL\_SUSPEND. Transitions are triggered by RLC configuration, suspend, and resume requests. State 2 has a self-loop for data transfer. State 3 has self-loops for received and sent signals.
+
+Figure 9.17: The state model for unacknowledged mode entities
+
+### 9.3.3 State model for acknowledged mode entities
+
+Figure 9.18 illustrates the state model for the acknowledged mode RLC entity (both transmitting and receiving). An acknowledged mode entity can be in one of the following states.
+
+#### 9.3.3.1 NULL State
+
+In the NULL state the RLC entity does not exist and therefore it is not possible to transfer any data through it.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating establishment, the RLC entity:
+
+- is created; and
+- enters the DATA\_TRANSFER\_READY state.
+
+#### 9.3.3.2 DATA\_TRANSFER\_READY State
+
+In the DATA\_TRANSFER\_READY state, acknowledged mode data can be exchanged between the entities according to subclause 11.3.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+Upon detection of an initiating condition for the RLC reset procedure described in subclause 11.4.2, the RLC entity:
+
+- initiates the RLC reset procedure (see subclause 11.4); and
+- enters the RESET\_PENDING state.
+
+Upon reception of a RESET PDU, the RLC entity responds according to subclause 11.4.3.
+
+Upon reception of a RESET ACK PDU, the RLC entity takes no action.
+
+Upon reception of CRLC-SUSPEND-Req from upper layer, the RLC entity is suspended and enters the LOCAL\_SUSPEND state.
+
+#### 9.3.3.3 RESET\_PENDING State
+
+In the RESET\_PENDING state the entity waits for a response from its peer entity and no data can be exchanged between the entities.
+
+Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+Upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, the RLC entity:
+
+- acts according to subclause 11.4.4; and
+- enters the DATA\_TRANSFER\_READY state.
+
+Upon reception of a RESET ACK PDU with a different RSN value as in the corresponding RESET PDU, the RLC entity:
+
+- discards the RESET ACK PDU (see subclause 11.4.4); and
+- stays in the RESET\_PENDING state.
+
+Upon reception of a RESET PDU, the RLC entity:
+
+- responds according to subclause 11.4.3; and
+- stays in the RESET\_PENDING state.
+
+Upon reception of CRLC-SUSPEND-Req from upper layer, the RLC entity:
+
+- enters the RESET\_AND\_SUSPEND state.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> NULL
+ NULL --> NULL : CRLC-CONFIG-Req
+ NULL --> DATA_TRANSFER_READY : CRLC-CONFIG-Req
+ NULL --> RESET_PENDING : CRLC-CONFIG-Req
+ NULL --> RESET_AND_SUSPEND : CRLC-CONFIG-Req
+ DATA_TRANSFER_READY --> NULL : CRLC-CONFIG-Req
+ DATA_TRANSFER_READY --> DATA_TRANSFER_READY : RESET, RESET ACK
+ DATA_TRANSFER_READY --> LOCAL_SUSPEND : CRLC-SUSPEND-Req, CRLC-SUSPEND-Conf
+ DATA_TRANSFER_READY --> RESET_PENDING : RESET
+ DATA_TRANSFER_READY --> RESET_AND_SUSPEND : CRLC-SUSPEND-Req
+ LOCAL_SUSPEND --> NULL : CRLC-CONFIG-Req
+ LOCAL_SUSPEND --> DATA_TRANSFER_READY : CRLC-RESUME-Req
+ LOCAL_SUSPEND --> RESET_PENDING : RESET
+ LOCAL_SUSPEND --> RESET_AND_SUSPEND : RESET
+ RESET_PENDING --> NULL : CRLC-CONFIG-Req
+ RESET_PENDING --> DATA_TRANSFER_READY : RESET ACK
+ RESET_PENDING --> LOCAL_SUSPEND : CRLC-SUSPEND-Req, CRLC-SUSPEND-Conf
+ RESET_PENDING --> RESET_AND_SUSPEND : CRLC-RESUME-Req
+ RESET_AND_SUSPEND --> NULL : CRLC-CONFIG-Req
+ RESET_AND_SUSPEND --> DATA_TRANSFER_READY : CRLC-RESUME-Req
+ RESET_AND_SUSPEND --> LOCAL_SUSPEND : RESET
+
+```
+
+Legend:
+ Received signal (solid line)
+ Sent signal (dashed line)
+
+State model diagram for acknowledged mode entities showing five states: 1. NULL, 2. DATA\_TRANSFER\_READY, 3. RESET\_PENDING, 4. LOCAL\_SUSPEND, and 5. RESET\_AND\_SUSPEND. Transitions are triggered by CRLC-CONFIG-Req, RESET, RESET ACK, CRLC-SUSPEND-Req, CRLC-SUSPEND-Conf, and CRLC-RESUME-Req. Solid lines represent received signals, and dashed lines represent sent signals.
+
+Figure 9.18: The state model for the acknowledged mode entities
+
+#### 9.3.3.4 LOCAL\_SUSPEND State
+
+In the LOCAL\_SUSPEND state, the RLC entity is suspended, i.e. it does not send AMD PDUs with "Sequence Number" greater than or equal to certain specified value (see subclause 9.7.5).
+
+Upon reception of CRLC-RESUME-Req from upper layers in this state, the RLC entity:
+
+- resumes the data transmission; and
+- enters the DATA\_TRANSFER\_READY state.
+
+Upon reception of CRLC-CONFIG-Req from upper layers indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+Upon detection of an initiating condition for RLC reset procedure described in subclause 11.4.2, the RLC entity:
+
+- initiates the RLC reset procedure (see subclause 11.4); and
+- enters the RESET\_AND\_SUSPEND state.
+
+#### 9.3.3.5 RESET\_AND\_SUSPEND State
+
+In the RESET\_AND\_SUSPEND state, the entity waits for a response from its peer entity or a primitive (CRLC-RESUME-Req) from its upper layer and no data can be exchanged between the entities.
+
+Upon reception of CRLC-CONFIG-Req from upper layer indicating release, the RLC entity:
+
+- enters the NULL state; and
+- is considered as being terminated.
+
+Upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, the RLC entity:
+
+- acts according to subclause 11.4.4; and
+- enters the LOCAL\_SUSPEND state.
+
+Upon reception of CRLC-RESUME-Req from upper layer in this state, the RLC entity:
+
+- is resumed, i.e. releases the suspend constraint; and
+- enters the RESET\_PENDING state.
+
+## 9.4 State variables
+
+The state variables defined in this subclause are normative.
+
+This sub-clause describes the state variables used in AM and UM in order to specify the peer-to-peer protocol. All state variables are non-negative integers. UMD and AMD PDUs are numbered by modulo integer sequence numbers (SN) cycling through the field: 0 to $2^{12} - 1$ for AM and 0 to $2^7 - 1$ for UM. All arithmetic operations contained in the present document on VT(S), VT(A), VT(MS), VR(R), VR(H) and VR(MR) are affected by the AM modulus. All arithmetic operations contained in the present document on VT(US), VR(US), VR(UDH), VR(UDR), VR(UOH) and VR(UM) are affected by the UM modulus. When performing arithmetic comparisons of state variables or Sequence number values a modulus base shall be used. This modulus base is subtracted (within the appropriate field) from all the values involved and then an absolute comparison is performed. At the Sender, VT(A) and VT(US) shall be assumed to be the modulus base in AM and UM respectively. At the Receiver, VR(R) shall be assumed to be the modulus base in AM and VR(US) shall be assumed to be the modulus base in UM when neither the "out of sequence SDU delivery" nor the "duplicate avoidance and reordering" function are configured. When "out of sequence SDU delivery" is configured, $(VR(UOH) - OSD\_Window\_Size + 1)$ shall be assumed to be the modulus base at the Receiver in UM; when the "duplicate avoidance and reordering" function is configured, $(VR(UDH) - DAR\_Window\_Size + 1)$ shall be assumed to be the modulus base at the Receiver in UM.
+
+The RLC shall maintain the following state variables in the Sender.
+
+### a) VT(S) - Send state variable.
+
+This state variable contains the "Sequence Number" of the next AMD PDU to be transmitted for the first time (i.e. excluding retransmitted PDUs). It shall be updated after the aforementioned AMD PDU is transmitted or after transmission of a MRW SUFI which includes $SN\_MRW\_LENGTH > VT(S)$ (see subclause 11.6).
+
+The initial value of this variable is 0.
+
+### b) VT(A) - Acknowledge state variable.
+
+This state variable contains the "Sequence Number" following the "Sequence Number" of the last in-sequence acknowledged AMD PDU. This forms the lower edge of the transmission window of acceptable acknowledgements. VT(A) shall be updated based on the receipt of a STATUS PDU including an ACK (see subclause 9.2.2.11.2) and/or an MRW\_ACK SUFI (see subclause 11.6).
+
+The initial value of this variable is 0. For the purpose of initialising the protocol, this value shall be assumed to be the first "Sequence Number" following the last in-sequence acknowledged AMD PDU.
+
+### c) VT(DAT).
+
+This state variable counts the number of times a AMD PDU has been scheduled to be transmitted. There shall be one VT(DAT) for each PDU and each shall be incremented every time the corresponding AMD PDU is scheduled to be transmitted or every time a STATUS PDU containing the POLL SUFI is scheduled to be transmitted and the sequence number of the corresponding AMD PDU is equal to VT(S)-1.
+
+The initial value of this variable is 0.
+
+### d) VT(MS) - Maximum Send state variable.
+
+This state variable contains the "Sequence Number" of the first AMD PDU that can be rejected by the peer Receiver, $VT(MS) = VT(A) + VT(WS)$ . This value represents the upper edge of the transmission window. The transmitter shall not transmit AMD PDUs with "Sequence Number" $\geq VT(MS)$ unless $VT(S) \geq VT(MS)$ . In that case, the AMD PDU with "Sequence Number" $= VT(S) - 1$ can also be transmitted. VT(MS) shall be updated when VT(A) or VT(WS) is updated.
+
+The initial value of this variable is Configured\_Tx\_Window\_size.
+
+### e) VT(US) – UM data state variable.
+
+This state variable contains the "Sequence Number" of the next UMD PDU to be transmitted. It shall be incremented by 1 each time a UMD PDU is transmitted.
+
+The initial value of this variable is 0.
+
+NOTE: For the UTRAN side, the initial value of this variable can be different from 0.
+
+### f) VT(PDU).
+
+This state variable is used when the "poll every Poll\_PDU PDU" polling trigger is configured. It shall be incremented by 1 for each AMD PDU that is transmitted including both new and retransmitted AMD PDUs. When it becomes equal to the value Poll\_PDU, a new poll shall be transmitted and the state variable shall be set to zero.
+
+The initial value of this variable is 0.
+
+### g) VT(SDU).
+
+This state variable is used when the "poll every Poll\_SDU SDU" polling trigger is configured. It shall be incremented by 1 for a given SDU when the AMD PDU carrying the first segment of this SDU is scheduled to be transmitted for the first time. When it becomes equal to the value Poll\_SDU a new poll shall be transmitted and the state variable shall be set to zero. The "Polling bit" shall be set to "1" in the first transmission of the AMD PDU that contains the last segment of an RLC SDU (indicated either by the "Length Indicator" indicating the end of the SDU or by the special value of the HE field).
+
+The initial value of this variable is 0.
+
+### h) VT(RST) - Reset state variable.
+
+This state variable is used to count the number of times a RESET PDU is scheduled to be transmitted before the reset procedure is completed. VT(RST) shall be incremented by 1 according to subclauses 11.4.2 and 11.4.5.1. VT(RST) shall only be reset upon the reception of a RESET ACK PDU ( i.e. VT(RST) shall not be reset when an RLC reset initiated by the peer RLC entity occurs) unless otherwise specified in subclause 9.7.7.
+
+The initial value of this variable is 0.
+
+### i) VT(MRW) – MRW command send state variable.
+
+This state variable is used to count the number of times a MRW command is transmitted. VT(MRW) is incremented by 1 each time a timer Timer\_MRW expires. VT(MRW) shall be reset when the SDU discard with explicit signalling procedure is terminated.
+
+The initial value of this variable is 0.
+
+### j) VT(WS) – Transmission window size state variable.
+
+This state variable contains the size that shall be used for the transmission window. VT(WS) shall be set equal to the WSN field when the transmitter receives a STATUS PDU including a WINDOW SUFI.
+
+The initial value of this variable is Configured\_Tx\_Window\_size.
+
+The RLC shall maintain the following state variables in the Receiver:
+
+### a) VR(R) - Receive state variable.
+
+This state variable contains the "Sequence Number" following that of the last in-sequence AMD PDU received. It shall be updated upon the receipt of the AMD PDU with "Sequence Number" equal to VR(R).
+
+The initial value of this variable is 0. For the purpose of initialising the protocol, this value shall be assumed to be the first "Sequence Number" following the last in-sequence received AMD PDU.
+
+### b) VR(H) - Highest expected state variable.
+
+This state variable contains the "Sequence Number" following the highest "Sequence Number" of any AMD PDU received or identified to be missing.. When a AMD PDU is received with "Sequence Number" x or a POLL SUFI is received with POLL\_SN=x such that VR(H)≤x$ VR(MS):
+ - start Timer\_Reordering;
+ - set VR(X) to VR(H).
+
+### 9.7.3 SDU discard function for acknowledged, unacknowledged, and transparent mode
+
+The SDU discard function is used by the Sender to discharge RLC PDUs from the RLC PDU buffer, when the transmission of the RLC PDUs does not succeed for a period of time or for a number of transmissions. The SDU discard function allows to avoid buffer overflow. There are several alternative operation modes of the RLC SDU discard function. Upper layers control, which discard function shall be used for each RLC entity.
+
+The following is a list of operation modes for the RLC SDU discard function, which are described in detail in the subsequent subclauses.
+
+**Table 9.2: List of criteria that control when to perform SDU discard**
+
+| Operation mode | Presence |
+|--------------------------------------------------|--------------------|
+| Timer based discard, with explicit signalling | Network controlled |
+| Timer based discard, without explicit signalling | Network controlled |
+| SDU discard after MaxDAT number of transmissions | Network controlled |
+| No discard after MaxDAT number of transmissions | Network controlled |
+
+#### 9.7.3.1 Timer based discard, with explicit signalling
+
+This alternative is only applicable to RLC entities operating in acknowledged mode. It uses a timer based triggering of SDU discard (Timer\_Discard). This makes the SDU discard function insensitive to variations in the channel rate and provides means for exact definition of maximum delay. However, the SDU loss rate of the connection is increased as SDUs are discarded.
+
+For every SDU received from upper layers, the Sender shall:
+
+- start a timer Timer\_Discard.
+
+When the timer Timer\_Discard of a SDU expires, the Sender shall:
+
+- discard the SDU;
+- if "Send MRW" is configured, or one or more segments of the discarded SDU were submitted to the lower layer:
+ - utilise explicit signalling to inform the Receiver according to subclause 11.6.
+
+NOTE: The support of the configuration "Send MRW" and the functionality connected with this configuration is implementation dependent.
+
+#### 9.7.3.2 Timer based discard, without explicit signalling
+
+This alternative is only applicable to RLC entities operating in unacknowledged or transparent mode. It uses the same timer based trigger for SDU discard (Timer\_Discard) as the one described in the subclause 9.7.3.1. The difference is that this discard method does not use any peer-to-peer signalling.
+
+For every SDU received from upper layers, the Sender shall:
+
+- start timer monitoring of the transmission time of the SDU.
+
+When the transmission time exceeds the configured value for a SDU, the Sender shall:
+
+- discard the SDU without explicit signalling (for RLC entities operating in unacknowledged mode apply subclause 11.2.4.3 for updating the state variables).
+
+#### 9.7.3.3 SDU discard after MaxDAT number of transmissions
+
+This alternative uses the number of transmissions as a trigger for SDU discard, and is therefore only applicable for acknowledged mode RLC. This makes the SDU discard function dependent on the channel rate. Also, this variant of the SDU discard function strives to keep the SDU loss rate constant for the connection, on the cost of a variable delay.
+
+If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall:
+
+- discard all SDUs that have segments or "Length Indicators" indicating the end of the SDUs in the AMD PDU; and
+- utilise explicit signalling to inform the Receiver according to clause 11.6.
+
+#### 9.7.3.4 No\_discard after MaxDAT number of transmissions
+
+This alternative uses the number of transmissions, and is therefore only applicable for acknowledged mode RLC.
+
+If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall:
+
+- initiate the RLC Reset procedure (see subclause 11.3.4.4).
+
+#### 9.7.3.5 SDU discard not configured
+
+If SDU discard has not been configured for an unacknowledged mode RLC entity, SDUs in the transmitter shall not be discarded unless the Transmission buffer is full.
+
+When the Transmission buffer in an unacknowledged mode RLC entity is full, the Sender may:
+
+- if segments of the SDU to be discarded have been submitted to lower layer:
+ - discard the SDU without explicit signalling according to subclause 11.2.4.3.
+- otherwise, if no segments of the SDU to be discarded have been submitted to lower layer:
+ - remove the SDU from the Transmission buffer without utilising any of the discard procedures.
+
+If SDU discard has not been configured for a transparent mode RLC entity, the Sender shall upon reception of new SDUs from upper layer:
+
+- discard all SDUs received from upper layer in previous TTIs that are not yet submitted to lower layer;
+- submit the new SDUs in the first possible TTI.
+
+For an acknowledged mode RLC entity, an SDU discard mode is always configured.
+
+### 9.7.4 Void
+
+### 9.7.5 Local Suspend function for acknowledged and unacknowledged mode
+
+The upper layers may suspend an RLC entity.
+
+When an RLC entity operating in unacknowledged mode is suspended by upper layers with the parameter N, the RLC entity shall:
+
+- acknowledge the suspend request with a confirmation containing the current value of VT(US);
+- not send UMD PDUs with "Sequence Number" $SN \geq VT(US) + N$ .
+
+When an RLC entity operating in acknowledged mode is suspended by upper layers with the parameter N, the RLC entity shall:
+
+- acknowledge the suspend request with a confirmation containing the current value of VT(S);
+- not send AMD PDUs with "Sequence Number" $SN \geq VT(S) + N$ .
+
+When an RLC entity operating in unacknowledged mode is resumed by upper layers, the RLC entity shall:
+
+- resume data transfer procedure.
+
+When an RLC entity operating in acknowledged mode is resumed by upper layers, the RLC entity shall:
+
+- if the RLC entity is suspended and a RLC Reset procedure is not ongoing:
+ - resume data transfer procedure.
+- otherwise, if the RLC entity is suspended and a RLC Reset procedure is ongoing:
+ - remove the suspend constraint;
+ - resume the RLC reset procedure according to subclause 11.4.
+
+### 9.7.6 RLC Stop, RLC Continue function for acknowledged and unacknowledged mode
+
+The upper layer may stop an RLC entity.
+
+When an RLC entity is stopped, the RLC timers are not affected.
+
+When a RLC entity is stopped by upper layers, the RLC entity shall:
+
+- not submit any RLC PDUs to lower layer or receive any RLC PDUs;
+- delay triggered Polling functions or status transmissions until the RLC entity is continued.
+
+NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the stop function until the end of the next TTI.
+
+When a RLC entity is continued by upper layers, the RLC entity shall:
+
+- if the RLC entity is stopped:
+ - continue the data transmission and reception;
+ - process the triggered Polling functions and status transmissions.
+- otherwise, if the RLC is not stopped:
+ - take no action.
+
+### 9.7.7 RLC re-establishment function for acknowledged and unacknowledged mode
+
+RLC re-establishment is performed upon request by upper layers.
+
+The RLC re-establishment function is applicable for AM or UM RLC. For UM, the whole RLC entity is re-established. For AM, upper layers may request re-establishment of the whole RLC entity or only the transmitting or receiving side of the RLC entity.
+
+When an UM RLC entity is re-established by upper layers, the RLC entity shall:
+
+- reset the state variables to their initial value;
+- set the configurable parameters to their configured value;
+- set the hyper frame number (HFN) to the value configured by upper layers;
+- if it is a receiving UM RLC entity:
+ - discard all UMD PDUs.
+ - stop all timers;
+- if it is a transmitting UM RLC entity:
+ - discard the RLC SDUs for which one or more segments have been submitted to a lower layer;
+ - if requested:
+ - inform the upper layers of the discarded SDUs.
+ - not stop Timer\_Discard if the RLC SDU is not discarded.
+
+When the transmitting and/or receiving side of an AM RLC entity is re-established by upper layers, the RLC entity shall:
+
+- if the receiving side of the RLC entity is re-established:
+ - reset the state variables specified for the receiver in subclause 9.4 to their initial values;
+ - set the configurable parameters applicable for the receiving side in subclause 9.6 to their configured values;
+ - set the hyper frame number (HFN) in the receiving side (DL in the UE) to the value configured by upper layers;
+ - discard the AMD PDUs in the receiving side.
+- if only the receiving side of the RLC entity is re-established:
+ - discard acknowledgement status report, WINDOW SUFI and MRW\_ACK SUFI in all STATUS PDUs and piggybacked STATUS PDUs, RESET PDU and RESET ACK PDU (i.e. discard all control PDUs except MRW SUFI and POLL SUFI);
+ - if an RLC reset procedure is ongoing (i.e. Timer\_RST is running):
+ - stop Timer\_RST;
+ - abort the ongoing RLC reset procedure;
+ - reset VT(RST);
+ - restart a new RLC reset procedure after the RLC re-establishment terminates.
+ - stop Timer\_Status\_Prohibit;
+ - for the remaining control PDUs and SUFI that were scheduled for transmission before re-establishment but were not delivered to lower layer:
+
+- assemble the control PDUs and SUFI that were not discarded into new control PDUs with the configured RLC PDU size;
+- schedule the new control PDUs for transmission.
+- if the transmitting side of the RLC entity is re-established:
+ - reset the state variables specified for the sender in subclause 9.4 to their initial values;
+ - set the configurable parameters applicable for the transmitting side in subclause 9.6 to their configured values;
+ - set the hyper frame number (HFN) in the transmitting side (UL in the UE) to the value configured by upper layers;
+ - discard SDUs in the transmitting side that have been completely transmitted (the AMD PDUs containing segments of the SDU and the "Length Indicator" indicating the end of the SDU have been transmitted);
+ - the UE may also discard partially transmitted SDUs (at least one AMD PDU containing a segment of the SDU has been transmitted);
+ - segment the SDUs that were not discarded into AMD PDUs with the configured RLC PDU size (that may be different from the size before the re-establishment);
+ - if only the transmitter side of the RLC entity is re-established:
+ - discard MRW SUFI and POLL SUFI in all STATUS PDUs and piggybacked STATUS PDUs, RESET PDU and RESET ACK PDU (i.e. discard all control PDUs except acknowledgement status report, WINDOW SUFI and MRW\_ACK SUFI);
+ - for the remaining control PDUs and SUFI that were scheduled for transmission before re-establishment but were not delivered to lower layer:
+ - assemble the control PDUs and SUFI that were not discarded into new control PDUs with the configured RLC PDU size;
+ - schedule the control PDUs for transmission.
+ - if an RLC reset procedure is ongoing (i.e. Timer\_RST is running):
+ - stop Timer\_RST;
+ - abort the ongoing RLC reset procedure;
+ - restart a new RLC reset procedure after the RLC re-establishment terminates.
+ - stop Timer\_Poll, Timer\_MRW and Timer\_Poll\_Prohibit.
+ - if both the transmitter and receiver side of the RLC entity is re-established:
+ - discard the control PDUs in both transmitting and receiving side and the AMD PDUs in the transmitting side;
+ - if an RLC reset procedure is ongoing (i.e. Timer\_RST is running):
+ - abort the ongoing RLC reset procedure.
+ - stop all timers described in subclause 9.5 except Timer\_Poll\_Periodic and Timer\_Status\_Periodic, and Timer\_Discard for SDUs that have not been discarded.
+ - if requested:
+ - inform the upper layers of the discarded SDUs.
+
+NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the re-establishment function until the end of the next TTI.
+
+### 9.7.8 Ciphering for acknowledged and unacknowledged mode
+
+The ciphering function is performed in RLC, according to the following rules if a radio bearer is using a non-transparent RLC mode (AM or UM). The data unit that is ciphered, depends on the transmission mode as described below.
+
+- For RLC UM mode, the ciphering unit is the UMD PDU excluding the first octet, i.e. excluding the UMD PDU header. This is shown below in Figure 9.19.
+
+
+
+Ciphering
+Unit
+
+↨
+
+| | | | |
+|------------------|--|---|--------------------|
+| Sequence Number | | E | Oct1 |
+| Length Indicator | | E | (Optional) (1) |
+| .
.
. | | | |
+| Length Indicator | | E | (Optional) |
+| Data | | | |
+| PAD | | | (Optional)
OctN |
+
+**Figure 9.19: Ciphering unit for a UMD PDU**
+
+- For RLC AM mode, the ciphering unit is the AMD PDU excluding the first two octets, i.e. excluding the AMD PDU header. This is shown below in Figure 9.20.
+
+
+
+Ciphering
+Unit
+
+↨
+
+| | | | | |
+|---------------------------------|-----------------|---|----|-----------------|
+| D/C | Sequence Number | | | Oct1 |
+| Sequence Number | | P | HE | Oct2 |
+| Length Indicator | | | E | Oct3 (Optional) |
+| .
.
. | | | | |
+| Length Indicator | | | E | |
+| Data | | | | |
+| PAD or a piggybacked STATUS PDU | | | | OctN |
+
+**Figure 9.20: Ciphering unit for an AMD PDU**
+
+The ciphering algorithm and key to be used are configured by upper layers [8] and the ciphering method shall be applied as specified in [9].
+
+The parameters that are required by RLC for ciphering are defined in [9] and are input to the ciphering algorithm. The parameters required by RLC which are provided by upper layers [8] are listed below:
+
+- RLC AM HFN (Hyper frame number for radio bearers that are mapped onto RLC AM);
+- RLC UM HFN (Hyper frame number for radio bearers that are mapped onto RLC UM);
+- BEARER (defined as the radio bearer identifier in [9]. It will use the value RB identity –1 as in [8]);
+- CK (Ciphering Key).
+
+### 9.7.9 Reconfiguration of RLC parameters by upper layers
+
+The RLC parameters for an RLC entity may be reconfigured (modified) by upper layers.
+
+When an RLC parameter is reconfigured by the upper layer, the UE shall:
+
+- start using the reconfigured value of the RLC parameter.
+
+If the parameter Configured\_Rx\_Window\_Size is reconfigured:
+
+- the UE shall update the state variable VR(UM), (see clause 9.4);
+- the UE shall update the state variable VR(MR), (see clause 9.4);
+- for AMD PDUs with "Sequence Number" x such that VR(MR) ≤ x < VR(H):
+ - the UE may discard these AMD PDUs; if discarded, the state variable VR(H) should be updated accordingly;
+ - consider the discarded AMD PDUs as not having been received.
+
+If the parameter Configured\_Tx\_Window\_Size is reconfigured:
+
+- the UE shall set the state variable VT(WS) equal to the Configured\_Tx\_Window\_Size;
+- the UE shall update the state variable VT(MS), (see subclause 9.4);
+- for AMD PDUs with "Sequence Number" x such that VT(MS) ≤ x < VT(S):
+ - the UE shall not discard any AMD PDUs that are not positively acknowledged;
+ - the UE may discard AMD PDUs that are positively acknowledged.
+
+When the transmission window size or the reception window size is reconfigured the required buffer memory may temporarily exceed the size of the configured window and thus exceed the available buffer memory (see subclause 11.3.4.9).
+
+If the parameter OSD\_Window\_Size is reconfigured:
+
+- the UE shall remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window $VR(UOH) \geq SN > VR(UOH) - OSD\_Window\_Size$ .
+
+If the parameter DAR\_Window\_Size is reconfigured:
+
+- the UE shall remove from storage any PDUs whose sequence numbers are outside of the storage window and deliver them to the higher RLC function to perform reassembly specified in subclause 11.2.3 and update the state variable VR(UDR) as specified in subclause 9.7.10;
+- the UE shall update the state variables VR(UDT) and operate the timer Timer\_DAR if needed (see subclause 9.7.10).
+
+### 9.7.10 Duplicate avoidance and reordering for unacknowledged mode
+
+The duplicate avoidance and reordering function can be configured for use within a receiving UM RLC entity in the UE. It combines PDU sequences received from several sources and/or repeat transmissions from a single source to form a single ordered PDU sequence that is passed to the header removal and reassembly functions. It completes duplicate detection, discard and re-ordering based on the UM PDU sequence number. Where the UM RLC receives input from several sources, inputs can be added or removed without changing the buffer contents, state variables and timers associated with the duplicate avoidance and reordering function or any subsequent UM RLC function.
+
+The duplicate avoidance and reordering function makes use of the state variable VR(UDR) and a receive window whose span is from VR(UDH) – DAR\_Window\_Size + 1 to VR(UDH) inclusively. For re-ordering the function uses a buffer for the temporary storage of PDUs.
+
+For each PDU received, the duplicate avoidance and reordering function shall (in the following SN denotes the sequence number of each PDU):
+
+Setting initial values of state variables:
+
+- If the PDU is the first PDU received by the duplicate avoidance and reordering function after establishment or re-establishment:
+
+- VR(UDH) is assigned the value SN;
+- VR(UDR) is assigned the value VR(UDH) – DAR\_Window\_Size + 1.
+
+Duplicate detection and re-ordering:
+
+- if SN is within the receive window:
+ - if SN < VR(UDR) or if a PDU with sequence number SN is already stored in the buffer:
+ - the PDU shall be discarded;
+ - else:
+ - the PDU shall be stored in the buffer.
+- if SN is outside of the receive window:
+ - the PDU shall be stored in the buffer;
+ - VR(UDH) shall be assigned the value SN, thereby advancing the receive window;
+ - for any stored PDUs with sequence numbers < VR(UDH) – DAR\_Window\_Size + 1, i.e. outside the receive window after its position is updated, remove the PDU from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
+ - if VR(UDR) < VR(UDH) – DAR\_Window\_Size + 1, i.e. VR(UDR) is outside the updated receive window;
+ - VR(UDR) shall be assigned the value VR(UDH) – DAR\_Window\_Size + 1.
+- if PDU with sequence number VR(UDR) is stored in the buffer:
+ - for this PDU and any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDR) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
+ - VR(UDR) shall be assigned the value of x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function.
+
+Timer operation:
+
+- if Timer\_DAR is not active when a PDU is stored with SN > VR(UDR) by the duplicate avoidance and reordering function:
+ - Timer\_DAR shall be started;
+ - VR(UDT) shall be assigned the value of the sequence number of the PDU.
+- Timer\_DAR shall be stopped:
+ - if the PDU with sequence number VR(UDT) is removed from the buffer before Timer\_DAR expires.
+- if Timer\_DAR expires:
+ - for all stored PDUs with sequence numbers lower or equal to VR(UDT) and for any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDT) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
+ - VR(UDR) shall be assigned the value x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function.
+- When Timer\_DAR is stopped or expires, and there remain PDUs stored by the duplicate avoidance and reordering function:
+ - Timer\_DAR shall be started;
+ - VR(UDT) shall be assigned the sequence number of the highest numbered stored PDU.
+
+# --- 10 Handling of unknown, unforeseen and erroneous protocol data
+
+Errors and the handling of errors defined in this clause are normative.
+
+## 10.1 Erroneous Sequence Number
+
+A STATUS PDU or Piggybacked STATUS PDU including "erroneous Sequence Number" is a STATUS PDU or Piggybacked STATUS PDU that contains:
+
+- a LIST, BITMAP or RLIST SUFI in which the "Sequence Number" of at least one AMD PDU that is negatively acknowledged is outside the interval $VT(A) \leq \text{"Sequence Number"} < VT(S)$ ; or
+- an ACK SUFI in which "LSN" is outside the interval $VT(A) \leq \text{"LSN"} \leq VT(S)$ .
+
+If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU including "erroneous Sequence Number", it shall:
+
+- discard the STATUS PDU or the Piggybacked STATUS PDU;
+- if inter-Node B Multiflow operation is not configured by higher layers, initiate the RLC reset procedure (see subclause 11.4).
+
+## 10.2 Inconsistent status indication
+
+If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU that indicates different status for the same AMD PDU, it shall:
+
+- discard the STATUS PDU or the Piggybacked STATUS PDU.
+
+## 10.3 Invalid PDU format
+
+If an UM or AM RLC entity receives a RLC PDU that contains reserved or invalid values (see subclause 9.2), it shall:
+
+- discard the RLC PDU.
+
+## 10.4 RLC PDU with CRC error
+
+If an UM or AM RLC entity receives a RLC PDU with an error indication, it shall:
+
+- discard the RLC PDU.
+
+If a TM RLC entity receives a RLC PDU with an error indication, it shall:
+
+- if "Delivery of Erroneous SDUs" is configured:
+ - process the RLC PDU according to subclause 11.1.3;
+- otherwise:
+ - discard the RLC PDU.
+
+# --- 11 Elementary procedures
+
+Procedures defined in this clause are normative.
+
+This description assumes elementary procedures. Interactions between procedures are not described.
+
+## 11.1 Transparent mode data transfer procedure
+
+### 11.1.1 General
+
+The transparent mode data transfer procedure is used for transferring data between two RLC peer entities, which are operating in transparent mode. Data is transferred from Sender to Receiver. This procedure should only apply to entities in DATA\_TRANSFER\_READY state. Figure 11.1 below illustrates the elementary procedure for transparent mode data transfer.
+
+Channels that can be used are DTCH, CCCH (uplink only), SHCCH (uplink only), BCCH and PCCH. The type of logical channel depends on if the RLC entity is located in the user plane (DTCH) or in the control plane (CCCH/BCCH/SHCCH/PCCH).
+
+
+
+```
+
+graph LR
+ Sender[Sender] -- "TMD PDU" --> Receiver[Receiver]
+ Sender --- S_Lower[ ]
+ Receiver --- R_Lower[ ]
+ style S_Lower fill:#888,stroke:none
+ style R_Lower fill:#888,stroke:none
+
+```
+
+Diagram illustrating the transparent mode data transfer procedure. A Sender box is on the left and a Receiver box is on the right. A horizontal arrow labeled 'TMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layer.
+
+**Figure 11.1: Transparent mode data transfer procedure**
+
+### 11.1.2 Transmission of TMD PDU
+
+Upon a request of transparent mode data transfer from upper layer, the Sender shall:
+
+- if no SDU discard configuration has been made by upper layers:
+ - discard SDUs received in previous TTIs upon reception of new SDUs from upper layers (see subclause 9.7.3.5);
+- otherwise (if "Timer Based SDU Discard without explicit signalling" is configured):
+ - start a timer Timer\_Discard for each SDU received from upper layers (see subclause 9.7.3);
+- schedule the RLC SDUs that have been received from upper layer for transmission;
+- if one or more RLC SDUs have been scheduled for transmission:
+ - notify the lower layer of reception of data from upper layers;
+ - perform the actions specified in subclause 11.1.2.2.
+
+#### 11.1.2.1 TMD PDU contents to set
+
+The Sender shall set the data field of the TMD PDU to all or a subset of the data contained in the SDU as described in subclause 11.1.2.2.
+
+#### 11.1.2.2 Submission of TMD PDUs to the lower layer
+
+If one or more RLC SDUs have been scheduled for transmission, according to subclause 11.1.2, the Sender shall:
+
+- if it is configured for segmented operation:
+ - inform the lower layer of the size of the next SDU to be sent;
+ - segment the SDU according to the PDU size indicated by the lower layer.
+- otherwise (the Sender is configured for non-segmented operation):
+ - inform the lower layer of the number and size of SDUs available for transmission;
+- submit to the lower layer, the requested number of TMD PDUs;
+
+- buffer the SDUs that are not submitted to the lower layer according to the discard configuration (see subclause 9.7.3).
+
+### 11.1.3 Reception of TMD PDU
+
+Upon delivery by the lower layer of a set of TMD PDUs (received within one TTI), the Receiver shall:
+
+- if it is configured for segmented operation:
+ - reassemble the TMD PDUs received in one TTI into one RLC SDU.
+- otherwise (it is configured for non-segmented operation):
+ - treat each received TMD PDU as a SDU;
+- if "Delivery of Erroneous SDUs" is configured as "no":
+ - submit only the RLC SDUs received without error to upper layers through the TM-SAP.
+- else if "Delivery of Erroneous SDUs" is configured as "yes":
+ - submit all RLC SDUs to upper layers through the TM-SAP;
+ - provide an error indication for each SDU received in error.
+- otherwise if "Delivery of Erroneous SDUs" is configured as "No detect":
+ - submit all RLC SDUs to upper layers through the TM-SAP.
+
+If segmentation is performed in transparent mode RLC, an SDU is erroneous if one or more of the TMD PDUs received in a TTI contains an error. If segmentation is not performed, an SDU is erroneous if the corresponding TMD PDU is erroneous.
+
+### 11.1.4 Abnormal cases
+
+#### 11.1.4.1 Void
+
+#### 11.1.4.2 SDU discard without explicit signalling
+
+Upon expiry of the timer Timer\_Discard in the Sender, the Sender shall:
+
+- discard the associated SDU;
+- if requested:
+ - inform the upper layers of the discarded SDU.
+
+In the case where the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the UE may wait until after it provides MAC with the requested set of PDUs before discarding the afore-mentioned SDU.
+
+## 11.2 Unacknowledged mode data transfer procedure
+
+### 11.2.1 General
+
+The unacknowledged mode data transfer procedure is used for transferring data between two RLC peer entities, which are operating in unacknowledged mode. Data is transferred from Sender to Receiver. This procedure should only apply to RLC entities in DATA\_TRANSFER\_READY state or LOCAL\_SUSPEND state. Figure 11.2 below illustrates the elementary procedure for unacknowledged mode data transfer.
+
+Channels that can be used are DTCH, DCCH, CCCH (downlink only), CTCH, SHCCH (downlink only), MCCH, MSCH, MTCH. The type of logical channel depends on if the RLC entity is located in the user plane (DTCH, CTCH, MTCH) or in the control plane (DCCH/CCCH(downlink only)/SHCCH(downlink only)/MCCH/MSCH). One or
+
+several PDUs may be transmitted in each transmission time interval (TTI). For each TTI, MAC decides which PDU size shall be used and how many PDUs shall be transmitted.
+
+
+
+Diagram illustrating the unacknowledged mode data transfer procedure. A 'Sender' box is on the left and a 'Receiver' box is on the right. A horizontal arrow labeled 'UMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layer.
+
+**Figure 11.2: Unacknowledged mode data transfer procedure**
+
+### 11.2.2 Transmission of UMD PDU
+
+Upon a request of unacknowledged mode data transfer from upper layer, the Sender shall:
+
+- if no SDU discard configuration has been made by upper layers:
+ - only discard SDUs when the Transmission buffer is full (see subclause 9.7.3);
+- if "Timer based SDU Discard without explicit signalling" is configured:
+ - start a timer Timer\_Discard for each SDU received from upper layer (see subclause 9.7.3);
+- schedule the RLC SDUs received from upper layer for transmission;
+- if one or more RLC SDUs have been scheduled for transmission:
+ - notify the lower layer of reception of data from upper layers;
+ - perform the actions specified in subclause 11.2.2.2.
+
+A UMD PDU shall be considered to be a padding PDU if it consists only of an RLC Header with one length indicator (indicating that the rest of the PDU is padding) and padding.
+
+#### 11.2.2.1 UMD PDU contents to set
+
+The Sender shall:
+
+- set the field "Sequence Number" equal to VT(US);
+- set a "Length Indicator" field for each SDU that ends in the UMD PDU according to subclause 9.2.2.8.
+
+For each "Extension bit" field in the RLC header, the Sender shall:
+
+- if the next field in the UMD PDU is a "Length Indicator":
+ - set the "Extension bit" to "1";
+- otherwise if the next field in the UMD PDU is data:
+ - set the "Extension bit" to "0".
+
+#### 11.2.2.2 Submission of UMD PDUs to the lower layer
+
+If one or more SDUs have been scheduled for transmission according to subclause 11.2.2, the Sender shall:
+
+- inform the lower layer of the number and size of SDUs scheduled for transmission;
+- if "SN\_Delivery" is configured:
+ - segment, but not concatenate SDUs
+- else:
+
+- segment, and if possible concatenate the SDUs according to the PDU sizes indicated by the lower layer (see subclause 9.2.2.9);
+- submit to the lower layer, the requested number of UMD PDUs;
+- update VT(US) for each UMD PDU submitted to the lower layer (see subclause 9.4);
+- buffer the SDUs that are not submitted to the lower layer according to the discard configuration (see subclause 9.7.3).
+
+### 11.2.3 Reception of UMD PDU
+
+Upon delivery of a set of UMD PDUs from the lower layer or from the duplicate avoidance and reordering subentity, the Receiver shall:
+
+- if "out of sequence SDU delivery" is configured:
+ - perform the actions specified in subclause 11.2.3.2;
+- else:
+ - perform the actions specified in subclause 11.2.3.1.
+
+#### 11.2.3.1 SDU discard and re-assembly
+
+Upon delivery of a set of UMD PDUs from the lower layer or from the duplicate avoidance and reordering subentity, the Receiver shall:
+
+- if out-of-sequence reception is configured and $SN \geq VR(UM)$ :
+ - discard the UMD PDU.
+- else:
+ - update VR(US) according to each received UMD PDU (see subclause 9.4);
+ - if the updating step of VR(US) is not equal to one (i.e. one or more UMD PDUs are missing):
+ - discard the SDUs that could have segments or "Length Indicators" indicating the end of the SDUs in the missing UMD PDUs according to subclauses 9.2.2.8 and 9.2.2.9.
+ - if the special "Length Indicator" "1111 100" or "1111 1111 1111 100" is the first "Length Indicator" of a UMD PDU received on the downlink:
+ - consider the first data octet in this UMD PDU as the first octet of an RLC SDU.
+ - if the "Extension bit" indicates that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded:
+ - consider the data part in this UMD PDU as one complete RLC SDU.
+ - if the special "Length Indicator" "1111 101" or "1111 1111 1111 101" is the first "Length Indicator" of a UMD PDU received on the downlink:
+ - consider the first data octet in this UMD PDU as the first octet of an RLC SDU and the last data octet as the last octet of the same RLC SDU.
+ - if the special "Length Indicator" "1111 1111 1111 010" is the first "Length Indicator" of a UMD PDU received on the downlink:
+ - consider the first data octet in this UMD PDU as the first octet of an RLC SDU and the second last data octet as the last octet of the same RLC SDU.
+ - reassemble the received UMD PDUs into RLC SDUs;
+ - submit the RLC SDUs to upper layers through the UM-SAP.
+
+#### 11.2.3.2 Out of sequence SDU delivery
+
+To enable the recovery of SDUs from UMD PDUs that are received in different transmissions the receiving function shall store PDUs until all SDUs that are associated with the PDU can be reconstructed or until they are discarded in accordance with the procedures described below. SDUs are transferred to the upper layers as soon as all PDUs that contain the segments of the SDU and the "Length Indicator" indicating the end of the SDU have been received.
+
+Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall for each PDU (in the following SN denotes the sequence number of each PDU):
+
+- If the PDU is the first PDU received (after the receiving entity is established or re-established or after Timer\_OSD expires):
+ - VR(UOH) shall be assigned the value SN-1.
+- if $VR(UOH) \geq SN > VR(UOH) - OSD\_Window\_Size$ then:
+ - if a PDU with sequence number SN is already stored:
+ - discard the PDU;
+ - else:
+ - store the PDU in sequence number order.
+- else:
+ - VR(UOH) shall be assigned the value SN, thereby advancing the storage window;
+ - store the PDU in sequence number order;
+ - remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window $VR(UOH) \geq SN > VR(UOH) - OSD\_Window\_Size$ ;
+ - if Timer\_OSD is active then Timer\_OSD shall be stopped;
+ - Timer\_OSD shall be started.
+- if a PDU with sequence number SN was stored:
+ - if the PDU contains one or more complete SDUs and/or if the PDU contains segments of SDUs for which all the remaining segments and length indicators are contained in stored PDUs:
+ - re-assemble the SDUs;
+ - submit the SDUs to upper layers through the UM-SAP;
+ - remove from storage any PDUs which do not contain any segment of a SDU that has not been re-assembled, and do not contain one of the special length indicators "0000 000", "0000 0000 0000 000" or "1111 1111 1111 011" that indicate the end of a SDU that has not been re-assembled.
+
+NOTE 0: If PDUs are removed from storage after SDU recovery then retransmitted PDUs may result in the duplicate transfer of SDUs to the higher layers.
+
+- if Timer\_OSD expires:
+ - remove from storage all stored PDUs.
+
+NOTE 1: When configured for out of sequence SDU delivery, the transmitter should consider the possibility that a loss of a number of $128 - OSD\_Window\_Size$ consecutively numbered PDUs may result in an undetected protocol error in the receiver, if the transmit state variable VT(US), at the end of a time interval equal to the duration of Timer\_OSD, is greater than $128 + SN - OSD\_Window\_Size + 1$ , where SN is the lowest sequence number of any PDU transmitted or retransmitted within that time interval.
+
+NOTE 2: The transmitter should not concatenate within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with SDUs or fractions of SDUs that contain other MCCH message types.
+
+NOTE 3: SDUs are contained within consecutively numbered PDUs. To enable SDUs containing MBMS Access Information messages to be transmitted at their designated times, the transmitter may transmit PDUs out of sequence order.
+
+NOTE 4: The transmitter should not transmit within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with the special length indicator "0000 000", "0000 0000 0000 000", and "1111 1111 1111 011".
+
+### 11.2.4 Abnormal cases
+
+#### 11.2.4.1 Length Indicator value reserved for UMD PDU
+
+Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for UMD PDUs in this version of the protocol, the Receiver shall:
+
+- ignore that UMD PDU.
+
+#### 11.2.4.2 Invalid length indicator value
+
+If the "Length Indicator" of an UMD PDU has a value that is larger than the PDU size – RLC header size and is not one of the predefined values listed in the table of subclause 9.2.2.8, the Receiver shall:
+
+- ignore the UMD PDU.
+
+#### 11.2.4.3 SDU discard without explicit signalling
+
+Upon expiry of the timer Timer\_Discard in the Sender, the Sender shall:
+
+- discard the associated SDU;
+- if requested:
+ - inform the upper layers of the discarded SDU;
+- for the first UMD PDU to be transmitted after the discard operation, the Sender shall:
+ - increment VT(US) so that the "Sequence Number" field in this UMD PDU is incremented with two compared with the previous UMD PDU;
+ - fill the first data octet in this UMD PDU with the first octet of an RLC SDU;
+ - if the "Extension bit" does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded:
+ - set the first "Length Indicator" in this UMD PDU to indicate that the previous RLC PDU was exactly filled with the last segment of an RLC SDU (to avoid that the Receiver unnecessarily discards an extra SDU).
+
+In the case where the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the UE may wait until after it provides MAC with the requested set of UMD PDUs before discarding the afore-mentioned SDU.
+
+#### 11.2.4.4 Invalid PDU size
+
+In the UE, if the "DL RLC UM LI size" is configured to 7 bits, if a received UMD PDU has a size larger than 125 octets, the Receiver shall:
+
+- ignore that UMD PDU.
+
+## 11.3 Acknowledged mode data transfer procedure
+
+### 11.3.1 General
+
+The acknowledged mode data transfer procedure is used for transferring data between two RLC peer entities, which are operating in acknowledged mode. Data is transferred from Sender to Receiver. This procedure should only apply to
+
+RLC entities in DATA\_TRANSFER\_READY state or LOCAL\_SUSPEND state. Figure 11.3 below illustrates the elementary procedure for acknowledged mode data transfer.
+
+The AMD PDUs shall be transmitted on the DCCH logical channel if the Sender is located in the control plane and on the DTCH if it is located in the user plane. One or several PDUs may be transmitted in each transmission time interval (TTI) and MAC decides how many PDUs shall be transmitted in each TTI.
+
+
+
+Diagram illustrating the Acknowledged mode data transfer procedure. A Sender box is on the left and a Receiver box is on the right. A horizontal arrow labeled 'AMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layers.
+
+**Figure 11.3: Acknowledged mode data transfer procedure**
+
+### 11.3.2 Transmission of AMD PDU
+
+Upon a request of acknowledged mode data transfer from upper layers or upon retransmission of AMD PDUs, the Sender shall:
+
+- when RLC SDUs are received from upper layers:
+ - if "fixed RLC PDU size" has been configured:
+ - segment, and if possible concatenate the RLC SDUs into AMD PDUs where the fixed PDU size is configured by upper layer (see subclause 9.2.2.9);
+ - if the last octet of the PDU is the last octet of an SDU and there is no SDU concatenation inside the PDU, and the "use of the special value of the HE field" has been configured by higher layers, set the HE field to indicate that the last octet of the PDU is the last octet of an SDU (see subclause 9.2.2.7).
+ - if "flexible RLC PDU size" has been configured:
+ - the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to create an AMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size.
+ - set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8, except for the SDUs where the end of the SDU has been indicated by the HE field according to subclause 9.2.2.7;
+ - if "Timer based SDU Discard with explicit signalling" is configured:
+ - start a timer Timer\_Discard for each SDU received from upper layer (see subclause 9.7.3);
+ - schedule the AMD PDUs for transmission;
+- for each AMD PDU which has been negatively acknowledged (see subclause 11.5.3):
+ - if the "Sequence Number" of the AMD PDU is less than VT(MS):
+ - schedule the AMD PDU for retransmission;
+- if a poll has been triggered by one of configured polling functions (see subclause 9.7.1); and
+- if polling is not prohibited (see subclause 9.5); and
+- if no AMD PDU is scheduled for transmission or retransmission; and
+- if there is at least one PDU that has been transmitted, has not been discarded and has not yet been acknowledged:
+
+- if the value of "Configured\_Tx\_Window\_Size" is larger than or equal to "2048":
+ - select the AMD PDU with "Sequence Number" equal to VT(S)-1; or
+ - assemble a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" is configured;
+- otherwise if the "Configured\_Tx\_Window\_Size" is less than "2048":
+ - select the AMD PDU with "Sequence Number" equal to VT(S)-1; or
+ - select an AMD PDU that has not been discarded and has not yet been acknowledged by the peer entity; or
+ - assemble a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" is configured;
+- if an AMD PDU was selected, schedule the selected AMD PDU for retransmission (in order to transmit a poll), or if a POLL SUFI was assembled, schedule a STATUS PDU containing the POLL SUFI for transmission:
+ - if the timer Timer\_Poll is configured:
+ - start the timer Timer\_Poll according to subclause 9.5.
+
+NOTE 1: In downlink, if "flexible RLC PDU size" is configured, the UTRAN should segment, and if possible concatenate the RLC SDUs into AMD PDUs with a size not larger than the maximum RLC PDU size.
+
+NOTE 2: In downlink, UTRAN can initiate the Polling function by assembling a POLL SUFI when "flexible RLC PDU size" in downlink is configured. If a POLL SUFI was assembled, UTRAN should schedule and submit to lower layer a STATUS PDU containing the POLL SUFI.
+
+NOTE 3: In uplink, the UE can initiate the Polling function by assembling a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" in uplink is configured. If a POLL SUFI was assembled, the UE should schedule and submit to lower layer a STATUS PDU containing the POLL SUFI.
+
+Each time an AMD PDU is scheduled for transmission or retransmission, the Sender shall:
+
+- increment the value of the corresponding VT(DAT);
+- if VT(DAT) = MaxDAT:
+ - perform the actions specified in subclause 11.3.3a;
+- else:
+ - notify the lower layer that data is available for transmission;
+ - perform the actions specified in subclause 11.3.2.2.
+
+In AM, a PDU shall be considered to be a padding PDU if it is:
+
+- an AMD PDU consisting only of an RLC Header with one "Length Indicator" (indicating that the rest of the PDU is padding) and padding; or
+- a STATUS PDU consisting only of a NO\_MORE SUFI.
+
+#### 11.3.2.1 AMD PDU contents to set
+
+If the AMD PDU is transmitted for the first time, the Sender shall:
+
+- set the "Sequence Number" field equal to VT(S);
+- if the last octet of the PDU is the last octet of an SDU and there is no SDU concatenation inside the PDU, and the use of the special value of HE field has been configured by higher layers, set the HE field to indicate that the last octet of the PDU is the last octet of an SDU (see subclause 9.2.2.7)
+- set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8, except for the SDUs where the end of the SDU has been indicated by the HE field according to subclause 9.2.2.7;
+
+- set the "Polling bit" to the value specified in subclause 11.3.2.1.1.
+
+Otherwise if the AMD PDU is retransmitted:
+
+- use the same value of the "Sequence Number" field as in the original transmission of the AMD PDU;
+- if the "Length Indicator" fields needed in the AMD PDU according to subclause 9.2.2.8 has changed due to that a piggybacked STATUS PDU is included in the AMD PDU or a piggybacked STATUS PDU was included in the previous transmission of the AMD PDU:
+ - update the "Length Indicator" fields according to 9.2.2.8.
+- set the "Polling bit" to the value specified in subclause 11.3.2.1.1.
+
+##### 11.3.2.1.1 Setting of the Polling bit
+
+The Sender shall:
+
+- if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):
+ - if polling is not prohibited, see subclause 9.5:
+ - set the "Polling bit" in the AMD PDU header to "1";
+- otherwise:
+ - set the "Polling bit" in the AMD PDU header to "0".
+
+##### 11.3.2.1.2 Void
+
+#### 11.3.2.2 Submission of AMD PDUs to lower layer
+
+If one or more AMD PDUs have been scheduled for transmission or retransmission according to subclause 11.3.2, the Sender shall:
+
+- not submit any AMD PDUs to lower layer that is not allowed to transmit. AMD PDUs are only allowed to transmit:
+ - if the AMD PDU has a "Sequence Number" < VT(MS) or the AMD PDU has a "Sequence Number" equal to VT(S)-1; and
+ - if the AMD PDU is not restricted to be transmitted by the local suspend function, see subclause 9.7.5.
+- inform the lower layer of both the numbers of AMD PDUs scheduled and allowed for transmission or retransmission;
+- set the AMD PDU contents according to subclause 11.3.2.1;
+- submit to the lower layer the requested number of AMD PDUs;
+- treat retransmissions with higher priority than AMD PDUs transmitted for the first time;
+- update the state variables in clause 9.4 for each AMD PDU submitted to lower layer except VT(DAT) which has already been updated, see subclause 11.3.2;
+- if the "Polling bit" is set to "1" in any of the AMD PDUs; and
+- if the timer Timer\_Poll is configured;
+ - start the timer Timer\_Poll according to subclause 9.5;
+- buffer the AMD PDUs that are not submitted to the lower layer according to the discard configuration (see subclause 9.7.3).
+
+### 11.3.3 Reception of AMD PDU by the Receiver
+
+Upon reception of an AMD PDU, the Receiver shall:
+
+- in the UE if "fixed RLC PDU size" has been configured:
+ - if the "downlink AMD PDU size" has not yet been set:
+ - set the "downlink AMD PDU size" to the size of the received PDU.
+- update VR(R), VR(H) and VR(MR) state variables for each received AMD PDU (see clause 9.4);
+- if Timer\_Reordering is configured:
+ - if a received AMD PDU SN = VR(MS)
+ - update VR(MS) to SN of the first AMD PDU that has not been received;
+ - if Timer\_Reordering is running:
+ - if VR(X) = VR(R); or
+ - if VR(X) falls outside of the receiving window and VR(X) is not equal to VR(MR):
+ - stop and reset Timer\_Reordering;
+ - if Timer\_Reordering is not running (includes the case Timer\_Reordering is stopped due to actions above):
+ - if VR(H) > VR(R):
+ - start Timer\_Reordering;
+ - set VR(X) to VR(H).
+- if a received AMD PDU includes a "Polling bit" set to "1", or "Missing PDU Indicator" is configured and the Receiver detects that a PDU is missing:
+ - initiate the STATUS PDU transfer procedure;
+- reassemble the received AMD PDUs into RLC SDUs;
+- if "In-Sequence Delivery" is configured:
+ - deliver the RLC SDUs in-sequence (i.e. in the same order as the RLC SDUs were originally transmitted by the peer entity) to upper layers through the AM-SAP.
+- otherwise:
+ - deliver the RLC SDUs in arbitrary order to upper layers through the AM-SAP.
+
+### 11.3.3a Reached maximum number of attempts
+
+If VT(DAT) = MaxDAT, the Sender shall:
+
+- if "No\_discard after MaxDAT number of transmissions" is configured:
+ - initiate the RLC reset procedure, see subclause 11.4.
+- if "SDU discard after MaxDAT number of transmissions" is configured:
+ - initiate the "SDU discard with explicit signalling" procedure for the corresponding SDU, see subclause 11.6.
+
+### 11.3.4 Abnormal cases
+
+#### 11.3.4.1 Void
+
+#### 11.3.4.2 Receiving an AMD PDU outside the reception window
+
+Upon reception of an AMD PDU with "Sequence Number" outside the interval $VR(R) \leq SN < VR(MR)$ , the Receiver shall:
+
+- discard the AMD PDU;
+- if the "polling bit" in the discarded AMD PDU is set to "1":
+ - initiate the STATUS PDU transfer procedure.
+
+#### 11.3.4.3 Timer\_Discard timeout
+
+##### 11.3.4.3.1 SDU discard with explicit signalling
+
+Upon expiry of the timer Timer\_Discard, the Sender shall:
+
+- initiate the SDU discard with explicit signalling procedure, see subclause 11.6.2.
+
+In the case where the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the UE may wait until after it provides MAC with the requested set of PDUs before discarding the afore-mentioned SDUs.
+
+#### 11.3.4.4 Void
+
+#### 11.3.4.5 Invalid length indicator value
+
+If the "Length Indicator" of an AMD PDU has a value that is larger than the PDU size – RLC header size and is not one of the predefined values listed in the table of subclause 9.2.2.8, the Receiver shall:
+
+- ignore that AMD PDU.
+
+#### 11.3.4.6 Length Indicator value reserved for AMD PDU
+
+Upon delivery by the lower layer of an AMD PDU that contains a "Length Indicator" value specified to be reserved for AMD PDUs in this version of the protocol, the Receiver shall:
+
+- ignore that AMD PDU.
+
+#### 11.3.4.7 Void
+
+#### 11.3.4.8 Receiving an AMD PDU within the reception window more than once (Handling of Duplicates)
+
+Upon reception of an AMD PDU with a "Sequence Number" within the interval $VR(R) \leq SN < VR(MR)$ , for which "Sequence Number" an AMD PDU has already been received, the Receiver shall:
+
+- discard the AMD PDU;
+- consider the AMD PDU with this "Sequence Number" as having been correctly received in the next status report to be transmitted;
+- if the "polling bit" in the discarded AMD PDU is set to "1":
+ - initiate the STATUS PDU transfer procedure.
+- if a piggybacked STATUS PDU is included in the AMD PDU:
+ - perform the actions specified in subclause 11.5.3.
+
+#### 11.3.4.9 Full Buffer Behavior
+
+It is foreseen that in some conditions, e.g. when the window size is re-configured, the UE may have memory limitations.
+
+While the buffer memory is full:
+
+- the UE is not required to segment RLC SDUs into AMD PDUs as per Subclause 11.3.2;
+- the UE shall:
+ - be able to process incoming AMD PDUs (especially to be able to process and store the AMD PDU with "Sequence Number" = VR(R));
+ - operate according to the normal protocol, e.g. process STATUS reports and perform retransmissions;
+- the UE may discard received AMD PDUs with "Sequence Number" within the receiving window and consider the discarded AMD PDUs as not having been received.
+
+#### 11.3.4.10 Invalid PDU size
+
+In the UE, if "fixed RLC PDU size" has been configured and if a received AMD PDU has a size different from the configured "downlink AMD PDU size", the Receiver shall:
+
+- ignore that AMD PDU.
+
+### 11.3.5 Transmission of POLL SUFF
+
+Each time a STATUS PDU containing the POLL SUFF is scheduled for transmission, the Sender shall:
+
+- increment the value of the corresponding VT(DAT) of the AMD PDU with sequence number equal to VT(S)-1;
+- if VT(DAT) = MaxDAT:
+ - perform the actions specified in subclause 11.3.3a;
+- else:
+ - notify the lower layer that STATUS PDU is available for transmission.
+
+## 11.4 RLC reset procedure
+
+### 11.4.1 General
+
+The RLC reset procedure is used to reset two RLC peer entities, which are operating in acknowledged mode. Figure 11.4 below illustrates the elementary procedure for an RLC reset. During the reset procedure the hyper frame numbers (HFN) in UTRAN and UE are synchronised. Two HFNs used for ciphering needs to be synchronised, DL HFN in downlink and UL HFN in uplink. In the reset procedure, the highest UL HFN and DL HFN used by the RLC entity in the transmitting sides, i.e. the HFNs associated with AMD PDUs of "Sequence Number"=VT(S)-1 if at least one AMD PDU had been transmitted or of "Sequence Number"=0 if no AMD PDU had been transmitted, are exchanged between UE and UTRAN.
+
+The RESET PDUs and the RESET ACK PDUs have higher priority than AMD PDUs.
+
+
+
+```
+
+sequenceDiagram
+ participant Sender
+ participant Receiver
+ Note left of Sender: [Lower Layer]
+ Note right of Receiver: [Lower Layer]
+ Sender->>Receiver: RESET
+ Receiver->>Sender: RESET ACK
+
+```
+
+Sequence diagram of the RLC reset procedure. A 'Sender' box is on the left and a 'Receiver' box is on the right. A horizontal arrow labeled 'RESET' points from the Sender to the Receiver. A horizontal arrow labeled 'RESET ACK' points from the Receiver back to the Sender. Below each box is a grey rectangular block representing the lower layers.
+
+Figure 11.4: RLC reset procedure
+
+### 11.4.2 Initiation
+
+The Sender shall:
+
+- if one of the following triggers is detected:
+ - 1) "No\_Discard after MaxDAT number of transmissions" is configured and VT(DAT) equals the value MaxDAT (see subclause 9.7.3.4);
+ - 2) VT(MRW) equals the value MaxMRW;
+ - 3) A STATUS PDU or a piggybacked STATUS PDU including "erroneous Sequence Number" is received (see clause 10);
+ - stop transmitting any AMD PDU or STATUS PDU;
+ - ignore any incoming AMD PDU, piggybacked STATUS PDU or STATUS PDU;
+ - increment VT(RST) by 1;
+ - if VT(RST) = MaxRST:
+ - perform the actions specified in subclause 11.4.4a.
+ - else (if VT(RST) < MaxRST):
+ - submit a RESET PDU to the lower layer;
+ - start the timer Timer\_RST according to the description in subclause 9.5.
+
+NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC reset procedure until the end of the next TTI.
+
+When a reset procedure has been initiated it can only be ended upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, upon request of re-establishment due to request of re-establishment (for the whole RLC entity or for only the transmitting or receiving side of the RLC entity), or release from upper layer. A reset procedure is not interrupted by the reception of a RESET PDU from the peer entity.
+
+#### 11.4.2.1 RESET PDU contents to set
+
+The Sender shall:
+
+- set the HFNI field to the currently highest used HFN (DL HFN when the RESET PDU is sent by UTRAN or UL HFN when the RESET PDU is sent by the UE);
+- set the RSN field to the sequence number of the RESET PDU. The sequence number of the first RESET PDU after the AM entity is established or re-established (for the whole RLC entity or for only the transmitting or receiving side of the RLC entity) shall be "0". This sequence number is incremented every time a new RESET PDU is transmitted, but not when a RESET PDU is retransmitted.
+
+### 11.4.3 Reception of the RESET PDU by the Receiver
+
+Upon reception of a RESET PDU the Receiver shall:
+
+- if the RESET PDU is not the first RESET PDU received since the entity was established or re-established; and
+- if the RSN value in the RESET PDU is the same as the RSN value in the last received RESET PDU:
+ - only submit a RESET ACK PDU to the lower layer with the contents set exactly as in the last transmitted RESET ACK PDU (i.e., in this case the RLC entity is not reset).
+- if the RESET PDU is the first RESET PDU received since the entity was established or re-established; or
+- if the RSN value is different from the RSN value in the last received RESET PDU:
+ - submit a RESET ACK PDU to the lower layer with the content set as specified in subclause 11.4.3.1;
+ - reset the state variables described in subclause 9.4 except VT(RST) to their initial values;
+ - stop all the timers described in subclause 9.5 except Timer\_RST, Timer\_Discard, Timer\_Poll\_Periodic and Timer\_Status\_Periodic;
+
+- reset configurable parameters to their configured values;
+- discard all RLC PDUs in the receiving side of the AM RLC entity;
+- discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity;
+- if requested for the transmitting side:
+ - inform the upper layers of the discarded SDUs.
+- set the HFN (DL HFN when the RESET PDU is received in UE or UL HFN when the RESET PDU is received in UTRAN) equal to the HFNI field in the received RESET PDU;
+- increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first transmitted and received AMD PDUs after the reset procedure.
+
+NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side of the AM RLC entity until the end of the next TTI.
+
+#### 11.4.3.1 RESET ACK PDU contents to set
+
+The RLC entity shall:
+
+- set the hyper frame number indicator field (HFNI) to the currently highest used HFN (DL HFN when the RESET ACK PDU is sent by UTRAN or UL HFN when the RESET ACK PDU is sent by the UE);
+- set the RSN field to the same value as in the corresponding received RESET PDU.
+
+### 11.4.4 Reception of the RESET ACK PDU by the Sender
+
+Upon reception of a RESET ACK PDU, the Sender shall:
+
+- if the Sender has already transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK PDU:
+ - if the received RSN value is the same as the one in the corresponding RESET PDU:
+ - set the HFN value (DL HFN when the RESET ACK PDU is received in UE or UL HFN when the RESET ACK PDU is received in UTRAN) to the HFNI field of the received RESET ACK PDU;
+ - reset the state variables described in subclause 9.4 to their initial values;
+ - stop all the timers described in subclause 9.5 except Timer\_Discard, Timer\_Poll\_Periodic and Timer\_Status\_Periodic;
+ - reset configurable parameters to their configured values;
+ - discard all RLC PDUs in the receiving side of the AM RLC entity;
+ - discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity;
+ - if requested for the transmitting side:
+ - inform the upper layers of the discarded SDUs.
+ - increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first transmitted and received AMD PDUs after the reset procedure;
+ - otherwise (if the received RSN value is not the same as the one in the corresponding RESET PDU):
+ - discard the RESET ACK PDU;
+
+- otherwise (if the Sender has not transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK PDU):
+ - discard the RESET ACK PDU.
+
+NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side until the end of the next TTI.
+
+### 11.4.4a Reached maximum number of attempts
+
+If VT(RST) = MaxRST, the Sender shall:
+
+- terminate the ongoing RLC RESET procedure;
+- stop the timer Timer\_RST if it was started;
+- indicate unrecoverable error to upper layer.
+
+### 11.4.5 Abnormal cases
+
+#### 11.4.5.1 Timer\_RST timeout
+
+If Timer\_RST expires before the reset procedure is terminated, the Sender shall:
+
+- increment VT(RST) by one;
+- if VT(RST) < MaxRST:
+ - set the RESET PDU as previously transmitted;
+ - transmit the RESET PDU;
+ - restart Timer\_RST according to the description in subclause 9.5.
+- else (if VT(RST) = MaxRST):
+ - perform the actions specified in subclause 11.4.4a.
+
+#### 11.4.5.2 Void
+
+#### 11.4.5.3 Reception of the RESET PDU by the Sender
+
+Upon reception of a RESET PDU, the Sender shall:
+
+- submit a RESET ACK PDU to the lower layer with the content set as specified in subclause 11.4.3.1;
+- reset the state variables described in subclause 9.4 except VT(RST) to their initial values;
+- stop all the timers described in subclause 9.5 except Timer\_RST, Timer\_Discard, Timer\_Poll\_Periodic and Timer\_Status\_Periodic;
+- reset configurable parameters to their configured values;
+- discard all RLC PDUs in the receiving side of the AM RLC entity;
+- discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity;
+- if requested for the transmitting side:
+ - inform the upper layers of the discarded SDUs.
+- set the HFN (DL HFN when the RESET PDU is received in UE or UL HFN when the RESET PDU is received in UTRAN) equal to the HFNI field in the received RESET PDU.
+
+NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side until the end of the next TTI.
+
+## 11.5 STATUS report transfer procedure
+
+### 11.5.1 General
+
+The status report transfer procedure is used for transferring of status information between two RLC peer entities, which are operating in acknowledged mode. Figure 11.5 below illustrates the elementary procedure for status report transfer. A status report consists of one or several STATUS PDUs.
+
+In case two logical channels are configured in the uplink, only acknowledgement status reports, MRW ACK SUFI and WINDOW SUFI shall be transmitted on the second logical channel. In case two logical channels are configured in the downlink, control PDUs can be transmitted on any of the two logical channels.
+
+The STATUS PDUs have higher priority than AMD PDUs.
+
+
+
+```
+
+graph LR
+ Sender[Sender]
+ Receiver[Receiver]
+ Receiver -- STATUS PDU --> Sender
+ subgraph LowerLayers
+ direction TB
+ L1[ ]
+ L2[ ]
+ end
+ Sender --- L1
+ Receiver --- L2
+ style L1 fill:#888,stroke:none
+ style L2 fill:#888,stroke:none
+
+```
+
+Diagram illustrating the Status report transfer procedure. A Sender (top left) and a Receiver (top right) are shown. A horizontal arrow labeled 'STATUS PDU' points from the Receiver to the Sender. Below each entity is a grey rectangular block representing the lower layers.
+
+Figure 11.5: Status report transfer procedure
+
+### 11.5.2 Initiation
+
+The Receiver shall:
+
+- if one of the following triggers is detected:
+ - 1) The "Polling bit" in a received AMD PDU is set to "1";
+ - 2) "Missing PDU Indicator" is configured and a missing AMD PDU is detected;
+ - 3) The "Timer based STATUS transfer" is configured and the timer Timer\_Status\_Periodic has expired:
+ - act on the trigger as specified in subclause 9.7.2.
+ - 4) Void
+ - 5) If the flexible RLC PDU size is configured and POLL SUFI is received:
+ - consider that Poll\_SN has been transmitted by the sender as specified in subclause 9.4:
+ - act on the trigger as specified in subclause 9.7.2.
+
+#### 11.5.2.1 Piggybacked STATUS PDU
+
+The Receiver may:
+
+- if STATUS PDU(s) to be sent fit into padding octets in AMD PDU(s) to be sent:
+ - piggyback a STATUS PDU on the AMD PDU to be sent.
+
+Submission of a piggybacked STATUS PDU in an AMD PDU to the lower layer follows the same rules as an ordinary STATUS PDU.
+
+#### 11.5.2.2 STATUS PDU contents to set
+
+On triggering of a status report, the Receiver shall:
+
+- if the "STATUS prohibit" is not active:
+
+- If Timer\_Reordering is not configured:
+ - include negative acknowledgements for all AMD PDUs detected as missing;
+ - include an ACK SUFI positively acknowledging all AMD PDUs received up to at least VR(R);
+- If Timer\_Reordering is configured, for all SN such that VR(R) <= SN < VR(MS):
+ - include negative acknowledgements for all AMD PDUs detected as missing;
+ - include an ACK SUFI positively acknowledging all AMD PDUs received up to at least VR(R);
+- if an MRW SUFI assembled as specified in subclause 11.6.2.2 had not been sent:
+ - optionally include the MRW SUFI;
+- if an MRW\_ACK SUFI assembled as specified in subclause 11.6.2.2 is awaiting transmission:
+ - optionally include the MRW\_ACK SUFI;
+- if the Sender's transmission window is to be updated:
+ - optionally include the WINDOW SUFI;
+- if all SUFIs can be accommodated in one STATUS PDU:
+ - construct the status report using one STATUS PDU, using one of the allowed PDU sizes;
+ - if the SUFIs included do not fill the entire STATUS PDU:
+ - if the STATUS PDU is not terminated with an ACK SUFI:
+ - terminate the STATUS PDU with a NO\_MORE SUFI.
+ - use padding in the remainder of the STATUS PDU (padding size may be zero);
+- otherwise (the status report is segmented):
+ - construct STATUS PDUs including only complete SUFIs using one of the allowed PDU sizes. The set of STATUS PDUs shall accommodate all the SUFIs to form the complete status report. Indication of the same AMD PDU shall not be given in more than one STATUS PDU of a status report, but the ACK SUFI can be present in more than one STATUS PDU of a status report;
+ - if any STATUS PDU constructed is not entirely filled with SUFIs:
+ - if the STATUS PDU is not terminated with an ACK SUFI:
+ - terminate that STATUS PDU with a NO\_MORE SUFI.
+ - use padding in the remainder of that STATUS PDU (padding size may be zero).
+
+Which SUFI fields to use is implementation dependent. Bitmap SUFI is used to indicate both received and/or missing AMD PDUs. List SUFI and/or Relative List SUFI are used to indicate missing AMD PDUs only. Acknowledgement SUFI is used to indicate the received AMD PDUs. (For SUFI details see 9.2.2.11.)
+
+#### 11.5.2.3 Submission of STATUS PDUs to the lower layer
+
+The Receiver shall:
+
+- inform the lower layer of the STATUS PDUs scheduled for transmission;
+- submit to the lower layer, the requested number of PDUs (STATUS PDUs, piggybacked AMD/STATUS PDUs and optionally AMD PDUs, see also subclause 11.3.2.2);
+- if "Timer based STATUS transfer" is configured and the timer Timer\_Status\_Periodic has expired:
+ - restart the timer Timer\_Status\_Periodic according to subclause 9.5 f);
+
+- if the STATUS PDU includes the MRW SUFI:
+ - start the timer Timer\_MR\_W according to subclause 9.5 i).
+
+### 11.5.3 Reception of the STATUS PDU by the Sender
+
+Upon reception of the STATUS PDU/piggybacked STATUS PDU, the Sender shall:
+
+- if an RLC SDU is positively acknowledged by the STATUS PDU:
+ - if requested:
+ - inform the upper layers of the reception of the RLC SDU by the peer AM RLC entity.
+- update the state variables VT(A) and VT(MS) according to the received STATUS PDU/piggybacked STATUS PDU;
+- if the STATUS PDU includes negatively acknowledged AMD PDUs:
+ - initiate the acknowledged data transfer procedure; and
+ - retransmit these AMD PDUs. Retransmitted AMD PDUs shall have higher priority than AMD PDUs to be transmitted for the first time;
+ - if an AMD PDU is negatively acknowledged more than once in a STATUS PDU:
+ - retransmit the AMD PDU only once.
+- if the STATUS PDU includes the MRW SUFI:
+ - take the actions specified in subclause 11.6.3.
+- if the STATUS PDU includes the MRW\_ACK SUFI:
+ - take the actions specified in subclause 11.6.4.
+- if the STATUS PDU includes the WINDOW SUFI:
+ - update the current transmission window size, VT(WS).
+
+### 11.5.4 Abnormal cases
+
+#### 11.5.4.1 Void
+
+## 11.6 SDU discard with explicit signalling procedure
+
+### 11.6.1 General
+
+The SDU discard with explicit signalling procedure is used for discarding SDUs and transferring the discard information between two peer entities, which are operating in acknowledged mode. The Sender shall discard an SDU that has not been successfully transmitted for a period of time or for a number of transmissions, and send a Move Receiving Window (MRW) SUFI to the Receiver. According to the MRW SUFI, the Receiver shall discard AMD PDUs carrying that SDU and update the reception window. Figure 11.6 below illustrates the elementary procedure for SDU discard with explicit signalling.
+
+
+
+```
+
+sequenceDiagram
+ participant Sender
+ participant Receiver
+ Sender->>Receiver: STATUS PDU (MRW SUFI)
+ Receiver-->>Sender: STATUS PDU (MRW_ACK SUFI)
+
+```
+
+Sequence diagram illustrating SDU discard with explicit signalling. A Sender sends a STATUS PDU (MRW SUFI) to a Receiver, which responds with a STATUS PDU (MRW\_ACK SUFI).
+
+**Figure 11.6: SDU discard with explicit signalling**
+
+### 11.6.2 Initiation
+
+The Sender shall initiate the SDU discard with explicit signalling procedure if one of the following triggers is detected:
+
+- "Timer based SDU discard with explicit signalling" is configured, *Timer\_Discard* expires for an SDU, and one or more segments of the SDU have been submitted to lower layer;
+- "Timer based SDU discard with explicit signalling" is configured, *Timer\_Discard* expires for an SDU, and "Send MRW" is configured;
+- "SDU discard after MaxDAT number of transmissions" is configured, and MaxDAT number of transmissions is reached (i.e. $VT(DAT) \geq MaxDAT$ ) for an AMD PDU.
+
+Upon initiation of the SDU discard with explicit signalling procedure, the Sender shall:
+
+- if "Timer based SDU discard with explicit signalling" is configured:
+ - discard all SDUs up to and including the SDU for which the timer *Timer\_Discard* expired.
+- if "SDU discard after MaxDAT number of transmissions" is configured:
+ - discard all SDUs that have segments or "Length Indicators" indicating the end of the SDUs in AMD PDUs with "Sequence Number" SN inside the interval $VT(A) \leq SN \leq X$ , where X is the value of the "Sequence Number" of the AMD PDU with $VT(DAT) \geq MaxDAT$ .
+- if requested:
+ - inform the upper layers of the discarded SDUs
+- discard all AMD PDUs including segments of the discarded SDUs or "Length Indicators" indicating the end of the SDUs, unless they also carry a segment of a SDU which is not discarded;
+- if more than 15 discarded SDUs are to be informed to the Receiver (see subclause 11.6.2.2):
+ - if "Send MRW" is not configured:
+ - assemble an MRW SUFI with the discard information of the SDUs.
+ - otherwise ("Send MRW" is configured):
+ - assemble an MRW SUFI with the discard information of the first 15 SDUs; and
+ - include the discard information of the rest SDUs in another MRW SUFI which shall be sent by the next SDU discard with explicit signalling procedure (after the current SDU discard with explicit signalling procedure is terminated).
+- otherwise (less than or equal to 15 discarded SDUs are to be informed to the Receiver):
+ - assemble an MRW SUFI with the discard information of the SDUs.
+- schedule and submit to lower layer a STATUS PDU/piggybacked STATUS PDU containing the MRW SUFI;
+- if $SN\_MRW_{LENGTH}$ in the MRW SUFI $> VT(S)$ :
+
+- update VT(S) to SN\_MRWLENGTH.
+- start a timer Timer\_MRW according to subclause 9.5.
+
+If a new SDU discard with explicit signalling procedure is triggered when the current SDU discard with explicit signalling procedure is still going on, no new MRW SUFI shall be sent before the current SDU discard with explicit signalling procedure is terminated by one of the termination criteria specified in subclause 11.6.4.
+
+#### 11.6.2.1 Void
+
+#### 11.6.2.2 STATUS PDU contents to set
+
+The Sender shall:
+
+- if "Send MRW" is configured:
+ - if no new SDU is present inside the AMD PDU which contains the "Length Indicator" of the last discarded SDU or if the AMD PDU contains the special value of the HE field to indicate the end of the last discarded SDU:
+ - set the last SN\_MRWi field in the MRW SUFI to 1 + "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last discarded SDU or the special value of the HE field to indicate the end of the last discarded SDU;
+ - set the NLENGTH field in the MRW SUFI to "0000".
+ - otherwise:
+ - set the last SN\_MRWi field in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last discarded SDU;
+ - set the NLENGTH field in the MRW SUFI so that the last data octet to be discarded in the Receiver shall be the octet indicated by the NLENGTH:th "Length Indicator" field of the AMD PDU which contains the "Length Indicator" of the last discarded SDU;
+ - set each of the other SN\_MRWi fields in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the i:th discarded SDU or the special value of the HE field to indicate the end of the i:th discarded SDU.
+- otherwise ("Send MRW" is not configured):
+ - if no new SDU is present inside the AMD PDU which contains the "Length Indicator" of the last discarded SDU or if the AMD PDU contains the special value of the HE field to indicate the end of the last discarded SDU:
+ - set the last SN\_MRWi field in the MRW SUFI to 1 + "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last SDU to be discarded in the Receiver or the special value of the HE field to indicate the end of the last discarded SDU;
+ - set the NLENGTH field in the MRW SUFI to "0000".
+ - otherwise:
+ - set the last SN\_MRWi field in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last SDU to be discarded in the Receiver;
+ - set the NLENGTH field in the MRW SUFI so that the last data octet to be discarded in the Receiver shall be the octet indicated by the NLENGTH:th "Length Indicator" field of the AMD PDU which contains the "Length Indicator" of the last SDU to be discarded in the Receiver;
+ - optionally set each of the other SN\_MRWi fields in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" or the special value of the HE field to indicate the end of the i:th SDU to be discarded in the Receiver;
+
+- if the MRW SUFI contains only one SN\_MRWi field and the value of SN\_MRWi field $\geq$ VT(A)+Configured\_Tx\_Window\_Size:
+ - set the LENGTH field in the MRW SUFI to "0000".
+- otherwise:
+ - set the LENGTH field in the MRW SUFI to the number of SN\_MRWi fields in the same MRW SUFI. In this case, SN\_MRWi shall be in the interval $VT(A) \leq SN\_MRWi < VT(A)+Configured\_Tx\_Window\_Size$ .
+
+### 11.6.3 Reception of the STATUS PDU by the Receiver
+
+Upon reception of the STATUS PDU/piggybacked STATUS PDU containing an MRW SUFI, the Receiver shall:
+
+- if the LENGTH field in the received MRW SUFI is "0000":
+ - consider SN\_MRWi to be above or equal to VR(R).
+- otherwise:
+ - consider SN\_MRWi to be less than VR(MR);
+- consider all the SN\_MRWi other than SN\_MRWi to be in sequential order within the list and sequentially above or equal to SN\_MRWi-1;
+- deliver all the successfully received SDUs from the SDU that have segments or "Length Indicators" indicating the end of the SDUs in AMD PDU with "Sequence Number" of VR(R) up to and including the last SDU that is indicated by the MRW SUFI;
+- discard AMD PDUs up to and including the PDU with sequence number SN\_MRWLENGTH-1;
+- if the NLENGTH field in the received MRW SUFI is "0000":
+ - reassemble from the first data octet of the AMD PDU with sequence number SN\_MRWLENGTH after the discard.
+- otherwise:
+ - discard further the data octets in the AMD PDU with sequence number SN\_MRWLENGTH up to and including the octet indicated by the NLENGTH:th "Length Indicator" field of the PDU with sequence number SN\_MRWLENGTH;
+ - reassemble from the succeeding data octet in the AMD PDU with sequence number SN\_MRWLENGTH after the discard;
+- if "Send MRW" is configured:
+ - inform upper layers about all of the discarded SDUs that were not previously delivered to upper layer or discarded by other MRW SUFIs;
+- update the state variables VR(R), VR(H) and VR(MR) according to the received STATUS PDU/piggybacked STATUS PDU;
+- assemble a MRW\_ACK SUFI according to subclause 11.6.3.1;
+- schedule and submit to lower layer a STATUS PDU/piggybacked STATUS PDU containing the MRW\_ACK SUFI.
+
+#### 11.6.3.1 STATUS PDU contents to set
+
+The Receiver shall:
+
+- set the SN\_ACK field in the MRW\_ACK SUFI to the new value of VR(R), updated after reception of the MRW SUFI;
+- if the SN\_ACK field in the MRW\_ACK SUFI is set equal to the SN\_MRWLENGTH field in the received MRW SUFI:
+
+- set the N field in the MRW\_ACK SUFI to the NLENGTH field in the received MRW SUFI.
+- otherwise:
+ - set the N field in the MRW\_ACK SUFI to "0000".
+- include the MRW\_ACK SUFI in the next STATUS PDU/piggybacked STATUS PDU to be transmitted, according to subclause 11.5.2.
+
+### 11.6.4 Termination
+
+The Sender shall terminate the SDU discard with explicit signalling procedure if one of the following criteria is fulfilled:
+
+- a STATUS PDU/piggybacked STATUS PDU containing an MRW\_ACK SUFI is received, and the SN\_ACK field in the received MRW\_ACK SUFI > the SN\_MRWLENGTH field in the transmitted MRW\_SUFI, and the N field in the received MRW\_ACK SUFI is set equal to "0000";
+- a STATUS PDU/piggybacked STATUS PDU containing an MRW\_ACK SUFI is received, and the SN\_ACK field in the received MRW\_ACK SUFI = the SN\_MRWLENGTH field in the transmitted MRW\_SUFI, and the N field in the received MRW\_ACK SUFI is set equal to the NLENGTH field in the transmitted MRW\_SUFI;
+- a STATUS PDU/piggybacked STATUS PDU containing an ACK SUFI is received, and this STATUS PDU/piggybacked STATUS PDU indicates that all AMD PDUs up to and including the AMD PDU with "Sequence Number" equal to (SN\_MRWLENGTH field in the transmitted MRW\_SUFI) – 1 has been received or discarded by the peer entity.
+
+Upon termination of the SDU discard with explicit signalling procedure, the Sender shall:
+
+- stop the timer Timer\_MRW;
+- update VT(A) and VT(MS) according to the received STATUS PDU/piggybacked STATUS PDU;
+
+The Sender shall not confirm to upper layers the SDUs that are requested to be discarded.
+
+### 11.6.4a Reached maximum number of attempts
+
+If VT(MRW) = MaxMRW, the Sender shall:
+
+- terminate the SDU discard with explicit signalling procedure;
+- stop the timer Timer\_MRW if it was started;
+- initiate the RLC RESET procedure (see subclause 11.4).
+
+### 11.6.5 Expiration of timer Timer\_MRW
+
+If Timer\_MRW expires before the discard procedure is terminated, the Sender shall:
+
+- increment VT(MRW) by one;
+- if VT(MRW) < MaxMRW:
+ - set the MRW SUFI as previously transmitted (even if additional SDUs were discarded in the mean-time);
+ - include the MRW SUFI in a new status report (if other SUFIs are included, their contents shall be updated);
+ - transmit the status report by either including it in a STATUS PDU or piggybacked in an AMD PDU;
+ - restart Timer\_MRW for this discard procedure according to the description in subclause 9.5.
+- else (if VT(MRW) = MaxMRW):
+ - perform the actions specified in subclause 11.6.4a.
+
+### 11.6.6 Abnormal cases
+
+#### 11.6.6.1 Reception of obsolete/corrupted MRW SUFI by the Receiver
+
+If the received MRW SUFI contains outdated information about the reception window (reception window already moved further than MRW SUFI is indicating), the Receiver shall:
+
+- discard the MRW SUFI;
+- set the SN\_ACK field in the MRW\_ACK SUFI to the current value of VR(R);
+- set the N field in the MRW\_ACK SUFI to "0000";
+- include the MRW\_ACK SUFI in the next STATUS PDU/piggybacked STATUS PDU to be transmitted, according to subclause 11.5.2.
+
+#### 11.6.6.2 Void
+
+#### 11.6.6.3 Reception of obsolete/corrupted MRW\_ACK SUFI by the Sender
+
+The Sender shall discard the received MRW\_ACK SUFI if one of the following cases occurs:
+
+- no ongoing SDU discard with explicit signalling procedure; or
+- the SN\_ACK field in the received MRW\_ACK SUFI < the SN\_MRWLENGTH field in the transmitted MRW SUFI; or
+- the SN\_ACK field in the received MRW\_ACK SUFI = the SN\_MRWLENGTH field in the transmitted MRW SUFI, and the N field in the received MRW\_ACK SUFI is not equal to the NLENGTH field in the transmitted MRW SUFI; or
+- the SN\_ACK field in the received MRW\_ACK SUFI > the SN\_MRWLENGTH field in the transmitted MRW SUFI, and the N field in the received MRW\_ACK SUFI is not equal to "0000".
+
+## 11.7 Void
+
+## 11.8 Void
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|-----|-----|----------------------------------------------------------------------|-------|-------|--|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | |
+| 10/1999 | RP-05 | RP-99465 | - | | Approved at TSG-RAN #5 and placed under Change Control | - | 3.0.0 | |
+| 12/1999 | RP-06 | RP-99641 | 001 | | RLC: Editorial corrections | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99641 | 002 | 1 | Editorial changes on RLC protocol specification | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99643 | 003 | 1 | MRW procedure | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99643 | 004 | | SDU Discard Functionality | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99643 | 005 | 2 | Change in RLC control PDU format | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99642 | 006 | 1 | Editorial corrections regarding CTCH | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99641 | 007 | | Updated RLC SDL | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99642 | 011 | | RLC Editorial Changes | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99642 | 013 | | Editorial Modification on RLC specification | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99641 | 014 | | Editorial changes | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99642 | 015 | | Change to one PU in a AMD PDU | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99643 | 016 | 1 | Introduction of RLC suspend state | 3.0.0 | 3.1.0 | |
+| | RP-06 | RP-99641 | 017 | 1 | RLC editorial corrections | 3.0.0 | 3.1.0 | |
+| 01/2000 | - | - | - | | Editorial corrections in title and Annex A (SDL) | 3.1.0 | 3.1.1 | |
+| | - | - | - | | Correction of persistent error regarding SDL in Table of Contents | 3.1.1 | 3.1.2 | |
+| 03/2000 | RP-07 | RP-000040 | 018 | 1 | RLC editorial changes | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 021 | 1 | Corrections to RLC | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 025 | 2 | Corrections to RLC | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 026 | 1 | STATUS PDUs | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 027 | 1 | Clarification of RLC AMD Model | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 028 | | Corrections to Timer discard procedures | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 029 | 1 | Segmentation of RLC SDUs | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 030 | 2 | Modification of SDU discard to support virtual PDCP sequence numbers | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 031 | | Removal of SCCH | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 032 | | Updated RLC SDL | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 033 | 1 | RLC Editorial Changes | 3.1.2 | 3.2.0 | |
+| | RP-07 | RP-000040 | 034 | | Order of bit transmission for RLC PDUs | 3.1.2 | 3.2.0 | |
+| 06/2000 | RP-08 | RP-000220 | 038 | | Corrections to RLC | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 039 | | Correction to the description of the MRW SUFI fields | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 040 | 1 | Editorial corrections to length indicators and local suspend rate | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 041 | 4 | Clarification of the RESET PDU | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 043 | 1 | Clarification of RLC/MAC interaction | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 044 | 2 | General RLC corrections | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 045 | | Clarification of RLC Transparent Mode operation | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 048 | | Editorial corrections to abbreviations, SCCH, BCCH | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 052 | | Updated RLC SDL | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 053 | | Correction to RLC | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 055 | | RLC Logical Channel mapping | 3.2.0 | 3.3.0 | |
+| | RP-08 | RP-000220 | 057 | | Correction of EPC timer mechanism | 3.2.0 | 3.3.0 | |
+| 09/2000 | RP-09 | RP-000358 | 059 | 1 | State variables after window change | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 060 | 4 | SDU discard | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 061 | 5 | General RLC corrections | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 066 | | Editorial changes to RLC | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 067 | 4 | Correction to RLC window size range | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 068 | 2 | Window based polling | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 070 | 2 | General corrections to RLC | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 071 | | State Transition in RLC Acknowledged Mode | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 073 | | Clarification of the Length Indicators | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 076 | 1 | RLC corrections | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 077 | 1 | Corrections to reset procedure and length indicator definitions | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 078 | | RLC Modes for SHCCH | 3.3.0 | 3.4.0 | |
+| | RP-09 | RP-000358 | 079 | | CCCH in UM RLC | 3.3.0 | 3.4.0 | |
+| 12/2000 | RP-10 | RP-000568 | 080 | 1 | Length Indicator and PDU formats | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 083 | 3 | Clarification to the Estimated PDU Counter | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 084 | 2 | Model of UM and AM entities | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 085 | 1 | General RLC corrections | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 086 | 1 | General RLC corrections | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 087 | 5 | RLC timers | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 088 | 1 | Reset procedure | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 089 | 1 | Editorial corrections to RLC | 3.4.0 | 3.5.0 | |
+| | RP-10 | RP-000568 | 090 | 2 | RLC UM protocol | 3.4.0 | 3.5.0 | |
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| | RP-10 | RP-000568 | 092 | 2 | Clarification to window size parameters, MRW SUFI and window based polling | 3.4.0 | 3.5.0 |
+| | RP-10 | RP-000568 | 093 | 3 | General RLC Corrections | 3.4.0 | 3.5.0 |
+| | RP-10 | RP-000568 | 094 | 1 | RLC Reset handling | 3.4.0 | 3.5.0 |
+| | RP-10 | RP-000568 | 095 | | Inclusion of stage 3 for ciphering | 3.4.0 | 3.5.0 |
+| 03/2001 | RP-11 | RP-010026 | 097 | 1 | Clarification on LIST SUFI and RLIST SUFI | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 098 | 1 | Corrections and clarifications for SDU discard without explicit signalling | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 099 | 1 | Tr mode operation | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 100 | 1 | Timer based discard with explicit signalling | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 101 | | Annex updates | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 103 | | Clarification on MRW SUFI and SDU discard procedure | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 104 | 1 | General clarification on SN arithmetic comparison | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 105 | 2 | General clarification on RLC header and PDU header | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 106 | 1 | Clarification on the primitives between RLC and higher layers | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 107 | 1 | Clarification on the model of AM entity | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 109 | 2 | Clarification on UMD transfer procedure | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 110 | 1 | RLC status transmission in CELL_PCH and URA_PCH | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 111 | | Re-establishment description | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 112 | 1 | Clarifications on the RESET and RESET ACK PDU sizes | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 113 | 1 | Editorial corrections and clarifications | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 114 | 1 | Clarifications on the RLC-AM-DATA-Conf primitive | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 116 | | Removal of the payload unit concept | 3.5.0 | 3.6.0 |
+| | RP-11 | RP-010026 | 118 | 2 | Padding Blocks and TFC selection pre-empting | 3.5.0 | 3.6.0 |
+| | RP-11 | - | - | | Upgrade to Release 4 - no technical change | 3.6.0 | 4.0.0 |
+| 06/2001 | RP-12 | RP-010309 | 120 | | Clarification on ACK SUFI | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 122 | | MRW SUFI clarification and enhancement | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 124 | | Clarification on AM states | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 126 | | Clarification on HFN update in RESET procedure | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 128 | | Clarification of RLC Discard | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 130 | | Removal of reference to RRC | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 132 | | Clarification in the LI Parameters section | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 136 | | Cleanup of RLC services and functions | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 138 | | Clarification on RLC re-establishment | 4.0.0 | 4.1.0 |
+| | RP-12 | RP-010309 | 140 | | Corrections and clarifications to the LIST and RLIST SUFI types | 4.0.0 | 4.1.0 |
+| 09/2001 | RP-13 | RP-010542 | 142 | | General clarifications | 4.1.0 | 4.2.0 |
+| | RP-13 | RP-010542 | 150 | | Correction to RLC state variables | 4.1.0 | 4.2.0 |
+| 12/2001 | RP-14 | RP-010761 | 152 | | General clarifications | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010761 | 156 | | Send state variable for Timer_Poll and window based polling | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010761 | 158 | | Unexpected data interruption during transmission scheduling | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010761 | 162 | | UE-ID Type Indicator | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010761 | 164 | | Removal of obsolete Send MRW option | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010771 | 160 | | Content of retransmitted RESET ACK PDU | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010771 | 166 | | Usage of UM RLC Special Length Indicator | 4.2.0 | 4.3.0 |
+| | RP-14 | RP-010771 | 170 | | Indication of SDU transmission result | 4.2.0 | 4.3.0 |
+| 03/2002 | RP-15 | RP-020068 | 172 | | Clarification on MRW SUFI and SDU discard with explicit signalling procedure | 4.3.0 | 4.4.0 |
+| | RP-15 | RP-020068 | 176 | | SDU discard termination | 4.3.0 | 4.4.0 |
+| | RP-15 | RP-020068 | 180 | | Initial value of VT(US) | 4.3.0 | 4.4.0 |
+| | RP-15 | - | - | | Upgrade to Release 5 - no technical change | 4.4.0 | 5.0.0 |
+| 06/2002 | RP-16 | RP-020327 | 186 | | Handling abnormal UMD PDUs and AMD PDUs | 5.0.0 | 5.1.0 |
+| | RP-16 | RP-020327 | 189 | | Clarification of the use of Length Indicators | 5.0.0 | 5.1.0 |
+| | RP-16 | RP-020327 | 192 | 1 | Correction to MaxDAT, MaxRST and MaxMRW | 5.0.0 | 5.1.0 |
+| | RP-16 | RP-020327 | 195 | | Clarification on polling functions | 5.0.0 | 5.1.0 |
+| 09/2002 | RP-17 | RP-020539 | 198 | | Correction to the behaviour after expiration of Timer_MRW during the SDU discard with explicit signalling procedure | 5.1.0 | 5.2.0 |
+| | RP-17 | RP-020539 | 201 | | Corrections to RLC retransmissions | 5.1.0 | 5.2.0 |
+| | RP-17 | RP-020637 | 204 | 1 | Corrections to RLC RESET procedure and Length Indicators | 5.1.0 | 5.2.0 |
+| | RP-17 | RP-020539 | 207 | | Corrections on handling of timers during a RLC reset or re-establishment | 5.1.0 | 5.2.0 |
+| | RP-17 | RP-020551 | 209 | | Corrections on indication of SDU transmission result | 5.1.0 | 5.2.0 |
+| 12/2002 | RP-18 | RP-020719 | 212 | | RB id in ciphering | 5.2.0 | 5.3.0 |
+| | RP-18 | RP-020862 | 213 | | Generation of RLC Status Reports to coordinate with MAC-hs reset | 5.2.0 | 5.3.0 |
+| 03/2003 | RP-19 | RP-030101 | 216 | | Correction to VT(MRW) definition | 5.3.0 | 5.4.0 |
+| | RP-19 | RP-030116 | 217 | | Enhancement of MRW procedure | 5.3.0 | 5.4.0 |
+| 06/2003 | RP-20 | RP-030292 | 220 | 2 | Handling of erroneous PDUs | 5.4.0 | 5.5.0 |
+| | RP-20 | RP-030292 | 225 | | Setting of the "Polling bit" in the "Every Poll_SDU SDU" function | 5.4.0 | 5.5.0 |
+| | RP-20 | RP-030297 | 222 | | Receiver behaviour when detecting an AMD PDU duplicate | 5.4.0 | 5.5.0 |
+| | RP-20 | RP-030297 | 227 | | RLC window size reconfigurations | 5.4.0 | 5.5.0 |
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 09/2003 | RP-21 | RP-030483 | 230 | | SDU Concatenation Exceptions and SDU Concatenation in AM Mode | 5.5.0 | 5.6.0 |
+| | RP-21 | RP-030483 | 233 | 1 | Decision of Discarded SDUs from Discarded PDUs | 5.5.0 | 5.6.0 |
+| | RP-21 | RP-030483 | 236 | 1 | RLC Reset Triggering and Update of VT(RST) | 5.5.0 | 5.6.0 |
+| | RP-21 | RP-030483 | 239 | | correction to the 'SDU discard with explicit signalling' procedure | 5.5.0 | 5.6.0 |
+| | RP-21 | RP-030478 | 242 | | Elimination of EPC mechanism | 5.5.0 | 5.6.0 |
+| | RP-21 | RP-030483 | 245 | | Correction of MRW and RESET timers in RLC | 5.5.0 | 5.6.0 |
+| | RP-21 | RP-030490 | 247 | | Reconfiguration of RLC window size | 5.5.0 | 5.6.0 |
+| 12-2003 | RP-22 | RP-030616 | 250 | | BITMAP and status report content | 5.6.0 | 5.7.0 |
+| | RP-22 | RP-030620 | 252 | | Indication of discarded SDU in RLC Reset and Re-establishment | 5.6.0 | 5.7.0 |
+| | RP-22 | - | - | | Upgrade to Release 6 - no technical change | 5.7.0 | 6.0.0 |
+| 06-2004 | RP-24 | RP-040224 | 258 | | DL RLC Size handling | 6.0.0 | 6.1.0 |
+| 12-2004 | RP-26 | RP-040504 | 262 | 1 | Correction of MRW SUFI content setting rule | 6.1.0 | 6.2.0 |
+| | RP-26 | RP-040504 | 264 | 1 | Correction of Poll Prohibit function | 6.1.0 | 6.2.0 |
+| | RP-26 | RP-040490 | 265 | 1 | Inclusion of out of sequence SDU delivery | 6.1.0 | 6.2.0 |
+| | RP-26 | RP-040490 | 266 | | Addition of MBMS Logical Channels and UM functionality for 'duplicate avoidance and reordering' | 6.1.0 | 6.2.0 |
+| 03-2005 | RP-27 | RP-050113 | 260 | 1 | Correction of MRW termination on reception of ACK SUFI | 6.2.0 | 6.3.0 |
+| | RP-27 | RP-050113 | 265 | | Correction to RLC Re-establishment | 6.2.0 | 6.3.0 |
+| | RP-27 | RP-050113 | 267 | | CRCLC-Config-Req in LOCAL SUSPEND State | 6.2.0 | 6.3.0 |
+| | RP-27 | RP-050113 | 268 | | Protocol error detection and recovery | 6.2.0 | 6.3.0 |
+| | RP-27 | RP-050068 | 270 | | Removal of the EPC mechanism | 6.2.0 | 6.3.0 |
+| | RP-27 | RP-050082 | 271 | | Inclusion of transmitter constraints | 6.2.0 | 6.3.0 |
+| 06-2005 | RP-28 | RP-050319 | 0272 | | Correction on actions taken Upon reception of an duplicated AMD PDU within the reception window | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050315 | 0273 | | Clarification on a Transmitter Constraint | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050319 | 0274 | | Reconfiguration of RLC parameters by upper layers may lead to Logic inconsistency of state variable VrH | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050302 | 0276 | | Erroneous Sequence Number definition | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050319 | 0277 | | Selecting a PDU to transmit a poll | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050319 | 0278 | | Support for out-of-sequence PDUs in RLC-UM | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050315 | 0279 | 1 | Clarification of the "Out of sequence SDU delivery" | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050317 | 0280 | | RLC LI Optimization for VoIP | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050315 | 0281 | | Correction to Out Of Sequence Delivery | 6.3.0 | 6.4.0 |
+| | RP-28 | RP-050315 | 0282 | | Clarification on operations when UE MCCH RLC entity is re-established and OSD_Window_Size is reconfigured | 6.3.0 | 6.4.0 |
+| 09-2005 | RP-29 | RP-050463 | 0284 | | Single Sided RLC Re-establishment | 6.4.0 | 6.5.0 |
+| | RP-29 | RP-050481 | 0285 | | Removal RLC-SDU alignment capability | 6.4.0 | 6.5.0 |
+| | RP-29 | RP-050468 | 0286 | | Arithmetic comparison for DAR function and VR(US) after MBMS being included | 6.4.0 | 6.5.0 |
+| | RP-29 | RP-050468 | 0287 | | Clarification on DAR window reconfiguration | 6.4.0 | 6.5.0 |
+| | RP-29 | RP-050468 | 0288 | | Clarification on reception of UMD PDU when OSD function is configured | 6.4.0 | 6.5.0 |
+| 12-2005 | RP-30 | RP-050784 | 0290 | | Correction on transmission of AMD PDU | 6.5.0 | 6.6.0 |
+| | RP-30 | RP-050788 | 0293 | | Initiation of state variable VR(UOH) | 6.5.0 | 6.6.0 |
+| | RP-30 | RP-050788 | 0294 | | Clarification on reception of UMD PDU when OSD function is configured | 6.5.0 | 6.6.0 |
+| | RP-30 | RP-050797 | 0296 | | Corrections to RLC re-establishment | 6.5.0 | 6.6.0 |
+| | RP-30 | RP-050802 | 0297 | 1 | RLC UMD header optimisation for RT services over HSDPA/HSUPA | 6.5.0 | 6.6.0 |
+| 03-2006 | RP-31 | RP-060090 | 0292 | 2 | Correction to RLC Re-establishment Procedure | 6.6.0 | 6.7.0 |
+| | RP-31 | RP-060090 | 0298 | | Correction to RLC reset procedure | 6.6.0 | 6.7.0 |
+| | RP-31 | RP-060094 | 0299 | | Introducing missing "and" to the RLC UMD operation with LI optimisation | 6.6.0 | 6.7.0 |
+| | RP-31 | - | - | | Upgrade to the Release 7 - no technical change | 6.7.0 | 7.0.0 |
+| 06/2006 | RP-32 | RP-060363 | 0301 | 1 | Clarification on abortion of RLC Reset procedure | 7.0.0 | 7.1.0 |
+| | RP-32 | RP-060363 | 0303 | | RLC SDU Discard during re-establishment | 7.0.0 | 7.1.0 |
+| 09/2006 | RP-33 | RP-060575 | 0305 | | AMD PDU discard | 7.1.0 | 7.2.0 |
+| 06/2007 | RP-36 | RP-070407 | 0306 | 1 | Removing an incomplete optimization for RLC operations during HSDPA cell change | 7.2.0 | 7.3.0 |
+| | RP-36 | RP-070407 | 0307 | - | Correction to Out of Sequence Reception function | 7.2.0 | 7.3.0 |
+| | RP-36 | RP-070407 | 0308 | - | DAR over CCCH | 7.2.0 | 7.3.0 |
+| | RP-36 | RP-070404 | 0309 | 2 | Introduction of Improved L2 support for high data rates | 7.2.0 | 7.3.0 |
+| | RP-36 | RP-070416 | 0311 | - | Corrections on modulus base in UM in RLC | 7.2.0 | 7.3.0 |
+| | RP-36 | RP-070407 | 0312 | - | Using special value of HE field to indicate end of an SDU for RLC AM | 7.2.0 | 7.3.0 |
+| 09/2007 | RP-37 | RP-070626 | 0313 | | Correction on POLL SUFI | 7.3.0 | 7.4.0 |
+| | RP-37 | RP-070626 | 0314 | | Special HE value setting | 7.3.0 | 7.4.0 |
+| 12/2007 | RP-38 | RP-070905 | 0315 | | Correction to Control Information transmission with two logical channels | 7.4.0 | 7.5.0 |
+| | RP-38 | RP-070910 | 0316 | | Introduction of CS Voice over HSPA | 7.4.0 | 8.0.0 |
+| 03/2008 | RP-39 | RP-080178 | 0319 | - | Correction to Reception of UM RLC | 8.0.0 | 8.1.0 |
+| | RP-39 | RP-080191 | 0321 | - | Correction to Control Information transmission | 8.0.0 | 8.1.0 |
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| | RP-39 | RP-080191 | 0323 | - | Poll SUFI and Status Reporting | 8.0.0 | 8.1.0 |
+| | RP-39 | RP-080202 | 0324 | - | Introducing flexible RLC PDU size in the uplink | 8.0.0 | 8.1.0 |
+| | RP-39 | RP-080190 | 0326 | - | Correction to the RLC RESET and RESET ACK PDU with flexible RLC PDU size | 8.0.0 | 8.1.0 |
+| 06/2008 | RP-40 | RP-080403 | 0328 | 1 | Correction on UM model depiction | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080391 | 0330 | 1 | Clarification on DAR Operation | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080405 | 0331 | - | CS-HSPA UL Segmentation | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080395 | 0333 | 3 | Removal of UTRAN behaviour | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080414 | 0334 | - | Correction to transmitting AM RLC entity | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080414 | 0335 | 1 | Removal of Redundant Description in Transmitting Side | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080390 | 0338 | - | Non-applicability of ciphering for MCCH, MSCH and MTCH | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080395 | 0343 | - | Maximum RLC PDU size | 8.1.0 | 8.2.0 |
+| | RP-40 | RP-080414 | 0344 | 1 | RLC PDU size adaptation | 8.1.0 | 8.2.0 |
+| 09/2008 | RP-41 | RP-080685 | 0349 | - | Correction to definition of N_LENGTH | 8.2.0 | 8.3.0 |
+| 03/2009 | RP-43 | RP-090117 | 0353 | - | Correction for VR(UM) | 8.3.0 | 8.4.0 |
+| | RP-43 | RP-090140 | 0354 | - | Concatenation/segmentation in case SN_Delivery parameter is configured | 8.3.0 | 8.4.0 |
+| | RP-43 | RP-090138 | 0356 | 1 | Clarification for the description of transmitting UM RLC entity | 8.3.0 | 8.4.0 |
+| | RP-43 | RP-090138 | 0357 | - | Correction to RLC text for MAC i/is | 8.3.0 | 8.4.0 |
+| | RP-43 | RP-090151 | 0358 | - | Removal of DCCH logical channel mapped on RLC TM entity | 8.3.0 | 8.4.0 |
+| 06/2009 | RP-44 | RP-090519 | 0359 | - | Submission of UMD PDU when SN_Delivery is configured | 8.4.0 | 8.5.0 |
+| | RP-44 | RP-090505 | 0364 | - | Removal of references to MAC-hs reset | 8.4.0 | 8.5.0 |
+| 09/2009 | RP-45 | RP-090917 | 0366 | - | Clarification on minimum PDU size | 8.5.0 | 8.6.0 |
+| | RP-45 | RP-090909 | 0368 | - | Clarification to LI setting after Timer_Discard expiry when alternative e-bit is used | 8.5.0 | 8.6.0 |
+| 12/2009 | RP-46 | RP-091329 | 0369 | - | Introduction of POLL SUFI in UL data transfer | 8.6.0 | 8.7.0 |
+| | RP-46 | RP-091336 | 0373 | - | Partial radio awareness for DC-HSUPA capable UEs | 8.6.0 | 9.0.0 |
+| 03/2010 | RP-47 | RP-100286 | 0375 | - | RLC recovery with uplink POLL SUFI(R9) | 9.0.0 | 9.1.0 |
+| 06/2010 | RP-48 | RP-100537 | 0379 | 2 | Correction of Poll SUFI handling for Improved L2 Uplink | 9.1.0 | 9.2.0 |
+| 12/2010 | RP-50 | RP-101365 | 0388 | - | Introduction of LCR TDD MC-HSUPA in 25.322 | 9.2.0 | 10.0.0 |
+| 06/2011 | RP-52 | RP-110771 | 0391 | 2 | Accept RLC PDUs with special value HE field if it's supported | 10.0.0 | 10.1.0 |
+| 09/2012 | RP-57 | RP-121369 | 0403 | - | Introduction of Multiflow in TS 25.322 | 10.1.0 | 11.0.0 |
+| 12/2012 | RP-58 | RP-121943 | 0404 | - | Introduction of further Multiflow agreements in TS 25.322 | 11.0.0 | 11.1.0 |
+| 03/2013 | RP-59 | RP-130239 | 0405 | - | Clarification on RLC Status Report prohibit functions | 11.1.0 | 11.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25323/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/25_series/25323/088921fa3f5a44c8551815122517eefd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ba66ebd8210610d7f6c02d186d6dfc848fbe2d8
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/088921fa3f5a44c8551815122517eefd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31646d287f720d59fa93e8beefce3f15091daaa64f4c760dc95cb119422a1fcd
+size 30429
diff --git a/marked/Rel-11/25_series/25323/17df1d7f3b046dfbff585ce4b68bc87d_img.jpg b/marked/Rel-11/25_series/25323/17df1d7f3b046dfbff585ce4b68bc87d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2587bd8ecdd0728be634f7fb1d2e9e2f2a510cc1
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/17df1d7f3b046dfbff585ce4b68bc87d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0003e188452012ddf30157c920a81999de07b4ec667b31902f179f1e92a75889
+size 20458
diff --git a/marked/Rel-11/25_series/25323/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-11/25_series/25323/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..125170572e92ca394688a928a4373c8c631d0ef1
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c96dd61444c486df8444ab3df4d45f006177bb0f8b5382847bbf91ed9729176
+size 52909
diff --git a/marked/Rel-11/25_series/25323/1b6859dc98bea4b394ac5ac200ee2881_img.jpg b/marked/Rel-11/25_series/25323/1b6859dc98bea4b394ac5ac200ee2881_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97259d9ce7d5662ced43bfefa81e217334541a57
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/1b6859dc98bea4b394ac5ac200ee2881_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e75c26fb5164e39371cbe144997727af128951282cfd0b5d18010e045df2cd9
+size 19962
diff --git a/marked/Rel-11/25_series/25323/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-11/25_series/25323/24c9e038a791677ed33100667b64f7e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4c85fb973e0274c5fa673654d266026b68fe9d7
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/24c9e038a791677ed33100667b64f7e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd0d65643cb4cf7e1bc8657c6af964eadbc5334a840120e18be13d5016fa84c1
+size 28749
diff --git a/marked/Rel-11/25_series/25323/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/25_series/25323/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6b368f827e003c18c57a3ab9cc259af4bb8b5bf
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5523de7da0b516a4b54cf1a3fd0ca1935bb3b0fa68675995e6e86ad2a130052a
+size 8942
diff --git a/marked/Rel-11/25_series/25323/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Rel-11/25_series/25323/2ba086df3506f81bae3a9b53725dcfea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22f68f3c64fea32dc1e3379d0ed28217cf99ed0c
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/2ba086df3506f81bae3a9b53725dcfea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff00cffd0ae9badfaae5709c33c6d67aacc7c9e37821d50e81430e097e11c27e
+size 70383
diff --git a/marked/Rel-11/25_series/25323/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-11/25_series/25323/382a9c9e4816bd229191ab4591424dd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0fd8ae302e91a43ce5d50d990d26eae33b7f3ee7
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/382a9c9e4816bd229191ab4591424dd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:113fa0ee28e4b242ab71f51c5242326f9ce5fb522db135e21cf34cf1f3c06364
+size 101621
diff --git a/marked/Rel-11/25_series/25323/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-11/25_series/25323/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..506359e86d7e0faaefaceb7b2a60ffae9d215f2a
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90fcb74d30e0a304deae76ed421f111d06b5cd9db68e06168f0e9b176be2a3ca
+size 24623
diff --git a/marked/Rel-11/25_series/25323/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg b/marked/Rel-11/25_series/25323/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26cacf575af51a691a2662ac9606eb205003e8b8
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:225ad3090713878bb4255e9c2c0ffba4da8338fe37867865df2624267e13f6ef
+size 25427
diff --git a/marked/Rel-11/25_series/25323/704082cc3e11776bda29595c76411362_img.jpg b/marked/Rel-11/25_series/25323/704082cc3e11776bda29595c76411362_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..318052eabf7f5f10880a00be7f11cc22d3fb37ce
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/704082cc3e11776bda29595c76411362_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:682b0fe1bc80ce2aa70862b8f5260d0e90d9f3cf191dbba4f1d5f34106b7c5be
+size 42068
diff --git a/marked/Rel-11/25_series/25323/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/Rel-11/25_series/25323/896e86ed12aff206d302c64f2e3091fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6ab929aaad57bdbafb4be8354216a64321094f2
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/896e86ed12aff206d302c64f2e3091fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1821b6e2c87f9e9b38b748f5ae2d482b748992c3d5486cafe6de8078acb7d03e
+size 106692
diff --git a/marked/Rel-11/25_series/25323/8f38356601e137ac471fc4771b9c5a5c_img.jpg b/marked/Rel-11/25_series/25323/8f38356601e137ac471fc4771b9c5a5c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..118028cffe7f01eda5d7efa0379fac5c58c5ff8c
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/8f38356601e137ac471fc4771b9c5a5c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f21b5ff62feaf7513603b0162e899c1bf518b6c51b3b0297d764fe6034ffefc3
+size 31662
diff --git a/marked/Rel-11/25_series/25323/bac21fd48fcd7f025c723590e07d1823_img.jpg b/marked/Rel-11/25_series/25323/bac21fd48fcd7f025c723590e07d1823_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..486645d798504ae203b4b856728b6e80d846f2ae
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/bac21fd48fcd7f025c723590e07d1823_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2f568da2bd22a258f32b1aed29d1ce585ca11720e03062830977a2a7c7cf9b3
+size 25568
diff --git a/marked/Rel-11/25_series/25323/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-11/25_series/25323/bf30e154f82662d212f21fccdfa2980f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff95ecdb9efc63bc0e5f2c8ac458c9e4cf984e6a
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/bf30e154f82662d212f21fccdfa2980f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6000db5ea21b0a68d3ab898a1b5e14666ae3b2538f0bbb67ebebb8b05b6baf60
+size 20957
diff --git a/marked/Rel-11/25_series/25323/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-11/25_series/25323/c53adc66eab40abd5f8b9107d950ad04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f51c5e5786f2c1178d5ab21c75be0214ccefad3a
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/c53adc66eab40abd5f8b9107d950ad04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:692e5385cf12a08620a4b4b3ffc302ff488a248f826c0a54fc77f11d22a5ff5d
+size 30303
diff --git a/marked/Rel-11/25_series/25323/raw.md b/marked/Rel-11/25_series/25323/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5e6ececead4deca9f86b34207e6cd4c0bebe3565
--- /dev/null
+++ b/marked/Rel-11/25_series/25323/raw.md
@@ -0,0 +1,1695 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and Abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 General..... | 9 |
+| 4.1 Objective ..... | 9 |
+| 4.2 Overview on sublayer architecture..... | 9 |
+| 5 Functions..... | 10 |
+| 5.1 Header Compression ..... | 10 |
+| 5.1.1 Mapping of PID values..... | 10 |
+| 5.1.2 IP Header Compression (RFC 2507)..... | 11 |
+| 5.1.2.1 Context identifiers..... | 11 |
+| 5.1.2.2 Mapping of PID values for RFC 2507..... | 11 |
+| 5.1.2.3 Management of Full Header transmission ..... | 11 |
+| 5.1.3 Robust Header Compression ..... | 11 |
+| 5.1.3.1 Context identifiers..... | 12 |
+| 5.1.3.2 Void ..... | 12 |
+| 5.1.3.3 Mapping of PID values ..... | 12 |
+| 5.1.3.4 Void ..... | 12 |
+| 5.1.3.5 Protocol Parameters ..... | 12 |
+| 5.1.3.6 Configuration by RRC..... | 13 |
+| 5.2 Void..... | 13 |
+| 5.3 Data Transfer..... | 13 |
+| 5.3.1 Data transfer over acknowledged mode RLC..... | 14 |
+| 5.3.2 Data transfer over unacknowledged and transparent mode RLC ..... | 14 |
+| 5.4 SRNS Relocation..... | 14 |
+| 5.4.1 Lossless SRNS Relocation ..... | 15 |
+| 5.4.1.1 Void ..... | 15 |
+| 5.4.1.2 Void ..... | 15 |
+| 5.4.1.3 Void ..... | 15 |
+| 5.4.2 Context relocation ..... | 15 |
+| 5.5 Lossless DL RLC PDU size change..... | 17 |
+| 5.6 General procedures..... | 17 |
+| 5.6.1.1 PDCP Sequence Numbering..... | 17 |
+| 5.6.1.2 PDCP Sequence Number synchronization ..... | 18 |
+| 5.6.1.3 Sequence Number and Data Forwarding ..... | 19 |
+| 5.6.1.4 CS Counter Handling..... | 19 |
+| 5.7 Header Compression and Decompression for MBMS..... | 19 |
+| 5.7.1 Cell change inside the same cell group ..... | 19 |
+| 5.7.2 Cell change between cell groups ..... | 20 |
+| 6 Services ..... | 20 |
+| 6.1 Services provided to upper layers ..... | 20 |
+| 6.2 Services expected from RLC layer..... | 20 |
+| 7 Elements for layer-to-layer communication ..... | 20 |
+| 7.1 Primitives between PDCP and upper layers..... | 20 |
+| 8 Elements for peer-to-peer communication..... | 22 |
+| 8.1 Protocol data units..... | 22 |
+| 8.2 Formats..... | 22 |
+| 8.2.1 PDCP-No-Header PDU ..... | 22 |
+| 8.2.2 PDCP Data PDU..... | 22 |
+| 8.2.3 PDCP SeqNum PDU ..... | 23 |
+| 8.2.4 PDCP AMR Data PDU ..... | 23 |
+
+| | | |
+|-----------------------------|----------------------------------------------------------------------|-----------|
+| 8.3 | Parameters ..... | 23 |
+| 8.3.1 | PDU Type..... | 23 |
+| 8.3.2 | PID..... | 24 |
+| 8.3.3 | Data..... | 24 |
+| 8.3.4 | Sequence number..... | 24 |
+| 8.3.5 | CS counter ..... | 24 |
+| 9 | Handling of unknown, unforeseen and erroneous protocol data ..... | 24 |
+| 9.1 | Invalid PDU type..... | 24 |
+| 9.2 | Invalid PID value ..... | 25 |
+| 9.3 | PDCP Unrecoverable Error Detection ..... | 25 |
+| Annex A (normative): | ROHC performance testing..... | 26 |
+| A.1 | Introduction ..... | 26 |
+| A.1.1 | Purpose of the performance testing ..... | 26 |
+| A.1.2 | Input sequence for uncompressed headers ..... | 26 |
+| A.1.3 | Feedback format for the test cases..... | 27 |
+| A.1.4 | Feedback generation for test cases (R-mode only)..... | 27 |
+| A.1.5 | Calculation of compressed header size..... | 28 |
+| A.2 | Test outline – RoHC RTP Profile 0x0001 ..... | 28 |
+| A.2.1 | Test 1a - Base test of ROHC RTP O-mode compressor ..... | 28 |
+| A.2.1.1 | Test purpose..... | 28 |
+| A.2.1.2 | Sequence details..... | 28 |
+| A.2.1.3 | Test requirement ..... | 29 |
+| A.2.2 | Test 1b - Base test of ROHC RTP R-mode compressor ..... | 29 |
+| A.2.2.1 | Test purpose..... | 29 |
+| A.2.2.2 | Sequence details..... | 30 |
+| A.2.2.3 | Test requirement ..... | 30 |
+| A.2.3 | Void ..... | 31 |
+| A.2.3.1 | Void ..... | 31 |
+| A.2.3.2 | Void ..... | 31 |
+| A.2.3.3 | Void ..... | 31 |
+| A.2.4 | Void ..... | 31 |
+| A.2.4.1 | Void ..... | 31 |
+| A.2.4.2 | Void ..... | 31 |
+| A.2.4.3 | Void ..... | 31 |
+| A.2.5 | Test 3a - Re-establishment of TS function after DTX in O-mode ..... | 31 |
+| A.2.5.1 | Test purpose..... | 31 |
+| A.2.5.2 | Sequence details..... | 31 |
+| A.2.5.3 | Test requirement ..... | 32 |
+| A.2.6 | Test 3b - Re-establishment of TS function after DTX in R-mode ..... | 32 |
+| A.2.6.1 | Test purpose..... | 32 |
+| A.2.6.2 | Sequence details..... | 32 |
+| A.2.6.3 | Test requirement ..... | 32 |
+| A.2.7 | Test 4a - Compressor response to single lost packets in O-mode ..... | 33 |
+| A.2.7.1 | Test purpose..... | 33 |
+| A.2.7.2 | Sequence details..... | 33 |
+| A.2.7.3 | Test requirement ..... | 33 |
+| A.2.8 | Test 4b - Compressor response to single lost packets in R-mode ..... | 33 |
+| A.2.8.1 | Test purpose..... | 33 |
+| A.2.8.2 | Sequence details..... | 33 |
+| A.2.8.3 | Test requirement ..... | 33 |
+| A.2.9 | Void ..... | 34 |
+| A.2.9.1 | Void ..... | 34 |
+| A.2.9.2 | Void ..... | 34 |
+| A.2.9.3 | Void ..... | 34 |
+| A.2.10 | Void ..... | 34 |
+| A.2.10.1 | Void ..... | 34 |
+| A.2.10.2 | Void ..... | 34 |
+| A.2.10.3 | Void ..... | 34 |
+| A.2.11 | Test 6a - TS function during DTX with varying delta in O-mode ..... | 34 |
+| A.2.11.1 | Test purpose..... | 34 |
+
+| | | |
+|-------------------------------|---------------------------------------------------------------------------|-----------|
+| A.2.11.2 | Sequence details..... | 34 |
+| A.2.11.3 | Test requirement ..... | 34 |
+| A.2.12 | Test 6b - TS function during DTX with varying delta in R-mode ..... | 35 |
+| A.2.12.1 | Test purpose..... | 35 |
+| A.2.12.2 | Sequence details..... | 35 |
+| A.2.12.3 | Test requirement ..... | 35 |
+| A.2.13 | Test 7a – SRNS relocation in O-mode ..... | 36 |
+| A.2.13.1 | Test purpose..... | 36 |
+| A.2.13.2 | Sequence details..... | 36 |
+| A.2.13.3 | Test requirement ..... | 36 |
+| A.3 | Test packet structures..... | 38 |
+| Annex B (informative): | Reference model for generating ROHC performance requirements ..... | 41 |
+| B.1 | Introduction ..... | 41 |
+| B.2 | For Voice over IP (VoIP) optimisation ..... | 41 |
+| B.2.1 | ROHC parameters optimisations for VoIP ..... | 41 |
+| B.2.2 | Parameter setting for ROHC reference model for VoIP..... | 41 |
+| B.2.3 | Setting the parameter value N in test cases for VoIP ..... | 41 |
+| Annex C (informative): | Change history..... | 42 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document provides the description of the Packet Data Convergence Protocol (PDCP).
+
+# --- 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 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [2] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification".
+- [3] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [4] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode".
+- [5] 3GPP TS 25.322: "RLC Protocol Specification".
+- [6] IETF RFC 2507: "IP Header Compression".
+- [7] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [8] IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".
+- [9] IETF RFC 3096: "Requirements for robust IP/UDP/RTP header compression".
+- [10] IETF RFC 4815: "ROBust Header Compression (ROHC): Corrections and Clarifications to RFC 3095".
+- [11] 3GPP TS 26.101: "Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec frame structure".
+- [12] 3GPP TS 26.201: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Frame structure".
+
+# --- 3 Definitions and Abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in [7] and the following apply.
+
+- N-context* Refers collectively to both *N-context-C* and *N-context-D*.
+- N-context\** Refers collectively to both *N-context-C\** and *N-context-D\**.
+- N-context-C* The compression context for downlink in SRNC at any given point of time.
+- N-context-C\** The frozen snapshot of the compression context for downlink taken by SRNC.
+- N-context-C-static\** The frozen snapshot of the static part of the compression context for downlink taken by SRNC.
+- N-context-D* The decompression context for uplink in SRNC at any given point of time.
+- N-context-D\** The frozen snapshot of the decompression context for uplink taken by SRNC.
+- N-context-D-static\** The frozen snapshot of the static part of the decompression context for uplink taken by SRNC.
+
+| | |
+|----------------------------|------------------------------------------------------------------------------------------------------|
+| M-context | Refers collectively to both M-context-C and M-context-D . |
+| M-context* | Refers collectively to both M-context-C* and M-context-D* . |
+| M-context-C | The compression context for uplink in UE at any given point of time. |
+| M-context-C* | The frozen snapshot of the compression context for uplink taken by UE. |
+| M-context-C-static* | The frozen snapshot of the static part of the compression context for uplink taken by UE. |
+| M-context-D | The decompression context for downlink in UE at any given point of time. |
+| M-context-D* | The frozen snapshot of the decompression context for downlink taken by UE. |
+| M-context-D-static* | The frozen snapshot of the static part of the decompression context for downlink taken by UE. |
+| M-HC | Entity located in the mobile terminal that performs header compression for uplink (i.e. UE PDCP) |
+| M-HCD | Refers collectively to both M-HC and M-HD . |
+| M-HD | Entity located in the mobile terminal that performs header decompression for downlink (i.e. UE PDCP) |
+| N-HC | Entity located in the network that performs header compression for downlink (i.e. RNC PDCP) |
+| N-HCD | Refers collectively to N-HC and N-HD |
+| N-HD | Entity located in the network that performs header decompression for uplink (i.e. RNC PDCP) |
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|--------------------------------------------|
+| AMR | Adaptive Multi-Rate |
+| AS | Access Stratum |
+| CID | Context Identifier |
+| C-SAP | Control Service Access Point |
+| HC | Header Compression |
+| IETF | Internet Engineering Task Force |
+| IP | Internet Protocol |
+| L2 | Layer 2 (data link layer) |
+| L3 | Layer 3 (network layer) |
+| MBMS | Multimedia Broadcast Multicast Service |
+| M-HC | Mobile Header Compressor |
+| M-HCD | Mobile Header Compressor/Decompressor |
+| M-HD | Mobile Header Decompressor |
+| NAS | Non Access Stratum |
+| N-HC | Network Header Compressor |
+| N-HCD | Network Header Compressor/Decompressor |
+| N-HD | Network Header Decompressor |
+| PDCP | Packet Data Convergence Protocol |
+| PDU | Protocol Data Unit |
+| PID | Packet Identifier |
+| PPP | Point-to-Point Protocol |
+| p-t-p | Point-to-Point |
+| p-t-m | Point-to-Multipoint |
+| RB | Radio Bearer |
+| RFC | Request For Comments |
+| RLC | Radio Link Control |
+| RNC | Radio Network Controller |
+| ROHC | RObust Header Compression |
+| RTP | Real Time Protocol |
+| SDU | Service Data Unit |
+| TCP | Transmission Control Protocol |
+| UDP | User Datagram Protocol |
+| UE | User Equipment |
+| UMTS | Universal Mobile Telecommunications System |
+| UTRA | UMTS Terrestrial Radio Access |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+# 4 General
+
+## 4.1 Objective
+
+The present document describes the functionality of the PDCP.
+
+## 4.2 Overview on sublayer architecture
+
+Figure 1 shows the model of the PDCP within the radio interface protocol architecture. The radio interface protocol architecture is defined in [3].
+
+Every PS domain RAB is associated with one RB, which in turn is associated with one PDCP entity. Each PDCP entity is associated with one or two (one for each direction) RLC entities depending on the RB characteristic (i.e. uni-directional or bi-directional) and RLC mode. The PDCP entities are located in the PDCP sublayer.
+
+Every PDCP entity uses zero, one or several different header compression protocols. Each individual PDCP entity uses at most one instance of each header compression protocol. Several PDCP entities may be defined for a UE with each using the same or a different set of header compression protocols. In this version of the specification, only two header compression protocols, RFC 2507 [6] and ROHC [8], [10], are supported.
+
+Every CS domain voice RAB is associated with one RB, which in turn is associated with one PDCP entity. Each PDCP entity is associated with two UM RLC entities as CS voice RBs are always bi-directional. The PDCP entities are located in the PDCP sublayer. The PDCP entity serving CS service does not use header compression.
+
+The PDCP sublayer is configured by upper layer [2] through the PDCP-C-SAP.
+
+
+
+The diagram illustrates the PDCP structure within the radio interface protocol architecture. At the top, 'Radio Bearers' are shown as vertical lines. These bearers connect to 'PDCP-SAPs' (Service Access Points), represented by circles. Above the PDCP-SAPs, a 'PDCP-SDU' (Service Data Unit) is shown entering the system. The PDCP-SAPs connect to the 'PDCP sublayer', which contains three 'PDCP entity' boxes. The first PDCP entity is connected to a 'C-SAP' (Control Service Access Point) and contains two 'HC Protocol' boxes (HC Protocol 1 and HC Protocol 2). The second PDCP entity contains an 'SDU numbering' box and two 'HC Protocol' boxes (HC Protocol 1 and HC Protocol 2). The third PDCP entity contains one 'HC Protocol' box (HC Protocol 1). Below the PDCP entities, the 'RLC' sublayer is shown, containing 'UM-SAP', 'AM-SAP', and 'TM-SAP' (Service Access Points). Arrows indicate the flow of data: from the PDCP entities down to the RLC sublayer, and from the RLC sublayer up to the PDCP entities. An 'RLC-SDU' (Service Data Unit) is shown entering the RLC sublayer from the right.
+
+Diagram of PDCP structure showing the relationship between Radio Bearers, PDCP entities, and RLC entities.
+
+**Figure 1: PDCP structure**
+
+Figure 1 represents one possible structure for the PDCP sublayer and should not restrict implementation. A PDCP entity is mapped to either one AM RLC entity or one or two UM or TM RLC entities. When a PDCP entity is mapped to two UM or TM RLC entities each RLC entity is used for a different direction.
+
+# 5 Functions
+
+PDCP provides its services to the NAS at the UE or the relay at the Radio Network Controller (RNC).
+
+The Packet Data Convergence Protocol shall perform the following functions:
+
+- header compression and decompression of IP data streams (e.g., TCP/IP and RTP/UDP/IP headers for IPv4 and IPv6) at the transmitting and receiving entity, respectively.
+- transfer of user data. This function is used for conveyance of data between users of PDCP services.
+- maintenance of PDCP sequence numbers for radio bearers that are configured to support lossless SRNS Relocation or lossless DL RLC PDU size change.
+- transfer of CS counter if the radio bearer is connected to a CS domain radio access bearer.
+- add and remove the padding in PDCP PDU for octet alignment.
+
+PDCP uses the services provided by the Radio Link Control (RLC) sublayer.
+
+## 5.1 Header Compression
+
+The header compression protocol is specific to the particular network layer, transport layer or upper layer protocol combinations e.g. TCP/IP and RTP/UDP/IP. The network layer protocol type, e.g. IP or PPP, is indicated during PDP context activation as defined in [1]. The header compression protocols and their parameters are configured by upper layers for each PDCP entity. Compressor and decompressor initiated signalling between peer PDCP entities, during operation, is accomplished through in-band signalling.
+
+### 5.1.1 Mapping of PID values
+
+Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
+
+- identify different types of header compression protocols;
+- if RFC2507:
+ - distinguish different header compression protocol packet types within a header compression protocol.
+
+The above requirements are realised by utilising the PID field in the PDCP PDU.
+
+The mapping of the PID values shall follow the general rules listed below:
+
+- PID values shall be mapped to the different packet types independently at each PDCP entity;
+- PID value "0" shall indicate "no compression". PID value "0" shall be used in a PDCP PDU containing in its Data field a PDCP SDU that is unchanged by the Sender and that shall not be decompressed by the Receiver.;
+- PID values are mapped in ascending order, starting from 1, for every configured header compression protocol, in the order of configuration by upper layer. The first available PID value is assigned to the first packet type of the header compression protocol as defined in the specification for this header compression protocol. PID values are mapped for all the specified packet types defined for the header compression protocol and in the order defined in subclause 5.1.2.2 and 5.1.3.3 for the respective header compression protocol;
+- PID values are re-mapped for the PDCP entity after any reconfiguration of the header compression protocols for that entity.
+
+The following table illustrates an example of the PID value mapping to the packet types when five arbitrary header compression methods are configured for one PDCP entity: RFC 2507[6], Methods A and B, ROHC [8], [10] and Method C. Method A, Method B and Method C are imaginary header compression protocols introduced for the purpose of illustration.
+
+**Table 1: Example of the PID value mapping table**
+
+| PID Value | Optimisation method | Packet type |
+|------------------|----------------------------|---------------------------|
+| 0 | No header compression | - |
+| 1 | RFC 2507 | Full header |
+| 2 | RFC 2507 | Compressed TCP |
+| 3 | RFC 2507 | Compressed TCP nondelta |
+| 4 | RFC 2507 | Compressed non TCP |
+| 5 | RFC 2507 | Context state |
+| 6 | Method A | Packet Type 1 of Method A |
+| 7 | Method A | Packet Type 2 of Method A |
+| 8 | Method B | Packet Type 1 of Method B |
+| 9 | Method B | Packet Type 2 of Method B |
+| 10 | RFC 3095, RFC 4815 | ROHC packet format |
+| 11 | Method C | Packet Type 1 of Method C |
+| 12 | Method C | Packet Type 2 of Method C |
+| 13...31 | Unassigned value | - |
+
+### 5.1.2 IP Header Compression (RFC 2507)
+
+The detailed operation of the RFC 2507 header compression protocol is specified in IETF RFC 2507 [6]. The mechanisms related to error recovery and packet reordering are also described in RFC 2507. These mechanisms shall be included in the functionality of the header compression supported by PDCP. The implementation of the RFC 2507 header compression functionality is not covered in this specification and is left to the implementation.
+
+#### 5.1.2.1 Context identifiers
+
+Context identifiers for RFC 2507 shall only be included in the RFC 2507 packet types format, as defined in [6].
+
+#### 5.1.2.2 Mapping of PID values for RFC 2507
+
+PID values shall be mapped to the RFC 2507 header compression packet types in the order presented in Table 2 below where "n" is the number of PID values already mapped to other protocol packet types.
+
+**Table 2: Mapping of PID values for RFC 2507 header compression protocol**
+
+| PID value | Optimisation method | Packet type |
+|------------------|----------------------------|--------------------------|
+| n+1 | RFC 2507 | Full header |
+| n+2 | RFC 2507 | Compressed TCP |
+| n+3 | RFC 2507 | Compressed TCP non-delta |
+| n+4 | RFC 2507 | Compressed non-TCP |
+| n+5 | RFC 2507 | Context state |
+
+#### 5.1.2.3 Management of Full Header transmission
+
+Transmission of a full header packet may be controlled by the lower layer information.
+
+For a TCP stream, if the PDCP receives from lower layer the information of failed transmission of a single packet, the PDCP may send the next packet as a full header.
+
+For a non-TCP stream, if the PDCP receives from lower layer the information of successful transmission of a full header packet, the PDCP may stop sending a full header packet that contains the same full header as the previously transmitted one.
+
+### 5.1.3 Robust Header Compression
+
+The detailed operation of the, "ROBust Header Compression (ROHC)" protocol is specified in IETF RFC 3095 [8] and IETF RFC 4815 [10].
+
+#### 5.1.3.1 Context identifiers
+
+The context of the ROHC protocol is defined in [8] and [10]. ROHC can be configured to support one or several contexts. Each context is identified by a value known as the context identifier (CID).
+
+#### 5.1.3.2 Void
+
+#### 5.1.3.3 Mapping of PID values
+
+The following PID value shall be mapped to the robust header compression protocol as presented in the table where n is the number of PID values already assigned to other protocol packet types.
+
+**Table 4: Mapping of PID values for RFC 3905 header compression protocol**
+
+| PID value | Optimisation method | Packet type |
+|-----------|---------------------|--------------------|
+| n+1 | RFC 3095, RFC 4815 | ROHC packet format |
+
+#### 5.1.3.4 Void
+
+#### 5.1.3.5 Protocol Parameters
+
+ROHC has two types of parameters [8], [10]:
+
+- configuration parameters: these are mandatory and must be configured between compressor and decompressor peers.
+- implementation parameters: these are optional and, when used, stipulate how the compression protocol operates.
+
+These parameters are categorized in four different groups, as defined below:
+
+- M: Mandatory and configured by upper layers.
+- MO: Parameters that must be supported and when used can only be configured or triggered by upper layers.
+- O: Optional parameters that are not configured by upper layers. They may be used locally (i.e. UTRAN and/or in UE).
+- N/A: These are not used in ROHC.
+
+The usage and definition of the parameters shall be as specified below.
+
+- MAX\_CID (M): This is the maximum CID value that can be used. One CID value shall always be reserved for uncompressed flows.
+- LARGE\_CIDS: This is not configured by upper layers but inferred from the configured value of MAX\_CID according to the following rule:
+
+If MAX\_CID > 15 then LARGE\_CIDS = TRUE else LARGE\_CIDS = FALSE.
+
+- PROFILES (M): Profiles are used to define which profiles are allowed to be used by the UE in uplink. In downlink, all the profiles defined in [8] shall be supported.
+- FEEDBACK\_FOR (N/A):
+- MRRU (M): Segmentation is not used by default.
+- NO\_OF\_PACKET\_SIZES\_ALLOWED (N/A).
+- PACKET\_SIZES\_ALLOWED (N/A)
+- PAYLOAD\_SIZES (O).
+- NO\_OF\_PACKET\_SIZES\_USED (O).
+
+- PACKET\_SIZES\_USED (O).
+- CONTEXT\_REINITIALIZATION (MO).
+- MODE (O).
+- CLOCK\_RESOLUTION (O).
+- REVERSE\_DECOMPRESSION\_DEPTH (M): Default value is that reverse decompression is not used.
+
+#### 5.1.3.6 Configuration by RRC
+
+If the variable "PDCP\_ROHC\_TARGET\_MODE" [2] is stored in the UE, and if applicable for the ROHC profile applied, the de-compressor shall only perform the operational state transitions defined in [8] to the stored mode.
+
+If the variable "PDCP\_ROHC\_TARGET\_MODE" [2] is not stored in the UE, the de-compressor shall not restrict the operational state transitions defined in [8].
+
+## 5.2 Void
+
+## 5.3 Data Transfer
+
+If header compression is configured the PDCP entity in the Sender shall:
+
+- perform header compression upon reception of a PDCP SDU from upper layers;
+- if the radio bearer is configured for lossless SRNS Relocation or lossless DL RLC PDU size change:
+ - maintain PDCP sequence numbering as specified in subclause 5.6.1.1;
+- submit the PDCP PDU to lower layer in the sequence received from the upper layer.
+
+If radio bearer is connected to a CS domain radio access bearer, the sender shall:
+
+- if the PDCP SDU length is of 1 or more bits:
+ - include the CS counter in the PDCP AMR Data PDU as specified in subclause 5.6.1.4;
+ - indicate the PDCP AMR PDU type in the PDU type field;
+ - fill the data field of the PDCP AMR PDU type with the PDCP SDU and add padding bits as specified in subclause 8.2.4.
+
+NOTE: If no AMR or AMR WB frames is generated by upper layers, no PDCP PDU is submitted to the lower layer.
+
+When the PDCP entity at the Receiver receives the PDCP PDU from lower layers, it shall:
+
+- if the received PDCP PDU is of type PDCP AMR Data PDU:
+ - the PDCP SDU is derived from the data field of the PDCP AMR Data PDU. The receiver determines the bit aligned data content and Frame Type from the PDU Data field length, as possible AMR and AMR WB payload has a unique size when being octet aligned;
+ - deliver the PDCP SDU and CS counter from the received PDCP header to the upper layer.
+- else:
+ - perform header decompression (if header compression is configured) of the PDCP PDU to obtain the PDCP SDU; and
+ - deliver the PDCP SDU to the upper layer in the order received from the lower layer;
+
+- if the received PDCP PDU is of type PDCP SeqNum PDU:
+ - follow the procedure in subclause 5.6.1.2.
+
+### 5.3.1 Data transfer over acknowledged mode RLC
+
+Figure 2 shows the PDCP data transfer over acknowledged mode RLC.
+
+
+
+Sequence diagram for PDCP data transfer over acknowledged mode RLC. The diagram shows the interaction between an Originator and a Receiver. The Originator contains PDCP user, PDCP, and RLC layers. The Receiver contains RLC, PDCP, and PDCP user layers. The sequence of messages is: 1. PDCP user sends PDCP-DATA.req to PDCP. 2. PDCP sends RLC-AM-DATA.req to RLC. 3. RLC sends data to the Receiver's RLC layer. 4. The Receiver's RLC layer sends an Acknowledgement back to the Originator's RLC layer. 5. The Receiver's RLC layer sends RLC-AM-DATA.ind to the Receiver's PDCP layer. 6. The Receiver's PDCP layer sends PDCP-DATA.ind to the Receiver's PDCP user. 7. The Originator's RLC layer sends RLC-AM-DATA.cnf (NOTE) to the Originator's PDCP layer.
+
+**Figure 2: PDCP data transfer over acknowledged mode RLC**
+
+NOTE: If the primitive RLC-AM-DATA.req is used with parameter CNF, the primitive RLC-AM-DATA.cnf is delivered. Otherwise, this primitive is not delivered.
+
+### 5.3.2 Data transfer over unacknowledged and transparent mode RLC
+
+Figure 3 shows the PDCP data transfer over unacknowledged or transparent mode RLC.
+
+
+
+Sequence diagram for PDCP data transfer over unacknowledged or transparent mode RLC. The diagram shows the interaction between a Sender and a Receiver. The Sender contains PDCP user, PDCP, and RLC layers. The Receiver contains RLC, PDCP, and PDCP user layers. The sequence of messages is: 1. PDCP user sends PDCP-DATA.req to PDCP. 2. PDCP sends RLC-UM-DATA.req or RLC-TM-DATA.req to RLC. 3. RLC sends data to the Receiver's RLC layer. 4. The Receiver's RLC layer sends RLC-UM-DATA.ind or RLC-TM-DATA.ind to the Receiver's PDCP layer. 5. The Receiver's PDCP layer sends PDCP-DATA.ind to the Receiver's PDCP user.
+
+**Figure 3: PDCP data transfer over unacknowledged or transparent mode RLC**
+
+## 5.4 SRNS Relocation
+
+In case of SRNS Relocation upper layer indicates to PDCP to perform either the re-initialisation or the context relocation of compression protocols of an RB, or the release of the compression protocols of an RB. In this version of the specification, context relocation is only applicable to RFC3095. Each of the compression protocols is handled independently, but the context relocation capability is optional for the UE and it is indicated as a part of the UE radio access capabilities.
+
+The re-initialisation of a given compression protocol entails the following:
+
+- Compression parameters may be reconfigured by upper layers during re-initialisation, otherwise compression parameters remain valid during re-initialisation.
+- All compression state information is initialised, e.g. header compression contexts. Therefore, the first 'compressed' packet type after SRNS Relocation is a full header.
+
+- The PDCP sequence numbers are not changed due to the PDCP header compression protocol re-initialisation.
+
+The context relocation of a given compression protocol entails the following:
+
+- Configured compression parameters remain valid during context relocation.
+- A snapshot of the compression state information (context) is taken in the source RNC and transferred to the target RNC, which initialises the header compression protocol according to the transferred snapshot. Therefore, the (de)compression continues after SRNS Relocation from the context used before relocation.
+- Some additional specific actions are performed both in UE and UTRAN during the SRNS Relocation in order to keep the (de)compressors consistent.
+
+### 5.4.1 Lossless SRNS Relocation
+
+Lossless SRNS Relocation is only applicable when RLC is configured for in-sequence delivery and acknowledged mode. The support of lossless SRNS Relocation is configured by upper layer.
+
+For the support of lossless SRNS Relocation, the PDCP entities maintain sequence numbers for PDCP SDUs, as described in subclause 5.6.1.1.
+
+These sequence numbers are synchronised between PDCP Sender and Receiver, as described in subclause 5.6.1.2.
+
+When a lossless SRNS Relocation is performed sequence numbers are exchanged between UE and UTRAN. They are used to confirm PDCP SDUs transmitted but not yet acknowledged by the Receiver, as described in subclause 5.6.1.3. After relocation the data transfer begins with the first unconfirmed PDCP SDU.
+
+#### 5.4.1.1 Void
+
+#### 5.4.1.2 Void
+
+#### 5.4.1.3 Void
+
+### 5.4.2 Context relocation
+
+The header compression context relocation is performed by the decision of upper layers in source RNC based on the UE radio capabilities. The decision is done independently every time the SRNS relocation occurs and is specific for each header compression protocol. It is indicated to UE as a part of the SRNS relocation signalling of the upper layer and the selected relocation method is configured to UE PDCP by the upper layer.
+
+The header compression context relocation shall not be performed if the radio bearer is configured to support the lossless SRNS Relocation.
+
+**In the UE**, upon reception of the indication about SRNS relocation being performed:
+
+- the upper layer configures PDCP (*CPDCP-CONFIG.Req*) to perform either re-initialisation (R) or the context relocation (C) of header compression protocols;
+- if the context relocation is to be applied for RFC3095 header compression protocol:
+ - if the **compressor** (M-HC) is operating in **R mode**:
+ - uplink data may be compressed and transmitted normally.
+ - if the **compressor** (M-HC) is operating in **O mode**:
+ - compress and transmit uplink data as specified in [8] using the assumption that all ROHC uplink packets transmitted are likely to be lost. When SRNS relocation is completed, M-HC should return to normal operation.
+
+NOTE: When the M-HC is using the assumption that all ROHC uplink packets transmitted are likely to be lost:
+
+- the M-HC can not transit to a higher compression state;
+ - for W-LSB encoding, the M-HC updates the set of candidate reference values used by the decompressor by adding newly transmitted values but not removing old values.
+- if the **compressor** (M-HC) is operating in **U mode**:
+ - M-HC shall transit to FO state and send IR-DYN to re-synchronise the dynamic part of the uplink context.
+ - if the reverse decompression is applied in the **decompressor** (M-HD):
+ - flush the reverse decompression buffer by discarding all packets in the buffer.
+ - in the **decompressor** (M-HD), in **all modes**:
+ - downlink data may be received and decompressed normally.
+
+**In the UTRAN source RNC**, while SRNS relocation is being performed:
+
+- if the context relocation is to be applied for RFC3095 header compression protocol:
+ - PDCP is requested to take a context snapshot by the upper layer (*CPDCP-CONTEXT.Req*);
+- if the **compressor** (source N-HC) is operating in **R mode**:
+ - the source N-HC should take a snapshot of its header compression compressor context (denoted *N-context-C\**);
+ - header compression contexts should not be updated anymore even though downlink data may be compressed and transmitted otherwise normally. This can be done by sending R-1\* packets.
+- if the **compressor** (source N-HC) is operating in **O mode**:
+ - the source N-HC should take a snapshot of its header compression compressor context (denoted *N-context-C\**);
+ - after the snapshot is taken, the source N-HC should only send UO-0 or UO-1\* packets. This means only RTP SN, RTP TS, and IP-ID (for IPv4 only) fields are updated in the decompressor context at M-HD.
+- if the **compressor** (source N-HC) is operating in **U mode**:
+ - the source N-HC should take a snapshot of the static part of its header compression compressor context (denoted *N-context-C-static\**).
+- if the **decompressor** (source N-HD) is operating in **R or O mode**:
+ - if the source N-HD is sure about the integrity of the *N-context-D*:
+ - the source N-HD should take a snapshot of its header compression decompressor context (denoted as *N-context-D\**).
+ - if the source N-HD is only sure about the integrity of the static part of the *N-context-D* (e.g. due to multiple detected errors):
+ - the source N-HD should take a snapshot only of the static part of the *N-context-D* (denoted as *N-context-D-static\**).
+ - RFC3095 acknowledgments should not be generated anymore even though uplink data may be received and decompressed otherwise normally.
+- if the **decompressor** (source N-HD) is operating in **U mode**:
+
+- the source N-HD should take a snapshot of the static part of its header compression decompressor context (denoted *N-context-D-static\**).
+- either *N-context-C\** or *N-context-C-static\** and either *N-context-D\** or *N-context-D-static\** should be delivered to the upper layer as *Context-Info (CPDCP-CONTEXT.Conf)*, which is to be transmitted further to the target RNC.
+
+**In the UTRAN target RNC**, while SRNS relocation is being performed:
+
+- the upper layer configures PDCP (*CPDCP-CONFIG.Req*) to perform either initialisation (I) or the context relocation (C) of header compression protocols;
+- the new header compression entity should be created;
+- if the context relocation is to be applied for RFC3095 header compression protocol:
+ - in the **compressor** (target N-HC), in **all modes**:
+ - the header compression compressor (target N-HC) should be initialised to the same mode as used in the source N-HC using *N-context-C\** as the initial header compression compressor context;
+ - in addition, if the source N-HC was operating in U-mode, the target N-HC should first send IR-DYN to resynchronise the dynamic part of the downlink context.
+ - in the **decompressor** (target N-HD), in **all modes**:
+ - if *Context-Info* carries N-context-D\*:
+ - the header compression decompressor (target N-HD) should be initialised to the same mode as used in the source N-HD using *N-context-D\** as the initial header compression decompressor context.
+ - if *Context-Info* carries N-context-D-static\*:
+ - the header compression decompressor (target N-HD) should be initialised to the same mode as used in the source N-HD using N-context-D-static\* as the initial header compression decompressor context;
+ - the target N-HD should send a request for IR-DYN.
+
+## 5.5 Lossless DL RLC PDU size change
+
+Lossless DL RLC PDU size change is only applicable when RLC is configured for in-sequence delivery and acknowledged mode. The support of lossless DL RLC PDU size change is configured by upper layer.
+
+For the support of lossless DL RLC PDU size change, the PDCP entities maintain sequence numbers for DL PDCP SDUs, as described in subclause 5.6.1.1.
+
+These DL sequence numbers are synchronised between PDCP Sender in the UTRAN and Receiver in the UE, as described in subclause 5.6.1.2.
+
+When a lossless DL RLC PDU size change is performed the next expected DL\_Receive PDCP SN is sent from the UE to the UTRAN. It is used to confirm DL PDCP SDUs transmitted but not yet acknowledged by the Receiver in the UE, as described in subclause 5.6.1.3. After lossless DL RLC PDU size change the data transfer begins with the first unconfirmed DL PDCP SDU.
+
+## 5.6 General procedures
+
+#### 5.6.1.1 PDCP Sequence Numbering
+
+The value of the PDCP sequence number ranges from 0 to 65535. The PDCP SN window size indicates the maximum number of PDCP SDUs, not confirmed to have been successfully transmitted to the peer entity by lower layer, that can be numbered at any given time. The PDCP SN window size is configured by upper layers. PDCP sequence numbers are set to "0" when the PDCP entity is set-up for the first time.
+
+In the following the "submission/reception of a PDCP SDU to/from lower layer" is used as a synonym for the submission/reception of a PDCP Data PDU or a PDCP SeqNum PDU to/from lower layer that carries in its Data field a compressed or uncompressed PDCP SDU.
+
+If lossless SRNS relocation and/or lossless DL RLC PDU size change are/is supported by the UE, for each radio bearer configured to support "lossless SRNS relocation or lossless DL RLC PDU size change" as specified in [1], PDCP sequence numbers are applied:
+
+- in the UE:
+ - the DL\_Receive PDCP SN shall be set to "0" for the first PDCP SDU received from lower layer;
+ - the DL\_Receive PDCP SN shall be incremented by "1" for the next PDCP SDU received from lower layer.
+- in the UTRAN:
+ - the DL\_Send PDCP SN should be set to "0" for the first PDCP SDU submitted to lower layer;
+ - the DL\_Send PDCP SN should be incremented by "1" for the next PDCP SDU submitted to lower layer.
+
+Additionally, if lossless SRNS relocation is supported by the UE, for each radio bearer configured to support "lossless SRNS relocation or lossless DL RLC PDU size change" as specified in [1], PDCP sequence numbers are applied:
+
+- in the UE:
+ - the UL\_Send PDCP SN shall be set to "0" for the first PDCP SDU submitted to lower layer;
+ - the UL\_Send PDCP SN shall be incremented by "1" for the next PDCP SDU submitted to lower layer;
+- in the UTRAN:
+ - the UL\_Receive PDCP SN should be set to "0" for the first PDCP SDU received from lower layer;
+ - the UL\_Receive PDCP SN should be incremented by "1" for the next PDCP SDU received from lower layer.
+
+PDCP sequence numbers shall not be decremented in a PDCP entity.
+
+#### 5.6.1.2 PDCP Sequence Number synchronization
+
+For radio bearers that are configured to support "lossless SRNS Relocation or lossless DL RLC PDU size change" as specified in [1]:
+
+the UE PDCP entity shall:
+
+- if the UE supports lossless SRNS relocation,
+ - if a PDCP entity has to synchronise the UL PDCP SN following a RLC reset or RLC transmitting side re-establishment not caused by a lossless SRNS Relocation; or
+ - if the UE PDCP entity receives an invalid "next expected UL Receive PDCP SN" from upper layer after a lossless SRNS Relocation;
+ - trigger the PDCP SN synchronisation procedure by submitting one PDCP SeqNum PDU to lower layer;
+ - consider that the synchronisation procedure is complete on confirmation by lower layer of the successful transmission of the PDCP SeqNum PDU.
+- if the UE supports lossless DL RLC PDU size change but not lossless SRNS relocation, the UE PDCP entity shall not submit PDCP SeqNum PDU to lower layer.
+
+- the UTRAN PDCP entity should:
+
+- if a PDCP entity has to synchronise the DL PDCP SN following a RLC reset or RLC transmitting side re-establishment not caused by a lossless SRNS Relocation or a lossless DL RLC size change; or
+- if the UTRAN PDCP entity receives an invalid "next expected DL\_Receive PDCP SN" from upper layer after lossless SRNS Relocation or lossless DL RLC PDU size change:
+
+- trigger the PDCP SN synchronisation procedure by submitting one PDCP SeqNum PDU to lower layer;
+- consider that the synchronisation procedure is complete on confirmation by lower layer of the successful transmission of the PDCP SeqNum PDU.
+
+In the UE/UTRAN, the "next expected UL/DL\_Receive PDCP SN" is considered invalid if its value is less than the UL/DL\_Send PDCP SN of the first transmitted but not yet acknowledged PDCP SDU or greater than that of the first unsent PDCP SDU.
+
+On receiving a PDCP SeqNum PDU:
+
+- the UE PDCP entity shall:
+ - set the value of the DL\_Receive PDCP SN to the value indicated in the PDCP SeqNum PDU;
+- the UTRAN PDCP entity should:
+ - set the value of the UL\_Receive PDCP SN to the value indicated in the PDCP SeqNum PDU.
+
+NOTE: If UTRAN has the intention to use only the lossless DL RLC PDU size change, UTRAN may not maintain UL PDCP SN. In this case, UTRAN should still transfer the user data to upper layer.
+
+#### 5.6.1.3 Sequence Number and Data Forwarding
+
+In case of a lossless SRNS Relocation procedure or lossless DL RLC size change, as described in [1]:
+
+- the UE shall send to the UTRAN the next expected DL\_Receive PDCP SN.
+
+Additionally, in case of lossless SRNS relocation procedure, as described in [1]:
+
+- the UTRAN should send to the UE the next expected UL\_Receive PDCP SN.
+
+This information exchange synchronises the Sequence Numbers at the UE and UTRAN PDCP entities.
+
+When requested by the upper layer, for each radio bearer configured to support lossless SRNS Relocation, the PDCP sublayer in the source RNC should forward the following to the target RNC:
+
+- the UL\_Receive PDCP SN of the next PDCP SDU expected to be received from the UE;
+- the DL\_Send PDCP SN of the first transmitted but not yet acknowledged PDCP SDU;
+- the transmitted but not yet acknowledged PDCP SDUs together with their related DL\_Send PDCP SNs;
+- the not yet transmitted PDCP SDUs.
+
+#### 5.6.1.4 CS Counter Handling
+
+In case the radio bearer is connected to a CS domain radio access bearer, the CS counter shall be included in the PDCP AMR Data PDU.
+
+The value of the CS counter shall be set to the first to fifth LSBs of the CFN at which the packet has been received from higher layers.
+
+In the receiving side, the CS counter shall be delivered to the upper layer together with the PDCP SDU.
+
+The CS counter is used to manage the delay jitter generated by the radio layer. The CS counter plus the value of the information element "Max CS delay", as signalled in [2], indicates the latest instance at which the AMR or AMR WB frames is delivered to the upper layer.
+
+## 5.7 Header Compression and Decompression for MBMS
+
+Header compression and decompression for a p-t-m MBMS service is performed in ROHC U-mode.
+
+Applying ROHC for p-t-m RB configuration is optional and should be configured per MBMS session.
+
+### 5.7.1 Cell change inside the same cell group
+
+When a UE moves to a cell that is the same cell group with that of the previous cell while receiving a p-t-m MBMS service which is provided in both cells, the UE shall:
+
+- continue header decompression during and after cell change.
+
+### 5.7.2 Cell change between cell groups
+
+When a UE moves to a cell that is the different cell group with that of the previous cell while receiving a p-t-m MBMS service which is provided in both cells, the UE shall:
+
+- reconfigure and re-initialise the PDCP entity;
+- reuse the static part of the header decompressor context used in the previous cell;
+- re-initialise header decompression after receiving IR-DYN or IR packet and correcting the CID of the context with the CID being used in the new cell.
+
+NOTE: How to correct CID is implementation issue and is not specified.
+
+# --- 6 Services
+
+## 6.1 Services provided to upper layers
+
+The following services are provided by PDCP to upper layers:
+
+- transfer of user data;
+- maintenance of PDCP SDU sequence numbers.
+
+## 6.2 Services expected from RLC layer
+
+For a detailed description of the following functions see [5].
+
+- transparent data transfer Service;
+- unacknowledged data transfer Service;
+- acknowledged data transfer Service.
+
+# --- 7 Elements for layer-to-layer communication
+
+The interaction between the PDCP layer and other layers are described in terms of primitives where the primitives represent the logical exchange of information and control between the PDCP layer and other layers. The primitives shall not specify or constrain implementations.
+
+## 7.1 Primitives between PDCP and upper layers
+
+The primitives between PDCP and upper layers are shown in Table 5.
+
+**Table 5: Primitives between PDCP and upper layers**
+
+| Generic Name | Parameter | | | |
+|---------------|----------------------------------------------------------------------------------------------------|------------------|-------------|----------------------------------|
+| | Req. | Ind. | Resp. | Conf. |
+| PDCP-DATA | Data | Data, CS Counter | Not Defined | Not Defined |
+| CPDCP-CONFIG | PDCP-Info, RLC-SAP
SN_Sync, R/I/C/RS,
Context-Info, PDCP
Unrecoverable Error
Detection | Not Defined | Not Defined | Not Defined |
+| CPDCP-CONTEXT | None | Not Defined | Not Defined | Context-Info |
+| CPDCP-RELEASE | RLC-SAP | Not Defined | Not Defined | Not Defined |
+| CPDCP-SN | PDCP SN | Not Defined | Not Defined | Not Defined |
+| CPDCP-RELOC | Next_Receive_SN | Not Defined | Not Defined | Next_Receive_SN,
Next_Send_SN |
+
+Each Primitive is defined as follows:
+
+### a) PDCP-DATA-Req./Ind.
+
+- PDCP-DATA-Req is used by upper user-plane protocol layers to request a transmission of upper layer PDU. PDCP-DATA-Ind is used to deliver PDCP SDU that has been received to upper user plane protocol layers.
+
+### b) CPDCP-CONFIG-Req.
+
+- CPDCP-CONFIG-Req is used to configure and – in case of already existing PDCP entity – to reconfigure a PDCP entity and to assign it to the radio bearer associated with that entity.
+
+### c) CPDCP-RELEASE-Req.
+
+- CPDCP-RELEASE-Req is used by upper layers to release a PDCP entity.
+
+### d) CPDCP-SN-Req.
+
+- This primitive is used at the UTRAN. CPDCP-SN-Req is used to transfer the PDCP SN to PDCP.
+
+### e) CPDCP-RELOC-Req/Conf.
+
+- CPDCP-RELOC-Req initiates the SRNS Relocation procedure in PDCP for those radio bearers that are configured to support lossless SRNS Relocation. The Next\_Receive\_SN is only included at the UE side.
+- CPDCP-RELOC-Conf is used to transfer the Next\_Receive\_SN and/or Next\_Send\_SN to upper layers for lossless SRNS Relocation. The Next\_Send\_SN is only included at the source RNC.
+
+### f) CPDCP-CONTEXT-Req./Conf.
+
+- CPDCP-CONTEXT-Req initiates specific actions in the source RNC in order to perform context relocation as a part of the SRNS relocation. The primitive is applicable only in the source RNC.
+- CPDCP-CONTEXT-Conf is used to transfer the header compression context information from PDCP to upper layer in order to perform context relocation as a part of the SRNS relocation. The primitive is applicable only in the source RNC.
+
+The following parameters are used in the primitives:
+
+#### 1) PDCP-Info:
+
+- Contains the parameters for each of the header compression protocols configured to be used by one PDCP entity.
+
+#### 2) RLC-SAP:
+
+- The RLC-SAP (TM/UM/AM) used by PDCP entity when communicating with RLC sublayer.
+
+#### 3) SN\_Sync:
+
+- Indicates that PDCP should start PDCP SN synchronisation procedure.
+- 4) Next\_Send\_SN:
+- The Send PDCP SN of the next PDCP SDU to be sent. There is one in the uplink (UL\_Send PDCP SN) and one in the downlink (DL\_Send PDCP SN). Refer to subclause 5.4.1.
+- 5) Next\_Receive\_SN:
+- The Receive PDCP SN of the next PDCP SDU expected to be received. There is one in the uplink (UL\_Receive PDCP SN) and one in the downlink (DL\_Receive PDCP SN). Refer to subclause 5.4.1.
+- 6) PDCP SN:
+- This includes a PDCP sequence number.
+- 7) R/I/C/RS
+- Indicates that PDCP should Re-initialise (R)/Initialise (I) the header compression protocols. Alternatively (Context-relocation, C) it indicates that UE PDCP shall perform specific actions related to context relocation during SRNS relocation. (RS) indicates to Re-initialise while keeping the static part of the header compression (only for ROHC). R/I/C/RS indication is given separately for each of the configured header compression protocol, if several exist for a given radio bearer.
+- 8) Context-Info:
+- Contains the header compression context information of each of the header compression protocols that are subject to the context relocation during SRNS relocation.
+- 9) CS Counter:
+- Contains the timing information of AMR or AMR WB frame that will be used by upper layer.
+- 10) PDCP Unrecoverable Error Detection:
+- Determines whether PDCP Unrecoverable Error Detection shall be performed in a PDCP entity.
+
+# --- 8 Elements for peer-to-peer communication
+
+## 8.1 Protocol data units
+
+Different PDU formats are defined for the PDCP protocol, one not introducing any overhead to the (compressed) PDCP SDU, others introducing such overhead.
+
+## 8.2 Formats
+
+A PDCP PDU shall be a multiple of 8 bits, if the RLC entity is configured for unacknowledged or acknowledged mode. Otherwise, if the RLC entity is configured for transparent mode, it is bit-aligned. In Tables 6, 7 and 8, bit strings are represented as follows: the first bit is the leftmost one on the first line of the table, the last bit is the rightmost on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines.
+
+SDUs are bit strings, with any non-null length. If not compressed within PDCP an SDU is included from first bit onward.
+
+### 8.2.1 PDCP-No-Header PDU
+
+The PDCP-No-Header PDU does not introduce any overhead to the PDCP SDU. The use of the PDCP-No-Header PDU is configured by the upper layer.
+
+The format of the PDCP-No-Header PDU is shown in Table 6.
+
+**Table 6: PDCP-No-Header PDU**
+
+| |
+|------|
+| Data |
+|------|
+
+### 8.2.2 PDCP Data PDU
+
+The PDCP Data PDU is used to convey:
+
+- data containing an uncompressed PDCP SDU; or
+- header compression related control signalling; or
+- data that has been obtained from PDCP SDU after header compression.
+
+The format of the PDCP Data PDU is shown in Table 7.
+
+Table 7: PDCP Data PDU format
+
+| | |
+|----------|-----|
+| PDU type | PID |
+| Data | |
+
+### 8.2.3 PDCP SeqNum PDU
+
+The PDCP SeqNum PDU is used to convey a PDCP SDU sequence number and:
+
+- data containing an uncompressed PDCP SDU; or
+- data that has been obtained from PDCP SDU after header compression.
+
+The format of the PDCP SeqNum PDU is shown in Table 8.
+
+Table 8: PDCP SeqNum PDU format
+
+| | |
+|-----------------|-----|
+| PDU type | PID |
+| Sequence number | |
+| Data | |
+| | |
+
+### 8.2.4 PDCP AMR Data PDU
+
+The PDCP AMR Data PDU is used to convey:
+
+- a PDCP SDU containing AMR or AMR WB frame
+
+The format of the PDCP AMR Data PDU is shown in Table 9.
+
+Table 9: PDCP AMR Data PDU format
+
+| | |
+|----------|------------|
+| PDU type | CS counter |
+| Data | |
+
+The PDCP PDU is octet aligned but the actual PDCP SDU carrying the AMR or AMR WB frame may not be octet aligned. The data field contains the "AMR Core Frame" of AMR IF1 as defined in [11] or "AMR-WB Core Frame" of AMR-WB IF1 as defined in [12]. The AMR classes are always encoded in the order of class A, B and C, where d(0) of the "AMR Core Frame" or "AMR-WB Core Frame" is carried in the first bit of data field. Any padding for octet alignment is inserted at the end of the data field.
+
+## 8.3 Parameters
+
+If not otherwise mentioned in the definition of each field then the bits in the parameters shall be interpreted as follows: the left most bit string is the first and most significant and the right most bit is the last and least significant bit.
+
+Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU.
+
+### 8.3.1 PDU Type
+
+Length: 3 bits.
+
+The PDU type field indicates the PDCP Data PDU type.
+
+| Bit | PDU Type |
+|----------------|---------------------------------------------------------------------------------|
+| 000 | PDCP Data PDU (Table 7) |
+| 001 | PDCP SeqNum PDU (Table 8) |
+| 010 | PDCP AMR Data PDU (Table 9) |
+| 011-111 | Reserved (PDUs with this encoding are invalid for this version of the protocol) |
+
+### 8.3.2 PID
+
+Length: 5 bits.
+
+The PID field indicates the used header compression and packet type.
+
+| Bit | Description |
+|--------------------|---------------------------------------------------------------------------------------|
+| 00000 | No header compression |
+| 00001-11111 | Dynamically negotiated header compression identifier, as described in subclause 5.1.1 |
+
+The PID field value indicates the used header compression protocol type and packet type. A specific header compression protocol may utilize a certain range of consecutive values from the PID field value space for different packet types. The Receiving PDCP entity performs the necessary operation (e.g. header decompression) according to the PID field value.
+
+### 8.3.3 Data
+
+The Data field may include either one of the following:
+
+- Uncompressed PDCP SDU;
+- Header compressed PDCP SDU;
+- Header compression protocol feedback information.
+
+### 8.3.4 Sequence number
+
+Length: 16 bits
+
+PDCP SDU sequence number.
+
+### 8.3.5 CS counter
+
+Length: 5 bits
+
+CS counter field value indicates the timing of AMR or AMR WB frame.
+
+# --- 9 Handling of unknown, unforeseen and erroneous protocol data
+
+## 9.1 Invalid PDU type
+
+If a PDCP entity receives a PDCP PDU with a PDU Type set to Reserved (see subclause 8.3.1), it shall:
+
+- discard the PDCP PDU.
+
+If a PDCP entity is not configured for lossless SRNS Relocation or lossless DL RLC PDU size change and receives a PDCP SeqNum PDU, it shall:
+
+- discard the PDCP SeqNum PDU.
+
+## 9.2 Invalid PID value
+
+If a PDCP entity receives a PDCP PDU with a PID value that is not mapped with a valid packet type (see subclause 5.1.1), it shall:
+
+- discard the PDCP PDU.
+
+## 9.3 PDCP Unrecoverable Error Detection
+
+For each radio bearer that is configured to perform PDCP Unrecoverable Error Detection:
+
+- if the PDCP entity receives 2 or 3 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value:
+ - the UE PDCP entity may indicate PDCP Unrecoverable Error to upper layer [2].
+- if the PDCP entity receives 4 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value:
+ - the UE PDCP entity shall indicate PDCP Unrecoverable Error to upper layer [2].
+
+NOTE1: Until the UE receives 4 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value, the UE may apply a self-recovery mechanism. For example, the UE PDCP entity may indicate to RLC layer that HFN can be incremented.
+
+NOTE2: The PDCP unrecoverable error detection is performed before the invalid PDU type check specified in subclause 9.1.
+
+NOTE3: PDCP unrecoverable error detection in the UE can only detect the problem in the downlink.
+
+# --- Annex A (normative): ROHC performance testing
+
+## A.1 Introduction
+
+This subclause defines performance test cases for ROHC. The ROHC profile within scope is profile 0x0001 for compression of RTP/UDP/IP headers only. This subclause is not meant to bring incoherent limitations to implementations, and is not meant to create a sub-specification of [8], [10] either, as a consequence of the requirements on performance that it defines.
+
+### A.1.1 Purpose of the performance testing
+
+The purpose of the test cases is to ensure that ROHC implementations meet minimal requirements that can fairly be expected when subjected to an input sequence that includes frequently occurring and commonly observed changes in the values of header fields. The metrics used correspond to:
+
+- the average compressed header size for an entire test sequence, to assess an implementation's efficiency in terms of its overall compression ratio, and
+- the average compressed header size for different sub-sequences within each test case, to assess an implementation's ability to minimize the variance in compressed header size with respect to the selection of the packet format used for individual packets.
+
+The latter is to avoid a less desirable behaviour where a compressor would consistently and exclusively use two types of compressed header formats; one format that offers no compression but that completely updates and/or repairs the context e.g. when the patterns of the header fields to be compressed do not allow optimal compression, and another format that provides the most efficient compression ratio otherwise. While it is noted that the use of larger headers is perfectly acceptable protocol-wise [8], the tests herein are meant to encourage compressor implementations to actively and efficiently implement compression.
+
+These metrics are defined so that they are not impacted by an implementation's specific robustness algorithm(s) as well as to allow a wide range of compression strategies.
+
+Compressor implementations are expected to implement robustness algorithms according to the optimistic approach for the U/O-modes of operation. The optimistic approach is the part of the selection of the packet format where a format that contains the necessary information to update a field is used a number N time, starting from the packet for which a new value has to be established in the decompressor context. While N is an implementation parameter, the metrics for each sequence in U/O-mode is expressed in terms of this parameter. Implementation should use the value N as an input parameter for the testing, to adapt to the expected robustness level required for the testing. The value of the parameter N is defined in test case definition separately (informative value is given in Annex B.2.3.). Similarly, R-mode operation requires that an update be conveyed to the decompressor until it gets acknowledged; however for R-mode, relevant test cases provide explicit feedback messages when necessary.
+
+The performance tests for ROHC as described in this subclause are carried out by providing a sequence of uncompressed IP/UDP/RTP packets to the ROHC RTP compressor, together with artificially generated feedback messages that are synchronized with the packet sequence. All packets in these sequences are built on the same base structure, with most field values being constant. The performance test cases define different change patterns for three specific fields: the IPv4 IP ID, the RTP SN, and the RTP TS.
+
+### A.1.2 Input sequence for uncompressed headers
+
+The structure of the IPv4/UDP/RTP header and IPv6/UDP/RTP header is outlined in annex A.3, along with tables of the values to be used for each field. Fields with values marked ANY can have any value; these are the addressing fields that uniquely identify the flow of packets being compressed and their respective value does not otherwise affect the expected compression ratio as they are either sent in uncompressed form or completely omitted in compressed packets. The checksum values are dependent on the entire content of the packet and are calculated according to their respective protocol specifications, RFC 768 and RFC 791, which are referred to in the tables. For the input sequence, the UDP checksum with IPv4 shall always be enabled and thus have a non-zero value, i.e the two octets of the UDP checksum are always included as part of the calculation of the compressed header size for both IPv4 and IPv6. Each test sequence defines specific values to create varying change patterns for the IPv4 IP ID, the RTP SN, and the RTP TS. A dummy payload of an arbitrary non-zero value shall be appended at the end of the header data, following the RTP header.
+
+The outline of each test case follows the same format with respect to the input sequences and the requirements. Test 1a and 1b are base tests using a well-behaving flow of packets as one of the inputs. All subsequent tests are based on test 1a or test 1b, each with specific test events added to the packet flow of the base tests.
+
+### A.1.3 Feedback format for the test cases
+
+The feedback messages used in the test cases, when applicable, are artificially generated and interspersed with the input sequence of uncompressed packets. Feedback messages are generated according to the following format:
+
+
+
+```
+
+ 0 1 2 3 4 5 6 7
++---+---+---+---+---+---+---+---+
+| 1 1 1 1 0 | Code | feedback type octet
++---+---+---+---+---+---+---+---+
+|Acktype| Mode | SN |
++---+---+---+---+---+---+---+---+
+| SN |
++---+---+---+---+---+---+---+---+
+| 0 0 0 1 | 0 0 0 1 |
++---+---+---+---+---+---+---+---+
+| CRC |
++---+---+---+---+---+---+---+---+
+
+```
+
+Where:
+
+- Code is set to 0x4 (indicates that feedback data above the type octet is 4 octets)
+- Acktype is set to 0x0 (means ACK)
+- Mode is set as defined by the test case
+- SN is set as defined by the test case
+- CRC is the 8-bit CRC computed over the entire feedback payload including any CID fields but excluding the packet type, the 'Size' field and the 'Code' octet, using the polynomial defined in [8], [10].
+
+NOTE: If compressor uses CID field in compressed packet, the CID field should be included in the feedback packet and the Code and CID should be set as defined in [8].
+
+### A.1.4 Feedback generation for test cases (R-mode only)
+
+This subclause defines a mechanism by which the test equipment shall dynamically generate feedback messages for each test case, once a transition to R-mode has been initiated and for the entire R-mode operation thereafter. Test cases may define additional feedback messages as input to the compressor.
+
+The test equipment shall generate a feedback message when the ROHC packet type octet of the received compressed header matches any of the values as described in the table A.1.4. The compressed header type can be identified by inspecting the packet type octet of the compressed header, i.e. the first octet of the ROHC base header [8].
+
+**Table A.1.4: Bitmasks for feedback generation**
+
+| Compressed Header Type (binary mask) | Packet Type | Outcome |
+|--------------------------------------|---------------|---------------|
+| 01xxxxxx | R-0-CRC | Send feedback |
+| 110xxxxx | UOR-2* | Send feedback |
+| 1111110x | IR | Send feedback |
+| 11111000 | IR-DYN | Send feedback |
+| Other values | Other packets | No feedback |
+
+where 'x' means 'any value'.
+
+The feedback message shall be of the format as described in subclause A.1.3 using:
+
+- Mode is set to 0x3 (means R-mode)
+- SN is set to the RTP SN corresponding to the received compressed header.
+
+The test equipment shall index the input sequence of uncompressed headers using the RTP Sequence Number, and it shall associate the correct RTP SN to each compressed header that it receives back from the compressor. The test equipment can derive the RTP SN by counting the number of received compressed headers.
+
+NOTE: The purpose of this mechanism is only to provide feedback to the compressor when operating in R-mode; it is not meant to make further verifications of any specific ROHC functionality and applies only to the test cases defined in this annex.
+
+### A.1.5 Calculation of compressed header size
+
+The following fields shall be excluded from the calculation of the size of the compressed header in evaluation of compression performance:
+
+- ROHC CID/add-CID octet(s);
+- ROHC padding octets;
+- ROHC segmentation octets;
+- ROHC feedback octets, either piggybacked on the behalf of an associated decompressor or as feedback packets interspersed within the flow of compressed packets.
+
+## A.2 Test outline – RoHC RTP Profile 0x0001
+
+RoHC compression shall start in U-mode, in accordance with RFC3095. Transition to other compression modes shall be initiated by the test equipment sending a feedback packet of type 2, indicating the desired mode transition.
+
+### A.2.1 Test 1a - Base test of ROHC RTP O-mode compressor
+
+#### A.2.1.1 Test purpose
+
+The purpose of the base test case is to verify that the compressor properly implements compression for a well-behaved IP/UDP/RTP packet flow, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [8] when operating in O-mode.
+
+#### A.2.1.2 Sequence details
+
+A sequence consisting of 70 packets in total is used, where all header fields are set according to the basic test packet structure, as described in subclause A.3, with addition of the following:
+
+1. The RTP Sequence Number is a linearly increasing counter with a packet-to-packet delta of 1, set to 0x0000 for the first packet and thus ending with 0x0045 (69) in the last packet of the sequence
+2. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet and thus ending with 0x00002B20 (11040) in the last packet of the sequence
+3. The IP Identification is set to the same value as the RTP Sequence Number; this means that for IPv4 the IP-ID behaviour is not random, thus value(RND)=0 defined in [8] for both IPv4 and IPv6.
+
+Between the 6th and 7th packets (SN=5 and SN=6) of the sequence, a ROHC feedback packet of feedback type 2 is to be given to the ROHC compressor to trigger an immediate transition to O-mode operation. The format of that packet is as follows:
+
+
+
+| | | | | | | | | |
+|---|---------|---|------|---|----|---|------|---------------------|
+| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | |
+| | 1 | 1 | 1 | 1 | 0 | | Code | feedback type octet |
+| | Acktype | | Mode | | SN | | | |
+| | SN | | | | | | | |
+
+
+
+```
+
+| 0 0 0 1 | 0 0 0 1 |
++---+---+---+---+---+---+---+---+
+| CRC |
++---+---+---+---+---+---+---+---+
+
+```
+
+Where:
+
+- Code is set to 0x4 (indicates that feedback data above the type octet is 4 octets)
+- Acktype is set to 0x0 (means ACK)
+- Mode is set to 0x2 (means O-mode)
+- SN is set to 0x000
+- CRC is the 8-bit CRC computed over the entire feedback payload including any CID fields but excluding the packet type, the 'Size' field and the 'Code' octet, using the polynomial defined in [8], [10].
+
+NOTE: If compressor uses CID field in compressed packet, the CID field should be included in the feedback packet and the Code and CID should be set as defined in [8].
+
+#### A.2.1.3 Test requirement
+
+**Table A.2.1.3: Test Requirement for Test 1a**
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|---------------------|--------------------------------------|--------------------------------------|
+| SN <= N-1 | 44 octets | 68 octets |
+| SN >= N | 5 octets | 5 octets |
+
+N is smaller than 8.
+
+The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+Figure A.2.1.3: Expected outcome for Test 1a. A graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels IR, IR-DYN, and 5. The X-axis has labels 0, N-1, 5, 6, and 69. The graph shows a step function: from SN=0 to SN=N-1, the header size is IR; at SN=N-1, it drops to 5; from SN=N to SN=69, it remains at 5. A feedback packet is indicated at SN=5 with the text 'Feedback-2 (ACK, mode=0x2, SN=0x000)'.
+
+**Figure A.2.1.3: Expected outcome for Test 1a**
+
+### A.2.2 Test 1b - Base test of ROHC RTP R-mode compressor
+
+#### A.2.2.1 Test purpose
+
+The purpose of the base test case is to verify that the compressor properly implements compression for a well-behaved IP/UDP/RTP packet flow, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [8] when operating in R-mode.
+
+#### A.2.2.2 Sequence details
+
+A sequence consisting of 70 packets in total is used where all header fields are set according to the basic test packet structure, as described in subclause A.3, with addition of the following:
+
+1. The RTP Sequence Number is a linearly increasing counter with a packet-to-packet delta of 1, set to 0x0000 for the first packet and thus ending with 0x0045 (69) in the last packet of the sequence
+2. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet and thus ending with 0x00002B20 (11040) in the last packet of the sequence.
+3. The IP Identification is set to the same value as the RTP Sequence Number; this means that for IPv4 the IP-ID behaviour is not random, thus value(RND)=0 defined in [8] for both IPv4 and IPv6.
+
+Between the 6th and 7th (SN=5 and SN=6) packets of the sequence, the first ROHC feedback packet of feedback type 2 is to be given to the ROHC compressor to initiate transition to R-mode operation. The format of that packet is as follows:
+
+
+
+```
+
+ 0 1 2 3 4 5 6 7
++---+---+---+---+---+---+---+---+
+| 1 1 1 1 0 | Code | feedback type octet
++---+---+---+---+---+---+---+---+
+|Acktype| Mode | SN |
++---+---+---+---+---+---+---+---+
+| SN |
++---+---+---+---+---+---+---+---+
+| 0 0 0 1 | 0 0 0 1 |
++---+---+---+---+---+---+---+---+
+| CRC |
++---+---+---+---+---+---+---+---+
+
+```
+
+Where:
+
+- Code is set to 0x4 (indicates that feedback data above the type octet is 4 octets)
+- Acktype is set to 0x0 (means ACK)
+- Mode is set to 0x3 (means R-mode)
+- SN is set to 0x000
+- CRC is the 8-bit CRC computed over the entire feedback payload including any CID fields but excluding the packet type, the 'Size' field and the 'Code' octet, using the polynomial defined in [8], [10].
+
+The test equipment waits for a UOR-2, IR-DYN or IR packet from the RoHC compressor with the mode transition parameter set to R. The value of x is the RTP SN of this received packet for which the test equipment generates the second feedback packet of type 2, as described in subclause A.1.4.
+
+#### A.2.2.3 Test requirement
+
+**Table A.2.2.3: Test Requirement for Test 1b**
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|---------------------------|--------------------------------------|--------------------------------------|
+| SN <= N-1 | 44 octets | 68 octets |
+| N <= SN <= 5 | 5 octets | 5 octets |
+| 6 <= SN <= x | 9 octets | 9 octets |
+| SN >= x+1 | 5 octets | 5 octets |
+
+The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+Figure A.2.2.3: Expected outcome for Test 1b. A graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels IR, IR-DYN, 9, and 5. The X-axis has labels 0, N-1, 5, 6, x, x+1, and 69. The graph shows a step function: from 0 to N-1, the header size is IR; from N-1 to 5, it is 5; from 5 to 6, it is 9; from 6 to x, it is 5; and from x to 69, it is 5. Two arrows point to the transitions at SN 5 and SN x, labeled 'Feedback-2 (ACK, mode=0x3, SN=0x000)' and 'Feedback-2 (ACK, mode=0x3, SN=x)' respectively.
+
+**Figure A.2.2.3: Expected outcome for Test 1b**
+
+### A.2.3 Void
+
+A.2.3.1 Void
+
+A.2.3.2 Void
+
+A.2.3.3 Void
+
+### A.2.4 Void
+
+A.2.4.1 Void
+
+A.2.4.2 Void
+
+A.2.4.3 Void
+
+### A.2.5 Test 3a - Re-establishment of TS function after DTX in O-mode
+
+#### A.2.5.1 Test purpose
+
+The purpose of the TS re-establishment test case is to verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it use efficient header formats available to ROHC RTP [8] when operating in O-mode.
+
+#### A.2.5.2 Sequence details
+
+The test sequence is the same as in subclause A.2.1, with the following exception:
+
+1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet.
+2. For packet with SN = 20, TS is increased to represent a 32 (0.64 seconds) packet skip ( $32 \times 160$ ) and is thus set to $(20+32) \times 160 = 8320$ (0x00002080). Then TS continues to grow as stated in 1 above.
+3. For packet with SN = 30, TS is increased to represent a 128 (2.56 seconds) packet skip ( $128 \times 160$ ) and is thus set to $(30+32+128) \times 160 = 30400$ (0x000076C0). Then TS continues to grow as stated in 1 above.
+4. For packet with SN = 40, TS is increased to represent a 2048 (40.96 seconds) packet skip ( $2048 \times 160$ ) and is thus set to $(40+32+128+2048) \times 160 = 359680$ (0x00057D00). Then TS continues to grow as stated in 1 above.
+5. TS thus ends at 364320 (0x00058F20) in the last packet of the sequence with RTP sequence number 69.
+
+#### A.2.5.3 Test requirement
+
+**Table A.2.5.3: Test Requirement for Test 3a**
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|---------------------------------|--------------------------------------|--------------------------------------|
+| SN <= 19 | See Test 1a | |
+| 20 <= SN <= 19 + N | 10 octets | 10 octets |
+| 30 <= SN <= 29 + N | 10 octets | 10 octets |
+| 40 <= SN <= 39 + N | 10 octets | 10 octets |
+| Other SN values | 5 octets | 5 octets |
+
+The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+Figure A.2.5.3: Expected outcome for Test 3a. A graph showing Header Size (octets) on the Y-axis (0 to 10) versus RTP SN on the X-axis (0 to 69). The graph shows a step function representing header sizes. From SN 0 to 19, the header size is 'See Test 1a'. At SN 20, it jumps to 10 octets. At SN 20+N, it drops to 5 octets. At SN 30, it jumps back to 10 octets (labeled 'TS jump(deltaTS=32x160)'). At SN 30+N, it drops to 5 octets. At SN 40, it jumps back to 10 octets (labeled 'TS jump(deltaTS=128x160)'). At SN 40+N, it drops to 5 octets. At SN 69, it drops to 0 octets. The Y-axis also has labels 'IR' and 'IR-DYN'.
+
+**Figure A.2.5.3: Expected outcome for Test 3a**
+
+### A.2.6 Test 3b - Re-establishment of TS function after DTX in R-mode
+
+#### A.2.6.1 Test purpose
+
+The purpose of the TS re-establish test case is to verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it use the efficient header formats available to ROHC RTP [8] when operating in R-mode.
+
+#### A.2.6.2 Sequence details
+
+The test sequence is the same as in subclause A.2.2, with the following exception:
+
+1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet.
+2. For packet with SN = 20, TS is increased to represent a 32 (0.64 seconds) packet skip ( $32 \times 160$ ) and is thus set to $(20+32) \times 160 = 8320$ (0x00002080). Then TS continues to grow as stated in 1 above.
+3. For packet with SN = 30, TS is increased to represent a 128 (2.56 seconds) packet skip ( $128 \times 160$ ) and is thus set to $(30+32+128) \times 160 = 30400$ (0x000076C0). Then TS continues to grow as stated in 1 above.
+4. For packet with SN = 40, TS is increased to represent a 2048 (40.96 seconds) packet skip ( $2048 \times 160$ ) and is thus set to $(40+32+128+2048) \times 160 = 359680$ (0x00057D00). Then TS continues to grow as stated in 1 above.
+5. TS thus ends at 393120 (0x0005FFA0) in the last packet of the sequence with RTP sequence number 69.
+
+#### A.2.6.3 Test requirement
+
+**Table A.2.6.3: Test Requirement for Test 3b**
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|--|--------------------------------------|--------------------------------------|
+|--|--------------------------------------|--------------------------------------|
+
+| | | |
+|---------------------------------|-------------|-----------|
+| SN <=19 | See Test 1b | |
+| 20 <= SN <= 19 + x | 10 octets | 10 octets |
+| 30 <= SN <= 29 + x | 10 octets | 10 octets |
+| 40 <= SN <= 39 + x | 10 octets | 10 octets |
+| Other SN values | 5 octets | 5 octets |
+
+The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+Figure A.2.6.3: Expected outcome for Test 3b. A graph showing Header Size (octets) on the Y-axis (0 to 10) versus RTP SN on the X-axis (0 to 69). The graph shows a step function representing header sizes. From SN 0 to 19, the header size is 10 octets (labeled 'See Test 1b'). At SN 20, there is a 'TS jump(deltaTS=32x160)' and the header size drops to 5 octets. At SN 20+x, it returns to 10 octets. At SN 30, there is a 'TS jump(deltaTS=128x160)' and the header size drops to 5 octets. At SN 30+x, it returns to 10 octets. At SN 40, there is a 'TS jump(deltaTS=2048x160)' and the header size drops to 5 octets. From SN 40+x to 69, the header size remains at 5 octets.
+
+**Figure A.2.6.3: Expected outcome for Test 3b**
+
+### A.2.7 Test 4a - Compressor response to single lost packets in O-mode
+
+#### A.2.7.1 Test purpose
+
+The purpose of this test is to verify that the compressor does not panic just because there is a single missing packet, i.e. the compressed packet size should not increase due to such events.
+
+#### A.2.7.2 Sequence details
+
+The test sequence is the same as in subclause A.2.1, with the following exception:
+
+- Packets with SN 20, 30, and 40 are removed from the sequence.
+
+#### A.2.7.3 Test requirement
+
+Maximal compressed header overhead for the test are the same as in A2.1.
+
+### A.2.8 Test 4b - Compressor response to single lost packets in R-mode
+
+#### A.2.8.1 Test purpose
+
+The purpose of this test is to verify that the compressor does not panic just because there is a single missing packet, i.e. the compressed packet size should not increase due to such events.
+
+#### A.2.8.2 Sequence details
+
+The test sequence is the same as in subclause A.2.2, with the following exception:
+
+- Packets with SN 20, 30, and 40 are removed from the sequence.
+
+#### A.2.8.3 Test requirement
+
+Maximal compressed header overhead for the test are the same as in A2.2.
+
+### A.2.9 Void
+
+A.2.9.1 Void
+
+A.2.9.2 Void
+
+A.2.9.3 Void
+
+### A.2.10 Void
+
+A.2.10.1 Void
+
+A.2.10.2 Void
+
+A.2.10.3 Void
+
+### A.2.11 Test 6a - TS function during DTX with varying delta in O-mode
+
+#### A.2.11.1 Test purpose
+
+The purpose of this test case is to verify that the compressor properly handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses efficient header formats available to ROHC RTP [8] when operating in O-mode.
+
+#### A.2.11.2 Sequence details
+
+The test sequence is the same as in subclause A.2.1, with the following exception:
+
+1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet.
+2. For packets SN = 20, 21 and 22, TS is increased to represent a 7 (0.14 seconds) packet skip (7x160) and is thus set to $(20+7) \times 160 = 4320$ (0x000010E0), $(21+7+7) \times 160 = 5600$ (0x000015E0) and $(22+7+7+7) \times 160 = 6880$ (0x00001AE0), respectively.
+3. For packets SN = 30, 31, 32, 33 and 34, TS is increased to represent a 7 (0.14 seconds) packet skip (7x160) and is thus set to 9280 (0x00002440), 10560 (0x00002940), 11840 (0x00002E40), 13120 (0x00003340) and 14400 (0x00003840) respectively.
+4. For packets SN = 40, 41, 42, 43, 44, 45, and 46, TS is increased to represent a 7 (0.14 seconds) packet skip (7x160) and is thus set to 16480 (0x00004060), 17760 (0x00004560), 19040 (0x00004A60), 20320 (0x00004F60), 21600 (0x00005460), 22880 (0x00005960) and 24160 (0x00005E60) respectively.
+5. TS thus ends at 27840 (0x00006CC0) in the last packet of the sequence with RTP sequence number 69.
+
+#### A.2.11.3 Test requirement
+
+**Table A.2.11.3: Test Requirement for Test 6a**
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|-------------------------------------------------------------------------------------------|---------------------------------------------|---------------------------------------------|
+| SN <= 19 | See Test 1a | |
+| 20 <= SN <= 22 + N
30 <= SN <= 34 + N
40 <= SN <= 46 + N | 15 octets | 15 octets |
+| Other SN values | 5 octets | 5 octets |
+
+The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+Figure A.2.11.3: Expected outcome for Test 6a. A graph showing Header Size (octets) on the Y-axis (values 5, 16, IR, IR-DYN) versus RTP SN on the X-axis (values 0, 20, 21, 22, 22+N, 30, 31, 32, 33, 34, 34+N, 40, 41, 42, 43, 44, 45, 46, 46+N, 69). The graph shows three groups of packets with 'TS jump(deltaTS=7x160)' annotations. The first group (SN 20-22) has a header size of 16 octets. The second group (SN 30-34) has a header size of 5 octets. The third group (SN 40-46) has a header size of 16 octets. The last packet (SN 69) has a header size of 5 octets. A 'See Test 1a' box is present for SN 0-19.
+
+Figure A.2.11.3: Expected outcome for Test 6a
+
+### A.2.12 Test 6b - TS function during DTX with varying delta in R-mode
+
+#### A.2.12.1 Test purpose
+
+The purpose of this test case is to verify how efficiently the compressor handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses the efficient header formats available to ROHC RTP [8] when operating in R-mode.
+
+#### A.2.12.2 Sequence details
+
+The test sequence is the same as in subclause A.2.2, with the following exception:
+
+1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet.
+2. For packets SN = 20, 21 and 22, TS is increased to represent a 7 (0.14 seconds) packet skip ( $7 \times 160$ ) and is thus set to $(20+7) \times 160 = 4320$ (0x000010E0), $(21+7+7) \times 160 = 5600$ (0x000015E0) and $(22+7+7+7) \times 160 = 6880$ (0x00001AE0), respectively.
+3. For packets SN = 30, 31, 32, 33 and 34, TS is increased to represent a 7 (0.14 seconds) packet skip ( $7 \times 160$ ) and is thus set to 9280 (0x00002440), 10560 (0x00002940), 11840 (0x00002E40), 13120 (0x00003340) and 14400 (0x00003840) respectively.
+4. For packets SN = 40, 41, 42, 43, 44, 45, and 46, TS is increased to represent a 7 (0.14 seconds) packet skip ( $7 \times 160$ ) and is thus set to 16480 (0x00004060), 17760 (0x00004560), 19040 (0x00004A60), 20320 (0x00004F60), 21600 (0x00005460), 22880 (0x00005960) and 24160 (0x00005E60) respectively.
+5. TS thus ends at 27840 (0x00006CC0) in the last packet of the sequence with RTP sequence number 69.
+
+#### A.2.12.3 Test requirement
+
+Table A.2.12.3: Test Requirement for Test 6b
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|----------------------------------------------------------------|--------------------------------------|--------------------------------------|
+| SN <= 19 | See Test 1b | |
+| 20 <= SN <= 22 + x
30 <= SN <= 34 + x
40 <= SN <= 46 + x | 15 octets | 15 octets |
+| Other SN values | 5 octets | 5 octets |
+
+The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+Figure A.2.12.3: Expected outcome for Test 6b. This is a graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels for IR, IR-DYN, 16, and 5. The X-axis has labels for 0, 20, 21, 22, 22+x, 30, 31, 32, 33, 34, 34+x, 40, 41, 42, 43, 44, 45, 46, 46+x, and 69. The graph shows a series of steps representing header sizes. The first step is a shaded box labeled 'See Test 1b' with a height of 16 octets, spanning from SN 0 to 20. Subsequent steps have a height of 5 octets. There are three 'TS jump(deltaTS=7x160)' annotations, each with four arrows pointing to specific points on the X-axis: (20, 21, 22, 22+x), (30, 31, 32, 33), and (40, 41, 42, 43). The final step shown is at SN 69.
+
+Figure A.2.12.3: Expected outcome for Test 6b
+
+### A.2.13 Test 7a – SRNS relocation in O-mode
+
+#### A.2.13.1 Test purpose
+
+This test applies to UEs supporting header compression context relocation from Rel-5 onwards.
+
+The purpose of this test case is to verify that the compressor does not interrupt efficient header compression upon reception of the indication about SRNS relocation being performed, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [8] when operating in O-mode when data transmission is resumed after SRNS relocation.
+
+Continuation of efficient header compression upon reception of the indication about SRNS relocation being performed is possible according to subclause 5.4.2, i.e. the compressor shall compress and transmit uplink data as specified in [8] using the assumption that all ROHC uplink packets transmitted are likely to be lost.
+
+#### A.2.13.2 Sequence details
+
+The test sequence is the same as in subclause A.2.1, with the following exception:
+
+Packets with SN = 10 to SN = 59 are removed from the sequence.
+
+SRNS relocation occurs between packet with SN = 9 and packet with SN = 60, thus simulating a 1s long SRNS relocation that affects compression of the IP/UDP/RTP packet flow.
+
+NOTE: The operation of the ROHC compressor is not affected by the time interval between packets with SN = 9 and SN = 60 (timer-based compression is not allowed because no appropriate feedback is provided).
+
+#### A.2.13.3 Test requirement
+
+Table A.2.13.3: Test Requirement for Test 7a
+
+| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 |
+|------------------|--------------------------------------|--------------------------------------|
+| SN <= N-1 | 44 octets | 68 octets |
+| N <= SN <= 9 | 5 octets | 5 octets |
+| 60 <= SN <= 59+N | 8 octets | 8 octets |
+| SN >= 60+N | 5 octets | 5 octets |
+
+N is smaller than 8. The sequence of expected compressed headers can be illustrated as follow (informative):
+
+
+
+A graph showing Header Size (octets) on the y-axis and RTP SN on the x-axis. The y-axis has labels IR, IR-DYN, 8, and 5. The x-axis has labels 0, N, 7, 8, 9, 60, 60 + N, and 69. A vertical arrow labeled 'Feedback(ACK, mode=0x2, SN=0x000)' points down at x=7. A horizontal double-headed arrow labeled 'SRNS relocation' spans from x=9 to x=60. The header size is IR from x=0 to x=N, 5 from x=N to x=9, 8 from x=60 to x=60+N, and 5 from x=60+N to x=69.
+
+Figure A.2.13.3: Expected outcome for Test 7a
+
+## A.3 Test packet structures
+
+IPv6/UDP/RTP
+
+
+
+```
+
+ 1 2 3
+0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|Version| Traffic Class | Flow Label |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Payload Length | Next Header | Hop Limit |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| |
++ +
+| |
++ Source Address +
+| |
++ +
+| |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| |
++ +
+| |
++ Destination Address +
+| |
++ +
+| |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Source Port | Destination Port |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Length | Checksum |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|V=2|P|X| CC |M| PT | sequence number |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| timestamp |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| synchronization source (SSRC) identifier |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+
+```
+
+Bit-level diagram of IPv6/UDP/RTP packet structure showing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, Source Port, Destination Port, Length, Checksum, PT, sequence number, timestamp, and SSRC identifier.
+
+IPv4/UDP/RTP
+
+
+
+```
+
+ 1 2 3
+0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|Version| IHL |Type of Service| Total Length |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Identification |R|D|F| Fragment Offset |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Time to Live | Protocol | Header Checksum |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Source Address |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Destination Address |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Options | Padding |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Source Port | Destination Port |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Length | Checksum |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|V=2|P|X| CC |M| PT | sequence number |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| timestamp |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+
+```
+
+Bit-level diagram of IPv4/UDP/RTP packet structure showing Version, IHL, Type of Service, Total Length, Identification, R, D, F, Fragment Offset, Time to Live, Protocol, Header Checksum, Source Address, Destination Address, Options, Padding, Source Port, Destination Port, Length, Checksum, PT, sequence number, and timestamp.
+
+```
+
+| synchronization source (SSRC) identifier |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+
+```
+
+### IPv6 header fields
+
+| Field | Size (bits) | Value |
+|---------------------|-------------|----------------|
+| Version | 4 | 0x6 |
+| Traffic Class | 8 | 0x00 |
+| Flow Label | 20 | 0x00000 |
+| Payload Length | 16 | 0x0034 |
+| Next Header | 8 | 0x11 |
+| Hop Limit | 8 | Test dependent |
+| Source Address | 128 | ANY |
+| Destination Address | 128 | ANY |
+
+### IPv4 header fields
+
+| Field | Size (bits) | Value |
+|---------------------|-------------|----------------|
+| Version | 4 | 0x4 |
+| Header Length (IHL) | 4 | 0x5 |
+| Type Of Service | 8 | 0x00 |
+| Packet Length | 16 | 0x0048 |
+| Identification | 16 | Test dependent |
+| Reserved flag (R) | 1 | 0x0 |
+| Don't Fragment (D) | 1 | 0x1 |
+| More Fragments (F) | 1 | 0x0 |
+| Fragment Offset | 13 | 0x0000 |
+| Time To Live | 8 | Test dependent |
+| Protocol | 8 | 0x11 |
+| Header Checksum | 16 | See RFC 791 |
+| Source Address | 32 | ANY |
+| Destination Address | 32 | ANY |
+
+### UDP header fields
+
+| Field | Size (bits) | Value |
+|------------------|-------------|-------------|
+| Source Port | 16 | ANY |
+| Destination Port | 16 | ANY |
+| Length | 16 | 0x0034 |
+| Checksum | 16 | See RFC 768 |
+
+### RTP header fields
+
+| Field | Size (bits) | Value |
+|-------------------|-------------|----------------|
+| Version (V) | 2 | 0x2 |
+| Padding (P) | 1 | 0x0 |
+| Extension (X) | 1 | 0x0 |
+| CSRC Counter (CC) | 4 | 0x0 |
+| Marker (M) | 1 | 0x0 |
+| Payload Type (PT) | 7 | 0x60 |
+| Sequence Number | 16 | Test dependent |
+| Timestamp | 32 | Test dependent |
+| SSRC | 32 | ANY |
+
+# Annex B (informative): Reference model for generating ROHC performance requirements
+
+## B.1 Introduction
+
+ROHC compressor and de-compressor may use a set of parameters in order to operate (e.g. L confidence parameter, dynamic FOTimer and static IRTimer, K1 out of N1, K2 out of N2...) that may be optimised for a given application (e.g. Voice over IP, Videotelephony over IP, Interactive Gaming over IP...).
+
+NOTE: L confidence parameter allows setting the number of times an IR or IR-Dyn packet is transmitted and FOTimer and IRTimer are used in order to determine when a transition to a lower compressor state is necessary: The dynamic timer FOTimer triggers SO state to FO state transition and the static IRTimer triggers SO/FO state to IR state transition.
+
+## B.2 For Voice over IP (VoIP) optimisation
+
+### B.2.1 ROHC parameters optimisations for VoIP
+
+For the support of VoIP in UTRAN, ROHC compressor and de-compressor parameter values (L confidence parameter, dynamic FOTimer and static IRTimer, K1 out of N1, K2 out of N2) may be used. Values used in ROHC reference model are given in annex B.2.2 for O-mode.
+
+- The initialisation phase duration;
+- The reaction delay to decompression failure;
+- The header compression ratio (compressed header size / uncompressed header size);
+- The error rates (in UDP and PDCP layers);
+- The amount of transferred data (including ROHC compressed packets and feedbacks);
+- The resource usage (transport block occupancy in the RLC layer).
+
+### B.2.2 Parameter setting for ROHC reference model for VoIP
+
+The following parameters setting is applied in the reference model for ROHC performance tests of VoIP application:
+
+**Table B.2.2: ROHC parameters setting for VoIP**
+
+| ROHC parameter | O-mode |
+|----------------|-------------|
+| L | 2 |
+| FOTimer | 0.12 second |
+| IRTimer | 0.12 second |
+| K1 / N1 | 2 / 20 |
+| K2 / N2 | 1 / 1 |
+
+### B.2.3 Setting the parameter value N in test cases for VoIP
+
+In test cases for VoIP to evaluate ROHC Compression performance for both O- and R-mode, the parameter N (defined in Annex A) is set to 4.
+
+# Annex C (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------|-------|-------|--|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | |
+| 12/1999 | RP-06 | RP-99645 | - | | Approved at TSG-RAN #6 and placed under Change Control | - | 3.0.0 | |
+| 03/2000 | RP-07 | RP-000041 | 004 | | Bit order of PDCP PDUs | 3.0.0 | 3.1.0 | |
+| | RP-07 | RP-000041 | 005 | | Changes to PDCP | 3.0.0 | 3.1.0 | |
+| 06/2000 | RP-08 | RP-000221 | 006 | 4 | Changes in PDCP PDU format due to PDCP sequence numbering | 3.1.0 | 3.2.0 | |
+| 09/2000 | RP-09 | RP-000359 | 009 | 3 | Clarification of PDCP Sequence Numbering | 3.1.0 | 3.2.0 | |
+| | RP-09 | RP-000359 | 011 | | Clarification on how to handle invalid PDUs | 3.2.0 | 3.3.0 | |
+| | RP-09 | RP-000359 | 012 | 2 | Primitives required for SRNS relocation | 3.2.0 | 3.3.0 | |
+| | RP-09 | RP-000359 | 015 | | Handling of invalid PDCP PDU sequence number | 3.2.0 | 3.3.0 | |
+| 03/2001 | RP-11 | RP-010027 | 018 | 1 | Editorial Corrections | 3.3.0 | 3.4.0 | |
+| | RP-11 | RP-010027 | 019 | 1 | Updates necessary for Rel-4 specification | 3.3.0 | 3.4.0 | |
+| | RP-11 | RP-010039 | 017 | 2 | Robust Header Compression | 3.4.0 | 4.0.0 | |
+| 06/2001 | RP-12 | RP-010310 | 021 | | Clarification on PDCP Sequence numbering | 4.0.0 | 4.1.0 | |
+| 09/2001 | RP-13 | RP-010543 | 028 | | Header compression protocol reinitialisation during SRNS relocation | 4.1.0 | 4.2.0 | |
+| | RP-13 | RP-010543 | 030 | | PDCP SDU Sequence Numbering | 4.1.0 | 4.2.0 | |
+| | RP-13 | RP-010543 | 036 | | Corrections to PDCP | 4.1.0 | 4.2.0 | |
+| | RP-13 | RP-010553 | 026 | | Selection of the RFC 3095 CID transmission | 4.1.0 | 4.2.0 | |
+| 12/2001 | RP-14 | RP-010762 | 038 | | General PDCP corrections | 4.2.0 | 4.3.0 | |
+| | RP-14 | RP-010772 | 039 | | Management of Full Header transmission | 4.2.0 | 4.3.0 | |
+| 03/2002 | RP-15 | RP-020069 | 043 | | Clarification on PDCP sequence numbering | 4.3.0 | 4.4.0 | |
+| | RP-15 | - | - | | Upgrade to Release 5 - no technical change | 4.4.0 | 5.0.0 | |
+| 06/2002 | RP-16 | RP-020328 | 049 | | Clarification on PDCP sequence number synchronization procedure | 5.0.0 | 5.1.0 | |
+| | RP-16 | RP-020345 | 050 | | RFC 3095 context relocation | 5.0.0 | 5.1.0 | |
+| 09/2002 | RP-17 | RP-020540 | 053 | | Mapping relation between PDCP and RLC | 5.1.0 | 5.2.0 | |
+| | RP-17 | RP-020552 | 055 | | Corrections to RFC3095 operation | 5.1.0 | 5.2.0 | |
+| | RP-17 | RP-020552 | 057 | | Mismatches between Rel-4 and R'99 in PDCP | 5.1.0 | 5.2.0 | |
+| 12/2003 | RP-22 | - | - | | Upgrade to Release 6 - no technical changes | 5.2.0 | 6.0.0 | |
+| 03/2005 | RP-27 | RP-050067 | 059 | 2 | Lossless DL RLC PDU size change | 6.0.0 | 6.1.0 | |
+| 06/2005 | RP-28 | RP-050315 | 060 | 1 | Introduction of MBMS | 6.1.0 | 6.2.0 | |
+| | RP-28 | RP-050303 | 062 | 2 | Target mode for ROHC operation | 6.1.0 | 6.2.0 | |
+| | RP-28 | RP-050303 | 064 | | Performance testing of ROHC | 6.1.0 | 6.2.0 | |
+| 09/2005 | RP-29 | RP-050468 | 065 | | Correction of MBMS header compression | 6.2.0 | 6.3.0 | |
+| 12/2005 | RP-30 | RP-050784 | 067 | 1 | Correction of the ROHC context relocation procedure | 6.3.0 | 6.4.0 | |
+| 03/2006 | RP-31 | RP-060083 | 069 | | Reference model for generating ROHC performance requirements | 6.4.0 | 6.5.0 | |
+| | RP-31 | - | - | | Upgrade to Release 7 - no technical changes | 6.5.0 | 7.0.0 | |
+| 06/2006 | RP-32 | RP-060374 | 0072 | 1 | RoHC Segmentation, padding and Packet_sizes_allowed parameter removal | 7.0.0 | 7.1.0 | |
+| | RP-32 | RP-060374 | 0075 | | Removal of unnecessary ROHC test cases | 7.0.0 | 7.1.0 | |
+| | RP-32 | RP-060374 | 0078 | | Introduction of ROHC test requirements | 7.0.0 | 7.1.0 | |
+| 09/2006 | RP-33 | RP-060573 | 0081 | | Removal of CID indication in PDCP PID | 7.1.0 | 7.2.0 | |
+| 12/2006 | RP-34 | RP-060717 | 0296 | 1 | Correction of feedback format for ROHC performance testing | 7.2.0 | 7.3.0 | |
+| | RP-34 | RP-060717 | 0299 | 1 | Correction on acceptable configurations for compression entities | 7.2.0 | 7.3.0 | |
+| 03/2007 | RP-35 | RP-070149 | 0301 | | Introduction of new test for O-mode including test requirement in case SRNS relocation for ROHC performance testing | 7.3.0 | 7.4.0 | |
+| 06/2007 | RP-36 | RP-070407 | 0302 | | PDCP reinitialisation at SRNS relocation | 7.4.0 | 7.5.0 | |
+| | RP-36 | RP-070406 | 0304 | | Update of normative references for Robust Header Compression (RFC3095) | 7.4.0 | 7.5.0 | |
+| 09/2007 | RP-37 | RP-070636 | 0305 | | Incorrect reference to RFC number for Header Compression packet formats | 7.5.0 | 7.6.0 | |
+| | RP-37 | RP-070636 | 0306 | | Correction for configuration of RFC3095 header compression | 7.5.0 | 7.6.0 | |
+| 12/2007 | RP-38 | RP-070893 | 0309 | | Clarification on RoHC Performance Testing | 7.6.0 | 7.7.0 | |
+| | RP-38 | RP-070910 | 0310 | | Introduction of CS voice over HSPA | 7.6.0 | 8.0.0 | |
+| 03/2008 | RP-39 | RP-080201 | 0311 | 1 | CS-HSPA UL AMR Rate and maximum jitter time | 8.0.0 | 8.1.0 | |
+| 09/2008 | RP-41 | RP-080687 | 0312 | | Clarification of the CS counter handling | 8.1.0 | 8.2.0 | |
+| 12/2008 | RP-42 | RP-081012 | 0313 | 1 | Delivery of CS Counter | 8.2.0 | 8.3.0 | |
+| 03/2009 | RP-43 | RP-090140 | 0314 | | Coding of the PDCP AMR Data PDU payload | 8.3.0 | 8.4.0 | |
+| | RP-43 | RP-090140 | 0315 | 1 | Condition to identify a CS-HSPA configuration | 8.3.0 | 8.4.0 | |
+| 06/2009 | | | | | Corrects Release shown on cover | 8.4.0 | 8.4.1 | |
+| 07/2009 | | | | | Corrects file properties. Adds previous line in this history table (and this one!). | 8.4.1 | 8.4.2 | |
+| 12/2009 | RP-46 | RP-091328 | 0317 | 2 | UM RLC ciphering error detection and recovery | 8.4.2 | 8.5.0 | |
+| 12/2009 | RP-46 | - | - | - | Upgrade to the Release 9 - no technical change | 8.5.0 | 9.0.0 | |
+| 09/2010 | RP-49 | RP-100859 | 0320 | 1 | Clarification on PDCP CID field (Rel-9) | 9.0.0 | 9.1.0 | |
+
+| | | | | | | | |
+|---------|-------|-----------|------|---|-------------------------------------------------|--------|--------|
+| 03/2011 | RP-51 | - | - | - | Upgrade to the Release 10 - no technical change | 9.1.0 | 10.0.0 |
+| 06/2011 | RP-52 | RP-110825 | 0323 | 1 | Removing RoHC discrepancy | 10.0.0 | 10.1.0 |
+| 09/2012 | RP-57 | - | - | - | Upgrade to the Release 11 - no technical change | 10.1.0 | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25324/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-11/25_series/25324/a7c51c18111139f9aca2805114108565_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80fc620c43ccb5daf4716d491ec4b8681218071b
--- /dev/null
+++ b/marked/Rel-11/25_series/25324/a7c51c18111139f9aca2805114108565_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94b74e35139e343b86d75e445e9878e527482723741c4daefee80f26abc7e4ed
+size 9773
diff --git a/marked/Rel-11/25_series/25324/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/25_series/25324/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b0ce5024c6df34f602ecedee1c987d40b5a0828
--- /dev/null
+++ b/marked/Rel-11/25_series/25324/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:943b37d106af2170cd9b74ced2513767b6df45e64f7a6cc6105a411e18902ac0
+size 52798
diff --git a/marked/Rel-11/25_series/25324/raw.md b/marked/Rel-11/25_series/25324/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9dc4ed1d609ba8dce05bccaea88afbc9fa51220d
--- /dev/null
+++ b/marked/Rel-11/25_series/25324/raw.md
@@ -0,0 +1,941 @@
+
+
+
+
+
+
+# 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 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document 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] TTA/EIA-41-D: "Technical realization of Cell Broadcast Service (CBS)".
+- [8] TTA/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.
+
+
+
+```
+graph TD; user-plane[user-plane] --- BMC-SAP((BMC-SAP)); BMC-SAP --- L2_BMC_sublayer[L2/BMC sublayer]; subgraph L2_BMC_sublayer; BMC[BMC]; end; CBMC-SAP((CBMC-SAP)) --- BMC; RRC[RRc] --- CBMC-SAP; L2_BMC_sublayer --- UM((UM)); UM --- L2_RLC_sublayer[L2/RLC sublayer]; subgraph L2_RLC_sublayer; RLC[RLC]; end; L2_RLC_sublayer --- CTCH-SAP((CTCH-SAP));
+```
+
+Figure 4.1-1: BMC protocol model diagram showing the stack of layers for BMC. At the top is a dashed box labeled 'user-plane'. Below it is an oval labeled 'BMC-SAP'. This is connected to a grey box labeled 'L2/BMC sublayer' which contains a white box labeled 'BMC'. To the left of the BMC sublayer is an oval labeled 'CBMC-SAP' connected to a grey box labeled 'RRc'. Below the BMC sublayer is an oval labeled 'UM'. This is connected to a grey box labeled 'L2/RLC sublayer' which contains a white box labeled 'RLC'. At the bottom is an oval labeled 'CTCH-SAP'.
+
+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,
[, Old-Serial-Number],
New-Serial-Number,
Data-Coding-Scheme,
CB-Data ,
[Category],
Repetition-Period,
Number-of-Broadcasts-Requested |
+| BMC-Data-IND | Message-ID,
Serial-Number,
Data-Coding-Scheme,
CB-Data |
+| BMC-Data-CNF | Message-ID,
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,
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
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant UTRAN
+ Note left of UE: UE
+ Note right of UTRAN: UTRAN
+ UTRAN->>UE: BMC message
+```
+
+Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) and a UTRAN (UMTS Radio Access Network) are shown. An arrow labeled 'BMC message' points from the UTRAN to the UE.
+
+**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 | 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)
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)
$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.
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)
if "Length of CBS Schedule Period" mod 8 = 0 then
N = "Length of CBS Schedule Period" div 8,
else
N = "Length of CBS Schedule Period" div 8 + 1.
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$
E Last CTCH BS index of the CBS schedule period,
$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)
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**
+
+| Condition | Explanation |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MDT1 | If Message Description Type = 1 or 5 then:
the CB-Message-Id IE is included |
+| MDT2 | If Message Description Type = 0 or 4 then:
the Offset to CTCH BS index of first transmission IE is included
pointing to the CTCH BS index where the BMC message is transmitted
the first time within the schedule period. |
+
+**Table 11.9-3: Encoding of Message Description Type**
+
+| Value | Explanation |
+|---------|------------------------------------------------------------------------------------------|
+| 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
(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**
+
+| IE/Group name | Need | Multi | Type and reference | Semantics description |
+|-------------------|------|-------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| Broadcast Address | MP | | Octet string (5) | Address information for higher layer.
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**
+
+| IE/Group name | Need | Multi | Type and reference | Semantics description |
+|---------------|------|-------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| CB Data41 | MP | | Octet string (N)
$N \geq 1$ | Content of CBS message (ANSI-41).
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 n of the Future extension bitmap is set to 1 then Extension n is present.
If bit n of the Future extension bitmap is set to 0 then Extension n 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 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. This IE is coded as the binary representation of the CTCH BS Index. This IE is mapped onto a single octet.
| REL-6 |
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|-------------------------------------------------------------------------------------------|--------|--------|--|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | |
+| 12/1999 | RP-06 | RP-99647 | - | | Approved at TSG-RAN #6 and placed under Change Control | - | 3.0.0 | |
+| 03/2000 | RP-07 | RP-000042 | 001 | | Miscellaneous corrections | 3.0.0 | 3.1.0 | |
+| | RP-07 | RP-000042 | 002 | 2 | Correction of messages and bit ordering | 3.0.0 | 3.1.0 | |
+| 09/2000 | RP-09 | RP-000360 | 005 | | Corrections | 3.1.0 | 3.2.0 | |
+| 12/2000 | RP-10 | RP-000569 | 006 | 1 | Correction to ANSI-41 Cell Broadcast Service | 3.2.0 | 3.3.0 | |
+| 03/2001 | RP-11 | RP-010028 | 007 | | Corrections | 3.3.0 | 3.4.0 | |
+| | RP-11 | - | - | | Upgrade to Release 4 - no technical change | 3.4.0 | 4.0.0 | |
+| 03/2002 | RP-15 | - | - | | Upgrade to Release 5 - no technical change | 4.0.0 | 5.0.0 | |
+| 06/2002 | RP-16 | RP-020329 | 010 | | Clarification on BMC message encoding | 5.0.0 | 5.1.0 | |
+| 12/2002 | RP-18 | RP-020720 | 013 | 1 | Bit order in BMC messages | 5.1.0 | 5.2.0 | |
+| 03/2003 | RP-19 | RP-030102 | 016 | 1 | Maximum size of BMC PDU | 5.2.0 | 5.3.0 | |
+| 12/2003 | RP-22 | - | - | | Upgrade to Release 6 - no technical changes | 5.3.0 | 6.0.0 | |
+| 06/2004 | RP-24 | RP-040202 | 020 | | Corrections to BMC Schedule message | 6.0.0 | 6.1.0 | |
+| 12/2004 | RP-26 | RP-040476 | 024 | 1 | Correction of BMC message bit order and IE coding | 6.1.0 | 6.2.0 | |
+| 06/2005 | RP-28 | RP-050319 | 0025 | | Clarification of RLC concatenation procedure with BMC | 6.2.0 | 6.3.0 | |
+| 09/2005 | RP-29 | RP-050464 | 0027 | 1 | Cell Broadcast | 6.3.0 | 6.4.0 | |
+| 03/2006 | RP-31 | RP-060090 | 0028 | | Introduction of Serial Number in BMC Schedule Message | 6.4.0 | 6.5.0 | |
+| | RP-31 | - | - | | Upgrade to Release 7 - no technical changes | 6.5.0 | 7.0.0 | |
+| 06/2006 | RP-32 | RP-060363 | 0030 | | Interpretation of "Offset to CTCH BS index of first transmission" in BMC Schedule message | 7.0.0 | 7.1.0 | |
+| 12/2007 | RP-38 | - | - | | Upgrade to the Release 8 - no technical change | 7.1.0 | 8.0.0 | |
+| 12/2009 | RP-46 | - | - | | Upgrade to the Release 9 - no technical change | 8.0.0 | 9.0.0 | |
+| 03/2011 | RP-51 | - | - | - | Upgrade to the Release 10 - no technical change | 9.0.0 | 10.0.0 | |
+| 09/2012 | RP-57 | - | - | - | Upgrade to the Release 11 - no technical change | 10.0.0 | 11.0.0 | |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25346/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/25_series/25346/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43d69e6dab6c6cefea177c2910ce5e3ad140c560
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f8fd0ea383af7a7f8ce7bf96f6b1d9e22ea8b6dd1dce704c7ab6231f125d343
+size 16807
diff --git a/marked/Rel-11/25_series/25346/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-11/25_series/25346/036ceaf207a7b289ca76e160892eb724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db134318cc3ae09711c3e292b5e45c9feca08a96
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/036ceaf207a7b289ca76e160892eb724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a4f899df6ad98dd31fd479d2fc46e0698dadb749e38cd267b72061f321b3706d
+size 74719
diff --git a/marked/Rel-11/25_series/25346/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-11/25_series/25346/0f1767577a073167eb9628d72034e083_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b936a1cfaffa49c612256a67818ae6f57db7cca0
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/0f1767577a073167eb9628d72034e083_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8699dd3e723223a908f88f63163d43bf9edb4b60aead6ae561ef3da2a58a688
+size 19867
diff --git a/marked/Rel-11/25_series/25346/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-11/25_series/25346/18291be12b470a557e8c9f3a74e021be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..434ed214f148a477e2d7f66eb77b02e63b6b4495
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/18291be12b470a557e8c9f3a74e021be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac55294411b0d39afdb0deda922b3ac5830585e7749964de412ab83547eeb70a
+size 20721
diff --git a/marked/Rel-11/25_series/25346/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-11/25_series/25346/195611c20b2dc7ed0fa3033392e22908_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5104e94fbc91266a52823d780bb75e41f1a51e6c
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/195611c20b2dc7ed0fa3033392e22908_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70e5fd61d38aa8044fd877f56d123805590a163f6712993325b9f485a6206043
+size 12436
diff --git a/marked/Rel-11/25_series/25346/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-11/25_series/25346/1c140ee5d1a87186977da94a96bfa700_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99f956d1d1b3b18e5e04dec0c6ac6c60f9d7f822
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/1c140ee5d1a87186977da94a96bfa700_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9423f8b3b64bcd4ee3c32b07fed16593b86c4455cc1089fa4532058d7959f415
+size 16258
diff --git a/marked/Rel-11/25_series/25346/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-11/25_series/25346/1f1614411edea7edfc86c839a608e1fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b88da66b6875fd1e9e1669aed6080266d89dcd24
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/1f1614411edea7edfc86c839a608e1fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f51759588bc8dbc871928c0ca71be21f389f8510af594ed73377d82c0ad00831
+size 120814
diff --git a/marked/Rel-11/25_series/25346/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/Rel-11/25_series/25346/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7990da24d969bc5ad0d5df4bf184800a6ddbf4a
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:700b1368604084a5c68124851cd8552d25c9e42878fff0ffc69a29ddf349640d
+size 26976
diff --git a/marked/Rel-11/25_series/25346/2876be3592c7b4878400b85f209b2b6a_img.jpg b/marked/Rel-11/25_series/25346/2876be3592c7b4878400b85f209b2b6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7353dd3871a1ef669f3bb527f7eb69bc62c1177b
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/2876be3592c7b4878400b85f209b2b6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bde8cc7d7d1386b8b1acccb57a412a21f7efc00703e2fdf6b8e21ad0c078101
+size 34589
diff --git a/marked/Rel-11/25_series/25346/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/marked/Rel-11/25_series/25346/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e11ea7c6d2907d04059c8d80d0803ad8f9041f2d
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d8042321767b20f95e8070f93fd8e61d858c736bfd6263d0500ff82c5957a73
+size 16197
diff --git a/marked/Rel-11/25_series/25346/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/25_series/25346/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a81f1f9ab59a372becfc8208ff60d8fe9a514e61
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f270b55ff981849183bb3cf72580040da522c36d1dc16b0d2ce50236ab7a690f
+size 25233
diff --git a/marked/Rel-11/25_series/25346/3711f8e9365e67e6019303fc07924eed_img.jpg b/marked/Rel-11/25_series/25346/3711f8e9365e67e6019303fc07924eed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c21526894a3a5185c7aa025caac709e78051487a
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/3711f8e9365e67e6019303fc07924eed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c19baa11ae30897208952ed6958f5370b1495b5e24a62bbbd8e813e993b9b3ba
+size 12844
diff --git a/marked/Rel-11/25_series/25346/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-11/25_series/25346/3b00a61116faef21d3a6009fd350b46a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35d542d92abf45e2504023dd259f29c7cfe49e8b
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/3b00a61116faef21d3a6009fd350b46a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b9127cfb49bbda629637faca027fe57936941833e3acf81b6b34d63e72d5ac7
+size 35337
diff --git a/marked/Rel-11/25_series/25346/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/25_series/25346/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf78e2ff01643d18dd962300cd3f10d01fd62f2f
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af11e4a8749f63e3e2a38172e46581f641c619ef620a3c90c6fe6eb25a023a06
+size 96056
diff --git a/marked/Rel-11/25_series/25346/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-11/25_series/25346/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d7dabea5e304fa41eaab734a112b3e369d428d5
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b7a3ab11b9ca779e96db140b4bf94b41eab51d1d5ce1446f9411458583de256
+size 14969
diff --git a/marked/Rel-11/25_series/25346/6f659142d4789aa889184459f884787e_img.jpg b/marked/Rel-11/25_series/25346/6f659142d4789aa889184459f884787e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05495dd15ad5d45534bbef12ae581d857a90315c
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/6f659142d4789aa889184459f884787e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb96deaea8d062e47b2969e507eb7973e40f3a75dfbe0b0fd066892b51572afa
+size 42092
diff --git a/marked/Rel-11/25_series/25346/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-11/25_series/25346/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e18813a3286c26315d29b43fb13c207f9855f469
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc8ca8bde558b0232c87a91972760f4c5eebf66a9a3299073c8c621b924a4396
+size 20559
diff --git a/marked/Rel-11/25_series/25346/822e033872d5ab16e861571f47b81ba7_img.jpg b/marked/Rel-11/25_series/25346/822e033872d5ab16e861571f47b81ba7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efb1b2d7578e3caf405411b9db8465d030fe5440
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/822e033872d5ab16e861571f47b81ba7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9a3a64dd390f63500fff600e4bb0a28352d097b02b5f8334eed19aa78775c94
+size 20274
diff --git a/marked/Rel-11/25_series/25346/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/25_series/25346/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f04beb16b83cf66aa3037c20e180e2023e7381c6
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f710516f391400702d4b31ea9ccfad11709347b3ea2c5897c0aa09e14c3e0c5
+size 28425
diff --git a/marked/Rel-11/25_series/25346/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/Rel-11/25_series/25346/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b9a7476d68c1e5041513d6c66e8908cfa3a7a49
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6fca6686e3a1bbc360a5ba3170440bb90d65d56e94835664ba6fbc7d75a38c74
+size 34705
diff --git a/marked/Rel-11/25_series/25346/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/25_series/25346/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2c4ba62885fa93fb8de74461d8f7a70d789897c
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13a18929448c3713af9adcf9b6eb4f3ed11ea032f26f220af3b3e3e7ef21cf27
+size 75560
diff --git a/marked/Rel-11/25_series/25346/94d3fdcc244924326f02533aeb2d93fc_img.jpg b/marked/Rel-11/25_series/25346/94d3fdcc244924326f02533aeb2d93fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e418666a61fd6dc6693ed9e9af6e023d148eec5
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/94d3fdcc244924326f02533aeb2d93fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe60a3394c36073795395efec1cf8e530bddc54165ceb0f1b7c6e569c4a9e816
+size 38226
diff --git a/marked/Rel-11/25_series/25346/9c8070d46f1d2480a875239e792f1ef6_img.jpg b/marked/Rel-11/25_series/25346/9c8070d46f1d2480a875239e792f1ef6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3c52488c64617f384839322c71d7cb8c19d8ae1
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/9c8070d46f1d2480a875239e792f1ef6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:038dc5589e8ace14b4763b1091fe3e08269d86e927ca28abbe66aae9a15dd7d5
+size 116797
diff --git a/marked/Rel-11/25_series/25346/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-11/25_series/25346/9ed248b025d766251d58be10b01a1cc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..808bc7e33c7dc866f215fda2c66abf35f89748b5
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/9ed248b025d766251d58be10b01a1cc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27cd4a2e44cf63265164da419afcf98ae888a7ab2432f9f7ad425997f594da2c
+size 40028
diff --git a/marked/Rel-11/25_series/25346/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-11/25_series/25346/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..377d3187201cfc843a9b5efa1a0e45be68cdc73a
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6e94467c3a525b1fe8141111b028b95aa33d18c0da468c691179e6276ce2363
+size 14475
diff --git a/marked/Rel-11/25_series/25346/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-11/25_series/25346/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05c576636c46390c4a65ebcb569caea7bb10c85e
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:81381f619a120d9e67aa454f57e384a6b11ed91afc2cba3d8c97efff744d01da
+size 22910
diff --git a/marked/Rel-11/25_series/25346/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-11/25_series/25346/a5184899f915014fa38608754efcc9c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f80905cfb0dd671b5e7ab7c6c3813bded2cb8267
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/a5184899f915014fa38608754efcc9c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5824393c2aace3dc9114ebee24b7a8c153409aeb394c74ad3ca6159632da6cb
+size 22505
diff --git a/marked/Rel-11/25_series/25346/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-11/25_series/25346/adc59ed6840bcb2d392ea323abfccedc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88ba4b54259a51de77733a744cdf21d879e61b15
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/adc59ed6840bcb2d392ea323abfccedc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e0927a63102e4430cbf36b90de9aa4c129eb461d55aaa9c0334fedbfa562580
+size 23587
diff --git a/marked/Rel-11/25_series/25346/ae375ead8aa673286b534e079e9a8533_img.jpg b/marked/Rel-11/25_series/25346/ae375ead8aa673286b534e079e9a8533_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32497eb3a2b4f11cc85ad06b2305338246933933
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/ae375ead8aa673286b534e079e9a8533_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:010b65b9d7cd2a8b1c8c3ecd6fb347095def02ac8d5dd619766a8a8ddf99be89
+size 20531
diff --git a/marked/Rel-11/25_series/25346/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/25_series/25346/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8fcdb419676458d2b357b4d78237fa0c3687160
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9bd2968e34fff4bb5d316d1e8d6bdfd8aa881eb1caef68a4fdc1020e6d4b139d
+size 50598
diff --git a/marked/Rel-11/25_series/25346/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-11/25_series/25346/b06a4c871dfd0ce034cf801519d0039a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..493bba4cbb9af7f56583024dbf80b5eb5ad1c562
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/b06a4c871dfd0ce034cf801519d0039a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d57c7480573fcdc529c5eb393d71d30688e8ea492e4c44d24fa45c1c027ff3f0
+size 14939
diff --git a/marked/Rel-11/25_series/25346/b17128855e79bd21a030ff6fcf1c3310_img.jpg b/marked/Rel-11/25_series/25346/b17128855e79bd21a030ff6fcf1c3310_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0b8d8f021ecc044ba0d898900e23a7137e2f755
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/b17128855e79bd21a030ff6fcf1c3310_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3a38c24784a949e7051c9143272d4080630ab72fd77d1857c9388be2a32dbf7
+size 9697
diff --git a/marked/Rel-11/25_series/25346/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-11/25_series/25346/b2ea162a0f53d5e0504b7d28346e0754_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2c16096f588aee6f770f3d3137dd7b0255943db
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/b2ea162a0f53d5e0504b7d28346e0754_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6cbcab8c9d245c276481e1f10cb4112dc6d701d712e6ace1581ffdd6ac13d1f
+size 21965
diff --git a/marked/Rel-11/25_series/25346/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-11/25_series/25346/b4f6d3668f7e851eaff07ccf26001623_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..158289deee90774e69ef83d8af2c893a1e1150df
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/b4f6d3668f7e851eaff07ccf26001623_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e87d308ec8a9f2f6509cebfff5a8998931e6b0961fbe5e95a30952987bd9468d
+size 19657
diff --git a/marked/Rel-11/25_series/25346/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/marked/Rel-11/25_series/25346/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df7752efbe2bada0782467e8ee972570ce06fd0b
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3fffbb4ab1f5009741e888f0e1b513919ac463af2f6a60164e186bf874141973
+size 13296
diff --git a/marked/Rel-11/25_series/25346/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg b/marked/Rel-11/25_series/25346/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..623cb5eb3811fee0cf55e11484a4c60f20b44074
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a615f35694df9109cc0bf3f6d753b72e948cccb75d482149bae7113dd9daa78
+size 21165
diff --git a/marked/Rel-11/25_series/25346/cdd9c57c9c578160002ead5cdaef414d_img.jpg b/marked/Rel-11/25_series/25346/cdd9c57c9c578160002ead5cdaef414d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..135709755bcd05c2004ec5fcdcc01f0d6ec30e6f
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/cdd9c57c9c578160002ead5cdaef414d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acc191847cef3f9e1331350ab464d8dc18b1ab383be8f5d15c39dfeb5bc51330
+size 16152
diff --git a/marked/Rel-11/25_series/25346/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Rel-11/25_series/25346/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a659e089bd41fee78703f4c61518344b1e2393fd
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53201f133b73894ccb356bc1712aa07f10b1f5cbed36b08def315c33015dad16
+size 16438
diff --git a/marked/Rel-11/25_series/25346/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/25_series/25346/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..307f1d4485aa567737cdd9d96f1acbe5202b4f36
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bb362abe518b70bd11c01f85fa031902b33e271a3d9bd692728393213acb1ac
+size 53197
diff --git a/marked/Rel-11/25_series/25346/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-11/25_series/25346/d3b5eac55166fc428a223bba5c46961b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c652961c44957cc5f9513887e910be571d6390d
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/d3b5eac55166fc428a223bba5c46961b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:759646984c1addd533ae1bbf23a7039f1692911bf0588a1991920a900f6eb608
+size 36957
diff --git a/marked/Rel-11/25_series/25346/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-11/25_series/25346/d7948c38a18636aefecdd95388196460_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ab0d0d4161d31c2ecbe87dc2fdf3cb4656f0cee
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/d7948c38a18636aefecdd95388196460_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:844d43d7117df8e3edd879006c51839c661e8c74a01322f2d2637545d9bec265
+size 12565
diff --git a/marked/Rel-11/25_series/25346/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/25_series/25346/d9c0a780cd22626253dab4aa41699e2f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e28416621788b1ac7708428561ad2ef2370d2a42
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/d9c0a780cd22626253dab4aa41699e2f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3af4fdcb28258238efbd4c4c9b555ecb1e8221e42d439fbf3ddfc0dddc9cde13
+size 77932
diff --git a/marked/Rel-11/25_series/25346/df65c22a46ec3e7285e44de67d3a59cf_img.jpg b/marked/Rel-11/25_series/25346/df65c22a46ec3e7285e44de67d3a59cf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3803466237ecdab453e03fad50feb1b083b94964
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/df65c22a46ec3e7285e44de67d3a59cf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8be3fcb470d5033c6809d8c983857e5568a7ea6e0271d80a3a986dc343724f72
+size 13428
diff --git a/marked/Rel-11/25_series/25346/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/marked/Rel-11/25_series/25346/e3eebf9854831ba50eca8b26c468f65e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e03d0a740965125d57081152013991dccbc11d61
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/e3eebf9854831ba50eca8b26c468f65e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bbe8b9fe0be4578e2a757c6fa9e0e52888ceba3b664c48e706a6c830d3ea700
+size 13428
diff --git a/marked/Rel-11/25_series/25346/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Rel-11/25_series/25346/e417ae35ab07134888be901c201d54cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d31bcc14a72482cb66a3c4a425eadcd2f7129bd9
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/e417ae35ab07134888be901c201d54cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a607e309e3deeb606b2f1588f23bd656904ece553e26af23967f814c12f71e34
+size 14358
diff --git a/marked/Rel-11/25_series/25346/e9f5aa7b76362051c591d6783211f820_img.jpg b/marked/Rel-11/25_series/25346/e9f5aa7b76362051c591d6783211f820_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7cd384b5822b0eb6a346a607df53ad539dc9d62
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/e9f5aa7b76362051c591d6783211f820_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5067123b2bd54470ec21124b0db8c3337ba96a9cb8b00cc962b378cb83b37604
+size 11901
diff --git a/marked/Rel-11/25_series/25346/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Rel-11/25_series/25346/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a95da0bf8429ed9be19a16cba6fb90a72ac4d22
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc696bcd8c943cbc6592d1107521823804b09a3ba23773002691edb0890f7a13
+size 31264
diff --git a/marked/Rel-11/25_series/25346/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-11/25_series/25346/fe7304192caf64cda93b580c5e7e5c06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..810bfbdd0ab58af515233f583fd1c1a56965b376
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/fe7304192caf64cda93b580c5e7e5c06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c4ad3e082d4a16ccb5d7669e99aa5937e8dfe59be41fb4dd670b4116ad50d4b
+size 12776
diff --git a/marked/Rel-11/25_series/25346/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-11/25_series/25346/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5aaefe2934beec30ff4357406ebc2d10daa301a
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7814f3dfda144d6ec23feec204b0f59c3c2308cce962ab0e294d20218f627bc5
+size 21314
diff --git a/marked/Rel-11/25_series/25346/raw.md b/marked/Rel-11/25_series/25346/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..15b7fb28a7e25e93991bc5505efcd1e595f7e8c1
--- /dev/null
+++ b/marked/Rel-11/25_series/25346/raw.md
@@ -0,0 +1,2600 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions, symbols and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Symbols..... | 9 |
+| 3.3 Abbreviations ..... | 9 |
+| 4 Background and introduction..... | 10 |
+| 5 MBMS UTRAN and protocol architecture..... | 10 |
+| 5.1 MBMS UTRAN architecture principles ..... | 10 |
+| 5.1.1 MBMS Service Context in CRNC ..... | 10 |
+| 5.1.2 MBMS Session start and MBMS Session Stop..... | 11 |
+| 5.1.3 MBMS Iu bearer..... | 11 |
+| 5.1.4 MBMS Iub bearer..... | 12 |
+| 5.1.5 Mapping of MBMS Iu bearer to p-t-p and p-t-m connections ..... | 12 |
+| 5.1.6 UE Linking/De-linking..... | 12 |
+| 5.1.7 RNC Registration ..... | 14 |
+| 5.1.8 RNC De-Registration ..... | 14 |
+| 5.1.9 CN De-Registration..... | 14 |
+| 5.1.10 URA Linking/De-linking..... | 14 |
+| 5.1.11 IP Multicast Distribution ..... | 15 |
+| 5.2 MBMS Uu Principles..... | 15 |
+| 5.2.1 MBMS Service States in UE..... | 15 |
+| 5.2.2 One PDCP and RLC entity shared among multiple cells within one RNS ..... | 16 |
+| 5.2.3 MCCH Information Scheduling ..... | 16 |
+| 5.2.4 MBMS Notification..... | 17 |
+| 5.2.5 MBMS Counting ..... | 18 |
+| 5.2.6 MBMS Radio Bearer Release in the UE ..... | 19 |
+| 5.2.7 MBMS Session Repetition ..... | 20 |
+| 5.2.8 MBMS Service Prioritisation ..... | 20 |
+| 5.3 Protocol structure ..... | 21 |
+| 5.3.1 MBMS User Plane Protocol Stack Architecture ..... | 21 |
+| 5.3.2 MBMS Control Plane Protocol Stack Architecture..... | 22 |
+| 5.4 MAC architecture..... | 23 |
+| 5.4.1 UTRAN MAC Architecture to support MBMS ..... | 23 |
+| 5.4.2 MAC-c/sh/m architecture: UTRAN side..... | 23 |
+| 5.4.3 MAC-c/sh/m architecture: UE side ..... | 24 |
+| 6 MBMS Channel Structure..... | 25 |
+| 6.1 Point-to-Point Transmission..... | 25 |
+| 6.2 Point-to-multipoint Transmission ..... | 25 |
+| 6.2.1 Logical Channels ..... | 25 |
+| 6.2.1.1 MBMS point-to-multipoint Control Channel (MCCH)..... | 25 |
+| 6.2.1.2 MBMS point-to-multipoint Traffic Channel (MTCH)..... | 25 |
+| 6.2.1.3 MBMS point-to-multipoint Scheduling Channel (MSCH) ..... | 25 |
+| 6.2.2 Transport Channel ..... | 26 |
+| 6.2.3 Physical Channel ..... | 26 |
+| 6.2.4 Mapping between channels ..... | 26 |
+| 6.2.5 Data Flows through Layer 2 ..... | 27 |
+| 6.2.5.1 Data flow for MCCH mapped to FACH..... | 27 |
+| 6.2.5.2 Data flow for MTCH mapped to FACH..... | 27 |
+| 6.2.5.3 Data flow for MSCH mapped to FACH..... | 27 |
+| 6.3 MBMS Notification Indicator Channel..... | 27 |
+| 7 MBMS Reception and UE Capability..... | 27 |
+| 7.1 Selective and Soft Combining for MBMS P-T-M transmission..... | 27 |
+
+| | | |
+|------------|------------------------------------------------------------------------|----|
+| 7.1.bis | Simulcast Combining (TDD only) ..... | 28 |
+| 7.1.ter | Chip Combining (1.28Mcps TDD)..... | 29 |
+| 7.1A | MBMS over a Single Frequency Network (MBSFN)..... | 30 |
+| 7.1A.1 | 3.84 / 7.68 MCPS TDD MBMS over a Single Frequency Network (MBSFN)..... | 31 |
+| 7.1A.2 | FDD MBMS over a Single Frequency Network (MBSFN)..... | 32 |
+| 7.1A.3 | 1.28 MCPS TDD MBMS over a Single Frequency Network (MBSFN)..... | 32 |
+| 7.1A.4 | 3.84 Mcps TDD IMB MBMS over a Single Frequency Network (MBSFN) ..... | 33 |
+| 7.1B | MBMS in case of inter-RNC synchronization ..... | 34 |
+| 7.1B.1 | Control Plane aspects ..... | 34 |
+| 7.1B.1.1 | MBMS Parameter Configurations ..... | 34 |
+| 7.1B.1.2 | MBMS Counting and mode switch coordination ..... | 34 |
+| 7.1B.1.3 | Control Plane Coordination at MBMS Session Start..... | 35 |
+| 7.1B.1.3.1 | Coordination of neighbor cell configuration ..... | 35 |
+| 7.1B.1.4 | MCCH synchronization in an MBSFN cluster ..... | 36 |
+| 7.1B.2 | User Plane aspects ..... | 36 |
+| 7.1B.2.1 | Timing requirements..... | 36 |
+| 7.1B.2.2 | MBMS User Data flow synchronization ..... | 36 |
+| 7.1B.2.3 | User Plane recovery in case of Multiple Packets Loss ..... | 37 |
+| 7.2 | UE Capability ..... | 38 |
+| 7.3 | MBMS Reception..... | 39 |
+| 7.3.1 | MBMS Reception in RRC Idle Mode ..... | 39 |
+| 7.3.2 | MBMS Reception in RRC Connected Mode: URA_PCH state..... | 39 |
+| 7.3.3 | MBMS Reception in RRC Connected Mode: CELL_PCH state ..... | 40 |
+| 7.3.4 | MBMS Reception in RRC Connected Mode: CELL_FACH state ..... | 40 |
+| 7.3.5 | MBMS Reception in RRC Connected Mode: CELL_DCH state ..... | 40 |
+| 8 | UTRAN Signalling Flows for MBMS ..... | 41 |
+| 8.1 | MBMS High Level Signalling Scenarios..... | 41 |
+| 8.1.1 | Session start..... | 41 |
+| 8.1.2 | Joining (during a session)..... | 43 |
+| 8.1.3 | Recounting..... | 44 |
+| 8.1.4 | Session stop ..... | 45 |
+| 8.2 | MBMS RNC Signalling Flows ..... | 45 |
+| 8.2.1 | MBMS Session Start procedure ..... | 45 |
+| 8.2.2 | MBMS Session Update procedure ..... | 46 |
+| 8.2.3 | MBMS Session Stop procedure..... | 46 |
+| 8.2.4 | RNC Registration procedure ..... | 47 |
+| 8.2.5 | RNC De-Registration procedure ..... | 47 |
+| 8.2.6 | CN De-Registration procedure ..... | 47 |
+| 8.2.7 | MBMS Channel Type Switching over Uu ..... | 48 |
+| 8.2.8 | MBMS UE Linking ..... | 48 |
+| 8.2.9 | MBMS UE De-Linking ..... | 49 |
+| 8.2.10 | MBMS Service Id Request..... | 49 |
+| 8.2.11 | MBMS Attach/Detach over Iur ..... | 50 |
+| 8.2.12 | MBMS Channel Type Reconfiguration over Iur ..... | 50 |
+| 8.2.13 | Information Exchange over Iur..... | 51 |
+| 8.2.14 | MBMS RAB Establishment Indication ..... | 52 |
+| 8.2.15 | MBMS RAB Release ..... | 52 |
+| 8.2.16 | MBMS Session Start procedure in case of IP Multicast transport ..... | 53 |
+| 8.2.17 | MBSFN MCCH Information..... | 54 |
+| 8.3 | MBMS Uu Signalling Flows..... | 54 |
+| 8.3.1 | Broadcast of MBMS System Information ..... | 54 |
+| 8.3.2 | MBMS Service Information ..... | 55 |
+| 8.3.3 | MBMS Radio Bearer Information..... | 55 |
+| 8.3.4 | MBMS Access Information..... | 56 |
+| 8.3.5 | MBMS Neighbouring Cell Information ..... | 56 |
+| 8.3.6 | MBMS Joined Indication ..... | 57 |
+| 8.3.7 | MTCH Scheduling Information ..... | 57 |
+| 8.3.8 | MBMS Change Information..... | 58 |
+| 8.3.9 | MBMS P-T-P Modification Request..... | 58 |
+| 8.3.10 | MBMS Counting Response..... | 59 |
+| 8.3.11 | MBMS Selected Services Information ..... | 59 |
+
+| | | |
+|-------------------------------|-------------------------------------------------------------------|-----------|
+| 9 | Security for MBMS..... | 59 |
+| 10 | Mobility Procedures for MBMS ..... | 60 |
+| 10.1 | Use of Periodical Transmission of MBMS Critical Information ..... | 60 |
+| 10.2 | UE Actions for Mobility ..... | 60 |
+| 10.2.1 | RRC idle mode ..... | 60 |
+| 10.2.2 | URA_PCH State ..... | 61 |
+| 10.2.3 | CELL_PCH ..... | 61 |
+| 10.2.4 | CELL_FACH ..... | 62 |
+| 10.2.5 | CELL_DCH State..... | 62 |
+| 11 | Resource Management for MBMS ..... | 63 |
+| 11.1 | MBMS Access Control Procedure ..... | 63 |
+| 11.2 | Frequency layer Convergence..... | 64 |
+| 11.3 | Frequency layer Dispersion..... | 64 |
+| Annex A (informative): | MBMS Phases in UTRAN ..... | 65 |
+| A1 | Security for MBMS..... | 65 |
+| A2 | MBMS Phase 2 ..... | 65 |
+| A3 | MBMS Phase 3 ..... | 66 |
+| A4 | MBMS Phases and Status Parameters ..... | 66 |
+| Annex B (informative): | MBMS Control Information ..... | 67 |
+| Annex C (informative): | Change history..... | 69 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is a technical specification of the overall support of Multimedia Broadcast Multicast Service 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.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1".
+- [3] 3GPP TS 22.246: "MBMS User Services; Stage 1".
+- [4] 3GPP TS 23.246: "Multimedia Broadcast Multicast Service; Architecture and Functional Description".
+- [5] 3GPP TR 25.992: "Multimedia Broadcast Multicast Service (MBMS); UTRAN/GERAN Requirements".
+- [6] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
+- [7] 3GPP TS 33.246: "3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS)".
+- [8] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [9] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".
+- [10] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".
+- [11] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
+- [12] 3GPP TS 25.306: "UE Radio Access capabilities".
+- [13] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification".
+- [14] 3GPP TS 25.446: "MBMS Synchronisation Protocol (SYNC)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+![Figure 3.1: MBMS Timeline, based on [4].](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates the MBMS timeline across three horizontal axes: UE1 events, UE2 events, and Service 1. The timeline is divided into three phases: Phase 1 (MBMS phase in UTRAN), Phase 2, and Phase 3. Key events include:
+
+- UE1 events:** Subscription can be at any time, subscription to service 1, service leave.
+- UE2 events:** Service join by the user can be at any time.
+- Service 1:** Start service 1 announcement, 1st session start, idle period of session 1, Data transfer (Service 1 session 1), session stop, Data transfer (Service 1 session 2), Stop Service 1 announcement.
+- Data Transfer:** Announcement, Data sent to UE1, Data sent to UE1 and UE2, Data sent to UE2.
+- Phases:** Phase 1 (MBMS phase in UTRAN), Phase 2, Phase 3.
+
+Figure 3.1: MBMS Timeline, based on [4].
+
+Figure 3.1: MBMS Timeline, based on [4].
+
+**MBMS session start** is the point at which the BM-SC is ready to send data.
+
+**MBMS notification** informs the UEs about forthcoming and about ongoing MBMS data transfer.
+
+**MBMS Cell Group** is a group of multiple cells belonging to one RNS and sharing one PDCP and RLC entity to utilize p-t-m transmission of the MBMS Service
+
+**MBMS session stop** is the point at which the BM-SC determines that there will be no more data to send for some period of time.
+
+**Data transfer** is the phase when MBMS data are transferred to the UEs.
+
+**MBMS service availability** is the phase between start of service announcement and the end of the last session or stop of service announcement.
+
+**MBMS Iu data bearer** denotes the data bearer established between SGSN and RNC to transport MBMS data
+
+**MBMS radio bearer** denotes the data bearer established between RNC and UE(s) to transport MBMS data
+
+**MBMS RAB** denotes both, the MBMS Iu data bearer and the MBMS radio bearer
+
+**MBMS Service Context** contains the necessary information for the UTRAN to control the MBMS Service in UTRAN.
+
+**MBMS Activated Services:** a set of services made up of those in MBMS multicast mode that the UE has joined as well as those in MBMS broadcast mode that the UE is interested in receiving.
+
+**MBMS Selected Services:** a subset of the MBMS activated services in MBMS Broadcast mode for which the UE applies RRC procedures to inform UTRAN that the service has been selected (by upper layers).
+
+**MBMS Iu signalling connection** denotes the signalling connection established between the RNC and the CN node to serve one MBMS Service Context.
+
+**MBMS Service Announcement:** Mechanism to allow users to be informed about the MBMS services available [4]
+
+**Pool area:** see definition in ref.[6]
+
+**MBMS Multicast Service Activation:** see description in ref.[4]
+
+**Critical Information:** MBMS Neighbouring Cell Information, MBMS Radio Bearer Information and MBMS Service Information sent on MCCH.
+
+**Non-critical information:** MBMS Access Information sent on MCCH.
+
+**MBMS Service Area:** The area in which a specific MBMS session is made available. Each transmission and retransmission of an MBMS session of an MBMS Bearer Service may be made available to a different MBMS Service Area. The MBMS Service Area is described by a list of MBMS Service Area IDs, where each MBMS Service Area ID represents a group of cells. The definition of an MBMS Service Area ID is independent of an MBMS session, and of an MBMS Bearer Service. [4]
+
+**L1-combining schedule:** Indicates when the soft combining is applicable between the specific S-CCPCH of the cell and the specific S-CCPCH of the neighbouring cell.
+
+**MBMS Single Frequency Network:** A simulcast transmission technique realised by transmission of identical waveforms at the same time via a group of cells covering a geographic area.
+
+**MBSFN mode:** In order to achieve higher spectral efficiency synchronized cells operate in MBSFN mode which implies that they transmit exactly the same content over an area that is seen as one MBSFN cell by the UE.
+
+**MBSFN cluster:** Set of cells operating in MBSFN mode providing only MBMS service in PtM mode and seen as one cell by a UE.
+
+**MBMS service transmission schedule:** Indicates when the specific MBMS service is expected to be transmitted in the cell in specific S-CCPCH. The information is transmitted on MSCH
+
+**S-CCPCH:** In case of TDD, the S-CCPCH refers to the CCTrCH carrying FACH. In case of 3.84 Mcps TDD MBSFN IMB, the S-CCPCH refers either to S-CCPCH frame type 1 or S-CCPCH frame type 2, or both S-CCPCH frame type 1 and S-CCPCH frame type 2.
+
+**UE Link** denotes the stored information in the RNC on MBMS services joined by the UE in the state other than URA\_PCH in the course of the UE Linking procedure.
+
+**URA Link** denotes the stored information in the RNC on MBMS services joined by a UE in URA\_PCH state in the course of the URA Linking procedure.
+
+**MBMS Master RNC:** role an RNC can take with respect to one or more specific MBSFN cluster(s). MRNC may be used for Inter-RNC MBSFN operation whenever dynamic synchronization of radio resources used for MBMS services is centrally controlled. There is only one MBMS Master RNC for any MBSFN cluster, which may control one or more MBSFN cluster(s). The MRNC has the overall control of the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s).
+
+**Synchronisation Sequence:** Each SYNC PDU contains a time stamp which indicates the start time of the synchronisation sequence. Each synchronisation sequence has the same duration which is configured in the BM-SC and the RNCs operating in inter-RNC synchronisation mode.
+
+**Synchronisation Period:** The synchronisation period provides the time reference for the indication of the start time of each synchronisation sequence. The time stamp which is provided in each SYNC PDU is a relative value which refers to the start time of the synchronisation period. The duration of the synchronisation period is configurable.
+
+## 3.2 Symbols
+
+(void)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 [1] and the following apply:
+
+| | |
+|-----------------|---------------------------------------------------------|
+| CELL_DCH | |
+| CELL_FACH | |
+| FFS | For Further Study |
+| FLC | Frequency Layer Convergence |
+| IMB | Integrated Mobile Broadcast |
+| LCI | Layer Convergence Information |
+| MBMS | Multimedia Broadcast Multicast Service |
+| MBSFN | MBMS over a Single Frequency Network |
+| MBMS service ID | Multimedia Broadcast Multicast Service service Identity |
+| MBMS Session ID | Multimedia Broadcast Multicast Service session identity |
+| MCCH | MBMS point-to-multipoint Control Channel |
+| MICH | MBMS notification Indicator Channel |
+| MRNC | MBMS Master RNC |
+| MSCH | MBMS point-to-multipoint Scheduling Channel |
+| MTCH | MBMS point-to-multipoint Traffic Channel |
+| NI | Notification Indicator |
+| PL | Preferred Layer |
+| p-t-p | Point-to-Point |
+| p-t-m | Point-to-Multipoint |
+| PF | Probability Factor |
+
+# --- 4 Background and introduction
+
+The Introduction of the Multimedia Broadcast Multicast Service in UTRA describes techniques for optimised transmission of MBMS bearer service in UTRA such as point-to-multipoint transmission, selective combining and transmission mode selection between point-to-multipoint and point-to-point bearer.
+
+The Stage 1 MBMS service requirements are defined in [2] and MBMS Stage 1 user services are defined in [3]. UTRAN (and GERAN) requirements are covered in TR 25.992 [5]. The overall architecture, functional description and the reference architecture of MBMS are covered in TS 23.246 [3].
+
+# --- 5 MBMS UTRAN and protocol architecture
+
+## 5.1 MBMS UTRAN architecture principles
+
+### 5.1.1 MBMS Service Context in CRNC
+
+Each RNC-which is controlling one or several cells within an MBMS Service area maintains an MBMS Service Context for each MBMS service.
+
+- 1 Each CRNC MBMS Service Context is associated with an MBMS service ID, i.e. TMGI.
+- 2 The CRNC MBMS Service Context contains a list of PMM connected mode UEs which are present in one or several cells of the CRNC and which have activated the MBMS service and/or a list of URAs in which there is at least one URA\_PCH UE which has activated the MBMS service. The list includes at least the U-RNTI of the UEs in the state other than URA\_PCH and/or URA-IDs.
+
+NOTE: The MBMS Service Context in the CRNC contains no information about RRC Idle mode UEs.
+
+- 3 The MBMS Service Context is created in the CRNC either
+ - if the SGSN informs the RNC that a UE has activated the MBMS Service in a cell controlled by the CRNC by the UE Linking procedure. In this case, the CRNC is the SRNC of the UE,
+ - or if the RNC is notified of an MBMS Session Start,
+ - or if the RNC serves as a Drift RNC for a PMM-CONNECTED UE and receives for this UE a UE Link from the SRNC containing the MBMS Service Id of the concerned MBMS Service,
+ - or if the RNC receives a URA Link containing the MBMS Service Id of the concerned MBMS Service.
+- 4 Each RNC which is informed by the SGSN that a UE has activated one (or several) MBMS Service(s) by the UE Linking procedure maintains an MBMS Service Context for each indicated MBMS service, irrespectively of the MBMS Service Area.
+- 5 The MBMS Service Context is released by the CRNC either
+ - if the MBMS Service Context does not contain any UE/URA information after a UE/URA Unlinking procedure from a SGSN and there is no active MBMS Session for the concerned MBMS Service,
+ - or if the MBMS Service Context does not contain any UE Link/URA Link at the time of a Session Stop
+ - or if the RNC receives a CN De-Registration for MBMS Service
+- 6 Associated functionalities:
+ - 6.1 Bearer type selection for MBMS transmissions based on information in the CRNC MBMS Service Context. The decision process requires inter-working with Radio Resource Management and with the UE's SRNC in the case of p-t-p bearers.
+ - 6.2 MBMS RB control for p-t-m bearers in each cell, based on information in the CRNC MBMS Service Context.
+ - 6.3 Update of the MBMS Service Context when a PMM-CONNECTED UE, which has activated an MBMS Service, has entered a cell. Update of the MBMS Service Context via Iur is performed by UE Linking.
+
+- 6.4 Update of the MBMS Service Context when a PMM-CONNECTED UE, which has activated an MBMS Service, has left a cell. Update of the MBMS Service Context via Iur is performed by UE Un-Linking.
+
+NOTE: For further details of UE linking via the Iur interface see chapter 5.1.6.
+
+### 5.1.2 MBMS Session start and MBMS Session Stop
+
+At MBMS Session Start and MBMS Session Stop the RNC receives a respective request from the CN. The MBMS Session Start Request shall contain the MBMS Service Id, MBMS Bearer Service Type and MBMS Session Attributes (MBMS Service Area Information, QoS parameters, ...). The MBMS Session Start Request triggers the RNC to notify UEs, which have activated the MBMS Service of the MBMS Session Start. The MBMS Session Stop Request may trigger the RNC to notify UEs, which have activated the MBMS Service of the MBMS Session Stop.
+
+The MBMS Session Start and Session Stop procedures provide the setup and release of the MBMS RAB in the following way:
+
+The MBMS Session Start Request shall contain all information necessary to setup an MBMS RAB. When the RNC receives an MBMS Session Start Request, it typically executes MBMS Iu data bearer set up and shall inform the sending CN node, of the outcome in the MBMS Session Start response message.
+
+Upon reception of MBMS Session Start Request, if the MBMS Service Context is not yet present in the RNC, the RNC shall store the MBMS Service Id. Further the RNC shall memorise the MBMS Bearer Service Type, MBMS Counting Information, MBMS Counting Information and MBMS Session Attributes (MBMS Service Area Information, QoS parameters, ...) as part of the MBMS Service Context.
+
+The RNC may choose not to execute the MBMS Iu data bearer setup, for a particular MBMS service, when:
+
+1. The RNC does not control any cell contained within the MBMS Service Area, or
+2. The RNC controls at least one cell contained within the MBMS Service Area and a list of PMM-Idle Mode UEs is included in MBMS Session Start but no RA's contained within the list are under the control of the RNC
+
+The RNC may not execute the MBMS Iu data bearer setup for a given Iu interface in case of Iu-flex. In those cases the CN node shall be informed accordingly.
+
+In case of Iu-flex, the RNC might receive more than one MBMS Session Start Request for an MBMS Service and shall not set up more than one MBMS Iu bearer for a certain MBMS Service towards a pool area.
+
+When the RNC receives an MBMS Session Stop Request it shall release the associated MBMS RAB resources.
+
+The MBMS Session Start and Session Stop procedures serve to establish and release the MBMS Iu signalling connection.
+
+### 5.1.3 MBMS Iu bearer
+
+For each MBMS service, data is transferred via an MBMS RAB between the SGSN and the UE. For each MBMS service, data is transferred via one MBMS Iu bearer between SGSN and the RNC in the whole MBMS Service area. Signalling messages specific for an MBMS Service are transferred via one dedicated MBMS Iu signalling connection between the RNC and the SGSN.
+
+- 1 One MBMS Iu bearer is established per MBMS service at MBMS Session Start.
+- 2 Regarding Iu-flex the RNC shall not set up more than one MBMS Iu bearer.
+- 3 Because of the dedicated channels and Iur mobility, there is a need to send MBMS data to an RNC which is not necessarily part of the MBMS Service area.
+- 4 The MBMS Iu bearer on Iu is established per MBMS service and not per UE individually.
+- 5 Each PMM-CONNECTED mode UE with an activated MBMS service has its UE context bind to the MBMS Iu bearer.
+- 6 There could be several MBMS RBs linked to one MBMS Iu bearer (i.e. one MBMS Iu bearer on Iu maybe mapped to multiple DTCH and/or or p-t-m traffic channels over the radio -interface).
+
+### 5.1.4 MBMS Iub bearer
+
+The existing FACH transport channel mechanism over Iub is to be used in case of p-t-m MBMS transmission.
+
+### 5.1.5 Mapping of MBMS Iu bearer to p-t-p and p-t-m connections
+
+The service specific MBMS RAB on Iu may be mapped to p-t-m bearers in order to provide MBMS data via common channels.
+
+- 1 The MBMS control function in the CRNC may decide to establish a p-t-m connection, if the number of counted MBMS users in a cell exceeds a certain operator-defined threshold or if the MBMS Counting Information indicates that MBMS Counting procedures are not applicable.
+- 2 The MBMS control function in the CRNC may decide to establish a p-t-m connection depending on the congestion scenario expected for a specific cell (e.g. in hotspot areas where no bearer type switching is needed). and/or the MBMS service characteristics (e.g. session duration time) on a per cell basis.
+- 3 The MBMS control function in the CRNC may, through a configurable parameter enable/disable bearer type switching and the associated procedures on a per cell basis.
+- 4 The MBMS control function in the CRNC establishes an MBMS RB by sending service specific signalling messages (e.g. MBMS RB Setup message) to all the UEs in the cell listening MBMS point-to-multipoint control channel (MCCH). UEs with activated service(s) may then execute the RB set-up.
+- 5 MBMS data is transferred on an MBMS point-to-multipoint traffic channel (MTCH) to all the UEs which have executed the RB setup.
+- 6 The MBMS control function in the CRNC releases the MBMS RB (e.g. MBMS RB Release) when the data transfer has been finished or it has been interrupted by the CRNC.
+- 7 p-t-p transmission of MBMS data should use the DTCH as defined for other dedicated services.
+- 8 p-t-m transmission of MBMS data applies to all RRC states and modes.
+
+### 5.1.6 UE Linking/De-linking
+
+UE Linking denotes the process where a UE, which has joined one or several MBMS services, is linked to one or several MBMS service context in the RNC.
+
+MBMS UE linking procedure in the SRNC is performed in following cases.
+
+1. When the UE, which has joined an MBMS service, is moved to PMM-CONNECTED and sets up a PS RAB This may happen at any point in time during the whole MBMS service availability (i.e. before, during and between MBMS sessions).
+2. When the UE joins an MBMS service and is in PMM-CONNECTED due to an existing PS RAB. This may happen at any point in time during the whole MBMS service availability (i.e. before, during and between MBMS sessions).
+3. When the UE is moved to PMM-CONNECTED only for MBMS purpose, e.g. to respond to counting/recounting indication or respond to p-t-p bearer indication from RNC. This may happen at any point in time during MBMS sessions.
+4. When the UE is moved to PMM-CONNECTED and the UE provides MBMS Selected Services Information to the RNC.
+
+Keeping UEs in PMM-CONNECTED only for MBMS between sessions is implementation specific. The UE linking in the SRNC for services delivered over MBMS Multicast mode is performed via UE dedicated Iu procedures. An entry for the UE is added to the related MBMS service context(s) in the SRNC. If an MBMS service context doesn't exist yet it needs to be created.
+
+In cases where a UE is present in a cell under the control of a drift RNC, the UE Linking is performed via Iur in the following way.
+
+1. When the UE, which has activated one or several MBMS services, is in CELL\_DCH state and starts to consume radio resources from one or several cells controlled by the DRNC, MBMS UE Linking in the DRNC is performed via UE dedicated Iur procedures. After that the DRNC shall update the MBMS Service context on the request of every radio link setup/release from the SRNC.
+2. When the UE, which has activated one or several MBMS services, is in CELL\_FACH state and starts to consume radio resources from one cell controlled by the DRNC, MBMS UE Linking in the DRNC is
+
+performed via UE dedicated Iur procedures. After that the DRNC shall update the MBMS Service context in the DRNC at every intra-DRNC cell change without the need to receive UE Link from the SRNC.
+
+3. If the UE is in CELL\_DCH and CELL\_FACH state and there is no dedicated RNL signalling activity ongoing for this UE and UE Linking is performed in the SRNC for an MBMS Service, MBMS UE Linking in the DRNC is performed via the MBMS Attach procedure.
+4. If the UE is in CELL\_PCH and moves to a cell within the DRNC area for the first time, the MBMS UE Linking in the DRNC is performed. The cell the UE moved to is indicated to the DRNC. After that at every intra-DRNC cell change the DRNC shall update the MBMS Service context in the DRNC without the need to receive UE Link from the SRNC.
+5. If the UE is in CELL\_PCH and there is no mobility related signalling activity ongoing for this UE and UE Linking is performed in the SRNC for an MBMS Service, MBMS UE Linking in the DRNC is performed via the MBMS Attach procedure.
+6. If the UE is in RRC connected mode and UE Linking is performed in the SRNC for an MBMS Service and a session of this MBMS Service is ongoing UE Linking in the DRNC needs to be performed immediately.
+
+At MBMS UE linking in the DRNC the MBMS service context in the DRNC needs to be updated. If an MBMS service context does not exist yet then it shall be created and if needed, DRNC can acquire the APN and IP Multicast Address from the SRNC for the specific service via Information Exchange procedure.
+
+UE De-linking denotes the process where a UE, which has joined MBMS service(s), is removed from one or several MBMS service contexts in the RNC.
+
+MBMS UE De-linking procedure in the SRNC is performed in following cases.
+
+1. When the UE has left the MBMS service and is in PMM-CONNECTED due to an existing PS RAB. This may happen at any point in time during the whole MBMS service availability (i.e. before, during and between MBMS sessions).
+2. When the UE sends new MBMS Selected Services Information to the RNC omitting an MBMS service which is identified on the MCCH.
+3. When CN decides to de-link a certain PMM-CONNECTED mode UE due to e.g. error cases.
+
+MBMS UE De-linking in the SRNC for services in MBMS Multicast mode is performed via UE dedicated Iu procedure. The entry for the UE is removed from the concerned MBMS service context(s) in the SRNC.
+
+MBMS UE De-linking procedure in the DRNC is performed via Iur in the following way:
+
+1. If the UE is in CELL\_DCH or CELL\_FACH state and stops consuming the radio resources from one or several cells controlled by the DRNC, MBMS UE is De-linked from the MBMS Service Context in the DRNC via UE dedicated Iur procedure.
+2. If the UE is in CELL\_DCH or CELL\_FACH state and there is no dedicated RNL signalling activity ongoing for this UE and UE De-linking is performed in the SRNC for an MBMS Service, MBMS UE De-linking in the DRNC is performed via the MBMS Detach procedure.
+3. If the UE is in CELL\_PCH and leaves for a cell out of the DRNC area the UE is delinked from the MBMS Service context in the DRNC via the MBMS Detach procedure. The cell the UE moved out of is indicated to the DRNC.
+4. If the UE is in RRC connected mode and UE De-linking is performed in the SRNC for an MBMS Service and a session of this MBMS Service is ongoing UE De-linking in the DRNC needs to be performed immediately.
+
+### 5.1.7 RNC Registration
+
+RNC Registration for a certain MBMS Service denotes the process where the CN becomes aware of an RNC hosting UEs, which have activated that MBMS Service.
+
+Due to UE mobility, a RNC with no MBMS Service Context, can be informed that a PMM-CONNECTED UE, which has entered the cell, has activated an MBMS Service by means of the MBMS UE Linking procedure via the Iur
+
+interface. Then the RNC informs the CN that it would like to receive MBMS Session Start Request messages when applicable for the concerned MBMS Service by sending MBMS Registration Request message.
+
+It results in the set-up of a corresponding MBMS distribution tree, but it does not result in the establishment of Iu user plane, which will be established by the MBMS Session Start procedure.
+
+1. Implicit Registration
+ - RNC Registration for Serving RNCs is performed implicitly, i.e. due to UE linking and MBMS Multicast Service Activation. No explicit registration procedure needs to be performed.
+2. Explicit Registration
+ - RNC Registration for Drift RNCs is performed explicitly if an RNC becomes a Drift RNC for a UE, which has activated an MBMS service and has no MBMS Service Context for that MBMS Service.
+ - RNC Registration for Drift RNCs is performed explicitly if an RNC is no longer the SRNC of any connected UE which has activated an MBMS service, but hosts at least a UE which consumes radio resources of the RNC via Iur. This shall happen only before sessions or between sessions.
+ - The DRNC will perform a registration towards its default CN node only.
+
+### 5.1.8 RNC De-Registration
+
+RNC De-Registration for a certain MBMS Service denotes the process where the CN becomes aware that an RNC registered at a CN node does not host any more PMM-CONNECTED UEs which have activated that MBMS Service.
+
+- Implicit RNC De-Registration
+ - RNC De-Registration for Serving RNCs is performed implicitly, i.e. due to UE Unlinking and MBMS Multicast Service Deactivation. No explicit de-registration procedure needs to be performed.
+- Explicit RNC De-Registration
+ - RNC De-Registration for Drift RNCs is performed explicitly if a RNC is not acting as a Serving RNC and has ceased to act as a Drift RNC for UEs which have activated an MBMS service, it will perform a de-registration towards the CN node it was registered to.
+ - The timing of RNC De-Registration is implementation specific.
+
+NOTE: When the Drift RNC performs the explicit De-registration, the Implicit registration may still remain and in that case Iu data bearer should not be removed.
+
+### 5.1.9 CN De-Registration
+
+CN De-Registration denotes the process where the CN informs the RNC that a certain MBMS service is no longer available. CN De-Registration should result in releasing of all associated MBMS Service Contexts and resources.
+
+The CN De-Registration procedure serves to release the MBMS Iu signalling connection.
+
+### 5.1.10 URA Linking/De-linking
+
+URA Linking denotes the process where a URA, which contains one or more cells in which at least one URA\_PCH UE has joined the MBMS service or has passed MBMS Selected Service Information about the MBMS service, is linked to an MBMS service context in the RNC. An entry for the URA is added to the MBMS service context in the RNC.
+
+If the UE in URA\_PCH state, which has activated one or several MBMS Services, is present within a URA containing one or more cells that are controlled by one or more drift RNCs, the URA Linking is performed in the following way.
+
+1. If the UE is in URA\_PCH, having activated one or more MBMS services, is the first UE for the particular MBMS service to move to a URA which contains one or more cells that are controlled by one or more DRNCs, the URA is linked to the MBMS Service context in each applicable DRNC. The URA the UE moved to will be indicated.
+2. As long as the SRNC serves UEs in URA\_PCH in URAs containing cells controlled by one or more DRNCs, the SRNC shall keep the other RNCs informed about every URA in which UEs having activated certain MBMS services have to be notified. This is done when the first UE enters the URA, by indicating to the other RNCs a list of URAs and the corresponding MBMS Services via MBMS Attach procedure.
+
+NOTE: Bullet points 1 and 2 above may be merged in a future version of this document.
+
+At MBMS URA linking in the RNC the MBMS service context in the RNC needs to be updated. If an MBMS service context does not exist yet then it shall be created and acquire the APN and IP Multicast Address from the SRNC for the specific service via Information Exchange procedure.
+
+URA De-linking denotes the process where a URA is removed from one or several MBMS service contexts in the RNC.
+
+1. If the UE is in URA\_PCH and, for the particular MBMS service, is the last UE to leave a URA which contains one or more cells controlled by one or more DRNCs the URA is de-linked from the MBMS Service context in each applicable DRNC via the MBMS Detach procedure.
+
+### 5.1.11 IP Multicast Distribution
+
+To improve the transport efficiency the IP Multicast may be used for the MBMS payload distribution in the backbone network between the GGSN and the RNCs, bypassing the SGSN.
+
+The GGSN allocates during the session start the Transport Layer Address used for the IP-multicast and the DL TEID used for the Iu Transport association. The RNCs will receive these parameters from SGSN in the Session Start message as part of the MBMS session attributes.
+
+The RNC may accept or reject the proposed IP Multicast distribution in the MBMS Session Start Response to the SGSN. If accepted the RNC shall report the channel (IP Multicast and Source address) to the backbone in order to join the bearer service multicast distribution. If one or more downstream RNC nodes doesn't accept IP Multicast distribution, the SGSN will establish an MBMS RAB which the IP multicast distribution is not applied, to related RNCs.
+
+The MBMS payload is forwarded by the GGSN towards the IP Multicast address. The RNCs joined to that IP Multicast address will receive the user data packets (SYNC PDU) together with the synchronisation-related information in header part of SYNC PDU. The information in header part of SYNC PDU is delivered to allow the softcombining and MBSFN transmission across the RNCs. The details of inter-RNC synchronization are described in section 7.1B.
+
+In case the header compression is used in MBMS PtM mode for an MBMS stream the compression is done in BM-SC. The usage of header compression is configured in advance in the BM-SC and the RNC is receiving the information during the MBMS Session start as part of the session attributes. In case header compression is configured, the MBMS user data packets forwarded from BM-SC to RNCs via GGSN will contain in addition to the synchronisation-related information and PDCP protocol information, the full IP header of the payload and the payload with compressed header. The RNC using MBMS PtP mode in a cell may process the UE dedicated RoHC for the full IP header of the payload and replace the compressed header of PtM mode with it.
+
+## 5.2 MBMS Uu Principles
+
+### 5.2.1 MBMS Service States in UE
+
+The MBMS bearer service has following service states in the UE:
+
+1. Not active, UE has not joined any MBMS multicast service or not activated the broadcast mode of the MBMS
+2. Not active, UE has joined at least one MBMS multicast service and/or activated the broadcast mode of the MBMS, but MBMS SYSTEM INFORMATION is not broadcasted on BCCH.
+3. Active, UE has joined at least one MBMS multicast service and/or activated the broadcast mode of the MBMS, but any of the services that UE has joined (interested in broadcast mode) is not being transmitted. UE monitors MICH to find modifications in the MCCH as defined in 5.1.6
+4. Active; at least one MBMS service appearing in the list of MBMS Activated Services, is received on p-t-m
+ - UE is receiving MBMS transmission on MTCH
+ - UE is using DRX based on scheduling information informing that coming MTCH transmission is not in the interest of the UE.
+5. Active; at least one MBMS service is received on p-t-p
+
+6. Active; at least one MBMS service is received on p-t-p and at least one MBMS service is received on p-t-m. (only valid if UE has capability to support this combination)
+
+When MBMS transmission is started in cell the UE moves from state 3 to either state 4 or state 5 (6), depending on p-t-p transmission mode and after MBMS transmission ends in the cell, the UE moves from state 4 or state 5 (6) to state 3.
+
+### 5.2.2 One PDCP and RLC entity shared among multiple cells within one RNS
+
+For each MBMS service, a group of multiple cells belonging to one RNS shares one PDCP entity and RLC entity over p-t-m transmission. The group of multiple cells is called 'MBMS Cell Group'.
+
+1. There are one or more MBMS Cell Groups per RNS. The MBMS Cell Groups are managed by the CRNC.
+2. There are one or more cells pertaining to the same RNS for one MBMS Cell Group.
+3. The MBMS Cell Group identity is used to uniquely identify a group of multiple cells, which for each MBMS service share the same PDCP entity and RLC entity within an RNS.
+
+In case the MBMS combining methods are used across multiple RNSs for an MBMS service, the RNSs belong to the same IP Multicast group used for the MBMS user data distribution from the GGSN to CRNCs. One common PDCP entity for header compression is used for MBMS P-t-M transmission among the RNSs being part of the IP Multicast group.
+
+The RLC entity for p-t-m transmission is shared by a group of multiple cells belonging to one RNS. The RLC entities, within the RNSs shall be synchronized to each other in way that they, process the user data in the same manner with the help of information delivered by the SYNC-protocol to RNS.
+
+### 5.2.3 MCCH Information Scheduling
+
+The MCCH information will be transmitted based on a fixed schedule. This schedule will identify the TTI containing the beginning of the MCCH information. The transmission of this information may take a variable number of TTIs and the UTRAN should transmit MCCH information in consecutive TTIs. The UE will keep receiving the S-CCPCH until:
+
+- It receives all of the MCCH information, or
+- It receives a TTI that does not include any MCCH data, or
+- The information contents indicate that further reception is not required (e.g. no modification to the desired service information).
+
+Based on this behaviour, the UTRAN may repeat the MCCH information following a scheduled transmission in order to improve reliability. The MCCH schedule will be common for all services.
+
+The entire MCCH information will be transmitted periodically based on a "repetition period". The "modification period" will be defined as an integer multiple of the repetition period. The MBMS ACCESS INFORMATION may be transmitted periodically based on an "access info period". This period will be an integer divider of the "repetition period".
+
+MCCH information is split into critical and non-critical information. The critical information is made up of the MBMS NEIGHBOURING CELL INFORMATION, MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION. The non-critical information corresponds to the MBMS ACCESS INFORMATION. Changes to critical information will only be applied at the first MCCH transmission of a modification period and in the beginning of each modification period UTRAN transmits the MBMS CHANGE INFORMATION including MBMS services ids whose MCCH information is modified at that modification period. MBMS CHANGE INFORMATION is repeated at least once in each repetition period of that modification period. Changes to non-critical information could take place at any time.
+
+The Figure 5.2.3 below illustrates the schedule with which the MBMS SERVICE INFORMATION and RADIO BEARER INFORMATION would be transmitted. Different colours indicate potentially different MCCH content.
+
+
+
+Figure 5.2.3: MCCH Information Schedule. This diagram shows the timing of MCCH information changes. A horizontal timeline represents time, with vertical dashed lines marking the start of 'Modification periods'. Two modification periods are shown. The 'Repetition period' is the interval between consecutive MCCH transmissions, represented by a double-headed arrow. MCCH transmissions are shown as colored blocks: purple, yellow, green, and red. An arrow labeled 'Change information' points to the first yellow block at the start of the first modification period. Subsequent blocks of the same color (yellow, green, red) represent repetitions of the information for that service group.
+
+Figure 5.2.3: MCCH Information Schedule
+
+### 5.2.4 MBMS Notification
+
+The MBMS notification mechanism is used to inform UEs of an upcoming change in critical MCCH information. Notifications are based on service groups. The mapping between service IDs and service groups is specified in [11].
+
+The MBMS notification indicators will be sent on an MBMS specific PICH, called the MICH. A single MICH frame will be able to carry indications for every service-group.
+
+Critical MCCH information can only be changed at the beginning of a modification period as described in Section 5.2.3. The MBMS notification indicator corresponding to the service group of every affected service shall be set continuously during the entire modification period preceding the first change in MCCH information related to a given service. Subsequent changes in the MCCH information in the next modification period related to the same service can be signalled on the MCCH.
+
+UEs which are not receiving any MBMS service on MTCH or p-t-p channel are free to read the MBMS notification at any time; however the modification interval shall be long enough so that UEs are able to reliably detect it even if they only receive the MICH during their regular Release '99 paging occasions.
+
+Upon detecting the MBMS notification indication for a service group, UEs with an activated service corresponding to this group shall start reading the MCCH at the beginning of the next modification period. The UE shall read at least MBMS CHANGE INFORMATION.
+
+The Figure 5.2.4 below illustrates the timing relation between the setting of the MICH and the first MCCH critical information change. The green colour for the MICH indicates when the NI is set for the service. For the MCCH, different colours indicate MCCH content related to the notification of different services.
+
+UEs, which are receiving MBMS service(s) on MTCH in idle mode or URA\_PCH, CELL\_PCH, or CELL\_FACH state shall read the MCCH at the beginning of the each modification period to receive the MBMS CHANGE INFORMATION, which will indicate MBMS service IDs and optionally MBMS Session ID whose MCCH information is modified at that modification period. If MBMS service Id and optionally MBMS Session ID, which UE has activated, is indicated in MBMS CHANGE INFORMATION the UE shall read the rest of the MCCH information.
+
+
+
+Figure 5.2.4: Illustration of MICH timing relative to Modification period. This diagram shows the relationship between MICH and MCCH timing. The top timeline represents the MICH, with a long red bar indicating the notification indicator. A green segment within the red bar corresponds to the first modification period, indicating when the notification is active. The bottom timeline represents the MCCH, with colored blocks (yellow, blue, red) representing different service groups. Vertical dashed lines mark the start of modification periods. An arrow labeled 'Change Information' points to the first yellow block at the start of the first modification period. The green segment on the MICH timeline aligns with the start of the modification period on the MCCH timeline.
+
+Figure 5.2.4: Illustration of MICH timing relative to Modification period
+
+### 5.2.5 MBMS Counting
+
+MBMS Counting is used to determine the optimum transmission mechanism for a given service.
+
+1. The need for counting is indicated in the notification, and achieved by requesting UEs, belonging to the same MBMS service group, to respond to counting by sending MBMS COUNTING RESPONSE signalling flow to CRNC.
+ - a. For UEs in idle mode the counting response refers to the RRC connection establishment procedure.
+ - b. For UEs in URA\_PCH, or CELL\_PCH state the counting response refers to cell update procedure
+ - c. For UEs in CELL\_FACH state the counting response refers to signalling on CCCH or DCCH.
+2. The exact number of UEs that need to respond to counting is an RRM issue.
+3. Since it is desirable in a specific cell, to avoid bringing a large number of UEs for counting purposes to RRC connected mode at the same time (RACH load, etc), RRM may control the load due to the RRC connection establishment requests, by setting an access "probability factor". For UEs in PMM connected mode the UTRAN may set different "probability factor" than for UEs in idle mode.
+4. Following counting, the number of subscribers that need to be maintained in RRC connected mode or for which the RNC releases their connection, is also an RRM issue. In Broadcast Mode, the RNC may also decide to reject the RRC connection establishment and indicate during this reject that counting has been completed.
+5. For a given MBMS service, the counting indication in the notification may be switched on and off, on per-cell basis.
+6. The RNC may use notification to indicate counting during an ongoing MBMS session (term used is re-counting).
+7. The RNC receives via Iu from CN information (MBMS service ID) about UEs who are in RRC Connected mode, and have joined the MBMS service. This information may be used for counting purposes.
+
+The MBMS counting function includes a mechanism by which the UTRAN can prompt UEs with a given activated service to become RRC connected. This procedure is only applicable for UEs in idle mode and relies on the MBMS ACCESS INFORMATION transmitted on the MCCH. The probability factor indicates the probability with which UEs need to attempt an RRC connection procedure.
+
+In order to trigger counting for a given service, the UTRAN may use the regular MBMS notification mechanism outlined in section 5.2.4 to force UEs with that service activated to read the MCCH information.
+
+Once a UE detects that the counting procedure is on-going for the specific service it wants to receive, it will attempt to respond to the counting based on the probability factor included in the MCCH. If the response to counting is for a service identified in the list of MBMS Selected Services, the UE should provide the MBMS Service ID in the response.
+
+Also, the UE will keep receiving the MBMS ACCESS INFORMATION at every access info period until the UE successfully responds to the counting or counting is no longer required. Whenever it receives new MBMS ACCESS INFORMATION the UE will update its probability factor with the new value.
+
+The Figure 5.2.5 below illustrates this mechanism. The green colour for the MICH indicates when the NI is set for the service. The green colour for the MBMS ACCESS INFORMATION indicates that the counting procedure is on-going and that UEs need to establish an RRC connection based on the included probability factor (PF). For the critical MCCH info, different colours indicate potentially different content.
+
+
+
+The diagram illustrates the timing of MBMS counting information. The top timeline, labeled 'MICH', shows a green segment followed by a red segment. The middle timeline, labeled 'ACCESS INFO', shows a series of red blocks. The first two are labeled 'PF0', the third is 'PF1', and the fourth is 'PF2'. Below these, three labels indicate 'UE Access with PF0', 'UE Access with PF1', and 'UE Access with PF2'. The bottom timeline, labeled 'Critical Info', shows yellow blocks. The first is labeled 'Change Information', and the others are labeled 'MCCH Information'. Arrows indicate the 'Modification period' (spanning the entire duration), 'Repetition period' (spanning the first four blocks), and 'Access info period' (spanning the first three blocks).
+
+Figure 5.2.5: Illustration of Access Info period during MBMS counting. The diagram shows three horizontal timelines: MICH, ACCESS INFO, and Critical Info. The MICH timeline has a green segment followed by a red segment. The ACCESS INFO timeline has red blocks labeled PF0, PF1, and PF2. The Critical Info timeline has yellow blocks labeled Change Information and MCCH Information. Arrows indicate the Modification period, Repetition period, and Access info period. Labels 'UE Access with PF0', 'UE Access with PF1', and 'UE Access with PF2' are present.
+
+**Figure 5.2.5: Illustration of Access Info period during MBMS counting**
+
+For every UE brought to RRC connected state for the purpose of counting, UTRAN will initiate the PMM Connection establishment procedure and will obtain from CN the set of MBMS services these users have joined.
+
+Counting for on-going services (re-counting) will rely on the same scheduling of the MCCH information.
+
+### 5.2.6 MBMS Radio Bearer Release in the UE
+
+The UE releases the MBMS RB by using one of the following mechanisms:
+
+- Explicit MBMS RB Release
+- Implicit MBMS RB Release
+
+The Explicit MBMS RB Release mechanism allows UTRAN to explicitly indicate to MBMS UEs that an MBMS Radio Bearer should be released. For p-t-m transmissions the Explicit MBMS RB Release indication is contained within the MBMS SERVICE INFORMATION signalling flow. For p-t-p transmission the release of MBMS radio bearers is completed in the same way as for a non-MBMS radio bearer. If the Explicit MBMS RB Release indication is received, the UE releases the MBMS RB.
+
+The Implicit MBMS RB Release mechanism applies only to p-t-m transmission and enables a UE to release the MBMS Radio Bearer without receiving the Explicit MBMS RB Release. The UE identifies Implicit MBMS RB release if it detects that the RB is not present in the MBMS SERVICE INFORMATION signalling flow.
+
+### 5.2.7 MBMS Session Repetition
+
+In the case that the BM-SC repeats MBMS sessions (send multiple time identical content), the MBMS service Id and MBMS session Id is used to identify specific MBMS service and session. The validity of the session Id is handled on the MBMS application layer between the BM-SC and the UE. If UTRAN receives the MBMS session ID in session start, the UTRAN should:
+
+- include MBMS session Id in critical and non critical information send on MCCH
+Note: The non-critical information may contain index referring to critical information, avoiding repetition of MBMS service and session Id in non-critical information.
+
+If the UE has already received correctly the data of the MBMS session, which is being indicated on MCCH, the UE may:
+
+- ignore FLC by not applying the Layer Convergence Information
+- ignore counting procedure in Idle, URA\_PCH, CELL\_PCH, and CELL\_FACH state
+- ignore p-t-m MBMS RB setup signalled on MCCH
+- ignore p-t-p MBMS RB indication signalled on MCCH
+- reject the p-t-p RB setup for MBMS service, signalled on DCCH
+
+In the case that UTRAN receives reject from the UE to the p-t-p RB setup for MBMS service on DCCH, the UTRAN should not try to re-establish p-t-p RB setup for that MBMS service and session.
+
+In the case that the UE has accepted the p-t-p RB for repeated MBMS session the UE shall receive the complete session.
+
+### 5.2.8 MBMS Service Prioritisation
+
+The CN may assign the Allocation and Retention Priority for the MBMS bearer service. The Allocation and Retention Priority allows for prioritisation between MBMS bearer services and between MBMS bearer services and non MBMS bearer services in the UTRAN.
+
+The UE may assign internally different priorities for different MBMS services to prioritise MBMS and non MBMS service reception. In case that UE has no capability to receive simultaneously, the dedicated non MBMS service and the MBMS service and the MBMS service has priority over the non MBMS service the UE may:
+
+- initialise signalling with CN on NAS layer to stop reception of dedicated non MBMS service
+
+If the UE has no capacity on receiving all MBMS services, which it has activated and which are transmitted simultaneously on p-t-m RBs, the UE may
+
+- stop autonomously ongoing reception of lower priority MBMS service
+- act on MCCH message assigned to the highest priority MBMS service
+- start autonomously the reception p-t-m RB of the highest priority MBMS service
+
+If the reception p-t-p RB of the lower priority MBMS service is blocking the reception of p-t-m RB of the higher priority MBMS service the UE may:
+
+If p-t-p RB is being established
+
+- reject the setup of p-t-p MBMS RB
+
+If the UTRAN receives reject message UTRAN should not try to re-establish p-t-p RB setup for that MBMS service and session.
+
+If p-t-p RB is already existing
+
+- request the release of p-t-p MBMS RB from the UTRAN or only indicate frequency of higher priority MBMS service
+
+If the UTRAN receives release request message UTRAN may release the p-t-p MBMS RB.
+
+## 5.3 Protocol structure
+
+### 5.3.1 MBMS User Plane Protocol Stack Architecture
+
+
+
+Figure 5.3.1-1: Protocol Stack for MTCH. This diagram shows the protocol stack for MTCH in MBMS. It consists of three main entities: UE, Node B, and Controlling RNC. The UE and Controlling RNC have identical stacks: PDCP, RLC, MAC, and PHY. The Node B has a PHY layer. Arrows indicate data flow from the Controlling RNC down through its stack, then to the Node B's PHY layer, and finally up through the UE's stack. The PDCP, RLC, and MAC layers in the UE and Controlling RNC are shown with dashed outlines.
+
+**Figure 5.3.1-1: Protocol Stack for MTCH**
+
+Figure 5.3.1-1 illustrates the protocol termination for MTCH in MBMS, which is used in p-t-m transmission.
+
+If configured by CRNC the PDCP sub-layer performs header compression/decompression for the MBMS traffic.
+
+The PDCP sub-layer may operate with the RFC 3095 header compression protocol. In that case, header compression should be performed under RFC 3095 U-mode.
+
+In the UTRAN, for p-t-m transmission, there is one PDCP entity for each MBMS service for each MBMS Cell Group that provides the service (an MBMS Cell Group may contain one or more than one cell).
+
+In the UTRAN, for p-t-m transmission, there is one RLC entity for each MBMS service in each cell or cell group in case of utilization of selective combining or maximum ratio combining in TDD, and one MAC entity for each cell.
+
+In the UE side, there is one PDCP and RLC entity for each MBMS service in each UE. In each UE there is one MAC entity per received cell when UE is performing the selective combining between these cells.
+
+In case of p-t-p transmission, DTCH is used for MBMS transmission and the protocol termination for DTCH mapped on DCH and RACH/FACH are presented in [8].
+
+
+
+Figure 5.3.1-2: Protocol Stack for MTCH (P-T-M) in case of IP multicast distribution. This diagram shows the protocol stack for MTCH in MBMS for IP multicast distribution. It consists of four main entities: UE, Node B, Controlling RNC, and BM-SC. The UE has a stack of PDCP, RLC, MAC, and PHY. The Node B has a PHY layer. The Controlling RNC has a stack of RLC, MAC, and a TNL layer. Above the Controlling RNC's RLC/MAC stack is a SYNC layer. The BM-SC has a stack of PDCP, SYNC, and TNL. Arrows indicate data flow from the BM-SC down through its stack, then to the Controlling RNC's TNL layer, then to the Controlling RNC's RLC/MAC stack, then to the Node B's PHY layer, and finally up through the UE's stack. The PDCP, RLC, and MAC layers in the UE are shown with dashed outlines. The PDCP, SYNC, and TNL layers in the BM-SC are also shown with dashed outlines.
+
+**Figure 5.3.1-2: Protocol Stack for MTCH (P-T-M) in case of IP multicast distribution**
+
+Figure 5.3.1-2 illustrates the protocol termination for MTCH in MBMS, which is used in p-t-m transmission in case of IP Multicast distribution.
+
+Based on the configuration in BM-SC the PDCP sub-layer may perform header compression/decompression for the MBMS traffic.
+
+The PDCP sub-layer may operate with the RFC 3095 header compression protocol. In that case, header compression should be performed under RFC 3095 U-mode.
+
+In the UTRAN, for p-t-m transmission, there is one PDCP entity for each MBMS service for each MBMS IP Multicast Group that provides the service (an MBMS IP Multicast Group may contain one or more than one RNC, see section 5.2.2).
+
+For p-t-m transmission there is one RLC entity for each MBMS service in each cell or in a group of multiple cells belonging to one RNS. The RLC entities, in the RNSs synchronized to each other, shall process the user data similar manner with the help of information delivered by the SYNC-protocol to RNS. There is one MAC entity for each cell.
+
+In the UE side, there is one PDCP and RLC entity for each MBMS service in each UE. In each UE there is one MAC entity per received cell when UE is performing the selective combining between these cells.
+
+In case of p-t-p transmission, DTCH is used for MBMS transmission and the protocol termination for DTCH mapped on DCH and RACH/FACH are presented in [8].
+
+### 5.3.2 MBMS Control Plane Protocol Stack Architecture
+
+
+
+Figure 5.3.2-1: Protocol Stack for MCCH and MSCH. This diagram shows the protocol stack for MCCH and MSCH across three entities: UE, Node B, and Controlling RNC. The UE stack consists of RRC, RLC, MAC, and PHY layers. The Controlling RNC stack also consists of RRC, RLC, MAC, and PHY layers. The Node B stack consists only of a PHY layer. Arrows indicate the flow of data: from the Controlling RNC's RRC, RLC, and MAC layers down to its PHY layer, then horizontally to the Node B's PHY layer, and finally vertically up through the UE's PHY, MAC, RLC, and RRC layers.
+
+**Figure 5.3.2-1: Protocol Stack for MCCH and MSCH**
+
+Figure 5.3.2-1 illustrates the protocol termination for MCCH and MSCH in MBMS, which are MBMS p-t-m control channels.
+
+MBMS functionalities are included in MAC and RRC.
+
+In case of p-t-p transmission, DCCH is used for MBMS and the protocol termination for DCCH mapped on DCH and FACH are presented in [8].
+
+
+
+Figure 5.3.2-2: Protocol Stack for MCCH. This diagram shows the protocol stack for MCCH across four entities: UE, Node B, Controlling RNC, and MBMS Master RNC. The UE stack consists of RRC, RLC, MAC, and PHY layers. The Controlling RNC stack consists of RRC, RLC, and MAC layers. The RRC layer in the Controlling RNC is split into two sub-layers: MCCH IC and RNSAP. The MBMS Master RNC stack consists of MCCH IC and RNSAP layers. The Node B stack consists only of a PHY layer. Arrows indicate the flow of data: from the MBMS Master RNC's MCCH IC and RNSAP layers down to the Controlling RNC's RRC sub-layers, then horizontally to the Controlling RNC's RLC and MAC layers, then down to its PHY layer, then horizontally to the Node B's PHY layer, and finally vertically up through the UE's PHY, MAC, RLC, and RRC layers.
+
+**Figure 5.3.2-2: Protocol Stack for MCCH**
+
+In case MRNC is used, figure 5.3.2-2 illustrates the protocol termination for MCCH in MBMS, which is MBMS p-t-m control channel.
+
+MBSFN MCCH Information Control function is split between MRNC and CRNC. The MRNC controls the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). The MRNC informs the CRNC of the MCCH configuration (using transfer of MCCH Information Control messages) and schedule information to be used (included in RNSAP). The CRNC performs the MCCH configuration and sends the MCCH information accordingly.
+
+## 5.4 MAC architecture
+
+### 5.4.1 UTRAN MAC Architecture to support MBMS
+
+
+
+The diagram illustrates the UTRAN MAC architecture for MBMS support. It is divided into three main vertical sections by dashed lines.
+
+- Left Section (MAC-hs):**
+ - Top: MAC Control signal.
+ - Middle: MAC-hs entity block.
+ - Bottom: HS-DSCH transport channels (Associated Downlink Signalling and Associated Uplink Signalling).
+- Middle Section (MAC-c/sh/m):**
+ - Top: Logical channels MSCH, MCCH, PCCH, BCCH, MTCH, MTCH, CCCH, CTCH, SHCCH (TDD only). Below this are two configuration paths: "Configuration without MAC-c/sh" and "Configuration with MAC-c/sh".
+ - Middle: MAC-c/sh/m entity block.
+ - Bottom: Transport channels PCH, FACH, FACH, RACH, CPCH (FDD only), USCH (TDD only), USCH (TDD only), DSCH, DSCH. This section connects to the Iub interface.
+- Right Section (MAC-d):**
+ - Top: MAC Control signal, MAC Control, DCCH, DTCH, DTCH.
+ - Middle: Multiple stacked MAC-d entity blocks.
+ - Bottom: DCH, DCH transport channels. This section connects to Iur or local interfaces.
+
+Figure 5.4.1: UTRAN MAC architecture diagram showing the flow of data and control signals through various MAC entities (MAC-hs, MAC-c/sh/m, MAC-d) and logical/transport channels (MSCH, MCCH, MTCH, FACH, RACH, etc.).
+
+Figure 5.4.1: UTRAN MAC architecture
+
+To support MBMS user and control plane transmission, a multicast functionality is added in the MAC c/sh, entitled "MAC m", to take care of scheduling of MBMS related transport channels as presented in Figure 5.4.1. In addition, three logical channels are considered for p-t-m transmission of MBMS: MCCH, MSCH and MTCH. These logical channels are mapped on FACH. In case of p-t-p transmission DTCH and DCCH are used.
+
+### 5.4.2 MAC-c/sh/m architecture: UTRAN side
+
+Figure 5.4.2 illustrates the MAC-m additions to the MAC-c/sh architecture in the UTRAN side, needed to transmit MBMS data over a common transport channel (FACH).
+
+MAC-c/sh/m is located in the controlling RNC. The following functionalities are covered:
+
+- Scheduling / Buffering / Priority Handling: This function manages common transport resources between MBMS and non-MBMS data flow(s) according to their priority and delay requirements set by higher layers.
+- TCTF MUX: This function handles insertion of the TCTF field in the MAC header and also the respective mapping between logical channels (i.e. MTCH and MCCH) and transport channels. The TCTF field indicates which type of logical channel (i.e. MTCH and MCCH) is used.
+- Addition of MBMS-ID: For p-t-m type of logical channels, the MBMS-ID field in the MAC header is used to distinguish between MBMS services.
+- TFC selection: Transport format combination selection is done for a common transport channel (FACH) mapped to MTCH, MSCH and MCCH. In the case of MBMS soft combining (excluding TrCH combining in TDD), the combinable S-CCPCHs shall have the same TFC during the TTIs in which L1 combining is used.
+
+There is one MAC-c/sh/m entity in the UTRAN for each cell.
+
+
+
+Figure 5.4.2: UTRAN side MAC-m architecture additions to MAC-c/sh. The diagram shows a stack of MAC functions. At the top, logical channels MCCH, MSCH, MTCH, and MTCH are shown. Below them, a block labeled 'add MBMS-ID' is added. Further down are 'TCTF MUX', 'Scheduling/Buffering/ Priority Handling', and 'TFC selection'. These are connected to a large grey block labeled 'MAC-c/sh/m'. Below this block, two transport channels labeled 'FACH' are shown. A 'MAC-Control' oval on the left is connected to the top of the stack.
+
+Figure 5.4.2: UTRAN side MAC-m architecture additions to MAC-c/sh
+
+### 5.4.3 MAC-c/sh/m architecture: UE side
+
+Figure 5.4.3 illustrates the MAC-m additions to the MAC-c/sh architecture in the UE side, needed to receive MBMS data over a transport channel (FACH).
+
+The following functionalities are covered:
+
+- TCTF DEMUX: This function handles detection and deletion of the TCTF field in the MAC header, and also the respective mapping between logical channels (i.e. MTCH and MCCH) and transport channels. The TCTF field indicates which type of logical channel (i.e. MTCH and MCCH) is used.
+- Reading of MBMS-ID: The MBMS-ID identifies data to a specific MBMS service.
+
+There is one MAC-m entity in the UE or in case of selective combining one MAC-m entity for each selectively combined cell in the UE.
+
+
+
+Figure 5.4.3: UE side MAC-m additions to MAC-c/sh. The diagram shows a stack of MAC functions. At the top, logical channels MCCH, MSCH, MTCH, and MTCH are shown. Below them, a block labeled 'read MBMS-ID' is added. Further down is 'TCTF DEMUX'. These are connected to a large grey block labeled 'MAC-c/sh/m'. Below this block, two transport channels labeled 'FACH' are shown. A 'MAC-Control' oval on the left is connected to the top of the stack.
+
+Figure 5.4.3: UE side MAC-m additions to MAC-c/sh
+
+# 6 MBMS Channel Structure
+
+There exists two transmission modes to provide the MBMS service:
+
+- Point-to-point transmission (p-t-p)
+- Point-to-multipoint transmission (p-t-m)
+
+## 6.1 Point-to-Point Transmission
+
+Point-to-point transmission is used to transfer MBMS specific control/user plane information as well as dedicated control/user plane information between the network and one UE in RRC Connected Mode. It is used only for the multicast mode of MBMS and for services identified in the list of MBMS Selected Services.
+
+For a UE in CELL\_FACH and Cell\_DCH, DCCH or DTCH is used, allowing all existing mappings to transport channels.
+
+A detailed description of channels used for point-to-point transmission is given in [8].
+
+## 6.2 Point-to-multipoint Transmission
+
+Point-to-multipoint transmission is used to transfer MBMS specific control/user plane information between the network and several UEs in RRC Connected or Idle Mode. It is used for broadcast or multicast mode of MBMS.
+
+### 6.2.1 Logical Channels
+
+#### 6.2.1.1 MBMS point-to-multipoint Control Channel (MCCH)
+
+This logical channel is used for a p-t-m downlink transmission of control plane information between network and UEs in RRC Connected or Idle Mode. The control plane information on MCCH is MBMS specific and is sent to UEs in a cell with an activated (joined) MBMS service. MCCH can be sent in S-CCPCH carrying the DCCH of the UEs in CELL\_FACH state, or in standalone S-CCPCH, or in same S-CCPCH with MTCH. For 3.84 Mcps TDD MBSFN IMB, MCCH is sent in a standalone S-CCPCH frame type 1 only.
+
+The MCCH is always mapped to one specific FACH in the S-CCPCH as indicated on the BCCH. If MCCH is the only logical channel mapped in to the FACH, the absence of the TCTF field is explicitly signalled otherwise the TCTF field is used in MAC header to identify MCCH logical channel type. In case of soft combining, the MCCH is mapped to a different S-CCPCH (CCTrCH in TDD) than MTCH.
+
+Reception of paging has priority over reception of MCCH for Idle mode and URA/CELL\_PCH UEs.
+
+#### 6.2.1.2 MBMS point-to-multipoint Traffic Channel (MTCH)
+
+This logical channel is used for a p-t-m downlink transmission of user plane information between network and UEs in RRC Connected or Idle Mode. The user plane information on MTCH is MBMS Service specific and is sent to UEs in a cell with an activated MBMS service.
+
+The MTCH is always mapped to one specific FACH in the S-CCPCH, or in the S-CCPCH frame type 2 in case of 3.84 Mcps TDD MBSFN IMB, as indicated on the MCCH. The TCTF field is always used in MAC header to identify MTCH logical channel type.
+
+#### 6.2.1.3 MBMS point-to-multipoint Scheduling Channel (MSCH)
+
+This logical channel is used for a p-t-m downlink transmission of MBMS service transmission schedule between network and UEs in RRC Connected or Idle Mode. The control plane information on MSCH is MBMS service and S-CCPCH specific and is sent to UEs in a cell receiving MTCH. One MSCH is sent in each S-CCPCH carrying the MTCH.
+
+The MSCH is always mapped to one specific FACH in the S-CCPCH as indicated on the MCCH. Due to different error requirements the MSCH is mapped to a different FACH than MTCH. If MSCH is the only logical channel mapped in to the FACH, the absence of the TCTF field is explicitly signalled otherwise the TCTF field is used in MAC header to identify MSCH logical channel type.
+
+### 6.2.2 Transport Channel
+
+FACH is used as a transport channel for MTCH, MSCH and MCCH.
+
+### 6.2.3 Physical Channel
+
+SCCPCH is used as a physical channel for FACH carrying MTCH or MCCH or MSCH.
+
+### 6.2.4 Mapping between channels
+
+Only in downlink, the following connections between logical channels and transport channels exist:
+
+- MCCH can be mapped to FACH
+- MTCH can be mapped to FACH
+- MSCH can be mapped to FACH
+
+The mappings as seen from the UE and UTRAN sides are shown in Figure 6.2.4-1 and Figure 6.2.4-2 respectively.
+
+
+
+The diagram illustrates the mapping of logical channels to a transport channel from the UE's perspective. At the top, three logical channels are shown: MSCH-SAP, MCCH-SAP, and MTCH-SAP. Each is connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label.
+
+Figure 6.2.4-1: Logical channels mapped onto transport channel, seen from the UE side. The diagram shows three logical channels (MSCH-SAP, MCCH-SAP, MTCH-SAP) at the top, each connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label.
+
+Figure 6.2.4-1: Logical channels mapped onto transport channel, seen from the UE side
+
+
+
+The diagram illustrates the mapping of logical channels to a transport channel from the UTRAN's perspective. At the top, three logical channels are shown: MSCH-SAP, MCCH-SAP, and MTCH-SAP. Each is connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label.
+
+Figure 6.2.4-2: Logical channels mapped onto transport channel, seen from the UTRAN side. The diagram shows three logical channels (MSCH-SAP, MCCH-SAP, MTCH-SAP) at the top, each connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label.
+
+Figure 6.2.4-2: Logical channels mapped onto transport channel, seen from the UTRAN side
+
+### 6.2.5 Data Flows through Layer 2
+
+#### 6.2.5.1 Data flow for MCCH mapped to FACH
+
+For MCCH, the RLC mode to be employed is UM-RLC, with required enhancements to support out of sequence SDU delivery. A MAC header is used for logical channel type identification.
+
+#### 6.2.5.2 Data flow for MTCH mapped to FACH
+
+For MTCH, the RLC mode to be employed is UM-RLC, with required enhancements to support selective combining. Quick repeat may be used in RLC-UM. A MAC header is used for logical channel type identification and MBMS service identification. For MBMS in case of inter-RNC MBSFN and soft combining, MAC PDUs to be transmitted in one TTI shall be ordered according to MBMS-ID when multiple MTCHs are multiplexed onto one FACH.
+
+#### 6.2.5.3 Data flow for MSCH mapped to FACH
+
+For MSCH, the RLC mode to be employed is UM-RLC. A MAC header is used for logical channel type identification.
+
+## 6.3. MBMS Notification Indicator Channel
+
+MBMS notification utilizes a new MBMS specific PICH called the MBMS Notification Indicator Channel (MICH) in each cell. Its coding is defined in [9] (FDD) and [10] (TDD).
+
+# --- 7 MBMS Reception and UE Capability
+
+## 7.1 Selective and Soft Combining for MBMS P-T-M transmission
+
+The selective combining for MBMS p-t-m transmission is supported by RLC PDU numbering. Therefore, the selective combining in the UE is possible from cells providing similar MBMS RB bit rate, provided that the de-synchronization between MBMS p-t-m transmission streams does not exceed the RLC re-ordering capability of the UE. Thus, there exist one RLC entity in the UE side.
+
+To support selective combining it is decided to:
+
+- Introduce re-ordering as a configurable feature of RLC-UM, within the RLC specification.
+- Use the same mechanism as what is specified for MAC-hs (single T1 timer).
+
+For selective combining there exist one RLC entity per MBMS service utilizing p-t-m transmission in the cell group of the CRNC. All cells in the cell group are under the same CRNC, i.e. Iur support is not considered.
+
+For soft combining to be possible, the relative delay between the radio links to be combined, when they are received by the UE, must be no more than (1 TTI)+(1 slot).
+
+The UE capability requirements to support selective and soft combining are defined in chapter 7.2. In case de-synchronization occurs between MBMS transmissions in neighbouring cells belonging to an MBMS cell group the CRNC may perform re-synchronization actions enabling UEs to perform the selective combining between these cells.
+
+For TDD, selection combining and soft combining can be used when Node-Bs are synchronised. For FDD soft combining can be used when Node-Bs are synchronized inside UE's soft combining reception window, and the data fields of the soft combined S-CCPCHs are identical during soft combining moments.
+
+When selective or soft combining is available between cells the UTRAN should send MBMS NEIGHBOURING CELL INFORMATION containing the MTCH configuration of the neighbouring cells, available for selective or soft combining. When partial soft combining is applied the MBMS NEIGHBOURING CELL INFORMATION contains the L1-combining schedule, which indicates the time moments when the UE may soft combine the S-CCPCH transmitted in neighbouring cells with the S-CCPCH transmitted in the serving cell. With MBMS NEIGHBOURING CELL INFORMATION the UE is able to receive MTCH transmission from neighbouring cell without reception of the MCCH of that cell.
+
+The UE determines the neighbouring cell suitable for selective or soft combining based on threshold (e.g. measured CPICH Ec/No) and the presence of MBMS NEIGHBOURING CELL INFORMATION of that neighbour cell.
+
+The possibility of performing selective or soft combining should be signalled to the UE.
+
+### 7.1.bis Simulcast Combining (TDD only)
+
+In contrast to FDD, downlink macro diversity has not been a characteristic of TDD during release '99/4/5. As such TDD receivers are not typically designed to facilitate the simultaneous reception of multiple radio links and the incorporation of such a requirement for MBMS in TDD would have non-trivial impacts on the receiver design.
+
+Much of the receiver complexity increase associated with the combining of multiple radio links in the UE can however be avoided in TDD by combining macro-diversity with timeslot re-use. This also allows for the throughput gains from timeslot re-use to be combined with further gains from macro diversity.
+
+In such a scheme, the transmissions of the same information from the multiple participating cells are arranged such that they arrive at the UE on substantially different timeslots, thereby removing the requirement at the UE to detect multiple cells in the same timeslot.
+
+As such, cells are partitioned into transmission "groups" or "sets". Each transmission set is allocated a timeslot (or set of timeslots) for MBMS transmission. The assigned slots are typically exclusively used by that MBMS set; sets do not transmit when another set is active. The UE attempts to receive information from each set and to combine them either at the physical layer or RLC layer in order to enhance reception reliability.
+
+Figure 7.1.bis shows such a scheme applied to a tri-sectorized deployment model. 3 timeslots ( $t_1$ , $t_2$ and $t_3$ ) are allocated to each sector for the purposes of MBMS transmission. Each sector is assigned to a particular "MBMS transmission set", set 1, 2 or 3.
+
+An MBMS data unit or transport block is encoded over several radio frames (eg: 80ms TTI). The physical channel bits that result are effectively transmitted three times; once by MBMS set 1 in timeslot $t_1$ , once by MBMS set 2 in timeslot $t_2$ , and once by MBMS set 3 in timeslot $t_3$ .
+
+
+
+**Legend:**
+
+- = cell site with a group of 3 individual sector transmitters
+- ▲ = UE receiver
+- ▨ = MBMS from set 1
+- = MBMS from set 2
+- ▤ = MBMS from set 3
+- ▒ = other channels
+
+**Transmission Schedule:**
+
+| timeslot | set 1 | set 2 | set 3 |
+|----------|--------|--------|--------|
+| t1 | Active | | |
+| t2 | | Active | |
+| t3 | | | Active |
+| t4 | | | |
+| t5 | | | |
+| t6 | | | |
+
+Figure 7.1.bis: Example of non-time-coincident macro diversity transmission. The figure illustrates a tri-sectorized cell deployment model across three timeslots (t1, t2, and t3). In each timeslot, a different MBMS transmission set is active. Set 1 (red hatched) is active in t1, Set 2 (yellow) in t2, and Set 3 (blue hatched) in t3. A UE receiver (green triangle) is shown receiving signals from the active sets. A legend identifies the symbols: red circle for a cell site with 3 sector transmitters, green triangle for a UE receiver, red hatched for MBMS from set 1, yellow for MBMS from set 2, blue hatched for MBMS from set 3, and green dotted for other channels. A graph on the right shows the transmission schedule for the three sets over six timeslots.
+
+**Figure 7.1.bis: Example of non-time-coincident macro diversity transmission**
+
+A given UE may be configured to listen to the separate transmissions of the MBMS physical channels (one from each set) which, over the course of the TTI, correspond to the MBMS transport block(s). The signals from each MBMS set
+
+are largely non-time-coincident and do not require the use of an extensively modified receiver architecture –a receiver architecture resembling that of a normal "single-radio-link" TDD receiver may be used.
+
+The received transport blocks may be provided to the RLC layer for selective combining, or soft information may be buffered and combined across MBMS sets during the course of the TTI via physical layer soft combining .
+
+The UTRAN shall signal to the UE on the MCCH which services may be soft combined (and in which cells). The cell group for soft combining may be different than the cell group for selective combining. The UE may assume that transmissions of a given service that may soft combined take place in the same frame.
+
+### 7.1.ter Chip Combining (1.28Mcps TDD)
+
+Chip Combining is a technique that bears some relation to Space Code Transmit Diversity (SCTD) in existing releases except that the combining is performed between cells with different scrambling codes instead of between transmit antennas of the same cell with the same scrambling code.
+
+Chip Combining has been proposed as another form of combining method for p-t-m transmissions for 1.28Mcps TDD mode. All involved cells still keep their own configuration of scrambling code (i.e. different cells participating in the p-t-m transmission have different scrambling codes on the MBMS timeslots). As for SFN transmission, in Chip Combining mode, all Node Bs involved are closely time synchronized, which is an inherent characteristic of TDD systems.
+
+The UE interested in one p-t-m MBMS service gets the active configuration, such as the midamble codes and the scrambling codes used in the current cell and in the involved neighbouring cells from BCCH and/or MCCH. The UE must monitor the signal strengths of the involved cells and must select a number of cells to combine. In an active p-t-m timeslot, the UE performs channel estimation of each cell to be combined and gets the system matrixes of each involved cell respectively, and then, one compound system matrix can be formed by combining the system matrix of these involved cells. After that, the UE uses joint detection algorithm to recover the MBMS data with the compound system matrix.
+
+Chip Combining brings no change and requirement to network equipment. However, in order to approach the performance offered by SFN, a relatively large number of cells must be detected and efficiently combined by the UE. Alternatively, chip combining could be used for small service areas (only a small number of cells participate in a simulcast transmission). In this case the number of cells which must be combined by the UE can be reduced and the performance loss compared to SFN is then lowered.
+
+A UE should have a minimum capability to detect and combine a certain number of cells so that performance of the MBMS p-t-m (and hence coverage of the MBMS service) can be guaranteed. The complexity of the UE and the performance of the chip combining method would have some bearing on the choice of this minimum number of cells that must be combined by the UE.
+
+## 7.1A MBMS over a Single Frequency Network (MBSFN)
+
+Another form of combining is possible for p-t-m transmissions and is realised via utilisation of the same scrambling code at a given moment in time by a group of cells covering a geographic area and is applicable for FDD and for TDD. This form of combining is referred to as MBMS over a Single Frequency Network (MBSFN). Signals from multiple cells may be combined by the UE in the same manner as used for multipath signal components from a single cell.
+
+The UE reception of MBMS services provided in MBSFN mode shall not affect the UE behaviour on the unicast carrier. Especially the UE mobility on the unicast carrier is not affected by the reception of MBMS services provided on a cell operating in MBSFN mode and can imply that the reception of the MBMS service on the cell operating in MBSFN mode is impossible due to the limited support of combination of frequency bands for MBMS SFN reception and unicast reception.
+
+MBSFN requires all Node Bs involved in the simulcast transmission to be closely time synchronised and exactly the same content is delivered to each of the involved Node Bs. All involved Node Bs are assumed to share the same CRNC (the MBSFN area is limited to the area controlled by a single RNC).
+
+For TDD, some or all timeslots may utilise an MBSFN mode of transmission. Such timeslots are configured by the RNC to use the same scrambling codes across participating Node-Bs. Any non-MBSFN timeslots continue to use the scrambling codes associated with the cell ID. The timeslots that are operating in the MBSFN mode form together with the synchronized neighbouring cells transmitting the exactly same data the over the MBSFN cluster.
+
+For FDD, Node-Bs participating in an MBSFN transmission do so on all slots of the radio frame. Thus, MBSFN transmission occupies an entire carrier in the case of FDD, whereas for TDD, part or all of the carrier may be used for MBSFN.
+
+In addition, MBSFN Integrated Mobile Broadcast (3.84 Mcps TDD MBSFN IMB) is defined. In this configuration, the downlink physical channels for the MBSFN option are mapped on a 3.84 Mcps TDD carrier frequency [10]. RF channel spacing according to the 3.84 Mcps TDD option is used. The entire carrier is used downlink for the 3.84 Mcps TDD MBSFN IMB transmission. For the Node B, the transmitter RF requirements defined for the 3.84 Mcps TDD carriers apply. For the UE, the receiver RF requirements defined for the 3.84 Mcps TDD carriers apply. A primary synchronisation code shall be used, which is orthogonal to the primary synchronisation code used in normal 3.84 Mcps TDD configurations. Unless specified otherwise, the RRC and the MAC protocols are operated according to the FDD requirements applicable for MBSFN.
+
+It shall be possible for UEs supporting MBSFN to receive MBMS via carriers operating in FDD or TDD MBSFN mode and to also obtain unicast and MBMS (those not provided via MBSFN) by another carrier.
+
+Allied to MBSFN is the use of higher order modulation techniques (16QAM) for S-CCPCH and in the case of 3.84/7.68 Mcps TDD only the use of a new burst type to support longer delay spread. In case of 3.84 Mcps TDD MBSFN IMB, there are two types of S-CCPCHs: S-CCPCH frame type1 and S-CCPCH frame type2. S-CCPCH frame type 1 consists of 15 slots per radio frame and uses a channelisation code of spreading factor 256. FACH carrying MCCH is mapped onto S-CCPCH type 1. S-CCPCH frame type 2 uses channelisation codes of spreading factor 16 and consists of 5 sub-frames per radio frame; each sub-frame consisting of 3 slots. S-CCPCH frame type 2 is used to support short duty cycles on MTCH. The FACH carrying MTCH may be mapped onto one or more codes of spreading factor 16.
+
+Reception of MBMS services over a network operating in MBSFN mode implies that the UE is registered to a PLMN in order to perform higher layer procedures such as subscription to MBMS broadcast services. The means by which a UE obtains details of services provided, subscribes to those services it is interested in and obtains any ciphering keys necessary to decrypt services and/or means by which the services are delivered (MBSFN mode, frequency band used etc.), is considered to be outside the scope of 3GPP specifications. However, it is envisaged that the UE may obtain service details via a point-to-point connection via the carrier that is used to provide unicast services.
+
+The UE selects a MBSFN cluster to receive MBMS service that is part of one of the registered PLMN or part of the equivalent PLMN list. (Note: Network sharing is supported on carriers operating in MBSFN mode using the possibility to broadcast multiple PLMNs in the MIB just as it supported on carriers supporting unicast services)
+
+For the MBSFN cluster in 1.28 Mcps TDD mode, the UE that needs receive MBMS services delivered in an MBSFN cluster may first get synchronized to the non MBSFN cell that the MBSFN cluster is associated with and then search the MBSFN cluster with the information indicated in the system information of the non MBSFN cell. From the UE's perspective, the registered PLMN of the MBSFN cluster should be the same as the PLMN that is registered by the UE from the associated unicast carrier.
+
+A MBSFN cluster provides only MBMS service in PtM mode. Counting and PtP establishment procedures are not supported for a cell operating in MBSFN mode.
+
+For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD, the selection between MBSFN clusters is performed similarly to the way that cell selection is performed for cells that are not operating in MBSFN mode. The UE shall meet the minimum performance requirements specified for the reception of a MBMS cluster. The UE may consider a minimum receive power of the CPICH (FDD and 3.84 Mcps TDD IMB) or P-CCPCH (3.84/7.68 Mcps TDD) in order to determine when to receive MBMS service broadcast in MBSFN mode. However apart from background search procedures for receiving other MBSFN clusters the UE is not required to perform inter-frequency measurements for other MBSFN clusters. Hierarchical cell structure, rules for fast moving UEs and inter-frequency and inter RAT measurements are not applicable for the cell operating in MBSFN mode. The intra frequency measurements for the reselection between MBSFN clusters are not specified.
+
+In a MBSFN cluster only MIB, system information blocks 3, 5/5bis and 11 may be broadcast. The content of other system information blocks is ignored by the UE.
+
+A MBSFN cluster on one frequency might indicate the existence and the services provided by other MBSFN clusters on different frequencies. The MBSFN cluster on one frequency may also indicate other MBSFN frequencies that have to be selected in order for the UE to be aware of available services that are not provided via the currently selected MBSFN cluster and for which the availability can not be indicated on the current MBSFN cluster. The choice of the MBSFN frequency based on this information is UE implementation specific. Because inter frequency measurements for MBSFN frequencies are not applicable the choice of the MBSFN frequency done by the UE may be completely service dependant. For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD the UE only has to discover one MBMS cluster
+
+on another frequency that fulfils the selection criteria. Other frequencies on which MBMS service is broadcast in MBSFN mode is indicated on the MBSFN frequency.
+
+A cluster operating in MBSFN mode does not provide paging information because the MBSFN cluster will not be considered as a suitable cell by the UE.
+
+The cells in a MBSFN cluster belong to different MBMS service areas compared to the cells of a carrier providing unicast service. This allows the RNC to know which services are intended for the transmission on the cells of a MBSFN cluster. The same MBMS bearer service is not provided on a MBSFN cluster and the unicast cells.
+
+The minimum MBMS service area must be equal to one MBSFN cluster. A MBMS bearer service must be transmitted in a complete MBSFN cluster.
+
+### 7.1A.1 3.84 / 7.68 MCPS TDD MBMS over a Single Frequency Network (MBSFN)
+
+A TDD UE operating on a carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10). For TDD carriers not dedicated to MBSFN, MBMS services may be delivered via MBSFN and/or non-MBSFN means. In the case that any non-MBSFN transmissions are used to deliver MBMS services, the MCCH should not be transmitted via MBSFN means.
+
+The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a TDD cell dedicated to MBSFN operation the UE is conceptually an independent component which receives MBMS service on a TDD cell dedicated to MBSFN.
+
+The TDD component of a UE for receiving MBMS service on a TDD carrier dedicated to downlink MBSFN shall:
+
+- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE
+- obtain details concerning the MCCH provided via the BCCH of the cell providing MBSFN and listen to that MCCH for details of MBMS services provided p-t-m on the TDD DL-only carrier
+- search for a suitable TDD MBSFN cluster providing the MBMS services that it is interested in:
+ - o is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH, SCH on the TDD carrier
+ - o may optionally support MICH on the TDD carrier
+ - o shall expect to receive S-CCPCH configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the TDD carrier.
+
+### 7.1A.2 FDD MBMS over a Single Frequency Network (MBSFN)
+
+A FDD UE operating on a carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10).
+
+The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a FDD cell dedicated to MBSFN operation the UE is conceptually an independent component which receives MBMS service on a FDD cell dedicated to MBSFN.
+
+The FDD component of a UE operating in a receive-only mode on a FDD carrier operating in MBSFN mode shall:
+
+- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE
+- obtain details concerning the MCCH provided via the BCCH of the cell providing MBSFN and listen to that MCCH for details of MBMS services provided p-t-m on the FDD DL-only carrier
+- search for a suitable FDD MBSFN cluster:
+
+- is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH and SCH on the FDD carrier
+- may optionally support MICH on the FDD carrier
+- shall expect to receive S-CCPCH configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the FDD carrier.
+
+#### 7.1A.31.28 MCPS TDD MBMS over a Single Frequency Network (MBSFN)
+
+A TDD UE operating on a carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10). For TDD carriers not dedicated to MBSFN, MBMS services may be delivered via MBSFN and/or non-MBSFN means. In the case that any non-MBSFN transmissions are used to deliver MBMS services, the MCCH should not be transmitted via MBSFN means.
+
+The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a TDD cell dedicated to MBSFN operation the UE is conceptually an independent component which receives MBMS service on a TDD cell dedicated to MBSFN.
+
+The TDD component of a UE for receiving MBMS service on a TDD carrier dedicated to downlink MBSFN shall:
+
+- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE
+- obtain details concerning the MCCH provided via the BCCH of the cell providing MBSFN and listen to that MCCH for details of MBMS services provided p-t-m on the TDD DL-only carrier
+- search for a suitable TDD MBSFN cluster providing the MBMS services that it is interested in:
+ - is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH on the TDD carrier
+ - may optionally support MICH on the TDD carrier
+ - shall expect to receive S-CCPCH configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the TDD carrier.
+
+NOTE: For 1.28 Mcps TDD, if a cell is operating in MBSFN mode, system information and MCCH messages are transmitted through the Special Timeslot [10].
+
+#### 7.1A.43.84 Mcps TDD IMB MBMS over a Single Frequency Network (MBSFN)
+
+A 3.84 Mcps TDD MBSFN IMB capable UE operating on an FDD or 3.84/7.68 Mcps TDD carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10).
+
+The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a cell dedicated to 3.84 Mcps TDD MBSFN IMB operation, the UE is conceptually an independent component which receives MBMS service on a cell dedicated to 3.84 Mcps TDD MBSFN IMB.
+
+The 3.84 Mcps TDD MBSFN IMB component of a UE receiving MBMS service on a 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB shall:
+
+- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE;
+- obtain details concerning the MCCH provided via the BCCH of the cell providing 3.84 Mcps TDD MBSFN IMB and listen to that MCCH for details of MBMS services provided p-t-m on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB;
+- search for a suitable MBSFN cluster providing the MBMS services the UE has activated;
+
+- o is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2 and SCH on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB;
+- o may optionally support MICH on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB;
+- o shall expect to receive S-CCPCH frame type 1 configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB.
+
+## 7.1B MBMS in case of inter-RNC synchronization
+
+### 7.1B.1 Control Plane aspects
+
+#### 7.1B.1.1 MBMS Parameter Configurations
+
+The common parameters in MBMS P-t-M RB configurations shall be configured in each RNC semi-static manner via O&M.
+
+The parameters, transmitted in RRC: MBMS Common P-T-M RB Information and to be configured, are:
+
+- RB Information list
+ - RB identity
+ - PDCP info
+ - RLC info
+- TrCh information for each TrCH
+ - Transport channel identity
+ - TFS
+- TrCh information for each CCTrCh
+ - CCTrCH identity
+ - TFCS
+
+In case of soft combining the Secondary CCPCH configurations shall be aligned between the neighboring cells.
+
+In case of MBSFN:
+
+If MBMS services are controlled statically, the parameters to be configured for MBSFN:
+
+- PhyCh information
+ - PhyCh identity
+ - Secondary CCPCH info MBMS
+
+.In the case the used parameter value in a cell may depend on the received RAB QoS and/or MBMS service area ID and/or TMGI value, the mapping information should be configured via O&M. Such mapping information should be available in RNCs before the MBMS session setup.
+
+If MRNC is used, the parameters shall be configured by MRNC, and the MRNC shall inform CRNC of the configuration and mapping information of MBMS service to RB information at session start.
+
+In addition to parameters used for air interface, the pool of DL TEIDs used for the MBMS transmission on Iu carried by IP-multicast distribution shall be configured in all RNCs by O&M. The stored DL TEIDs used in IP multicast distribution shall not be used by the RNC for any other transmission.
+
+#### 7.1B.1.2 MBMS Counting and mode switch coordination
+
+The RNC shall generate the MBMS Counting procedure towards UEs as in case of intra-RNC selective/soft combining (see section 5.2.5).
+
+If the RNS controlled by a RNC is smaller than the possible selective / soft combining area, the status of the cells in surrounding RNC that are part of the selective/soft combining area should be known before deciding on the own transmission mode. Therefore the RNC shall exchange the transmission mode and counting information with the neighbouring RNCs, which are controlling cells part of the same selective/soft combining area as the cells controlled by the current RNC. Also the neighbour cells indicated for selective/soft combining in MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message have to be coordinated between RNCs.
+
+The RNSAP function, *Information Exchange* is used for counting and mode switch coordination.
+
+The RNC may request for the counting results and transmission mode information in cells controlled by a neighbour RNC by sending the INFORMATION EXCHANGE INITIATION REQUEST message to the relevant neighbouring RNCs.
+
+For counting the INFORMATION EXCHANGE INITIATION REQUEST message will contain the information about the cells controlled by the sending RNC, for which the sending RNC have requested counting. The RNC receiving the INFORMATION EXCHANGE INITIATION REQUEST message shall first identify if any of the cells received in the message is announced as a neighbour cell for the MBMS service in the cells controlled by the receiving RNC (own cells). Thereafter the receiving RNC shall perform counting in these own cells and inform sending RNC about the result over Iur in the INFORMATION EXCHANGE INITIATION RESPONSE message.
+
+For MBMS transmission mode change the INFORMATION EXCHANGE INITIATION REQUEST message will contain information about the cells controlled by the sending RNC ("initiating cell list") and the TMGIs for which the MBMS transmission mode are requested to be reported when the transmission mode is changed. The MBMS transmission mode shall be reported for cells under control of the RNC receiving the INFORMATION EXCHANGE INITIATION REQUEST message. The MBMS transmission mode for the TMGIs in the INFORMATION EXCHANGE INITIATION REQUEST message shall be reported for the cells that have a configured neighbour relation to the cells in the "initiating cell list".
+
+The RNC initiating the Information Exchange Initiation procedure shall use the received MBMS transmission mode information of the neighbour cells under control of another RNC to update MBMS NEIGHBOURING CELL P\_T\_M RB INFORMATION message content of its own cells.
+
+#### 7.1B.1.3 Control Plane Coordination at MBMS Session Start
+
+##### 7.1B.1.3.1 Coordination of neighbor cell configuration
+
+The RNC shall at MBMS session start in its own cells, being part of the targeted MBMS service area, activate the RNSAP Information Exchange Initiation procedure to all neighboring RNCs, which are controlling cells allowed to be used for selective/soft combining with the relevant own cells of the RNC. The response, INFORMATION EXCHANGE INITIATION RESPONSE and INFORMATION REPORT messages shall contain the copy of the RRC containers, which were sent out on MCCH announcing the active MBMS session and for each MBMS session that is started a list of cell identities in which the MBMS session (identified with TMGI) was setup.
+
+The receiving RNC shall identify based on the received information the valid neighbor cells for soft/selective combining in the RNC, which is the sender of the message for the new MBMS session, and retrieve the S-CCPCH configuration in those neighboring cells. Finally the MBMS COMMON P-T-M RB INFORMATION shall be updated with the received S-CCPCH configuration information and the neighboring cells are announced in MBMS NEIGHBOURING CELL P-T-M RB INFORMATION.
+
+As part of the "Valid neighbor cell identification" the RNC shall verify that the configuration of the cells of the sending RNC is aligned and possible for soft combining, e.g. that the MBMS logical channel id is aligned for all MBMS sessions. The RNC shall not accept the cell as neighbor cell if not aligned. The consequence of a mismatch is that the soft/selective combining gain is lost for this MBMS session, but as this abnormal condition only occurs rarely it is regarded as acceptable.
+
+###### Coordination of MBMS configurations after RNC restarts
+
+In case of restart the RNC may lose all the MBMS configurations of its cells as well the neighbor cell MBMS information and any other MBMS related parameters.
+
+The RNC will recover from that situation by getting the MBMS configurations updated in a three phase approach:
+
+1. via O&M the MBMS service configurations for its cells. In addition to the MBMS service area configurations there are other parameters which can be configured semi-static manner via O&M system like indicated above.
+2. As part of the general restart procedure the SGSN will send the Session Starts for all ongoing MBMS sessions to the RNC. RNC will respond to the MBMS Session Start messages normal manner in line with the MBMS service area configurations of its cells.
+3. After the RNC has become aware of the active MBMS sessions it will identify the relevant neighboring RNCs which should be contacted to retrieve the necessary parameters for the neighbor cell configuration.
+
+#### 7.1B.1.4 MCCH synchronization in an MBSFN cluster
+
+To synchronize MCCH dynamically, the logical entity "MBMS Master RNC" may be introduced to control the resources of the RNSs within the MBSFN cluster(s). There's only one MBMS Master RNC for any MBSFN cluster. The other RNC can be seen as the CRNC.
+
+If MRNC is used, the RNSAP procedure "MBSFN MCCH Information" is used to transfer information between MRNC and CRNC to synchronize the MCCH.
+
+### 7.1B.2 User Plane aspects
+
+#### 7.1B.2.1 Timing requirements
+
+The soft combining and MBSFN mode across RNCs will require similar timing requirements between the cells controlled by different RNCs as what is required for cells part of same RNC in Rel-6 and Rel-7. The summary of the timing requirements is presented in the table below.
+
+**Table 7.1B.2.1-1 The table summarizes the timing requirements for WCDMA MBMS**
+
+| Functionality | Release | Timing requirement |
+|----------------------------------------------------|------------------|--------------------|
+| MBMS 40 ms TTI | 3GPP Release 6 | 40.667 ms |
+| MBMS 80 ms TTI | 3GPP Release 6 | 80.667 ms |
+| MBMS with single frequency network support (MBSFN) | 3GPP Release 7/8 | 12.8 microseconds |
+
+There are several ways to synchronize the network elements to a common reference time: which meet Rel6/MBSFN timing requirements.
+
+- 3GPP synchronization in UTRAN,
+- Network Time Protocol (NTP),
+- Relying on IP multicast distribution,
+- Global positioning system (GPS),
+- IEEE1588.
+
+All the listed synchronisation methods may be used but the provided accuracy could be dependent on the synchronisation deployment solution
+
+#### 7.1B.2.2 MBMS User Data flow synchronization
+
+The synchronized radio interface transmission from the cells controlled by different RNCs require a SYNC-protocol support over the Iu-interface between the BM-SC and the RNCs.
+
+As part of the SYNC-protocol procedure the BM-SC shall include to the SYNC PDU packets a time stamp which tells the timing based on which the RNC sends MBMS data over air interface. This time stamp is based on a common time reference available at the BM-SC and the RNCs and represents a relative time value which refers to the start time of the synchronisation period.
+
+MBMS user data shall be time-stamped based on separable synchronization sequences which are tied to multiples of the TTI length. Synchronization sequence is transmitted continuously, even if there is no MBMS user data in the
+
+synchronization sequence. Each synchronization sequence for each service is denoted by a single timestamp value working in such a manner that an increase of the timestamp value by one synchronisation sequence length shall be interpreted as an implicit start-of-a-new-synchronization-sequence-indicator, so that the RNC becomes aware that a new sequence is starting. For additional robustness, the timestamp shall be replicated to all packets that shall be submitted over the air interface within one or multiple TTIs.
+
+When adding the Time Stamp the BM-SC should take into account following factors: arrival time of data, the Maximum Transmission Delay from BM-SC to the farthest RNC, the length of the synchronization sequence used for time stamping and other extra delay (e.g. processing delay in RNC and NodeB ). The parameters 'Max Tx Delay', 'synchronization sequence length' and 'Other Extra Delay' are set via O&M in BM-SC.
+
+The BM-SC does not know the absolute time point at which a TTI starts, but the sequence length for the time stamp is set by O&M like the delay parameters. The BM-SC will use the delay parameters to define the transmission time point of that user data packet and for the following user data packets the sequence length for the time stamp: following user data packets arriving within e.g. 40ms will receive the same time stamp value as the first data packet, if the sequence length is set to be 40 ms.
+
+The RNC shall schedule the received data packets in the TTIs following the time point indicated by the timestamp.
+
+NOTE: From the timestamp the RNC can interpret the TTI from which the transmission of the first user data packet with that time stamp value shall start. Whether there will be data packets to be transmitted in the following TTIs will depend on the used synchronization sequence length vs. the TTI length and on the user data flow.
+
+In case MRNC is used and TDM multiplexing is used over air interface, scheduling transmission time interval is defined as a time interval of the minimal common multiple of synchronization sequence length and TDM period (CFN period shall be divided by TDM period) in the MRNC. The MRNC shall inform the scheduling transmission time interval to the RNCs over Iur together with MCCH message. The RNC shall schedule received data packets in the scheduling transmission time interval following the time point indicated by the timestamp. If multiple synchronization sequences are to be transmitted consecutively in one scheduling transmission time interval, these synchronization sequences shall be processed as if they are a single synchronization sequence.
+
+In case MRNC is not used and TDM is used over air interface, the synchronization sequence length should be configured to be multiples of the TDM Period (CFN period shall be a multiple of the TDM period).
+
+The elementary procedures related to the SYNC-protocol are defined in [14].
+
+In addition to the Time Stamp parameter the BM-SC shall provide together with each MBMS User data packet the '*Packet Counter*' and '*Elapsed Octet Counter*' information. Based on these parameters the RNC is able to notice if any data packets were lost during transmission via IP Multicast and to know the size of the lost payload, in case of a single packet is lost. Additionally the RNC is able to reorder the PDUs before passing them to RLC processing, if needed.
+
+At the end of each synchronization sequence the BM-SC shall send to the RNCs at least one user data frame, which contains counter information including '*Total Number Of Packet Counter*' and '*Total Number Of Octet*' without MBMS payload. This *Total Counter* frame is implicitly marking the end-of-sync.seq.. The *Total Counter* frame without payload may be repeated in order to improve the reliability of the delivery to the RNCs.
+
+If neither Total Counter frame nor data Frame is received by a RNC for a synchronization sequence, the RNC shall regard the whole synchronization sequence data frame as lost.
+
+#### 7.1B.2.3 User Plane recovery in case of Multiple Packets Loss
+
+In case multiple contiguous SYNC PDUs are lost in the RNC, the division of payload between the lost packets is not necessarily known by the RNC. This may lead to an incorrect RLC SN value usage in the RNC, when handling the first data packet received from BM-SC after the multiple packet loss. The RNC is able to notice the loss of multiple user data packets based on the '*Packet Counter*' information delivered by the SYNC-protocol together with the user data packets. In such a situation the radio interface transmission should be avoided until the RNC is able to resynchronize its transport block creation with the neighbouring RNCs or the radio interface transmission may be avoided for exact TTI(s) impacted by the lost SYNC PDUs using the help of the length information of the lost SYNC PDU provided by SYNC protocol.
+
+In case of soft combining and MBSFN mode the RNC resynchronization is supported by the RLC SN reset at the start of each synchronization sequence in all RNCs part of the IP Multicast distribution. The RNCs are able to notice the start
+
+of the synchronization sequence from the new time stamp value and the packet counter information received from BM-SC.
+
+In case MRNC is used and TDM multiplexing is used over air interface, the RNC re-synchronization is supported by the RLC SN reset at the start of each scheduling transmission time interval signalled from MRNC in all RNCs part of the IP Multicast distribution.
+
+In case of selective combining the RNC shall request from the neighbouring RNCs, which are used for selective combining for that particular MBMS stream, the correct RLC SN value to be used for the first RLC PDU of the next synchronization sequence.
+
+## 7.2 UE Capability
+
+The UE MBMS capability is not sent to UTRAN and is subject to UE implementation, including the relation between MBMS capability and actual RRC state which is also a UE implementation. A consequence is that a UE may be counted although its actual capability does not allow to receive MBMS transmissions e.g. because of its current RRC state.
+
+The standard will describe a minimum UE capability requirement in order to allow operators to configure MBMS channels that can be common to all UEs supporting the given service.
+
+There are some UE capability requirements that are common to all eventual service categories:
+
+The minimum UE capability for MBMS capable UE, is one primary CCPCH plus all the configurations below. The UE is not required to support these configurations simultaneously.
+
+1. One PICH and one MICH
+2. One S-CCPCH and one MICH
+3. One S-CCPCH (dedicated FACH and possibly the FACH, which may carry MCCH) and two S-CCPCH with 80ms TTI for MTCH reception
+4. One S-CCPCH (dedicated FACH and possibly the FACH, which may carry MCCH) and three S-CCPCH with 40ms TTI for MTCH reception
+5. One PICH and two S-CCPCH with 80ms TTI for MTCH reception
+6. One PICH and three S-CCPCH with 40ms TTI for MTCH reception
+
+The requirement one reflects the case when the UE is in Idle mode, or URA\_PCH, CELL\_PCH state and MBMS reception is not ongoing and requirement five and six are for the case that MBMS reception is ongoing in Idle mode, or URA\_PCH, CELL\_PCH state.
+
+The requirement two reflects the case when the UE is in CELL\_FACH state and MBMS is reception not ongoing and requirement three and four are for the case when MBMS reception is ongoing respectively.
+
+The requirement for the number of simultaneous S-CCPCHs for MTCH reception includes those S-CCPCHs for which combining is performed.
+
+When MBMS ptm reception is ongoing, the UE is required to periodically monitor the MCCH, which may be mapped onto a different S-CCPCH from MTCH, and a different S-CCPCH than the R'99 FACH when the UE is in CELL\_FACH state. However this does not increase the requirement for the number of S-CCPCHs to be simultaneously received by the UE.
+
+The ability of the UE to receive DPCH/HS-PDSCH simultaneously with S-CCPCH carrying MTCH/MCCH is subject to UE capability.
+
+The minimum MBMS bit rate that all MBMS capable UEs shall support is to be defined [12].
+
+For FDD, the UE shall support selective combining and soft combining on cells not indicating that they provide MBMS service in MBSFN mode.
+
+For FDD and 3.84 Mcps TDD IMB, the UE is not required to support selective combining and soft combining on cells indicating that they provide MBMS service in MBSFN mode.
+
+For a TDD UE supporting both transmit and receive functions, selective and soft combining shall be supported. For a 3.84 / 7.68 Mcps TDD UE supporting both transmit and receive functions, MBSFN operation shall also be supported. For a UE supporting 3.84 / 7.68 Mcps TDD MBSFN receive only, support for selective combining and soft combining is not required.
+
+The standard may restrict further the UE implementation options by defining certain capability combinations.
+
+If the UE is supporting MBMS ptm reception in CELL\_DCH state, it shall have capability to acquire MCCH configuration from BCCH after handover procedure, and after that receive MCCH and MTCH.
+
+## 7.3 MBMS Reception
+
+The following descriptions add MBMS specific processes to be considered for each RRC State/Mode.
+
+The BCCH contains information regarding the MCCH, while the latter contains information on the MTCH.
+
+In the sub-sections below, how and when the UE reads the MCCH is not described as periodic MCCH transmission is described in section 5.2.3.
+
+The reception of multiple MBMS services simultaneously is subject to UE capability; selection principles between MBMS services are defined in section 5.2.8. The specific actions related to MBMS session repetition are specified in section 5.2.7.
+
+### 7.3.1 MBMS Reception in RRC Idle Mode
+
+In idle mode, the UE shall:
+
+- if the UE supports MBMS and
+- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available
+ - act on RRC messages received on MCCH and:
+ - if the MBMS service requires the establishment of an RRC Connection due to counting response or due to the utilisation of p-t-p transfer mode for the MBMS service:
+ - inform upper layers that the MBMS Service requires the establishment of an RRC Connection.
+ - if the MBMS service does not require the establishment of an RRC Connection :
+ - listen to the common transport channel on which the MTCH is mapped.
+ - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell:
+ - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell.
+
+### 7.3.2 MBMS Reception in RRC Connected Mode: URA\_PCH state
+
+In URA\_PCH, the UE shall:
+
+- if the UE supports MBMS and
+- if the UE has activated an MBMS service and there is an ongoing session for this service in the URA where the UE is situated, i.e. MTCH and MCCH are available
+ - act on RRC messages received on MCCH,
+ - if on the MCCH it is indicated that the MBMS service in the cell requires a counting response or is due to the utilisation of p-t-p transfer mode for the MBMS service:
+ - initiate a cell update procedure, for sending MBMS COUNTING RESPONSE, or MBMS P-T-P MODIFICATION REQUEST signalling flow. The cause to be used in the cell update procedure is defined in [13].
+
+- for each MBMS service that the UE has activated and where transmission on a MTCH is indicated in the MCCH, listen to the common transport channel on which the MTCH is mapped,
+- if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell
+ - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell.
+
+### 7.3.3 MBMS Reception in RRC Connected Mode: CELL\_PCH state
+
+In CELL\_PCH, the UE shall:
+
+- if the UE supports MBMS and
+- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available
+ - act on RRC messages received on MCCH
+ - if on the MCCH it is indicated that the MBMS service in the cell requires counting response or is due to the utilisation of p-t-p transfer mode for the MBMS service:
+ - initiate a cell update procedure for sending MBMS COUNTING RESPONSE, or MBMS P-T-P MODIFICATION REQUEST signalling flow. The cause to be used in the cell update procedure is defined in [13].
+ - listen to the common transport channel on which the MTCH is mapped,
+ - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell
+ - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell.
+
+### 7.3.4 MBMS Reception in RRC Connected Mode: CELL\_FACH state
+
+In CELL\_FACH, the UE shall:
+
+- if the UE supports MBMS and
+- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available
+ - act on RRC messages received on MCCH
+ - if on the MCCH it is indicated that the MBMS service in the cell requires a counting response or is due to the utilisation of p-t-p transfer mode for MBMS service:
+ - initiate a counting response for sending MBMS COUNTING RESPONSE, or MBMS P-T-P MODIFICATION REQUEST signalling flow.
+ - listen to the common transport channel on which the MTCH is mapped
+ - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell
+ - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell.
+
+NOTE: For UEs in CELL\_FACH, UTRAN may decide to send MBMS data over DTCH.
+
+### 7.3.5 MBMS Reception in RRC Connected Mode: CELL\_DCH state
+
+In CELL\_DCH, the UE shall,
+
+- if the UE supports MBMS and
+
+- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available and
+- if the UE has the capabilities:
+ - act on RRC messages received on MCCH
+ - listen to the common transport channel on which the MTCH is mapped.
+ - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell and UE has capability
+ - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell.
+
+NOTE: For UEs in CELL\_DCH, UTRAN may decide to send MBMS data over DTCH
+
+# 8 UTRAN Signalling Flows for MBMS
+
+## 8.1 MBMS High Level Signalling Scenarios
+
+### 8.1.1 Session start
+
+Upon receiving a session start indication from CN, UTRAN initiates the session start sequence to allocate radio resources to UEs for receiving the MBMS content. As part of this sequence, UTRAN may apply the counting procedure (counting the number of idle mode, URA\_PCH, CELL\_PCH and CELL\_FACH state UEs) to decide whether to use the p-t-m or p-t-p transfer mode. For MBMS Broadcast mode, the applicability of the counting procedure for a service is indicated by the CN.
+
+The Figure 8.1.1 shows an example of a possible session start sequence.
+
+
+
+```
+
+sequenceDiagram
+ participant UE
+ participant UTRAN
+ Note right of UE: 1. Notification for session start
+ Note right of UE: 2. MBMS RB (MTCH, DTCH) establishment
+ Note right of UE: 3. MBMS data transfer
+
+```
+
+Sequence diagram showing the session start process between a UE and UTRAN. The diagram consists of three steps: 1. Notification for session start, 2. MBMS RB (MTCH, DTCH) establishment, and 3. MBMS data transfer. The UE and UTRAN are represented by boxes at the top, with vertical lines extending downwards. The steps are shown as horizontal bars between the two lifelines.
+
+Figure 8.1.1: Session start
+
+In general, the session start sequence involves the following steps:
+
+- In case UTRAN applies counting to determine the most optimal transfer mode the following steps are performed:
+ - UTRAN sets the correct MBMS Notification Indicator (NI) and sends the MBMS CHANGE INFORMATION and the MBMS ACCESS INFORMATION including service ID, the session ID if received from the CN, and access probability on MCCH.
+ - Upon DRX wakeup, UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH not receiving an MBMS service provided in p-t-m transfer mode evaluate the MBMS NI and if set, read the MBMS CHANGE INFORMATION from MCCH at beginning of the modification period. UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION directly. If service Id of activated MBMS service and session ID that the UE has not received is indicated in MBMS CHANGE
+
+INFORMATION UEs continue reading the rest of MCCH information. Upon receiving the MBMS ACCESS INFORMATION including access probability, UEs in idle mode or URA\_PCH, CELL\_PCH, and CELL\_FACH state for which the probability check passes, initiate counting response. UTRAN counts the UEs with an activated MBMS service by combining the UE linking from CN and received counting responses from UEs.
+
+- In the case that no UE is counted as present in the cell then UTRAN may decide not to provide any RB for the service in the cell.
+- In case a pre- defined threshold is reached, UTRAN applies the p-t-m RB establishment procedure specified below. Otherwise, UTRAN may repeat the MBMS ACCESS INFORMATION a number of times, using different probability values. If the threshold is not reached, UTRAN applies the p-t-p RB establishment procedure
+- In case UTRAN selects the p-t-m RB establishment procedure:
+ - UTRAN configures MTCH and updates MCCH (MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION) by including the service ID, the session ID if received from the CN, and p-t-m RB information for the concerned MBMS service
+ - In case p-t-m RB establishment is not preceded by counting, UTRAN sets the correct MBMS Notification Indicator (NI) and sends MBMS CHANGE INFORMATION.
+ - UTRAN sends the MBMS dedicated notification message including the service ID and cause= session start on DCCH to inform UEs in CELL\_DCH that are not receiving an MBMS service provided using p-t-m transfer mode
+ - In case p-t-m RB establishment is preceded by counting, UEs read MCCH at the pre- defined time(s) to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION
+ - In case p-t-m RB establishment is not preceded by counting, Upon DRX wakeup, UEs not receiving MTCH evaluate the MBMS NI and if set, read MCCH at beginning of modification period to acquire MBMS CHANGE INFORMATION. UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION directly. If service Id of activated MBMS service and session ID that the UE has not received is indicated in MBMS CHANGE INFORMATION UEs continue reading the rest of MCCH information to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION
+ - UEs that are incapable of receiving the MTCH for the session that is started in parallel to the existing activity notify the user. This enables the user to choose between the ongoing activity and the new MBMS service
+ - Upon receiving MBMS dedicated notification with cause= session start, UEs in CELL\_DCH that are incapable of receiving the MCCH and the corresponding MTCH in parallel to the existing activity notify the user. This enables the user to choose between the ongoing activity and the new MBMS service. If the user decides to receive the new MBMS service, the UE shall read MCCH to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION.
+ - Upon receiving the MBMS SERVICE INFORMATION and the MBMS RB INFORMATION including the p-t-m RB information for the concerned MBMS service, the UE starts receiving the p-t-m radio bearers
+- In case UTRAN selects the p-t-p RB establishment procedure:
+ - UTRAN indicates on MCCH in MBMS CHANGE INFORMATION that MBMS service is provided via p-t-p
+ - After receiving MBMS CHANGE INFORMATION UEs with an activated MBMS service, after possible service prioritisation, request MBMS p-t-p RB establishment by sending MBMS P-T-P MODIFICATION REQUEST signalling flow.
+ - Furthermore, UTRAN establishes the p-t-p RB by means of appropriate RRC procedures e.g. the RB setup procedure
+
+- UEs establish the p-t-p radio bearers by means of the RRC procedure selected by UTRAN eg. the RB setup procedure
+- UTRAN updates MCCH (MBMS SERVICE INFO) to inform UEs joining or entering the cell at a later point in time.
+
+### 8.1.2 Joining (during a session)
+
+In case the user wants to join an MBMS service (before or during a session), the UE initiates NAS procedures (e.g. MBMS service activation).
+
+If no session is ongoing upon completion of the joining procedure, the joining procedure is transparent to the AS.
+
+In case a session using p-t-m transfer mode is ongoing upon completion of the joining procedure, the UE may initiate reception of the p-t-m radio bearers. In case the ongoing session applies p-t-p transfer mode, UTRAN may establish the p-t-p radio bearers. UTRAN would do this upon receiving a UE linking indication from CN, which normally follows the joining. As a result of the UE linking, UTRAN may decide to change the transfer mode from p-t-p to p-t-m. This change of transfer mode is out of the scope of this sequence (to be covered by a separate sequence).
+
+The Figure 8.1.2 shows an example of a possible joining sequence.
+
+
+
+```
+
+sequenceDiagram
+ participant UE
+ participant UTRAN
+ Note right of UE: 1. Joining (NAS)
+ Note right of UTRAN: 2. Initiate reception of PTM RBs
+ Note right of UTRAN: 3. MBMS data transfer, PTM
+
+```
+
+Sequence diagram showing the joining process between a UE and UTRAN. The diagram consists of two vertical lifelines labeled 'UE' and 'UTRAN'. Three horizontal boxes represent the sequence of events: 1. Joining (NAS), 2. Initiate reception of PTM RBs, and 3. MBMS data transfer, PTM. The sequence starts with the UE sending a message to UTRAN for step 1, followed by UTRAN responding for step 2, and finally UTRAN sending data for step 3.
+
+**Figure 8.1.2: Joining with continuation of p-t-m**
+
+In general, the joining sequence involves the following steps:
+
+- UEs in idle mode first perform RRC connection establishment, while UEs in CELL\_PCH and URA\_PCH first perform cell update
+- UEs initiate the joining procedure (NAS)
+- In case UTRAN continues to use the p-t-m transfer mode:
+ - UTRAN sends the MBMS dedicated notification message on DCCH including the service ID and cause= session ongoing to inform UEs in CELL\_DCH
+ - Upon receiving MBMS dedicated notification with cause= session ongoing, UEs in CELL\_DCH that are incapable of receiving the MCCH and the corresponding MTCH in parallel to the existing activity notify the upper layer. This enables the user to choose between the ongoing activity and the new MBMS service. If the user chooses to receive the new MBMS service or if the UE in Cell\_DCH is capable of receiving MCCH and MTCH in parallel to the existing activity, the UE shall read MCCH to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION from MCCH.
+ - Upon acquiring the MBMS SERVICE INFORMATION and the MBMS RADIO BEARER INFORMATION including the p-t-m RB information for the concerned MBMS service, the UE starts receiving the p-t-m radio bearers
+- In case UTRAN continues using the p-t-p transfer mode:
+
+- UTRAN establishes the p-t-p RB by means of appropriate RRC procedures eg. the RB setup procedure
+- UEs establish the p-t-p radio bearers by means of the RRC procedure selected by UTRAN eg. the RB setup procedure.
+
+### 8.1.3 Recounting
+
+During a p-t-m MBMS session, UTRAN may perform re- counting to verify if p-t-m is still the optimal transfer mode. The purpose of the re- counting procedure is to count the number of idle mode, URA\_PCH, CELL\_PCH, and CELL\_FACH state UEs that have joined a specific service. As a result of this procedure, UTRAN may decide to change the transfer mode from p-t-m to p-t-p. This change of transfer mode is outside the scope of this sequence (to be covered by a separate sequence).
+
+The Figure 8.1.3 shows an example of a possible recounting sequence.
+
+
+
+```
+
+sequenceDiagram
+ participant UE
+ participant UTRAN
+ Note right of UTRAN: MBMS data transfer, PTM
+ Note right of UTRAN: 1. Notification for re-counting
+ Note right of UTRAN: 2: Act based on messages received on MCCH
+ Note right of UTRAN: MBMS data transfer, PTM
+
+```
+
+Sequence diagram illustrating the recounting process between a UE and UTRAN. The sequence starts with 'MBMS data transfer, PTM', followed by '1. Notification for re-counting', then '2: Act based on messages received on MCCH', and finally 'MBMS data transfer, PTM'.
+
+**Figure 8.1.3: Recounting with continuation of p-t-m**
+
+In case UTRAN applies re- counting to determine the most optimal transfer mode, the following steps are performed:
+
+- UTRAN sends the MBMS CHANGE INFORMATION and the MBMS ACCESS INFORMATION including service ID, and access probability on MCCH
+- UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION at the beginning of each modification period. If service Id of activated MBMS service is indicated in MBMS CHANGE INFORMATION UEs continue reading the rest of MCCH information.
+- Upon receiving the MBMS ACCESS INFORMATION including access probability, UEs in idle mode or URA\_PCH, CELL\_PCH and CELL\_FACH state for which the probability check passes, initiate counting response.
+- UTRAN counts the UEs with an activated MBMS service by combining the UE linking from CN and received counting responses from UEs.
+- In the case that no UE is counted as present in the cell then UTRAN may decide not to provide any RB for the service in the cell.
+- In case a pre- defined threshold is reached, UTRAN continues using the p-t-m transfer mode. Otherwise, UTRAN may repeat the MBMS ACCESS INFORMATION a number of times, using different probability values. If the threshold is not reached, UTRAN switches transfer mode from p-t-m to p-t-p
+- In case UTRAN continues using the p-t-m transfer mode, it may return UEs that responded to counting back to idle mode by releasing the RRC connection.
+
+### 8.1.4 Session stop
+
+UTRAN may apply the session stop procedure to inform UEs that the end of MTCH transmission concerns the end of a session rather than just an idle period. The purpose of the procedure is to reduce the UE power consumption.
+
+The Figure 8.1.4 shows an example of a possible session stop sequence.
+
+
+
+```
+
+sequenceDiagram
+ participant UE
+ participant UTRAN
+ Note right of UE: 1. Termination of MBMS data transfer, PTM
+ Note right of UE: 2. Notification for session stop
+
+```
+
+The diagram shows a sequence of two steps between a UE and a UTRAN. The first step is 'Termination of MBMS data transfer, PTM' and the second step is 'Notification for session stop'.
+
+Sequence diagram for Session stop procedure between UE and UTRAN.
+
+**Figure 8.1.4: Session stop**
+
+In case UTRAN provides the service p-t-m, the session stop sequence involves the following steps:
+
+- UTRAN updates the MBMS CHANGE INFORMATION, MBMS SERVICE INFORMATION and the MBMS RADIO BEARER INFORMATION including the service ID and the explicit radio bearer release indicator. UTRAN updates MCCH (MBMS SERVICE INFORMATION) to inform UEs joining or entering the cell in a later point of time.
+- UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION at the beginning of the each modification period. If service Id of activated MBMS service is indicated in MBMS CHANGE INFORMATION UEs continue reading the rest of MCCH information.
+- Upon receiving this information the UE stops receiving the MTCH
+
+In case UTRAN provides the service p-t-p, the session stop sequence involves the following steps:
+
+- UTRAN releases the p-t-p radio bearers and updates MCCH (MBMS SERVICE INFO) to inform UEs joining or entering the cell at a later point in time.
+
+## 8.2 MBMS RNC Signalling Flows
+
+### 8.2.1 MBMS Session Start procedure
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note right of CN: [RANAP] MBMS SESSION START REQUEST
+ Note left of RNC: [RANAP] MBMS SESSION START RESPONSE
+
+```
+
+The diagram shows a sequence of two messages between an RNC and a CN. The first message is '[RANAP] MBMS SESSION START REQUEST' sent from the CN to the RNC. The second message is '[RANAP] MBMS SESSION START RESPONSE' sent from the RNC to the CN.
+
+Sequence diagram for MBMS Session Start procedure between RNC and CN.
+
+**Figure 8.2.1: MBMS Session Start procedure. Successful operation.**
+
+The MBMS Session Start procedure is initiated by the CN when an MBMS Session is started. The MBMS SESSION START REQUEST is sent to each RNC that is connected to the CN (in case of Iu-flex the RNC may receive more than one MBMS SESSION START REQUEST message).
+
+The MBMS SESSION START REQUEST contains the MBMS Service Id, and optionally the MBMS Session ID, MBMS Bearer Service Type and the MBMS Session Attributes (MBMS Service Area Information, QoS parameters...) It may also include a list of RAs which lists each RA that contains at least one PMM-IDLE UE that has activated the service.
+
+MBMS Session Start procedure also provides the MBMS Iu Data Bearer Establishment functionality. In case of Iu-flex the RNC shall not establish more than one MBMS Iu bearer for a certain service towards a pool area and shall inform the respective CN nodes accordingly.
+
+The MBMS Session Start procedure in case of IP Multicast is described in section 8.2.16.
+
+### 8.2.2 MBMS Session Update procedure
+
+![Sequence diagram for MBMS Session Update procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION UPDATE REQUEST'. A second horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION UPDATE RESPONSE'.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg)
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: MBMS Session Update procedure. Successful operation.
+ CN->>RNC: [RANAP] MBMS SESSION UPDATE REQUEST
+ RNC-->>CN: [RANAP] MBMS SESSION UPDATE RESPONSE
+```
+
+Sequence diagram for MBMS Session Update procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION UPDATE REQUEST'. A second horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION UPDATE RESPONSE'.
+
+**Figure 8.2.2: MBMS Session Update procedure. Successful operation.**
+
+The MBMS Session Update procedure is initiated by the CN when an MBMS Session is ongoing and SGSN notices that there is a need to update the list of RAs. The MBMS SESSION UPDATE REQUEST contains the MBMS Service Id, and e.g. List of RAs with PMM Idle UEs..
+
+### 8.2.3 MBMS Session Stop procedure
+
+![Sequence diagram for MBMS Session Stop procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION STOP REQUEST'. A second horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION STOP RESPONSE'.](822e033872d5ab16e861571f47b81ba7_img.jpg)
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: MBMS Session Stop procedure.
+ CN->>RNC: [RANAP] MBMS SESSION STOP REQUEST
+ RNC-->>CN: [RANAP] MBMS SESSION STOP RESPONSE
+```
+
+Sequence diagram for MBMS Session Stop procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION STOP REQUEST'. A second horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION STOP RESPONSE'.
+
+**Figure 8.2.3: MBMS Session Stop procedure.**
+
+This signalling flow depicts the MBMS Session Stop procedure.
+
+This procedure is initiated by the CN to the RNCs with an ongoing MBMS session, when no more data will be sent for that MBMS service for some period of time.
+
+The MBMS Session Stop procedure also provides the MBMS Iu Data Bearer Release functionality.
+
+### 8.2.4 RNC Registration procedure
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: Initiated by RNC
+ RNC->>CN: [RANAP] MBMS REGISTRATION REQUEST
+ CN-->>RNC: [RANAP] MBMS REGISTRATION RESPONSE
+```
+
+The diagram shows a sequence of messages between an RNC and a CN. The RNC sends a '[RANAP] MBMS REGISTRATION REQUEST' to the CN, and the CN responds with a '[RANAP] MBMS REGISTRATION RESPONSE'.
+
+Sequence diagram for MBMS Registration procedure between RNC and CN.
+
+**Figure 8.2.4: MBMS Registration procedure.**
+
+This signalling flow depicts the MBMS Registration procedure.
+
+This procedure is initiated by the RNC in the case that the RNC is not SRNC for any UE that has joined the MBMS Service, but this RNC is DRNC for PMM-CONNECTED UEs that have joined the MBMS Service and there is no MBMS Service Context for the MBMS Service in this RNC.
+
+This procedure shall be initiated by the DRNC, as soon as a UE link is received over the Iur and there exists no MBMS Service Context for the MBMS service for which the UE link is received.
+
+### 8.2.5 RNC De-Registration procedure
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: Initiated by RNC
+ RNC->>CN: [RANAP] MBMS DE-REGISTRATION REQUEST
+ CN-->>RNC: [RANAP] MBMS DE-REGISTRATION RESPONSE
+```
+
+The diagram shows a sequence of messages between an RNC and a CN. The RNC sends a '[RANAP] MBMS DE-REGISTRATION REQUEST' to the CN, and the CN responds with a '[RANAP] MBMS DE-REGISTRATION RESPONSE'.
+
+Sequence diagram for RNC MBMS De-Registration procedure between RNC and CN.
+
+**Figure 8.2.5: RNC MBMS De-Registration procedure.**
+
+This signalling flow depicts the RNC De-Registration procedure. This procedure is initiated by the RNC towards the CN node it was registered to in case the RNC is not acting as a Serving RNC for any UE that has activated the MBMS Service and has ceased to act as a Drift RNC for UEs which has activated an MBMS service.
+
+### 8.2.6 CN De-Registration procedure
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note right of CN: Initiated by CN
+ CN->>RNC: [RANAP] MBMS DE-REGISTRATION REQUEST
+ RNC-->>CN: [RANAP] MBMS DE-REGISTRATION RESPONSE
+```
+
+The diagram shows a sequence of messages between a CN and an RNC. The CN sends a '[RANAP] MBMS DE-REGISTRATION REQUEST' to the RNC, and the RNC responds with a '[RANAP] MBMS DE-REGISTRATION RESPONSE'.
+
+Sequence diagram for CN MBMS De-Registration procedure between CN and RNC.
+
+**Figure 8.2.6: CN MBMS De-Registration procedure.**
+
+This signalling flow depicts the CN De-Registration procedure.
+
+This procedure is initiated by the CN in order to inform the RNC that a certain MBMS Service is no longer available.
+
+### 8.2.7 MBMS Channel Type Switching over Uu
+
+![Sequence diagram for MBMS Channel Type Switching over Uu. Lifelines: UE, CRNC, SRNC. The sequence starts with MBMS CONTROL (p-t-p) from CRNC to UE, followed by two MBMS DATA (p-t-m) messages from CRNC to UE. The CRNC then determines to switch channel type from ptm to ptp. It sends an MBMS Channel Type Reconfiguration Signalling over Iur to the SRNC. The SRNC decides whether to perform channel type switching to p-t-p or not. The SRNC sends an [RRC] RB SETUP message to the UE. The UE responds with [RRC] RB SETUP COMPLETE to the SRNC. Finally, the SRNC sends MBMS Data (p-t-p) to the UE.](036ceaf207a7b289ca76e160892eb724_img.jpg)
+
+```
+
+sequenceDiagram
+ participant UE
+ participant CRNC
+ participant SRNC
+ Note right of CRNC: CRNC determines to switch channel type from ptm to ptp
+ CRNC->>UE: MBMS CONTROL (p-t-p)
+ CRNC->>UE: MBMS DATA (p-t-m)
+ CRNC->>UE: MBMS DATA (p-t-m)
+ CRNC->>SRNC: MBMS Channel Type Reconfiguration Signalling over Iur
+ Note right of SRNC: SRNC decides whether to perform channel type switching to p-t-p or not
+ SRNC->>UE: [RRC] RB SETUP
+ UE->>SRNC: [RRC] RB SETUP COMPLETE
+ SRNC->>UE: MBMS Data (p-t-p)
+
+```
+
+Sequence diagram for MBMS Channel Type Switching over Uu. Lifelines: UE, CRNC, SRNC. The sequence starts with MBMS CONTROL (p-t-p) from CRNC to UE, followed by two MBMS DATA (p-t-m) messages from CRNC to UE. The CRNC then determines to switch channel type from ptm to ptp. It sends an MBMS Channel Type Reconfiguration Signalling over Iur to the SRNC. The SRNC decides whether to perform channel type switching to p-t-p or not. The SRNC sends an [RRC] RB SETUP message to the UE. The UE responds with [RRC] RB SETUP COMPLETE to the SRNC. Finally, the SRNC sends MBMS Data (p-t-p) to the UE.
+
+**Figure 8.2.7: Channel type switching signalling flow from p-t-m to p-t-p.**
+
+The CRNC is responsible for the decision regarding having p-t-m transmission or no p-t-m transmission in a cell for a specific MBMS service. The CRNC informs all the SRNCs having UEs in that cell about its decision. The SRNC is the RNC controlling the RRC connection and RBs to a specific UE. In the example shown, the CRNC decided to no longer use p-t-m, then the SRNC decided to perform channel type switching to deliver the MBMS service over DTCH mapped on a dedicated channel. The RB SETUP message contains the MBMS Service Id. It is FFS whether the SRNC always follows the CRNC's request or not.
+
+NOTE: the channel type switching in this case includes a change of both transport and logical channels.
+
+### 8.2.8 MBMS UE Linking
+
+![Sequence diagram for MBMS UE linking signalling flow. Lifelines: SRNC, CN. The SRNC sends a [RANAP] MBMS UE LINKING REQUEST message to the CN. The CN responds with a [RANAP] MBMS UE LINKING RESPONSE message to the SRNC.](18291be12b470a557e8c9f3a74e021be_img.jpg)
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant CN
+ SRNC->>CN: [RANAP] MBMS UE LINKING REQUEST
+ CN->>SRNC: [RANAP] MBMS UE LINKING RESPONSE
+
+```
+
+Sequence diagram for MBMS UE linking signalling flow. Lifelines: SRNC, CN. The SRNC sends a [RANAP] MBMS UE LINKING REQUEST message to the CN. The CN responds with a [RANAP] MBMS UE LINKING RESPONSE message to the SRNC.
+
+**Figure 8.2.8: MBMS UE linking signalling flow**
+
+This signalling flow is only applicable for handling UEs in PMM-CONNECTED mode with activated MBMS Services.
+
+The signalling flow is used to link a specific UE to one or several MBMS service contexts in the SRNC. The MBMS UE LINKING REQUEST message contains the whole list of MBMS Service Ids and MBMS PTP RAB IDs (e.g. mapped from NSAPIs) activated by the UE. If there has not been an MBMS service context related to an MBMS Service Id then SRNC creates an MBMS service context as a result of this procedure.
+
+### 8.2.9 MBMS UE De-Linking
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant SRNC
+ Note left of CN:
+ CN->>SRNC: [RANAP] MBMS UE DE-LINKING REQUEST
+ Note right of SRNC:
+ SRNC->>CN: [RANAP] MBMS UE DE-LINKING RESPONSE
+```
+
+The diagram shows a sequence of two messages between a Core Network (CN) and a Radio Network Controller (SRNC). The CN sends a '[RANAP] MBMS UE DE-LINKING REQUEST' to the SRNC, and the SRNC responds with a '[RANAP] MBMS UE DE-LINKING RESPONSE'.
+
+Sequence diagram for MBMS UE De-linking signalling flow between CN and SRNC.
+
+**Figure 8.2.9: MBMS UE De-linking signalling flow**
+
+This signalling flow is only applicable for handling UEs in PMM-CONNECTED mode with activated MBMS Services.
+
+The signalling flow is used to remove a specific UE from one or several MBMS service context in the SRNC. The MBMS UE DE-LINKING REQUEST message contains the list of MBMS Service Ids de-activated by the UE.
+
+### 8.2.10 MBMS Service Id Request
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant RNC
+ participant MSC
+ participant SGSN
+ Note left of UE:
+ UE->>RNC: Iu-cs connection establishment
+ Note right of RNC:
+ RNC->>MSC: [RANAP] COMMON ID
+ Note right of MSC:
+ MSC->>SGSN: [RANAP] MBMS SERVICE ID REQ
+ Note right of SGSN:
+ SGSN->>RNC: [RANAP] MBMS SERVICE ID RESPONSE
+```
+
+The diagram illustrates a sequence of interactions between a User Equipment (UE), Radio Network Controller (RNC), Mobile Switching Center (MSC), and Serving GPRS Support Node (SGSN). The UE initiates an 'Iu-cs connection establishment' with the RNC. The RNC then sends a '[RANAP] COMMON ID' message to the MSC. The MSC sends a '[RANAP] MBMS SERVICE ID REQ' to the SGSN, which responds with a '[RANAP] MBMS SERVICE ID RESPONSE' back to the RNC.
+
+Sequence diagram for MBMS Service Id list over Iu signalling flow between UE, RNC, MSC, and SGSN.
+
+**Figure 8.2.10: MBMS Service Id list over Iu signalling flow**
+
+This signalling flow is applicable for handling MBMS to UEs in RRC-Connected, PMM-IDLE state. The list of MBMS services the user has joined is sent over Iu.
+
+The purpose of this signalling flow is to perform UE linking for a RRC connected, PMM idle user. The UE provides an indication that the user has joined at least one MBMS service and the PS Domain specific IDNNS (the message that would carry this information is FFS) whenever an Iu-cs connection is established and the UE is PMM idle (that is there is no Iu-ps connection). The RNC requests the MBMS services the UE has joined from the SGSN (or the SGSN the UE is attached to in case of Iu-flex) using a connectionless procedure. The MBMS SERVICE ID REQ contains the IMSI of the UE. The SGSN response contains the full list of MBMS services the user has joined.
+
+The MBMS service list is then stored in the RNC. The list is deleted when the UE moves to RRC idle and the RRC context is removed in the RNC.
+
+### 8.2.11 MBMS Attach/Detach over Iur
+
+![Sequence diagram for MBMS attach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS ATTACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS ATTACH RESPONSE' message to the SRNC.](0f1767577a073167eb9628d72034e083_img.jpg)
+
+```
+sequenceDiagram
+ participant SRNC
+ participant CRNC
+ Note right of SRNC: [RNSAP] MBMS ATTACH REQUEST
+ SRNC->>CRNC: [RNSAP] MBMS ATTACH REQUEST
+ Note left of CRNC: [RNSAP] MBMS ATTACH RESPONSE
+ CRNC->>SRNC: [RNSAP] MBMS ATTACH RESPONSE
+```
+
+Sequence diagram for MBMS attach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS ATTACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS ATTACH RESPONSE' message to the SRNC.
+
+**Figure 8.2.11-1: MBMS attach request signalling flow: Successful Operation.**
+
+This signalling flow is only applicable for handling UEs in RRC connected mode with activated MBMS Services.
+
+The purpose of this signalling flow is
+
+- to either allow the CRNC to add one or several new UEs to the total number of UEs in a given cell using one or several MBMS services. The MBMS ATTACH REQUEST then contains the Cell Id of the new cell (may contain the URA Id of the new URA for UEs in URA\_PCH state), the whole list of affected MBMS Service Ids and a UTRAN specific UE Identification if necessary.
+- or to allow the SRNC to inform the DRNC in which URA notifications for MBMS Services have to be sent. The MBMS ATTACH REQUEST then contains a list of URAs and the corresponding MBMS Services.
+
+![Sequence diagram for MBMS detach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS DETACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS DETACH RESPONSE' message to the SRNC.](b4f6d3668f7e851eaff07ccf26001623_img.jpg)
+
+```
+sequenceDiagram
+ participant SRNC
+ participant CRNC
+ Note right of SRNC: [RNSAP] MBMS DETACH REQUEST
+ SRNC->>CRNC: [RNSAP] MBMS DETACH REQUEST
+ Note left of CRNC: [RNSAP] MBMS DETACH RESPONSE
+ CRNC->>SRNC: [RNSAP] MBMS DETACH RESPONSE
+```
+
+Sequence diagram for MBMS detach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS DETACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS DETACH RESPONSE' message to the SRNC.
+
+**Figure 8.2.11-2: MBMS detach request signalling flow: Successful Operation.**
+
+This signalling flow is only applicable for handling UEs in RRC connected mode with activated MBMS Services.
+
+The purpose of this signalling flow is
+
+- to either allow the CRNC to decrease the total number of UEs receiving one or several MBMS service in a given cell. The MBMS DETACH REQUEST contains the Cell Id of the old cell (may contain the URA Id of the old URA for UEs in URA\_PCH state), the whole list of affected MBMS Service Ids and a UTRAN specific UE Identification if necessary.
+- or to allow the SRNC to inform the DRNC in which URA there is not anymore a need to send notifications for MBMS Services due to the presence of UEs in URA\_PCH. The MBMS DETACH REQUEST then contains a list of URAs and the corresponding MBMS Services
+
+### 8.2.12 MBMS Channel Type Reconfiguration over Iur
+
+These signalling flows need further study.
+
+
+
+```
+
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: [RNSAP] MBMS CHANNEL TYPE RECONFIGURAITON INDICATION
+ DRNC->>SRNC: [RNSAP] MBMS CHANNEL TYPE RECONFIGURAITON INDICATION
+ Note left of SRNC: [RNSAP] MBMS CHANNEL TYPE RECONFIGURATION CONFIRMATION
+ SRNC->>DRNC: [RNSAP] MBMS CHANNEL TYPE RECONFIGURATION CONFIRMATION
+
+```
+
+Sequence diagram showing Channel Type Reconfiguration signalling flow between DRNC and SRNC.
+
+**Figure 8.2.12: Channel Type Reconfiguration signalling flow: Successful Operation.**
+
+This signalling flow is only applicable for handling MBMS UEs in RRC connected mode.
+
+The purpose of this signalling flow is that the CRNC informs the selected channel type to the SRNCs used in a cell under the CRNC. The MBMS CHANNEL TYPE RECONFIGURATION INDICATION contains a list of U-RNTI, Channel type and MBMS Service Id corresponding to the UEs connected to the SRNC.
+
+### 8.2.13 Information Exchange over Iur
+
+These signalling flows is used by the DRNC to acquire the MBMS related information for MBMS service identified by TMGI and is used between the RNCs, which are controlling cells neighbouring to each other for selective/soft combining in case of inter-RNC synchronization.
+
+
+
+```
+
+sequenceDiagram
+ participant DRNC/RNC1
+ participant SRNC/RNC2
+ Note right of DRNC/RNC1: [RNSAP] INFORMATION EXCHANGE INITIATION REQUEST
+ DRNC/RNC1->>SRNC/RNC2: [RNSAP] INFORMATION EXCHANGE INITIATION REQUEST
+ Note left of SRNC/RNC2: [RNSAP] INFORMATION EXCHANGE INITIATION RESPONSE
+ SRNC/RNC2->>DRNC/RNC1: [RNSAP] INFORMATION EXCHANGE INITIATION RESPONSE
+ Note right of SRNC/RNC2: Transmission Mode Change
+ SRNC/RNC2->>DRNC/RNC1: [RNSAP] INFORMATION REPORT
+
+```
+
+Sequence diagram showing Information Exchange Initiation signalling flow between DRNC/RNC1 and SRNC/RNC2.
+
+**Figure 8.2.13: Information Exchange Initiation signalling flow: Successful Operation.**
+
+The purpose of this signalling flow is that the DRNC request the APN and IP multicast address for an MBMS service. The INFORMATION EXCHANGE INITIATION REQUEST includes the TMGI for which the APN and IP multicast address are requested. In the INFORMATION EXCHANGE INITIATION RESPONSE message, the corresponding APN and IP multicast address are included.
+
+If the Information Exchange procedure is started and the transmission mode is changed, this shall be reported by the INFORMATION REPORT message.
+
+And the additional purpose of this signalling flow used in case of inter-RNC synchronization is
+
+- to request the external neighbouring RNC(s) to provide the counting results in cells the neighbouring RNC controls
+- to request the external neighbouring RNC(s) to inform about the transmission mode change in cells the neighbouring RNC controls for a MBMS session
+
+- to request the external neighbouring RNC(s) to provide the MBMS PTM RB configuration used in cells the neighbouring RNC controls
+- to request the external neighbouring RNC(s) to provide the RLC Sequence Number.
+
+### 8.2.14 MBMS RAB Establishment Indication
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note right of RNC: [RANAP] MBMS RAB ESTABLISHMENT INDICATION
+ RNC->>CN: [RANAP] MBMS RAB ESTABLISHMENT INDICATION
+```
+
+The diagram shows a sequence of two vertical lifelines labeled 'RNC' and 'CN'. A single horizontal arrow points from the RNC lifeline to the CN lifeline. Above the arrow, the text '[RANAP] MBMS RAB ESTABLISHMENT INDICATION' is displayed.
+
+Sequence diagram for MBMS RAB Establishment Indication procedure
+
+**Figure 8.2.14: MBMS RAB Establishment Indication procedure**
+
+This signalling flow is used by the RNC to indicate to the CN the establishment of the MBMS RAB corresponding to the MBMS Iu signalling connection.
+
+When the RNC decides not to establish an MBMS Iu bearer, for a particular MBMS service, during MBMS Session Start procedure, for example the RNC does not control any contained in MBMS Service Area Information and the RNC does not belong to any of the RA in a list of RAs which lists each RA that contains at least one PMM-IDLE UE but later when a UE linking (via Iu or Iur) is performed or as a result (p-t-p decision) of channel type reconfiguration in another RNC, the RNC establishes the Iu bearer and uses this procedure to inform the CN that an Iu bearer has been established.
+
+If Iu-Flex is active, the selection of the CN node is implementation dependant.
+
+The MBMS RAB ESTABLISHMENT INDICATION message contains the *Transport Layer Address* IE and the *Iu Transport Association* IE.
+
+### 8.2.15 MBMS RAB Release
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note right of RNC: [RANAP] MBMS RAB RELEASE REQUEST
+ RNC->>CN: [RANAP] MBMS RAB RELEASE REQUEST
+ Note right of CN: [RANAP] MBMS RAB RELEASE
+ CN->>RNC: [RANAP] MBMS RAB RELEASE
+```
+
+The diagram shows a sequence of two vertical lifelines labeled 'RNC' and 'CN'. Two horizontal arrows are shown. The first arrow points from the RNC lifeline to the CN lifeline, with the text '[RANAP] MBMS RAB RELEASE REQUEST' above it. The second arrow points from the CN lifeline back to the RNC lifeline, with the text '[RANAP] MBMS RAB RELEASE' above it.
+
+Sequence diagram for MBMS RAB Release Request procedure
+
+**Figure 8.2.15: MBMS RAB Release Request procedure.**
+
+This signalling flow is used by the RNC to indicate to the CN to request the release of an MBMS RAB.
+
+At reception of the MBMS RAB RELEASE REQUEST message the CN should initiate the release of all MBMS resources related to the Iu connection without releasing the Iu signalling connection.
+
+The RNC shall at reception of MBMS RAB RELEASE initiate the release of the related MBMS RAB resources.
+
+The MBMS RAB release may be initiated e.g. for the following reasons (unexhausted):
+
+- There are lack of radio resource in UTRAN and RNC decided to pre-empt an MBMS RAB for a on-going MBMS session based on Allocation/Retention Priority
+- When there are no UEs with a given activated MBMS service consuming radio resources in cells under the RNC or the RNC is controlling UEs in cells under another RNC;
+- In case of channel type switching from ptp to ptm in cells under control of another RNC in its role of DRNC;
+- There are no cells under the RNC which are part of the RA List Of Idle UEs if received.
+
+### 8.2.16 MBMS Session Start procedure in case of IP Multicast transport
+
+![Sequence diagram for MBMS Session Start procedure between RNC and CN. CN sends [RANAP] MBMS SESSION START REQUEST to RNC. RNC performs an IGMP JOIN. RNC sends [RANAP] MBMS SESSION START RESPONSE to CN.](adc59ed6840bcb2d392ea323abfccedc_img.jpg)
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ CN->>RNC: [RANAP] MBMS SESSION START REQUEST
+ Note left of RNC: IGMP JOIN
+ RNC->>CN: [RANAP] MBMS SESSION START RESPONSE
+
+```
+
+Sequence diagram for MBMS Session Start procedure between RNC and CN. CN sends [RANAP] MBMS SESSION START REQUEST to RNC. RNC performs an IGMP JOIN. RNC sends [RANAP] MBMS SESSION START RESPONSE to CN.
+
+**Figure 8.2.16-1: MBMS Session Start procedure. Successful operation.**
+
+The MBMS Session Start procedure is initiated by the CN when an MBMS Session is started. The MBMS SESSION START REQUEST is sent to each RNC that is connected to the CN (in case of Iu-flex the RNC may receive more than one MBMS SESSION START REQUEST message).
+
+The MBMS SESSION START REQUEST contains the MBMS Service Id, and optionally the MBMS Session ID, MBMS Bearer Service Type, the MBMS Session Attributes (MBMS Service Area Information, QoS parameters, ...) and Transport Layer Address used for the IP-multicast and Iu Transport Association (DL TEID) IE. In addition in case PDCP is used for the MBMS service the PDCP information is included. It may also include a list of RAs which lists each RA that contains at least one PMM-IDLE UE that has activated the service.
+
+The RNC stores the session attributes in the MBMS Service Context, sets the state attribute of its MBMS Service Context to 'Active' and joins the IP Multicast group, which is used for the User data delivery of this MBMS session between the GGSN and RNCs in case radio resource is available. In case of successful joining the indicated IP Multicast group the RNC replies to the CN nodes from which it has received the MBMS Session Start Request message that the IP Multicast Bearer setup was successful and establishes the radio resource for the transfer of MBMS data to the interested UEs.
+
+### 8.2.17 MBSFN MCCH Information
+
+
+
+```
+
+sequenceDiagram
+ participant CRNC
+ participant MRNC
+ MRNC->>CRNC: MBSFN MCCH INFORMATION
+
+```
+
+Sequence diagram for MBSFN MCCH Information procedure. MRNC sends MBSFN MCCH INFORMATION message to CRNC.
+
+**Figure 8.2.17-1: MBSFN MCCH Information procedure, Successful Operation**
+
+The signalling flow shall be used only if MRNC is used for MBSFN operation.
+
+The MBSFN MCCH INFORMATION message contains the MCCH messages list sent on the MRNC and the MCCH configuration information of the MRNC.
+
+The signalling flow is used by the MRNC to inform the CRNC of the MCCH configuration and scheduling information used in MRNC upon receipt of MBMS SESSION START message from CN.
+
+The CRNC shall prepare the setup of the requested MBMS sessions upon receipt of MBMS SESSION START message from CN, then instead of preparing RRC messages and physical configuration, wait for the MBSFN MCCH INFORMATION message that is sent from MRNC.
+
+Upon receipt of the MBSFN MCCH INFORMATION message, if the *MCCH Configuration* IE exists, the CRNC shall setup or reconfigure the MCCH of all cells in the MBSFN cluster with the configuration contained in this IE, and update the System Information of these cells.
+
+The CRNC shall decode the *L3 Information* IE contained in the *MCCH Message List* IE and apply the RLC/MAC/PHY configuration specified by relative MCCH Message to setup the RB information of MTCH, and then send the *L3 Information* IE on the MCCH in the receiving sequence at the beginning of the first MCCH modification period following the CFN carried in the message.
+
+## 8.3 MBMS Uu Signalling Flows
+
+### 8.3.1 Broadcast of MBMS System Information
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC
+ Note right of CRNC: MBMS SYSTEM INFORMATION
+ CRNC->>UE: MBMS SYSTEM INFORMATION
+ Note left of UE:
+```
+
+The diagram illustrates a sequence of events between a User Equipment (UE) and a Control Radio Network Controller (CRNC). The UE is represented by a box on the left, and the CRNC by a box on the right. Vertical lines extend downwards from each box, representing their respective timelines. A horizontal arrow points from the CRNC's timeline to the UE's timeline, labeled 'MBMS SYSTEM INFORMATION'. This indicates a broadcast message sent from the CRNC to the UE.
+
+Sequence diagram showing the broadcast of MBMS system information from CRNC to UE.
+
+**Figure 8.3.1: Broadcast of MBMS system information.**
+
+This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and PMM-CONNECTED mode.
+
+The purpose of the signalling flow is for UTRAN to broadcast MBMS system information to UEs using the BCCH. The MBMS SYSTEM INFORMATION shall be repeatedly transmitted after its first transmission. Upon receiving the first MBMS SYSTEM INFORMATION, the UE shall establish the radio bearer carrying an MCCH.
+
+The MBMS SYSTEM INFORMATION includes:
+
+- MCCH schedule information (access info, repetition and modification periods)
+- Configuration of a radio bearer carrying an MCCH
+
+More information may be included in the MBMS SYSTEM INFORMATION.
+
+### 8.3.2 MBMS Service Information
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC
+ Note right of CRNC: MBMS SERVICE INFORMATION
+ CRNC->>UE: MBMS SERVICE INFORMATION
+```
+
+A sequence diagram illustrating the signalling flow for MBMS service information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS SERVICE INFORMATION' centered above the arrow.
+
+Sequence diagram showing MBMS service information signalling flow from CRNC to UE.
+
+**Figure 8.3.2: MBMS service information signalling flow**
+
+This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and PMM-CONNECTED mode.
+
+The purpose of the signalling flow is for RNC to inform UEs of all of MBMS services available in one cell. The MBMS SERVICE INFORMATION shall be transmitted periodically on MCCH to provide an indication of the status of the MBMS service in the cell and to support mobility.
+
+The MBMS SERVICE INFORMATION contains MBMS service ids, optionally the MBMS Session ID, and an indication of the service status in the cell i.e. whether it is provided by p-t-m or p-t-p bearers or whether explicit release is indicated. The MBMS service ids indicate the MBMS services which are being served in the cell or the MBMS services which can be served if the UE requests it. P-t-m indication indicates that the MBMS service is on p-t-m in the cell, thus it informs the UE of the need of reception of the MBMS RADIO BEARER INFORMATION.
+
+### 8.3.3 MBMS Radio Bearer Information
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC
+ Note right of CRNC: MBMS RADIO BEARER INFORMATION
+ CRNC->>UE: MBMS RADIO BEARER INFORMATION
+```
+
+A sequence diagram illustrating the signalling flow for MBMS radio bearer information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS RADIO BEARER INFORMATION' centered above the arrow.
+
+Sequence diagram showing MBMS radio bearer information signalling flow from CRNC to UE.
+
+**Figure 8.3.3: MBMS radio bearer information signalling flow**
+
+This signalling flow is applicable for handling MBMS to UEs in IDLE and PMM-CONNECTED mode.
+
+The purpose of the signalling flow is for the RNC to inform UE(s) regarding the MTCH radio bearer information. MBMS RADIO BEARER INFORMATION is only available for p-t-m transmission. MBMS RADIO BEARER INFORMATION shall be transmitted periodically on MCCH to support mobility in the MBMS service.
+
+MBMS RADIO BEARER INFORMATION includes MBMS Service Id, radio bearer, transport channel and physical channel information per MBMS service.
+
+### 8.3.4 MBMS Access Information
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC
+ CRNC->>UE: MBMS ACCESS INFORMATION
+```
+
+A sequence diagram illustrating the signalling flow for MBMS Access Information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS ACCESS INFORMATION' centered above it.
+
+Sequence diagram showing MBMS Access Information signalling flow from CRNC to UE.
+
+**Figure 8.3.4: MBMS Access Information signalling flow**
+
+This signalling flow is applicable for handling MBMS UEs in IDLE mode or URA\_PCH, CELL\_PCH, CELL\_FACH state.
+
+The purpose of the signalling flow is for the RNC to inform UE(s) with particular activated MBMS service of the potential need to make an MBMS Counting Response i.e. establish an RRC connection or make a cell update. The MBMS ACCESS INFORMATION is transmitted during counting and re-counting on MCCH. The MBMS ACCESS INFORMATION includes, for each service for which counting is required, the MBMS service identifier, probability factors for idle and connected modes and an indication of the connected mode states to which the signalling flow applies.
+
+### 8.3.5 MBMS Neighbouring Cell Information
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC
+ CRNC->>UE: MBMS NEIGHBOURING CELL INFORMATION
+```
+
+A sequence diagram illustrating the signalling flow for MBMS Neighbouring Cell Information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS NEIGHBOURING CELL INFORMATION' centered above it.
+
+Sequence diagram showing MBMS Neighbouring Cell Information signalling flow from CRNC to UE.
+
+**Figure 8.3.5: MBMS Neighbouring Cell Information signalling flow**
+
+This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and CONNECTED mode.
+
+The purpose of the MBMS NEIGHBOURING CELL INFORMATION signalling flow is for the UTRAN to inform to UEs of the MTCH configuration of the neighbouring cells which are available for selective combining. In case of partial soft combining, the MBMS NEIGHBOURING CELL INFORMATION contains the L1-combining schedule, which indicates when the soft combining is applicable between the specific S-CCPCH of the cell and the specific S-CCPCH of the neighbouring cell. With MBMS NEIGHBOURING CELL INFORMATION the UE is able to receive MTCH transmission from neighbouring cell without reception of the MCCH of that cell. The MBMS NEIGHBOURING CELL INFORMATION shall be repeatedly transmitted on MCCH when selective or soft combining is utilized in the MBMS p-t-m transmission in the given cell group.
+
+### 8.3.6 MBMS Joined Indication
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant SRNC
+ UE->>SRNC: MBMS JOINED INDICATION
+```
+
+A sequence diagram illustrating the signalling flow for MBMS Joined Indication. It features two vertical lifelines: 'UE' on the left and 'SRNC' on the right. A horizontal arrow points from the UE lifeline to the SRNC lifeline, with the text 'MBMS JOINED INDICATION' centered above it.
+
+Sequence diagram showing MBMS Joined Indication signalling flow from UE to SRNC.
+
+**Figure 8.3.6: MBMS joined indication signalling flow**
+
+This signalling flow is applicable for handling MBMS to UEs in RRC-Connected, PMM-IDLE state. The MBMS JOINED INDICATION is sent over the DCCH.
+
+The signalling flow is initiated by the UE after entering RRC-Connected, PMM-IDLE state. The purpose of the signalling flow is to enable the UE to inform the SRNC that the user has joined at least one MBMS service. The SRNC requests the MBMS services the UE has joined from the SGSN as defined in subclause 8.2.10.
+
+In SRNC relocation this information is transmitted from source RNC to target RNC.
+
+NOTE: If SRNC has valid linking information the complete service list of activated services is also transmitted from source RNC to target RNC in SRNC relocation.
+
+### 8.3.7 MTCH Scheduling Information
+
+
+
+A sequence diagram illustrating the MTCH Scheduling Information flow. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MTCH SCHEDULING INFORMATION' centered above the arrow.
+
+Sequence diagram showing MTCH Scheduling Information flow from CRNC to UE.
+
+**Figure 8.3.7: MTCH scheduling information.**
+
+This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and CONNECTED mode.
+
+The purpose of the signalling flow is to enable UEs to perform discontinuous reception of MTCH. The UE may discontinuously receive MTCH based on scheduling information indicated by the MTCH SCHEDULING INFORMATION. This signalling is transmitted on MSCH mapped on SCCPCH carrying MTCH. The MTCH SCHEDULING INFORMATION is signalled on each MSCH repetition period. The MSCH repetition period and the offset from the cell timing are indicated on MCCH. In case of soft combining, the MSCH repetition period is same for all soft combinable S-CCPCH. The scheduling information allows to cover different periods for different MBMS services.
+
+The MTCH SCHEDULING INFORMATION includes for each service:
+
+- MBMS service Id (the actual coding is defined in stage-3).
+- Beginning and duration of MBMS data transmission (one contiguous block or more is defined in Stage-3).
+- Duration can be infinite (no DTX). This option could be signalled in the MCCH (Stage-3 definition).
+- Indication of no MBMS data transmission for either this period or several consecutive periods (a period is expressed in MSCH repetition period).
+
+### 8.3.8 MBMS Change Information
+
+
+
+A sequence diagram illustrating the MBMS Change Information flow. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS CHANGE INFORMATION' centered above the arrow.
+
+Sequence diagram showing MBMS Change Information flow from CRNC to UE.
+
+**Figure 8.3.8: MBMS change information.**
+
+This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and CONNECTED mode. UTRAN should transmit this signalling flow in beginning of each modification period on MCCH and repeat it at least in every repetition period of that modification period. UE shall read this information flow when detecting that MICH bits set for a service that UE has activated, or periodically at the begin of each modification period when receiving MTCH.
+
+The purpose of the signalling flow is to indicate MBMS services whose MCCH information is changed in that modification period. The content of MBMS CHANGE INFORMATION shall be minimized, so that the MCCH reading time for the UEs, activated MBMS service whose MCCH information is not modified on that modification period, is minimized.
+
+The MBMS CHANGE INFORMATION includes:
+
+- The MBMS service Ids for which MCCH information is modified on that modification period.
+
+### 8.3.9 MBMS P-T-P Modification Request
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant SRNC
+ Note right of UE: MBMS P-T-P Modification Request
+ UE->>SRNC: MBMS P-T-P Modification Request
+```
+
+Sequence diagram for MBMS P-T-P Modification Request. A UE sends an MBMS P-T-P Modification Request message to an SRNC.
+
+Figure 8.3.9: MBMS P-T-P Modification Request.
+
+This signalling flow is applicable for handling UEs with an activated service that requires MBMS p-t-p RB in PMM IDLE and CONNECTED mode. In idle mode, URA\_PCH and CELL\_PCH states the UE may transmit this signalling flow to request the setup of a p-t-p MBMS RB after receiving the indication on MCCH that p-t-p transfer mode is utilised or, in CELL\_DCH state, to request the release of the p-t-p MBMS RB due to higher priority MBMS service, or to indicate the frequency used for transmitting the higher priority service as specified in subclause 5.2.8. This signalling flow is transmitted on DCCH or on CCCH dependent upon UE state.
+
+UEs in idle mode are required to perform RRC connection establishment for sending this information flow. UEs that are in URA\_PCH or CELL\_PCH state are required to make a cell update and UEs that are in CELL\_DCH state transmit an MBMS MODIFICATION REQUEST message.
+
+When UTRAN receives this message from the UE, the UTRAN may setup or release the p-t-p MBMS RB by normal RB release procedure or , in the case of a preferred frequency being indicated, it may perform inter-frequency HHO.
+
+The MBMS P-T-P Modification Request message includes the identity of the MBMS service when the service appears in the list of MBMS Selected Services.
+
+### 8.3.10 MBMS Counting Response
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC
+ Note right of UE: MBMS Counting Response
+ UE->>CRNC: MBMS Counting Response
+```
+
+Sequence diagram for MBMS Counting Response. A UE sends an MBMS Counting Response message to a CRNC.
+
+Figure 8.3.10: MBMS Counting Response.
+
+This signalling flow is applicable for UEs passing the probability check in counting procedure in idle mode or URA\_PCH, CELL\_PCH or CELL\_FACH state. For the UE in idle mode this signalling flow refers to the complete RRC connection establishment procedure. For UEs in URA\_PCH, CELL\_PCH and CELL\_FACH state this signalling flow refers to cell update procedure.
+
+The MBMS Counting Response message includes the identity of the MBMS service when the service appears in the list of MBMS Selected Services.
+
+### 8.3.11 MBMS Selected Services Information
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant CRNC/SRNC
+ Note right of UE: MBMS Selected Services Information
+ UE->>CRNC/SRNC:
+ Note left of CRNC/SRNC:
+```
+
+The diagram illustrates a sequence of messages between a User Equipment (UE) and a CRNC/SRNC. The UE is on the left and the CRNC/SRNC is on the right. A horizontal arrow points from the UE to the CRNC/SRNC, labeled "MBMS Selected Services Information".
+
+Sequence diagram showing MBMS Selected Services Information flow from UE to CRNC/SRNC.
+
+**Figure 8.3.11: MBMS Selected Services Information.**
+
+This signalling flow is applicable for UEs entering CELL\_DCH state. The purpose of the signalling flow is to enable the UE to inform the SRNC that the user requires the reception of MBMS Selected Services. When the SRNC is not the CRNC of the UE, this signalling flow may interact with the URA linking/de-linking described in subclause 5.1.10.
+
+This signalling flow is also applicable for UEs in CELL\_DCH states, when the list of MBMS Selected Services has been modified.
+
+This signalling flow is also applicable for UEs in CELL\_PCH, URA\_PCH and CELL\_FACH states when the list of MBMS Selected Services has been modified by the upper layers and the MBMS Service appears in the MCCH of the cell and the RNC has indicated in the MBMS GENERAL INFORMATION message that it should be notified of a change to this list. If an MBMS Service is contained in the list of MBMS Selected Services but is currently not available in the cell, when the service appears on the MCCH the UE does not perform this signalling flow.
+
+The purpose of the signalling flow is to enable the UE to inform the CRNC that the list of MBMS Selected Services in the UE has been modified.
+
+# --- 9 Security for MBMS
+
+Ciphering for MBMS multicast data is done between the BM-SC and the UE as defined in [7]. Therefore, for MBMS p-t-m data transmissions no radio interface ciphering is applied.
+
+In case of p-t-p MBMS data transmissions, if the security is activated for the UE the ciphering is also applied for p-t-p MBMS data RB as for any other RB of the UE.
+
+# --- 10 Mobility Procedures for MBMS
+
+One of the requirements in [5] is: "Data loss during cell change should be minimal". Therefore, when the UE receiving an MBMS session in idle mode or connected mode (not including CELL\_DCH) re-selects between cells, it should be possible to provide service continuity to this UE.
+
+The following mechanism has been identified to minimise the data loss on cell change.
+
+## 10.1 Use of Periodical Transmission of MBMS Critical Information
+
+In this mechanism, the cell periodically transmits an MBMS critical information, informing all MBMS services currently configured for p-t-m transmission or p-t-p transmission. If MBMS service is configured for p-t-m transmission, the periodical transmission of MBMS critical information may also contain the Radio Bearer information corresponding to each MBMS service and Neighbouring cell information.
+
+If the cell is configured for p-t-p transmission, then the UE would perform a normal RRC connection establishment.
+
+## 10.2 UE Actions for Mobility
+
+The UE mobility between intra frequency cells is not affected by the MBMS reception. The mobility between different frequency layers is affected by the Frequency Layer Convergence process as defined in 11.2, if used by the network.
+
+In CELL\_FACH and in CELL\_DCH state the RRC operation has priority over MBMS reception, thus UE performs the inter frequency and inter RAT measurements as configured by the SRNC. UTRAN should utilize different periodicities between MCCH transmissions and CELL\_FACH state measurement occasion, such that CELL\_FACH state measurements and MCCH transmissions are not constantly overlapping for some UE.
+
+In Idle mode and in CELL\_PCH, URA\_PCH states the measurements are performed as configured by the network based on the Release 5. The MBMS specific measurement occasions to S-CCPCH for UEs in idle mode and in CELL\_PCH, URA\_PCH states are not introduced and measurements have priority over MBMS reception. The usage of channel protection (channel coding) to recover some of the lost transport blocks is possible.
+
+UEs may have DRx occasions for specific MBMS service when UE can stop decoding S-CCPCH and perform measurements. DRx occasion are based on scheduling information.
+
+R'99 standards have some means to reduce need for number of measurements, which can be utilized for MBMS.
+
+When the UE reselects the cell due to the mobility or returns to on service from out of service, the UE shall acquire the MCCH information if the activated MBMS service is available in the selected cell for the reception of the service. The service is available when the session has been already started and the service is being served on p-t-p/p-t-m in the cell, or the service can be served in the cell if the UE requests it.
+
+If the MBMS service is available in the cell, the UE will perform an action for the service reception in the cell. For example, if the service is on p-t-p, the idle mode UE will initiate RRC connection establishment procedure. Otherwise, the UE does not need to perform such an action in the cell. The UE, which moves to the new cell, will operate according to the RRC state/mode as follows.
+
+Whenever the UE moves between p-t-m cells while continuing to receive a service, UE shall receive MCCH information in a new cell, which includes an MBMS cell group identity. If a UE moves between cells belong to the same MBMS cell group based on the MCCH information, the UE does not need to re- establish RLC entity and re-initialise PDCP entity for the service received on MTCH. If a UE moves between cells belong to different MBMS cell groups based on the MCCH information, the UE shall re- establish RLC entity and re- initialise PDCP entity for the service received on MTCH.
+
+### 10.2.1 RRC idle mode
+
+Idle mode UE shall:
+
+- if BCCH contains information regarding the MCCH in the new cell:
+ - listen to the MCCH and receive the MBMS SERVICE INFORMATION;
+ - if the MBMS SERVICE INFORMATION contains the activated MBMS service-id:
+ - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m:
+ - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH;
+ - else:
+ - initiate RRC connection establishment procedure and request the setup of MBMS p-t-p RB;
+ - if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and;
+ - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id:
+ - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION.
+
+### 10.2.2 URA\_PCH State
+
+URA\_PCH state UE shall:
+
+- perform URA update procedure if needed;
+- if BCCH contains information regarding the MCCH in the new cell:
+ - listen to the MCCH and receive the MBMS SERVICE INFORMATION;
+
+- if MBMS SERVICE INFORMATION contains the activated MBMS service id:
+ - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m:
+ - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH;
+ - else:
+ - initiate cell update procedure and request to setup the MBMS p-t-p RB;
+- if the UE receive the MBMS RADIO BEARER INFORMATION before MBMS SERVICE INFORMATION message and;
+ - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id:
+ - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION.
+
+### 10.2.3 CELL\_PCH
+
+CELL\_PCH state UE shall:
+
+- perform cell update procedure;
+- if BCCH contains information regarding the MCCH in the new cell:
+ - listen to the MCCH and receive the MBMS SERVICE INFORMATION;
+- if MBMS SERVICE INFORMATION contains the activated MBMS service id and:
+ - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m:
+ - receive the MBMS RADIO BEARER INFORMATION message and listen to the MTCH.
+ - else:
+ - initiate the cell update procedure and request to setup the MBMS p-t-p RB.
+- if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and;
+ - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id:
+ - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION.
+
+### 10.2.4 CELL\_FACH
+
+CELL\_FACH state UE shall:
+
+- perform cell update procedure
+- if BCCH contains information regarding the MCCH in the new cell:
+ - listen to the MCCH and receive the MBMS SERVICE INFORMATION;
+- if MBMS SERVICE INFORMATION contains the activated MBMS service id and:
+ - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m:
+ - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH;
+ - else:
+ - initiate request to setup the MBMS p-t-p RB;
+- if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and;
+ - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id:
+
+- listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION.
+
+### 10.2.5 CELL\_DCH State
+
+CELL\_DCH state UE shall:
+
+- act on the RRC message received on DCCH in handover.
+- if the UE has the capability to support MBMS in CELL\_DCH:
+ - if BCCH contains information regarding the MCCH in the new cell:
+ - listen to the MCCH and receive the MBMS SERVICE INFORMATION;
+ - if MBMS SERVICE INFORMATION contains the activated MBMS service id and;
+ - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m:
+ - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH.
+ - if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and;
+ - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id:
+ - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION.
+
+# --- 11 Resource Management for MBMS
+
+## 11.1 MBMS Access Control Procedure
+
+MCCH messages initiating counting or recounting cause multiple responses from UEs within a cell. This may result in RACH congestion if number of UEs is high in a cell. To avoid this, CRNC may perform MBMS access control procedure during counting or recounting procedure. MBMS access control procedure is described in Figure 11.1.
+
+
+
+```
+
+sequenceDiagram
+ participant UEs
+ participant CRNC
+ Note right of CRNC: 1. Setting of the initial probability factor
+ CRNC->>UEs: 2. Signaling the initial probability factor
+ Note left of UEs: 3. UE in Idle mode request RRC connection based on the initial probability factor 1
+UE in URA/CELL_PCH or CELL_FACH state response counting based on the initial probability factor 2
+ Note right of CRNC: 4. Detecting the needs for updating
+ Note right of CRNC: 5. Updating to the optimum probability factor
+ CRNC->>UEs: 6. Signaling the updated probability factor
+ Note left of UEs: 7. UE in Idle mode request RRC connection based on the updated probability factor 1
+UE in URA/CELL_PCH or CELL_FACH state response counting based on the updated probability factor 2
+
+```
+
+The diagram illustrates the MBMS Access Control Procedure. It starts with the CRNC (right) performing step 1: 'Setting of the initial probability factor'. It then signals this to the UEs (left) in step 2: 'Signaling the initial probability factor'. The UEs perform step 3: 'UE in Idle mode request RRC connection based on the initial probability factor 1' and 'UE in URA/CELL\_PCH or CELL\_FACH state response counting based on the initial probability factor 2'. The CRNC then performs step 4: 'Detecting the needs for updating' and step 5: 'Updating to the optimum probability factor'. It signals the updated factor to the UEs in step 6: 'Signaling the updated probability factor'. Finally, the UEs perform step 7: 'UE in Idle mode request RRC connection based on the updated probability factor 1' and 'UE in URA/CELL\_PCH or CELL\_FACH state response counting based on the updated probability factor 2'.
+
+Sequence diagram of MBMS Access Control Procedure between UEs and CRNC.
+
+**Figure 11.1: MBMS Access Control Procedure**
+
+1. CRNC calculates an initial probability factor for an MBMS service when a MCCH message causing counting or recounting is about to be sent. CRNC can use different probability factor for UEs in Idle mode and for different UEs in URA\_PCH, CELL\_PCH and CELL\_FACH.
+2. CRNC includes the probability factor into the MCCH message and sends it to UEs. This can be done in MBMS Group Notification.
+3. UEs in idle mode or in URA\_PCH, CELL\_PCH and CELL\_FACH state passing the probability check performs counting response UEs keep listening to MCCH to get updated probability factor until they have successfully responded to counting or counting is no longer required.
+4. CRNC detects the probability factor needs to be updated. Detecting mechanism is not to be standardized.
+5. CRNC recalculates the probability factor. The way of calculating new probability factor is not to be standardized.
+6. CRNC includes the updated probability factor into the MCCH message and sends it to UEs.
+7. UEs in idle mode or in URA\_PCH, CELL\_PCH or CELL\_FACH state that pass the probability check, by using updated probability factor, perform counting response.
+
+CRNC and UEs that are still trying to perform the counting response repeat step 3 ~ step 7 until e.g. counting or recounting procedure ends.
+
+## 11.2 Frequency layer Convergence
+
+Frequency Layer Convergence (FLC) denotes the process where the UTRAN requests UEs to preferentially re-select to the frequency layer on which the MBMS service is intended to be transmitted. This layer preference could be done by
+
+an additional MBMS session related Layer Convergence Information (LCI) such as offset and target frequency. The FLC is supported by specifications for both networks utilizing HCS and for networks not utilizing HCS.
+
+The preferred layer (PL) is indicated per MBMS service and the LCI (offset) is the same for all MBMS services on a given preferred layer. UTRAN can consist of multiple preferred layers and the PL for given services is decided by RRM. Thus the PL for an MBMS service might be different in different parts of the service area. Network co-ordination between RNCs may be added for the Rel-7. The CN may also request the RNC (e.g. using “no-FLC-flag” value) not to apply any frequency layer convergence mechanisms for the MBMS service (e.g. emergency service). In case no PL info is specified for the MBMS service, the UE may assume that the MBMS service is available on all frequencies.
+
+The LCI can be signalled to UEs by the CRNC after the session start is received over Iu interface until reception of the session stop. The UEs shall take LCI into account whenever it is signalled on the MCCH in Idle mode and URA\_PCH, CELL\_PCH and in CELL\_FACH states. The FLC is not applicable in CELL\_DCH state, as it is only effecting UEs cell re-selection procedure.
+
+The UE shall ignore Sintersearch parameter only for the potential preferred layers when LCI is signalled and on preferred layer the UE shall apply the Sintersearch parameter. In case of UE is in CELL\_FACH state without measurement occasions, the UE may not be able to measure cells on preferred layers.
+
+In the case that the UE has joined multiple services and they have different frequencies as preferred layer, the UE should apply the FLC applicable for the highest priority MBMS service, which it has activated and has a PL. The priority setting of different MBMS services is decided by NAS.
+
+Based on RRM decision, a given MBMS service can be provided on non-preferred layer by p-t-p or p-t-m transfer mode.
+
+The details of the mechanism are defined in state 3.
+
+## 11.3 Frequency layer Dispersion
+
+Frequency Layer Dispersion (FLD) denotes the process where the UTRAN redistributes UEs across the frequencies. UTRAN can use FLD per MBMS session.
+
+For FDD, the FLD is applicable in Idle mode, URA\_PCH, CELL\_PCH and CELL\_FACH states.
+
+For TDD, the FLD is applicable in Idle mode, URA\_PCH and CELL\_PCH states.
+
+When FLC is applied, the UE stores the frequency where it was camped previously. Upon session stop or service deactivation, the UE attempts to return to that frequency.
+
+If the UE does not find a suitable cell on the target frequency, the UE attempts to select a cell on a randomly chosen frequency.
+
+Dispersion applies when the MBMS session on the MBMS preferred frequency ends, or when the MBMS service on the MBMS preferred frequency is deactivated by the UE. Dispersion does not apply in the case where the UE decides to receive another service for which FLC is applied.
+
+The details of the mechanism are defined in the stage 3.
+
+# Annex A (informative): MBMS Phases in UTRAN
+
+
+
+The diagram shows the following timeline elements:
+
+- UE1 events:** Subscription to service1 (black dot), User service join (green dot), service leave (red X).
+- UE2 events:** subscription to service1 (black dot), service leave (red X).
+- Service 1 events:** Start Service 1 announcement (blue dot), 1st Session start (green dot), Idle period of seconds (dashed green line), Data transfer (green double-headed arrows), 1st session stop (red dot), Service 1 Session 2 (green double-headed arrow), Stop Service 1 announcement (blue dot).
+- Transfer of data:** Announcement (blue bar), Data sent to UE1 (green bar), Data sent to UE1 and UE2 (green bar), Data sent to UE1 and UE2 (green bar), Data sent to UE2 (green bar).
+- MBMS phase in UTRAN:** Phase 1 (black line), Phase 2 (green line), Phase 3 (green line), Phase 1 (black line), Phase 2 (green line), Phase 3 (green line), Phase 1 (black line).
+
+Callouts indicate that subscription and service join can occur at any time. RB setup is shown between Phase 1 and Phase 2.
+
+Figure A: Timeline of MBMS Service. This diagram illustrates the timeline of an MBMS service across five horizontal axes: UE1 events, UE2 events, Service 1 events, Transfer of data, and MBMS phase in UTRAN. UE1 and UE2 events show subscription, service join, and service leave actions. Service 1 events show session start, idle periods, data transfers, and session stops. Transfer of data shows announcements and data sent to specific UEs. The MBMS phase in UTRAN is divided into Phase 1 (idle), Phase 2 (setup), and Phase 3 (data transfer).
+
+**Figure A: Timeline of MBMS Service**
+
+The UTRAN MBMS behavior is divided into 3 phases. Figure A illustrates the timeline of an MBMS service with regards to these phases.
+
+## A1 Security for MBMS
+
+A cell stays in phase 1, if there is no ongoing session for the MBMS service, or if it does not belong to the MBMS service area of the service.
+
+A UE that has joined an MBMS service may regularly try to receive MBMS notification in a cell [FFS]. At this phase the UE does not request service delivery to UTRAN.
+
+## A2 MBMS Phase 2
+
+This phase starts when UTRAN receives the MBMS "session start" from CN, and ends when UTRAN initially sets up MBMS radio bearer for the session, or decides not to set up the MBMS radio bearer in a cell.
+
+In this phase, UTRAN transmits notification to UEs about the incoming service and could perform counting procedure to decide the type of MBMS radio bearer. UTRAN decides whether to set up p-t-m, p-t-p radio bearer or no radio bearer, based on the number of UEs that expected to receive the service in the cell. A UE that has at least one activated MBMS service acts on an RRC message in MCCH.
+
+## A3 MBMS Phase 3
+
+This phase starts after initial MBMS radio bearer setup and ends when UTRAN receives the MBMS "session stop" from CN.
+
+In this phase, UTRAN transmits the data for the MBMS service received from CN using, if any, the established radio bearer. If there is no set-up radio bearer, UTRAN waits for service delivery request from UE. Recounting and radio bearer reconfiguration may be performed during this phase.
+
+UTRAN behaviour in this phase can be divided into three states: no transmission, p-t-p transmission, and p-t-m transmission. Each cell belonging to the same MBMS service area may be in any of three states. With the variation of the number of UEs, the state of a cell may change between the three states. UTRAN may broadcast the state of each cell.
+
+- 1) **No Transmission:** In this state of a cell, there is no established radio bearer because there is no UE who wants to receive the service. An MBMS-joined (or MBMS-interested in broadcast mode) UE in idle mode that moves into the cell of this state requests service delivery to UTRAN.
+- 2) **P-t-p Transmission:** In this state of a cell, p-t-p radio bearer is established. A UE that has joined (or interested in broadcast mode) an MBMS service may receive MBMS data over p-t-p radio bearer if there is MBMS data to receive.
+- 3) **P-t-m Transmission:** In this state of a cell, p-t-m radio bearer is established. A UE that has joined (or interested in broadcast mode) an MBMS service may receive MBMS data over p-t-m radio bearer if there is MBMS data to receive.
+
+## A4 MBMS Phases and Status Parameters
+
+Table 1 lists the MBMS parameters that need to be broadcast in each MBMS phase. The list is [FFS]
+
+**Table 1: MBMS Status Parameters**
+
+| | Phase 1 | Phase 2 | Phase 3 | Description |
+|--------------------|---------|------------|----------------------|-----------------------------------------|
+| Service ID | X | O | O | Identity of the Service |
+| Transmission State | X | X | O (NONE/p-t-p/p-t-m) | State of the cell for MBMS transmission |
+| Counting | X | O (On/Off) | O (On/Off) | Whether counting procedure is going on. |
+
+- 1) **Service ID:** This parameter indicates the identity of the service concerned.
+- 2) **Transmission state:** This parameter indicates to UE(s) the state of the concerned cell while it is in phase 3. According to this parameter, UE entering the cell starts re-configuration of the radio bearer, or requests service delivery to UTRAN. Specifically, if this parameter is set to "p-t-m", UE receives service over p-t-m radio bearer and if set to "p-t-p", UE receives service over p-t-p radio bearer. If it is set to NONE, UE has to request UTRAN to deliver the service.
+- 3) **Counting:** The counting parameter informs UEs whether counting is required (and is going on) or not. If this parameter is set to "ON", UE should perform RRC connection procedure.
+
+# Annex B (informative): MBMS Control Information
+
+Tables 2 and 3 describe MBMS control information in the downlink and uplink.
+
+**Table 2: Mapping of MBMS Control Parameters in DL**
+
+| Information Element | Description |
+|----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MICH – Transmitted continuously – Can be modified at a modification period boundary | |
+| MBMS Notification Indicators | Indicates when new information is to be transmitted on MCCH in the next modification period. |
+| BCCH - Transmitted periodically | |
+| MCCH System Information | Includes:
- Configuration of the radio bearer carrying MCCH,
- MCCH schedule information (access info, repetition and modification periods). |
+| MCCH – Non Critical Information – Transmitted at access info events – Can be modified at any transmission | |
+| MBMS Access Information | Contains parameters that control, for the purposes of counting, whether UEs should establish an RRC connection (idle mode) or make a cell update (URA_PCH state). It may include for each service for which counting is in progress:
- MBMS service identity,
- Probability factor (Idle mode),
- Probability factor (URA_PCH),
Additional parameters may be identified in stage 3. |
+| MCCH – Critical Information – Transmitted at repetition period Events – Can be modified at a modification period boundary | |
+| MBMS Change Information | Identifies MBMS services for which parameters are modified in this modification period. It may include for each service listed:
- MBMS service identity,
- MBMS session identity.
Additional parameters may be identified in stage 3. In stage 3, MBMS Change Information is contained in the MBMS MODIFIED SERVICES INFORMATION message. |
+| MBMS Service Information | Identifies MBMS services that are available in the cell. It may include for each service listed:
- MBMS service identity,
- MBMS session identity,
- Indication that a p-t-m bearer is established for the service in the cell,
- RB release indication,
- Preferred frequency layer information.
Additional parameters may be identified in stage 3. In stage 3, MBMS Services Information for a service is contained in either the MBMS MODIFIED SERVICES INFORMATION or the MBMS UNMODIFIED SERVICES INFORMATION messages depending upon the change status of the service. |
+| MBMS Radio Bearer Information | Contains, for one or more MBMS services information describing the radio bearer and the p-t-m bearer that is used within the serving cell. It may include for each service listed:
- MBMS service identity,
- MBMS cell group identity,
- Physical channel information,
- Transport channel information,
- Radio Bearer information.
Additional parameters may be identified in stage 3. |
+
+| | |
+|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MBMS Neighbouring Cell Information | Contains, for one or more MBMS services transmitted in neighbour cells that can be used for soft or selective combining, information describing the p-t-m bearer to which it is mapped in the neighbour cell. It may include for each service listed: - - MBMS service identity,
- - Cell identification information,
- - Physical channel information,
- - Transport channel information,
- - Radio Bearer information,
- - L1 scheduling information,
- - Soft/ selective combining information.
Additional parameters may be identified in stage 3. |
+| MSCH – Transmitted periodically | |
+| MTCH Scheduling Information | Contains information that enables UEs to perform discontinuous reception of MTCH. It may include for each of one or more services: - - MBMS service identity,
- - The start time and duration of a period of data transmission,
- - Indication that there is no data transmission for one or more MSCH repetition periods.
|
+
+**Table 3: Mapping of MBMS Control Parameters in UL**
+
+| Information Element | Description |
+|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| DCCH - Service Related Control Information | |
+| MBMS Joined Indication | Indicates that a PMM IDLE state UE in RRC connected mode has joined at least one MBMS service |
+| MBMS P-T-P Modification Request | UEs in CELL_DCH state may transmit this signalling flow to request the release of a p-t-p MBMS RB for a higher priority MBMS service. |
+
+# Annex C (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|--------------------|-------------------------------------|----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 8/02 | RAN2#31 | R2-021846 | | | | | 0.0.1 |
+| 9/02 | RAN2#32 | R2-020590 | | | Skeleton Endorsed with some changes in sections from RAN2#31 | 0.0.1 | 1.0.0 |
+| 11/02 | RAN2#33 | R2-022927 | | | No MBMS Discussions | | |
+| 1/03 | RAN2/3 MBMS AdHoc | R2-030006 | | | R2-022644 and R2-022699 | 1.0.0 | 1.1.0 |
+| 2/03 | RAN2#34 | R2-030122 | | | Inclusion of R2-030010, R2-030050, figure from R2-030015, mechanism 1 from R2-030062, + editorial changes + principles in section 5.1.3 | 1.1.0 | 1.4.0 |
+| 4/03 | RAN2#35 | R2-030707 | | | Inclusion of R2-030010 + section 5.1.4 based on agreed bullet points from RAN2#34 + correction of version numbering + addition of "change history" section. | 1.4.0 | 1.5.0 |
+| 5/03 | RAN2/3AdHoc | R2-030882 | | | -R2-030907 "Functional Description on MAC-c/sh/m".
-R2-030902 on the "MBMS Control Plane Protocol Stack".
-R2-030910 on MBMS UTRAN Phases in Annex A.
-R3-030584: only inclusion of sections: 7.1.3 and 7.1.4. In 7.1.3 there is one additional comment regarding the addition of "PMM" wherever CONNECTED mode" is mentioned.
-R3-030614: Addition of chapter 5.1.x
-R3-030615: changes in section 5.1.2.
-R3-030615: proposed section 5.1 was reworded. | 1.5.0 | 1.6.0 |
+| 5/03 | RAN2#36 | | | | - Inclusion of contribution R2-03930, sections: 7.2.1.1 and 7.2.1.2 from decisions from RAN2/3 MBMS adhoc.
- Use of term "MBMS service context" instead of "MBMS context" throughout the document.
- Correction of spelling mistake in figure 1: "Protocol Stack for MCTCH" should be: "Protocol Stack for MTCH".
- Revision of Appendix A "MBMS Phase 1": Part of the second paragraph has been deleted due to concerns from RAN3.
- During the RAN2 MBMS AdHoc it was decided that MCCH and MTCH are to be mapped on FACH. This decision is captured at the bottom of 5.3.1 by adding the sentence "Both logical channels are mapped on FACH". FACH is also mentioned is several places in 5.3.2 (MAC Architecture) as an example (e.g. FACH). The "e.g." has now been deleted. | 1.6.0 | 1.6.1 |
+| 06/03 | TSG RAN #20 | | | | The version 2.0.0 identical to version 1.6.1 was presented in TSG RAN plenary meeting for information and approval. The TS was not approved so drafting work will continue in WG2/3 based on version 2.0.0.
The changes in version 2.1.0 compared to 2.0.0 are in Section 5.1.4 Counting where point 8 " The possibility for the RNC to receive the service Id in RRC connection request is [FFS]... " is removed. This reflects to the decision made in RAN2/3AdHoc 05/03 but was missing from earlier versions, and pointed out by RAN WG2 chairman in reflector and in TSG RAN #20. | 2.0.0 | 2.1.0 |
+| 09/03 | RAN2#37
RAN3#37 | R2-031713
R3-031174
R3-031223 | | | Editorial corrections based on R2-031713 included.
New chapter "7. MBMS reception UE Capability" created and agreed UE capability text inserted to the new chapter "7.1. UE Capability".
Modifications based on R3-031174 to the definitions
Sections 5.1.1, 5.1.5 and 5.1.6 enhanced and sections 5.1.7, 5.1.8 and 5.1.9 crated, and signalling flows updated in section 7.1.based on R3-031223 | 2.1.0 | 2.2.0 |
+
+| Change history | | | | | | | |
+|----------------|-------------|------------------------------------------------------------------------------------------------------------------|----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| | | | | | Following Editorial enhancements proposed by editor: Chapter 5.3.1.1 and 5.3.1.2 moved to under chapter 6.1. Logical channels and chapter "5.4 MBMS Reception in RRC States/Modes" moved under chapter 7. in new chapter "7.2 MBMS reception " | | |
+| 10/03 | RAN2#
38 | R2-032116
R2-032074
R2-032121
R2-032277
R2-032087
R2-032275
R2-032081
R2-032281 | | | Chapter 5.2.1 MBMS User Plane Protocol Stack Architecture enhanced accordingly.
Chapter 9 Security for MBMS enhanced accordingly
Chapter 8.2.2 MBMS service availability enhanced, (message changed to information). Chapter 9.2. UE Actions for Mobility created and 9.2.4 text depending UE capability inserted
Chapters 8.2.4. MBMS Joined Services Indication and 8.2.5 MBMS PMM-Connected State Required Indication created
Chapters 6.1. re-formatted, Section 6.2.1-6.2.5 created
The MBMS access control procedure inserted in chapter 11.1
Broadcast of MBMS System Information signalling flow added.
Tables inserted to an informative annex to identify MBMS control information and describe their mapping on transport channels | 2.2.0 | 2.3.0 |
+| | RAN3#
38 | R3-031421 | | | MBMS Time line and MBMS Service announcement definitions included in Section 3.1 Chapter 5.1.1 One Context per MBMS Service in CRNC and 5.1.8 RNC deregistration updated accordingly
Editorial harmonization of terms: MCCH and MTCH used constantly. (NCCH and CTCH removed)
In Uu signalling messages CRNC introduced to keep messages send/received in SRNC and CRNC inline. | | |
+| 11/03 | RAN2#
39 | R2-032350
R2-032398
R2-032667
R2-032666
R2-032497 | | | The Signalling flow MBMS service availability changed to MBMS service information in 8.2.2. Appropriate changes done in 10.2.
In the Chapter 7.1. included that MBMS UE must capability to receive two SCCPCH
MBMS notification principles chapter created as 5.1.5 and PICH bits used for MBMS notification defined in 6.2.3 physical channels chapters.
The number of different protocol entities clarified in chapter 5.2.1.
The shared PDCP entity principle created in 5.1.4. Protocol layer re-establishments due to mobility defined in 10.2.
UEs measurements are clarified based in working assumption in Section 10.2.
Editorial enhancements to chapter names in chapters 5.1.1, 5.1.2 and 5.1.3 | 2.3.0 | 2.4.0 |
+| 01/04 | RAN2#
40 | R2-04086
Meeting report
R2-040027
R2-040070 | | | A chapter 11.2 Frequency layer Convergence introduced based on revised text from R2-04086
Text inserted based on conclusion on selective combining, multiplexing and measurement occasions
Editorial clarifications. Constant usage of MBMS Service Area as defined in [4]
Session stop included
High level signalling scenarios inserted | 2.4.0 | 2.5.0 |
+| | RAN3#
40 | R3-040061
R3-040075
R3-040076 | | | Modification to chapter 5.1.8
Modification to RNC registration procedure
Additional modifications to 5.1.8 | | |
+| 02/04 | RAN2#
41 | Meeting minutes
R2-040572
R2-040690
R2-040711 | | | Selective combining, simulcast for TDD, Neighbouring cell info, included
MCCH scheduling, MBMS notification and counting enhanced.
MBMS access
MTCH Scheduling information signalling flow included
MBMS high level signalling scenarios updated
Editorial clean up, separation of UTRAN architecture principles and MBMS Uu principles chapter created | 2.5.0 | 2.6.0 |
+| | RAN3#
41 | R3-040577
R3-040576
R3-040314
R3-040393
R3-040575
R3-040458
R3-040516 | | | Functionality to filtering of MBMS notifications and Session update signalling flow included
MBMS Service Id Request to handle UEs in RRC connected PMM idle state. The Signalling flow MBMS Joined Indication modified and MBMS PMM connected stated required removed.
FFS removed from RNC De-Registration and CN De-Registration
Clarifications to MBMS Iu bearer and MBMS Session Start and Session Stop and CN De-Registration
UE linking over Iur modified according agreements
Clarification to creation of MBMS Service context after receiving the first UE linking | | |
+
+| Change history | | | | | | | |
+|----------------|--------|------------------------------|------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| | | R3-040545
Meeting minutes | | | Editorial clean up to RAN3 specific sections.
The Iur bearer mechanisms defined.
Editorial enhancements based on comments after email review on RAN1/2/3 reflectors. | | |
+| 03/2004 | RAN#23 | RP-040079 | | | Upgrade towards Change Control (Release 6) and ETSI MCC clean-up. | 2.6.0 | 6.0.0 |
+| 06/2004 | RP-24 | RP-040216 | 001 | | Updates based on the MBMS ad-hoc, Budapest, 20-22 April 2004 | 6.0.0 | 6.1.0 |
+| | RP-24 | RP-040216 | 002 | | Updates to TS25.346 from the RAN3#42 meeting in Montreal, Canada, 10-14 May 2004 | 6.0.0 | 6.1.0 |
+| 09/2004 | RP-25 | RP-040340 | 003 | | Introduction of MBMS Change Information and Removal of usage of the secondary notification indicators | 6.1.0 | 6.2.0 |
+| | RP-25 | RP-040340 | 004 | | Clarifications to Frequency Layer Convergence and UE behaviour at return on Service | 6.1.0 | 6.2.0 |
+| | RP-25 | RP-040340 | 005 | | Iur Linking for URA_PCH UEs and MBMS Session Start Request corrections for TS25.346 from RAN3#43 | 6.1.0 | 6.2.0 |
+| 12/2004 | RP-26 | RP-040492 | 006 | 1 | Actions due to MBMS session repetition and MBMS service prioritisation | 6.2.0 | 6.3.0 |
+| | RP-26 | RP-040492 | 007 | 1 | Introduction of MSCH and soft combining and other general corrections | 6.2.0 | 6.3.0 |
+| | RP-26 | RP-040492 | 008 | | Corrections to UE Linking, Session Start and addition of URA Linking and Information Exchange procedure | 6.2.0 | 6.3.0 |
+| | RP-26 | RP-040492 | 009 | | Update of Annex B | 6.2.0 | 6.3.0 |
+| 03/2005 | RP-27 | RP-050080 | 010 | | Introduction of MBMS Frequency dispersion | 6.3.0 | 6.4.0 |
+| | RP-27 | RP-050080 | 011 | | Correction on MBMS multiplexing and soft combining in TDD | 6.3.0 | 6.4.0 |
+| | RP-27 | RP-050080 | 012 | | Clarification to UE capabilities to consider MCCH reception and selective/soft combining requirements | 6.3.0 | 6.4.0 |
+| | RP-27 | RP-050080 | 013 | | Extending the counting procedure for UEs in CELL_PCH/FACH state and introducing UE initialised p-t-p setup request | 6.3.0 | 6.4.0 |
+| | RP-27 | RP-050080 | 015 | | Introduction of new procedure in MBMS stage 2 spec | 6.3.0 | 6.4.0 |
+| 06/2005 | RP-28 | RP-050314 | 0016 | | FLD scenario clarifications | 6.4.0 | 6.5.0 |
+| | RP-28 | RP-050314 | 0018 | | Handling the validity of the MBMS session Id | 6.4.0 | 6.5.0 |
+| 09/2005 | RP-29 | RP-050468 | 0019 | | Change of scope for the MBMS Access Information and MBMS P-T-P Modification Request signalling flows plus editorial corrections | 6.5.0 | 6.6.0 |
+| 12/2005 | RP-30 | RP-050788 | 0020 | | Correction to MBMS Cell Group | 6.6.0 | 6.7.0 |
+| 03/2006 | RP-31 | - | - | | Upgrade to Release 7 - no technical change | 6.7.0 | 7.0.0 |
+| 06/2006 | RP-32 | RP-060368 | 0022 | | Clarification of conditions for soft combining | 7.0.0 | 7.1.0 |
+| 09/2006 | RP-33 | RP-060624 | 0024 | 1 | Enhancing MBMS support for Mobile TV | 7.1.0 | 7.2.0 |
+| 03/2007 | RP-35 | RP-070151 | 0026 | 1 | Modification of the MBMS Service Area definition | 7.2.0 | 7.3.0 |
+| 06/2007 | RP-36 | RP-070400 | 0027 | 4 | MBMS TDD and FDD Physical Layer Improvements | 7.3.0 | 7.4.0 |
+| | RP-36 | RP-070401 | 0029 | | MSCH transmission - alignment to stage 3 | 7.3.0 | 7.4.0 |
+| 09/2007 | RP-37 | RP-070625 | 0032 | | MBMS Counting completion (stage 2) | 7.4.0 | 7.5.0 |
+| | RP-37 | RP-070625 | 0034 | | MBMS services naming | 7.4.0 | 7.5.0 |
+| | RP-37 | RP-070632 | 0036 | | Editorial Corrections concerning non MBSFN dedicated TDD carriers | 7.4.0 | 7.5.0 |
+| 12/2007 | RP-38 | RP-070902 | 0037 | | More improvement on Dedicated Carrier for 1.28Mcps TDD MBMS | 7.5.0 | 7.6.0 |
+| | RP-38 | - | - | | Upgrade to the Release 8 - no technical change | 7.6.0 | 8.0.0 |
+| 03/2008 | RP-39 | RP-080177 | 0040 | - | Correction on Frequency Layer Dispersion (FLD) in MBMS stage 2 | 8.0.0 | 8.1.0 |
+| | RP-39 | RP-080180 | 0042 | 1 | Clarification of FLC flag in MBMS stage 2 | 8.0.0 | 8.1.0 |
+| 12/2008 | RP-42 | RP-081023 | 0045 | - | Introduction of MBMS Improved Solution | 8.1.0 | 8.2.0 |
+| | RP-42 | RP-081129 | 0046 | 2 | Support for 3.84 Mcps MBSFN IMB operation | 8.1.0 | 8.2.0 |
+| 03/2009 | RP-43 | RP-090143 | 0047 | - | Correction of MBMS improvements | 8.2.0 | 8.3.0 |
+| | RP-43 | RP-090264 | 0048 | - | Correction on MBMS Improved Solution | 8.2.0 | 8.3.0 |
+| 12/2009 | RP-46 | RP-091326 | 0049 | - | Correction for the Synchronisation Sequence | 8.3.0 | 8.4.0 |
+| 12/2009 | RP-46 | - | - | - | Upgrade to the Release 9 - no technical change | 8.4.0 | 9.0.0 |
+| 03/2010 | RP-47 | RP-100305 | 0051 | - | Clarification on Total counter frame | 9.0.0 | 9.1.0 |
+| | RP-47 | RP-100305 | 0052 | - | Calculation of time stamp value | 9.0.0 | 9.1.0 |
+| | RP-47 | RP-100291 | 0053 | - | Update for SYNC Description | 9.0.0 | 9.1.0 |
+| 03/2011 | RP-51 | - | - | - | Upgrade to the Release 10 - no technical change | 9.1.0 | 10.0.0 |
+| 09/2012 | RP-57 | - | - | - | Upgrade to the Release 11 - no technical change | 10.0.0 | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25401/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-11/25_series/25401/036ceaf207a7b289ca76e160892eb724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13a90ac7c9ee728e50dcdd3c6f11bb39d759eb88
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/036ceaf207a7b289ca76e160892eb724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bed957403cc5d6703c03f5026eb956e835f11310c06a607962c21163e9fca025
+size 38963
diff --git a/marked/Rel-11/25_series/25401/04792a75cf3c66957b41cbcf7b2815a5_img.jpg b/marked/Rel-11/25_series/25401/04792a75cf3c66957b41cbcf7b2815a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09c7b59fe95ccf05dd74faae6c575124be9c4bb4
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/04792a75cf3c66957b41cbcf7b2815a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94b660852c3d82cc35455fdc5a0b8a126109021a32c7d8939c6dae41d6a940f3
+size 5248
diff --git a/marked/Rel-11/25_series/25401/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/marked/Rel-11/25_series/25401/080a7af02bc47cf21ebfae4e0be39745_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7378f32a3419cb51d75ff933686a4fc09ee9bac
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/080a7af02bc47cf21ebfae4e0be39745_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2769f8689cdbea4ded17e089e885288893f2c00bdc45de405f2ed4a146248c6d
+size 39373
diff --git a/marked/Rel-11/25_series/25401/0908107b858fa3783d10d93b3a3444b2_img.jpg b/marked/Rel-11/25_series/25401/0908107b858fa3783d10d93b3a3444b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7fce7e947666b97028f1c3013e9122a840ce371
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/0908107b858fa3783d10d93b3a3444b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc9ef6f70935682ac19d4abc5d1934be1e112d180be5a20672061e340459aae5
+size 39292
diff --git a/marked/Rel-11/25_series/25401/099fb63c349231e49f1979fe6e7563e2_img.jpg b/marked/Rel-11/25_series/25401/099fb63c349231e49f1979fe6e7563e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f822af5a1c1be7be4627fc0fdf76c5d8366fa058
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/099fb63c349231e49f1979fe6e7563e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36cc5361acc97b16ee6d5800e0dbfece50de0e2377b463052f9216801b6bba17
+size 5156
diff --git a/marked/Rel-11/25_series/25401/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-11/25_series/25401/0c80c383f76034e117adf5e5eaadaaf3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29447273eb6a6704d3f82f15592f791ba2e80b02
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/0c80c383f76034e117adf5e5eaadaaf3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61afb67e14dcf2649234cafa4e1c2c538ff3f4b895cf62ad2e42c2f670e75330
+size 30617
diff --git a/marked/Rel-11/25_series/25401/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-11/25_series/25401/0f26e70157bd4c45f825795cdcd20fbd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..974ff7b53ccea6dc8dd4dea6adff4a82b014ba84
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/0f26e70157bd4c45f825795cdcd20fbd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52fd007193e9c4c5ed0a0d4c1f32331b6facb4eb15dfafeec467a119e0c08aa9
+size 52926
diff --git a/marked/Rel-11/25_series/25401/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Rel-11/25_series/25401/1033dc9fde75540d224c907681b1b7aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d9cd60fe1ede06d08dd50551a9dbc373493b9d2
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/1033dc9fde75540d224c907681b1b7aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccbb71da8589f271cbbf6dd3c487bde0fdf8aad9158ba491a329f84722c308dd
+size 68509
diff --git a/marked/Rel-11/25_series/25401/132cff7e872feb31f629703959beddd7_img.jpg b/marked/Rel-11/25_series/25401/132cff7e872feb31f629703959beddd7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1204e46a151e6cad097f7a31b42c18f1c05e0aa
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/132cff7e872feb31f629703959beddd7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b92f4e4ccc9678acc581283cdbfbfffd31f88a67f927256f03d74ce6dd29df7a
+size 20318
diff --git a/marked/Rel-11/25_series/25401/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/25_series/25401/187d05bf7ead21e1394b61320d8b3632_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8812597fd4231cc7e7d44932e57c30396df168de
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/187d05bf7ead21e1394b61320d8b3632_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d45e066398c88c216019dd30bd0c484420efd3eacc7d9c25825572ac3460d7ca
+size 26166
diff --git a/marked/Rel-11/25_series/25401/19d7a7ce68d3e9036613910b761c4b24_img.jpg b/marked/Rel-11/25_series/25401/19d7a7ce68d3e9036613910b761c4b24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0970541f624c086b06849daa148f388b2ff18722
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/19d7a7ce68d3e9036613910b761c4b24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd7f90f1c34c68d2d59836037d82c838cb816d82cdf05b5df94754740ef2362d
+size 48057
diff --git a/marked/Rel-11/25_series/25401/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/25_series/25401/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9264d5866babfed8eb5e21b1c2c3335e40c15e8b
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d705891311ef9a8d6122abd46db19ac00d9a8bd42feb2d6cdbf317a7e1ff0001
+size 58199
diff --git a/marked/Rel-11/25_series/25401/1ad662a678c4f002de911d403f00de8e_img.jpg b/marked/Rel-11/25_series/25401/1ad662a678c4f002de911d403f00de8e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ca95f9bcfcae95a5212cfb36ae8a654589b15c8
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/1ad662a678c4f002de911d403f00de8e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4706d16c1bf926e177afe4cc9432abd73a606b38a0affcbac435dbc5525e24a
+size 79727
diff --git a/marked/Rel-11/25_series/25401/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-11/25_series/25401/1ce027dfd26183da52137cf990213724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97632c5c71f3a58c8c5f0a808216f1c8c7fa64ed
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/1ce027dfd26183da52137cf990213724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa6e745d7c88a1e0c8187dbb80b2d6052bdcb9500a797f80c2e4a83ff5a45548
+size 29388
diff --git a/marked/Rel-11/25_series/25401/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-11/25_series/25401/28085f681b9fff76a53c5b8b32338ee1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0ddae78c6fae73759f2224090c30dd35fe0bc9d
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/28085f681b9fff76a53c5b8b32338ee1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c19b5f84fac669626f05bf125b647a712eeb0c201988c7a465516178a589aadc
+size 48494
diff --git a/marked/Rel-11/25_series/25401/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-11/25_series/25401/29f586959675cafdf81cf934954908eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be47dea724db5a80ccc6393c729a4037f4874bc7
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/29f586959675cafdf81cf934954908eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d43d1e1e22a545f40db5fb9c2be591f5b4954bc88b625cf9c4e9e12e337c79b6
+size 25957
diff --git a/marked/Rel-11/25_series/25401/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/25_series/25401/2cf3896394a2342a2b46c504ab9a8830_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..350ec310e36044da5b9e3034062bd917b204642c
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/2cf3896394a2342a2b46c504ab9a8830_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7dcb5e9133194b2f3b9626489fb022e30e0cdfd4769351d5fdb0b8048c9bd61
+size 24868
diff --git a/marked/Rel-11/25_series/25401/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/marked/Rel-11/25_series/25401/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f377afd6ca164fa9a1c9270e54866d3b82a3e6c
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3685b07021df67584eba7b8f7025eb233c7186f68d0af693765cc2846354ca65
+size 45465
diff --git a/marked/Rel-11/25_series/25401/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/25_series/25401/3337af75dfee8af7687b4f49914d6c93_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..044c224822cdd74a240351a0e853d0fb79213f44
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/3337af75dfee8af7687b4f49914d6c93_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b185ec4974a5bf0250bb2ba21864d78b467c29c577feb91d5828d80b78aedb7
+size 53602
diff --git a/marked/Rel-11/25_series/25401/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-11/25_series/25401/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93200a2facfb8c458c01db860eec59fed90994c2
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d43510226c056f69e0717a3a0f6bc4218c1661cc642e6de37060185cd1cd504b
+size 42614
diff --git a/marked/Rel-11/25_series/25401/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/25_series/25401/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3dcf7adfedf683e89cec38022e45a14d914b159
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89144eeef8b244ee997e00e43ddcc73e379662af6e6c7a2efc636eb78593a058
+size 41940
diff --git a/marked/Rel-11/25_series/25401/396197257cf9437b526bb6585b6a9c8a_img.jpg b/marked/Rel-11/25_series/25401/396197257cf9437b526bb6585b6a9c8a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..317f7dc272c04dcd036271edad41248fd8efb2cd
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/396197257cf9437b526bb6585b6a9c8a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:314fafc3bd960f40dd1abe4c7d3906168cb5e3e155d6aaf4348306e9270baae7
+size 40678
diff --git a/marked/Rel-11/25_series/25401/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-11/25_series/25401/41a438d7e4adc17c3a4005e7c9500091_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..281753b1393c58ea01129ada4e21abb15d24e236
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/41a438d7e4adc17c3a4005e7c9500091_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9bed1699f3b563ac9aec1639ce75b9d2931da155974aabd7fef7791dd6754694
+size 58464
diff --git a/marked/Rel-11/25_series/25401/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-11/25_series/25401/458fdbcb4015a4ee90bd84809afc4aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d86571b5d8866601fda931d3af2b30cae766e52
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/458fdbcb4015a4ee90bd84809afc4aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d066fabfec16cf1f90ab3e91575bb1b3d1e4ac2114fc2c147226039f8d3c73d0
+size 5519
diff --git a/marked/Rel-11/25_series/25401/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-11/25_series/25401/51db757d054ce1ce83c436a3578b56ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8af1bbb4f4b9f73260b4d2d37bf4361687c06565
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/51db757d054ce1ce83c436a3578b56ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d49519dc6eafe1f224afe71fce314fcd03aea45ec36b6c7d317f535fd0ff9e24
+size 27326
diff --git a/marked/Rel-11/25_series/25401/52ebea0f3ff6ab1f69dacaef58c089ad_img.jpg b/marked/Rel-11/25_series/25401/52ebea0f3ff6ab1f69dacaef58c089ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d9b25ce3fdead3755cb82e828290d8fe93dfbeb5
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/52ebea0f3ff6ab1f69dacaef58c089ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9892e7bdbe1f5b1ebcfb1d77e3dd496cdad491109274ad1552c164b252827201
+size 4966
diff --git a/marked/Rel-11/25_series/25401/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/marked/Rel-11/25_series/25401/5c3dd31372f59e15250f0ab1613ca485_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9354a9071071298f3ccf7fb36ce2c1229a91335
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/5c3dd31372f59e15250f0ab1613ca485_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04dc0a2ee8d572240a256973dc3e053a8c63c4bfa0aee1ae7a57d1ca6c617478
+size 24657
diff --git a/marked/Rel-11/25_series/25401/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-11/25_series/25401/67d03c9e89620d73e3786c869e559752_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24e4bc8add7216db200b2770cd7324b65288a463
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/67d03c9e89620d73e3786c869e559752_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:475d131c67d79db275a639cb71deca478d02f52336e85b1b98baae5f80f078eb
+size 31803
diff --git a/marked/Rel-11/25_series/25401/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/25_series/25401/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80a24af92dbb704fcee0e10872af079c225b3806
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:927cef80226997e02275dfa5e67cb551a6944922fbafd9b9eebf1f8e1faeca99
+size 81381
diff --git a/marked/Rel-11/25_series/25401/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-11/25_series/25401/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41fea86d265e78974350d8f6c09b8248ee784b76
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e027feed54fb147d01ce7149957b25fd58ea5f6f443bc4fadc67af2fca120cd1
+size 73752
diff --git a/marked/Rel-11/25_series/25401/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/25_series/25401/7ed5d5770331f31ade15439a21c31425_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43777389a0d9673f51f1835b5f080d40f250705a
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/7ed5d5770331f31ade15439a21c31425_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7775d63b28c605faf9f166821519022d8dd58bb61f7c3a96ba73093dbea5b9f8
+size 64317
diff --git a/marked/Rel-11/25_series/25401/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/25_series/25401/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0aa218cfebd324c03e13fe2c0d69a48104b8d55a
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9920dd2228be267a47ddfac0941146b9567df8b13a5b24eac1e9850ae906bb7
+size 38862
diff --git a/marked/Rel-11/25_series/25401/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-11/25_series/25401/84e5b251aa38db522f76f5cc3afcb853_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d2510532c4df37b66570e1f4755107f48c3b4533
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/84e5b251aa38db522f76f5cc3afcb853_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec4d081f147cd31a3d8a154dd7917cff9087b8ef9ae8f934e90758875d9a868e
+size 48021
diff --git a/marked/Rel-11/25_series/25401/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-11/25_series/25401/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3a4ea92332a33e23dde5e2570963879fcdac4593
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bea0e9bed3be9e2e16b6f88f1aa4cd229946f2f0b95a69e8e6735369b19c17e
+size 25766
diff --git a/marked/Rel-11/25_series/25401/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-11/25_series/25401/86b4670fc1a5a694821ee92b99c1209a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c469b1055039a2ec378d8a8920e89657c36ffdd
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/86b4670fc1a5a694821ee92b99c1209a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b5729a6d47ffc4dccaf04dad156cf77c48e1488b376f97b950f6491d79e40a4
+size 31988
diff --git a/marked/Rel-11/25_series/25401/8a425cd12663f0c24560eb1155c1f681_img.jpg b/marked/Rel-11/25_series/25401/8a425cd12663f0c24560eb1155c1f681_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..368405a4be4073c3fcaed6e1358a16718b79898b
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/8a425cd12663f0c24560eb1155c1f681_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec1970969c789004a0f4b7c6eebb93c0be228d34c27a0aa7c4cfe4a567d6dff5
+size 4939
diff --git a/marked/Rel-11/25_series/25401/8d8c758885b4f754ff071bf3b572ab3c_img.jpg b/marked/Rel-11/25_series/25401/8d8c758885b4f754ff071bf3b572ab3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5f0e58d2d9c9aa7ffe1f71c0569857de2240e91
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/8d8c758885b4f754ff071bf3b572ab3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91fe2325c1182476b464e229931aff80ff7a52accbadb3ce3dd8d610fb90c045
+size 39827
diff --git a/marked/Rel-11/25_series/25401/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-11/25_series/25401/9a14684f8ae1345c6efea6f5994c730c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28e8c15640e702bece0bd50972a6603d75bd0b04
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/9a14684f8ae1345c6efea6f5994c730c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:568431d64da8da9a33abdcf4c16534f40b5101c92d739662ab65281bc6a808d5
+size 27522
diff --git a/marked/Rel-11/25_series/25401/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/25_series/25401/9b1ec0090070bdf52ea28763b8d52477_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3614decabd25799b7abdb8bbbe07a92ec38f7de
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/9b1ec0090070bdf52ea28763b8d52477_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:675f8f4c6966d80e7e4197dbbdb4c6958e0153fb122e219f7af92e92fbdaccfa
+size 51506
diff --git a/marked/Rel-11/25_series/25401/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-11/25_series/25401/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b03ec87694fa574a8e7e444ad418f9c935c0a699
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9633b5d5a8073c6caf0519b9caec69d0213271836aa154c3d8ff5cc7a68df29e
+size 48476
diff --git a/marked/Rel-11/25_series/25401/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Rel-11/25_series/25401/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0dfd85fa6bdfcd6b44e748fafd377efed3278b72
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af573bb4ce420ee2b3c61100b2cb60850752606a156c1157961e484bd3f9d82e
+size 24809
diff --git a/marked/Rel-11/25_series/25401/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/25_series/25401/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e01bbf6a6ca2d8e4cb5a110246528dd4715513e
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f1617aee2483aecbdb10a05b341d06c8b9f5233c546d7637ea987052872650c
+size 6122
diff --git a/marked/Rel-11/25_series/25401/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/25_series/25401/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d46390d0a761ac363210525c5bbd3fbffd8ecc85
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e473fed17b146fe9dd89708f14d74f01fe050a43e1624c089b539b550c39dd93
+size 100435
diff --git a/marked/Rel-11/25_series/25401/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/25_series/25401/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..536efcaab0af3a619cde54167a92dffc5d6096d7
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b28883aa6ec69280e65996a30f82fe67351f16250e91331be26bffd8c7f48a5
+size 42990
diff --git a/marked/Rel-11/25_series/25401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/25_series/25401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5aa6c18bcedf4f9f47d9aa2e53c8b0e121965a67
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39a7b737289b8fdcf1713b96f087688838521ef762f5c92565005486405d7096
+size 18256
diff --git a/marked/Rel-11/25_series/25401/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-11/25_series/25401/a734898ce18e972938949637c32a34f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..569686442c990b6b431fcbbc94b1e8c523deb6b7
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/a734898ce18e972938949637c32a34f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c838858c93a9b5cc2db62e04570697ccaf96da60d79b0024099102e6aa422e1e
+size 107702
diff --git a/marked/Rel-11/25_series/25401/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/25_series/25401/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a7442990db00a5bdebf690d3aa83bc13bd6ac79
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf83aa232c1dbf5c5ad551612c4d5f91d56b4aba4142b827197ba409fc58d7b1
+size 184987
diff --git a/marked/Rel-11/25_series/25401/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-11/25_series/25401/b44f89b176c971c7dd264c07bfef2c2a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62c3c9bf34bd6929322c546ee94d8dafb6a7d46c
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/b44f89b176c971c7dd264c07bfef2c2a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64968fc4f698bafc189c6b06fb1011ab0b7412111c01e64cd03d5c3fc4e28503
+size 33298
diff --git a/marked/Rel-11/25_series/25401/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/marked/Rel-11/25_series/25401/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2606f0e0bb3f11e2cbb6b6aee29d450407216d3
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cabda20c78dbe940d3d391b665e30a2ef7a045221640a5a1452d6ae5024d22d
+size 4709
diff --git a/marked/Rel-11/25_series/25401/c419b566d720267c499087add1506018_img.jpg b/marked/Rel-11/25_series/25401/c419b566d720267c499087add1506018_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c61fcf390b9c416b5ae3587a31ec3a9224cf7ac
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/c419b566d720267c499087add1506018_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2880978a279ab269421aef7f76f667a764085e853c8d9c153219e4e27caaa77
+size 70910
diff --git a/marked/Rel-11/25_series/25401/c468d53e877568cd7d8c5ba1632c2e65_img.jpg b/marked/Rel-11/25_series/25401/c468d53e877568cd7d8c5ba1632c2e65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be774f92bd2370ee3f8e5ee23f945c310015415f
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/c468d53e877568cd7d8c5ba1632c2e65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27deea2da309b2cedf92ccb4558df8c6b0dc53e33caefa9aa9c7e52a0bb4f808
+size 25961
diff --git a/marked/Rel-11/25_series/25401/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/25_series/25401/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96bddaf0388d58baa5ad06e5b53239f06bd33764
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c4bfa7eff5336a6cf37cf8c121ea363518aeb16cbc789787c903b9d8a5783a0
+size 34259
diff --git a/marked/Rel-11/25_series/25401/daf05db9f13b34fb12da52f007bbfe5b_img.jpg b/marked/Rel-11/25_series/25401/daf05db9f13b34fb12da52f007bbfe5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..143002a79fc7afc5e95091278b56d086c0bf050f
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/daf05db9f13b34fb12da52f007bbfe5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:858dce0f12961a5d8e10da0260768edfb1a97403faf42aec54ff58378c26cb25
+size 27115
diff --git a/marked/Rel-11/25_series/25401/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-11/25_series/25401/db5deafdae53dbc7d5972957f708c691_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45ae04a0e68519fb6cd3a03cf7360902fcc3e834
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/db5deafdae53dbc7d5972957f708c691_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22d28e79c1222c3475600fb232c1ac5e0a757bd13fdaf5ec78af2e22ffb0e757
+size 5485
diff --git a/marked/Rel-11/25_series/25401/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-11/25_series/25401/e05122559f56af5699789b7118d8fe87_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5770d426cde168d2ceec1e6091d82c09dae444f
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/e05122559f56af5699789b7118d8fe87_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e9c4adb32001f029726dd8c061037a070bd17799bb54074cf5c507759c46957
+size 40493
diff --git a/marked/Rel-11/25_series/25401/e190b6ddb7c2e64b940749a1c5612256_img.jpg b/marked/Rel-11/25_series/25401/e190b6ddb7c2e64b940749a1c5612256_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c35a5d97d292fa3e879eed58d2f1f909052ef19
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/e190b6ddb7c2e64b940749a1c5612256_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0185b3a8930580349e6a23df7b8e0c8494188c967ec2b0fc70f5df49272c7a62
+size 46583
diff --git a/marked/Rel-11/25_series/25401/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/marked/Rel-11/25_series/25401/e3eebf9854831ba50eca8b26c468f65e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81bfa7ed329b0ff2800f442ca13069f015a1151b
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/e3eebf9854831ba50eca8b26c468f65e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c79b6ecf526f4a0470f5052d587f63ccb4d1f59a6ecf0546a3829ed51a257e6d
+size 5518
diff --git a/marked/Rel-11/25_series/25401/f24f909d837b5476783e1bbea2dfc143_img.jpg b/marked/Rel-11/25_series/25401/f24f909d837b5476783e1bbea2dfc143_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f124b5abe747b45baaa39791ba2cb97c367a4de
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/f24f909d837b5476783e1bbea2dfc143_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91ca91c261184e373a96896cfba77fcd15052270ad5b42f9daa412f15dd76072
+size 43025
diff --git a/marked/Rel-11/25_series/25401/fc0cdcafc5389b99674ba116c9787ffd_img.jpg b/marked/Rel-11/25_series/25401/fc0cdcafc5389b99674ba116c9787ffd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8336552268aa2fd1c928ef4edd050a56b1ed210
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/fc0cdcafc5389b99674ba116c9787ffd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:729e46d39cda5c5d76f939112cb24665c61b46b70cdaec5d614f4eb5bb578e3a
+size 4689
diff --git a/marked/Rel-11/25_series/25401/raw.md b/marked/Rel-11/25_series/25401/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d495a9aa50208e93775613b1b7a5e3db1ab9505
--- /dev/null
+++ b/marked/Rel-11/25_series/25401/raw.md
@@ -0,0 +1,2193 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|---------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 10 |
+| 3.3 Notation..... | 12 |
+| 4 General principles ..... | 13 |
+| 5 UMTS General architecture ..... | 13 |
+| 5.1 Overview ..... | 13 |
+| 5.2 General protocols architecture ..... | 14 |
+| 5.2.1 User plane..... | 14 |
+| 5.2.2 Control plane ..... | 15 |
+| 6 UTRAN Architecture..... | 15 |
+| 6.1 UTRAN Identifiers..... | 20 |
+| 6.1.1 PLMN Identity..... | 20 |
+| 6.1.2 CN Domain Identifier..... | 20 |
+| 6.1.3 RNC Identifier..... | 20 |
+| 6.1.4 Service Area Identifier..... | 20 |
+| 6.1.5 Cell Identifier..... | 20 |
+| 6.1.6 Local Cell Identifier ..... | 20 |
+| 6.1.7 UE Identifiers ..... | 20 |
+| 6.1.7.1 Usage of RNTI..... | 22 |
+| 6.1.7.a UE Identifiers in GERAN A/Gb mode (1.28Mcps TDD)..... | 22 |
+| 6.1.8 Identifiers for dedicated resources within UTRAN..... | 22 |
+| 6.1.8.1 Radio Network Control Plane identifiers..... | 22 |
+| 6.1.8.2 Transport Network Identifiers ..... | 22 |
+| 6.1.8.3 Binding identifier..... | 23 |
+| 6.1.9 URA Identity ..... | 25 |
+| 6.1.10 Service Identifiers for MBMS ..... | 25 |
+| 6.1.10.1 IP Multicast Address and APN..... | 25 |
+| 6.1.10.2 TMGI ..... | 25 |
+| 6.1.10.3 Session Identifier ..... | 25 |
+| 6.1.10.4 MBMS Service Area..... | 25 |
+| 6.1.10.5 MBMS Cell Group Identifier..... | 25 |
+| 6.1.10.6 MBMS UTRAN Cell Group Identifier..... | 25 |
+| 6.1.11 Transport Network Identifiers for MBMS ..... | 25 |
+| 6.1.12 Binding Identifiers for MBMS ..... | 26 |
+| 6.1.13 Use of Extended Identifiers ..... | 26 |
+| 6.2 Transport Addresses..... | 26 |
+| 6.3 Function Distribution Principles ..... | 26 |
+| 7 UTRAN Functions description ..... | 27 |
+| 7.1 List of functions ..... | 27 |
+| 7.2 Functions description ..... | 28 |
+| 7.2.0 Transfer of user data..... | 28 |
+| 7.2.1 Functions related to overall system access control..... | 28 |
+| 7.2.1.1 Admission Control..... | 28 |
+| 7.2.1.2 Congestion Control..... | 28 |
+| 7.2.1.3 System information broadcasting ..... | 29 |
+| 7.2.1.4 MOCN and GWCN configuration support..... | 29 |
+| 7.2.2 Radio channel ciphering and deciphering ..... | 29 |
+| 7.2.3 Functions related to Mobility ..... | 29 |
+| 7.2.3.1 Handover..... | 29 |
+| 7.2.3.2 SRNS Relocation ..... | 29 |
+
+| | | |
+|-----------|-------------------------------------------------------------------------------------------------------------------|----|
+| 7.2.3.3 | Paging support ..... | 30 |
+| 7.2.3.4 | Positioning ..... | 30 |
+| 7.2.3.5 | NAS Node Selection Function..... | 30 |
+| 7.2.3.6 | Shared Networks Access Control ..... | 30 |
+| 7.2.3.7 | GERAN System Information Retrieval ..... | 31 |
+| 7.2.3.8 | Enhanced SRNS Relocation ..... | 31 |
+| 7.2.3.9 | Subscriber Profile ID for RAT/Frequency Priority ..... | 31 |
+| 7.2.4 | Functions related to radio resource management and control ..... | 31 |
+| 7.2.4.1 | Radio resource configuration and operation..... | 31 |
+| 7.2.4.2 | Radio environment survey ..... | 31 |
+| 7.2.4.3 | Combining/splitting control ..... | 32 |
+| 7.2.4.4 | Connection set-up and release ..... | 32 |
+| 7.2.4.5 | Allocation and deallocation of Radio Bearers ..... | 32 |
+| 7.2.4.6 | [TDD - Dynamic Channel Allocation (DCA)] ..... | 32 |
+| 7.2.4.7 | Radio protocols function..... | 33 |
+| 7.2.4.8 | RF power control ..... | 33 |
+| 7.2.4.8.1 | UL Outer Loop Power Control..... | 33 |
+| 7.2.4.8.2 | DL Outer Loop Power Control..... | 33 |
+| 7.2.4.8.3 | UL Inner Loop Power Control ..... | 33 |
+| 7.2.4.8.4 | DL Inner Loop Power Control ..... | 34 |
+| 7.2.4.8.5 | UL Open Loop Power Control ..... | 34 |
+| 7.2.4.8.6 | DL Open Loop Power Control ..... | 34 |
+| 7.2.4.9 | Radio channel coding..... | 34 |
+| 7.2.4.10 | Radio channel decoding..... | 34 |
+| 7.2.4.11 | Channel coding control..... | 34 |
+| 7.2.4.12 | Initial (random) access detection and handling ..... | 34 |
+| 7.2.4.13 | CN Distribution function for Non Access Stratum messages..... | 35 |
+| 7.2.4.14 | [3.84 Mcps and 7.68 Mcps TDD - Timing Advance]..... | 35 |
+| 7.2.4.15 | Service specific function for Non Access Stratum messages ..... | 35 |
+| 7.2.4.16 | [1.28 Mcps TDD – Uplink Synchronisation]..... | 35 |
+| 7.2.5 | Functions related to broadcast and multicast services (broadcast/multicast interworking function
BM-IWF) ..... | 35 |
+| 7.2.5.1 | Broadcast/Multicast Information Distribution ..... | 35 |
+| 7.2.5.2 | Broadcast/Multicast Flow Control..... | 35 |
+| 7.2.5.3 | CBS Status Reporting ..... | 35 |
+| 7.2.6 | Tracing..... | 36 |
+| 7.2.7 | Volume Reporting ..... | 36 |
+| 7.2.8 | RAN Information Management..... | 36 |
+| 7.2.9 | Functions related to MBMS ..... | 36 |
+| 7.2.9.1 | MBMS provision ..... | 36 |
+| 7.2.9.2 | MBMS Notification Coordination ..... | 36 |
+| 7.2.10 | SIPTO at Iu-PS ..... | 36 |
+| 7.2.11 | Explicit Congestion Notification ..... | 36 |
+| 7.2.12 | MDT ..... | 36 |
+| 8 | Mobility Management..... | 37 |
+| 8.1 | Signalling connection..... | 37 |
+| 8.2 | Consequences for Mobility Handling ..... | 37 |
+| 9 | Synchronisation..... | 37 |
+| 9.1 | SYNCHRONISATION MODEL..... | 37 |
+| 10 | UTRAN O&M Requirements ..... | 38 |
+| 10.1 | O&M of Node B..... | 38 |
+| 10.1.1 | Implementation Specific O&M ..... | 39 |
+| 10.1.2 | Logical O&M ..... | 39 |
+| 11 | UTRAN Interfaces ..... | 40 |
+| 11.1 | General Protocol Model for UTRAN Interfaces ..... | 40 |
+| 11.1.1 | General ..... | 40 |
+| 11.1.2 | Horizontal Layers ..... | 40 |
+| 11.1.3 | Vertical Planes..... | 40 |
+| 11.1.3.1 | Control Plane ..... | 40 |
+
+| | | |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------|
+| 11.1.3.2 | User Plane ..... | 41 |
+| 11.1.3.3 | Transport Network Control Plane ..... | 41 |
+| 11.1.3.4 | Transport Network User Plane ..... | 41 |
+| 11.2 | Protocol Model (Informative) ..... | 42 |
+| 11.2.1 | RACH Transport Channel ..... | 42 |
+| 11.2.2 | CPCH [FDD] Transport Channel ..... | 43 |
+| 11.2.3 | FACH Transport Channel ..... | 43 |
+| 11.2.4 | DCH Transport Channel ..... | 44 |
+| 11.2.5 | DSCH Transport Channel [TDD] ..... | 45 |
+| 11.2.6 | USCH Transport Channel [TDD] ..... | 46 |
+| 11.2.7 | HS-DSCH Transport Channel ..... | 47 |
+| 11.2.8 | E-DCH Transport Channel ..... | 50 |
+| 12 | UTRAN Performance Requirements ..... | 52 |
+| 12.1 | UTRAN delay requirements ..... | 52 |
+| Annex A (informative): | SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities ..... | 53 |
+| Annex A2 (Informative): | Deployment of Extended Identifiers ..... | 54 |
+| A2.1 | RNC Sizing Changes ..... | 54 |
+| A2.1.1 | U-RNTI Considerations ..... | 54 |
+| A2.1.2 | Extend S-RNTI and reduce RNC-ID: Solution 1 ..... | 55 |
+| A2.1.3 | Pooled RNCs: Solution 2 ..... | 55 |
+| A2.2 | RNC ID Extension ..... | 56 |
+| A2.2.1 | Solution for RNC-ID Extension ..... | 56 |
+| A2.2.2 | Rules for Configuration ..... | 57 |
+| A2.2.3 | Configuration Example ..... | 60 |
+| Annex B (informative): | Change history ..... | 62 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document describes the overall architecture of the UTRAN, including internal interfaces and assumptions on the radio and Iu interfaces.
+
+# --- 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] Void
+- [2] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions".
+- [3] Void
+- [4] 3GPP TS 25.442: "UTRAN Implementation Specific O&M Transport".
+- [5] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2".
+- [6] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [7] 3GPP TS 25.331: " Radio Resource Control (RRC); Protocol specification".
+- [8] 3GPP TS 23.101: "General UMTS Architecture".
+- [9] 3GPP TS 25.414: " UTRAN Iu Interface Data Transport & Transport Signalling".
+- [10] 3GPP TS 25.424: "UTRAN Iur Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams".
+- [11] 3GPP TS 25.434: "UTRAN Iub Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams".
+- [12] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (Ipv6) Specification".
+- [13] Void
+- [14] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [15] "Information technology – Open Systems Interconnection – Network service definition", X.213, ISO/IEC 8348.
+- [16] "Information technology – Open Systems Interconnection – Network service definition Amendment 1: Addition of the Internet protocol address format identifier", X.213/Amd.1, ISO/IEC 8348.
+- [17] IETF RFC 791 (1981-09): "Internet Protocol".
+- [18] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams".
+- [19] Void
+
+- [20] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
+- [21] 3GPP TR 43.930: "Iur-g interface; Stage 2".
+- [22] 3GPP TR 44.901: "External Network Assisted Cell Change".
+- [23] 3GPP TS 48.018: "General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP)".
+- [24] 3GPP TS 25.460: "UTRAN Iuant Interface: General Aspects and Principles".
+- [25] 3GPP TS 25.461: "UTRAN Iuant Interface: Layer 1".
+- [26] 3GPP TS 25.462: "UTRAN Iuant Interface: Signalling Transport".
+- [27] Void
+- [28] 3GPP TS 23.251: "Network sharing - Architecture and functional description".
+- [29] 3GPP TS 25.410: "UTRAN Iu Interface: general aspects and principles".
+- [30] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
+- [31] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+- [32] 3GPP TS 25.466: "UTRAN Iuant Interface: Application part".
+- [33] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN".
+- [34] IETF RFC 4548 (2006-05): "Internet Code Point (ICP) Assignments for NSAP Addresses"
+- [35] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; stage 2".
+- [36] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [37] IETF RFC 3168 (2001-09): "The Addition of Explicit Congestion Notification (ECN) to IP".
+- [38] 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 following terms and definitions apply:
+
+**[1.28Mcps TDD - Multi-frequency Cell:** If multiple frequencies are configured in one cell, the cell is defined as the multi-frequency cell.]
+
+**[1.28Mcps TDD - Primary frequency:** In a multi-frequency cell, the frequency on which the P-CCPCH is transmitted is defined as primary frequency.]
+
+**[1.28Mcps TDD - Secondary frequency:** In a multi-frequency cell, any frequency other than the primary frequency is defined as secondary frequency.]
+
+**ALCAP:** generic name for the transport signalling protocols used to set-up and tear-down transport bearers
+
+**Cell:** Radio Network object that can be uniquely identified by a User Equipment from a (cell) identification that is broadcasted over a geographical area from one *UTRAN Access Point*
+A Cell is either FDD or TDD mode.
+
+**Iu:** interface between an RNC and an MSC, SGSN or CBC, providing an interconnection point between the RNS and the Core Network. It is also considered as a reference point
+
+**Iub:** interface between the RNC and the Node B
+
+**Iur:** logical interface between two RNCs
+
+Whilst logically representing a point to point link between RNCs, the physical realisation need not be a point to point link.
+
+**Iur-g:** logical interface between RNC/BSS and BSS
+
+Whilst logically representing a point to point link between RNC/BSS and BSS, the physical realisation need not be a point to point link.
+
+**Logical Model:** Logical Model defines an abstract view of a network or network element by means of information objects representing network element, aggregations of network elements, the topological relationship between the elements, endpoints of connections (termination points), and transport entities (such as connections) that transport information between two or more termination points
+
+The information objects defined in the Logical Model are used, among others, by connection management functions. In this way, a physical implementation independent management is achieved.
+
+**Network sharing supporting UE:** as defined in TS 23.251 [28].
+
+**Network sharing non-supporting UE:** as defined in TS 23.251 [28].
+
+**Node B:** logical node in the RNS responsible for radio transmission / reception in one or more cells to/from the UE
+The logical node terminates the Iub interface towards the RNC.
+
+**Radio Resources:** resources that constitute the radio interface in UTRAN, e.g. frequencies, scrambling codes, spreading factors, power for common and dedicated channels
+
+**Node B Application Part:** Radio Network Signalling over the Iub
+
+**Radio Network Controller:** logical node in the RNS in charge of controlling the use and the integrity of the radio resources
+
+**Controlling RNC:** role an RNC can take with respect to a specific set of Node B's
+
+There is only one Controlling RNC for any Node B. The Controlling RNC has the overall control of the logical resources of its node B's.
+
+**MBMS Master RNC:** role an RNC can take with respect to one or more specific MBSFN cluster(s)
+
+MRNC may be used for Inter-RNC MBSFN operation whenever dynamic synchronization of radio resources used for MBMS services is centrally controlled. There is only one MBMS Master RNC for any MBSFN cluster, which may control one or more MBSFN cluster(s). The MRNC has the overall control of the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s).
+
+**Radio Network Subsystem:** RNS can be either a full UTRAN or only a part of a UTRAN
+
+An RNS offers the allocation and release of specific radio resources to establish means of connection in between an UE and the UTRAN. A Radio Network Subsystem contains one RNC and is responsible for the resources and transmission/reception in a set of cells.
+
+**Serving RNS:** role an RNS can take with respect to a specific connection between an UE and UTRAN
+
+There is one Serving RNS for each UE that has a connection to UTRAN. The Serving RNS is in charge of the radio connection between a UE and the UTRAN. The Serving RNS terminates the Iu for this UE.
+
+**Drift RNS:** role an RNS can take with respect to a specific connection between an UE and UTRAN
+
+An RNS that supports the Serving RNS with radio resources when the connection between the UTRAN and the UE need to use cell(s) controlled by this RNS is referred to as Drift RNS.
+
+**Radio Access Network Application Part:** Radio Network Signalling over the Iu
+
+**Radio Network Subsystem Application Part:** Radio Network Signalling over the Iur
+
+**RRc Connection:** point-to-point bi-directional connection between RRc peer entities on the UE and the UTRAN sides, respectively
+
+An UE has either zero or one RRc connection.
+
+**Stand-Alone SMLC:** as defined in TS 25.305 [33].
+
+**User Equipment:** Mobile Equipment with one or several UMTS Subscriber Identity Module(s)
+
+A device allowing a user access to network services via the Uu interface. The UE is defined in ref. TS 23.101 [8]. If this term is used in the context of Iur-g, it means MS in case it uses radio resources of a DBSS.
+
+**Universal Terrestrial Radio Access Network:** UTRAN is a conceptual term identifying that part of the network which consists of RNCs and Node Bs between Iu and Uu
+
+The concept of UTRAN instantiation is currently undefined.
+
+**User Datagram Protocol:** as defined in IETF RFC 768 [14].
+
+**UTRAN Access Point:** conceptual point within the UTRAN performing radio transmission and reception
+
+A UTRAN access point is associated with one specific *cell*, i.e. there exists one UTRAN access point for each cell. It is the UTRAN-side end point of a *radio link*.
+
+**Radio Link:** "radio link" is a logical association between a single User Equipment and a single UTRAN access point. Its physical realisation comprises one or more radio bearer transmissions.
+
+**Radio Link Set:** set of one or more Radio Links that has a common generation of Transmit Power Control (TPC) commands in the DL
+
+**Uu:** Radio interface between UTRAN and the User Equipment
+
+**RAB sub-flows:** Radio Access Bearer can be realised by UTRAN through several sub-flows
+
+These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes.
+
+RAB sub-flows have the following characteristics:
+
+- 1) The sub-flows of a RAB are established and released at the RAB establishment and release, respectively.
+- 2) The sub-flows of a RAB are submitted and delivered together at the RAB SAP.
+- 3) The sub-flows of a RAB are carried over the same Iu transport bearer.
+- 4) The sub-flows of a RAB are organised in a predefined manner at the SAP and over the Iu interface. The organisation is imposed by the NAS as part of its co-ordination responsibility.
+
+**Set of co-ordinated DCHs:** set of co-ordinated DCHs is a set of dedicated transport channels that are always established and released in combination
+
+Individual DCHs within a set of co-ordinated DCHs cannot be operated on individually e.g. if the establishment of one DCH fails, the establishment of all other DCHs in the set of co-ordinated DCHs shall be terminated unsuccessfully. A set of coordinated DCHs is transferred over one transport bearer. All DCHs in a set of co-ordinated DCHs shall have the same TTI.
+
+**Shared Network Area (SNA):** Area consisting of one or more LA's to which access can be controlled.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|--------|-------------------------------------------|
+| AAL | ATM Adaptation Layer |
+| AAL2 | ATM Adaptation Layer 2 |
+| ALCAP | Access Link Control Application Part |
+| APN | Access Point Name |
+| ATM | Asynchronous Transfer Mode |
+| BM-IWF | Broadcast Multicast Interworking Function |
+| BMC | Broadcast/Multicast Control |
+| BSS | Base Station Subsystem |
+| CBC | Cell Broadcast Centre |
+
+| | |
+|-------|---------------------------------------------|
+| CBS | Cell Broadcast Service |
+| CN | Core Network |
+| CRNC | Controlling Radio Network Controller |
+| DCH | Dedicated Channel |
+| DL | Downlink |
+| DRNS | Drift RNS |
+| DSP | Domain Specific Part |
+| EAB | Extended Access Barring |
+| E-DCH | Enhanced UL DCH |
+| EDGE | Enhanced Data rates for Global Evolution |
+| FACH | Forward Access Channel |
+| FFS | For Further Study |
+| GERAN | GSM EDGE Radio Access Network |
+| GSM | Global System for Mobile Communications |
+| GTP | GPRS Tunnelling Protocol |
+| GWCN | GateWay Core Network |
+| HPLMN | Home PLMN |
+| IDP | Initial Domain Part |
+| IPv4 | Internet Protocol, version 4 |
+| IPv6 | Internet Protocol, version 6 |
+| LA | Location Area |
+| MAC | Medium Access Control |
+| MBMS | Multimedia Broadcast Multicast Service |
+| MCCH | MBMS point-to-multipoint Control Channel |
+| MDT | Minimization of Drive-Tests |
+| MOCN | Multi Operator Core Network |
+| MRNC | MBMS Master Radio Network Controller |
+| MSCH | MBMS point-to-multipoint Scheduling Channel |
+| MTCH | MBMS point-to-multipoint Traffic Channel |
+| NACC | Network Assisted Cell Change |
+| NAS | Non Access Stratum |
+| NBAP | Node B Application Part |
+| NNSF | NAS Node Selection Function |
+| NSAP | Network Service Access Point |
+| PCH | Paging Channel |
+| PLMN | Public Land Mobile Network |
+| PTM | Point To Multipoint |
+| PTP | Point To Point |
+| QoS | Quality of Service |
+| RAB | Radio Access Bearer |
+| RACH | Random Access Channel |
+| RANAP | Radio Access Network Application Part |
+| RET | Remote Electrical Tilting |
+| RIM | RAN Information Management |
+| RNC | Radio Network Controller |
+| RNL | Radio Network Layer |
+| RNS | Radio Network Subsystem |
+| RNSAP | Radio Network Subsystem Application Part |
+| RNTI | Radio Network Temporary Identity |
+| SAB | Service Area Broadcast |
+| SAS | Stand-Alone SMLC |
+| SIPTO | Selected IP Traffic Offload |
+| SMLC | Serving Mobile Location Centre |
+| SNA | Shared Network Area |
+| SRNC | Serving Radio Network Controller |
+| SRNS | Serving RNS |
+| TMA | Tower Mounted Amplifier |
+| TBSS | Target BSS |
+| TEID | Tunnel Endpoint Identifier |
+| TMGI | Temporary Mobile Group Identity |
+| TNL | Transport Network Layer |
+| TTI | Transmission Time Interval |
+
+| | |
+|-------|--------------------------------------------|
+| UDP | User Datagram Protocol |
+| UE | User Equipment |
+| UL | Uplink |
+| UMTS | Universal Mobile Telecommunication System |
+| URA | UTRAN Registration Area |
+| USIM | UMTS Subscriber Identity Module |
+| UTRAN | Universal Terrestrial Radio Access Network |
+
+## 3.3 Notation
+
+For the purposes of the present document, the following notations apply:
+
+- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.
+- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD.
+- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.
+- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.
+- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.
+- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.
+- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.
+- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.
+- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.
+- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.
+- 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.
+
+| | |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IE | When referring to an information element (IE) in the specification, the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Transport Format Set IE . |
+| Value of an IE | When referring to the value of an information element (IE) in the specification, the "Value" is enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)". |
+| 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. FACH FLOW CONTROL control frame. |
+
+# --- 4 General principles
+
+The general principles guiding the definition of UTRAN Architecture as well as the UTRAN interfaces are the following:
+
+- Logical separation of signalling and data transport networks.
+- UTRAN and CN functions are fully separated from transports functions. Addressing scheme used in UTRAN and CN shall not be tied to the addressing schemes of transport functions. The fact that some UTRAN or CN function resides in the same equipment as some transport functions does not make the transport functions part of the UTRAN or the CN.
+- [FDD - Macro diversity is fully handled in the UTRAN.]
+- Mobility for RRC connection is fully controlled by the UTRAN.
+- When defining the UTRAN interfaces the following principles were followed: The functional division across the interfaces shall have as few options as possible.
+- Interfaces should be based on a logical model of the entity controlled through this interface.
+- One Physical Network Element can implement multiple Logical Nodes.
+
+Transport Network Control Plane is a functional plane in the interfaces protocol structure that is used for the transport bearer management. The actual signalling protocol that is in use within the Transport Network Control Plane depends on the underlying transport layer technology. The intention is not to specify a new UTRAN specific Application Part for the Transport Network Control Plane but to use signalling protocols standardised in other groups (if needed) for the applied transport layer technology.
+
+# --- 5 UMTS General architecture
+
+## 5.1 Overview
+
+Figure 1 shows a simplified UMTS architecture with the external reference points and interfaces to the UTRAN.
+
+
+
+Diagram illustrating the UMTS Architecture. It shows three main components stacked vertically: CN (Core Network) at the top, UTRAN (UMTS Terrestrial Radio Access Network) in the middle, and UE (User Equipment) at the bottom. The CN is connected to the UTRAN via the Iu interface. The UTRAN is connected to the UE via the Uu interface.
+
+UTRAN UMTS Terrestrial Radio Access Network
+ CN Core Network
+ UE User Equipment
+
+Figure 1: UMTS Architecture diagram showing CN (Core Network) connected to UTRAN (UMTS Terrestrial Radio Access Network) via the Iu interface, and UTRAN connected to UE (User Equipment) via the Uu interface.
+
+**Figure 1: UMTS Architecture**
+
+## 5.2 General protocols architecture
+
+The protocols over Uu and Iu interfaces are divided into two structures:
+
+### - **User plane protocols**
+
+These are the protocols implementing the actual radio access bearer service, i.e. carrying user data through the access stratum.
+
+### - **Control plane protocols**
+
+These are the protocols for controlling the radio access bearers and the connection between the UE and the network from different aspects (including requesting the service, controlling different transmission resources, handover & streamlining etc.). Also a mechanism for transparent transfer of NAS messages is included.
+
+### 5.2.1 User plane
+
+The radio access bearer service is offered from SAP to SAP by the Access Stratum. Figure 2 shows the protocols on the Uu and Iu interfaces that linked together provide this radio access bearer service.
+
+
+
+Diagram illustrating the Iu and Uu User plane. The diagram shows the protocol stack across the UE, UTRAN, and CN. The stack is divided into two main strata: Non-Access Stratum (NAS) and Access Stratum (AS). The NAS contains Radio protocols (1) in the UE, Radio protocols (1) and Iu protocols (2) in the UTRAN, and Iu protocols (2) in the CN. The AS contains the Radio (Uu) interface between the UE and UTRAN, and the Iu interface between the UTRAN and CN.
+
+Figure 2: Iu and Uu User plane diagram showing the protocol stack across the UE, UTRAN, and CN. The diagram is divided into Non-Access Stratum (NAS) and Access Stratum (AS). The NAS contains Radio protocols (1) in the UE, Radio protocols (1) and Iu protocols (2) in the UTRAN, and Iu protocols (2) in the CN. The AS contains the Radio (Uu) interface between the UE and UTRAN, and the Iu interface between the UTRAN and CN.
+
+- (1) The radio interface protocols are defined in documents TS 25.2xx and TS 25.3xx.
+- (2) The Iu interface protocols are defined in documents TS 25.41x.
+
+**Figure 2: Iu and Uu User plane**
+
+### 5.2.2 Control plane
+
+Figure 3 shows the control plane (signalling) protocol stacks on Iu and Uu interfaces.
+
+
+
+The diagram illustrates the control plane protocol stacks for the Uu and Iu interfaces. It is divided into two main horizontal layers: the Non-Access Stratum (NAS) at the top and the Access Stratum (AS) below. The NAS contains three protocol boxes labeled 'CM, MM, GMM, SM (3)'. The AS is further divided into three vertical sections representing the User Equipment (UE), the Radio Network Subsystem (UTRAN), and the Core Network (CN). The UE section contains a box for 'Radio protocols (1)'. The UTRAN section contains two boxes: 'Radio protocols (1)' and 'Iu protocols (2)'. The CN section contains a box for 'Iu protocols (2)'. Arrows indicate the flow of signalling: from the NAS in the UE down to the Radio protocols, then horizontally through the UTRAN Radio protocols to the Iu protocols, and finally up to the NAS in the CN. Vertical double-headed arrows connect the NAS to the AS in both the UE and CN. The interfaces are labeled at the bottom: 'Radio (Uu)' between UE and UTRAN, and 'Iu' between UTRAN and CN.
+
+Figure 3: Iu and Uu Control plane diagram showing protocol stacks for UE, UTRAN, and CN across Non-Access Stratum and Access Stratum layers.
+
+- (1) The radio interface protocols are defined in documents TS 25.2xx and TS 25.3xx.
+- (2) The protocol is defined in documents TS 25.41x. (Description of Iu interface).
+- (3) **CM, MM, GMM, SM:** This exemplifies a set of NAS control protocols between UE and CN. There may be different NAS protocol stacks in parallel. The evolution of the protocol architecture for these protocols is outside the scope of the present document.
+
+**Figure 3: Iu and Uu Control plane**
+
+NOTE: Both the Radio protocols and the Iu protocols contain a mechanism to transparently transfer NAS messages.
+
+# 6 UTRAN Architecture
+
+The UTRAN consists of a set of Radio Network Subsystems connected to the Core Network through the Iu.
+
+A RNS consists of a Radio Network Controller one or more Node Bs and optionally one SAS. A Node B is connected to the RNC through the Iub interface.
+
+A Node B can support FDD mode, TDD mode or dual-mode operation.
+
+There are three chip-rate options in the TDD mode: 7.68 Mcps TDD, 3.84 Mcps TDD and 1.28 Mcps TDD. Each TDD cell supports one of these options.
+
+A Node B which supports TDD cells can support one chip-rate option only, or more than one option.
+
+A RNC which supports TDD cells can support one chip-rate option only, or more than one option.
+
+The RNC is responsible for the Handover decisions that require signalling to the UE.
+
+A RNC may include a combining/splitting function to support combination/splitting of information streams (see subclause 7.2.4.3).
+
+Inside the UTRAN, the RNCs of the Radio Network Subsystems can be interconnected together through the Iur. Iu(s) and Iur are logical interfaces. Iur can be conveyed over direct physical connection between RNCs or virtual networks using any suitable transport network.
+
+The UTRAN architecture is shown in figure 4.
+
+
+
+This diagram illustrates the UTRAN architecture. At the top, a 'Core Network' block is connected to two 'RNC' (Radio Network Controller) blocks via 'Iu' interfaces. Both RNCs are part of a 'UTRAN' (Universal Terrestrial Radio Access Network). Each RNC is connected to two 'Node B' (Base Station) blocks via 'Iub' interfaces. Each Node B is represented by a rectangle containing three small circles. The RNCs are interconnected by an 'Iur' interface. The entire UTRAN section is enclosed in a dashed box, and each RNC and its associated Node Bs are grouped into separate dashed boxes labeled 'RNS' (Radio Network Subsystem).
+
+Figure 4: UTRAN Architecture diagram
+
+**Figure 4: UTRAN Architecture**
+
+Regarding the UE positioning method, the RNC may have full internal support for this function and/or may be connected to one SAS via the Iupc interface. The following picture illustrates the resulting UTRAN architecture when the Iupc interface is adopted.
+
+
+
+This diagram shows the UTRAN architecture with the Iupc option. It is similar to Figure 4, but the left RNC is additionally connected to an 'SAS' (Serving AS) block via an 'Iupc' interface. The right RNC remains connected to the 'Core Network' via an 'Iu' interface. All other connections, including 'Iur' between RNCs and 'Iub' between RNCs and Node Bs, are maintained. The layout of the RNS and UTRAN dashed boxes is consistent with Figure 4.
+
+Figure 4a: UTRAN Architecture with the Iupc option diagram
+
+**Figure 4a: UTRAN Architecture with the Iupc option**
+
+The RNC may be connected to BSS supporting GERAN Iu mode via the Iur-g interface. The following picture illustrates the UTRAN and GERAN Iu mode connection when the Iur-g interface is adopted. For 1.28Mcps TDD, the RNC may be connected to BSS supporting GERAN A/Gb mode via the Iur-g interface. The figure 4c illustrates the UTRAN and GERAN A/Gb mode connection when the Iur-g interface is adopted for 1.28Mcps TDD.
+
+
+
+This diagram illustrates the network architecture for UTRAN and GERAN Iu mode connection with Iur-g. At the top is a 'Core Network' block. Below it, a 'GERAN BSS' block is connected to the Core Network via an 'Iu' interface. To the right, an 'RNS' (Radio Network Subsystem) block is also connected to the Core Network via an 'Iu' interface. The 'GERAN BSS' and the 'RNS' are connected to each other via an 'Iur-g' interface. Inside the 'RNS' block, there is an 'RNC' (Radio Network Controller) block at the top, which is connected to two 'Node B' blocks (represented by rectangles with three circles below them) via 'Iub' interfaces.
+
+Figure 4b: UTRAN and GERAN Iu mode connection with Iur-g
+
+**Figure 4b: UTRAN and GERAN Iu mode connection with Iur-g**
+
+
+
+This diagram illustrates the network architecture for UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD. At the top is a 'Core Network' block. Below it, a 'GERAN BSS' block is connected to the Core Network via 'A' and 'Gb' interfaces. To the right, an 'RNS' block is connected to the Core Network via an 'Iu' interface. The 'GERAN BSS' and the 'RNS' are connected to each other via an 'Iur-g' interface. Inside the 'RNS' block, there is an 'RNC 1.28Mcps TDD' block at the top, which is connected to two 'Node B' blocks (represented by rectangles with three circles below them) via 'Iub' interfaces.
+
+Figure 4c: UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD
+
+**Figure 4c: UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD**
+
+Each RNS is responsible for the resources of its set of cells.
+
+For each connection between User Equipment and the UTRAN, One RNS is the Serving RNS. When required, Drift RNSs support the Serving RNS by providing radio resources as shown in figure 5. The role of an RNS (Serving or Drift) is on a per connection basis between a UE and the UTRAN.
+
+
+
+This diagram illustrates the network architecture for Serving and Drift RNS. At the top is a 'Core Network' block. Below it, a 'DRNS' (Drift Radio Network Subsystem) block and an 'SRNS' (Serving Radio Network Subsystem) block are both connected to the Core Network via an 'Iu' interface. The 'DRNS' and the 'SRNS' are connected to each other via an 'Iur' interface. Inside the 'DRNS' block, there is a 'Cells' block (represented by a row of circles) which is connected to a 'UE' (User Equipment) block. Inside the 'SRNS' block, there is also a 'Cells' block (represented by a row of circles) which is connected to the 'UE' block.
+
+Figure 5: Serving and Drift RNS
+
+**Figure 5: Serving and Drift RNS**
+
+To support UE mobility between UTRAN and GERAN Iu mode, the Serving RNS may be connected to the DBSS and vice versa as illustrated in figures 5a and 5b. For 1.28Mcps TDD, to support UE mobility between UTRAN and
+
+GERAN A/Gb mode, the Serving RNS may be connected to the TBSS as illustrated in figure 5c. The role of an RNS or BSS (Serving or Drift) is on a per connection basis between a UE and the UTRAN/Iu mode, or between a UE and the UTRAN/GERAN A/Gb mode for 1.28Mcp TDD.
+
+
+
+```
+
+graph TD
+ CN[Core Network] -- Iu --> SRNS[SRNS]
+ CN -- Iu --> DBSS[DBSS]
+ DBSS -- Iur-g --> SRNS
+ DBSS -- Cell --> MS[MS]
+
+```
+
+Figure 5a: Serving RNS and Drift BSS, GERAN Iu mode. The diagram shows a Core Network at the top connected via an Iu interface to an SRNS (Serving RNS) and a DBSS (Drift BSS). The DBSS is connected to a Cell, which is in turn connected to an MS (Mobile Station). The SRNS and DBSS are connected via an Iur-g interface.
+
+**Figure 5a: Serving RNS and Drift BSS, GERAN Iu mode**
+
+
+
+```
+
+graph TD
+ CN[Core Network] -- Iu --> SBSS[SBSS]
+ CN -- Iu --> DRNC[DRNC]
+ DRNC -- Iur-g --> SBSS
+ DRNC -- Cell --> UE[UE]
+
+```
+
+Figure 5b: Serving BSS and Drift RNS, GERAN Iu mode. The diagram shows a Core Network at the top connected via an Iu interface to an SBSS (Serving BSS) and a DRNC (Drift RNC). The DRNC is connected to a Cell, which is in turn connected to a UE (User Equipment). The SBSS and DRNC are connected via an Iur-g interface.
+
+**Figure 5b: Serving BSS and Drift RNS, GERAN Iu mode**
+
+
+
+```
+
+graph TD
+ CN[Core Network] -- Iu --> SRNS[SRNS 1.28Mcps TDD]
+ CN -- Iu --> TBSS[TBSS]
+ TBSS -- Iur-g --> SRNS
+ TBSS -- Cell --> MS[MS]
+
+```
+
+Figure 5c: Serving RNS and Target BSS, GERAN A/Gb mode. The diagram shows a Core Network at the top connected via an Iu interface to an SRNS 1.28Mcps TDD (Serving RNS) and a TBSS (Target BSS). The TBSS is connected to a Cell, which is in turn connected to an MS (Mobile Station). The SRNS and TBSS are connected via an Iur-g interface.
+
+**Figure 5c: Serving RNS and Target BSS, GERAN A/Gb mode**
+
+The UTRAN is layered into a Radio Network Layer and a Transport Network Layer.
+
+The UTRAN architecture, i.e. the UTRAN logical nodes and interfaces between them, are defined as part of the Radio Network Layer.
+
+For each UTRAN interface (Iu, Iur, Iub, Iupc) the related transport network layer protocol and functionality is specified. The transport network layer provides services for user plane transport, signalling transport and transport of implementation specific O&M.
+
+An implementation of equipment compliant with the specifications of a certain interface shall support the Radio Network Layer protocols specified for that interface. It shall also as a minimum, for interoperability, support the transport network layer protocols according to the transport network layer specifications for that interface.
+
+The network architecture of the transport network layer is not specified by 3GPP and is left as an operator issue.
+
+The equipment compliant to 3GPP standards shall at least be able to act as endpoints in the transport network layer, and may also act as a switch/router within the transport network layer.
+
+For implementation specific O&M signalling to the Node B, only the transport network layer protocols are in the scope of UTRAN specifications.
+
+
+
+The diagram illustrates the protocol layering between the Radio Network Layer (RNL) and the Transport Layer (TL). The RNL contains the following entities: Node B Management System, Node B, CRNC/DRNC/MRNC, SBSS, DBSS, SAS, and CN. The TL contains the following networks and links: O&M Network (25.442), Signalling Link 25.432, UP Transport (25.414, 25.424, 25.426, 25.434), Signalling Network (25.412, 25.422, 25.4x2), and Iu PS UP Network (25.414). The interfaces shown are Iub, Iur, Iur-g, Iu, Iupc, and Iup-g. The diagram shows how these interfaces connect to the appropriate transport networks or links.
+
+Figure 6: Protocol layering diagram showing the relationship between the Radio Network Layer and the Transport Layer. The Radio Network Layer contains Node B Management System, Node B, CRNC/DRNC/MRNC, SBSS, DBSS, SAS, and CN. The Transport Layer contains O&M Network (25.442), Signalling Link 25.432, UP Transport (25.414, 25.424, 25.426, 25.434), Signalling Network (25.412, 25.422, 25.4x2), and Iu PS UP Network (25.414). Interfaces shown include Iub, Iur, Iur-g, Iu, Iupc, and Iup-g.
+
+Figure 6: Protocol layering
+
+Figure 6 illustrates which parts of the transport network layer that may be (but are not mandated to be) configured by the operator as transport networks, i.e. the radio network layer provides a destination address, namely:
+
+- Transport network for implementation specific O&M traffic;
+- Signalling network for Iu, Iur, Iur-g and Iupc;
+- Transport network for Iub, Iur and Iu CS user plane connections;
+- Transport network for Iu PS user plane connections.
+
+The signalling link for Iub signalling as seen by the radio network layer cannot be configured as a network (no address provided).
+
+A transport network for UTRAN may be configured by the operator to be used also for other traffic than UTRAN traffic.
+
+## 6.1 UTRAN Identifiers
+
+### 6.1.1 PLMN Identity
+
+A Public Land Mobile Network is uniquely identified as defined in TS 23.003 [6] subclause 12.1.
+
+### 6.1.2 CN Domain Identifier
+
+A CN Domain Edge Node is identified as defined in TS 23.003 [6] sub-clause 12.2.
+
+### 6.1.3 RNC Identifier
+
+An RNC node is uniquely identified by its RNC Identifier among the nodes in UTRAN and GERAN Iu mode as defined in TS 23.003 [6] sub-clause 12.3. A BSS node in GERAN Iu mode is uniquely identified by its RNC Identifier among the nodes in GERAN Iu mode and UTRAN.
+
+### 6.1.4 Service Area Identifier
+
+The Service Area Identifier (SAI) is defined in TS 23.003 [6] sub-clause 12.4.
+
+### 6.1.5 Cell Identifier
+
+The Cell identifier (C-Id) is used to uniquely identify a cell within an RNS/BSS. The Cell-Id together with the identifier of the controlling RNC/BSS (CRNC-Id) constitutes the UTRAN/GERAN Cell Identity (UC-Id) and is used to identify the cell uniquely within UTRAN/GERAN Iu mode. UC-Id or C-Id is used to identify a cell in UTRAN Iub and Iur interfaces or Iur-g interface.
+
+- **UC-Id = RNC-Id + C-Id.**
+
+The C-Id is defined by the operator, and set in the RNC/BSS via O&M. The C-Id is set in a Node B by its C-RNC or in the GERAN Iu mode cell.
+
+### 6.1.6 Local Cell Identifier
+
+The Local Cell identifier is used to uniquely identify the set of resources within a Node B required to support a cell (as identified by a C-Id). As a minimum it shall be unique within the Node B, but it is also capable of supporting uniqueness within the UTRAN for management system purposes.
+
+The Local Cell Identifier is used for the initial configuration of a Node B when no C-Id is defined. The Local Cell identifier is defined by the operator, and set in both the Node B and its C-RNC via O&M. The relationship between the Local Cell Identifier and C-Id is set in the C-RNC via O&M.
+
+### 6.1.7 UE Identifiers
+
+Radio Network Temporary Identities (RNTI) are used as UE identifiers within UTRAN/GERAN Iu mode and in signalling messages between UE and UTRAN/GERAN Iu mode.
+
+Six types of RNTI exist:
+
+- 1) Serving RNC/BSS RNTI (s-RNTI);
+- 2) Drift RNC/BSS RNTI (d-RNTI);
+- 3) Cell RNTI (c-RNTI);
+- 4) UTRAN/GERAN RNTI (u-RNTI);
+- 5) [TDD – DSCH RNTI (DSCH-RNTI)];
+- 6) HS-DSCH RNTI (HS-DSCH RNTI);
+- 7) E-DCH RNTI (E-RNTI);
+
+#### **s-RNTI is used:**
+
+- by UE to identify itself to the Serving RNC/BSS;
+- by SRNC/SBSS to address the UE/MS;
+- by DRNC/DBSS to identify the UE to Serving RNC.
+
+s-RNTI is allocated for all UEs having a RRC connection, it is allocated by the Serving RNC/BSS and it is unique within the Serving RNC/BSS. s-RNTI is reallocated always when the Serving RNC/BSS for the RRC connection is changed.
+
+#### **d-RNTI is used:**
+
+- by serving RNC/BSS to identify the UE to Drift RNC/BSS.
+
+NOTE: The d-RNTI is never used on Uu.
+
+d-RNTI is allocated by drift RNC/BSS upon drift UE contexts establishment and it shall be unique within the drift RNC/BSS. Serving RNC/BSS shall know the mapping between s-RNTI and the d-RNTIs allocated in Drift RNCs/BSSs for the same UE. Drift RNC/BSS shall know the s-RNTI and SRNC-ID related to existing d-RNTI within the drift RNC/BSS.
+
+#### **c-RNTI is used:**
+
+- by UE to identify itself to the controlling RNC;
+- by controlling RNC to address the UE.
+
+c-RNTI is allocated by controlling RNC upon UE accessing a new cell. C-RNTI shall be unique within the accessed cell. Controlling RNC shall know the d-RNTI associated to the c-RNTI within the same logical RNC (if any).
+
+#### **u-RNTI**
+
+The u-RNTI is allocated to an UE having a RRC connection and identifies the UE within UTRAN/GERAN Iu mode.
+
+u-RNTI is composed of:
+
+- SRNC identity;
+- s-RNTI.
+
+#### **[TDD – DSCH-RNTI is used:]**
+
+- [TDD – by controlling RNC to address the UE on the DSCH and USCH].
+
+[TDD – DSCH-RNTI is allocated by controlling RNC upon UE establishing a DSCH or USCH channel. DSCH-RNTI shall be unique within the cell carrying the DSCH and/or USCH. DSCH-RNTI is used as UE identifier in RRC messages concerning DSCH and USCH allocations and is used in both the downlink and uplink.
+
+#### **HS-DSCH RNTI is used:**
+
+- for the UE specific CRC in HS-SCCH and HS-PDSCH.
+
+HS-DSCH RNTI is allocated by controlling RNC upon UE establishing a HS-DSCH channel. HS-DSCH RNTI shall be unique within the cell carrying the HS-DSCH.
+
+#### **E-RNTI is used:**
+
+- for the UE[FDD - /UE group] specific CRC in E-AGCH.
+
+E-DCH RNTI is allocated by NodeB upon UE establishing an E-DCH channel. E-DCH RNTI allocated to a UE [FDD - /UE group] shall be unique within the cell carrying the E-DCH.
+
+Each RNC has a unique identifier within the UTRAN part of the PLMN, denoted by RNC identifier (RNC-ID). This identifier is used to route UTRAN interface messages to correct RNC. RNC-ID of the serving RNC together with the s-RNTI is a unique identifier of the UE in the UTRAN part of the PLMN.
+
+#### 6.1.7.1 Usage of RNTI
+
+u-RNTI is used as a UE identifier for the first cell access (at cell change) when a RRC connection exists for this UE and for UTRAN originated paging including associated response messages. RNC-ID is used by Controlling RNC/BSS to route the received uplink messages towards the Serving RNC/BSS.
+
+NOTE: For the initial access a unique core network UE identifier is used.
+
+c-RNTI is used as a UE identifier in all other DCCH/DTCH common channel messages on air interface.
+
+### 6.1.7a UE Identifiers in GERAN A/Gb mode (1.28Mcps TDD)
+
+Radio Network Temporary Identity (RNTI) is used as a UE identifier within UTRAN /GERAN A/Gb mode and in signalling messages between UE and UTRAN /GERAN A/Gb mode. One type of RNTI exists:
+
+- Drift RNTI (D-RNTI)
+
+The D-RNTI is allocated by the TBSS and is used to identify the UE during a handover via the Iur-g interface.
+
+There is one possible scenario in which the D-RNTI is used:
+
+- The serving RAN node is a UTRAN RNC and the target RAN node is a GERAN BSS in A/Gb mode.
+
+### 6.1.8 Identifiers for dedicated resources within UTRAN
+
+#### 6.1.8.1 Radio Network Control Plane identifiers
+
+Each addressable object in each reference point has an application part level identifier. This identifier is allocated autonomously by the entity responsible for initiation of the setup of the object. This application part identifier will be used as a reference to the object that is setup. Both ends of the reference point shall memorise the AP Identifier during the lifetime of the object. Application part identifier can be related to a specific Transport Network identifier and that relationship shall also be memorised by both ends.
+
+Table 1 lists the basic AP level identifiers in each reference point.
+
+**Table 1: Basic AP level identifiers in each reference point**
+
+| Object | Identifier | Abbreviation | Valid for |
+|---------------------------------|------------------------|--------------|-----------|
+| Radio Access Bearer | Radio Access Bearer ID | RAB-ID | Iu |
+| Dedicated Transport channel | DCH-ID | DCH-ID | Iur, Iub |
+| [TDD – Downlink Shared Channel] | DSCH-ID | DSCH-ID | Iur, Iub |
+| [TDD – Uplink Shared Channel] | USCH-ID | USCH-ID | Iur, Iub |
+
+#### 6.1.8.2 Transport Network Identifiers
+
+Transport Network identifiers are used in the Transport Network Layer (TNL) to identify the transport bearer and may be used in User Plane in the actual data transmission using the transport link. The Transport Network identifier identifies the transport link according to the naming conventions defined for the transport link type in question. Both ends of the reference point of the concerned TNL shall memorise the Transport Network identifiers during the lifetime of the transport link. Each Transport Network identifier can be bound to an Application Part identifier.
+
+The Transport Network identifiers vary depending on the transport link type.
+
+Table 2 indicates examples of the identifiers used for different transmission link types.
+
+**Table 2: Examples of the identifiers used for different transmission link types**
+
+| Transmission link type | Transport Network Identifier |
+|------------------------|------------------------------|
+| AAL2 | AAL2 Path ID + CID |
+| GTP over IP | IP address + TEID |
+| UDP over IP | IP address + UDP port |
+
+The communication of Transport Network identifiers is made in two ways:
+
+When an ALCAP is used, the transport layer address communicated via the Radio Network Layers protocols (NBAP, RNSAP, RANAP...) is a Transport Network Control Plane address and the Transport Network identifiers are communicated through this Transport Network Control Plane only.
+
+When no ALCAP is used, the Transport Network identifiers are directly communicated via the Radio Network Layers protocols (NBAP, RNSAP, RANAP...) on all interfaces.
+
+In both cases, the transport layer address (e.g. IP address) is encapsulated by the Transport Network Layer in the NSAP structure as defined in [Annex A of X.213, ISO/IEC 8348 [15], X.213/Amd. 1, ISO/IEC 8348 [16]] transported transparently on Iub, Iur and Iu-CS and passed transparently from the Radio Network Layer to the Transport Network Layer. The NSAP structure (encapsulation) is only used in order to provide to the TNL explicit identification of the type of the TNL address that is being conveyed by the given RNL protocol. It is then the responsibility of the Transport Network Layer to interpret this structure (e.g. to determine accordingly if the requested network type is ATM or IP).
+
+On the Iu-PS, the NSAP structure is not used in RANAP but the 'straight IP addressing' shall be used.
+
+The following scheme depicts the encapsulation of a native IPv6 (IETF RFC 2460 [12]) address in NSAP structure when conveyed in RANAP, RNSAP and NBAP.
+
+
+
+| Octet 1 | octet 2 | octet 3 | octet 4 |
+|--------------------|-----------------------|---------|-----------------|
+| AFI=35 (IANA) | ICP=0 (embedded IPv6) | | IPv6 (byte 1) |
+| IPv6 (bytes 2-5) | | | |
+| IPv6 (bytes 6-9) | | | |
+| IPv6 (bytes 10-13) | | | |
+| IPv6 (bytes 14-16) | | | 0 0 0 0 0 0 0 0 |
+
+**Figure 6A: IPv6 address embedded in NSAP structure in RANAP/RNSAP/NBAP.**
+
+Note 1: The last octet of the DSP (the DSP is the remaining octets after the IDP IETF RFC 4548 [34]) the encapsulation of a native IPv6 address in NSAP structure is unspecified.
+
+Note 2: The encapsulation of a native IPv4 address in NSAP structure when conveyed in RANAP, RNSAP and NBAP shall be encoded according to IETF RFC 4548 [34]. The last 13 octets of the DSP are unspecified.
+
+Note 3: The default values for the unspecified octets are zero.
+
+#### 6.1.8.3 Binding identifier
+
+Binding Identifier (Binding ID) is used to initialise the linkage between ALCAP and Application Part (RANAP, RNSAP, NBAP) identifiers. Binding identifier can be used both in Radio Network Control plane Application Part protocols and in Transport Network Control Plane's ALCAP protocol. When no ALCAP is used, Binding ID may also be used to carry the UDP port on Iub, Iur and Iu-CS interfaces.
+
+Binding ID binds the Radio and Transport Network Control plane identifiers together. To ensure maximal independence of those two planes, the binding ID should be used only when necessary: Binding ID shall thus be used only in Radio Network Control plane Application Part messages in which a new association between the planes is created and in ALCAP messages creating new transport bearers.
+
+Binding ID for each transport bearer shall be allocated before the setup of that transport bearer.
+
+The Binding ID is sent on one direction using the Application Part protocol and is return in the other direction by the ALCAP protocol.
+
+When an Application Part procedure with an allocated Binding ID is applied for modifying an existing Radio Network User Plane connection, the decision to use the Binding ID (and the ALCAP procedures) shall be done by that end of the reference point that decides whether to use the existing transport bearer or to set up a new transport bearer.
+
+The Binding ID shall already be assigned and tied to a radio application procedure when the first ALCAP message is received in a node.
+
+The association between the connection Id in the Application Part protocol (e.g. identifying a RAB) and the corresponding connection Id in the ALCAP protocol (e.g. identifying the AAL2 channel for that RAB) that was created with the help of Binding ID shall be memorised by both peers of each reference point for the lifetime of the corresponding transport bearer.
+
+The Binding ID may be released and re-used as soon as both the Application Part procedure and the ALCAP procedure that used it are completed in both peers of the reference point.
+
+Figure 6a illustrates how application instances of the Radio Network Control Plane and instances of the Transport Network Plane are linked together through the Binding Identifier in the set-up phase.
+
+![Figure 6a: Usage of Binding ID. A sequence diagram showing three steps between two nodes, AP-1 and AP-2, and their corresponding ALCAP entities (ALCAP-1 and ALCAP-2). Step 1: AP-1 sends a 'Radio Network Control Plane Setup (Response)' message to AP-2, containing '[Node 1 Transport Address, Binding ID]'. Step 2: AP-2 sends a request to ALCAP-2, containing 'Node 1 Transport Address, Binding ID'. Step 3: ALCAP-2 sends an 'ALCAP Establish Request' message to ALCAP-1, containing '[Node 1 Transport Address, Binding ID]'. Dashed arrows indicate the flow of the Binding ID between the Application Parts and the ALCAP entities.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg)
+
+Figure 6a: Usage of Binding ID. A sequence diagram showing three steps between two nodes, AP-1 and AP-2, and their corresponding ALCAP entities (ALCAP-1 and ALCAP-2). Step 1: AP-1 sends a 'Radio Network Control Plane Setup (Response)' message to AP-2, containing '[Node 1 Transport Address, Binding ID]'. Step 2: AP-2 sends a request to ALCAP-2, containing 'Node 1 Transport Address, Binding ID'. Step 3: ALCAP-2 sends an 'ALCAP Establish Request' message to ALCAP-1, containing '[Node 1 Transport Address, Binding ID]'. Dashed arrows indicate the flow of the Binding ID between the Application Parts and the ALCAP entities.
+
+- Step 1: Application Part AP-1 assigns the Binding Identifier and sends a Radio Network Control Plane Set-up (Response) message (which of the two messages depends on the involved interface - lu/lur or lub). The message contains the originating node Transport layer address and the Binding Identifier.
+- Step 2: Among reception of the Radio Network Control Plane Set-up message, the peer entity AP-2 requests ALCAP-2 to establish a transport bearer. The Binding Identifier is passed to ALCAP-2.
+- Step 3: ALCAP-2 sends an ALCAP Establish Request to the peer entity ALCAP-1. The message contains the Binding Identifier. The Binding Identifier allows correlating the incoming transport connection with the Application Part transaction in step 1.
+
+**Figure 6a: Usage of Binding ID**
+
+Table 3 indicates the binding identifier allocating entity in each interface.
+
+**Table 3: Binding identifier allocating entity in each interface**
+
+| Reference point | Allocating entity | Application part message including Binding-ID |
+|-----------------|-------------------|-----------------------------------------------|
+| lu | CN | Request from CN |
+| lur | DRNC | Response to the request from SRNC |
+| lub | Node-B | Response to the request from DRNC |
+
+### 6.1.9 URA Identity
+
+The URA identity is used to uniquely identify an URA, which is a specified set of UTRAN and/or GERAN cells. The URA identity can be used to indicate to the UE and the SRNC which URA it shall use in case there are multiple URA identities broadcast in the cell where the UE is located.
+
+### 6.1.10 Service Identifiers for MBMS
+
+#### 6.1.10.1 IP Multicast Address and APN
+
+The IP Multicast Address and an APN are used to enable the routing of MBMS registration requests within the CN. These identifiers are transparent to RAN.
+
+#### 6.1.10.2 TMGI
+
+The Temporary Mobile Group Identity (TMGI) is used for group notification purposes and is unique within HPLMN. TMGI is used at the start of a session and at UE linking to identify an MBMS Bearer Service.
+
+The structure of TMGI is specified in TS 23.003 [6].
+
+#### 6.1.10.3 Session Identifier
+
+MBMS session Identifier is used to identify one specific session of a MBMS service and is forwarded transparently to the UE.
+
+#### 6.1.10.4 MBMS Service Area
+
+The MBMS Service Area is defined in TS 25.413 [31].
+
+The mapping between a MBMS Service Area and a list of cells is set in the RNC via O&M.
+
+#### 6.1.10.5 MBMS Cell Group Identifier
+
+The MBMS Cell Group Identifier is defined in TS 25.346 [30]
+
+#### 6.1.10.6 MBMS UTRAN Cell Group Identifier
+
+Void.
+
+### 6.1.11 Transport Network Identifiers for MBMS
+
+Transport Network identifiers are used in the Transport Network Layer (TNL) to identify the MBMS transport bearers and may be used in User Plane in the actual MBMS data transmission using the transport link. Each MBMS Transport Network identifier can be bound to an Application Part identifier. The Application Part identifier over the Iu interface is the TMGI corresponding to one MBMS Bearer Service.
+
+The handling of the MBMS Transport Network identifiers is the same as the handling of Transport Network identifiers for dedicated resources described in section 6.1.8.2.
+
+### 6.1.12 Binding Identifiers for MBMS
+
+Binding identifiers can be used for MBMS both in Radio Network Control plane Application Part protocols and in Transport Network Control Plane's ALCAP protocol. When ALCAP is used, Binding Identifiers (Binding ID) are used to initialise the linkage between ALCAP and the MBMS Application Part (RNSAP, NBAP) identifiers. When no ALCAP is used, the Binding ID may also be used to carry the UDP port on Iub and Iur interfaces.
+
+The handling of the MBMS Binding identifiers is the same as the handling of Binding identifiers for dedicated resources described in section 6.1.8.3.
+
+### 6.1.13 Use of Extended Identifiers
+
+The use and deployment of extended RNC-ID and extended S-RNTI in deployments is described in Annex A2.
+
+## 6.2 Transport Addresses
+
+The transport layer address parameter is transported in the radio network application signalling procedures that result in establishment of transport bearer connections.
+
+The transport layer address parameter shall not be interpreted in the radio network application protocols and reveal the addressing format used in the transport layer.
+
+The formats of the transport layer addresses are further elaborated in TS 25.414 [9], TS 25.424 [10], TS 25.434 [11], TS 25.426 [18].
+
+## 6.3 Function Distribution Principles
+
+For radio resource management functionality, the following principles apply:
+
+- The CRNC owns the radio resources of a cell.
+- The SRNC handles the connection to one UE, and may borrow radio resources of a certain cell from the CRNC.
+- When used, the MRNC controls the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s).
+
+Dynamical control of power for dedicated channels, within limits admitted by CRNC, is done by the SRNC.
+
+- Dynamic control on smaller time-scale for some radio links of the UE connection may be done by the Node B. This “inner loop” control is controlled by an “outer loop”, for which the SRNC has overall responsibility.
+- Scheduling of data for dedicated channels is done by the SRNC, while for common channels it is done by the CRNC.
+
+For management of node-internal resources, the following principle apply:
+
+- Each UTRAN node is considered a network element on its own. The knowledge about the equipment of a network element is kept within the network element itself and its management system. The node itself always manages node-internal resources.
+
+For transport network resource management, the following principle apply:
+
+- Management of transport network resources belong to the Transport Layer. Mechanisms relevant for the selected transport technology are used. No functional split between UTRAN nodes is specified what regards the Transport Layer.
+
+As a general guideline, the UTRAN protocols should be designed in such a way that they minimise the need for a DRNC to interpret the user plane frame protocol information other than for the combining/splitting purpose.
+
+# --- 7 UTRAN Functions description
+
+## 7.1 List of functions
+
+- Transfer of User Data.
+- Functions related to overall system access control:
+ - Admission Control;
+ - Congestion Control;
+ - System information broadcasting.
+- Radio channel ciphering and deciphering.
+- Integrity protection.
+- Functions related to mobility:
+ - Handover;
+ - SRNS Relocation;
+ - Paging support;
+ - Positioning;
+
+- GERAN System Information Retrieval;
+- Enhanced SRNS Relocation.
+- Functions related to radio resource management and control:
+ - Radio resource configuration and operation;
+ - Radio environment survey;
+ - Combining/splitting control;
+ - Connection set-up and release;
+ - Allocation and deallocation of Radio Bearers;
+ - [TDD - Dynamic Channel Allocation (DCA)];
+ - Radio protocols function;
+ - RF power control;
+ - [3.84 Mcps TDD and 7.68Mcps TDD - Timing Advance];
+ - [1.28 Mcps TDD – Uplink Synchronisation];
+ - Radio channel coding;
+ - Radio channel decoding;
+ - Channel coding control;
+ - Initial (random) access detection and handling;
+ - CN Distribution function for Non Access Stratum messages.
+- Synchronisation.
+- Functions related to broadcast and multicast services (see note) (broadcast/multicast interworking function BM-IWF).
+
+NOTE: Only Broadcast is applicable for Release 99.
+
+- Broadcast/Multicast Information Distribution.
+- Broadcast/Multicast Flow Control.
+- CBS Status Reporting.
+- Tracing.
+- MDT.
+- Volume reporting.
+- NAS Node Selection.
+- RAN Information Management.
+- MBMS provision.
+- MBMS Notification.
+- MOCN and GWCN configuration support.
+- SIPTO at Iu-PS (optional).
+- Explicit Congestion Notification.
+
+## 7.2 Functions description
+
+### 7.2.0 Transfer of user data
+
+This function provides user data transfer capability across the UTRAN between the Iu and Uu reference points.
+
+### 7.2.1 Functions related to overall system access control
+
+System access is the means by which a UMTS user is connected to the UTRAN in order to use UMTS services and/or facilities. User system access may be initiated from either the mobile side, e.g. a mobile originated call, or the network side, e.g. a mobile terminated call.
+
+#### 7.2.1.1 Admission Control
+
+The purpose of the admission control is to admit or deny new users, new radio access bearers or new radio links (for example due to handover). The admission control should try to avoid overload situations and base its decisions on interference and resource measurements. The admission control is employed at for example initial UE access, RAB assignment/reconfiguration and at handover. These cases may give different answers depending on priority and situation.
+
+The Admission Control function based on UL interference and DL power is located in the Controlling RNC.
+
+The Serving RNC is performing admission Control towards the Iu interface.
+
+#### 7.2.1.2 Congestion Control
+
+The task of congestion control is to monitor, detect and handle situations when the system is reaching a near overload or an overload situation with the already connected users. This means that some part of the network has run out, or will soon run out of resources. The congestion control should then bring the system back to a stable state as seamless as possible.
+
+NOTE: This admission Control function is related to Radio Resources.
+
+Congestion control is performed within UTRAN.
+
+The RNC may trigger EAB as specified in TS 23.060 [36] subclause 5.3.6.4 and TS 23.251[28] subclause 4.6.
+
+#### 7.2.1.3 System information broadcasting
+
+This function provides the mobile station with the Access Stratum and Non Access Stratum information which are needed by the UE for its operation within the network.
+
+The basic control and synchronisation of this function is located in UTRAN.
+
+#### 7.2.1.4 MOCN and GWCN configuration support
+
+In the MOCN configuration only the radio access part of the network is shared. For the MOCN configuration it is required that the rerouting function, as described in TS 25.410 [29], is supported.
+
+In the GWCN configuration, besides shared radio access network, the core network operators also share part of the core network, at least MSC and/or SGSN.
+
+For both the GWCN and MOCN configurations, the RNC carries the selected PLMN-id between network sharing supporting UEs and the corresponding CN.
+
+The network sharing MOCN and GWCN configurations are described in detail in TS 23.251 [28].
+
+### 7.2.2 Radio channel ciphering and deciphering
+
+This function is a pure computation function whereby the radio transmitted data can be protected against a non-authorised third-party. Ciphering and deciphering may be based on the usage of a session-dependent key, derived through signalling and/or session dependent information.
+
+This function is located in the UE and in the UTRAN.
+
+### 7.2.3 Functions related to Mobility
+
+#### 7.2.3.1 Handover
+
+This function manages the mobility of the radio interface. It is based on radio measurements and it is used to maintain the Quality of Service requested by the Core Network.
+
+Handover may be directed to/from another system (e.g. UMTS to GSM handover).
+
+The handover function may be either controlled by the network, or independently by the UE. Therefore, this function may be located in the SRNC, the UE, or both.
+
+#### 7.2.3.2 SRNS Relocation
+
+The SRNS Relocation function coordinates the activities when the SRNS role is to be taken over by another RNS/BSS. The SRNS relocation function manages the Iu interface connection mobility from an RNS to another RNS/BSS.
+
+
+
+Figure 7: Serving RNS Relocation. The diagram shows two states: 'Before SRNS Relocation' and 'After SRNS Relocation'. In both, a 'Core Network' is connected via an 'Iu' interface to an 'SRNS'. The 'SRNS' is connected to three 'Cells', which are in turn connected to a 'UE'. In the 'Before' state, the 'SRNS' is also connected via an 'Iur' interface to a 'DRNS', which has its own set of cells. In the 'After' state, the 'SRNS' is connected via an 'Iur' interface to an 'RNS', which has its own set of cells. The 'UE' is shown moving from the cells of the 'DRNS' in the 'Before' state to the cells of the 'RNS' in the 'After' state, while remaining connected to the 'SRNS'.
+
+**Figure 7: Serving RNS Relocation**
+
+The SRNS Relocation is initiated by the SRNC.
+
+This function is located in the RNC and the CN.
+
+#### 7.2.3.3 Paging support
+
+This function provides the capability to request a UE to contact the UTRAN/GERAN Iu mode when the UE is in Idle, CELL\_PCH or URA\_PCH/GRA\_PCH states (TS 25.331 [7], TR 43.930 [21]). This function also encompasses a coordination function between the different Core Network Domains onto a single RRC connection.
+
+#### 7.2.3.4 Positioning
+
+This function provides the capability to determine the geographic position and optionally the velocity of a UE.
+
+#### 7.2.3.5 NAS Node Selection Function
+
+The optional NAS Node Selection Function (NNSF) enables the RNC to initially assign CN resources to serve a UE and subsequently setup a signalling connection to the assigned CN resource.
+
+The NNSF is described in detail in TS 23.236 [20].
+
+#### 7.2.3.6 Shared Networks Access Control
+
+The Shared Networks Access Control function allows the CN to request the UTRAN to apply UE specific access control to LAs of the UTRAN and LAs of neighbouring networks.
+
+The Shared Networks Access Control function is based on either whole PLMNs or Shared Network Areas (SNAs). An SNA is an area corresponding to one or more LAs within a single PLMN to which UE access can be controlled.
+
+In order to apply Shared Networks Access Control for the UTRAN or for a neighbouring system, the UTRAN shall be aware of whether the concerned LA belongs to one (or several) SNA(s) or not.
+
+If access for a specific UE needs to be restricted, the CN shall provide SNA Access Information for that UE. The SNA Access Information indicates which PLMNs and/or which SNAs the UE is allowed to access.
+
+Based on whether the LA belongs to the PLMNs or SNAs the UE is allowed to access, the UTRAN determines if access to a certain LA for a certain UE shall be allowed.
+
+If access is not allowed, the UTRAN shall request the CN to release existing resources either by initiating Iu Release Request procedure with cause value "Access Restricted due to Shared Network" or by requesting a relocation with the same cause value.
+
+#### 7.2.3.7 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 RAN to request GERAN (via CN) to provide this system information.
+- The SRNC to request the DRNC (via Iur interface) to provide this system information, if available.
+
+The request and subsequent transfer of the GERAN System Information is performed transparently with the RIM function. The RIM function is further described in section 7.2.8.
+
+#### 7.2.3.8 Enhanced SRNS Relocation
+
+The Enhanced SRNS Relocation function coordinates the activities when the SRNS role is to be taken over by another RNS. The Enhanced SRNS Relocation function manages the Iu interface connection mobility from an RNS to another RNS.
+
+The Enhanced SRNS Relocation is initiated by the SRNC. The relocation of the SRNS functionality is prepared via RNSAP means. The CN is not informed until the preparation and execution of the relocation has taken place.
+
+This function is located in the RNC and the CN.
+
+#### 7.2.3.9 Subscriber Profile ID for RAT/Frequency Priority
+
+The RRM strategy in UTRAN may be based on user specific information.
+
+The Subscriber Profile ID for RAT/Frequency Priority (SPID) parameter received by the RNC via the Iu interface is an index referring to user information (e.g. mobility profile, service usage profile). The information is UE specific and applies to all its Radio Bearers.
+
+This index is mapped by the RNC to locally defined configuration in order to apply specific RRM strategies (e.g. to define RRC\_IDLE mode priorities and control inter-RAT/inter frequency handover in RRC\_CONNECTED mode).
+
+### 7.2.4 Functions related to radio resource management and control
+
+*Radio resource management* is concerned with the allocation and maintenance of radio communication resources. UMTS radio resources must be shared between circuit transfer mode services and packet transfer mode services (i.e. Connection-oriented and/or connectionless-oriented services).
+
+#### 7.2.4.1 Radio resource configuration and operation
+
+This function performs configures the radio network resources, i.e. cells and common transport channels, and takes the resources into or out of operation.
+
+#### 7.2.4.2 Radio environment survey
+
+This function performs measurements on radio channels (current and surrounding cells) and translates these measurements into radio channel quality estimates. Measurements may include:
+
+- 1) Received signal strengths (current and surrounding cells);
+- 2) Estimated bit error ratios, (current and surrounding cells);
+- 3) Estimation of propagation environments (e.g. high-speed, low-speed, satellite, etc.);
+- 4) Transmission range (e.g. through timing information);
+- 5) Doppler shift;
+- 6) Synchronisation status;
+- 7) Received interference level;
+- 8) Total DL transmission power per cell.
+
+This function is located in the UE and in the UTRAN.
+
+#### 7.2.4.3 Combining/splitting control
+
+This function controls the combining/splitting of information streams to receive/ transmit the same information through multiple physical channels (possibly in different cells) from/ towards a single mobile terminal.
+
+The UL combining of information streams may be performed using any suitable algorithm, for example:
+
+- [FDD - based on maximum ratio algorithm (maximum ratio combining)];
+- [FDD - based on quality information associated to each TBS (selection-combining)];
+- [TDD - based on the presence/absence of the signal (selection)].
+
+[FDD - combining/splitting control should interact with channel coding control in order to reduce the bit error ratio when combining the different information streams].
+
+In some cases, depending on physical network configuration, there may be several entities which combine the different information streams, i.e. there may be combining/splitting at the SRNC, DRNC or Node B level.
+
+This function is located in the UTRAN.
+
+#### 7.2.4.4 Connection set-up and release
+
+This function is responsible for the control of connection element set-up and release in the radio access sub network. The purpose of this function is:
+
+- 1) To participate in the processing of the end-to-end connection set-up and release;
+- 2) And to manage and maintain the element of the end-to-end connection, which is located in the radio access sub network.
+
+In the former case, this function will be activated by request from other functional entities at call set-up/release. In the latter case, i.e. when the end-to-end connection has already been established, this function may also be invoked to cater for in-call service modification or at handover execution.
+
+This function is located both in the UE and in the RNC.
+
+#### 7.2.4.5 Allocation and deallocation of Radio Bearers
+
+This function consists of translating the connection element set-up (resp. release) requests into physical radio channel allocation (resp. deallocation) accordingly to the QoS of the Radio Access Bearer.
+
+This function may be activated during the call since e.g. the user service request may vary, or macro diversity may be used.
+
+This function is located in the CRNC and SRNC.
+
+#### 7.2.4.6 [TDD - Dynamic Channel Allocation (DCA)]
+
+DCA is used in the TDD mode. It includes Fast DCA and Slow DCA. Slow DCA is the process of assigning radio resources, including time slots, to different TDD cells according to the varying cell load. Fast DCA is the process of assigning resources to Radio Bearers, and is related to Admission Control.
+
+#### 7.2.4.7 Radio protocols function
+
+This function provides user data and signalling transfer capability across the UMTS radio interface by adapting the services (according to the QoS of the Radio Access Bearer) to the Radio transmission. This function includes amongst other:
+
+- Multiplexing of services and multiplexing of UEs on Radio bearers;
+- Segmentation and reassembly;
+- Acknowledged/Unacknowledged delivery according to the Radio Access Bearer QoS.
+
+#### 7.2.4.8 RF power control
+
+This group of functions controls the level of the transmitted power in order to minimise interference and keep the quality of the connections. It consist of the following functions: UL Outer Loop Power Control, DL Outer Loop Power Control, UL Inner Loop Power Control, DL Inner Loop Power Control, UL Open Loop Power Control and DL Open Loop Power Control.
+
+##### 7.2.4.8.1 UL Outer Loop Power Control
+
+The UL Outer Loop Power Control located in the SRNC [TDD – except for uplink shared channels where it is located in the CRNC] sets the target quality value for the UL Inner Loop Power Control which is located in Node B for FDD and 1.28 Mcps TDD and is located in the UE for 3.84 Mcps and 7.68 Mcps TDD. It receives input from quality estimates of the transport channel. The UL outer loop power control is mainly used for a long-term quality control of the radio channel.
+
+In FDD and 1.28 Mcps TDD this function is located in the UTRAN, in 3.84 Mcps and 7.68 Mcps TDD the function is performed in UTRAN and the target quality value is sent to the UE by the SRNC or the CRNC, respectively.
+
+In FDD and 1.28 Mcps TDD, if the connection involves both a SRNS and a DRNS the function UL Outer Loop Power Control (located in the SRNC [1.28 Mcps TDD – or in the CRNC, respectively]) sets the target quality for the UL Inner Loop Power Control function (located in Node B).
+
+##### 7.2.4.8.2 DL Outer Loop Power Control
+
+The DL Outer Loop Power Control sets the target quality value for the DL inner loop power control. It receives input from quality estimates of the transport channel, measured in the UE. The DL outer loop power control is mainly used for a long-term quality control of the radio channel.
+
+This function is located mainly in the UE, but some control parameters are set by the UTRAN.
+
+The SRNC, regularly (or under some algorithms), sends the target down link power range based on the measurement report from UE.
+
+##### 7.2.4.8.3 UL Inner Loop Power Control
+
+The UL Inner Loop Power Control sets the power of the uplink dedicated [TDD – and shared] physical channels.
+
+In FDD, it is a closed loop process. It receives the quality target from UL Outer Loop Power Control and quality estimates of the uplink dedicated physical control channel. The power control commands are sent on the downlink dedicated physical control channel to the UE. This function is located in both the UTRAN and the UE.
+
+In 3.84 Mcps and 7.68 Mcps TDD it is a open loop process, it receives the quality target from the UL Outer Loop Power Control and uses the quality target and quality estimates of downlink channels to set the transmit power. This function is located in the UE.
+
+In 1.28 Mcps TDD, it is a closed loop process. It receives the quality target from UL Outer Loop Power Control, and quality estimates of the uplink dedicated physical channels as well as physical uplink shared channels, if any. The
+
+power control commands are sent on the downlink dedicated physical channels and physical downlink shared channels, if any, to the UE. This function is located in both the UTRAN and the UE.
+
+##### 7.2.4.8.4 DL Inner Loop Power Control
+
+The DL Inner Loop Power Control sets the power of the downlink dedicated [TDD – and shared] physical channels. It receives the quality target from DL Outer Loop Power Control and quality estimates of the [FDD - downlink dedicated physical control channel] [TDD – downlink dedicated physical channels and physical downlink shared channels if any]. The power control commands are sent on the [FDD - uplink dedicated physical control channel] [TDD – downlink dedicated physical channels and physical downlink shared channels if any] to the UTRAN.
+
+This function is located in both the UTRAN and the UE.
+
+##### 7.2.4.8.5 UL Open Loop Power Control
+
+The UL Open Loop Power Control sets the initial power of the UE, i.e. at random access. The function uses UE measurements and broadcasted cell/system parameters as input.
+
+This function is located in both the UTRAN and the UE.
+
+##### 7.2.4.8.6 DL Open Loop Power Control
+
+The DL Open Loop Power Control sets the initial power of downlink channels. It receives downlink measurement reports from the UE.
+
+This function is located in both the UTRAN and the UE.
+
+#### 7.2.4.9 Radio channel coding
+
+This function introduces redundancy into the source data flow, increasing its rate by adding information calculated from the source data, in order to allow the detection or correction of signal errors introduced by the transmission medium. The channel coding algorithm(s) used and the amount of redundancy introduced may be different for the different types of logical channels and different types of data.
+
+This function is located in both the UE and in the UTRAN.
+
+#### 7.2.4.10 Radio channel decoding
+
+This function tries to reconstruct the source information using the redundancy added by the channel coding function to detect or correct possible errors in the received data flow. The channel decoding function may also employ a priori error likelihood information generated by the demodulation function to increase the efficiency of the decoding operation. The channel decoding function is the complement function to the channel coding function.
+
+This function is located in both the UE and in the UTRAN.
+
+#### 7.2.4.11 Channel coding control
+
+This function generates control information required by the channel coding/ decoding execution functions. This may include channel coding scheme, code rate, etc.
+
+This function is located in both the UE and in the UTRAN.
+
+#### 7.2.4.12 Initial (random) access detection and handling
+
+This function will have the ability to detect an initial access attempt from a mobile station and will respond appropriately. The handling of the initial access may include procedures for a possible resolution of colliding attempts, etc. The successful result will be the request for allocation of appropriate resources for the requesting mobile station.
+
+This function is located in the UTRAN.
+
+#### 7.2.4.13 CN Distribution function for Non Access Stratum messages
+
+In the RRC protocol, messages from the NAS shall be transparently transferred within the Access Stratum using the Direct Transfer procedure. A distribution function in the UE and the SRNC shall handle the CN domain indicator being part of the AS message to direct messages to the appropriate NAS entity i.e. the appropriate Mobility Management instance in the UE domain and the appropriate CN domain.
+
+In the downlink direction the UE shall be provided by the SRNC with the information on the originating CN domain for the individual NAS message.
+
+In the uplink direction, the process performed by the distribution function in the UE consists in inserting the appropriate values for the CN domain indicator in the AS message and the process performed by the SRNC consists in evaluating the CN domain indicator contained in the AS message and distribute the NAS message to the corresponding RANAP instance for transfer over Iu interface.
+
+This distribution function is located in both the UE and in the SRNC.
+
+#### 7.2.4.14 [3.84 Mcps and 7.68 Mcps TDD - Timing Advance]
+
+This function is used in uplink to align the uplink radio signals from the UE to the UTRAN. Timing Advance is based on uplink burst timing measurements performed by the Node B L1, and on Timing Advance commands sent downlink to the UE.
+
+#### 7.2.4.15 Service specific function for Non Access Stratum messages
+
+A service specific function in the UE provides a SAP for a particular service (e.g. a given priority). In the downlink direction, the SRNC may base the routing on this SAP.
+
+This service specific function is located in both the UE and the SRNC.
+
+#### 7.2.4.16 [1.28 Mcps TDD – Uplink Synchronisation]
+
+This function is used in uplink to synchronise the uplink radio signals from the UE to the UTRAN. At the detection of uplink burst, the Node B will evaluate the received power level and timing, and reply by sending the adjustment information to UE to modify its timing and power level for next transmission and for establishment of the Uplink synchronisation procedure.
+
+### 7.2.5 Functions related to broadcast and multicast services (broadcast/multicast interworking function BM-IWF)
+
+See note.
+
+#### 7.2.5.1 Broadcast/Multicast Information Distribution
+
+The broadcast/multicast information distribution function distributes received CBS messages towards the BMC entities configured per cell for further processing. The distribution of broadcast/multicast information relate on the mapping between service area and cells controlled by the RNC. The provision of this mapping information is an O&M function.
+
+NOTE: Only Broadcast is applicable for Release 99.
+
+#### 7.2.5.2 Broadcast/Multicast Flow Control
+
+When processing units of the RNC becomes congested, the Broadcast/Multicast Flow Control function informs the data source about this congestion situation and takes means to resolve the congestion.
+
+#### 7.2.5.3 CBS Status Reporting
+
+The RNC collects status data per cell (e.g. No-of-Broadcast-Completed-List, Radio-Resource-Loading-List), and matches these data to Service Areas. The status data is transmitted to the CBC, if a query has been made by the CBC.
+
+### 7.2.6 Tracing
+
+This function allows tracing of various events related to the UE and its activities.
+
+### 7.2.7 Volume Reporting
+
+The data volume reporting function is used to report the volume of unacknowledged data to the CN for accounting purpose.
+
+### 7.2.8 RAN Information Management
+
+The RAN Information Management (RIM) function is a generic mechanism that allows the request and transfer of information between two RAN nodes e.g. GERAN System information. The RIM mechanism allows to start, stop and resume both on demand and on event transfer of information. RIM also provides native error handling function at RIM level and at RIM application level. The RIM function is further described in TR 44.901 [22] and TS 48.018 [23].
+
+### 7.2.9 Functions related to MBMS
+
+#### 7.2.9.1 MBMS provision
+
+The MBMS provision enables the RNC to provide a multicast service via an optimised transmission of the MBMS bearer service in UTRAN via techniques such as PTM transmission, selective combining, Soft Combining and transmission mode selection between PTM and PTP bearer.
+
+The MBMS provision enables the RNC to provide a broadcast service via a PTM transmission bearer.
+
+#### 7.2.9.2 MBMS Notification Coordination
+
+The characteristic of MBMS implies a need for MBMS notification co-ordination i.e. specific handling of MBMS Notification when UE is in Cell-DCH state. MBMS notification co-ordination is performed by UTRAN when the session is ongoing. The TMGI is used for coordination.
+
+The MBMS functions are further described in TS 25.346 [30].
+
+### 7.2.10 SIPTO at Iu-PS
+
+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 [36].
+
+### 7.2.11 Explicit Congestion Notification
+
+The RNC and the UE support of the Explicit Congestion Notification (ECN) is specified in Section 5 of IETF RFC 3168 [37] (i.e., the normative part of IETF RFC 3168 [37] that applies to the end-to-end flow of IP packets), and below. This enables the RNC to control the initial codec rate selection and/or to trigger a codec rate reduction. Thereby the RNC can increase capacity (e.g., in terms of number of accepted VoIP calls), and improve coverage (e.g. for high bit rate video sessions).
+
+The RNC should set the Congestion Experienced (CE) codepoint ('11') in PDCP SDUs in the downlink direction to indicate downlink (radio) congestion if those PDCP SDUs have one of the two ECN-Capable Transport (ECT) codepoints set.
+
+The RNC should set the Congestion Experienced (CE) codepoint ('11') in PDCP SDUs in the uplink direction to indicate uplink (radio) congestion if those PDCP SDUs have one of the two ECN-Capable Transport (ECT) codepoints set.
+
+### 7.2.12 MDT
+
+This function allows to activate and handle MDT sessions by trace procedure as described in TS37.320 [38].
+
+# --- 8 Mobility Management
+
+## 8.1 Signalling connection
+
+Based on TS 23.110 [2], the UE may either have or not have a signalling connection:
+
+- 1) When a signalling connection exists that is established over the Dedicated Control Service Access Point (DC-SAP) from the Access Stratum.
+Therefore, the CN can reach the UE by the dedicated connection SAP on the CN side, and the UTRAN has a context with the UE and CN for this particular connection. This context is erased when the connection is released. The *dedicated connection* can be initiated from the UE only.
+
+NOTE: A dedicated connection is currently defined as Signalling Connection in TS 23.110 [2]. Note that in the radio interface, dedicated or common channels can be used.
+
+Depending on the activity of a UE, the location of the UE is known either on cell level (higher activity) or in a larger area consisting of several cells (lower activity). This will (i) minimise the number of location update messages for moving UEs with low activity and (ii) remove the need for paging for UEs known on cell level.
+
+- 2) When a dedicated connection does not exist, the CN must reach the UE via the Notification SAP. The message sent to the UE can be a request to the UE to establish a dedicated connection. The UE is addressed with a user/terminal identity and a "geographical area".
+
+## 8.2 Consequences for Mobility Handling
+
+It is generally agreed to contain radio access specific procedures within UTRAN. This means that all cell level mobility should be handled within UTRAN. Also the cell structure of the radio network should not necessarily be known outside the UTRAN.
+
+When there exists a dedicated connection to the UE, the UTRAN shall handle the radio interface mobility of the UE. This includes procedures such as soft handover, and procedures for handling mobility in the CELL\_PCH and URA\_PCH/GRA\_PCH state TS 25.331 [7].
+
+When a dedicated connection between the UTRAN and the UE does not exist, no UE information is needed in UTRAN. Therefore, the mobility is handled directly between UE and CN outside access stratum (e.g. by means of registration procedures). When paging the UE, the CN indicates a 'geographical area' that is translated within UTRAN to the actual cells that shall be paged. A 'geographical area' shall be identified in a cell-structure independent way. One possibility is the use of 'Location Area identities'.
+
+During the lifetime of the dedicated connection, the registrations to the CN are suppressed by the UE. When a dedicated connection is released, the UE performs a new registration to the CN, when needed.
+
+Thus, the UTRAN does not contain any permanent 'location registers' for the UE, but only temporary contexts for the duration of the dedicated connection. This context may typically contain location information (e.g. current cell(s) of the UE) and information about allocated radio resources and related connection references.
+
+# --- 9 Synchronisation
+
+## 9.1 SYNCHRONISATION MODEL
+
+Different synchronisation issues are identified within UTRAN, i.e.:
+
+- Network Synchronisation;
+- Node Synchronisation;
+- Transport Channel synchronisation;
+- Radio Interface Synchronisation;
+- Time Alignment handling.
+
+The Nodes involved by the above mentioned synchronisation issues (with exception of Network and Node Synchronisation) are shown by the Synchronisation Issues Model of figure 8. Further details of synchronisation are in TS 25.402 [5].
+
+![Figure 8: Synchronisation issues model. This diagram illustrates the synchronization hierarchy in a UTRAN. At the top, a Vocoder is connected to a CN (Core Network). Below the CN are two RNCs (Radio Network Controllers) within an RNS (Radio Network Subsystem). Each RNC is connected to multiple Node Bs. The Node Bs are connected to UEs (User Equipment), labeled UE1 and UE2. Vertical arrows on the left indicate three levels of synchronization: 'Time Alignment Handling' between the Vocoder and RNCs, 'Transport Channel Synchronisation' between RNCs and Node Bs, and 'Radio Interface Synchronisation' between Node Bs and UEs. A dashed box labeled '[TDD] Radio Interface Sync.' surrounds the Node Bs and UEs, with a note 'Optional TDD only input & output sync ports'.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg)
+
+Figure 8: Synchronisation issues model. This diagram illustrates the synchronization hierarchy in a UTRAN. At the top, a Vocoder is connected to a CN (Core Network). Below the CN are two RNCs (Radio Network Controllers) within an RNS (Radio Network Subsystem). Each RNC is connected to multiple Node Bs. The Node Bs are connected to UEs (User Equipment), labeled UE1 and UE2. Vertical arrows on the left indicate three levels of synchronization: 'Time Alignment Handling' between the Vocoder and RNCs, 'Transport Channel Synchronisation' between RNCs and Node Bs, and 'Radio Interface Synchronisation' between Node Bs and UEs. A dashed box labeled '[TDD] Radio Interface Sync.' surrounds the Node Bs and UEs, with a note 'Optional TDD only input & output sync ports'.
+
+Figure 8: Synchronisation issues model
+
+# 10 UTRAN O&M Requirements
+
+## 10.1 O&M of Node B
+
+The O&M of Node B is separated in two parts: the O&M linked to the actual implementation of Node B, denoted as Implementation Specific O&M, and the O&M which impacts on the traffic carrying resources in Node B controlled from the RNC, denoted *logical O&M*. The RNS architecture with the O&M interfaces is shown in figure 9.
+
+
+
+Figure 9: RNS architecture with O&M interfaces. This diagram shows the management architecture. At the top, 'Management Platform(s)' contain four models: 'Node B Management Model' (blue), 'RNC Management Model' (blue), 'Node B Management Model' (yellow), and 'Co-located equipment Management Model' (red). Below are two 'Node B' units (one blue, one yellow) and a central 'RNC' unit (blue). The blue Node B has a 'luant interface' to the blue Node B Management Model and a 'lub interface' to the RNC. The yellow Node B has a 'lub interface' to the yellow Node B Management Model and a 'lub interface' to the RNC. The RNC has a 'lub interface' to the blue Node B Management Model and a 'lub interface' to the red Co-located equipment Management Model. Each Node B and the RNC contain internal O&M components: 'RET Antenna Control', 'TMA Control', 'Implementation O&M specific', 'Logical O&M', and 'Traffic Functions'. The RNC also contains 'RNC O&M', 'Node B Logical O&M', and 'Traffic Functions'.
+
+Figure 9: RNS architecture with O&M interfaces
+
+NOTE 1: The concept of an interface from the RNC to the management system is shown for clarity only. Its definition is outside the scope of 3GPP-TSG-RAN-WG3.
+
+NOTE 2: The presentation of the O&M functions within the management system is shown for clarity only. Their actual implementation is outside the scope of 3GPP-TSG-RAN-WG3.
+
+NOTE 3: The standardisation of the Implementation Specific O&M is outside the scope of 3GPP-TSG-RAN-WG3. The 3GPP-TSG-RAN-WG3 should only address the bearer for the Implementation Specific O&M.
+
+NOTE 4: The figure shows only logical connections and does not intend to mandate any physical interfaces.
+
+NOTE 5: The Iuant interface to the control unit of the RET antennas or TMAs is specified in the series of Technical Specifications 25.460 [24], 25.461 [25], 25.462 [26] and 25.466 [32]. An Implementation Specific O&M function is needed for the RET antennas or TMAs control to translate the control signalling from the Node B Element Manager into the control commands of the Iuant interface specified in TS 25.460 [24].
+
+### 10.1.1 Implementation Specific O&M
+
+The Implementation Specific O&M functions are heavily dependent on the implementation of Node B, both for its hardware components and for the management of the software components. It needs therefore to be implementation dependent, and be performed between Node B and the management system.
+
+One solution for the transport of Implementation Specific O&M is to route from Node B to the management system via the RNC. In this case, the Implementation Specific O&M interface and Iub interface share the same physical bearer, and TS 25.442 [4] specifies the routing function and the transport bearer for this scenario. The deployment of the routing across the RNC in the UTRAN is optional. Where signalling between co-located equipment and its management system is required, this may be carried over the same bearer as Implementation Specific O&M.
+
+### 10.1.2 Logical O&M
+
+Logical O&M is the signalling associated with the control of logical resources (channels, cells,...) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP.
+
+# --- 11 UTRAN Interfaces
+
+## 11.1 General Protocol Model for UTRAN Interfaces
+
+### 11.1.1 General
+
+The general protocol model for UTRAN Interfaces is depicted in figure 10, and described in detail in the following subclauses. The structure is based on the principle that the layers and planes are logically independent of each other. Therefore, as and when required, the standardisation body can easily alter protocol stacks and planes to fit future requirements.
+
+
+
+Figure 10: General Protocol Model for UTRAN Interfaces. The diagram shows two main horizontal layers: Radio Network Layer (top) and Transport Network Layer (bottom). The Radio Network Layer is divided into Control Plane (left) and User Plane (right). The Control Plane contains an Application Protocol. The User Plane contains Data Stream(s). The Transport Network Layer is divided into three vertical planes: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The left Transport User Network Plane contains a Signalling Bearer(s). The middle Transport Network Control Plane contains ALCAP(s) and a Signalling Bearer(s). The right Transport User Network Plane contains a Data Bearer(s). All three planes connect to a common Physical Layer at the bottom. Arrows indicate data flow: from Application Protocol to Signalling Bearer(s) in the left plane, from ALCAP(s) to Signalling Bearer(s) in the middle plane, and from Data Stream(s) to Data Bearer(s) in the right plane. All bearers then connect to the Physical Layer.
+
+**Figure 10: General Protocol Model for UTRAN Interfaces**
+
+### 11.1.2 Horizontal Layers
+
+The Protocol Structure consists of two main layers, Radio Network Layer, and Transport Network Layer. All UTRAN related issues are visible only in the Radio Network Layer, and the Transport Network Layer represents standard transport technology that is selected to be used for UTRAN, but without any UTRAN specific requirements.
+
+### 11.1.3 Vertical Planes
+
+#### 11.1.3.1 Control Plane
+
+The Control Plane Includes the Application Protocol, i.e. RANAP, RNSAP or NBAP, and the Signalling Bearer for transporting the Application Protocol messages.
+
+Among other things, the Application Protocol is used for setting up bearers for (i.e. Radio Access Bearer or Radio Link) in the Radio Network Layer. In the three plane structure the bearer parameters in the Application Protocol are not directly tied to the User Plane technology, but are rather general bearer parameters.
+
+The Signalling Bearer for the Application Protocol may or may not be of the same type as the Signalling Protocol for the ALCAP. The Signalling Bearer is always set up by O&M actions.
+
+#### 11.1.3.2 User Plane
+
+The User Plane Includes the Data Stream(s) and the Data Bearer(s) for the Data Stream(s). The Data Stream(s) is/are characterised by one or more frame protocols specified for that interface.
+
+#### 11.1.3.3 Transport Network Control Plane
+
+The Transport Network Control Plane does not include any Radio Network Layer information, and is completely in the Transport Layer. It includes the ALCAP protocol(s) that is/are needed to set up the transport bearers (Data Bearer) for the User Plane. It also includes the appropriate Signalling Bearer(s) needed for the ALCAP protocol(s).
+
+The Transport Network Control Plane is a plane that acts between the Control Plane and the User Plane. The introduction of Transport Network Control Plane is performed in a way that the Application Protocol in the Radio Network Control Plane is kept completely independent of the technology selected for Data Bearer in the User Plane. Indeed, the decision to actually use an ALCAP protocol is completely kept within the Transport Network Layer.
+
+It should be noted that ALCAP might not be used for all types Data Bearers. If there is no ALCAP signalling transaction, the Transport Network Control Plane is not needed at all. This is the case when pre-configured Data
+
+Bearers are used or when the IP (IETF RFC 791 [17]) UTRAN option is used between two IP UTRAN nodes or between an IP UTRAN node and an IP CN node.
+
+When Transport Network Control Plane is used, the transport bearers for the Data Bearer in the User Plane are set up in the following fashion. First there is a signalling transaction by the Application Protocol in the Control Plane, which triggers the set up of the Data Bearer by the ALCAP protocol that is specific for the User Plane technology.
+
+The following interworking alternatives are specified for the IP-ATM interworking:
+
+- 1) ATM/IP Dual Stack supported in the IP UTRAN node. When an ATM/IP dual stack is implemented in the IP UTRAN node, support of an IP ALCAP protocol is not required.
+
+Annex A of TS 25.414 [9] shows an example of protocols for the case the ATM&IP UTRAN/CN-node has no ATM connectivity.
+
+
+
+The diagram shows a 'Rel5 IP UTRAN node' represented by a large rectangle. Inside this rectangle, at the top, is a box labeled 'RNL'. Below 'RNL' are two side-by-side boxes: 'IP' on the left and 'ATM' on the right. To the left of the 'IP' box, a horizontal line labeled 'IP transport option' enters the node. To the right of the 'ATM' box, a horizontal line labeled 'ATM transport option' exits the node.
+
+Diagram of Rel5 IP UTRAN node with IP transport option and ATM transport option.
+
+- 2) An Interworking Function (IWF), either internal or external to the UTRAN/CN node.
+
+Annex A of TS 25.414 [9] shows an example of a protocol stack for the case when the IWF is an external unit to the UTRAN/CN node. Other protocol stacks for this case are not precluded.
+
+
+
+The diagram shows a 'Rel5 IP UTRAN node' represented by a dashed rectangle. Inside, at the top, is a box labeled 'RNL'. Below 'RNL' are two side-by-side boxes: 'IP' on the left and 'IP' on the right. To the right of the second 'IP' box is another box labeled 'TNL Interworking Function'. Below 'TNL Interworking Function' are two side-by-side boxes: 'IP' on the left and 'ATM' on the right. To the left of the first 'IP' box, a horizontal line labeled 'IP transport option' enters the node. To the right of the 'ATM' box, a horizontal line labeled 'ATM transport option' exits the node.
+
+Diagram of Rel5 IP UTRAN node with IP transport option and ATM transport option, featuring a TNL Interworking Function.
+
+#### 11.1.3.4 Transport Network User Plane
+
+The Data Bearer(s) in the User Plane, and the Signalling Bearer(s) for Application Protocol, belong also to Transport Network User Plane. As described in the previous subclause, the Data Bearers in Transport Network User Plane are directly controlled by Transport Network Control Plane during real time operation, but the control actions required for setting up the Signalling Bearer(s) for Application Protocol are considered O&M actions.
+
+## 11.2 Protocol Model (Informative)
+
+The following subclause is a informative subclause which aim is to provide an overall picture of how the MAC layer is distributed over Uu, Iub and Iur for the RACH, FACH, DCH, [TDD – DSCH, USCH] and HS-DSCH.
+
+### 11.2.1 RACH Transport Channel
+
+Figure 11 shows the protocol stack model for the RACH transport channel when the Controlling and Serving RNC are co-incident.
+
+For the RACH transport channel, Dedicated MAC (MAC-d) uses the services of Common MAC (MAC-c/sh).
+
+
+
+Figure 11: RACH: Coincident Controlling and Serving RNC. This diagram shows the protocol stack for a User Equipment (UE), NodeB, and a combined CRNC/SRNC. The UE stack consists of DTCH, DCCH, and CCCH channels at the top, followed by MAC-d, MAC-c/sh, and PHY layers. The NodeB stack consists of PHY and TNL layers, with a RachFP entity between them. The CRNC/SRNC stack consists of CCCH, DCCH, and DTCH channels at the top, followed by MAC-d, MAC-c/sh, RachFP, and TNL layers. The interfaces shown are Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC.
+
+**Figure 11: RACH: Coincident Controlling and Serving RNC**
+
+The Common MAC (MAC-c/sh) entity in the UE transfers MAC-c/sh PDU to the peer MAC-c/sh entity in the RNC using the services of the Physical Layer.
+
+An Interworking Function (IWF) in the Node B interworks the RACH frame received by the PHY entity into the RACH Frame Protocol (RACH FP) entity.
+
+The RACH Frame Protocol entity adds header information to form a RACH FP PDU that is transported to the RNC over a transport bearer.
+
+At the RNC, the RACH FP entity delivers the MAC-c/sh PDU to the MAC-c/sh entity.
+
+Figure 12 shows the protocol model for the RACH transport channel with separate Controlling and Serving RNC. In this case, Iur RACH Frame Protocol (RACH FP) is used to interwork the Common MAC (MAC-c/sh) at the Controlling RNC with the Dedicated MAC (MAC-d) at the Serving RNC.
+
+
+
+Figure 12: RACH: Separate Controlling and Serving RNC. This diagram shows the protocol stack for a User Equipment (UE), NodeB, a Controlling RNC (CRNC), and a Serving RNC (SRNC). The UE stack is identical to Figure 11. The NodeB stack is identical to Figure 11. The CRNC stack consists of CCCH at the top, followed by MAC-c/sh, RachFP, and TNL layers. The SRNC stack consists of DCCH and DTCH channels at the top, followed by MAC-d, RACH FP, and TNL layers. The interfaces shown are Uu between UE and NodeB, Iub between NodeB and CRNC, and Iur between CRNC and SRNC. A horizontal line labeled 'RACH FP' connects the RachFP entity in the CRNC to the RACH FP entity in the SRNC.
+
+**Figure 12: RACH: Separate Controlling and Serving RNC**
+
+### 11.2.2 CPCH [FDD] Transport Channel
+
+Void.
+
+### 11.2.3 FACH Transport Channel
+
+Figure 15 shows the protocol model for the FACH transport channel when the Controlling and Serving RNC are co-incident.
+
+
+
+Figure 15: FACH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the FACH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh/m, and PHY layers. The MAC-d layer is connected to DTCH, DCCH, MTCH, and MCCH channels. The MAC-c/sh/m layer is connected to CCCH, MSCH, and FACH FP. The PHY layer is connected to the Uu interface. In the center, the NodeB stack consists of PHY and TNL layers. The PHY layer is connected to the Uu interface and the FACH FP. The TNL layer is connected to the Iub interface. On the right, the CRNC/SRNC stack consists of MAC-d, MAC-c/sh/m, FACH FP, and TNL layers. The MAC-d layer is connected to MTCH, MCCH, DCCH, and DTCH channels. The MAC-c/sh/m layer is connected to MSCH, CCCH, and FACH FP. The FACH FP layer is connected to the Iub interface. The TNL layer is connected to the Iub interface.
+
+**Figure 15: FACH Co-incident Controlling and Serving RNC**
+
+The Common MAC (MAC-c/sh/m) entity in the RNC transfers MAC-c PDU to the peer MAC-c entity in the UE using the services of the FACH Frame Protocol (FACH FP) entity.
+
+The FACH Frame Protocol entity adds header information to form a FACH FP PDU which is transported to the Node B over a transport bearer.
+
+An Interworking Function (IWF) in the Node B interworks the FACH frame received by FACH Frame Protocol (FACH FP) entity into the PHY entity.
+
+FACH scheduling is performed by MAC-c/sh/m in the CRNC.
+
+Figure 16 shows the protocol model for the FACH transport channel with separate Controlling and Serving RNC. In this case, Iur FACH Frame Protocol is used to interwork the Common MAC (MAC-c) at the Controlling RNC with the Dedicated MAC (MAC-d) at the Serving RNC.
+
+
+
+Figure 16: FACH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the FACH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh, and PHY layers. The MAC-d layer is connected to DTCH, DCCH, MTCH, and MCCH channels. The MAC-c/sh layer is connected to CCCH, MSCH, and FACH FP. The PHY layer is connected to the Uu interface. In the center, the NodeB stack consists of PHY and TNL layers. The PHY layer is connected to the Uu interface and the FACH FP. The TNL layer is connected to the Iub interface. On the right, the CRNC stack consists of MAC-c/sh/m, FACH FP, and TNL layers. The MAC-c/sh/m layer is connected to MTCH, MCCH, MSCH, and CCCH channels. The FACH FP layer is connected to the Iub interface. The TNL layer is connected to the Iur interface. On the far right, the SRNC stack consists of MAC-d, FACH FP, and TNL layers. The MAC-d layer is connected to DCCH and DTCH channels. The FACH FP layer is connected to the Iur interface. The TNL layer is connected to the Iur interface.
+
+**Figure 16: FACH: Separate Controlling and Serving RNC**
+
+### 11.2.4 DCH Transport Channel
+
+Figure 17 shows the protocol model for the DCH transport channel when the Controlling and Serving RNC are co-incident.
+
+
+
+Figure 17: DCH: Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the DCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) has a stack with MAC-d and PHY layers, receiving DTCH and DCCH data. The UE connects to a NodeB via the Uu interface. The NodeB contains a PHY layer and an Interworking Function (IWF) block with DchFP and TNL layers. The NodeB connects to the CRNC/SRNC via the Iub interface. The CRNC/SRNC has a stack with MAC-d, PHY, DchFP, and TNL layers, also receiving DTCH and DCCH data.
+
+**Figure 17: DCH: Co-incident Controlling and Serving RNC**
+
+The DCH transport channel introduces the concept of distributed PHY layer.
+
+An Interworking Function (IWF) in the Node B interworks between the DCH Frame Protocol (DCH FP) entity and the PHY entity.
+
+
+
+Figure 18: DCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the DCH transport channel when the CRNC and SRNC are separate. The UE stack includes MAC-d, PHY-upper, and PHY layers. The UE connects to the NodeB via the Uu interface. The NodeB contains a PHY layer and an IWF block with DchFP and TNL layers. The NodeB connects to the CRNC via the Iub interface. The CRNC contains a PHY layer, two DchFP entities, and two TNL entities. The CRNC connects to the SRNC via the Iur interface. The SRNC has a stack with MAC-d, PHY, DchFP, and TNL layers, receiving DTCH and DCCH data.
+
+**Figure 18: DCH: Separate Controlling and Serving RNC**
+
+Figure 18 shows the protocol model for the DCH transport channel with separate Controlling and Serving RNC. In this case, the Iub DCH FP is terminated in the CRNC and interworked with the Iur DCH FP through a PHY function. This function performs optional soft handover or can be a null function.
+
+### 11.2.5 DSCH Transport Channel [TDD]
+
+Figure 19 shows the protocol model for the DSCH transport channel when the Controlling and Serving RNC are co-incident.
+
+
+
+Figure 19: DSCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the DSCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY and TNL layers, with a DschFP entity shown above the TNL. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of MAC-d, MAC-c/sh, DschFP, and TNL layers. The MAC-d layer is connected to DCCH and DTCH channels.
+
+**Figure 19: DSCH Co-incident Controlling and Serving RNC**
+
+The Shared MAC (MAC-c/sh) entity in the RNC transfers MAC-c/sh PDU to the peer MAC-c/sh entity in the UE using the services of the DSCH Frame Protocol (DSCH FP) entity. The DSCH FP entity adds header information to form a DSCH FP PDU that is transported to the Node B over a transport bearer.
+
+An Interworking Function (IWF) in the Node B interworks the DSCH frame received by DSCH FP entity into the PHY entity. DSCH scheduling is performed by MAC-c/sh in the CRNC.
+
+Figure 20 shows the protocol model for the DSCH transport channel with separate Controlling and Serving RNC. In this case, Iur DSCH Frame Protocol is used to interwork the MAC-c/sh at the Controlling RNC with the MAC-d at the Serving RNC.
+
+
+
+Figure 20: DSCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the DSCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. On the left, the UE stack consists of MAC-d, MAC-c/sh, and PHY layers, connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY and TNL layers, with a DschFP entity shown above the TNL. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of MAC-c/sh, DschFP, and TNL layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of MAC-d, DschFP, and TNL layers, connected to DCCH and DTCH channels.
+
+**Figure 20: DSCH: Separate Controlling and Serving RNC**
+
+### 11.2.6 USCH Transport Channel [TDD]
+
+Figure 21 shows the protocol model for the USCH transport channel when the Controlling and Serving RNC are co-incident.
+
+
+
+Figure 21: USCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the USCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of DTCH and DCCH channels at the top, followed by MAC-d, MAC-c/sh, and PHY layers. The UE is connected to a NodeB via the Uu interface. The NodeB stack includes PHY and TNL layers, with an UschFP entity positioned between them. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of TNL, UschFP, MAC-c/sh, and MAC-d layers at the top, which then branch into DCCH and DTCH channels.
+
+**Figure 21: USCH Co-incident Controlling and Serving RNC**
+
+The Shared MAC (MAC-c/sh) entity in the RNC *receives* MAC-c/sh PDU *from* the peer MAC-c/sh entity in the UE using the services of the Interworking Function in the Node B, and the USCH Frame Protocol (USCH FP) entity. The USCH FP entity *in the Node B* adds header information to form a USCH FP PDU that is transported to the RNC over a transport bearer.
+
+An Interworking Function (IWF) in the Node B interworks *the received USCH PHY entity into an USCH frame to be transmitted by the USCH FP entity over the Iub interface*. USCH scheduling is performed by MAC-c/sh in UE and by C-RRc in the CRNC.
+
+Figure 22 shows the protocol model for the USCH transport channel with separate Controlling and Serving RNC. In this case, Iur USCH Frame Protocol is used to interwork the MAC-c/sh at the Controlling RNC with the MAC-d at the Serving RNC.
+
+
+
+Figure 22: USCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the USCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. The UE stack on the left is identical to Figure 21. The UE connects to a NodeB via the Uu interface. The NodeB stack includes PHY, TNL, and UschFP layers. The NodeB connects to the CRNC via the Iub interface. The CRNC stack consists of TNL, UschFP, and MAC-c/sh layers. The CRNC connects to the SRNC via the Iur interface. The SRNC stack consists of TNL, UschFP, MAC-d, and then branches into DCCH and DTCH channels.
+
+**Figure 22: USCH: Separate Controlling and Serving RNC**
+
+### 11.2.7 HS-DSCH Transport Channel
+
+Figure 23 shows the protocol model for the HS-DSCH transport channel when the Controlling and Serving RNC are co-incident. [FDD and 1.28 Mcps TDD – The protocol model in Figure 23 is applied for HS-DSCH configured for UEs in Cell\_DCH.]
+
+
+
+Figure 23: HS-DSCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the HS-DSCH transport channel when the Controlling and Serving RNC are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-(e)hs, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes MAC-(e)hs, HS-DSCHFP, PHY, and TNL layers. The MAC-(e)hs layer is connected to the MAC-d layer in the CRNC/SRNC. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of MAC-d, HS-DSCHFP, and TNL layers. The MAC-d layer is connected to DCCH and DTCH channels.
+
+**Figure 23: HS-DSCH Co-incident Controlling and Serving RNC**
+
+The High Speed MAC (MAC-hs) or Enhanced High Speed MAC (MAC-ehs) entity in the Node B transfers MAC-hs (or MAC-ehs) PDU to the peer MAC-hs (or MAC-ehs) entity in the UE over the Uu interface. The Dedicated MAC (MAC-d) entity in the RNC transfers MAC-d PDUs to the MAC-hs or MAC-ehs in the Node B using the services of the HS-DSCH Frame Protocol (HS-DSCH FP) entity. The HS-DSCH FP entity adds header information to form a HS-DSCH FP PDU that is transported to the Node B over a transport bearer.
+
+A Relaying Function in the Node B relays the HS-DSCH frame received by HS-DSCH FP entity to the MAC-hs (or MAC-ehs) entity. HS-DSCH scheduling is performed by MAC-hs (or MAC-ehs) in the Node B.
+
+Figure 24 shows the protocol model for the HS-DSCH transport channel with separate Controlling and Serving RNC. [FDD and 1.28 Mcps TDD – The protocol model in Figure 24 is applied for HS-DSCH configured for UEs in Cell\_DCH.] In this case, Iur HS-DSCH Frame Protocol is used to interwork the Flow Control function at the Controlling RNC with the MAC-d at the Serving RNC. Also in this case, Iub HS-DSCH Frame Protocol is used to interwork the MAC-hs (or MAC-ehs) at the Node B with the Flow Control function at the Controlling RNC.
+
+
+
+Figure 24: HS-DSCH: Separate Controlling and Serving RNC (configuration with CRNC flow control). This diagram illustrates the protocol stack for the HS-DSCH transport channel when the Controlling and Serving RNC are separate. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-(e)hs, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes MAC-(e)hs, HS-DSCHFP, PHY, and TNL layers. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of CRNC HS-DSCH Flow Control, HS-DSCHFP, and TNL layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL layers. The MAC-d layer is connected to DCCH and DTCH channels.
+
+**Figure 24: HS-DSCH: Separate Controlling and Serving RNC (configuration with CRNC flow control)**
+
+Figure 25 shows the protocol model for the HS-DSCH transport channel with the Controlling RNC user plane RNL being bypassed. [FDD and 1.28 Mcps TDD – The protocol model in Figure 25 is applied for HS-DSCH configured for UEs in Cell\_DCH.] In this case, the CRNC does not have any user plane RNL function for the HS-DSCH. MAC-d in SRNC is located directly above MAC-hs (or MC-ehs) in Node B, i.e. in the HS-DSCH user plane RNL, the SRNC is directly connected to the Node B, thus bypassing the CRNC user plane RNL. The CRNC performs only user plane TNL functions.
+
+
+
+Figure 25: HS-DSCH: Serving RNC with bypassed Controlling RNC (configuration without CRNC flow control). The diagram illustrates the protocol stack across three entities: UE, NodeB, and SRNC, with an intermediate CRNC. The UE stack consists of MAC-d, MAC-(e)hs, and PHY. The NodeB stack consists of MAC-(e)hs, HS-DSCHFP, PHY, and TNL. The CRNC stack consists of TNL. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL. The interfaces are labeled Uu (between UE and NodeB), Iub (between NodeB and CRNC), and Iur (between CRNC and SRNC). Arrows indicate data flow from DCCH and DTCH in the UE, through the MAC layers, across the interfaces, and into the MAC-d layer in the SRNC.
+
+**Figure 25: HS-DSCH: Serving RNC with bypassed Controlling RNC (configuration without CRNC flow control)**
+
+[FDD and 1.28 Mcps TDD - Figure 25A shows the protocol model for the HS-DSCH transport channel configured for UEs in Cell\_FACH, Cell\_PCH and URA\_PCH, when the Controlling and Serving RNC are co-incident.
+
+The Common MAC (MAC-c/sh/m) entity in the RNC transfers MAC-c PDU to the peer MAC-c entity in the UE using the services of the HS-DSCH Frame Protocol (HS-DSCH FP) entity.
+
+The HS-DSCH Frame Protocol entity adds header information to form a HS-DSCH FP PDU which is transported to the Node B over a transport bearer.
+
+The Enhanced High Speed MAC (MAC-ehs) entity in the Node B transfers MAC-ehs PDU to the peer MAC-ehs entity in the UE over the Uu interface. ]
+
+
+
+Figure 25A: Protocol stack diagram for HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH with co-incident Controlling and Serving RNC. The diagram shows three main entities: UE, NodeB, and CRNC/SRNC. The UE stack consists of MAC-d, MAC-c/sh, MAC-ehs, and PHY layers. MAC-d is connected to DTCH, DCCH, PCCH, CCCH, and BCCH. The NodeB stack consists of MAC-ehs, HS-DSCHFP, PHY, and TNL layers. The CRNC/SRNC stack consists of MAC-d, MAC-c/sh, HS-DSCHFP, and TNL layers. MAC-d is connected to DCCH, DTCH, PCCH, CCCH, and BCCH. The interfaces are Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC.
+
+**Figure 25A: HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH: Co-incident Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)**
+
+[FDD and 1.28 Mcps TDD - Figure 25B shows the protocol model for the HS-DSCH transport channel configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH, with separate Controlling and Serving RNC. In this case, Iur HS-DSCH Frame Protocol is used to interwork the Flow Control function at the MAC-c at Controlling RNC with the MAC-d at the Serving RNC. Also in this case, Iub HS-DSCH Frame Protocol is used to interwork the MAC-ehs at the Node B with the Flow Control function at the MAC-c at the Controlling RNC.]
+
+
+
+Figure 25B: Protocol stack diagram for HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH with separate Controlling and Serving RNC. The diagram shows four main entities: UE, NodeB, CRNC, and SRNC. The UE stack consists of MAC-d, MAC-c/sh, MAC-ehs, and PHY layers. MAC-d is connected to DTCH, DCCH, PCCH, CCCH, and BCCH. The NodeB stack consists of MAC-ehs, HS-DSCHFP, PHY, and TNL layers. The CRNC stack consists of MAC-c/sh, HS-DSCHFP, and TNL layers. MAC-c/sh is connected to PCCH, CCCH, and BCCH. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL layers. MAC-d is connected to DCCH and DTCH. The interfaces are Uu between UE and NodeB, Iub between NodeB and CRNC, and Iur between CRNC and SRNC.
+
+**Figure 25B: HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH: Serving RNC with Separate Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)**
+
+### 11.2.8 E-DCH Transport Channel
+
+Figure 26 shows the protocol model for the E-DCH transport channel when the Controlling and Serving RNC are co-incident. [FDD and 1.28 Mcps TDD – The protocol model in Figure 26 is applied for E-DCH configured for UEs in Cell\_DCH.]
+
+
+
+Figure 26: E-DCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the E-DCH transport channel. On the left, the UE (User Equipment) stack consists of DTCH and DCCH at the top, followed by MAC-d, MAC-e/ MAC-es, MAC-i/ MAC-is, and PHY layers. The UE connects to the NodeB via the Uu interface. The NodeB stack includes MAC-e/ MAC-i and EDCH FP at the top, with PHY and TNL layers below. The NodeB connects to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of DCCH and DTCH at the top, followed by MAC-d, MAC-es/ MAC-is, EDCH FP, and TNL layers.
+
+**Figure 26: E-DCH Co-incident Controlling and Serving RNC**
+
+The E-DCH MAC (MAC-e/MAC-es)/Enhanced E-DCH MAC (MAC-i/MAC-is) entity in the UE transfers MAC-e /MAC-i PDUs to the peer MAC-e/MAC-i entity in the Node B and MAC-es/MAC-is PDUs to the peer MAC-es /MAC-is entity in the RNC using the services of the Physical Layer.
+
+The E-DCH FP entity adds header information to form a E-DCH FP PDU that is transported to the RNC over a transport bearer.
+
+An Interworking Function (IWF) in the Node B interworks the E-DCH frame received by the MAC-e/MAC-i entity into the E-DCH Frame Protocol (E-DCH FP) entity. E-DCH scheduling is performed by MAC-e/MAC-i in the Node B and reordering is performed by MAC-es/MAC-is in the RNC.
+
+Figure 27 shows the protocol model for the E-DCH transport channel with separate Controlling and Serving RNC. [FDD and 1.28 Mcps TDD – The protocol model in Figure 27 is applied for E-DCH configured for UEs in Cell\_DCH.] In this case, the CRNC does not have any user plane RNL function for the E-DCH. MAC-es/MAC-is in SRNC is located directly above MAC-e/MAC-is in Node B, i.e. in the E-DCH user plane RNL, the SRNC is directly connected to the Node B, thus bypassing the CRNC user plane RNL. The CRNC performs only user plane TNL functions.
+
+
+
+Figure 27: E-DCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for E-DCH when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. On the left, the User Equipment (UE) stack consists of DTCH and DCCH inputs to MAC-d, which is connected to MAC-es/MAC-e and MAC-is/MAC-i, which in turn connect to the PHY layer. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes MAC-e/MAC-i and E-DCH FP entities connected to the PHY and TNL layers. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of two TNL entities. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack includes TNL, E-DCH FP, MAC-es/MAC-is, and MAC-d entities, which output to DCCH and DTCH.
+
+**Figure 27: E-DCH: Separate Controlling and Serving RNC**
+
+[FDD and 1.28 Mcps TDD - Figure 28 shows the protocol model for the E-DCH transport channel configured for UE in Cell\_FACH for CCCH transmission.
+
+The E-DCH MAC (MAC-i/MAC-is) entity in the UE transfers MAC-i and MAC-is PDUs to the peer MAC-i in the Node B and and MAC-is entity in the CRNC.
+
+The E-DCH FP entity adds header information to form a E-DCH FP PDU that is transported to the RNC over a transport bearer.]
+
+
+
+Figure 28: E-DCH configured for UE in Cell\_FACH(CCCH case)(FDD and 1.28 Mcps TDD only). This diagram shows the protocol stack for E-DCH when the UE is in Cell\_FACH mode for CCCH transmission. The UE stack includes MAC-c, MAC-is/MAC-i, and PHY layers. The MAC-c entity receives input from CCCH. The UE connects to the NodeB via the Uu interface. The NodeB stack includes MAC-i and EDCH FP entities connected to the PHY and TNL layers. The NodeB connects to the CRNC via the Iub interface. The CRNC stack includes TNL, EDCH FP, MAC-is, and MAC-c entities, which output to CCCH.
+
+**Figure 28: E-DCH configured for UE in Cell\_FACH(CCCH case)(FDD and 1.28 Mcps TDD only)**
+
+[FDD and 1.28 Mcps TDD - Figure 29 shows the protocol model for the E-DCH transport channel configured for UE in Cell\_FACH for DCCH and DTCH transmission when the Controlling and Serving RNC are co-incident.
+
+The E-DCH MAC (MAC-i/MAC-is) entity in the UE transfers MAC-i PDUs to the peer MAC-i entity in the Node B and MAC-is PDUs to the peer MAC-is entity in the RNC using the services of the Physical Layer.
+
+The E-DCH FP entity adds header information to form an E-DCH FP PDU that is transported to the RNC over a transport bearer.
+
+An Interworking Function (IWF) in the Node B interworks the E-DCH frame received by the MAC-i entity into the E-DCH Frame Protocol (E-DCH FP) entity. E-DCH scheduling is performed by MAC-i in the Node B and reordering is performed by MAC-is in the RNC.]
+
+
+
+This diagram illustrates the protocol stack for an E-DCH configured for a UE in Cell\_FACH mode where the controlling and serving RNC are co-incident. The stack is shown for three entities: UE, NodeB, and CRNC/SRNC, connected via Uu and Iub interfaces. In the UE, DTCH and DCCH data flows enter the MAC-d layer, which then passes through MAC-is / MAC-i and PHY. At the NodeB, the PHY layer connects to MAC-i and EDCH FP. The MAC-i layer is connected to the CRNC/SRNC via the Iub interface. In the CRNC/SRNC, the EDCH FP layer receives data from the MAC-i layer and passes it through TNL to the MAC-is and MAC-d layers, which then deliver the data to the DCCH and DTCH channels.
+
+Figure 29: Protocol stack diagram for E-DCH in Cell\_FACH with co-incident controlling and serving RNC.
+
+**Figure 29: E-DCH configured for UE in Cell\_FACH (DCCH/DTCH case) :Co-incident Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)**
+
+[FDD and 1.28 Mcps TDD - Figure 30 shows the protocol model for the E-DCH transport channel configured for UE in Cell\_FACH for DCCH and DTCH transmission, with separate Controlling and Serving RNC.
+
+An Interworking Function (IWF) in the CRNC interworks the E-DCH data frame received from Node B into the Iur E-DCH Frame Protocol (E-DCH FP) entity.]
+
+
+
+This diagram illustrates the protocol stack for an E-DCH configured for a UE in Cell\_FACH mode where the controlling and serving RNC are separate. The stack is shown for four entities: UE, NodeB, CRNC, and SRNC, connected via Uu, Iub, and Iur interfaces. In the UE, DTCH and DCCH data flows enter the MAC-d layer, which then passes through MAC-is / MAC-i and PHY. At the NodeB, the PHY layer connects to MAC-i and E-DCH FP. The MAC-i layer is connected to the CRNC via the Iub interface. In the CRNC, the E-DCH FP layer receives data from the MAC-i layer and passes it through TNL to the Iur interface. At the Iur interface, the data is processed by an IWF (represented by two E-DCH FP blocks) and then passed to the SRNC. In the SRNC, the data passes through TNL to the MAC-is and MAC-d layers, which then deliver the data to the DCCH and DTCH channels.
+
+Figure 30: Protocol stack diagram for E-DCH in Cell\_FACH with separate controlling and serving RNC.
+
+**Figure 30: E-DCH configured for UE in Cell\_FACH (DCCH/DTCH case): Separate Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)**
+
+# 12 UTRAN Performance Requirements
+
+## 12.1 UTRAN delay requirements
+
+Void.
+
+# --- Annex A (informative): SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities
+
+Ranges of SPID (Subscriber Profile ID for RAT/Frequency Priority) values, respectively Operator Specific and Reference values and the mapping at RNS of Reference SPID values to cell reselection and inter-RAT/inter frequency handover priorities are defined in TS 36.300 [35].
+
+# Annex A2 (Informative): Deployment of Extended Identifiers
+
+## A2.1 RNC Sizing Changes
+
+### A2.1.1 U-RNTI Considerations
+
+The U-RNTI of 32 bits is normally divided in the following way:
+
+
+
+| | |
+|----------------|---------------|
+| RNC-ID 12 bits | S-RNTI 20bits |
+|----------------|---------------|
+
+**Figure A2.1.1.1: RNC Side, normal split of U-RNTI in RNC-ID and S-RNTI**
+
+When a large number of small RNCs were considered (HSPA+ cells), then extended RNC-ID was added, this took bits from the S-RNTI reducing this to 16bits thus:
+
+
+
+| | |
+|----------------|---------------|
+| RNC-ID 16 bits | S-RNTI 16bits |
+|----------------|---------------|
+
+**Figure A2.1.1.2: RNC-Side, split of U-RNTI in RNC-ID and S-RNTI in the case of many small RNCs deployed**
+
+Whilst this limited the S-RNTIs available to a RNC to 65k, as the RNCs were smaller this was acceptable, and allowed the addressing of 65k RNCs (per PLMN).
+
+Also related is the cell identity, containing the cell id and the RNC-ID
+
+
+
+| | |
+|----------------|----------------|
+| RNC-ID 12 bits | Cell id 16bits |
+|----------------|----------------|
+
+**Figure A2.1.1.3: RNC Side, normal split of Cell identity in RNC-ID and Cell id.**
+
+Or for extended RNC-ID
+
+
+
+| | |
+|----------------|----------------|
+| RNC-ID 16 bits | Cell id 12bits |
+|----------------|----------------|
+
+**Figure A2.1.1.4: RNC Side, split of Cell identity in RNC-ID and CELL I in case of extended RNC-ID (many small RNCs deployed)**
+
+Rules are applied to handle extended RNC-ID in relation to the addressing of RNCs in Clause A2.2.
+
+For extending the S-RNTI to handle larger number of UEs.
+
+The UE side is unchanged:
+
+
+
+| | |
+|----------------|---------------|
+| RNC-ID 12 bits | S-RNTI 20bits |
+|----------------|---------------|
+
+**Figure A2.1.1.5: UE Side, Normal split of U-RNTI in RNC-ID and S-RNTI**
+
+The RAN side uses a shorter RNC-ID and extended S-RNTI to give 4x increase in the number of UEs that can be supported on a RNC.
+
+
+
+| | |
+|----------------|---------------|
+| RNC-ID 10 bits | S-RNTI 22bits |
+|----------------|---------------|
+
+**Figure A2.1.1.6: UE Side, Split of U-RNTI in RNC-ID and S-RNTI in case of large number of UEs deployed.**
+
+Rules and methods to achieve this extension are in Clause A2.1.2 and A2.1.3.
+
+### A2.1.2 Extend S-RNTI and reduce RNC-ID: Solution 1
+
+In this solution the S-RNTI is extended by 2 bits and the RNC-ID reduced by 2 bits. This gives an increased number of UE supported to $2^{22}$ , but a reduced number of RNC-IDs available at 1024 ( $2^{10}$ ).
+
+UE Side
+
+
+
+| | |
+|----------------|---------------|
+| RNC-ID 12 bits | S-RNTI 20bits |
+|----------------|---------------|
+
+**Figure A2.1.2.1: UE Side, Normal split of U-RNTI in RNC-ID and S-RNTI**
+
+RAN Side
+
+
+
+| | |
+|-------------------|---------------|
+| RNC-ID 10
bits | S-RNTI 22bits |
+|-------------------|---------------|
+
+**Figure A2.1.2.2: RNC Side, Extended S-RNTI and reduced RNC-ID ranges**
+
+Although this approach increases by 4 the number of SRNTIs available, new rules are needed to handle addressing large RNCs with 10bit RNC-IDs. It is also incompatible with extended RNC-ID. The co-existence of extended RNC-ID and extended S-RNTI in one network may not be possible or the rules would become exceedingly complex.
+
+#### Reallocation of U-RNTI to allow more S-RNTI
+
+Initially we look at the current restrictions in the standards.
+
+In TS25.331 Section 8.1.1.6.5 (System Information Block type 5 and 5bis), UE checks the 12bits of RNC-ID for performing URA update. Therefore the UE is using the 12bits of the RNC-Id in the U\_RNTI to check for change in RNC and perform URA update.
+
+- 2> if the UE is in CELL\_PCH or URA\_PCH state:
+ - 3> for FDD and for 1.28 Mcps TDD, if the UE supports HS-DSCH reception in CELL\_PCH and URA\_PCH state; and
+ - 3> if IE "HS-DSCH paging system information" is included:
+ - 4> if this IE is not currently stored; and
+ - 4> if the value of the IE "SRNC identity" in the variable U\_RNTI is not equal to the 12 MSBs of the received IE "Cell identity" in System Information Block type 3; and
+ - 4> if the UE is in URA\_PCH state:
+ - 5> initiate the URA update procedure as specified in subclause 8.3.1, using the cause "periodic URA update".
+
+Due to this, RNC with Extended S-RNTI implementation would make sure to design the U-RNTI, to avoid unnecessary URA updates. This can be done by ensuring that the 2 MSB of the extended the S-RNTI are the same for UEs in the same area.
+
+### A2.1.3 Pooled RNCs: Solution 2
+
+In this solution a large RNC consists of 4 (or 2) RNCs each with a 12 bit RNC-ID. This could be considered a version of Solution 1, but here the large RNC is handled as a single RNC where the 2 LSBs of the RNC-ID are zero.
+
+UE Side
+
+
+
+| | |
+|----------------|---------------|
+| RNC-ID 12 bits | S-RNTI 20bits |
+|----------------|---------------|
+
+**Figure A2.1.3.1: UE Side, Normal split of U-RNTI in RNC-ID and S-RNTI**
+
+RAN Side
+
+
+
+| | | |
+|----------------|--------|----------------|
+| RNC-ID 10 bits | R
x | S-RNTI 20 bits |
+|----------------|--------|----------------|
+
+Figure A2.1.3.1: RNC Side, RNC-ID split into extended RNC-ID and sub-RNC indicator. The diagram shows a 32-bit RNC-ID structure: 10 bits for RNC-ID, 2 bits for R (sub-RNC indicator), and 20 bits for S-RNTI.
+
+**Figure A2.1.3.1: RNC Side, RNC-ID split into extended RNC-ID and sub-RNC indicator.**
+
+On the RAN side only the 10 MSBs are used for routing/addressing RNCs. Large RNC RNC-IDs are identified by RNC ID range and the 2 LSBs of RNC-ID being zero. CN routing and RNC routing would need updating to ensure that the mobility to the correct RNC occurs based on 10 bit RNC-ID. Other non-pooled RNCs will be routed in the normal way. This has perhaps more impact on the network than solution 1 but the large RNC would support the extended number of UEs, as it acts like 4 RNCs.
+
+## A2.2 RNC ID Extension
+
+The problem of insufficient RNC ID number space was identified and it was agreed to extend the range of the RNC ID. As a solution for the extension of the number space, it was agreed to increase the bit length of the RNC-ID from 12bits to 16bits by introducing a new ID with 16bits-length , and to introduce an *Extended RNC ID IE* into the relevant specifications. While the maximum number of RNCs within one PLMN in the current specification is 4096, the introduction of the new IE allows a maximum of 65536 (4096:legacy RNC ID + 61440: extended RNC-ID) RNCs to be deployed in one PLMN in the future.
+
+### A2.2.1 Solution for RNC-ID Extension
+
+The Extended RNC-ID is only introduced into the network internal signalling specifications, e.g. RANAP between RNC and CN and does not require any changes to the RRC protocol so that legacy UEs can operate in an RNS which is configured to use an extended RNC ID.
+
+This is possible by partitioning the 32bits of the U-RNTI in a different manner in RNS which is configured to use the extended RNC-ID. Thus some bits of the S-RNTI (20bits) part of the U-RNTI are used to extend the SRNC-ID part in the RNS using the extended RNC-ID. Therefore, the extension for the SRNC-ID in the network is not visible for the UE. As specified today, the UE always treats the 32 bit together as U-RNTI.
+
+
+
+**UE Side**
+
+| | |
+|--------------------------|-------------------|
+| SRNC identity
12 bits | S-RNTI
20 bits |
+|--------------------------|-------------------|
+
+**RAN Side**
+
+| | |
+|--------------------------|-------------------|
+| SRNC identity
16 bits | S-RNTI
16 bits |
+|--------------------------|-------------------|
+
+Figure A2.2.1.1: Interpretation of U-RNTI in UE side and RAN side is configured to use the extended RNC ID. The diagram shows two interpretations of the 32-bit U-RNTI. On the UE side, it is split into 12 bits for SRNC identity and 20 bits for S-RNTI. On the RAN side, it is split into 16 bits for SRNC identity and 16 bits for S-RNTI.
+
+**Figure A2.2.1.1: Interpretation of U-RNTI in UE side and RAN side is configured to use the extended RNC ID**
+
+As the same logic is applied for Cell Identity, 4MSB of the 16bit C-ID are used as an extension of RNC-ID. Thus under the RNC using the extended RNC-ID, the bits available for the C-ID are reduced to 12bits (4096).
+
+
+
+**UE Side**
+
+| | |
+|--------------------------|--------------------|
+| SRNC identity
12 bits | Cell-ID
16 bits |
+|--------------------------|--------------------|
+
+
+
+**RAN Side**
+
+| | |
+|--------------------------|--------------------|
+| SRNC identity
16 bits | Cell-ID
12 bits |
+|--------------------------|--------------------|
+
+**Figure A2.2.1.2: Interpretation of Cell identity (= UC-ID) in UE side and RAN side is configured to use the extended RNC ID**
+
+The number of UEs and cells in one RNS using the extended RNC-ID are different from the one using the current RNC ID as shown in the table below since the 4bits used for the S-RNTI and Cell ID are used as part of extended RNC-ID in the RNS.
+
+| | Current RNC-ID | Extended RNC-ID |
+|---------------------------------------------------|-----------------------|------------------------|
+| The number of UEs in RNS | 1 048 576 | 65 536 |
+| The number of UEs for Inter-RAT HO at once in RNS | 1 024 | 64 |
+| The number of cells in RNS | 65 536 | 4 096 |
+
+### A2.2.2 Rules for Configuration
+
+There are some limitations for configuring network when the extended RNC-ID scheme is used. The network configuration shall follow all four rules as stated below together.
+
+#### Explanation of terms
+
+**Legacy RNC/CN:** RNC/CN do not comprehend/support the extended RNC-ID IE/Scheme, e.g. Pre-Rel7 RNC/CN.
+
+**Upgraded RNC/CN:** RNC/CN comprehend/support the extended RNC-ID IE/Scheme and can distinguish which RNC-ID scheme are used in the received message or sending message based on the stored configuration data.
+
+##### Rule1):
+
+In case relocation needs to be supported to/from an RNC using the extended RNC-ID, it is recommended to connect the source and target RNCs to the same upgraded CN to reduce the number of upgraded CN. In case CN cannot be upgraded, it is recommended to use legacy RNC-ID under that CN. (Example in Figure A2.2.2.1).
+
+##### Rule2):
+
+Not configure the Iur interface connection between legacy RNC and upgraded RNC using the extended RNC-ID.
+
+##### Rule3):
+
+In case RNCs with legacy RNC-ID and RNCs with extended RNC-ID co-exist in the network, configure the legacy RNC-ID so that legacy RNC-ID will not be the same as the 12 bit of MSB of any of extended RNC-ID to which the legacy RNC may have Iur connection. (See the Figure A2.2.2.3 and A2.2.2.4).
+
+##### Rule4):
+
+In case a URA spanned over multiple RNCs with extended RNC-ID and the RNCs have different capability on HS-DSCH reception in URA\_PCH state, the RNCs capable of HS-DSCH reception in URA\_PCH state shall not have the same 12bit MSB in their extended RNC-ID compared to the RNCs not capable of HS-DSCH reception in URA\_PCH. (See Figures A2.2.2.5 and A2.2.2.6).
+
+#### Depiction of Configuration Rules
+
+
+
+**Only CN #1 needs to be upgraded to understand 16bit RNC-ID**
+
+RAN 1 and 4 with 12-bit RNC-ID PS only RAN 2 and 3 with 16-bit RNC-ID
+
+Diagram showing network configuration where only CN #1 needs an upgrade. CN #1 is connected to RANs 1, 2, and 3. CN #2 is connected to RAN 4. RANs 1 and 4 use 12-bit RNC-IDs (light blue), while RANs 2 and 3 use 16-bit RNC-IDs (pink). Arrows show data flow from CN #1 to RANs 2 and 3, which then flow to RAN 4. Red 'X' marks indicate that CN #1 cannot currently understand the 16-bit RNC-IDs from RANs 2 and 3.
+
+Figure A2.2.2.1: Configuration example for Rule 1 and 2
+
+
+
+**CN #1 and CN #2 need to be upgraded to understand 16bit RNC-ID**
+
+RAN 1 and 4 with 12-bit RNC-ID PS only RAN 2 and 3 with 16-bit RNC-ID
+
+Diagram showing network configuration where both CN #1 and CN #2 need upgrades. CN #1 is connected to RANs 1, 2, and 3. CN #2 is connected to RAN 4. RANs 1 and 4 use 12-bit RNC-IDs (light blue), while RANs 2 and 3 use 16-bit RNC-IDs (pink). Arrows show data flow from CN #1 to CN #2, and from CN #2 to RAN 4. Red 'X' marks indicate that both CN #1 and CN #2 cannot currently understand the 16-bit RNC-IDs from RANs 2 and 3.
+
+Figure A2.2.2.2: Configuration example for Rule 1 and 2.
+
+
+
+This diagram illustrates a problematic configuration. At the top, an orange box represents 'RNC A (Upgraded)' with 'RNC ID: 00B'. It is connected via 'Iur' links to two grey boxes: 'eHSPA Node B3' (RNC ID: 00A1) and 'eHSPA Node B' (RNC ID: 00A2). A red line labeled 'RRC Connection' connects RNC A to a UE (User Equipment) icon. The UE sends a 'Cell/URA Update' message with 'U RNTI: 00B1xxxx' to eHSPA Node B. A blue arrow points from the UE to a 'RNC-ID Table' which lists: 'RNC1: 00B', 'eHSPA NB1: 00B1', and 'eHSPA NB3: 00A1'. A red question mark is placed near the table. Another blue arrow points from eHSPA Node B to a third grey box, 'eHSPA Node B1' (RNC ID: 00B1). Below the UE, the text 'SRNC-ID: 00B' and 'S-RNTI: 1xxxx' is shown.
+
+Diagram of a problematic configuration example (does not follow Rule3).
+
+Figure A2.2.2.3: Problematic configuration example (does not follow Rule3)
+
+
+
+This diagram shows a configuration that follows Rule3. RNC A (Upgraded) with RNC ID: 00B is connected via 'Iur' links to 'eHSPA Node B3' (RNC ID: 00A1) and 'eHSPA Node B2' (RNC ID: 00A2). A red 'RRC Connection' line connects RNC A to a UE. The UE sends a 'Cell/URA Update' with 'U RNTI: 00B1xxxx' to eHSPA Node B2. A blue arrow points to a 'RNC-ID Table' containing: 'RNC1: 00B' and 'eHSPA NB3: 00A1'. A dashed line labeled 'No Iur and not neighbouring' connects eHSPA Node B2 to 'eHSPA Node B1' (RNC ID: 00B1). Below this, a note states: 'No case that UE anchored by eHSPA Node B1 moves to cell under the Node B2', accompanied by a crossed-out UE icon. Below the UE, the text 'SRNC-ID: 00B' and 'S-RNTI: 1xxxx' is shown.
+
+Diagram of a configuration example for Rule3.
+
+Figure A2.2.2.4: Configuration example for Rule3
+
+
+
+Diagram of a problematic configuration example (Figure A2.2.2.5) showing three eHSPA nodes (B1, B2, B3) with RNC IDs 00A1, 00A2, and 00A3. Node B2 is highlighted in yellow and labeled 'Non Capable of Enhanced-FACH SRNC for UE1'. Nodes B1 and B3 are labeled 'Capable of Enhanced-FACH'. Arrows show 'Paging Request' messages from B2 to B1 and B3, with question marks indicating uncertainty. Below the nodes, a 'URA' label is present. A blue double-headed arrow labeled 'RRC' connects the URA to a UE. Another UE is shown to the right, with a dashed blue arrow pointing to it and the text 'UE does NOT send URA Update'.
+
+Figure A2.2.2.5 Problematic configuration example (does not follow Rule4)
+
+
+
+Diagram of a configuration example for Rule 4 (Figure A2.2.2.6) showing three eHSPA nodes (B1, B2, B3) with RNC IDs 00A1, 00B1, and 00A2. Node B2 is highlighted in yellow and labeled 'Non Capable of Enhanced-FACH'. Nodes B1 and B3 are labeled 'Capable of Enhanced-FACH'. Arrows show 'Paging Request' messages from B2 to B1 and B3. Below the nodes, a 'URA' label is present. A blue double-headed arrow labeled 'RRC' connects the URA to a UE. Another UE is shown to the right, with a blue arrow labeled 'URA Update' pointing to it and a red arrow labeled 'RRC Release' pointing away from it.
+
+Figure A2.2.2.6 Configuration example for Rule4
+
+### A2.2.3 Configuration Example
+
+The RNC ID configuration example below is following the rules listed in A2.2.2 and showing the configuration in Figure A2.2.2.2 in a large scale.
+
+Error! No
+
+60
+
+Error! No text of specified style in
+
+
+
+The diagram illustrates a network configuration using hexagonal cells to represent different types of nodes and RNCs. A legend on the right indicates that cyan hexagons are 'Overlay cells' and purple hexagons are 'Non-Overlay cells'.
+
+- RNS\_A:** A cluster of cells at the top. It includes a central cyan overlay cell labeled 'RNC\_A 00B (Upgraded to Rel7)'. Surrounding this are several purple non-overlay cells, many labeled 'NB (f1)'. Some cells contain additional labels: 'eNB (f2) 00A1', 'eNB (f2) 00A2', 'eNB3 (f2) 00C1', 'eNB (f2) 00C2', 'eNB (f2) 00C3', and 'eNB (f2) 00C4'. Connections between RNC\_A and cells are labeled 'lub' (red lines) and 'lur' (blue lines).
+- RNS\_B:** A cluster of cells on the left, labeled 'RNC\_B 01B (Upgraded)'. It contains purple non-overlay cells labeled 'NB (f1)'. One cell contains 'NB (f1)' and 'eNB (f2) 00A5'. Connections are labeled 'lub' (red) and 'lur' (blue).
+- RNS\_C:** A cluster of cells at the bottom, labeled 'RNC\_C 00A (Upgraded)'. It includes a central cyan overlay cell. Surrounding cells are purple non-overlay cells labeled 'NB (f1)'. Some contain 'eNB (f2) 00B1', 'eNB3 (f2) 00B3', 'eNB (f2) 00B2', and 'eNB (f2) 00B4'. Connections are labeled 'lub' (red) and 'lur' (blue).
+
+Green lines connect various cells within the RNS clusters. Dotted lines indicate connections between RNS\_B and RNS\_C.
+
+Diagram showing RNC ID configuration with overlay and non-overlay cells for RNS\_A, RNS\_B, and RNS\_C.
+
+Figure A2.2.3.1: Valid RNC ID Configuration Example
+
+# Annex B (informative): Change history
+
+| Change history | | | | | |
+|----------------|---------|---------------------------------|-----------|-------------|--------------------------------------------------------|
+| TSG RAN# | Version | CR | Tdoc RAN | New Version | Subject/Comment |
+| RAN_05 | - | - | - | 3.0.0 | Approved at TSG RAN #5 and placed under Change Control |
+| RAN_06 | 3.0.0 | - | RP-99735 | 3.1.0 | Approved at TSG RAN #6 |
+| RAN_06 | 3.0.0 | - | RP-99736 | 3.1.0 | Approved at TSG RAN #6 |
+| RAN_06 | 3.0.0 | - | RP-99737 | 3.1.0 | Approved at TSG RAN #6 |
+| RAN_06 | 3.0.0 | - | RP-99738 | 3.1.0 | Approved at TSG RAN #6 |
+| RAN_07 | 3.1.0 | - | RP-000073 | 3.2.0 | Approved at TSG RAN #7 |
+| RAN_08 | 3.2.0 | - | RP-000231 | 3.3.0 | Approved at TSG RAN #8 |
+| RAN_09 | 3.3.0 | 013
014
015
016
017 | RP-000370 | 3.4.0 | Approved at TSG RAN #9 |
+| RAN_10 | 3.4.0 | 018
019 | RP-000607 | 3.5.0 | Approved at TSG RAN #10 |
+| RAN_11 | 3.5.0 | 020
021 | RP-010107 | 3.6.0 | Approved at TSG RAN #11 |
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|---------------------|-----|---------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| March 01 | 11 | RP-010164 | 23 | 1 | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 |
+| June 01 | 12 | RP-010370 | 025,
028,
032 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 |
+| June 01 | 12 | RP-010389 | 026,
029 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 |
+| June 01 | 12 | RP-010403 | 030 | | Approved at TSG RAN #12 and placed under Change Control | 4.1.0 | 5.0.0 |
+| 09/2001 | 13 | RP-010575 | 033 | | Uplink power control for LCR TDD | 5.0.0 | 5.1.0 |
+| 09/2001 | 13 | RP-010575 | 038 | | Clarification of coordinated DCHs | 5.0.0 | 5.1.0 |
+| 03/2002 | 15 | RP-020221 | 046 | | New UE identifier for MAC-c/sh multiplexing for DSCH | 5.1.0 | 5.2.0 |
+| 03/2002 | 15 | RP-020189 | 044 | 2 | Introduction of IP Transport in UTRAN | 5.1.0 | 5.2.0 |
+| 03/2002 | 15 | RP-020190 | 039 | 2 | HSDPA Additions for REL-5 | 5.1.0 | 5.2.0 |
+| 03/2002 | 15 | RP-020195 | 045 | 1 | NNSF Functional Description | 5.1.0 | 5.2.0 |
+| 06/2002 | 16 | RP-020422 | 047 | | HSDPA-related changes | 5.2.0 | 5.3.0 |
+| 06/2002 | 16 | RP-020421 | 048 | | Corrections on ATM-IP interoperability scenarios | 5.2.0 | 5.3.0 |
+| 06/2002 | 16 | RP-020399 | 051 | | New UE identifier for Shared Channel handling for TDD DSCH/USCH | 5.2.0 | 5.3.0 |
+| 06/2002 | 16 | RP-020421 | 052 | | Introduction of IP transport in UTRAN | 5.2.0 | 5.3.0 |
+| 06/2002 | 16 | RP-020421 | 053 | 2 | Independence of RNL and TNL | 5.2.0 | 5.3.0 |
+| 09/2002 | 17 | RP-020605 | 055 | 1 | Clarification on ALCAP Identifiers | 5.3.0 | 5.4.0 |
+| 09/2002 | 17 | RP-020627 | 056 | 1 | Introduction of Iur-g | 5.3.0 | 5.4.0 |
+| 09/2002 | 17 | RP-020625 | 057 | 1 | Introduction of the Access Control Function: SNA | 5.3.0 | 5.4.0 |
+| 09/2002 | 17 | RP-020628 | 059 | | Introduction of HS-DSCH RNTI in TS25.401 | 5.3.0 | 5.4.0 |
+| 12/2002 | 18 | RP-020750 | 062 | | Definition of URA | 5.4.0 | 5.5.0 |
+| 12/2002 | 18 | RP-020764 | 064 | 1 | Corrections to the SNA Access Control Function | 5.4.0 | 5.5.0 |
+| 03/2003 | 19 | RP-030084 | 065 | | CR on revising the definition of SAS to support all REL-4 UE positioning methods | 5.5.0 | 6.0.0 |
+| 06/2003 | 20 | RP-030317 | 068 | 1 | Correction to HS-DSCH transport in case of SRNC not coincident with DRNC and without flow control in the DRNC | 6.0.0 | 6.1.0 |
+| 12/2003 | 22 | RP-030675 | 076 | 1 | NAS/AS issue for shared networks in connected mode | 6.1.0 | 6.2.0 |
+| 06/2004 | 24 | RP-040182 | 084 | 1 | Introduction of Iu and Iur support of Network Assisted Cell Change from UTRAN to GERAN | 6.2.0 | 6.3.0 |
+| 06/2004 | 24 | RP-040254 | 086 | | Completion of the REL-5 IP Transport WI | 6.2.0 | 6.3.0 |
+| 09/2004 | 25 | RP-040303 | 087 | 1 | Introduction of Iuant into UTRAN architecture for control of RET Antennas | 6.3.0 | 6.4.0 |
+| 09/2004 | 25 | RP-040297 | 091 | | Terminology correction of IP ALCAP CR | 6.3.0 | 6.4.0 |
+| 12/2004 | 26 | RP-040439 | 92 | | Support of MOCN and GWCN configurations in UTRAN | 6.4.0 | 6.5.0 |
+| 12/2004 | 26 | RP-040440 | 94 | 1 | Introduction of E-DCH in 25.401 | 6.4.0 | 6.5.0 |
+| 12/2004 | 26 | RP-040437 | 95 | 1 | CR for Introducing MBMS in 25.401 | 6.4.0 | 6.5.0 |
+| 06/2005 | 28 | RP-050225 | 97 | | Feature Cleanup: Removal of CPCH | 6.5.0 | 6.6.0 |
+| 06/2005 | 28 | RP-050222 | 99 | | Feature clean-up: Removal of DSCH (FDD mode) | 6.5.0 | 6.6.0 |
+| 09/2005 | 29 | RP-050435 | 101 | | E-DCH Protocol Model | 6.6.0 | 6.7.0 |
+
+| | | | | | | | |
+|---------|-------|-----------|-----|---|----------------------------------------------------------------------------------|--------|--------|
+| 03/2006 | 31 | RP-060072 | 100 | 2 | Enabling the Providing of Velocity | 6.7.0 | 7.0.0 |
+| 03/2006 | 31 | RP-060073 | 102 | 1 | Introduction of 7.68Mcps TDD option | 6.7.0 | 7.0.0 |
+| 09/2006 | 33 | RP-060511 | 105 | | Introduction of 3.84 Mcps and 7.68Mcps TDD Enhanced Uplink | 7.0.0 | 7.1.0 |
+| 09/2006 | 33 | RP-060499 | 107 | 2 | MBMS Transport Identifiers | 7.0.0 | 7.1.0 |
+| 12/2006 | 34 | RP-060698 | 109 | 1 | Delete reference to "MBMS UTRAN Cell Group Identifier" | 7.1.0 | 7.2.0 |
+| 12/2006 | 34 | RP-060837 | 110 | 1 | Consistency of Specification Notations | 7.1.0 | 7.2.0 |
+| 03/2007 | 35 | RP-070058 | 111 | | Introduction of TMA | 7.2.0 | 7.3.0 |
+| 03/2007 | 35 | RP-070062 | 112 | | Introduction of 1.28 Mcps TDD Enhanced Uplink | 7.2.0 | 7.3.0 |
+| 06/2007 | 36 | RP-070328 | 113 | 2 | Introduction of Enhanced Cell_FACH state feature | 7.3.0 | 7.4.0 |
+| 09/2007 | 37 | RP-070568 | 114 | 1 | Introduction of GANSS (Galileo and Additional Navigation Satellite Systems) | 7.4.0 | 7.5.0 |
+| 09/2007 | 37 | RP-070650 | 115 | 1 | Introduction of multi-frequency for 1.28Mcps TDD in 25.401 | 7.4.0 | 7.5.0 |
+| 06/2008 | 40 | RP-080297 | 116 | | MAC-ehs in CELL_DCH | 7.5.0 | 7.6.0 |
+| 06/2008 | 40 | RP-080306 | 118 | | Introduction of Improved L2 for Uplink | 7.6.0 | 8.0.0 |
+| 09/2008 | 41 | RP-080590 | 122 | 1 | The supplement of IPv4 encoding in NSAP structure | 8.0.0 | 8.1.0 |
+| 09/2008 | 41 | RP-080587 | 123 | | Introduction of Enhanced Uplink in Cell_FACH | 8.0.0 | 8.1.0 |
+| 12/2008 | 42 | RP-080849 | 124 | 1 | Enable to dynamically control the MBMS services in MBSFN | 8.1.0 | 8.2.0 |
+| 12/2008 | 42 | RP-080850 | 125 | 1 | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.1.0 | 8.2.0 |
+| 12/2008 | 42 | RP-080840 | 126 | | Introduction of Enhanced Relocation | 8.1.0 | 8.2.0 |
+| 12/2009 | - | - | - | - | Created version 9.0.0 based on version 8.2.0 | 8.2.0 | 9.0.0 |
+| 03/2010 | 47 | RP-100229 | 128 | 1 | SPID description and implementation guidelines in UTRAN | 9.0.0 | 9.1.0 |
+| 12/2010 | 50 | RP-101389 | 131 | | Introduction of the SIPTO at lu-PS Function | 9.1.0 | 10.0.0 |
+| 12/2010 | 50 | RP-101272 | 133 | 1 | Adding support for ECN in UTRA | 9.1.0 | 10.0.0 |
+| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.0 | 10.1.0 |
+| 03/2011 | 51 | RP-110230 | 136 | 1 | Support for MDT | 10.0.0 | 10.1.0 |
+| 06/2011 | 52 | RP-110684 | 137 | 1 | Correction of references | 10.1.0 | 10.2.0 |
+| 06/2011 | 52 | RP-110694 | 138 | 3 | Introduction of Enhancements of Iur-g Interface | 10.1.0 | 10.2.0 |
+| 09/2012 | 57 | RP-121140 | 139 | 3 | EAB for CN Overload Control | 10.2.0 | 11.0.0 |
+| 12/2012 | 58 | RP-121736 | 140 | 2 | Documenting the Description of Extended S-RNTI and RNC-ID operation | 11.0.0 | 11.1.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25412/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-11/25_series/25412/0b87abe67b21a93777287649c33e755d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9b2721a50f345735bb75e448a1f742a1685b762
--- /dev/null
+++ b/marked/Rel-11/25_series/25412/0b87abe67b21a93777287649c33e755d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f0e04cbe07c009ae313f048589ea54e3259459366e9a4927eb3cb5c10dcc28e
+size 39020
diff --git a/marked/Rel-11/25_series/25412/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/25_series/25412/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a1b938ddf9aa6437ec775c88641d361886d4247
--- /dev/null
+++ b/marked/Rel-11/25_series/25412/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a756a537f7b9a675e1815e2c318edee48941673b6f5a04c8ef13d658c51228fb
+size 34951
diff --git a/marked/Rel-11/25_series/25412/raw.md b/marked/Rel-11/25_series/25412/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..70a80ce2286683707e3585b1a12b8570096b0cc7
--- /dev/null
+++ b/marked/Rel-11/25_series/25412/raw.md
@@ -0,0 +1,275 @@
+
+
+
+
+
+
+# --- Contents
+
+- 1 Scope.....5
+- 2 References.....5
+- 3 Abbreviations.....6
+- 4 Data Link Layer .....7
+ - 4.1 ATM Transport Option .....7
+ - 4.2 IP Transport Option.....7
+- 5 RANAP Signalling Bearer .....7
+ - 5.1 Introduction .....7
+ - 5.2 Signalling Bearer for Circuit Switched Domain .....7
+ - 5.2.1 Protocol Stack for the CS Domain .....7
+ - 5.2.2 ATM Transport Option.....8
+ - 5.2.3 IP Transport Option.....8
+ - 5.3 Signalling Bearer for Packet Switched Domain.....9
+ - 5.3.1 Protocol Stack for the PS Domain.....9
+ - 5.3.2 ATM Transport Option 1.....9
+ - 5.3.3 ATM Transport Option 2.....10
+ - 5.3.4 IP Transport Option.....10
+ - 5.4 Services Provided by the Signalling Bearer.....10
+- Annex A (informative): Change History.....11
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the standards for Signalling Transport to be used across Iu Interface. Iu Interface is a logical interface between the RNC and the UTRAN Core Network. The present document describes how the RANAP signalling messages are transported over Iu.
+
+# --- 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] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN Signalling ATM Adaptation Layer (SAAL) - overview description".
+- [2] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM Adaptation Layer – Service Specific Connection Oriented Protocol (SSCOP)".
+- [3] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer – Service Specific Co-ordination Function for signalling at the Network Node Interface (SSCF AT NNI)".
+- [4] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
+- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [6] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Type 5".
+- [7] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [8] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages".
+- [9] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [10] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [11] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide".
+- [12] ITU-T Recommendation Q.716 (1993-03): "Signalling Connection Control Part (SCCP) performance".
+- [13] IETF RFC 791 (1981-09): "Internet Protocol".
+- [14] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
+- [15] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM".
+- [16] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol".
+- [17] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)"
+- [18] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles".
+
+- [19] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)".
+- [20] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [21] IETF RFC 2507 (1999-02): "IP header compression".
+- [22] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [23] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [24] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [25] IETF RFC 2460 (1996-12): "Internet Protocol, Version 6 (Ipv6) Specification".
+- [26] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [27] Void.
+- [28] IETF RFC 3031 (2001-01): "MPLS".
+- [29] IETF RFC 3153 (2001-08): "PPPmultiplexing".
+- [30] IETF RFC 3309 (2002-09): "SCTP Checksum Change".
+- [31] ANSI T1.111-2001: "Signalling System Number 7 (SS7) - Message Transfer Part (MTP)".
+- [32] ANSI T1.112-2001: "Signalling System Number 7 (SS7) -- Signalling Connection Control Part (SCCP)".
+- [33] ANSI T1.645-1995 (R2003), "B-ISDN Signaling ATM Adaptation Layer - Service Specific Coordination Function for Support of Signaling at the Network Node Interface (SSCF at the NNI)".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-----------|----------------------------------------------------------|
+| AAL | ATM Adaptation Layer |
+| AAL2 | ATM Adaptation Layer 2 |
+| AAL5 | ATM Adaptation Layer 5 |
+| ATM | Asynchronous Transfer Mode |
+| CS | Circuit Switched |
+| DiffServ | Differentiated Services |
+| HDLC | High Level Data Link Control |
+| IP | Internet Protocol |
+| M3UA | SS7 MTP3 User Adaptation Layer |
+| ML/MC-PPP | Muti-Link/Multi-Class PPP |
+| MPLS | Multiprotocol Label Switching |
+| MSC | Mobile services Switching Center |
+| MTP3-B | Message Transfer Part |
+| PPP | Point-to-Point protocol |
+| PPPMux | PPP Multiplexing |
+| PS | Packet Switched |
+| RANAP | Radio Access Network Application Part |
+| RNC | Radio Network Controller |
+| SAAL-NNI | Signalling ATM Adaptation Layer – Network Node Interface |
+| SCCP | Signalling Connection Control Part |
+| SCTP | Stream Control Transmission Protocol |
+| SGSN | Serving GPRS Support Node |
+| SSCF | Service Specific Co-ordination Function |
+| SSCOP | Service Specific Connection Oriented Protocol |
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the radio network control plane according to (ITU-T Rec. I.361 [5]). The structure of the cell header used in the UTRAN Iu interface is the cell header format and encoding at NNI (see Figure 3/I.361).
+
+## 4.2 IP Transport Option
+
+An RNC/CN using IP transport option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [19], IETF RFC 1662 [20]).
+
+Note: This does not preclude the single implementation and use of any other data link layer protocol (e.g. PPPMux (IETF RFC 3153 [29])/AAL5/ATM, PPP/AAL2/ATM, Ethernet, MPLS (IETF RFC 3031 [28])/ATM, etc.) fulfilling the UTRAN requirements toward the upper Layers.
+
+An RNC/CN using IP transport option having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [21]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [22], IETF RFC 2686 [23]). In this case, the negotiation of header compression (IETF RFC 2507 [21]) over PPP shall be performed via IETF RFC 2509 [24].
+
+# --- 5 RANAP Signalling Bearer
+
+## 5.1 Introduction
+
+This subclause specifies the Signalling Bearer protocol stack that supports the RANAP signalling protocol.
+
+The following requirements on the Signalling Bearer can be stated:
+
+- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode;
+- provide separate independent connections for distinguishing transactions with individual UE's;
+- supervise the 'UE connections' and provide connection status information to the Upper Layers for individual UE's;
+- provide networking and routing functions;
+- provide redundancy in the signalling network;
+- provide load sharing.
+
+## 5.2 Signalling Bearer for Circuit Switched Domain
+
+### 5.2.1 Protocol Stack for the CS Domain
+
+The protocol stacks for the CS Domain are shown in figure 1. The standard allows operators to choose one out of two standardised protocol suites for transport of SCCP messages.
+
+Figure 1 shows, for the Iu IP CS domain, the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture.
+
+The following figure 1 also illustrates the protocol model having Broadband Signalling System No.7 as the signalling bearer for RANAP over the Iu interface that fulfils the requirements. Figure 1 shows, for the CS domain, the point at which the service primitives are invoked. The SAP provides the SCCP primitives.
+
+
+
+The diagram illustrates two protocol stacks for the lu-CS Control Plane. Both stacks begin with the RANAP layer at the top, which connects to an SCCP-SAP (Service Access Point). Below the SCCP-SAP, the stacks differ based on the transport option.
+
+**Protocol stack for ATM transport option (Left):**
+
+- RANAP
+- SCCP-SAP
+- SCCP
+- MTP3-B
+- SAAL-NNI
+- ATM
+
+**Protocol stack for IP transport option (Right):**
+
+- RANAP
+- SCCP-SAP
+- SCCP
+- M3UA
+- SCTP
+- IP
+- Data Link
+
+Figure 1: SAP between RANAP and its transport for lu - CS Domain. The diagram shows two protocol stacks. The left stack is for the ATM transport option, and the right stack is for the IP transport option. Both stacks start with the RANAP layer at the top, which connects to an SCCP-SAP. Below the SCCP-SAP, the ATM stack consists of SCCP, MTP3-B, SAAL-NNI, and ATM layers. The IP stack consists of SCCP, M3UA, SCTP, IP, and Data Link layers.
+
+Protocol stack for ATM transport option
+
+Protocol stack for IP transport option
+
+Figure 1: SAP between RANAP and its transport for lu - CS Domain
+
+### 5.2.2 ATM Transport Option
+
+1. **SCCP** (ITU-T Rec. Q.711 [7] or ANSI T1.112-2001 [32]) provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. SCCP shall be used as specified in TS 25.410 [18].
+2. **MTP3-B** (ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]) provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded. MTB3-B shall comply with ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31].
+3. **SAAL-NNI** (ITU-T Rec. Q.2100 [1]) consists of the following sub-layers: - **SSCF** (ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 (R2003) [33]), - **SSCOP** (ITU-T Rec. Q.2110 [2]) and - **AAL5** (ITU-T Rec. I.363.5 [6]). The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells. It shall be possible to use SAAL-NNI connections pre-configured as PVCs for signalling transport on the lu-Interface.
+4. **ATM** (ITU-T Rec. I.361 [5]).
+
+### 5.2.3 IP Transport Option
+
+1. **SCCP**, see subclause 5.2.2.
+2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the MSC when it is a newly introduced entity in the network.
+3. **SCTP** refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The checksum method specified in IETF RFC 3309 [30] shall be used instead of the method specified in IETF RFC 2960 [16]. Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint.
+4. **IP**. IPv6 shall be supported according to IETF RFC 2460 [25]. IPv4 support (IETF RFC 791 [13]) is optional.
+
+Note: This does not preclude the single implementation and use of IPv4.
+
+Due to the possible transition from IPv4 to IPv6 the IP dual stack support is recommended.
+
+An RNC/CN using IP transport option shall support Diffserv code point marking IETF RFC 2474 [26]. The Diffserv code point may be determined from the application parameters.
+
+## 5.3 Signalling Bearer for Packet Switched Domain
+
+### 5.3.1 Protocol Stack for the PS Domain
+
+The protocol stacks for the PS Domain is shown in figure 2. The standard allows operators to choose one out of three standardised protocol suites for transport of SCCP messages.
+
+
+
+The diagram illustrates two protocol stacks for the Iu-PS Control Plane. Both stacks begin with RANAP at the top, followed by an SCCP-SAP (Service Access Point). Below the SCCP-SAP is the SCCP layer. The left stack, labeled 'Protocol stacks for ATM transport options', continues with MTP3-B and M3UA, followed by SCTP, SAAL-NNI, IP, AAL5, and finally ATM. The right stack, labeled 'Protocol stack for IP transport option', continues with M3UA, SCTP, IP, and Data Link.
+
+Figure 2: SAP between RANAP and its transport for the Iu -IP domain. The diagram shows two protocol stacks. The left stack is for ATM transport options, and the right stack is for IP transport option. Both stacks start with RANAP at the top, followed by SCCP-SAP, then SCCP. Below SCCP, the ATM stack includes MTP3-B, M3UA, SCTP, SAAL-NNI, IP, AAL5, and ATM. The IP stack includes M3UA, SCTP, IP, and Data Link.
+
+Protocol stacks for ATM transport options
+
+Protocol stack for IP transport option
+
+Figure 2: SAP between RANAP and its transport for the Iu -IP domain
+
+Figure 2 shows, for the Iu IP domain, the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture.
+
+### 5.3.2 ATM Transport Option 1
+
+1. **SCCP** (ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8] /ITU-T Rec. Q.713 [9] /ITU-T Rec. Q.714 [10] /ITU-T Rec. Q.715 [11] /ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32]) provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. The SCCP shall be used as specified in TS 25.410 [18].
+2. **MTP3-B** (ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]) provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded. MTB3-B shall comply with ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31].
+3. **SAAL-NNI** (ITU-T Rec. Q.2100 [1]) consists of the following sub-layers: - **SSCF-NNI** (ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 (R2003) [33]), - **SSCOP** (ITU-T Rec. Q.2110 [2]) and - **AAL5** (ITU-T Rec. I.363.5 [6]). The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells. It shall be possible to use SAAL-NNI connections pre-configured as PVCs for signalling transport on the Iu-interface.
+4. **ATM** (ITU-T Rec. I.361 [5]).
+
+### 5.3.3 ATM Transport Option 2
+
+1. **SCCP**, see subclause 5.3.2.
+
+2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the SGSN when it is a newly introduced entity in the network.
+3. **SCTP** refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The multi-homing services of SCTP shall be required at both ends of an SCTP-association to enable transport redundancy and reliability. **M3UA**. An implementation of SCTP to this document shall utilise the new checksum method specified in IETF RFC 3309 [30] instead of the method specified in IETF RFC 2960 [16].
+4. **IP** (IETF RFC 791 [13]) over ATM is defined in IETF RFC 2684 [14] and IETF RFC 2225 [15].
+5. **AAL5** refers to ITU-T Rec. I.363.5 [6]. It shall be possible to use AAL5 connections pre-configured as PVCs for signalling transport on the Iu-interface.
+
+### 5.3.4 IP Transport Option
+
+1. **SCCP** , see subclause 5.3.2.
+2. **M3UA**, refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the SGSN when it is a newly introduced entity in the network.
+3. **SCTP**, refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. An implementation of SCTP to this document shall utilise the new checksum method specified in IETF RFC 3309 [30] instead of the method specified in IETF RFC 2960 [16]. Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint.
+4. **IP**. IPv6 shall be supported according to IETF RFC 2460 [25]. IPv4 support (IETF RFC 791 [13]) is optional.
+
+Note: This does not preclude the single implementation and use of IPv4.
+
+Due to the possible transition from IPv4 to IPv6, the IP dual stack support is recommended.
+
+An RNC/CN using IP transport option shall support Diffserv code point marking (IETF RFC 2474 [26]). The Diffserv code point may be determined from the application parameters.
+
+## 5.4 Services Provided by the Signalling Bearer
+
+When considering the requirements that the upper layers, i.e. RANAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in references ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8] /ITU-T Rec. Q.713 [9] /ITU-T Rec. Q.714 [10] /ITU-T Rec. Q.715 [11] / ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32].
+
+# --- Annex A (informative): Change History
+
+| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New |
+|------------|-----------|------|-----|------------------------------------------------------------|--------|
+| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 |
+| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 |
+| 03/2011 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 |
+| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 |
+| 06/2011 | RP-110685 | 0026 | | Correction to the References in 25.412 | 10.1.0 |
+| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25413/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/marked/Rel-11/25_series/25413/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4be78f14cf4b911ec531f1f43654237652012249
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9accbb499a596eda11022894d398c37bb4395296675653018f2af56bf759395
+size 23504
diff --git a/marked/Rel-11/25_series/25413/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/Rel-11/25_series/25413/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38538781d615491bd7a7f26d8adbfc5da8edf846
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e6e8a76331c99404bbf9d0e78f451245c8491c43d05e9e05443017ffa382c55
+size 26157
diff --git a/marked/Rel-11/25_series/25413/0ca7be012da0968655b2468b0fa108c3_img.jpg b/marked/Rel-11/25_series/25413/0ca7be012da0968655b2468b0fa108c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..890b522e531026c8272a787ea24025bf419a5513
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/0ca7be012da0968655b2468b0fa108c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:324339c0aa864fc11e4e844b94a64ca127e0deb5c392a9c5a8d03d551c11bd1d
+size 10426
diff --git a/marked/Rel-11/25_series/25413/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-11/25_series/25413/0f1767577a073167eb9628d72034e083_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb98a221b489886bfe712606623276800a5b757c
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/0f1767577a073167eb9628d72034e083_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0615c0471d0e57bc835524f3e83f1a46127d9b0c115cd1347b201a79f67c8c0
+size 16288
diff --git a/marked/Rel-11/25_series/25413/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg b/marked/Rel-11/25_series/25413/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..260110e533a94aaa89b80644147fb41552f38ae6
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05621e20d7a45f0810253ce24a631e306981467692be5176ebaba782ad4db506
+size 18897
diff --git a/marked/Rel-11/25_series/25413/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/Rel-11/25_series/25413/184d3d9a856c77aae93652f4fe30f752_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be27dd77d1ea84e9ad6317d71d56e10bbc288206
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/184d3d9a856c77aae93652f4fe30f752_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8f6f01d1c81041d4c227c018cb8060e71e674e5da0e7a8108bbdfbc2f3ec816
+size 16788
diff --git a/marked/Rel-11/25_series/25413/18d7d8de298d79e7bc87af5217f11203_img.jpg b/marked/Rel-11/25_series/25413/18d7d8de298d79e7bc87af5217f11203_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29438831a3e1ab25aef9e3a6cc9e74257a3a9e71
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/18d7d8de298d79e7bc87af5217f11203_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53cee48c6b41f189876a9fde0ae2f619d202a3a8f1e2ccbaa7ed78887a7cae53
+size 19534
diff --git a/marked/Rel-11/25_series/25413/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-11/25_series/25413/195611c20b2dc7ed0fa3033392e22908_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..78a2c23947550028024881cd1ccf2dcb55f8e091
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/195611c20b2dc7ed0fa3033392e22908_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eced70b4e244e02838b2944da003adaac629e35d8fa6dce34272562ce6d0960e
+size 15803
diff --git a/marked/Rel-11/25_series/25413/1aa60e916522640d538e81fd202045b4_img.jpg b/marked/Rel-11/25_series/25413/1aa60e916522640d538e81fd202045b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b83c5de664bb1a5995518ba8387670cd9a4dc002
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/1aa60e916522640d538e81fd202045b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c42df21b49b1ab5465dd3a804c07ec34a1593d506463e3d7ffa2368dcd9fb982
+size 9032
diff --git a/marked/Rel-11/25_series/25413/279ae82c0ef66d5fb9a204a4218a78dc_img.jpg b/marked/Rel-11/25_series/25413/279ae82c0ef66d5fb9a204a4218a78dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8808fb0568502ea6d9d45210741096c73dd717d
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/279ae82c0ef66d5fb9a204a4218a78dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5696b42a490ef835a8e92253678524de3ff23fca1408af62dfaf547ee770ccc
+size 14490
diff --git a/marked/Rel-11/25_series/25413/294444660b1376c49aeca748b8184e77_img.jpg b/marked/Rel-11/25_series/25413/294444660b1376c49aeca748b8184e77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00043efe82ecce09ff2c5b2ee52d8a45b30d9942
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/294444660b1376c49aeca748b8184e77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec5aa11a0b8c4b7e0013cc88c91d357f8a2025910b48ceb5dbbef63e380e64c8
+size 17514
diff --git a/marked/Rel-11/25_series/25413/2aa94b70ba3fadcba8420d9e3128253a_img.jpg b/marked/Rel-11/25_series/25413/2aa94b70ba3fadcba8420d9e3128253a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f7690463f98c0c723a8337babab20c016c9bdaa
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/2aa94b70ba3fadcba8420d9e3128253a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ceaa7ff6d7f833e413c7d35864c1f7281a0c503d960c2cec16c072c8fcdaaf5
+size 13792
diff --git a/marked/Rel-11/25_series/25413/2d863654cf3803cea82b686d9b3ebee8_img.jpg b/marked/Rel-11/25_series/25413/2d863654cf3803cea82b686d9b3ebee8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..684b7336b7b14dc8139eae54d4822ee7b45520b3
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/2d863654cf3803cea82b686d9b3ebee8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e69be67b2c29dac1bf232e30b15e0c122cfc85f6a477be5acc907ee0a322cdc
+size 25697
diff --git a/marked/Rel-11/25_series/25413/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-11/25_series/25413/31ef15d175af5babdbf4d2fbac884c1b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..010bd8336b744c4aaee9db5535e3215537641b46
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/31ef15d175af5babdbf4d2fbac884c1b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfc8eb4fff5463a07d253e63d2c134cfb63b1e5c2c5eefdf65a1a03eaf6807aa
+size 11402
diff --git a/marked/Rel-11/25_series/25413/3620f4edb9cb38933df56238cd9d9d7b_img.jpg b/marked/Rel-11/25_series/25413/3620f4edb9cb38933df56238cd9d9d7b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe7a6532cedaf9dd6d5bf1a9ec7c7e2d63485e01
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/3620f4edb9cb38933df56238cd9d9d7b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5ef664b3b24d4e61f3eefd546438a099480696ad255cce1f43cc55ee34cd3a0
+size 8597
diff --git a/marked/Rel-11/25_series/25413/373a4175af7be33a9c37a4a7edf83507_img.jpg b/marked/Rel-11/25_series/25413/373a4175af7be33a9c37a4a7edf83507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e375d9638069226813f4cf1f5095144bb6f3a92f
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/373a4175af7be33a9c37a4a7edf83507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:934cdf0f92a6cb3e01f0e2e2e31fcd7ecc8d6a2d7cde4f4d9415262ae5c25e1b
+size 12520
diff --git a/marked/Rel-11/25_series/25413/4304a81342b40a72da20f26eb2cb2aa0_img.jpg b/marked/Rel-11/25_series/25413/4304a81342b40a72da20f26eb2cb2aa0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77064179f7b2d92e8c988e0c23247000737b54df
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/4304a81342b40a72da20f26eb2cb2aa0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5015131e84cc860e4c8dcbc575b414f3ac9baa1a187612eed9c59664b2019b2
+size 22678
diff --git a/marked/Rel-11/25_series/25413/4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg b/marked/Rel-11/25_series/25413/4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ad2d6dad4be4543d9d5e8cc6a27775cd29e73a9
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dc747e20d3fd81c81aab4a935f3560049645f50690a427480ab17a1098a2222
+size 17144
diff --git a/marked/Rel-11/25_series/25413/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg b/marked/Rel-11/25_series/25413/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df2965cf6ea8d38e97eac52838408f144644ab14
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8bf8eb8ce682c2c18689bf54e198aec296196ed0435d0316a619d5dbf6b6f05
+size 12883
diff --git a/marked/Rel-11/25_series/25413/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-11/25_series/25413/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18a414eddd1b9533a4b8686b0deb3341e6f2a130
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da13a63248248093aca136131cdd2de31120d2dc2f37d22472e17f579cde1938
+size 23622
diff --git a/marked/Rel-11/25_series/25413/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg b/marked/Rel-11/25_series/25413/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ca6008c102437c3d7420a904b8c909beae7521f
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa6cd45c35e62075d3381b83126a913c9a75ca7095b876663082118f462de6ee
+size 16063
diff --git a/marked/Rel-11/25_series/25413/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/25_series/25413/694df81535f89c7bfb9ef0df6f130dc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..597a0e8658e5fe7fb08413952b2ab3251f168aee
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/694df81535f89c7bfb9ef0df6f130dc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20e14872760a6be5ee844657f5318a5fc83e32755e0f3ae7d895359943988733
+size 9660
diff --git a/marked/Rel-11/25_series/25413/6a09da17f0048d526c7ec1e45fc9f178_img.jpg b/marked/Rel-11/25_series/25413/6a09da17f0048d526c7ec1e45fc9f178_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..985702220f4cbaaba0a1cc9b742a792c5cabd641
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/6a09da17f0048d526c7ec1e45fc9f178_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad4d178562a0fced29a7e4040b2859d6ed6a21fc22e43acef98440ef6bf3c8ac
+size 22998
diff --git a/marked/Rel-11/25_series/25413/7156cf400ef0e19f9d06a5d0549834a3_img.jpg b/marked/Rel-11/25_series/25413/7156cf400ef0e19f9d06a5d0549834a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f9b47f3b8515909a4ba4c0891f799112525bdb0
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/7156cf400ef0e19f9d06a5d0549834a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31d627ad8d945cb53f4eea8ed0c5a26f0ea244f52b960e044862ffface8783c9
+size 8882
diff --git a/marked/Rel-11/25_series/25413/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/marked/Rel-11/25_series/25413/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ef2a90ac13a4a200ac563780f940182ae9e4fbb
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b3eaf4daaa7b99e6f733f021f1130ff0453bb1f498bc801612ead8907b82cbf
+size 15097
diff --git a/marked/Rel-11/25_series/25413/879d68959f0c0ba370ef82447298ba17_img.jpg b/marked/Rel-11/25_series/25413/879d68959f0c0ba370ef82447298ba17_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8dc27c903a87599cd39e3d4ed0a5cc54396f6093
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/879d68959f0c0ba370ef82447298ba17_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7feba49576d68628bc3d08a565a979b5b39423240e9e9403b7c8695ab8239003
+size 8213
diff --git a/marked/Rel-11/25_series/25413/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg b/marked/Rel-11/25_series/25413/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f1ba8a96a83a86403e2b7896d35ee77736f0bb5
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5df0833d90eaf0d4892001154569379c1f66d806b0bb7b252d6eed34f1161c70
+size 19822
diff --git a/marked/Rel-11/25_series/25413/8be52e8ae172cee527c14d299d386f3c_img.jpg b/marked/Rel-11/25_series/25413/8be52e8ae172cee527c14d299d386f3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62f25c3214ac09882ad0c821f17fa341130d34be
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/8be52e8ae172cee527c14d299d386f3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de61f3882e8b6995c6bd2d14442043aef1afe326d418b9a37ccb8830d34f92f1
+size 10433
diff --git a/marked/Rel-11/25_series/25413/901755bf86813427f3a32efa0363a27c_img.jpg b/marked/Rel-11/25_series/25413/901755bf86813427f3a32efa0363a27c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de7a2caafe6a674b2cf7b5dd1ea6a669a4e3326b
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/901755bf86813427f3a32efa0363a27c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d85a82ec0e0a441e03bb3919bc7e2d638487f9fce94a8b25407254e6e432e8f8
+size 22997
diff --git a/marked/Rel-11/25_series/25413/94c8aee0680a2ea73faab37ba2a0963f_img.jpg b/marked/Rel-11/25_series/25413/94c8aee0680a2ea73faab37ba2a0963f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79297172cc29adae3e53df877aee9d95906754c7
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/94c8aee0680a2ea73faab37ba2a0963f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d224a84031835dc4af29c5382a19b01bcc941fdbca0b00c06a69e241ed2548f1
+size 21614
diff --git a/marked/Rel-11/25_series/25413/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-11/25_series/25413/9ff1b32449ea068bba9647d71904bd59_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf39330076cdd14866786668b71e8c5ff59deb4a
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/9ff1b32449ea068bba9647d71904bd59_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ade340f532267d73b56859dcd0f3aadae2a29d347e35fefb48bcb10eb09eb25
+size 17710
diff --git a/marked/Rel-11/25_series/25413/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg b/marked/Rel-11/25_series/25413/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa3a22471ab737ca59e09a37fb332e404f14308d
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:506f2e1aaaa0df492ccf6cc1e679767a87efd1aff54eae2990968b71a144364c
+size 72958
diff --git a/marked/Rel-11/25_series/25413/a5af75db42b20d999e69c4930b56e26e_img.jpg b/marked/Rel-11/25_series/25413/a5af75db42b20d999e69c4930b56e26e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce6daa638332e3f81edbc503d872326a8b7d3472
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/a5af75db42b20d999e69c4930b56e26e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9affbf43f8e972b1fae85180c5ef4ae315bb21c11f06946d596ffc81a777db33
+size 21519
diff --git a/marked/Rel-11/25_series/25413/aa39f51ba214496042ee3e2ce4ecee80_img.jpg b/marked/Rel-11/25_series/25413/aa39f51ba214496042ee3e2ce4ecee80_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9f77b3a8eda76c6106743159e487fc9b7f75f52
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/aa39f51ba214496042ee3e2ce4ecee80_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f58c555446141e20f1bd3be18718cfa7cfbc0b5e62cec3b948587b0ab5529d7
+size 74755
diff --git a/marked/Rel-11/25_series/25413/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/Rel-11/25_series/25413/ac31fdfebb9751f7f10416dfe33bc872_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9639b6edfbc960927c4a7d9fab935c5c1d8c04ab
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/ac31fdfebb9751f7f10416dfe33bc872_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bac5788d7130db8730ef70b7ce6f7242e3612af1f6174497924e74f6f03656d9
+size 14100
diff --git a/marked/Rel-11/25_series/25413/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-11/25_series/25413/adc59ed6840bcb2d392ea323abfccedc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4bd10d763b1d1b00bba71d686d919ca5b711d1b7
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/adc59ed6840bcb2d392ea323abfccedc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5056b79463f47cdb73490f7f7ef66f8f61a3b94128956a39b5876e114f856192
+size 12468
diff --git a/marked/Rel-11/25_series/25413/b701cd8c436a2857a615a76a868a3bb7_img.jpg b/marked/Rel-11/25_series/25413/b701cd8c436a2857a615a76a868a3bb7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c16b13928655c4f149450a57813366c676d24e3
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/b701cd8c436a2857a615a76a868a3bb7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15b7ecb0c5e3466595511e1fec1a953ab9f667136b5f93c76d25745ff6e9bbe3
+size 7979
diff --git a/marked/Rel-11/25_series/25413/b7deb5c8e534f921026ab2447e0653b4_img.jpg b/marked/Rel-11/25_series/25413/b7deb5c8e534f921026ab2447e0653b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eeb43b88843ff93978812065de627beb5554cf89
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/b7deb5c8e534f921026ab2447e0653b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40d72a298404eb317c5960fc7a0438c74758d5376990936f7b637b390fa9d57b
+size 9073
diff --git a/marked/Rel-11/25_series/25413/b9d5785720b6edd0917019f211469dde_img.jpg b/marked/Rel-11/25_series/25413/b9d5785720b6edd0917019f211469dde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c6e0e440e93cddfc32637b3ffb80a1da1610caa
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/b9d5785720b6edd0917019f211469dde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5d83a5d66714990b580995417f56c96148dbecfcd77d9e1531e22ff4bd96109
+size 75637
diff --git a/marked/Rel-11/25_series/25413/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/Rel-11/25_series/25413/bb3063a33c89b248574f64b6d8dfc404_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c658e25d4a18178d3e5cfe6f305b6900247f3307
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/bb3063a33c89b248574f64b6d8dfc404_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5a8e209d07d481483b265db4baa2eab63dea78545b96313611e442db994f48f
+size 24067
diff --git a/marked/Rel-11/25_series/25413/bbe5fb08522c43eab0afefcac30e719b_img.jpg b/marked/Rel-11/25_series/25413/bbe5fb08522c43eab0afefcac30e719b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ab2a77969dc8c8f1d8efba1f092374376f43bc3
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/bbe5fb08522c43eab0afefcac30e719b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c7ac2185403d7e0b15b2422c45aa2e89f832d5f566fb3b636f09e912c32a359
+size 12158
diff --git a/marked/Rel-11/25_series/25413/c09b8a811aa8d56401cfa959cf953640_img.jpg b/marked/Rel-11/25_series/25413/c09b8a811aa8d56401cfa959cf953640_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..624d91d66092842ae2f282cd52dc623964fe373a
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/c09b8a811aa8d56401cfa959cf953640_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2312684ef17e06a409d421b654fb408e24add00df7fa22d6514f4188b48e5a27
+size 16397
diff --git a/marked/Rel-11/25_series/25413/c0f4777175572d5c52cae16fdddd70be_img.jpg b/marked/Rel-11/25_series/25413/c0f4777175572d5c52cae16fdddd70be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b072f40b2502ed0a3adec86b493e655c2577bcbd
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/c0f4777175572d5c52cae16fdddd70be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14641df4be6d3ac233741d395ba51ae89f5506849de654825cb5ee0ea195b8b2
+size 8304
diff --git a/marked/Rel-11/25_series/25413/c5424b117a719524c619938e97c4cb1f_img.jpg b/marked/Rel-11/25_series/25413/c5424b117a719524c619938e97c4cb1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..84044a9680ba11c59d9089f683e94ad8e2ec7184
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/c5424b117a719524c619938e97c4cb1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a80148869fbe96b9bbed27c56e61af1437e913e53a45500e1cd78fded8d9a5c
+size 74013
diff --git a/marked/Rel-11/25_series/25413/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/Rel-11/25_series/25413/d197b6ded14ea918198a280ff07122b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..72d4c97bcda6cffc9a2d588db0ac42d0eaaab269
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/d197b6ded14ea918198a280ff07122b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c91c6c7fa4ed1e8a660609c1b1f5fdd33f965a283a4cbe4388488a97a8d47a0
+size 24668
diff --git a/marked/Rel-11/25_series/25413/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-11/25_series/25413/d7948c38a18636aefecdd95388196460_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7aba172c2fa87be0917a5cf483d99c23ac50fa77
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/d7948c38a18636aefecdd95388196460_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ae0d213652ac8995f6b5450b276ef56d5e126aa5570c7900a64ce15bd47af74
+size 7663
diff --git a/marked/Rel-11/25_series/25413/daa9e738320d13f92e63ceaef7ad93c4_img.jpg b/marked/Rel-11/25_series/25413/daa9e738320d13f92e63ceaef7ad93c4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a9234cc15b6cd54f7fd7c5d3ce04ef6a949b059
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/daa9e738320d13f92e63ceaef7ad93c4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1339d8d7024c1f860b8a324d0ff94d9e77e41c3ee05a74d50b100f075b9d9366
+size 17043
diff --git a/marked/Rel-11/25_series/25413/dbb517710e0ac3c6efd29c72e14bfc2e_img.jpg b/marked/Rel-11/25_series/25413/dbb517710e0ac3c6efd29c72e14bfc2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da1fb3f192e1ad37b31e62d0357efa1261b37dfe
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/dbb517710e0ac3c6efd29c72e14bfc2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:942581776a1f9a00602d4080185ac4bb756d7cb4f23ace26b0c1354bcbc59359
+size 9018
diff --git a/marked/Rel-11/25_series/25413/ddcf2f580e914bff1e7756ed288874e1_img.jpg b/marked/Rel-11/25_series/25413/ddcf2f580e914bff1e7756ed288874e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff0609a5e1b692099aeae1ca7499e03791917147
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/ddcf2f580e914bff1e7756ed288874e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f96da7884d0484daf665a9e0051e136a54dcf9db92f6177ed3dfabfdfe859e21
+size 16838
diff --git a/marked/Rel-11/25_series/25413/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-11/25_series/25413/df1966d80c74bc127f159a48f38b13ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36a954c547483118c72cc3fa31bc67ffaacdd87e
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/df1966d80c74bc127f159a48f38b13ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86154efb1fc35e06277b598b9c80c988f779cd93e2bc60ac78b7ec99c98cc08a
+size 18038
diff --git a/marked/Rel-11/25_series/25413/df65c22a46ec3e7285e44de67d3a59cf_img.jpg b/marked/Rel-11/25_series/25413/df65c22a46ec3e7285e44de67d3a59cf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e14322cdeee57d85d9594b2a9de04d3cabc14fe
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/df65c22a46ec3e7285e44de67d3a59cf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad91b941d53a68d1591e87221dfd21bb53adb3929e16524ff3fbc6963e13aa62
+size 9803
diff --git a/marked/Rel-11/25_series/25413/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/marked/Rel-11/25_series/25413/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28f8bed1efa631eecf74c317f975d2fc8d261851
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92ffdadcb350a0044373d58ce4951bdf0c801861c1eef062670b7e923e438842
+size 8990
diff --git a/marked/Rel-11/25_series/25413/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Rel-11/25_series/25413/e5ded42f8e352da02ee86cb55550c45d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f0e50c4d280a67486c4fc4301f9b08815795acca
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/e5ded42f8e352da02ee86cb55550c45d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b47f888087df0265bbf217f356c9e1e2152f7e4cc05ecbb4bbb48c823267e33
+size 16338
diff --git a/marked/Rel-11/25_series/25413/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Rel-11/25_series/25413/f97535cdaa4fe017f4659512f4f78028_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bafafffe7584025638f99eefc45e459d535772c9
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/f97535cdaa4fe017f4659512f4f78028_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8aa647d28619df1d3f79fc813acefdfd349a7e174c8b7cce062b40f723101843
+size 21774
diff --git a/marked/Rel-11/25_series/25413/fa3258abeaa067802e97eb4d1901572f_img.jpg b/marked/Rel-11/25_series/25413/fa3258abeaa067802e97eb4d1901572f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fce0685089fc7f904abb7f73cececcb1a890b6db
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/fa3258abeaa067802e97eb4d1901572f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fdac13391cdcd79b91d150975806c7e2c61f02ad381310474e12ed41223ced7f
+size 16911
diff --git a/marked/Rel-11/25_series/25413/ff1d158cd884747c86bf1d1b07dbd61f_img.jpg b/marked/Rel-11/25_series/25413/ff1d158cd884747c86bf1d1b07dbd61f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00dd4ee48ac22c9ff5b4fe48409ef5e201c57073
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/ff1d158cd884747c86bf1d1b07dbd61f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96fe4dddeaf9acf0eeadb16a3ff9a1f5df4b0f5fc206492256afa4e287db245a
+size 8947
diff --git a/marked/Rel-11/25_series/25413/raw.md b/marked/Rel-11/25_series/25413/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d946138fbab3c085b004db1ca7f8c9ec82b1663
--- /dev/null
+++ b/marked/Rel-11/25_series/25413/raw.md
@@ -0,0 +1,18275 @@
+Error:
+
+2
+
+Error: Reference source not found
+
+---
+
+# Contents
+
+| | |
+|-----------------------------------------------------------|----|
+| Foreword..... | 13 |
+| 1 Scope..... | 14 |
+| 2 References..... | 14 |
+| 3 Definitions, symbols and abbreviations..... | 16 |
+| 3.1 Definitions..... | 16 |
+| 3.2 Symbols..... | 19 |
+| 3.3 Abbreviations..... | 19 |
+| 4 General..... | 21 |
+| 4.1 Procedure Specification Principles..... | 21 |
+| 4.2 Forwards and Backwards Compatibility..... | 21 |
+| 4.3 Specification Notations..... | 21 |
+| 5 RANAP Services..... | 22 |
+| 6 Services Expected from Signalling Transport..... | 22 |
+| 7 Functions of RANAP..... | 22 |
+| 8 RANAP Procedures..... | 24 |
+| 8.1 Elementary Procedures..... | 24 |
+| 8.2 RAB Assignment..... | 25 |
+| 8.2.1 General..... | 25 |
+| 8.2.2 Successful Operation..... | 26 |
+| 8.2.2.1 Successful Operation for GERAN Iu-mode..... | 33 |
+| 8.2.3 Unsuccessful Operation..... | 33 |
+| 8.2.4 Abnormal Conditions..... | 33 |
+| 8.3 RAB Release Request..... | 34 |
+| 8.3.1 General..... | 34 |
+| 8.3.2 Successful Operation..... | 34 |
+| 8.3.3 Abnormal Conditions..... | 35 |
+| 8.4 Iu Release Request..... | 35 |
+| 8.4.1 General..... | 35 |
+| 8.4.2 Successful Operation..... | 35 |
+| 8.4.3 Abnormal Conditions..... | 35 |
+| 8.5 Iu Release..... | 35 |
+| 8.5.1 General..... | 35 |
+| 8.5.2 Successful Operation..... | 36 |
+| 8.5.3 Abnormal Conditions..... | 37 |
+| 8.6 Relocation Preparation..... | 37 |
+| 8.6.1 General..... | 37 |
+| 8.6.2 Successful Operation..... | 37 |
+| 8.6.2.1 Successful Operation for GERAN Iu-mode..... | 41 |
+| 8.6.3 Unsuccessful Operation..... | 41 |
+| 8.6.4 Abnormal Conditions..... | 42 |
+| 8.6.5 Co-ordination of Two Iu Signalling Connections..... | 42 |
+| 8.7 Relocation Resource Allocation..... | 43 |
+| 8.7.1 General..... | 43 |
+| 8.7.2 Successful Operation..... | 43 |
+| 8.7.2.1 Successful Operation for GERAN Iu-mode..... | 48 |
+| 8.7.3 Unsuccessful Operation..... | 49 |
+| 8.7.3.1 Unsuccessful Operation for GERAN Iu-mode..... | 50 |
+| 8.7.4 Abnormal Conditions..... | 50 |
+| 8.7.5 Co-ordination of Two Iu Signalling Connections..... | 50 |
+| 8.8 Relocation Detect..... | 51 |
+| 8.8.1 General..... | 51 |
+| 8.8.2 Successful Operation..... | 51 |
+| 8.8.3 Abnormal Conditions..... | 51 |
+
+| | | |
+|----------|-----------------------------------------------------|----|
+| 8.8.4 | Co-ordination of Two Iu Signalling Connections..... | 52 |
+| 8.9 | Relocation Complete..... | 52 |
+| 8.9.1 | General..... | 52 |
+| 8.9.2 | Successful Operation..... | 52 |
+| 8.9.3 | Abnormal Conditions..... | 52 |
+| 8.9.4 | Co-ordination of Two Iu Signalling Connections..... | 52 |
+| 8.10 | Relocation Cancel..... | 53 |
+| 8.10.1 | General..... | 53 |
+| 8.10.2 | Successful Operation..... | 53 |
+| 8.10.3 | Unsuccessful Operation..... | 53 |
+| 8.10.4 | Abnormal Conditions..... | 53 |
+| 8.10.5 | Co-ordination of Two Iu Signalling Connections..... | 54 |
+| 8.11 | SRNS Context Transfer..... | 54 |
+| 8.11.1 | General..... | 54 |
+| 8.11.2 | Successful Operation..... | 54 |
+| 8.11.3 | Unsuccessful Operation..... | 54 |
+| 8.11.4 | Abnormal Conditions..... | 55 |
+| 8.12 | SRNS Data Forwarding Initiation..... | 55 |
+| 8.12.1 | General..... | 55 |
+| 8.12.2 | Successful Operation..... | 55 |
+| 8.12.3 | Abnormal Conditions..... | 55 |
+| 8.13 | SRNS Context Forwarding from Source RNC to CN..... | 55 |
+| 8.13.1 | General..... | 55 |
+| 8.13.2 | Successful Operation..... | 56 |
+| 8.13.3 | Abnormal Conditions..... | 56 |
+| 8.14 | SRNS Context Forwarding to Target RNC from CN..... | 56 |
+| 8.14.1 | General..... | 56 |
+| 8.14.2 | Successful Operation..... | 57 |
+| 8.14.3 | Abnormal Conditions..... | 57 |
+| 8.15 | Paging..... | 57 |
+| 8.15.1 | General..... | 57 |
+| 8.15.2 | Successful Operation..... | 57 |
+| 8.15.3 | Abnormal Conditions..... | 58 |
+| 8.16 | Common ID..... | 59 |
+| 8.16.1 | General..... | 59 |
+| 8.16.2 | Successful Operation..... | 59 |
+| 8.16.3 | Abnormal Conditions..... | 60 |
+| 8.17 | CN Invoke Trace..... | 60 |
+| 8.17.1 | General..... | 60 |
+| 8.17.2 | Successful Operation..... | 60 |
+| 8.17.2.1 | Successful Operation for GERAN Iu mode..... | 61 |
+| 8.17.3 | Abnormal Conditions..... | 61 |
+| 8.17.3.1 | Abnormal Conditions for GERAN Iu mode..... | 61 |
+| 8.18 | Security Mode Control..... | 62 |
+| 8.18.1 | General..... | 62 |
+| 8.18.2 | Successful Operation..... | 62 |
+| 8.18.3 | Unsuccessful Operation..... | 63 |
+| 8.18.4 | Abnormal Conditions..... | 63 |
+| 8.19 | Location Reporting Control..... | 64 |
+| 8.19.1 | General..... | 64 |
+| 8.19.2 | Successful Operation..... | 64 |
+| 8.19.3 | Abnormal Conditions..... | 65 |
+| 8.20 | Location Report..... | 65 |
+| 8.20.1 | General..... | 65 |
+| 8.20.2 | Successful Operation..... | 65 |
+| 8.20.3 | Abnormal Conditions..... | 67 |
+| 8.21 | Data Volume Report..... | 67 |
+| 8.21.1 | General..... | 67 |
+| 8.21.2 | Successful Operation..... | 67 |
+| 8.21.3 | Unsuccessful Operation..... | 68 |
+| 8.21.4 | Abnormal Conditions..... | 68 |
+
+| | | |
+|----------|------------------------------------------------------|----|
+| 8.22 | Initial UE Message..... | 68 |
+| 8.22.1 | General..... | 68 |
+| 8.22.2 | Successful Operation..... | 68 |
+| 8.22.2.1 | Successful Operation for GERAN Iu-mode..... | 69 |
+| 8.23 | Direct Transfer..... | 69 |
+| 8.23.1 | General..... | 69 |
+| 8.23.2 | Successful Operation..... | 70 |
+| 8.23.2.1 | CN Originated Direct Transfer..... | 70 |
+| 8.23.2.2 | UTRAN Originated Direct Transfer..... | 71 |
+| 8.23.3 | Abnormal Conditions..... | 71 |
+| 8.24 | Void..... | 71 |
+| 8.25 | Overload Control..... | 71 |
+| 8.25.1 | General..... | 71 |
+| 8.25.2 | Philosophy..... | 72 |
+| 8.25.3 | Successful Operation..... | 72 |
+| 8.25.3.1 | Overload at the CN..... | 72 |
+| 8.25.3.2 | Overload at the UTRAN..... | 73 |
+| 8.25.4 | Abnormal Conditions..... | 73 |
+| 8.26 | Reset..... | 73 |
+| 8.26.1 | General..... | 73 |
+| 8.26.2 | Successful Operation..... | 73 |
+| 8.26.2.1 | Reset Procedure Initiated from the CN..... | 73 |
+| 8.26.2.2 | Reset Procedure Initiated from the UTRAN..... | 74 |
+| 8.26.3 | Abnormal Conditions..... | 74 |
+| 8.26.3.1 | Abnormal Condition at the CN..... | 74 |
+| 8.26.3.2 | Abnormal Condition at the UTRAN..... | 74 |
+| 8.26.3.3 | Crossing of Reset Messages..... | 75 |
+| 8.27 | Error Indication..... | 75 |
+| 8.27.1 | General..... | 75 |
+| 8.27.2 | Successful Operation..... | 75 |
+| 8.27.3 | Abnormal Conditions..... | 76 |
+| 8.28 | CN Deactivate Trace..... | 76 |
+| 8.28.1 | General..... | 76 |
+| 8.28.2 | Successful Operation..... | 76 |
+| 8.28.2.1 | Successful Operation for GERAN Iu mode..... | 76 |
+| 8.28.3 | Abnormal Conditions..... | 76 |
+| 8.29 | Reset Resource..... | 76 |
+| 8.29.1 | General..... | 76 |
+| 8.29.1.1 | Reset Resource procedure initiated from the RNC..... | 76 |
+| 8.29.1.2 | Reset Resource procedure initiated from the CN..... | 76 |
+| 8.29.2 | Successful Operation..... | 77 |
+| 8.29.2.1 | Reset Resource procedure initiated from the RNC..... | 77 |
+| 8.29.2.2 | Reset Resource procedure initiated from the CN..... | 77 |
+| 8.30 | RAB Modification Request..... | 78 |
+| 8.30.1 | General..... | 78 |
+| 8.30.2 | Successful Operation..... | 78 |
+| 8.30.3 | Abnormal Conditions..... | 79 |
+| 8.31 | Location Related Data..... | 79 |
+| 8.31.1 | General..... | 79 |
+| 8.31.2 | Successful Operation..... | 79 |
+| 8.31.2.1 | Successful Operation for GERAN Iu mode..... | 79 |
+| 8.31.3 | Unsuccessful Operation..... | 80 |
+| 8.31.4 | Abnormal Conditions..... | 80 |
+| 8.31.4.1 | Abnormal Conditions for GERAN Iu mode..... | 80 |
+| 8.32 | Information Transfer..... | 80 |
+| 8.32.1 | General..... | 80 |
+| 8.32.2 | Successful Operation..... | 81 |
+| 8.32.3 | Unsuccessful Operation..... | 82 |
+| 8.32.4 | Abnormal Conditions..... | 82 |
+| 8.33 | UE Specific Information..... | 82 |
+| 8.33.1 | General..... | 82 |
+
+| | | |
+|------------|---------------------------------------------------------|-----|
+| 8.33.2 | Successful Operation..... | 82 |
+| 8.34 | Direct Information Transfer..... | 83 |
+| 8.34.1 | General..... | 83 |
+| 8.34.2 | Successful Operation..... | 83 |
+| 8.34.2.1 | Direct Information Transfer initiated from the RNC..... | 83 |
+| 8.34.2.1.1 | Successful Operation for GERAN Iu mode..... | 83 |
+| 8.34.2.2 | Direct Information Transfer initiated from the CN..... | 84 |
+| 8.34.3 | Abnormal Conditions..... | 84 |
+| 8.35 | Uplink Information Exchange..... | 84 |
+| 8.35.1 | General..... | 84 |
+| 8.35.2 | Successful Operation..... | 85 |
+| 8.35.3 | Unsuccessful Operation..... | 86 |
+| 8.35.4 | Abnormal Conditions..... | 86 |
+| 8.36 | MBMS Session Start..... | 86 |
+| 8.36.1 | General..... | 86 |
+| 8.36.2 | Successful Operation..... | 87 |
+| 8.36.3 | Unsuccessful Operation..... | 90 |
+| 8.36.4 | Abnormal Conditions..... | 90 |
+| 8.37 | MBMS Session Update..... | 91 |
+| 8.37.1 | General..... | 91 |
+| 8.37.2 | Successful Operation..... | 91 |
+| 8.37.3 | Unsuccessful Operation..... | 92 |
+| 8.37.4 | Abnormal Conditions..... | 92 |
+| 8.38 | MBMS Session Stop..... | 92 |
+| 8.38.1 | General..... | 92 |
+| 8.38.2 | Successful Operation..... | 93 |
+| 8.38.3 | Abnormal Conditions..... | 93 |
+| 8.39 | MBMS UE Linking..... | 93 |
+| 8.39.1 | General..... | 93 |
+| 8.39.2 | Successful Operation..... | 94 |
+| 8.39.3 | Unsuccessful Operation..... | 94 |
+| 8.39.4 | Abnormal Conditions..... | 94 |
+| 8.40 | MBMS Registration..... | 95 |
+| 8.40.1 | General..... | 95 |
+| 8.40.2 | Successful Operation..... | 95 |
+| 8.40.3 | Unsuccessful Operation..... | 96 |
+| 8.40.4 | Abnormal Conditions..... | 96 |
+| 8.41 | MBMS CN De-Registration..... | 96 |
+| 8.41.1 | General..... | 96 |
+| 8.41.2 | Successful Operation..... | 97 |
+| 8.41.3 | Unsuccessful Operation..... | 97 |
+| 8.41.4 | Abnormal Conditions..... | 97 |
+| 8.42 | MBMS RAB Establishment Indication..... | 98 |
+| 8.42.1 | General..... | 98 |
+| 8.42.2 | Successful Operation..... | 98 |
+| 8.42.3 | Abnormal Conditions..... | 98 |
+| 8.43 | MBMS RAB Release..... | 98 |
+| 8.43.1 | General..... | 98 |
+| 8.43.2 | Successful Operation..... | 99 |
+| 8.43.3 | Unsuccessful Operation..... | 99 |
+| 8.43.4 | Abnormal Conditions..... | 99 |
+| 8.44 | Enhanced Relocation Complete..... | 100 |
+| 8.44.1 | General..... | 100 |
+| 8.44.2 | Successful Operation..... | 100 |
+| 8.44.3 | Unsuccessful Operation..... | 102 |
+| 8.45 | Enhanced Relocation Complete Confirm..... | 102 |
+| 8.45.1 | General..... | 102 |
+| 8.45.2 | Successful Operation..... | 102 |
+| 8.46 | SRVCC Preparation..... | 102 |
+| 8.46.1 | General..... | 102 |
+| 8.46.2 | Successful Operation..... | 103 |
+
+| | | |
+|---------|-----------------------------------------------|-----|
+| 8.46.3 | Abnormal Conditions..... | 103 |
+| 8.47 | UE Radio Capability Match..... | 103 |
+| 8.47.1 | General..... | 103 |
+| 8.47.2 | Successful Operation..... | 103 |
+| 8.47.3 | Unsuccessful Operation..... | 103 |
+| 8.47.4 | Abnormal Conditions..... | 103 |
+| 9 | Elements for RANAP Communication..... | 104 |
+| 9.1 | Message Functional Definiton and Content..... | 104 |
+| 9.1.1 | General..... | 104 |
+| 9.1.2 | Message Contents..... | 105 |
+| 9.1.2.1 | Presence..... | 105 |
+| 9.1.2.2 | Criticality..... | 105 |
+| 9.1.2.3 | Range..... | 105 |
+| 9.1.2.4 | Assigned Criticality..... | 105 |
+| 9.1.3 | RAB ASSIGNMENT REQUEST..... | 105 |
+| 9.1.4 | RAB ASSIGNMENT RESPONSE..... | 107 |
+| 9.1.5 | RAB RELEASE REQUEST..... | 109 |
+| 9.1.6 | IU RELEASE REQUEST..... | 109 |
+| 9.1.7 | IU RELEASE COMMAND..... | 110 |
+| 9.1.8 | IU RELEASE COMPLETE..... | 110 |
+| 9.1.9 | RELOCATION REQUIRED..... | 111 |
+| 9.1.10 | RELOCATION REQUEST..... | 112 |
+| 9.1.11 | RELOCATION REQUEST ACKNOWLEDGE..... | 114 |
+| 9.1.12 | RELOCATION COMMAND..... | 116 |
+| 9.1.13 | RELOCATION DETECT..... | 116 |
+| 9.1.14 | RELOCATION COMPLETE..... | 117 |
+| 9.1.15 | RELOCATION PREPARATION FAILURE..... | 117 |
+| 9.1.16 | RELOCATION FAILURE..... | 117 |
+| 9.1.17 | RELOCATION CANCEL..... | 118 |
+| 9.1.18 | RELOCATION CANCEL ACKNOWLEDGE..... | 118 |
+| 9.1.19 | SRNS CONTEXT REQUEST..... | 118 |
+| 9.1.20 | SRNS CONTEXT RESPONSE..... | 118 |
+| 9.1.21 | SRNS DATA FORWARD COMMAND..... | 119 |
+| 9.1.22 | FORWARD SRNS CONTEXT..... | 119 |
+| 9.1.23 | PAGING..... | 120 |
+| 9.1.24 | COMMON ID..... | 120 |
+| 9.1.25 | CN INVOKE TRACE..... | 121 |
+| 9.1.26 | SECURITY MODE COMMAND..... | 122 |
+| 9.1.27 | SECURITY MODE COMPLETE..... | 122 |
+| 9.1.28 | SECURITY MODE REJECT..... | 123 |
+| 9.1.29 | LOCATION REPORTING CONTROL..... | 123 |
+| 9.1.30 | LOCATION REPORT..... | 123 |
+| 9.1.31 | DATA VOLUME REPORT REQUEST..... | 124 |
+| 9.1.32 | DATA VOLUME REPORT..... | 124 |
+| 9.1.33 | INITIAL UE MESSAGE..... | 125 |
+| 9.1.34 | DIRECT TRANSFER..... | 126 |
+| 9.1.35 | CN INFORMATION BROADCAST REQUEST..... | 127 |
+| 9.1.36 | CN INFORMATION BROADCAST CONFIRM..... | 127 |
+| 9.1.37 | CN INFORMATION BROADCAST REJECT..... | 127 |
+| 9.1.38 | OVERLOAD..... | 127 |
+| 9.1.39 | RESET..... | 128 |
+| 9.1.40 | RESET ACKNOWLEDGE..... | 129 |
+| 9.1.41 | ERROR INDICATION..... | 129 |
+| 9.1.42 | CN DEACTIVATE TRACE..... | 130 |
+| 9.1.43 | RANAP RELOCATION INFORMATION..... | 130 |
+| 9.1.44 | RESET RESOURCE..... | 131 |
+| 9.1.45 | RESET RESOURCE ACKNOWLEDGE..... | 133 |
+| 9.1.46 | RAB MODIFY REQUEST..... | 133 |
+| 9.1.47 | LOCATION RELATED DATA REQUEST..... | 134 |
+| 9.1.48 | LOCATION RELATED DATA RESPONSE..... | 134 |
+| 9.1.49 | LOCATION RELATED DATA FAILURE..... | 135 |
+
+| | | |
+|----------|-----------------------------------------------------|-----|
+| 9.1.50 | INFORMATION TRANSFER INDICATION..... | 135 |
+| 9.1.51 | INFORMATION TRANSFER CONFIRMATION..... | 135 |
+| 9.1.52 | INFORMATION TRANSFER FAILURE..... | 136 |
+| 9.1.53 | UE SPECIFIC INFORMATION INDICATION..... | 136 |
+| 9.1.54 | DIRECT INFORMATION TRANSFER..... | 137 |
+| 9.1.55 | UPLINK INFORMATION EXCHANGE REQUEST..... | 137 |
+| 9.1.56 | UPLINK INFORMATION EXCHANGE RESPONSE..... | 138 |
+| 9.1.57 | UPLINK INFORMATION EXCHANGE FAILURE..... | 138 |
+| 9.1.58 | MBMS SESSION START..... | 139 |
+| 9.1.59 | MBMS SESSION START RESPONSE..... | 140 |
+| 9.1.60 | MBMS SESSION START FAILURE..... | 141 |
+| 9.1.61 | MBMS SESSION UPDATE..... | 141 |
+| 9.1.62 | MBMS SESSION UPDATE RESPONSE..... | 141 |
+| 9.1.63 | MBMS SESSION UPDATE FAILURE..... | 142 |
+| 9.1.64 | MBMS SESSION STOP..... | 142 |
+| 9.1.65 | MBMS SESSION STOP RESPONSE..... | 142 |
+| 9.1.66 | MBMS UE LINKING REQUEST..... | 143 |
+| 9.1.67 | MBMS UE LINKING RESPONSE..... | 143 |
+| 9.1.68 | MBMS REGISTRATION REQUEST..... | 144 |
+| 9.1.69 | MBMS REGISTRATION RESPONSE..... | 144 |
+| 9.1.70 | MBMS REGISTRATION FAILURE..... | 145 |
+| 9.1.71 | MBMS CN DE-REGISTRATION REQUEST..... | 145 |
+| 9.1.72 | MBMS CN DE-REGISTRATION RESPONSE..... | 145 |
+| 9.1.73 | MBMS RAB ESTABLISHMENT INDICATION..... | 146 |
+| 9.1.74 | MBMS RAB RELEASE REQUEST..... | 146 |
+| 9.1.75 | MBMS RAB RELEASE..... | 147 |
+| 9.1.76 | MBMS RAB RELEASE FAILURE..... | 147 |
+| 9.1.77 | ENHANCED RELOCATION COMPLETE REQUEST..... | 147 |
+| 9.1.78 | ENHANCED RELOCATION COMPLETE RESPONSE..... | 149 |
+| 9.1.79 | ENHANCED RELOCATION COMPLETE FAILURE..... | 150 |
+| 9.1.80 | ENHANCED RELOCATION COMPLETE CONFIRM..... | 151 |
+| 9.1.81 | RANAP ENHANCED RELOCATION INFORMATION REQUEST..... | 151 |
+| 9.1.82 | RANAP ENHANCED RELOCATION INFORMATION RESPONSE..... | 153 |
+| 9.1.83 | SRVCC CS KEYS REQUEST..... | 154 |
+| 9.1.84 | SRVCC CS KEYS RESPONSE..... | 154 |
+| 9.1.85 | UE RADIO CAPABILITY MATCH REQUEST..... | 155 |
+| 9.1.86 | UE RADIO CAPABILITY MATCH RESPONSE..... | 155 |
+| 9.2 | Information Element Definitions..... | 155 |
+| 9.2.0 | General..... | 155 |
+| 9.2.1 | Radio Network Layer Related IEs..... | 155 |
+| 9.2.1.1 | Message Type..... | 155 |
+| 9.2.1.2 | RAB ID..... | 157 |
+| 9.2.1.3 | RAB Parameters..... | 157 |
+| 9.2.1.4 | Cause..... | 169 |
+| 9.2.1.5 | CN Domain Indicator..... | 177 |
+| 9.2.1.6 | Trace Type..... | 177 |
+| 9.2.1.7 | Trigger ID..... | 177 |
+| 9.2.1.8 | Trace Reference..... | 177 |
+| 9.2.1.9 | UE Identity..... | 178 |
+| 9.2.1.10 | OMC ID..... | 178 |
+| 9.2.1.11 | Integrity Protection Information..... | 179 |
+| 9.2.1.12 | Encryption Information..... | 179 |
+| 9.2.1.13 | Chosen Integrity Protection Algorithm..... | 179 |
+| 9.2.1.14 | Chosen Encryption Algorithm..... | 179 |
+| 9.2.1.15 | Categorisation Parameters..... | 180 |
+| 9.2.1.16 | Request Type..... | 180 |
+| 9.2.1.17 | Data Volume Reporting Indication..... | 180 |
+| 9.2.1.18 | User Plane Mode..... | 180 |
+| 9.2.1.19 | UP Mode Versions..... | 181 |
+| 9.2.1.20 | Chosen UP Version..... | 181 |
+| 9.2.1.21 | Paging Area ID..... | 181 |
+
+| | | |
+|-----------|-----------------------------------------------------|-----|
+| 9.2.1.22 | Non Searching Indication..... | 181 |
+| 9.2.1.23 | Relocation Type..... | 182 |
+| 9.2.1.24 | Source ID..... | 182 |
+| 9.2.1.25 | Target ID..... | 182 |
+| 9.2.1.26 | MS Classmark 2..... | 185 |
+| 9.2.1.27 | MS Classmark 3..... | 185 |
+| 9.2.1.28 | Source RNC to Target RNC Transparent Container..... | 185 |
+| 9.2.1.29 | Old BSS to New BSS Information..... | 189 |
+| 9.2.1.30 | Target RNC to Source RNC Transparent Container..... | 189 |
+| 9.2.1.30a | Source to Target Transparent Container..... | 189 |
+| 9.2.1.30b | Target to Source Transparent Container..... | 189 |
+| 9.2.1.30c | TAI..... | 190 |
+| 9.2.1.31 | L3 Information..... | 190 |
+| 9.2.1.32 | Number of Steps..... | 190 |
+| 9.2.1.33 | DL N-PDU Sequence Number..... | 191 |
+| 9.2.1.34 | UL N-PDU Sequence Number..... | 191 |
+| 9.2.1.35 | Criticality Diagnostics..... | 191 |
+| 9.2.1.36 | Key Status..... | 193 |
+| 9.2.1.37 | DRX Cycle Length Coefficient..... | 193 |
+| 9.2.1.38 | Iu Signalling Connection Identifier..... | 193 |
+| 9.2.1.39 | Global RNC-ID..... | 193 |
+| 9.2.1.39a | Extended RNC-ID..... | 194 |
+| 9.2.1.40 | PDP Type Information..... | 194 |
+| 9.2.1.40a | PDP Type Information extension..... | 195 |
+| 9.2.1.41 | Service Handover..... | 195 |
+| 9.2.1.42 | Message Structure..... | 195 |
+| 9.2.1.43 | Alternative RAB Parameter Values..... | 196 |
+| 9.2.1.44 | Assigned RAB Parameter Values..... | 199 |
+| 9.2.1.45 | Requested RAB Parameter Values..... | 201 |
+| 9.2.1.46 | Global CN-ID..... | 203 |
+| 9.2.1.46a | Vertical Accuracy Code..... | 203 |
+| 9.2.1.46b | Response Time..... | 203 |
+| 9.2.1.46c | Positioning Priority..... | 204 |
+| 9.2.1.46d | Client Type..... | 204 |
+| 9.2.1.47 | New BSS to Old BSS Information..... | 204 |
+| 9.2.1.48 | Inter-System Information Transparent Container..... | 204 |
+| 9.2.1.49 | Cell Load Information..... | 205 |
+| 9.2.1.50 | Cell Capacity Class Value..... | 205 |
+| 9.2.1.51 | Load Value..... | 205 |
+| 9.2.1.52 | RT Load Value..... | 205 |
+| 9.2.1.53 | NRT Load Information Value..... | 206 |
+| 9.2.1.54 | Source RNC PDCP context info..... | 206 |
+| 9.2.1.55 | Information Transfer ID..... | 206 |
+| 9.2.1.56 | Provided Data..... | 206 |
+| 9.2.1.57 | GERAN Classmark..... | 207 |
+| 9.2.1.58 | GERAN BSC Container..... | 207 |
+| 9.2.1.59 | UESBI-Iu..... | 207 |
+| 9.2.1.60 | Cell Load Information Group..... | 208 |
+| 9.2.1.61 | Source Cell Identifier..... | 208 |
+| 9.2.1.62 | Inter-system Information Transfer Type..... | 209 |
+| 9.2.1.63 | Information Transfer Type..... | 209 |
+| 9.2.1.64 | RNC Trace Session Information..... | 210 |
+| 9.2.1.65 | Equipments To Be Traced..... | 210 |
+| 9.2.1.66 | Trace Recording Session Information..... | 212 |
+| 9.2.1.67 | Trace Recording Session Reference..... | 212 |
+| 9.2.1.68 | Trace Propagation Parameters..... | 212 |
+| 9.2.1.69 | Trace Depth..... | 212 |
+| 9.2.1.70 | List Of Interfaces To Trace..... | 213 |
+| 9.2.1.71 | Information Exchange ID..... | 213 |
+| 9.2.1.72 | Information Exchange Type..... | 213 |
+| 9.2.1.73 | Information Request Type..... | 213 |
+
+| | | |
+|-----------|-------------------------------------------------------|-----|
+| 9.2.1.74 | Information Requested..... | 213 |
+| 9.2.1.75 | PTP RAB ID..... | 214 |
+| 9.2.1.76 | Frequency Layer Convergence Flag..... | 214 |
+| 9.2.1.77 | Session Update ID..... | 214 |
+| 9.2.1.78 | MBMS IP Multicast Address and APN Request..... | 214 |
+| 9.2.1.79 | Source BSS to Target BSS Transparent Container..... | 215 |
+| 9.2.1.80 | Target BSS to Source BSS Transparent Container..... | 215 |
+| 9.2.1.81 | Include Velocity..... | 215 |
+| 9.2.1.82 | Periodic Location Info..... | 215 |
+| 9.2.1.83 | Last Visited UTRAN Cell Information..... | 216 |
+| 9.2.1.84 | MBMS HC Indicator..... | 216 |
+| 9.2.1.85 | CSG Id..... | 216 |
+| 9.2.1.86 | Subscriber Profile ID for RAT/Frequency priority..... | 217 |
+| 9.2.1.87 | SRVCC operation possible..... | 217 |
+| 9.2.1.88 | SRVCC HO Indication..... | 217 |
+| 9.2.1.89 | SRVCC Information..... | 217 |
+| 9.2.1.90 | E-UTRAN Service Handover..... | 217 |
+| 9.2.1.91 | UE Aggregate Maximum Bit Rate..... | 218 |
+| 9.2.1.92 | CSG Membership Status..... | 218 |
+| 9.2.1.93 | Cell Access Mode..... | 218 |
+| 9.2.1.94 | Offload RAB Parameters..... | 219 |
+| 9.2.1.95 | MSISDN..... | 219 |
+| 9.2.1.96 | IRAT Measurement Configuration..... | 219 |
+| 9.2.1.97 | MDT Configuration..... | 220 |
+| 9.2.1.98 | M1 Report..... | 222 |
+| 9.2.1.99 | M2 Report..... | 223 |
+| 9.2.1.100 | MDT Report parameters..... | 223 |
+| 9.2.1.101 | RNSAP Relocation Parameters..... | 223 |
+| 9.2.1.102 | RAB Parameters List..... | 224 |
+| 9.2.1.103 | RAB Data Volume Report..... | 224 |
+| 9.2.1.104 | UP Information..... | 224 |
+| 9.2.1.105 | Location Reporting Transfer Information..... | 225 |
+| 9.2.1.106 | Trace Information..... | 226 |
+| 9.2.1.107 | Frame Sequence Number..... | 227 |
+| 9.2.1.108 | PDU Type 14 Frame Sequence Number..... | 227 |
+| 9.2.1.109 | Priority Class Indicator..... | 227 |
+| 9.2.1.110 | Management Based MDT Allowed..... | 227 |
+| 9.2.1.111 | End Of CSFB..... | 227 |
+| 9.2.1.112 | Out Of UTRAN..... | 227 |
+| 9.2.1.113 | Voice Support Match Indicator..... | 228 |
+| 9.2.1.114 | rSRVCC HO Indication..... | 228 |
+| 9.2.1.115 | rSRVCC Information..... | 228 |
+| 9.2.1.116 | MDT PLMN List..... | 228 |
+| 9.2.1.117 | M4 Report..... | 228 |
+| 9.2.1.118 | M5 Report..... | 229 |
+| 9.2.1.119 | M6 Report..... | 229 |
+| 9.2.1.120 | M7 Report..... | 230 |
+| 9.2.1.121 | rSRVCC operation possible..... | 230 |
+| 9.2.1.122 | UTRAN Cell Identifier..... | 230 |
+| 9.2.2 | Transport Network Layer Related IEs..... | 230 |
+| 9.2.2.1 | Transport Layer Address..... | 230 |
+| 9.2.2.2 | Iu Transport Association..... | 231 |
+| 9.2.2.3 | DL GTP-PDU Sequence Number..... | 231 |
+| 9.2.2.4 | UL GTP-PDU Sequence Number..... | 231 |
+| 9.2.2.5 | Correlation ID..... | 231 |
+| 9.2.2.6 | Tunnel Information..... | 232 |
+| 9.2.3 | NAS Related IEs..... | 232 |
+| 9.2.3.1 | Permanent NAS UE Identity..... | 232 |
+| 9.2.3.2 | Temporary UE ID..... | 232 |
+| 9.2.3.3 | Paging Cause..... | 233 |
+| 9.2.3.4 | NAS Broadcast Information..... | 233 |
+
+| | | |
+|-----------|-------------------------------------------------------------------|-----|
+| 9.2.3.5 | NAS PDU..... | 233 |
+| 9.2.3.6 | LAI..... | 233 |
+| 9.2.3.7 | RAC..... | 234 |
+| 9.2.3.8 | SAPI..... | 234 |
+| 9.2.3.9 | SAI..... | 234 |
+| 9.2.3.10 | Area Identity..... | 235 |
+| 9.2.3.11 | Geographical Area..... | 235 |
+| 9.2.3.12 | Unsuccessfully Transmitted Data Volume..... | 238 |
+| 9.2.3.13 | Data Volume Reference..... | 239 |
+| 9.2.3.14 | Information Identity..... | 239 |
+| 9.2.3.15 | Information Priority..... | 239 |
+| 9.2.3.16 | Information Control..... | 239 |
+| 9.2.3.17 | CN Broadcast Area..... | 239 |
+| 9.2.3.18 | NAS Synchronisation Indicator..... | 239 |
+| 9.2.3.19 | Location Related Data Request Type..... | 239 |
+| 9.2.3.20 | Broadcast Assistance Data Deciphering keys..... | 240 |
+| 9.2.3.21 | Requested GPS Assistance Data..... | 241 |
+| 9.2.3.22 | Last Known Service Area..... | 241 |
+| 9.2.3.23 | Shared Network Information..... | 241 |
+| 9.2.3.24 | SNA Access Information..... | 242 |
+| 9.2.3.25 | SNAC..... | 242 |
+| 9.2.3.26 | Location Related Data Request Type Specific To GERAN Iu Mode..... | 242 |
+| 9.2.3.27 | Position Data..... | 243 |
+| 9.2.3.28 | Position Data Specific To GERAN Iu Mode..... | 245 |
+| 9.2.3.29 | Accuracy Fulfilment Indicator..... | 246 |
+| 9.2.3.30 | RIM Transfer..... | 246 |
+| 9.2.3.31 | RIM Information..... | 246 |
+| 9.2.3.32 | RIM Routing Address..... | 246 |
+| 9.2.3.33 | Selected PLMN Identity..... | 248 |
+| 9.2.3.34 | NAS Sequence Number..... | 248 |
+| 9.2.3.35 | Redirection Completed..... | 248 |
+| 9.2.3.36 | Redirection Indication..... | 249 |
+| 9.2.3.37 | TMGI..... | 249 |
+| 9.2.3.38 | MBMS Session Identity..... | 249 |
+| 9.2.3.39 | MBMS Bearer Service Type..... | 250 |
+| 9.2.3.39a | MBMS Counting Information..... | 250 |
+| 9.2.3.40 | MBMS Session Duration..... | 250 |
+| 9.2.3.41 | MBMS Service Area..... | 250 |
+| 9.2.3.42 | RA List of Idle Mode UEs..... | 250 |
+| 9.2.3.43 | Delta RA List of Idle Mode UEs..... | 251 |
+| 9.2.3.44 | MBMS CN De-Registration..... | 252 |
+| 9.2.3.45 | MBMS Registration Request Type..... | 253 |
+| 9.2.3.46 | Requested MBMS IP Multicast Address and APN..... | 253 |
+| 9.2.3.47 | Requested Multicast Service List..... | 253 |
+| 9.2.3.48 | MBMS Session Repetition Number..... | 254 |
+| 9.2.3.49 | Time to MBMS Data Transfer..... | 254 |
+| 9.2.3.50 | Redirect Attempt Flag..... | 254 |
+| 9.2.3.51 | Velocity Estimate..... | 254 |
+| 9.2.3.52 | RAT Type..... | 257 |
+| 9.2.3.53 | Requested GANSS Assistance Data..... | 257 |
+| 9.2.3.54 | Higher bitrates than 16 Mbps flag..... | 257 |
+| 9.3 | Message and Information Element Abstract Syntax (with ASN.1)..... | 259 |
+| 9.3.0 | General..... | 259 |
+| 9.3.1 | Usage of private message mechanism for non-standard use..... | 259 |
+| 9.3.2 | Elementary Procedure Definitions..... | 260 |
+| 9.3.3 | PDU Definitions..... | 272 |
+| 9.3.4 | Information Element Definitions..... | 344 |
+| 9.3.5 | Common Definitions..... | 397 |
+| 9.3.6 | Constant Definitions..... | 398 |
+| 9.3.7 | Container Definitions..... | 406 |
+| 9.4 | Message Transfer Syntax..... | 411 |
+
+| | | |
+|-------------------------------|---------------------------------------------------------------------------------------------------|------------|
+| 9.5 | Timers..... | 411 |
+| 10 | Handling of Unknown, Unforeseen and Erroneous Protocol Data..... | 412 |
+| 10.1 | General..... | 412 |
+| 10.2 | Transfer Syntax Error..... | 412 |
+| 10.3 | Abstract Syntax Error..... | 413 |
+| 10.3.1 | General..... | 413 |
+| 10.3.2 | Criticality Information..... | 413 |
+| 10.3.3 | Presence Information..... | 414 |
+| 10.3.4 | Not comprehended IE/IE group..... | 414 |
+| 10.3.4.1 | Procedure Code..... | 414 |
+| 10.3.4.1A | Type of Message..... | 414 |
+| 10.3.4.2 | IEs other than the Procedure Code and Type of Message..... | 414 |
+| 10.3.5 | Missing IE or IE group..... | 416 |
+| 10.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present..... | 417 |
+| 10.4 | Logical Error..... | 417 |
+| 10.5 | Exceptions..... | 418 |
+| 11 | Special Procedures for RNC to RNC Communication..... | 418 |
+| 11.1 | General..... | 418 |
+| 11.2 | RANAP Relocation Information..... | 418 |
+| 11.2.1 | General..... | 418 |
+| 11.2.2 | Operation..... | 418 |
+| 11.3 | RANAP Enhanced Relocation Information..... | 419 |
+| 11.3.1 | General..... | 419 |
+| 11.3.2 | Operation..... | 419 |
+| Annex A (informative): | RANAP guidelines..... | 424 |
+| A.1 | Rules for building RANAP messages..... | 424 |
+| A.1.1 | Rules for RANAP messages that shall contain the CN Domain Indicator IE..... | 424 |
+| A.2 | Guidelines for Usage of the Criticality Diagnostics IE..... | 424 |
+| A.2.1 | EXAMPLE MESSAGE Layout..... | 424 |
+| A.2.2 | Example on a Received EXAMPLE MESSAGE..... | 425 |
+| A.2.3 | Content of Criticality Diagnostics..... | 426 |
+| A.2.3.1 | Example 1..... | 426 |
+| A.2.3.2 | Example 2..... | 427 |
+| A.2.3.3 | Example 3..... | 428 |
+| A.2.3.4 | Example 4..... | 429 |
+| A.2.3.5 | Example 5..... | 430 |
+| A.2.4 | ASN.1 of EXAMPLE MESSAGE..... | 431 |
+| Annex B (informative): | RANAP Transparent containers content..... | 434 |
+| Annex C (informative): | Processing of Transparent Containers at the SGSN..... | 435 |
+| Annex D (informative): | Change History..... | 436 |
+
+---
+
+## Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+---
+
+# 1 Scope
+
+The present document specifies the radio network layer signalling protocol called Radio Access Network Application Part (RANAP) for the Iu interface. RANAP supports the functions of Iu interface by signalling procedures defined in this document. RANAP is developed in accordance to the general principles stated in TR 23.930 [1], TS 25.410 [2] and TS 25.401 [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 23.930 (version.4.0.0, 2001-04): "Iu Principles".
+- [2] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles".
+- [3] 3GPP TS 25.401: "UTRAN Overall Description".
+- [4] 3GPP TR 25.931: "UTRAN Functions, Examples on Signalling Procedures".
+- [5] 3GPP TS 25.412: "UTRAN Iu interface signalling transport".
+- [6] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols".
+- [7] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".
+- [8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".
+- [9] 3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling".
+- [10] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [11] 3GPP TS 48.008: "Mobile Switching Centre – Base Station System (MSC - BSS) interface; Layer 3 specification".
+- [12] Void
+- [13] ITU-T Recommendation X.691 (07/2002): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".
+- [14] ITU-T Recommendation X.680 (07/2002): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+- [15] ITU-T Recommendation X.681 (07/2002): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification".
+- [16] 3GPP TS 23.110: "UMTS Access Stratum, Services and Functions".
+- [17] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) specification".
+- [18] 3GPP TR 25.921 (version.7.0.0): "Guidelines and principles for protocol description and error handling".
+- [19] 3GPP TS 23.003: "Numbering, addressing and identification".
+
+- [20] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
+- [21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [22] 3GPP TS 24.080: "Mobile radio Layer 3 supplementary services specification; Formats and coding".
+- [23] 3GPP TS 29.108: "Application of the Radio Access Network Application Part (RANAP) on the E-interface".
+- [24] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [25] GSM TS 12.20: "Base Station System (BSS) management information".
+- [26] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
+- [27] 3GPP TS 43.051: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Overall description - Stage 2".
+- [28] Void.
+- [29] 3GPP TS 43.059: "Functional stage 2 description of Location Services (LCS) in GERAN".
+- [30] 3GPP TS 22.071: "Location Services (LCS); Service description - Stage 1".
+- [31] 3GPP TR 25.994 (version.5.0.0): "Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults".
+- [32] 3GPP TR 25.995 (version.5.0.0): "Measures employed by the UMTS Radio Access Network (UTRAN) to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification".
+- [33] 3GPP TS 23.195 (version.5.4.0): "Provision of UE Specific Behaviour Information to Network Entities".
+- [34] 3GPP TS 49.031: "Location Services (LCS) – Base Station System Application Part LCS Extension – (BSSAP-LE)".
+- [35] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [36] 3GPP TS 48.018: "General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP)".
+- [37] 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements".
+- [38] 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and Configuration Management".
+- [39] 3GPP TS 23.251: "Network sharing - Architecture and functional description".
+- [40] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1".
+- [41] 3GPP TS 23.246: "Multimedia Broadcast Multicast Service; Architecture and Functional Description".
+- [42] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
+- [43] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2".
+- [44] 3GPP TS 29.061 "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
+- [45] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
+
+- [46] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
+- [47] 3GPP TS 43.055: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Dual Transfer Mode (DTM) - Stage 2".
+- [48] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
+- [49] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
+- [50] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception(FDD)".
+- [51] 3GPP TS 25.446: "MBMS Synchronisation Protocol(SYNC)".
+- [52] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; stage 2".
+- [53] 3GPP TS 23.007: "Restoration procedures"
+- [54] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2"
+- [55] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB) - Stage 2"
+- [56] 3GPP TS 22.220: "Service requirements for Home NodeBs and Home eNodeBs".
+- [57] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
+- [58] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [59] 3GPP TS 29.281: "General Packet Radio Service (GPRS); Tunnelling Protocol User Plane (GTPv1-U)".
+- [60] 3GPP TS 33.102: "3G Security; Security architecture".
+- [61] 3GPP TS 32.240: "Charging management; Charging architecture and principles".
+- [62] 3GPP TS 52.008: "Telecommunication management; GSM subscriber and equipment trace".
+- [63] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
+- [64] 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".
+- [65] 3GPP TS 23.139: "3GPP system – fixed broadband access network interworking".
+- [66] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
+
+---
+
+## 3 Definitions, symbols and abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions below apply. Terms and definitions not defined below can be found in TR 21.905 [35].
+
+**Cell Load-Based Inter-System Handover:** This mechanism, which is contained within a UTRAN RNC, consists of three primary functions:
+
+1. The RNC has the capability to generate and send Cell Load Information towards the target/source system.
+
+2. The RNC has the capability to receive Cell Load Information from the target/source system, and is able to interpret this information.
+3. The ability of the RNC to make a handover decision by comparing the Cell Load Information that it has received from the target system with the Cell Load Information it has about its own cells.
+
+**Ciphering Alternative:** defines both the Ciphering Status (started/not started) together with the Ciphering Algorithm considered altogether.
+
+**Core Network operator:** as defined in TS 23.251 [39].
+
+**Corresponding RNC-ID:** RNC-ID corresponding to an eNB ID, which enables a source RNC to address a target eNB for handover purposes via CN elements that cannot interpret an eNB ID (see TS 23.401 [48]).
+
+**CSG Cell:** a UTRAN cell broadcasting a CSG Indicator and a CSG identity. This cell operates in Closed Access Mode as defined in TS 22.220 [56].
+
+**Default CN node:** An RNC with an inactive or not implemented NAS Node Selection Function TS 23.236 [26] has one single permanent default CN node per CN domain. It always initiates the Initial UE Message procedure towards its default CN node. If the NAS Node Selection Function is active, then no Default CN node exists.
+
+**Directed retry:** Directed retry is the process of assigning a User Equipment to a radio resource that does not belong to the serving RNC e.g. in situations of congestion. It is triggered by the RAB Assignment procedure and employs relocation procedures.
+
+**Elementary Procedure:** RANAP protocol consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the RNS and the CN. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. Examples on using several RANAP EPs together with each other and EPs from other interfaces can be found in reference TR 25.931 [4].
+
+An EP consists of an initiating message and possibly a response message. Three kinds of EPs are used:
+
+- **Class 1:** Elementary Procedures with response (success and/or failure).
+- **Class 2:** Elementary Procedures without response.
+- **Class 3:** Elementary Procedures with possibility of multiple responses.
+
+For Class 1 EPs, the types of responses can be as follows:
+
+Successful:
+
+- A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.
+
+Unsuccessful:
+
+- A signalling message explicitly indicates that the EP failed.
+- On time supervision expiry (i.e. absence of expected response).
+
+Successful and Unsuccessful:
+
+- One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome.
+
+Class 2 EPs are considered always successful.
+
+Class 3 EPs have one or several response messages reporting both successful, unsuccessful outcome of the requests and temporary status information about the requests. This type of EP only terminates through response(s) or EP timer expiry.
+
+**Enhanced relocation:** denotes a method where the relocation of the SRNS functionality is prepared via RNSAP means. The CN is not informed until the preparation and execution of the relocation has taken place.
+
+**Gateway Core Network:** as defined in TS 23.251 [39].
+
+**GERAN BSC in Iu mode:** In the context of this specification no distinction between an UTRAN RNC and a GERAN BSC in Iu mode is made. The GERAN BSC in Iu mode will behave as a RNC unless explicitly stated (see TS 43.051 [27]).
+
+**Hybrid Cell:** a UTRAN cell broadcasting a CSG Identity and operating in Hybrid Access Mode as defined in TS 22.220 [56].
+
+**Integrity Protection Alternative:** defines both the Integrity Protection Status (started/not started) together with the Integrity Protection Algorithm considered altogether.
+
+**Management Based Activation:** as defined in TS 32.421 [37].
+
+**MBMS Bearer Service:** as defined in TS 23.246 [41].
+
+**MBMS Iu signalling connection:** as defined in TS 25.346 [42].
+
+**MBMS RAB:** as defined in TS 25.346 [42].
+
+**MBMS Service Area:** as defined in TS 23.246 [41].
+
+**MBMS Service Context:** as defined in TS 25.346 [42].
+
+**MBMS Session:** as defined in TS 25.346 [42].
+
+**MBMS session start:** as defined in TS 25.346 [42].
+
+**MBMS session stop:** as defined in TS 25.346 [42].
+
+**Multicast Service:** as defined in TS 22.146 [40].
+
+**Multi-Operator Core Network:** as defined in TS 23.251 [39].
+
+**Network sharing non-supporting UE:** as defined in TS 23.251 [39].
+
+**Network sharing supporting UE:** as defined in TS 23.251 [39].
+
+**Packet System Information:** as defined in TS 44.060 [46].
+
+**PUESBINE feature:** as defined in TS 23.195 [33].
+
+**Relocation of SRNS:** relocation of SRNS is a UMTS functionality used to relocate the serving RNS role from one RNS to another RNS. This UMTS functionality is realised by several elementary procedures executed in several interfaces and by several protocols and it may involve a change in the radio resources used between UTRAN and UE
+
+It is also possible to relocate the serving RNS role from:
+
+- one RNS within UMTS to another relocation target external to UMTS;
+- functionality equivalent to the serving RNS role from another relocation source external to UMTS to another RNS.
+
+**RAN Information Management:** as defined in TS 48.018 [36].
+
+**RNSAP Relocation:** see definition in TS 25.467 [55].
+
+**Trace Recording Session:** as defined in TS 32.421 [37].
+
+**Trace Recording Session Reference:** as defined in TS 32.421 [37].
+
+**Trace Reference:** as defined in TS 32.421 [37].
+
+**Trace Session:** as defined in TS 32.421 [37].
+
+**Serving RNC:** SRNC is the RNC belonging to SRNS
+
+**Serving RNS:** role an RNS can take with respect to a specific connection between an UE and UTRAN. There is one serving RNS for each UE that has a connection to UTRAN. The serving RNS is in charge of the radio connection between a UE and the UTRAN. The serving RNS terminates the Iu for this UE
+
+**Signalling Based Activation:** as defined in TS 32.421 [37].
+
+**Source RNC:** source RNC is the RNC belonging to source RNS
+
+**Source RNS:** role, with respect to a specific connection between UTRAN and CN, that RNS takes when it decides to initiate a relocation of SRNS
+
+**System Information in GERAN:** as defined in TS 44.018 [45].
+
+**Target RNC:** target RNC is the RNC belonging to target RNS
+
+**Target RNS:** role an RNS gets with respect to a specific connection between UTRAN and CN when it is being a subject of a relocation of SRNS which is being made towards that RNS
+
+**UE Specific Behaviour Information – Iu:** as defined in TS 23.195 [33].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+Applicable abbreviations can be found in TR 21.905 [35]. For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|---------|-----------------------------------------------------|
+| AAL2 | ATM Adaptation Layer type 2 |
+| ALCAP | Access Link Control Application Part |
+| APN | Access Point Name |
+| AS | Access Stratum |
+| ASN.1 | Abstract Syntax Notation One |
+| ATM | Asynchronous Transfer Mode |
+| BBF | Broadband Forum |
+| BSC | Base Station Controller |
+| CC | Call Control |
+| CN | Core Network |
+| CRNC | Controlling RNC |
+| CS | Circuit Switched |
+| CSG | Closed Subscriber Group |
+| DCH | Dedicated Channel |
+| DL | Downlink |
+| DRNC | Drift RNC |
+| DRNS | Drift RNS |
+| DSCH | Downlink Shared Channel |
+| eNB | E-UTRA NodeB |
+| EP | Elementary Procedure |
+| E-UTRA | Evolved UTRA |
+| E-UTRAN | Evolved UTRAN |
+| GANSS | Galileo and Additional Navigation Satellite Systems |
+| GERAN | GSM/EDGE Radio Access Network |
+| GPRS | General Packet Radio System |
+| GSM | Global System for Mobile communications |
+| GTP | GPRS Tunnelling Protocol |
+| GWCN | GateWay Core Network |
+| HNB | Home Node B |
+| IE | Information Element |
+| IMEI | International Mobile Equipment Identity |
+| IMSI | International Mobile Subscriber Identity |
+| IPv4 | Internet Protocol (version 4) |
+| IPv6 | Internet Protocol (version 6) |
+
+| | |
+|-----------|--------------------------------------------------------------------|
+| IRAT | Inter-RAT |
+| L-GW | Local GateWay |
+| LIPA | Local IP Access |
+| MBMS | Multimedia Broadcast Multicast Service |
+| MDT | Minimization of Drive Tests |
+| MM | Mobility Management |
+| MOCN | Multi Operator Core Network |
+| MSC | Mobile services Switching Center |
+| MSISDN | MS International PSTN/ISDN Number |
+| NACC | Network Assisted Cell Change |
+| NAS | Non Access Stratum |
+| NNSF | NAS Node Selection Function |
+| NRT | Non-Real Time |
+| N-PDU | Network – Protocol Data Unit |
+| OSP:IHOSS | Octet Stream Protocol: Internet-Hosted Octet Stream Service |
+| P-TMSI | Packet TMSI |
+| PDCP | Packet Data Convergence Protocol |
+| PDP | Packet Data Protocol |
+| PDU | Protocol Data Unit |
+| PLMN | Public Land Mobile Network |
+| PPP | Point-to-Point Protocol |
+| PS | Packet Switched |
+| PSI | Packet System Information |
+| PTP | Point To Point |
+| PUESBINE | Provision of UE Specific Behaviour Information to Network Entities |
+| QoS | Quality of Service |
+| RAB | Radio Access Bearer |
+| RANAP | Radio Access Network Application Part |
+| RAT | Radio Access Technology |
+| RIM | RAN Information Management |
+| RNC | Radio Network Controller |
+| RNS | Radio Network Subsystem |
+| RRC | Radio Resource Control |
+| rSRVCC | reverse Single Radio Voice Call Continuity |
+| RT | Real Time |
+| SAI | Service Area Identifier |
+| SAP | Service Access Point |
+| SDU | Service Data Unit |
+| SGSN | Serving GPRS Support Node |
+| SI | System Information in GERAN |
+| SIPTO | Selected IP Traffic Offload |
+| SNA | Shared Network Area |
+| SNAC | Shared Network Area Code |
+| SRNC | Serving RNC |
+| SRNS | Serving RNS |
+| SRVCC | Single Radio Voice Call Continuity |
+| TEID | Tunnel Endpoint Identifier |
+| TMGI | Temporary Mobile Group Identity |
+| TMSI | Temporary Mobile Subscriber Identity |
+| UE | User Equipment |
+| UEA | UMTS Encryption Algorithm |
+| UESBI-Iu | UE Specific Behaviour Information - Iu |
+| UIA | UMTS Integrity Algorithm |
+| UL | Uplink |
+| UMTS | Universal Mobile Telecommunications System |
+| USCH | Uplink Shared Channel |
+| UTRA | UMTS Terrestrial Radio Access |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+## 4 General
+
+### 4.1 Procedure Specification Principles
+
+The principle for specifying the procedure logic is to specify the functional behaviour of the RNC exactly and completely. The CN functional behaviour is left unspecified. The EPs Relocation Preparation, Reset, Reset Resource and Overload Control are exceptions from this principle.
+
+The following specification principles have been applied for the procedure text in clause 8:
+
+- The procedure text discriminates between:
+
+- 1) Functionality which "shall" be executed
+
+The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 of Class 3 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
+
+- 2) Functionality which "shall, if supported" be executed
+
+The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
+
+- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including *Criticality Diagnostics* IE, see section 10. For examples on how to use the *Criticality Diagnostics* IE, see Annex A.2.
+
+### 4.2 Forwards and Backwards Compatibility
+
+The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.
+
+### 4.3 Specification Notations
+
+For the purposes of the present document, the following notations apply:
+
+- | | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure | When referring to an elementary 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. RAB Assignment procedure. |
+| 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. RAB ASSIGNMENT REQUEST message. |
+| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. User Plane Mode IE. |
+| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Geographical Coordinates". |
+
+---
+
+## 5 RANAP Services
+
+RANAP provides the signalling service between UTRAN or GERAN (in Iu mode) and CN that is required to fulfil the RANAP functions described in clause 7. RANAP services are divided into four groups. The first three are based on Service Access Points (SAP) defined in TS 23.110 [16]:
+
+1. General control services: They are related to the whole Iu interface instance between RNC and logical CN domain, and are accessed in CN through the General Control SAP. They utilise connectionless signalling transport provided by the Iu signalling bearer.
+2. Notification services: They are related to specified UEs or all UEs in specified area, and are accessed in CN through the Notification SAP. They utilise connectionless signalling transport provided by the Iu signalling bearer.
+3. Dedicated control services: They are related to one UE, and are accessed in CN through the Dedicated Control SAP. RANAP functions that provide these services are associated with Iu signalling connection that is maintained for the UE in question. The Iu signalling connection is realised with connection oriented signalling transport provided by the Iu signalling bearer.
+4. MBMS control services: They are related to one MBMS Bearer Service. RANAP functions that provide these services are associated with one or several Iu signalling connection that is maintained for the MBMS Bearer Service in question during the MBMS Session. The Iu signalling connection is realised with connection oriented signalling transport provided by the Iu signalling bearer.
+
+---
+
+## 6 Services Expected from Signalling Transport
+
+Signalling transport (See TS 25.412 [5]) shall provide two different service modes for the RANAP.
+
+1. Connection oriented data transfer service. This service is supported by a signalling connection between RNC and CN domain. It shall be possible to dynamically establish and release signalling connections based on the need. Each active UE shall have its own signalling connection. Each MBMS Bearer Service during a given MBMS Session shall have one or several signalling connections. The signalling connection shall provide in sequence delivery of RANAP messages. RANAP shall be notified if the signalling connection breaks.
+2. Connectionless data transfer service. RANAP shall be notified in case a RANAP message did not reach the intended peer RANAP entity.
+
+---
+
+## 7 Functions of RANAP
+
+RANAP protocol has the following functions:
+
+- Relocating serving RNC. This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another.
+- Overall RAB management. This function is responsible for setting up, modifying and releasing RABs.
+- Queuing the setup of RAB. The purpose of this function is to allow placing some requested RABs into a queue, and indicate the peer entity about the queuing.
+- Requesting RAB release. While the overall RAB management is a function of the CN, the RNC has the capability to request the release of RAB.
+- Release of all Iu connection resources. This function is used to explicitly release all resources related to one Iu connection.
+- Requesting the release of all Iu connection resources. While the Iu release is managed from the CN, the RNC has the capability to request the release of all Iu connection resources from the corresponding Iu connection.
+- SRNS context forwarding function. This function is responsible for transferring SRNS context from the RNC to the CN for intersystem change in case of packet forwarding.
+
+- Controlling overload in the Iu interface. This function allows adjusting the load in the control plane of the Iu interface.
+- Resetting the Iu. This function is used for resetting an Iu interface.
+- Sending the UE Common ID (permanent NAS UE identity) to the RNC. This function makes the RNC aware of the UE's Common ID.
+- Paging the user. This function provides the CN for capability to page the UE.
+- Controlling the tracing of the subscriber or user equipment activity. This function allows setting the trace mode for a given subscriber or user equipment. This function also allows the deactivation of a previously established trace.
+- MDT function. This function is to enable the transfer of MDT measurements collected by the UE.
+- Transport of NAS information between UE and CN (see TS 24.008 [8]). This function has two sub-classes:
+ 1. Transport of the initial NAS signalling message from the UE to CN. This function transfers transparently the NAS information. As a consequence also the Iu signalling connection is set up.
+ 2. Transport of NAS signalling messages between UE and CN, This function transfers transparently the NAS signalling messages on the existing Iu signalling connection. It also includes a specific service to handle signalling messages differently.
+- Controlling the security mode in the UTRAN. This function is used to send the security keys (ciphering and integrity protection) to the UTRAN, and setting the operation mode for security functions.
+- Controlling location reporting. This function allows the CN to operate the mode in which the UTRAN reports the location of the UE.
+- Location reporting. This function is used for transferring the actual location information from RNC to the CN.
+- Data volume reporting function. This function is responsible for reporting unsuccessfully transmitted DL data volume over UTRAN for specific RABs.
+- Reporting general error situations. This function allows reporting of general error situations, for which function specific error messages have not been defined.
+- Location related data. This function allows the CN to either retrieve from the RNC deciphering keys (to be forwarded to the UE) for the broadcast assistance data, or request the RNC to deliver dedicated assistance data to the UE.
+- Information Transfer. This function allows the CN to transfer information to the RNC.
+- Uplink Information Exchange. This function allows the RNC to transfer or request information to the CN. For instance the RNC has the capability to request MBMS specific information to the CN e.g. the Multicast Service lists for a given UE or the IP Multicast Address and APN for one or several MBMS Bearer Services.
+- MBMS RANAP overall function. This function allows the following different sub-functions:
+ - MBMS RAB management. This function is responsible for setting up, updating and releasing the MBMS RAB as well as the MBMS Iu signalling connection corresponding to one MBMS Session. The MBMS RAB is defined for the CN PS domain only.
+ - MBMS CN (PS domain) de-registration. This function makes the RNC aware that a given Multicast Service is no longer available.
+ - MBMS UE linking/de-linking. This function makes the RNC aware that a given UE, with existing Iu-ps signalling connection, has joined/left some Multicast Service(s).
+ - Requesting MBMS Service registration/de-registration. While the overall MBMS CN de-registration is a function of the CN (PS domain), the RNC has the capability to register/de-register to a specific Multicast Service.
+
+These functions are implemented by one or several RANAP elementary procedures described in the following clause.
+
+## 8 RANAP Procedures
+
+### 8.1 Elementary Procedures
+
+In the following tables, all EPs are divided into Class 1, Class 2 and Class 3 EPs (see subclause 3.1 for explanation of the different classes):
+
+**Table 1: Class 1**
+
+| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome |
+|--------------------------------|--------------------------------------|---------------------------------------|--------------------------------------|
+| | | Response message | Response message |
+| Iu Release | IU RELEASE COMMAND | IU RELEASE COMPLETE | |
+| Relocation Preparation | RELOCATION REQUIRED | RELOCATION COMMAND | RELOCATION PREPARATION FAILURE |
+| Relocation Resource Allocation | RELOCATION REQUEST | RELOCATION REQUEST ACKNOWLEDGE | RELOCATION FAILURE |
+| Relocation Cancel | RELOCATION CANCEL | RELOCATION CANCEL ACKNOWLEDGE | |
+| SRNS Context Transfer | SRNS CONTEXT REQUEST | SRNS CONTEXT RESPONSE | |
+| Security Mode Control | SECURITY MODE COMMAND | SECURITY MODE COMPLETE | SECURITY MODE REJECT |
+| Data Volume Report | DATA VOLUME REPORT REQUEST | DATA VOLUME REPORT | |
+| Reset | RESET | RESET ACKNOWLEDGE | |
+| Reset Resource | RESET RESOURCE | RESET RESOURCE ACKNOWLEDGE | |
+| Location related Data | LOCATION RELATED DATA REQUEST | LOCATION RELATED DATA RESPONSE | LOCATION RELATED DATA FAILURE |
+| Information Transfer | INFORMATION TRANSFER INDICATION | INFORMATION TRANSFER CONFIRMATION | INFORMATION TRANSFER FAILURE |
+| Uplink Information Exchange | UPLINK INFORMATION EXCHANGE REQUEST | UPLINK INFORMATION EXCHANGE RESPONSE | UPLINK INFORMATION EXCHANGE FAILURE |
+| MBMS Session Start | MBMS SESSION START | MBMS SESSION START RESPONSE | MBMS SESSION START FAILURE |
+| MBMS Session Update | MBMS SESSION UPDATE | MBMS SESSION UPDATE RESPONSE | MBMS SESSION UPDATE FAILURE |
+| MBMS Session Stop | MBMS SESSION STOP REQUEST | MBMS SESSION STOP RESPONSE | |
+| MBMS UE Linking | MBMS UE LINKING REQUEST | MBMS UE LINKING RESPONSE | |
+| MBMS Registration | MBMS REGISTRATION REQUEST | MBMS REGISTRATION RESPONSE | MBMS REGISTRATION FAILURE |
+| MBMS CN De-Registration | MBMS CN DE-REGISTRATION REQUEST | MBMS CN DE-REGISTRATION RESPONSE | |
+| MBMS RAB Release | MBMS RAB RELEASE REQUEST | MBMS RAB RELEASE | MBMS RAB RELEASE FAILURE |
+| Enhanced Relocation Complete | ENHANCED RELOCATION COMPLETE REQUEST | ENHANCED RELOCATION COMPLETE RESPONSE | ENHANCED RELOCATION COMPLETE FAILURE |
+| SRVCC Preparation | SRVCC CS KEYS REQUEST | SRVCC CS KEYS RESPONSE | |
+| UE Radio Capability Match | UE RADIO CAPABILITY MATCH REQUEST | UE RADIO CAPABILITY MATCH RESPONSE | |
+
+**Table 2: Class 2**
+
+| Elementary Procedure | Message |
+|-----------------------------------------------|--------------------------------------|
+| RAB Modification Request | RAB MODIFY REQUEST |
+| RAB Release Request | RAB RELEASE REQUEST |
+| Iu Release Request | IU RELEASE REQUEST |
+| Relocation Detect | RELOCATION DETECT |
+| Relocation Complete | RELOCATION COMPLETE |
+| SRNS Data Forwarding Initiation | SRNS DATA FORWARD COMMAND |
+| SRNS Context Forwarding from Source RNC to CN | FORWARD SRNS CONTEXT |
+| SRNS Context Forwarding to Target RNC from CN | FORWARD SRNS CONTEXT |
+| Paging | PAGING |
+| Common ID | COMMON ID |
+| CN Invoke Trace | CN INVOKE TRACE |
+| CN Deactivate Trace | CN DEACTIVATE TRACE |
+| Location Reporting Control | LOCATION REPORTING CONTROL |
+| Location Report | LOCATION REPORT |
+| Initial UE Message | INITIAL UE MESSAGE |
+| Direct Transfer | DIRECT TRANSFER |
+| Overload Control | OVERLOAD |
+| Error Indication | ERROR INDICATION |
+| UE Specific Information | UE SPECIFIC INFORMATION INDICATION |
+| Direct Information Transfer | DIRECT INFORMATION TRANSFER |
+| MBMS RAB Establishment Indication | MBMS RAB ESTABLISHMENT INDICATION |
+| Enhanced Relocation Complete Confirm | ENHANCED RELOCATION COMPLETE CONFIRM |
+
+**Table 3: Class 3**
+
+| Elementary Procedure | Initiating Message | Response Message |
+|-----------------------------|---------------------------|------------------------------------|
+| RAB Assignment | RAB ASSIGNMENT REQUEST | RAB ASSIGNMENT RESPONSE x N (N>=1) |
+
+The following applies concerning interference between Elementary Procedures:
+
+- The Reset procedure takes precedence over all other EPs.
+- The Reset Resource procedure takes precedence over all other EPs except the Reset procedure.
+- The Iu Release procedure takes precedence over all other EPs except the Reset procedure and the Reset Resource procedure.
+
+## 8.2 RAB Assignment
+
+### 8.2.1 General
+
+The purpose of the RAB Assignment procedure is to establish new RABs and/or to enable modifications and/or releases of already established RABs for a given UE. The procedure uses connection oriented signalling.
+
+## 8.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: RAB ASSIGNMENT REQUEST
+ Note right of RNC: RNC processes request
+ RNC-->>CN: RAB ASSIGNMENT RESPONSE
+ Note right of CN: * it can be several responses
+
+```
+
+Sequence diagram of the RAB Assignment procedure. The CN (Core Network) sends a RAB ASSIGNMENT REQUEST message to the RNC (Radio Network Controller). The RNC responds with a RAB ASSIGNMENT RESPONSE message. The diagram shows multiple response messages, indicated by an asterisk (\*), which can be several responses.
+
+**Figure 1: RAB Assignment procedure. Successful operation.**
+
+The CN initiates the procedure by sending a RAB ASSIGNMENT REQUEST message. When sending the RAB ASSIGNMENT REQUEST message, the CN shall start the $T_{RABAssgt}$ timer.
+
+The CN may request the UTRAN to:
+
+- establish,
+- modify,
+- release
+
+one or several RABs with one RAB ASSIGNMENT REQUEST message.
+
+The CN shall include in the RAB ASSIGNMENT REQUEST message at least one request to either establish/modify or release a RAB.
+
+The message shall contain the information required by the UTRAN to build the new RAB configuration, such as:
+
+- list of RABs to establish or modify with their bearer characteristics;
+- list of RABs to release;
+- UE Aggregate Maximum Bit Rate (if available).
+
+For each RAB requested to be established, the message shall contain:
+
+- RAB ID;
+- NAS Synchronisation Indicator (only when available);
+- RAB parameters (including e.g. Allocation/Retention Priority);
+- User Plane Information (i.e. required User Plane Mode and required UP Mode Versions);
+- Transport Layer Information;
+- PDP Type Information (only for PS) or PDP Type Information extension (only for PS);
+- Data Volume Reporting Indication (only for PS);
+- DL GTP-PDU sequence number (only when GTP-PDU sequence number is available in cases of intersystem change from GPRS to UMTS or when establishing a RAB for an existing PDP context or in some further cases described in TS 23.060 [21]);
+
+- UL GTP-PDU sequence number (only when GTP-PDU sequence number is available in cases of intersystem change from GPRS to UMTS or when establishing a RAB for an existing PDP context or in some further cases described in TS 23.060 [21]);
+- DL N-PDU sequence number (only when N-PDU sequence number is available in case of intersystem change from GPRS to UMTS or in some further cases described in TS 23.060 [21]);
+- UL N-PDU sequence number (only when N-PDU sequence number is available in case of intersystem change from GPRS to UMTS or in some further cases described in TS 23.060 [21]).
+
+The RAB ASSIGNMENT REQUEST message shall, if supported, include the *Correlation ID* IE for each RAB established towards a L-GW collocated with the RNC.
+
+For each RAB requested to be modified, the message may contain:
+
+- RAB ID (mandatory);
+- NAS Synchronisation Indicator;
+- RAB parameters;
+- Transport Layer Information;
+- User Plane Information.
+
+If the *UE Aggregate Maximum Bit Rate* IE is present in the RAB ASSIGNMENT REQUEST message, the UTRAN shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non-GBR traffic for this UE.
+
+The *Transport Layer Information* IE may be present at a RAB modification except in the case when the only other present IE, besides the *RAB ID* IE, is the *NAS Synchronisation Indicator* IE.
+
+At a RAB modification that does not include transfer of the *NAS Synchronisation Indicator* IE, the *RAB Parameters* IE shall be present in the RAB ASSIGNMENT REQUEST message only when any previously set value for this IE is requested to be modified.
+
+At a RAB modification, the *User Plane Information* IE shall be present in the RAB ASSIGNMENT REQUEST message only when any previously set value for this IE is requested to be modified.
+
+For a RAB setup, the *SDU Format Information Parameter* IE in the *RAB Parameters* IE shall be present only if the *User Plane Mode* IE is set to "support mode for pre-defined SDU sizes" and the *Traffic Class* IE is set to either "Conversational" or "Streaming".
+
+For a RAB setup or modification, when the maximum bit rate (respectively the guaranteed bit rate when applicable) to be signalled for the RAB exceeds the maximum value of the *Maximum Bit Rate* IE (respectively *Guaranteed Bit Rate* IE), either the *Extended Maximum Bit Rate* IE (respectively *Extended Guaranteed Bit Rate* IE) shall be included together with the *Maximum Bit Rate* IE (respectively *Guaranteed Bit Rate* IE) set to its maximum value or the *Supported Maximum Bit Rate* IE (respectively *Supported Guaranteed Bit Rate* IE) shall be used.
+
+For a RAB setup or modification, if the *Extended Maximum Bit Rate* IE (respectively *Extended Guaranteed Bit Rate* IE) is present, the RNC shall consider it and ignore the *Maximum Bit Rate* IE (respectively *Guaranteed Bit Rate* IE).
+
+For a RAB if *Extended Maximum Bit Rate* IE (respectively *Extended Guaranteed Bit Rate* IE when applicable) is signalled in one direction RNC shall use the *Extended Maximum Bit Rate* IE (respectively *Extended Guaranteed Bit Rate* IE) also for the other direction for this RAB. If the *Supported Maximum Bit Rate* IE (respectively *Supported Guaranteed Bit Rate* IE) is present, it shall be used in both directions.
+
+For a RAB setup or modification, if the *Supported Maximum Bit Rate* IE (respectively *Supported Guaranteed Bit Rate* IE) is present, the RNC shall consider it and ignore the *Maximum Bit Rate* IE (respectively *Guaranteed Bit Rate* IE).
+
+For a RAB setup, the *RAB Parameters* IE may contain the *Signalling Indication* IE. The *Signalling Indication* IE shall not be present if the *Traffic Class* IE is not set to "Interactive" or if the *CN Domain Indicator* IE is not set to "PS domain".
+
+If the *RAB Parameters* IE is present for a RAB modification, the *SDU Format Information Parameter* IE in the *RAB Parameters* IE shall be present only if the *Traffic Class* IE is set to either "Conversational" or "Streaming" and if
+
+- either the User Plane mode is currently "support mode for pre-defined SDU sizes" and the *User Plane Mode* IE is not contained in the RAB ASSIGNMENT REQUEST message
+- or if the *User Plane Mode* IE optionally contained within the RAB ASSIGNMENT REQUEST message is set to "support mode for pre-defined SDU sizes".
+
+If, for a RAB requested to be modified, one (or more) of these IEs except *RAB ID* IE are not present in the RAB ASSIGNMENT REQUEST message the RNC shall continue to use the value(s) currently in use for the not present IEs.
+
+If, for a RAB requested to be modified, the *Signalling Indication* IE is not present and the *Traffic Class* IE is set to "interactive", this indicates that the signalling nature of the RAB is not changed by the modification.
+
+For each RAB requested to be released, the message shall contain:
+
+- RAB ID;
+- Cause.
+
+Upon reception of the RAB ASSIGNMENT REQUEST message, the UTRAN shall execute the requested RAB configuration. The CN may indicate that RAB QoS negotiation is allowed for certain RAB parameters and in some cases also which alternative values to be used in the negotiation in the *Alternative RAB parameters values* IE.
+
+If some of the alternative maximum bit rates (respectively alternative guaranteed bit rates when applicable) to be signalled for the RAB exceed the maximum value of the *Alternative Maximum Bit Rate* IE (respectively *Alternative Guaranteed Bit Rate* IE), they shall be included either in the *Extended Alternative Maximum Bit Rate* IE (respectively *Extended Alternative Guaranteed Bit Rate* IE), or in the *Supported Alternative Maximum Bit Rate* IE (respectively *Supported Alternative Guaranteed Bit Rate* IE). If the *Supported Alternative Maximum Bit Rate* IE (respectively *Supported Alternative Guaranteed Bit Rate* IE) is used it shall be used for all alternative bitrate definitions for the RAB.
+
+For a RAB setup or modification, if the *Extended Alternative Maximum Bit Rate* IE (respectively *Extended Alternative Guaranteed Bit Rate* IE) is present, the RNC shall consider these rates together with the bit rates signalled within the *Alternative Maximum Bit Rate* IE (respectively *Alternative Guaranteed Bit Rate* IE) if present.
+
+For an entry in the list or for a discrete value if the *Extended Alternative Maximum Bit Rate* IE (respectively *Extended Alternative Guaranteed Bit Rate* IE when applicable) is signalled in one direction RNC shall use the *Extended Alternative Maximum Bit Rate* IE (respectively *Extended Alternative Guaranteed Bit Rate* IE) also for the other direction of this entry or discrete value. If the *Supported Alternative Maximum Bit Rate* IE (respectively *Supported Alternative Guaranteed Bit Rate* IE) is present it shall be used in both directions for all entries in the list or discrete values.
+
+For a RAB setup or RAB requested to be modified, the RAB ASSIGNMENT REQUEST message may also include an alternative RAB configuration specified in the *Alternative RAB configuration* IE in the *Alternative RAB Parameter Values* IE. If *Alternative RAB configuration* IE for a RAB is included in the RAB ASSIGNMENT REQUEST message, the RNC is allowed after the successful RAB setup or RAB modification to request the CN to trigger the execution of this alternative RAB configuration. No negotiation is allowed during the RAB Assignment procedure between the requested RAB configuration and this alternative RAB configuration.
+
+If the RAB ASSIGNMENT REQUEST message contains a request of a RAB configuration with *Extended Maximum Bit Rate* IE and/or *Extended Guaranteed Bit Rate* IE respectively if *Supported Maximum Bit Rate* IE and/or *Supported Guaranteed Bit Rate* IE are greater than 16 Mbps in *RAB parameters* IE, the CN should indicate that RAB QoS negotiation is allowed. If this RAB Configuration is for a UE that is not able to support the requested bit rates according to the *Access Stratum Release Indicator* IE in TS 25.331 [10]:
+
+- The UTRAN shall, if supported, perform RAB QoS negotiation.
+- If RAB QoS negotiation is performed, the RNC shall signal the assigned bit rate indications within the *Assigned RAB Parameter Values* IE in the following way:
+ - *Extended Assigned Maximum Bit Rate* IE and *Extended Assigned Guaranteed Bit Rate* IE shall not be set in *Assigned RAB Parameter Values* IE;
+ - if the *Supported Assigned Maximum Bit Rate* IE and *Supported Assigned Guaranteed Bit Rate* IE are used, they shall be set to a value less than or equal to 16 Mbps.
+
+The same RAB ID shall only be present once in the whole RAB ASSIGNMENT REQUEST message.
+
+The RAB ID shall uniquely identify the RAB for the specific CN domain and for the particular UE, which makes the RAB ID unique over the Iu connection on which the RAB ASSIGNMENT REQUEST message is received. When a RAB ID already in use over that particular Iu instance is used, the procedure is considered as modification of that RAB.
+
+The RNC shall pass the contents of the *RAB ID* IE to the radio interface protocol for each RAB requested to be established or modified.
+
+The RNC shall establish or modify the resources according to the values of the *Allocation/Retention Priority* IE (priority level, pre-emption indicators, queuing) and the resource situation as follows:
+
+- The RNC shall consider the priority level of the requested RAB, when deciding on the resource allocation.
+- If the requested RAB is allowed for queuing and the resource situation requires so, the RNC may place the RAB in the establishment queue.
+- The priority levels and the pre-emption indicators may (singularly or in combination) be used to determine whether the RAB assignment has to be performed unconditionally and immediately. If the requested RAB is marked as "may trigger pre-emption" and the resource situation requires so, the RNC may trigger the pre-emption procedure which may then cause the forced release of a lower priority RAB which is marked as "pre-emptable". Whilst the process and the extent of the pre-emption procedure is operator-dependent, the pre-emption indicators, if given in the RAB ASSIGNMENT REQUEST message, shall be treated as follows:
+ 1. The values of the last received *Pre-emption Vulnerability* IE and *Priority Level* IE shall prevail.
+ 2. If the *Pre-emption Capability* IE is set to "may trigger pre-emption", then this allocation request may trigger the pre-emption procedure.
+ 3. If the *Pre-emption Capability* IE is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption procedure.
+ 4. If the *Pre-emption Vulnerability* IE is set to "pre-emptable", then this connection shall be included in the pre-emption process.
+ 5. If the *Pre-emption Vulnerability* IE is set to "not pre-emptable", then this connection shall not be included in the pre-emption process.
+ 6. If the *Priority Level* IE is set to "no priority" the given values for the *Pre-emption Capability* IE and *Pre-emption Vulnerability* IE shall not be considered. Instead the values "shall not trigger pre-emption" and "not pre-emptable" shall prevail.
+- If the *Allocation/Retention Priority* IE is not given in the RAB ASSIGNMENT REQUEST message, the allocation request shall not trigger the pre-emption process and the connection may be pre-empted and considered to have the value "lowest" as priority level. Moreover, queuing shall not be allowed.
+- The UTRAN pre-emption process shall keep the following rules:
+ 1. UTRAN shall only pre-empt RABs with lower priority, in ascending order of priority.
+ 2. The pre-emption may be done for RABs belonging to the same UE or to other UEs.
+
+If the *NAS Synchronisation Indicator* IE is contained in the RAB ASSIGNMENT REQUEST message, the RNC shall pass it to the radio interface protocol for transfer to the UE.
+
+If the RAB ASSIGNMENT REQUEST message includes the *PDP Type Information* IE or *PDP Type Information* extension IE, the UTRAN may use it to configure any compression algorithms.
+
+If included, the *Service Handover* IE tells if the requested RAB
+
+- should be handed over to GSM, i.e. from a NAS point of view, the requested RAB should be handed over to GSM as soon as possible although the final decision whether to perform a handover to GSM is still made in the UTRAN.
+- should not be handed over to GSM, i.e. from a NAS point of view, the requested RAB should remain in UMTS as long as possible although the final decision whether to perform a handover to GSM is still made in the UTRAN.
+
+- shall not be handed over to GSM, i.e. the requested RAB shall never be handed over to GSM. This means that the UTRAN shall not initiate handover to GSM for the UE unless the RABs with this indication have first been released with the normal release procedures.
+
+The value of the *Service Handover* IE is valid throughout the lifetime of the RAB or until changed by a RAB modification.
+
+The *Service Handover* IE shall only influence decisions made regarding UTRAN-initiated inter-system handovers.
+
+If the *Service Handover* IE is not included during RAB Setup and all subsequent RAB Modifications, the decision whether to perform an inter-system handover to GSM is only an internal UTRAN matter.
+
+If included, the *E-UTRAN Service Handover* IE tells if the requested RAB is allowed to be handed over to E-UTRAN.
+
+If the E-UTRAN service handover function is supported,
+
+- The RNC shall not trigger handover or redirection to E-UTRAN for a UE with a signaling connection only;
+- The RNC shall not trigger handover or redirection to E-UTRAN for a UE if all established RABs have *E-UTRAN Service Handover* IE set to "Handover to E-UTRAN shall not be performed".
+
+The value of the *E-UTRAN Service Handover* IE is valid throughout the lifetime of the RAB or until changed by a RAB modification.
+
+If the *E-UTRAN Service Handover* IE is not included during RAB Setup and all subsequent RAB Modifications, the decision whether to perform an inter-system mobility to E-UTRAN, e.g., handover or redirection, is only an internal UTRAN matter.
+
+The UTRAN shall report to the CN, in the first RAB ASSIGNMENT RESPONSE message, the result for all the requested RABs, such as:
+
+- List of RABs successfully established or modified.
+- List of RABs released.
+- List of RABs queued.
+- List of RABs failed to establish or modify.
+- List of RABs failed to release.
+
+The same RAB ID shall only be present once in the whole RAB ASSIGNMENT RESPONSE message.
+
+For each RAB successfully established towards the PS domain or towards the CS domain when an ALCAP is not used, the RNC shall include the *Transport Layer Address* IE and the *Iu Transport Association* IE in the RAB ASSIGNMENT RESPONSE message.
+
+For each RAB successfully released towards the PS domain, for which data volume reporting had been requested when the RAB was established, the RNC shall include the *DL Data Volumes* IE in the RAB ASSIGNMENT RESPONSE message. The *DL Data Volumes* IE shall contain in the *Unsuccessfully Transmitted DL Data Volume* IE the total amount of unsuccessfully transmitted DL data for the RAB since its establishment and may contain the *Data Volume Reference* IE.
+
+For each RAB successfully released towards the PS domain, the RNC shall include in the RAB ASSIGNMENT RESPONSE message the *DL GTP-PDU Sequence Number* IE and the *UL GTP-PDU Sequence Number* IE, if available and if the release was initiated by the UTRAN.
+
+The RNC shall report in the RAB ASSIGNMENT RESPONSE message at least one RAB:
+
+- setup/modified or
+- released or
+- queued or
+- failed to setup/modify or
+
+- failed to release.
+
+If any alternative RAB parameter values have been used when establishing or modifying a RAB, these RAB parameter values shall be included in the RAB ASSIGNMENT RESPONSE message within the *Assigned RAB Parameter Values* IE.
+
+If any alternative RAB parameter values have been used from the *Extended Alternative Maximum Bit Rate* IE (respectively *Extended Alternative Guaranteed Bit Rate* IE), these RAB parameter values shall be included in the RAB ASSIGNMENT RESPONSE message within the *Extended Assigned Maximum Bit Rate* IE (respectively *Extended Assigned Guaranteed Bit Rate* IE).
+
+For a RAB if the *Extended Assigned Maximum Bit Rate* IE (respectively *Extended Assigned Guaranteed Bit Rate* IE when applicable) is signalled in one direction RNC shall signal the *Extended Assigned Maximum Bit Rate* IE (respectively *Extended Assigned Guaranteed Bit Rate* IE) also in the other direction for this RAB. If the *Supported Assigned Maximum Bit Rate* IE (respectively *Supported Assigned Guaranteed Bit Rate* IE) is used it shall be used in both directions.
+
+If any alternative RAB parameter values have been used from the *Supported Alternative Maximum Bit Rate Information* IE (respectively *Supported Alternative Guaranteed Bit Rate Information* IE), these RAB parameter values shall be included in the RAB ASSIGNMENT RESPONSE message within the *Supported Assigned Maximum Bit Rate* IE (respectively *Supported Assigned Guaranteed Bit Rate* IE).
+
+For the CS domain, when an ALCAP is used, UTRAN shall report the successful outcome of a specific RAB to establish or modify only after the Iu user plane at RNL level is ready to be used in UL and DL. At a RAB establishment, the transport network control plane signalling required to set up the transport bearer shall use the *Transport Layer Address* IE and *Iu Transport Association* IE. At a RAB modification when *Transport Layer Address* (IE) and *Iu Transport Association* IEs are included, the RNC shall establish a new transport bearer. The transport network control plane signalling shall then use the included *Transport Layer Address* IE and *Iu Transport Association* IE. Then the switch over to this new transport bearer shall be done immediately after transport bearer establishment and initialisation of the user plane mode. If *Transport Layer Address* (IE) and *Iu Transport Association* IEs are not included, then the RNC may modify the already existing transport bearer.
+
+For the PS domain or for the CS domain when an ALCAP is not used, when they are present at a RAB modification, the RNC shall use the embedded *Transport Layer Address* IE and *Iu Transport Association* IEs as the termination point of the new transport bearer.
+
+For the PS domain or for the CS domain when an ALCAP is not used, for each RAB successfully modified, if the RNC has changed the *Transport Layer Address* IE and/or the *Iu Transport Association* IE, it shall include the new value(s) in the RAB ASSIGNMENT RESPONSE message.
+
+Before reporting the successful outcome of a specific RAB to establish or modify, the RNC shall have executed the initialisation of the user plane, if necessary.
+
+Re-initialisation of the user plane shall not be performed if:
+
+- the *RAB Parameters* IE is not included, for example during transfer of *NAS Synchronisation Indicator* IE;
+- the *RAB Parameters* IE is included but the *SDU Format Information Parameter* IE is not changed for the existing RAB and the *NAS Synchronisation Indicator* IE is not included.
+
+Re-initialisation of the user plane shall be performed if the *RAB Parameters* IE and *NAS Synchronisation Indicator* IE are included.
+
+If the RNC can not initialise the requested user plane mode for any of the user plane mode versions in the *UP Mode Versions* IE according to the rules for initialisation of the respective user plane mode versions, as described in TS 25.415 [6], the RAB Assignment shall fail with the cause value "RNC unable to establish all RFCs".
+
+In case of establishment of a RAB for the PS domain, the CN must be prepared to receive user data before the RAB ASSIGNMENT RESPONSE message has been received.
+
+If none of the RABs have been queued, the CN shall stop timer TRABsgt and the RAB Assignment procedure terminates. In that case, the procedure shall also be terminated in the UTRAN.
+
+When the request to establish or modify one or several RABs is put in a queue, the UTRAN shall start the timer $T_{\text{QUEUING}}$ . This timer specifies the maximum time for queuing of the request for establishment or modification. The same timer $T_{\text{QUEUING}}$ supervises all RABs of the request being queued.
+
+For each RAB that is queued the following outcomes are possible:
+
+- successfully established or modified;
+- failed to establish or modify;
+- failed due to expiry of the timer $T_{\text{QUEUING}}$ .
+
+For RABs indicated as queued in the first RAB ASSIGNMENT RESPONSE message, the UTRAN shall report the outcome of the queuing for every RAB individually or for several RABs in subsequent RAB ASSIGNMENT RESPONSE message(s). This is left to implementation. The UTRAN shall stop $T_{\text{QUEUING}}$ when all RABs have been either successfully established or modified or failed to establish or modify. The RAB Assignment procedure is then terminated both in the CN and the UTRAN when all RABs have been responded to.
+
+When the CN receives the response that one or several RABs are queued, it shall expect the UTRAN to provide the outcome of the queuing function for each RAB before expiry of the $T_{\text{RABAsstgt}}$ timer. In case the timer $T_{\text{RABAsstgt}}$ expires, the CN shall consider the RAB Assignment procedure terminated and the RABs not reported shall be considered as failed.
+
+In case the timer $T_{\text{QUEUING}}$ expires, the RAB Assignment procedure terminates in the UTRAN for all queued RABs, and the UTRAN shall respond for all of them in one RAB ASSIGNMENT RESPONSE message. The RAB Assignment procedure shall also be terminated in the CN.
+
+In case a request to modify or release a RAB contains the RAB ID of a RAB being queued, the RAB shall be taken out of the queue and treated according to the second request. The first request shall be responded to as a RAB failed to setup or modify with the cause value "Request superseded".
+
+If the UTRAN failed to modify a RAB, it shall keep the RAB as it was configured prior to the modification request.
+
+When UTRAN reports unsuccessful establishment/modification of a RAB, the cause value should be precise enough to enable the core network to know the reason for unsuccessful establishment/modification. Typical cause values are: "Requested Traffic Class not Available", "Invalid RAB Parameters Value", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for DL not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available", "Requested Transfer Delay not Achievable", "Invalid RAB Parameters Combination", "Condition Violation for SDU Parameters", "Condition Violation for Traffic Handling Priority", "Condition Violation for Guaranteed Bit Rate", "User Plane Versions not Supported", "Iu UP Failure", "Iu Transport Connection Failed to Establish", " $T_{\text{QUEUING}}$ Expiry".
+
+If the RAB ID of a RAB requested to be released is unknown in the RNC, this shall be reported as a RAB failed to release with the cause value "Invalid RAB ID".
+
+The RNC may indicate an impending directed retry attempt to GSM by sending a RAB ASSIGNMENT RESPONSE message with a RAB ID included in the list of RABs failed to setup and a cause value of "Directed Retry".
+
+The RNC shall be prepared to receive a RAB ASSIGNMENT REQUEST message containing a *RABs To Be Released* IE at any time and shall always reply to it. If there is an ongoing RAB Assignment procedure for a RAB indicated within the *RABs To Be Released* IE, the RNC shall discard the preceding RAB Assignment procedure for that specific RAB, release any related resources and report the released RAB within the RAB ASSIGNMENT RESPONSE message.
+
+After sending a RAB ASSIGNMENT RESPONSE message containing RAB ID within the *RABs Released* IE, the RNC shall be prepared to receive a new establishment request for a RAB identified by the same RAB ID.
+
+In case SIPTO at Iu-PS functionality is supported by the UTRAN, the following applies in addition for the successful operation of the RAB Assignment procedure:
+
+- If the *MSISDN* IE is present in the RAB ASSIGNMENT REQUEST message, then the UTRAN may offload the RAB(s) where the *Offload RAB Parameters* IE is present in the *RABs To Be Setup Or Modified Item IEs* IE. The *Access Point Name* IE and the *Charging Characteristics* IE within the *Offload RAB Parameters* IE and the *MSISDN* IE may only be used for the SIPTO at Iu-PS function and according to the description in TS 23.060 [21].
+
+### 8.2.2.1 Successful Operation for GERAN Iu-mode
+
+For GERAN Iu-mode the following shall apply in addition for the successful operation of the RAB Assignment procedure:
+
+- In case of GERAN Iu-mode, for a RAB requested to be setup or modified from the CS domain, the RAB ASSIGNMENT REQUEST message may contain the *GERAN BSC Container* IE in order to provide GERAN-specific information to GERAN (see TS 43.051 [27]).
+- In case of GERAN Iu-mode (only for CS), if the BSC cannot provide an appropriate RAB corresponding to the content of the *GERAN BSC Container* IE (if received), the BSC shall report unsuccessful RAB establishment/modification indicating the cause value "GERAN Iu-mode Failure" and the *GERAN Classmark* IE in the *GERAN Iu mode specific RABs Failed To Setup Or Modify List* IE within the RAB ASSIGNMENT RESPONSE message.
+
+### 8.2.3 Unsuccessful Operation
+
+The unsuccessful operation for this Class 3 Elementary procedure is described under the Successful Operation chapter.
+
+### 8.2.4 Abnormal Conditions
+
+For a RAB requested to be modified, if only the *RAB ID* IE, the *NAS Synchronisation Indicator* IE and the *Transport Layer Information* IE are included in the *First Setup or Modify Item* IE, the RAB shall not be modified, and the corresponding *RAB ID* IE and *Cause* IE shall be included in the "RABs Failed To Setup Or Modify List" in the RAB ASSIGNMENT RESPONSE message.
+
+If, for a RAB requested to be setup towards the PS domain, any of the following IEs:
+
+- *PDP Type Information*.
+- *PDP Type Information extension*.
+- *Data Volume Reporting Indication*.
+
+is not present, the RNC shall continue with the procedure.
+
+#### **Interactions with Relocation Preparation/Enhanced Relocation procedure:**
+
+If the relocation or enhanced relocation becomes necessary during the RAB Assignment procedure, the RNC may interrupt the ongoing RAB Assignment procedure and initiate the Relocation Preparation or Enhanced Relocation procedure as follows:
+
+1. The RNC shall terminate the RAB Assignment procedure indicating unsuccessful RAB configuration modification:
+ - for all queued RABs;
+ - for RABs not already established or modified, and
+ - for RABs not already released;with the cause "Relocation triggered".
+2. The RNC shall terminate the RAB Assignment procedure indicating successful RAB configuration modification:
+ - for RABs already established or modified but not yet reported to the CN, and
+ - for RABs already released but not yet reported to the CN.
+3. The RNC shall report the outcome of the procedure in one RAB ASSIGNMENT RESPONSE message.
+4. The RNC shall either invoke relocation by sending a RELOCATION REQUIRED message to the active CN node(s) or enhanced relocation by sending the Iur ENHANCED RELOCATION REQUEST message to the target RAN node.
+
+5. The CN shall terminate the RAB Assignment procedure at reception of the RAB ASSIGNMENT RESPONSE message.
+
+Directed retry from UMTS to GSM (CS domain only):
+
+In the case where the RNC has no RAB configuration for a particular UE in the CS domain, and the RNC receives a RAB ASSIGNMENT REQUEST message for that UE requesting the establishment of one RAB only, a directed retry to perform inter-system handover to GSM may be initiated. In this case the RNC may interrupt the ongoing RAB Assignment procedure and initiate the Relocation Preparation procedure as follows:
+
+1. The RNC shall terminate the RAB Assignment procedure indicating unsuccessful RAB configuration modification of that RAB with the cause "Directed retry".
+2. The RNC shall report the outcome of the procedure in one RAB ASSIGNMENT RESPONSE message.
+3. The RNC shall invoke relocation by sending a RELOCATION REQUIRED message to the active CN node, with the cause "Directed Retry".
+4. The CN shall terminate the RAB Assignment procedure at reception of the RAB ASSIGNMENT RESPONSE message.
+
+For a RAB setup or modification, if the *Supported Maximum Bit Rate* IE (respectively *Supported Guaranteed Bit Rate* IE) is present in the *RAB Parameters* IE, the RNC shall ignore the corresponding bitrate and/or extended bitrate definition in this IE.
+
+For a RAB setup or modification, if the *Supported Alternative Maximum Bit Rate* IE (respectively *Supported Alternative Guaranteed Bit Rate* IE) is present in the *Alternative RAB Parameter Values* IE, the RNC shall ignore the corresponding alternative bitrate and/or extended alternative bitrate definitions in this IE.
+
+## 8.3 RAB Release Request
+
+### 8.3.1 General
+
+The purpose of the RAB Release Request procedure is to enable the UTRAN to request the release of one or several radio access bearers. The procedure uses connection oriented signalling.
+
+### 8.3.2 Successful Operation
+
+
+
+```
+
+graph LR
+ RNC[RNC] -- "RAB RELEASE REQUEST" --> CN[CN]
+ style RNC fill:#fff,stroke:#000
+ style CN fill:#fff,stroke:#000
+ style RNC_base[ ] fill:#000,height:10px
+ style CN_base[ ] fill:#000,height:10px
+ RNC --- RNC_base
+ CN --- CN_base
+
+```
+
+Diagram of the RAB Release Request procedure. It shows two entities, RNC and CN, connected by a vertical line. A horizontal arrow labeled 'RAB RELEASE REQUEST' points from the RNC to the CN. Both entities have a thick horizontal bar at their base, representing the user plane connection.
+
+Figure 2: RAB Release Request procedure. Successful operation.
+
+The RNC initiates the procedure by generating a RAB RELEASE REQUEST message towards the CN. The *RABs To Be Released* IE shall indicate the list of RABs requested to release and the *Cause* IE associated to each RAB shall indicate the reason for the release, e.g. "RAB pre-empted", "Release due to UTRAN Generated Reason", "Radio Connection With UE Lost".
+
+The RNC shall indicate the *Cause* IE set to "GTP Resources Unavailable" for the reasons specified in TS 23.007 [53].
+
+Upon reception of the RAB RELEASE REQUEST message, the CN should normally initiate the appropriate release procedure for the RABs identified in the RAB RELEASE REQUEST message as defined below. It is up to the CN to decide how to react to the request.
+
+#### Interaction with Iu Release Command:
+
+If no RABs will remain according to the RAB RELEASE REQUEST message, the CN should initiate the Iu Release procedure if it does not want to keep the Iu signalling connection. The cause value to use is "No Remaining RAB".
+
+#### Interaction with RAB Assignment (release RAB):
+
+If the CN decides to release some or all indicated RABs, the CN should invoke the RAB Assignment procedure (release RAB) to this effect.
+
+### 8.3.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.4 Iu Release Request
+
+### 8.4.1 General
+
+The purpose of the Iu Release Request procedure is to enable the UTRAN to request the CN to release the Iu connection for a particular UE due to some UTRAN generated reason (e.g. "O&M Intervention", "Unspecified Failure", "User Inactivity", "Repeated Integrity Checking Failure", "Release due to UE generated signalling connection release", "Radio Connection With UE Lost", "Access Restricted Due to Shared Networks"). The procedure uses connection oriented signalling.
+
+### 8.4.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: RNC
+ Note right of CN: CN
+ RNC->>CN: IU RELEASE REQUEST
+ Note right of CN: CN
+```
+
+Sequence diagram showing the Iu Release Request procedure. An RNC (Radio Network Controller) sends an IU RELEASE REQUEST message to a CN (Core Network).
+
+**Figure 3: Iu Release Request procedure. Successful operation.**
+
+The RNS controlling the Iu connection(s) of that particular UE initiates the procedure by generating an IU RELEASE REQUEST message towards the affected CN domain(s). The procedure may be initiated for instance when the contact with a particular UE is lost or due to user inactivity.
+
+The IU RELEASE REQUEST message shall indicate the appropriate cause value for the requested Iu connection release. It is up to the CN to decide how to react to the request.
+
+#### Interactions with Iu Release procedure:
+
+The Iu Release procedure should be initiated upon reception of an IU RELEASE REQUEST message when the cause is different than "User Inactivity". When the cause is set to "User Inactivity", it is optional to initiate the Iu Release procedure.
+
+### 8.4.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.5 Iu Release
+
+### 8.5.1 General
+
+The purpose of the Iu Release procedure is to enable the CN to release an Iu connection for a particular UE and all UTRAN resources related only to that Iu connection. The procedure uses connection oriented signalling.
+
+The Iu Release procedure can be initiated for at least the following reasons:
+
+- Completion of transaction between the UE and the CN.
+- UTRAN-generated reasons, e.g. reception of an IU RELEASE REQUEST message.
+- Completion of successful relocation of SRNS.
+
+- Cancellation of relocation after successful completion of a Relocation Resource Allocation procedure.
+- Detection of two Iu connections in the same domain toward one UE.
+
+The Iu release procedure should also be initiated when there is a period of Iu signalling inactivity with no existing RAB.
+
+## 8.5.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ CN->>RNC: IU RELEASE COMMAND
+ RNC->>CN: IU RELEASE COMPLETE
+
+```
+
+Sequence diagram of Iu Release procedure showing IU RELEASE COMMAND from CN to RNC and IU RELEASE COMPLETE from RNC to CN.
+
+**Figure 4: Iu Release procedure. Successful operation.**
+
+The CN initiates the procedure by sending an IU RELEASE COMMAND message to the UTRAN.
+
+After the IU RELEASE COMMAND message has been sent, the CN shall not send further RANAP connection-oriented messages on this particular connection.
+
+The IU RELEASE COMMAND message shall include a *Cause* IE indicating the reason for the release (e.g. "Successful Relocation", "Normal Release", "Release due to UTRAN Generated Reason", "Relocation Cancelled", "No Remaining RAB").
+
+When the RNC receives the IU RELEASE COMMAND message:
+
+1. Clearing of the related UTRAN resources is initiated. However, the UTRAN shall not clear resources related to other Iu signalling connections the UE might have. The Iu transport bearers for RABs subject to data forwarding and other UTRAN resources used for the GTP-PDU forwarding process, are released by the RNC only when the timer TDATAfwd expires.
+2. The RNC returns any assigned Iu user plane resources to idle i.e. neither uplink user data nor downlink user data can be transferred over the Iu interface anymore. Then the RNC sends an IU RELEASE COMPLETE message to the CN. (The RNC does not need to wait for the release of UTRAN radio resources or for the transport network layer signalling to be completed before returning the IU RELEASE COMPLETE message.) When an IU RELEASE COMPLETE message is sent, the procedure is terminated in the UTRAN.
+
+If the IU RELEASE COMMAND message included the *End Of CSFB* IE, the RNC may use the indication to determine which of the existing mechanisms that should be used to move the UE to E UTRAN.
+
+If the IU RELEASE COMMAND message includes the *Out Of UTRAN* IE, the RNC may use the indication to determine whether to explicitly release the RRC connection.
+
+If the IU RELEASE COMMAND message included the *Last E-UTRAN PLMN Identity* IE, the RNC may take this information into account when selecting the target cell or frequency and then act as defined in TS 23.272 [66].
+
+In case the UE has been linked to Multicast Service(s) in UTRAN and the RNC receives the IU RELEASE COMMAND message from PS domain or from CS domain when no Iu signalling connection exists towards the other domain the RNC shall perform UE de-linking as described in TS 25.346 [42].
+
+The IU RELEASE COMPLETE message shall include within the *RABs Data Volume Report List* IE for each RAB towards the PS domain successfully addressed and for which data volume reporting was requested during RAB establishment, the total amount of unsuccessfully transmitted DL data for the RAB since its establishment.
+
+If the release was initiated by the UTRAN, for each RAB towards the PS domain for which the *DL GTP-PDU Sequence Number* IE and/or the *UL GTP-PDU Sequence Number* IE are (is) available, the RNC shall include the available sequence number(s) in the *RABs Released Item* IE (within the *RAB Released List* IE) in the IU RELEASE COMPLETE message.
+
+The *RAB Release Item* IE shall not be present if there is no sequence number to be reported for that RAB.
+
+Reception of an IU RELEASE COMPLETE message terminates the procedure in the CN.
+
+**Interaction with Trace:**
+
+In case of simultaneous Iu signalling connections for both CS and PS domains, if a trace session was activated by both domains, the successful release of one of the connections should not close this trace session. If the trace session was activated by only one domain and the Iu connection for this domain is successfully released, this trace session shall be stopped in UTRAN.
+
+## **8.5.3 Abnormal Conditions**
+
+If the Iu Release procedure is not initiated towards the source RNC from the CN before the expiry of timer $T_{RELOCoverall}$ , the source RNC should initiate the Iu Release Request procedure towards the CN with a cause value " $T_{RELOCoverall}$ expiry".
+
+## **8.6 Relocation Preparation**
+
+### **8.6.1 General**
+
+The purpose of the Relocation Preparation procedure is to prepare relocation of SRNS either with involving the UE or without involving the UE. The relocation procedure shall be co-ordinated over all Iu signalling connections existing for the UE in order to allow Relocation co-ordination in the target RNC. The procedure uses connection oriented signalling.
+
+The source RNC shall not initiate the Relocation Preparation procedure for an Iu signalling connection if a Prepared Relocation exists in the RNC for that Iu signalling connection or if a Relocation Preparation procedure is ongoing for that Iu signalling connection or in the case of a MOCN configuration if the Rerouting Function is ongoing.
+
+### **8.6.2 Successful Operation**
+
+
+
+```
+
+sequenceDiagram
+ participant Source RNC
+ participant CN
+ Source RNC->>CN: RELOCATION REQUIRED
+ CN->>Source RNC: RELOCATION COMMAND
+
+```
+
+Sequence diagram showing 'RELOCATION REQUIRED' message from Source RNC to CN, followed by 'RELOCATION COMMAND' message from CN to Source RNC.
+
+**Figure 5: Relocation Preparation procedure. Successful operation.**
+
+The source RNC initiates the procedure by sending a RELOCATION REQUIRED message. The source RNC shall decide whether to initiate an intra-system Relocation or an inter-system handover.
+
+The source RNC shall indicate the appropriate cause value for the Relocation in the *Cause* IE. Typical cause values are "Time critical Relocation", "Resource optimisation relocation", "Relocation desirable for radio reasons", "Directed Retry", "Reduce Load in Serving Cell", "Access Restricted Due to Shared Networks", "No Iu CS UP relocation".
+
+The source RNC shall determine whether the relocation of SRNS shall be executed with or without involvement of the UE. The source RNC shall set accordingly the *Relocation Type* IE to "UE involved in relocation of SRNS" or "UE not involved in relocation of SRNS".
+
+In case of intra-system Relocation, the source RNC:
+
+- shall indicate in the *Source ID* IE the RNC-ID of the source RNC and in the *Target ID* IE the RNC-ID of the target RNC only including the RAC if the message is sent towards the PS domain;
+- shall in case SRVCC is performed include the *SRVCC HO Indication* IE in the RELOCATION REQUIRED message. The value of *SRVCC HO Indication* IE shall be set by the source RNC. In case the source RNC decides to involve at the target side only CS domain, the *SRVCC HO Indication* IE shall be set to "CS only", to "PS and CS" in case CS and PS domain at the target side shall be involved;
+
+NOTE: The *Number of Iu Instances* IE within the *Source RNC to Target RNC Transparent Container* IE shall be set according to the *SRVCC HO Indication* IE.
+
+- shall include in the RELOCATION REQUIRED message the *Source to Target Transparent Container* IE. This container shall be encoded according to the *Source RNC to Target RNC Transparent Container* IE definition. The *Source RNC to Target RNC Transparent Container* IE shall include:
+ - the *Relocation Type* IE and the *Number of Iu Instances* IE containing the number of Iu signalling connections existing for the UE.
+ - the *Integrity Protection Key* IE from the last received domain on which the Security Mode Control procedure has been successfully performed, and the associated *Chosen Integrity Protection Algorithm* IE that has been selected for this domain.
+ - the *Ciphering Key* IE for the signalling data from the last received domain on which the Security Mode Control procedure has been successfully performed if the ciphering has been started, together with the associated *Chosen Encryption Algorithm* IE that has been selected for this domain. If the ciphering has not been started, the RNC may include the *Ciphering Key* IE and the *Chosen Encryption Algorithm* IE if they are available.
+ - for each domain where the Security Mode Control procedure has been successfully performed in the source RNC, the *Chosen Encryption Algorithm* IE of CS (PS respectively) user data corresponding to the ciphering alternative that has been selected for this domain. If the Security Mode Control procedure had not been successful or performed for one domain or had proposed no ciphering alternative, the *Chosen Encryption Algorithm* IE for the user data of this domain shall not be included. When both the CS and the PS user data *Chosen Encryption Algorithm* IEs are provided, they shall be the same.
+ - the *RRC Container* IE. If the *Relocation Type* IE is set to "UE not involved in relocation of SRNS" and the UE is using DCH(s), DSCH(s), USCH(s), HS-DSCH and/or E-DCH, the *Source RNC to Target RNC Transparent Container* IE shall:
+ - for each RAB include the RAB ID, the *CN Domain Indicator* IE and the mapping between each RAB subflow and transport channel identifier(s) over Iur, i.e. if the RAB is carried on a DCH(s), the DCH ID(s) shall be included, and when it is carried on DSCH(s), USCH(s), HS-DSCH and/or E-DCH, the DSCH ID(s), USCH ID(s), HS-DSCH MAC-d Flow ID and/or E-DCH MAC-d Flow ID respectively shall be included.
+ - only in the case the active SRBs in SRNC are not all mapped onto the same DCH, include the *SRB TrCH Mapping* IE containing for each SRB the SRB ID and the associated transport channel identifier over Iur, i.e. if the SRB is carried on a DCH, the DCH ID shall be included, and when it is carried on DSCH, USCH, HS-DSCH and/or E-DCH, the DSCH ID, USCH ID, HS-DSCH MAC-d Flow ID and/or E-DCH MAC-d Flow ID respectively shall be included.
+ - the *d-RNTI* IE, if the *Relocation Type* IE is set to "UE not involved in relocation of SRNS".
+ - the *Target Cell ID* IE, if the *Relocation Type* IE is set to "UE involved in relocation of SRNS".
+ - in the *PS RAB To Be Replaced* IE the RAB ID of the voice RAB which is relocated from the PS to the CS CN domain, in case SRVCC is performed.
+ - the *d-RNTI for No IuCS UP* IE, if the source RNC doesn't have an Iu-CS user plane connection, the *Relocation Type* IE is set to "UE involved in relocation of SRNS" and the reason for the relocation is the source RNC cannot support CS service. The *Cause* IE shall be set as "No Iu CS UP relocation" in the RELOCATION REQUIRED message.
+ - the *MBMS Linking Information* IE, if available, in case the UE has been linked to at least one Multicast Service.
+ - the *UE History Information* IE and the source RNC shall add the stored information to the *Last Visited Cell List* IE, in case the source RNC is configured to collect UE history information.
+ - the *Subscriber Profile ID for RAT/Frequency priority* IE if available in the source RNC.
+
+- the *Management Based MDT Allowed* IE only or the *Management Based MDT Allowed* IE and the *Management Based MDT PLMN List* IE, if this has been provided to the RNC and the serving PLMN of the relocation target is included in the *Management Based MDT PLMN List*.
+- the *Last E-UTRAN PLMN Identity* IE if available in the source RNC.
+- may in case a Trace Recording Session is active in the Source RNC due to a Signalling Based Activation (see TS 32.421 [37]), include the *Trace Recording Session Information* IE containing information identifying the Trace Record being generated in the *Source RNC to Target RNC Transparent Container* IE.
+
+In case of inter-system handover to GSM CS domain, the RNC:
+
+- the source RNC shall indicate in the *Source ID* IE the Service Area Identifier and in the *Target ID* IE the cell global identity of the cell in the target system;
+- shall include the *MS Classmark 2* and *MS Classmark 3* IEs received from the UE in the RELOCATION REQUIRED message to the CN;
+- shall include the *Old BSS to New BSS Information* IE within the RELOCATION REQUIRED message only if the information is available. This information shall include, if available, the current traffic load in the source cell, i.e. prior to the inter-system handover attempt. This information shall also include the source cell identifier the included traffic load values correspond to. In the case the UE is using, prior to the inter-system handover attempt, radio resources of more than one cell, it is implementation specific for which cell the source RNC should report the current traffic load and the cell identifier.
+- shall in case SRVCC is performed include the *SRVCC HO Indication* IE in the RELOCATION REQUIRED message. The value of *SRVCC HO Indication* IE shall be set to "CS only" by the source RNC;
+
+In case of inter-system handover to GSM PS domain, the RNC:
+
+- shall indicate in the *Source ID* IE the Service Area Identifier, in the *Target ID* IE the cell global identity of the cell in the target system and shall also indicate routing area code for the relevant cell in the target system;
+- shall include the *Source BSS to Target BSS Transparent Container* IE within the RELOCATION REQUIRED message to the CN. It may indicate in this container whether it requests to receive the SI/PSI container from the external inter-system handover target in the RELOCATION COMMAND message.
+
+In case of inter-system handover towards the GSM CS domain and GSM PS domain in parallel, the source RNC:
+
+- shall include in the *Target ID* IE the same cell global identity of the cell in the target system for CS domain and PS domain and set the appropriate information about the nature of the CS/PS inter-system handover (see TS 43.055 [47]) in the *Old BSS to New BSS Information* IE and *Source BSS to Target BSS Transparent Container* IE accordingly.
+- shall in case SRVCC is performed include the *SRVCC HO Indication* IE in the RELOCATION REQUIRED message. The value of *SRVCC HO Indication* IE shall be set to "PS and CS" by the source RNC;
+
+In case of inter-system handover to E-UTRAN (as specified in TS 23.401 [48]), the RNC:
+
+- shall indicate in the *Source ID* IE the RNC-ID of the source RNC and in the *Target ID* IE either the eNB-ID or the Corresponding RNC-ID of the target eNodeB in the target system (see subclause 9.2.1.25);
+- shall include the *Source to Target Transparent Container* IE within the RELOCATION REQUIRED message. The information in the container shall be encoded according to the *Source eNB to Target eNB Transparent Container* IE definition as specified in TS 36.413 [49].
+- shall, in case rSRVCC is performed, include the *rSRVCC HO Indication* IE in the RELOCATION REQUIRED message. The value of *rSRVCC HO Indication* IE shall be set to "PS only" by the source RNC.
+
+When the source RNC sends the RELOCATION REQUIRED message, it shall start the timer $T_{\text{RELOCprep}}$ .
+
+When the preparation including resource allocation in the target system is ready and the CN has decided to continue the relocation of SRNS, the CN shall send a RELOCATION COMMAND message to the source RNC and the CN shall start the timer $T_{\text{RELOCcomplete}}$ .
+
+If the *CSG Id* IE and no *Cell Access Mode* IE are received in the RELOCATION REQUIRED message, the CN shall perform the access control according to the CSG Subscription Data of that UE and if the access control is successful, or if one of the RABs has some particular ARP values (see TS 23.060 [21]), it shall continue the relocation and propagate the target *CSG Id* IE to the target side. If the access control is unsuccessful but at least one of the RABs has some particular ARP values (see TS 23.060 [21]) the CN shall also provide the *CSG Membership Status* IE set to "non-member" to the target side.
+
+If the *CSG Id* IE and the *Cell Access Mode* IE set to "hybrid" are received in the RELOCATION REQUIRED message, the CN shall provide the *CSG Membership Status* IE of the UE and the target CSG Id to the target side.
+
+If the *Target To Source Transparent Container* IE or the *L3 information* IE or the *Target BSS to Source BSS Transparent Container* IE is received by the CN from the relocation target, it shall be included in the RELOCATION COMMAND message.
+
+The RELOCATION COMMAND message may also contain the *Inter-System Information Transparent Container* IE.
+
+In case of SRVCC operation, when the target system is GERAN the RELOCATION COMMAND message shall contain the *SRVCC Information* IE.
+
+In case of rSRVCC operation, the RELOCATION COMMAND message shall contain the *rSRVCC Information* IE.
+
+If the *Target BSS to Source BSS Transparent Container* IE is received in the RELOCATION COMMAND message, only the value part of the UE related containers received shall be sent to the UE.
+
+For each RAB successfully established in the target system and originating from the PS domain, the RELOCATION COMMAND message shall contain at least one pair of Iu transport address and Iu transport association to be used for the forwarding of the DL N-PDU duplicates towards the relocation target. If more than one pair of Iu transport address and Iu transport association is included, the source RNC shall select one of the pairs to be used for the forwarding of the DL N-PDU duplicates towards the relocation target. Upon reception of the RELOCATION COMMAND message from the PS domain, the source RNC shall start the timer $T_{DATAfwd}$ .
+
+The Relocation Preparation procedure is terminated in the CN by transmission of the RELOCATION COMMAND message.
+
+If the target system (including target CN) does not support all existing RABs, the RELOCATION COMMAND message shall contain a list of RABs indicating all the RABs that are not supported by the target system. This list may include information on RABs from the PS domain not existing in the source RNC which shall be ignored by the source RNC. This list is contained in the *RABs to Be Released* IE. The source RNC shall use this list to avoid transferring associated contexts where applicable and may use this list e.g. to decide if to cancel the relocation or not. The resources associated with not supported RABs shall not be released until the relocation is completed. This is in order to make a return to the old configuration possible in case of a failed or cancelled relocation.
+
+Upon reception of the RELOCATION COMMAND message the source RNC shall stop the timer $T_{RELOCprep}$ , start the timer $T_{RELOCoverall}$ and terminate the Relocation Preparation procedure. The source RNC is then defined to have a Prepared Relocation for that Iu signalling connection.
+
+When the Relocation Preparation procedure is successfully terminated and when the source RNC is ready, the source RNC should trigger the execution of relocation of SRNS.
+
+#### **Interactions with the SRVCC Preparation procedure:**
+
+In case of SRVCC operation, the *Source RNC to Target RNC Transparent Container* IE shall include the *Integrity Protection Key* IE, the *Ciphering Key* IE for the signalling data and the SRVCC Information as received during the SRVCC Preparation procedure.
+
+#### **Interactions with the rSRVCC Preparation procedure:**
+
+In case of rSRVCC operation, the RNC shall only initiate the Relocation Preparation procedure on the Iu-CS signalling connections existing for the UE.
+
+#### **Interactions with other procedures:**
+
+If, after a RELOCATION REQUIRED message is sent and before the Relocation Preparation procedure is terminated, the source RNC receives a RANAP message initiating another connection oriented RANAP class 1 or class 3 procedure
+
+(except IU RELEASE COMMAND message, which shall be handled normally) via the same Iu signalling connection, the source RNC shall either:
+
+1. cancel the Relocation Preparation procedure i.e. execute the Relocation Cancel procedure with an appropriate value for the *Cause* IE, e.g. "Interaction with other procedure", and after successful completion of the Relocation Cancel procedure, the source RNC shall continue the initiated RANAP procedure;
+
+or
+
+2. terminate the initiated RANAP procedure without any changes in UTRAN by sending the appropriate response message with the cause value "Relocation Triggered" to the CN. The source RNC shall then continue the relocation of SRNS.
+
+If during the Relocation Preparation procedure the source RNC receives a DIRECT TRANSFER message it shall be handled normally up to the anticipated limit according to section 14.12.4.2 TS 25.331 [10].
+
+If during the Relocation Preparation procedure the source RNC receives connection oriented RANAP class 2 messages (with the exception of DIRECT TRANSFER message) it shall decide to either execute the procedure immediately or suspend it. In case the relocation is cancelled, the RNC shall resume any suspended procedures (if any).
+
+After the Relocation Preparation procedure is successfully terminated, all RANAP messages (except IU RELEASE COMMAND message, which shall be handled normally) received via the same Iu signalling bearer shall be ignored by the source RNC.
+
+### 8.6.2.1 Successful Operation for GERAN Iu-mode
+
+The relocation between UTRAN and GERAN Iu-mode shall be considered in the Relocation Preparation procedure as intra-system relocation from RANAP point of view.
+
+For GERAN Iu-mode and to support Relocation towards a GERAN BSC in Iu mode the following shall apply in addition for the successful operation of the Relocation Preparation procedure:
+
+- In case of a Relocation to GERAN Iu-mode (only for CS), the RNC shall include, if available, the *GERAN Classmark* IE within the RELOCATION REQUIRED message in those cases where the transmission of the *GERAN Classmark* IE is required, as defined in TS 43.051 [27].
+
+### 8.6.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant Source RNC
+ participant CN
+ Note left of Source RNC:
+ Source RNC->>CN: RELOCATION REQUIRED
+ Note right of CN:
+ CN-->>Source RNC: RELOCATION PREPARATION FAILURE
+ Note left of Source RNC:
+
+```
+
+Sequence diagram illustrating the Unsuccessful Operation of the Relocation Preparation procedure. The diagram shows two entities: Source RNC and CN. The Source RNC sends a RELOCATION REQUIRED message to the CN. The CN responds with a RELOCATION PREPARATION FAILURE message back to the Source RNC.
+
+**Figure 6: Relocation Preparation procedure. Unsuccessful operation.**
+
+If the CN or target system is not able to even partially accept the relocation of SRNS, or a failure occurs during the Relocation Preparation procedure in the CN, or the CN decides not to continue the relocation of SRNS, the CN shall send a RELOCATION PREPARATION FAILURE message to the source RNC.
+
+The RELOCATION PREPARATION FAILURE message shall contain the appropriate value for the *Cause* IE, e.g. "TRELOCalloc expiry", "Relocation Failure in Target CN/RNC or Target System", "Relocation not supported in Target RNC or Target System", "Relocation Target not allowed", "No Radio Resources Available in Target Cell" or "Traffic Load In The Target Cell Higher Than In The Source Cell".
+
+Transmission of the RELOCATION PREPARATION FAILURE message terminates the procedure in the CN. Reception of the RELOCATION PREPARATION FAILURE message terminates the procedure in UTRAN.
+
+When the Relocation Preparation procedure is unsuccessfully terminated, the existing Iu signalling connection can be used normally.
+
+If the Relocation Preparation procedure is unsuccessfully terminated, the CN shall release the possibly existing Iu signalling connection for the same UE and related to the same relocation of SRNS towards the target RNC by initiating the Iu Release procedure towards the target RNC with an appropriate value for the *Cause* IE, e.g. "Relocation Cancelled".
+
+The RELOCATION PREPARATION FAILURE message may contain the *Inter-System Information Transparent Container* IE.
+
+If the *CSG Id* IE and no *Cell Access Mode* IE are received in the RELOCATION REQUIRED message and the access control is unsuccessful and if none of the RABs has some particular ARP values (see TS 23.060 [21]), the CN shall send the RELOCATION PREPARATION FAILURE message with an appropriate cause value to the source RNC. Upon reception, the source RNC may decide to prevent relocation for that UE towards CSG cells with corresponding CSG Id.
+
+#### Interactions with Relocation Cancel procedure:
+
+If there is no response from the CN to the RELOCATION REQUIRED message before timer $T_{\text{RELOCprep}}$ expires in the source RNC, the source RNC shall cancel the Relocation Preparation procedure by initiating the Relocation Cancel procedure with the appropriate value for the *Cause* IE, e.g. " $T_{\text{RELOCprep}}$ expiry".
+
+### 8.6.4 Abnormal Conditions
+
+If the target RNC indicated in the RELOCATION REQUIRED message is not known to the CN:
+
+1. The CN shall reject the relocation of SRNS by sending a RELOCATION PREPARATION FAILURE message to the source RNC with *Cause* IE set to "Unknown target RNC".
+2. The CN shall continue to use the existing Iu connection towards the source RNC.
+
+NOTE: In case two CN domains are involved in the SRNS Relocation Preparation procedure and the Source RNC receives the *Target RNC to Source RNC Transparent Container* IE via two CN domains, it may check whether the content of the two *Target RNC to Source RNC Transparent Container* IE is the same. In case the Source RNC receives two different *Target RNC to Source RNC Transparent Container* IEs, the RNC behaviour is left implementation-specific.
+
+NOTE: In case two CN domains are involved in the SRNS Relocation Preparation procedure due to the inter-system handover towards the GSM CS domain and GSM PS domain in parallel and the Source RNC receives the *L3 Information* IE from CS domain and the *Target BSS to Source BSS Transparent Container* IE from PS domain, it may check whether the content of the *L3 Information* IE and the content of the *Target BSS to Source BSS Transparent Container* IE is the same. In case the Source RNC receives two IEs with different contents, the RNC behaviour is left implementation-specific.
+
+### 8.6.5 Co-ordination of Two Iu Signalling Connections
+
+If the RNC decides to initiate the Relocation Preparation procedure for a UTRAN to UTRAN relocation, the RNC shall initiate simultaneously a Relocation Preparation procedure on all Iu signalling connections existing for the UE. The source RNC shall also include the same *Source RNC to Target RNC Transparent Container* IE, *Relocation Type* IE, *Source ID* IE and *Cause* IE in the RELOCATION REQUIRED message towards the two domains.
+
+For intersystem handover to GSM, the Relocation Preparation procedure shall be initiated either only towards the circuit-switched CN or only towards the packet-switched CN, if the inter-system handover towards the GSM CS domain and GSM PS domain in parallel is not supported. Otherwise the Relocation Preparation procedure shall be simultaneously initiated towards both the circuit-switched CN and the packet-switched CN.
+
+The source RNC shall not trigger the execution of relocation of SRNS unless it has received a RELOCATION COMMAND message from all Iu signalling connections for which the Relocation Preparation procedure has been initiated, except for the case where there is at least one of the RABs that has a particular ARP value (see TS 23.060 [21]).
+
+If the source RNC receives a RELOCATION PREPARATION FAILURE message from the CN, the RNC shall initiate the Relocation Cancel procedure on the other Iu signalling connection for the UE if the other Iu signalling connection
+
+exists and if the Relocation Preparation procedure is still ongoing or the procedure has terminated successfully in that Iu signalling connection, except for the case where there is at least one of the RABs that has a particular ARP value (see TS 23.060 [21]) in the other domain.
+
+## 8.7 Relocation Resource Allocation
+
+### 8.7.1 General
+
+The purpose of the Relocation Resource Allocation procedure is to allocate resources from a target RNS for a relocation of SRNS. The procedure shall be co-ordinated over all Iu signalling connections existing for the UE. The procedure uses connection oriented signalling.
+
+NOTE: In case of SRVCC operation, the procedure shall be co-ordinated in the domains which the source RNC decides to involve in the SRVCC operation.
+
+### 8.7.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant Target RNC
+ participant CN
+ CN->>Target RNC: RELOCATION REQUEST
+ Target RNC->>CN: RELOCATION REQUEST ACKNOWLEDGE
+
+```
+
+Sequence diagram showing the successful operation of the Relocation Resource Allocation procedure. A CN node sends a RELOCATION REQUEST message to a Target RNC. The Target RNC responds with a RELOCATION REQUEST ACKNOWLEDGE message.
+
+**Figure 7: Relocation Resource Allocation procedure. Successful operation.**
+
+The CN initiates the procedure by generating a RELOCATION REQUEST message. In a UTRAN to UTRAN relocation, the message shall contain the information (if any) required by the UTRAN to build at least the same set of RABs as existing for the UE before the relocation, except the relocation due to SRVCC operation. The CN may indicate that RAB QoS negotiation is allowed for certain RAB parameters and in some cases also which alternative values to be used in the negotiation.
+
+The RELOCATION REQUEST message may also include an alternative RAB configuration for a RAB specified in the *Alternative RAB configuration* IE in the *Alternative RAB Parameter Values* IE. If *Alternative RAB configuration* IE for a RAB is included in the RELOCATION REQUEST message, the target RNC is allowed after the successful relocation to request the CN to trigger the execution of this alternative RAB configuration. No negotiation is allowed during the Relocation Resource Allocation procedure between the requested RAB configuration and this alternative RAB configuration.
+
+When the CN transmits the RELOCATION REQUEST message, it shall start the timer $T_{RELOCalloc}$ .
+
+When a RELOCATION REQUEST message is sent from a CN node towards an RNC for which the sending CN node is not the default CN node, the *Global CN-ID* IE shall be included.
+
+Upon reception of the RELOCATION REQUEST message, the target RNC shall initiate allocation of requested resources.
+
+The RELOCATION REQUEST message shall contain the following IEs:
+
+- *Permanent NAS UE Identity* IE (if available);
+- *Cause* IE;
+- *CN Domain Indicator* IE;
+
+- *Source RNC To Target RNC Transparent Container IE;*
+- *Iu Signalling Connection Identifier IE;*
+- *Integrity Protection Information IE (if available);*
+- *SNA Access Information IE (if available);*
+- *UESBI-Iu IE (if available);*
+- *Selected PLMN identity IE if in MOCN or GWCN configuration;*
+- *CN MBMS Linking Information IE (if available);*
+- *UE Aggregate Maximum Bit Rate IE (if available);*
+- *Anchor PLMN Identity IE (if available).*
+
+For each RAB requested to relocate (or to be created e.g. in the case of inter-system handover), the message shall contain the following IEs:
+
+- *RAB-ID IE;*
+- *NAS Synchronisation Indicator IE (if the relevant NAS information is provided by the CN);*
+- *RAB parameters IE;*
+- *User Plane Information IE;*
+- *Transport Layer Address IE;*
+- *Iu Transport Association IE;*
+- *Data Volume Reporting Indication IE (only for PS);*
+- *PDP Type Information IE (only for PS).*
+
+The RELOCATION REQUEST message may include the following IE:
+
+- *Encryption Information IE (shall not be included if the Integrity Protection Information IE is not included);*
+- *CSG Membership Status IE (shall be included in cases of relocation of CSG capable UEs to hybrid cells);*
+- *PDP Type Information extension IE (may be included if PDP Type Information IE is included).*
+
+For each RAB requested to relocate the message may include the following IEs:
+
+- *Service Handover IE;*
+- *Alternative RAB Parameter Values IE;*
+- *E-UTRAN Service Handover IE.*
+
+The following information elements received in RELOCATION REQUEST message require the same special actions in the RNC as specified for the same IEs in the RAB Assignment procedure:
+
+- *RAB-ID IE;*
+- *User plane Information IE (i.e. required User Plane Mode and required User Plane Versions);*
+- *Priority level IE, Pre-emption Capability IE and Pre-emption Vulnerability IE;*
+- *Service Handover IE;*
+- *E-UTRAN Service Handover IE.*
+
+The *SDU Format Information Parameter* IE in the *RAB Parameters* IE shall be present only if the *User Plane Mode* IE is set to "support mode for pre-defined SDU sizes" and the *Traffic Class* IE is set to either "Conversational" or "Streaming".
+
+For a RAB setup, the *RAB Parameters* IE may contain the *Signalling Indication* IE. The *Signalling Indication* IE shall not be present if the *Traffic Class* IE is not set to "Interactive" or if the *CN Domain Indicator* IE is not set to "PS domain".
+
+If the RELOCATION REQUEST message includes the Permanent NAS UE identity (i.e. IMSI), the RNC shall associate the permanent identity to the RRC Connection of that user and shall save it for the duration of the RRC connection.
+
+If the RELOCATION REQUEST message includes the *PDP Type Information* IE or *PDP Type Information extension* IE, the UTRAN may use this IE to configure any compression algorithms.
+
+If the *CSG Id* IE is received in the RELOCATION REQUEST message, the UTRAN shall validate it by comparing it with the CSG ID broadcast by the target cell. If it is valid and if the *CSG Membership Status* IE is received set to "member", the target RNC may apply appropriate handling to the UE.
+
+If the *CSG Membership Status* IE and the *CSG Id* IE are received in the RELOCATION REQUEST message and the CSG Id does not correspond to the CSG Id broadcast by the target cell, the RNC may provide the QoS to the UE as for a non member and shall send back in the RELOCATION REQUEST ACKNOWLEDGE message the actual CSG Id broadcast by the target cell.
+
+If the target RNC receives the *CSG Id* IE and the *CSG Membership Status* IE is set to "non-member" in the RELOCATION REQUEST message and the target cell is a CSG cell and at least one of the RABs has some particular ARP values (see TS 23.060 [21]) the RNC shall send back the RELOCATION REQUEST ACKNOWLEDGE to the CN accepting those RABs and failing the other RABs.
+
+The *Cause* IE shall contain the same value as the one received in the related RELOCATION REQUIRED message.
+
+The *Iu Signalling Connection Identifier* IE contains an Iu signalling connection identifier which is allocated by the CN. The value for the *Iu Signalling Connection Identifier* IE shall be allocated so as to uniquely identify an Iu signalling connection for the involved CN node. The RNC shall store and remember this identifier for the duration of the Iu connection.
+
+The RNC shall, if supported, use the *UESBI-Iu* IE when included in the RELOCATION REQUEST message. If *UESBI-Iu* IE contains an IMEISV the RNC may use this information to determine the characteristics of the UE for subsequent handling.
+
+If the *CN MBMS Linking Information* IE is included in the RELOCATION REQUEST message, the RNC shall, if supported, use the *CN MBMS Linking Information* IE to perform suitable UE linking as described in TS 25.346 [42].
+
+The algorithms within the *Integrity Protection Information* IE and the *Encryption Information* IE shall be ordered in preferred order with the most preferred first in the list.
+
+The *Permitted Encryption Algorithms* IE within the *Encryption Information* IE may contain "no encryption" within an element of its list in order to allow the RNC not to cipher the respective connection. This can be done either by not starting ciphering or by using the UEA0 algorithm. In the absence of the *Encryption Information* IE, the RNC shall not start ciphering.
+
+The *Source To Target Transparent Container* IE is encoded as the *Source RNC To Target RNC Transparent Container* IE. The following applies for the *Source RNC To Target RNC Transparent Container* IE:
+
+- In case of intra-system relocation, if no *Integrity Protection Key* IE (*Ciphering Key* IE respectively) is provided within the *Source RNC to Target RNC Transparent Container* IE, the target RNC shall not start integrity protection (ciphering respectively).
+- In case of intra-system relocation, when an *Ciphering Key* IE is provided within the *Source RNC to Target RNC Transparent Container* IE, the target RNC may select to use a ciphering alternative where an algorithm is used. It shall in this case make use of this key to cipher its signalling data whatever the selected algorithm. The *Encryption Key* IE that is contained within the *Encryption Information* IE of the RELOCATION REQUEST message shall never be considered for ciphering of signalling data.
+
+- In case of intra-system relocation, when an *Integrity Protection Key IE* is provided within the *Source RNC to Target RNC Transparent Container IE*, the target RNC shall select one integrity algorithm to start integrity and shall in this case make use of this key whatever the selected algorithm. The integrity protection key that is contained within the *Integrity Protection Information IE* of the RELOCATION REQUEST message shall never be considered.
+- In case of intra-system relocation, when a *Trace Recording Session Information IE* is provided within the *Source RNC to Target RNC Transparent Container IE*, the Target RNC should store that information to include it in a potential future Trace Record for that UE.
+- If the *Subscriber Profile ID for RAT/Frequency priority IE* is contained in the *Source RNC to Target RNC Transparent Container IE*, the target RNC shall store the received Subscriber Profile ID for RAT/Frequency priority and use it as defined in TS 36.300 [52].
+- If the *CSFB Information IE* is contained in the *Source RNC to Target RNC Transparent Container IE*, the target RNC may apply special treatment.
+- The RELOCATION REQUEST message may contain the *Cell Load Group Information IE* in the *Source RNC to Target RNC Transparent Container IE*.
+- If the *Management Based MDT Allowed IE* only or the *Management Based MDT Allowed IE* and the *Management Based MDT PLMN List IE*, is contained in the *Source RNC to Target RNC Transparent Container IE*, the target RNC shall use it, if supported, to allow subsequent selection of the UE for management based MDT as defined in TS 32.422 [38].
+- If the *Last E-UTRAN PLMN Identity IE* is contained in the *Source RNC to Target RNC Transparent Container IE*, the target RNC may store the received last E-UTRAN PLMN Identity and use it as defined in TS 23.272 [66].
+
+In case of inter-system relocation, the integrity protection and ciphering information to be considered shall be the ones received in the *Integrity Protection Information IE* and *Encryption Information IE* of the RELOCATION REQUEST message.
+
+The *Global CN-ID IE* contains the identity of the CN node that sent the RELOCATION REQUEST message, and it shall, if included, be stored together with the Iu signalling connection identifier. If the *Global CN-ID IE* is not included, the RELOCATION REQUEST message shall be considered as coming from the default CN node for the indicated CN domain.
+
+The following additional actions shall be executed in the target RNC during the Relocation Resource Allocation procedure:
+
+If included in the RELOCATION REQUEST ACKNOWLEDGE message, the *Target to Source Transparent Container IE* shall be encoded as the *Target RNC to Source RNC Transparent Container IE*.
+
+If the *Relocation Type IE* is set to "UE involved in relocation of SRNS":
+
+- except the relocation due to SRVCC operation, the target RNC should not accept a requested RAB if the RAB did not exist in the source RNC before the relocation. In case of SRVCC operation, the target RNC may accept CS RAB even if it did not exist in the source RNC before the relocation.
+- The target RNC may accept a requested RAB only if the RAB can be supported by the target RNC.
+- Other RABs shall be rejected by the target RNC in the RELOCATION REQUEST ACKNOWLEDGE message with an appropriate value in the *Cause IE*, e.g. "Unable to Establish During Relocation".
+- The target RNC shall include information adapted to the resulting RAB configuration in the target to source RNC transparent container to be included in the RELOCATION REQUEST ACKNOWLEDGE message sent to the CN. If the target RNC supports triggering of the Relocation Detect procedure via the Iur interface, the RNC shall assign a d-RNTI for the context of the relocation and include it in the container. If two CNs are involved in the relocation of SRNS, the target RNC may, however, decide to send the container to only one CN.
+- If any alternative RAB parameter values have been used when allocating the resources, these RAB parameter values shall be included in the RELOCATION REQUEST ACKNOWLEDGE message within the *Assigned RAB Parameter Values IE*.
+
+- If *d-RNTI for No IuCS UP* IE is contained in the RELOCATION REQUEST message, the target RNC shall use this information to configure the resource for the UE over Iur during the relocation.
+
+If the *Relocation Type* IE is set to "UE not involved in relocation of SRNS":
+
+- The target RNC shall not accept a requested RAB if the RAB did not exist in the source RNC before the relocation.
+- The target RNC may accept a RAB only if the radio bearer(s) for the RAB either exist(s) already and can be used for the RAB by the target RNC, or do(es) not exist before the relocation but can be established in order to support the RAB in the target RNC.
+- If existing radio bearers are not related to any RAB that is accepted by the target RNC, the radio bearers shall be ignored during the relocation of SRNS and the radio bearers shall be released by the radio interface protocols after completion of relocation of SRNS.
+- If any alternative RAB parameter values have been used when allocating the resources, these RAB parameter values shall be included in the RELOCATION REQUEST ACKNOWLEDGE message within the *Assigned RAB Parameter Values* IE. It should be noted that the usage of alternative RAB parameter values is not applicable to the UTRAN initiated relocation of type "UE not involved in relocation of SRNS".
+
+If the *UE History Information* IE is included in the RELOCATION REQUEST message and the target RNC is configured to collect the information, the target RNC shall, if supported, collect information defined in the *UE History Information* IE.
+
+After all necessary resources for accepted RABs including the initialised Iu user plane, are successfully allocated, the target RNC shall send a RELOCATION REQUEST ACKNOWLEDGE message to the CN.
+
+For each RAB successfully setup the RNC shall include the following IEs:
+
+- *RAB ID*
+- *Transport Layer Address* (when no ALCAP has been used)
+- *Iu Transport Association* (when no ALCAP has been used)
+
+Two pairs of *Transport Layer Address* IE and *Iu Transport Association* IE may be included for RABs established towards the PS domain.
+
+For each RAB the RNC is not able to setup during the Relocation Resource Allocation procedure, the RNC shall include the *RAB ID* IE and the *Cause* IE within the *RABs Failed To Setup* IE. The resources associated with the RABs indicated as failed to set up shall not be released in the CN until the relocation is completed. This is in order to make a return to the old configuration possible in case of a failed or cancelled relocation.
+
+The RELOCATION REQUEST ACKNOWLEDGE message sent to the CN shall, if applicable and if not sent via the other CN domain, include the *Target RNC To Source RNC Transparent Container* IE. This container shall be transferred by the CN to the source RNC or the external relocation source while completing the Relocation Preparation procedure.
+
+If the target RNC supports cell load-based inter-system handover, then in the case of inter-system handover, the *New BSS to Old BSS Information* IE may be included in the RELOCATION REQUEST ACKNOWLEDGE message. This information shall include, if available, the current traffic load in the target cell assuming a successful completion of the handover in progress.
+
+In case of inter-system relocation, the RNC shall include the *Chosen Integrity Protection Algorithm* IE (*Chosen Encryption Algorithm* IE respectively) within the RELOCATION REQUEST ACKNOWLEDGE message, if, and only if the *Integrity Protection Information* IE (*Encryption Information* IE respectively) was included in the RELOCATION REQUEST message.
+
+In case of intra-system relocation, the RNC shall include the *Chosen Integrity Protection Algorithm* IE (*Chosen Encryption Algorithm* IE respectively) within the RELOCATION REQUEST ACKNOWLEDGE message, if, and only if the *Integrity Protection Key* IE (*Ciphering Key* IE respectively) was included within the *Source RNC-to-Target RNC transparent container* IE.
+
+If one or more of the RABs that the target RNC has decided to support can not be supported by the CN, then these failed RABs shall not be released towards the target RNC until the relocation is completed.
+
+If the *NAS Synchronisation Indicator* IE is contained in the RELOCATION REQUEST message, the target RNC shall pass it to the UE.
+
+If the *SNA Access Information* IE is contained in the RELOCATION REQUEST message, the target RNC shall store this information and use it to determine whether the UE has access to radio resources in the UTRAN. The target RNC shall consider that the UE is authorised to access only the PLMNs identified by the *PLMN identity* IE in the *SNA Access Information* IE. If the *Authorised SNAs* IE is included for a given PLMN (identified by the *PLMN identity* IE), then the target RNC shall consider that the access to radio resources for the concerned UE is restricted to the LAs contained in the SNAs identified by the *SNAC* IEs.
+
+If the *SNA Access Information* IE is not contained in the RELOCATION REQUEST message, the target RNC shall consider that no access restriction applies to the UE in the UTRAN.
+
+Transmission and reception of a RELOCATION REQUEST ACKNOWLEDGE message terminate the procedure in the UTRAN and in the CN respectively.
+
+Before reporting the successful outcome of the Relocation Resource allocation procedure, the RNC shall have executed the initialisation of the user plane mode as requested by the CN in the *User Plane Mode* IE. If the RNC can not initialise the requested user plane mode for any of the user plane mode versions in the *UP Mode Versions* IE according to the rules for initialisation of the respective user plane mode versions, as described in TS 25.415 [6], the RAB Relocation shall fail with the cause value "RNC unable to establish all RFCs".
+
+If the *Selected PLMN identity* IE is contained in the RELOCATION REQUEST message, the target RNC shall use this information to send it to the UE.
+
+If the *UE Aggregate Maximum Bit Rate* IE is included in the RELOCATION REQUEST message, the UTRAN shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non-GBR traffic for this UE.
+
+In case SIPTO at Iu-PS functionality is supported by the UTRAN, the following applies in addition for the successful operation of the Relocation Resource Allocation procedure:
+
+- If the *MSISDN* IE is present in the RELOCATION REQUEST message, then the UTRAN may offload the RAB(s) where the *Offload RAB Parameters* IE is present in the *RABs To Be Setup Item IEs* IE. The *Access Point Name* IE and the *Charging Characteristics* IE within the *Offload RAB Parameters* IE and the *MSISDN* IE may only be used for the SIPTO at Iu-PS function and according to the description in TS 23.060 [21].
+
+#### **Interactions with Uplink Information Exchange procedure:**
+
+In case of UTRAN to UTRAN CS only relocation, if the RELOCATION REQUEST message includes the *MBMS Linking Information* IE in the *Source RNC To Target RNC Transparent Container* IE, the RNC shall, if supported, initiate the Uplink Information Exchange procedure to retrieve the Multicast Service list for the UE, create relevant MBMS Service Context, store this information and perform the relevant UE linking as defined in TS 25.346 [42].
+
+### **8.7.2.1 Successful Operation for GERAN Iu-mode**
+
+The relocation between UTRAN and GERAN Iu-mode shall be considered in the Relocation Resource Allocation procedure as intra-system relocation from RANAP point of view.
+
+For GERAN Iu-mode and to support Relocation towards a GERAN BSC in Iu mode the following shall apply in addition for the successful operation of the Relocation Resource Allocation procedure:
+
+- In case of GERAN Iu-mode, for RAB requested to be relocated from the the CS domain, the RELOCATION REQUEST message may contain the *GERAN BSC Container* IE in order to provide GERAN specific information to the target BSC (see TS 43.051 [27]).
+
+### 8.7.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant CN
+ participant Target RNC
+ Note left of Target RNC:
+ Target RNC->>CN: RELOCATION REQUEST
+ Note right of CN:
+ CN-->>Target RNC: RELOCATION FAILURE
+
+```
+
+Sequence diagram showing an unsuccessful relocation operation between a Target RNC and a CN. The Target RNC sends a RELOCATION REQUEST to the CN, and the CN responds with a RELOCATION FAILURE message.
+
+**Figure 8: Relocation Resource Allocation procedure: Unsuccessful operation.**
+
+If the target RNC can not even partially accept the relocation of SRNS or a failure occurs during the Relocation Resource Allocation procedure in the target RNC, the target RNC shall send a RELOCATION FAILURE message to the CN. The RELOCATION FAILURE message shall contain the *Cause* IE with an appropriate value.
+
+If the target RNC cannot support any of the integrity protection (ciphering respectively) alternatives provided in the *Integrity Protection Information* IE or *Encryption Information* IE, it shall return a RELOCATION FAILURE message with the cause "Requested Ciphering and/or Integrity Protection algorithms not supported".
+
+If the target RNC cannot support the relocation due to PUESBINE feature, it shall return a RELOCATION FAILURE message with the cause "Incoming Relocation Not Supported Due To PUESBINE Feature".
+
+If the target RNC does not receive the *CSG Membership Status* IE but does receive the *CSG Id* IE in the RELOCATION REQUEST message and the *CSG Id* IE is not valid, it shall send the RELOCATION FAILURE message to the CN with an appropriate cause value.
+
+If the *CSG Id* IE is not received in the RELOCATION REQUEST message and the access control for the relocation to a CSG cell is unsuccessful and if none of the RABs has some particular ARP values (see TS 23.060 [21]), the target RNC shall return a RELOCATION FAILURE message with an appropriate cause value, e.g. "Relocation Target not allowed".
+
+Transmission and reception of a RELOCATION FAILURE message terminate the procedure in the UTRAN and in the CN respectively.
+
+When the CN receives a RELOCATION FAILURE message from the target RNC, it shall stop timer $T_{RELOCALloc}$ and shall assume possibly allocated resources within the target RNC completely released.
+
+In case of inter-system handover, and if the target RNC supports cell load-based inter-system handover, then
+
+- the *NewBSS to Old BSS Information* IE may be included in the RELOCATION FAILURE message. This information shall include, if available, the current traffic load in the target cell.
+- the RELOCATION FAILURE message shall contain the *Cause* IE with an appropriate value, e.g. "No Radio Resources Available in Target Cell" or "Traffic Load In The Target Cell Higher Than In The Source Cell".
+- If the *Cause* IE received in the RELOCATION REQUEST message contains the value "Reduce Load in Serving Cell" and the load in the target cell is greater than in the source cell then, if the target cell is not in a congested or blocked state, the RNC shall return a RELOCATION FAILURE message which may include the cause "Traffic Load In The Target Cell Higher Than In The Source Cell".
+- When the RNC returns a RELOCATION FAILURE message with the cause "Traffic Load In The Target Cell Higher Than In The Source Cell", it shall also include the *NewBSS to Old BSS Information* IE. This information shall include the current traffic load in the target cell.
+
+### 8.7.3.1 Unsuccessful Operation for GERAN Iu-mode
+
+For GERAN Iu-mode and to support Relocation towards a GERAN BSC in Iu mode the following shall apply in addition for the unsuccessful operation of the Relocation Resource Allocation procedure:
+
+- In case a Relocation to GERAN Iu-mode fails (only for CS), because the Target BSC cannot provide an appropriate RAB corresponding to the content of the *GERAN BSC Container* IE (if received), the Target BSC shall report the unsuccessful Relocation Resource Allocation by indicating the cause value "GERAN Iu-mode Failure" within the RELOCATION FAILURE message and shall include the *GERAN Classmark* IE.
+
+### 8.7.4 Abnormal Conditions
+
+If after reception of the RELOCATION REQUEST message, the target RNC receives another RELOCATION REQUEST message on the same Iu connection, then the target RNC shall discard the latter message and the original Relocation Resource Allocation procedure shall continue normally.
+
+If the target RNC receives a *Source RNC to Target RNC Transparent Container* IE containing *Chosen Integrity Protection (Encryption respectively) Algorithm* IE without *Integrity Protection (Ciphering respectively) Key* IE, it shall return a RELOCATION FAILURE message with the cause "Conflict with already existing Integrity protection and/or Ciphering information".
+
+#### Interactions with Iu Release procedure:
+
+If the CN decides to not continue the Relocation Resource Allocation procedure (e.g. due to $T_{RELOCalloc}$ expiry) before the Relocation Resource Allocation procedure is completed, the CN shall stop timer $T_{RELOCalloc}$ (if timer $T_{RELOCalloc}$ has not already expired) and the CN shall, if the Iu signalling connection has been established or later becomes established, initiate the Iu Release procedure towards the target RNC with an appropriate value for the *Cause* IE, e.g. "Relocation Cancelled".
+
+- NOTE: In case two CN domains are involved in the Relocation Resource Allocation procedure, the target RNC may check whether the content of the two *Source RNC to Target RNC Transparent Container* IEs or the two *SNA Access Information* IEs is the same. In case the target RNC receives two different *Source RNC to Target RNC Transparent Container* IEs or two different *SNA Access Information* IEs, the RNC behaviour is left implementation specific.
+
+### 8.7.5 Co-ordination of Two Iu Signalling Connections
+
+Co-ordination of two Iu signalling connections during Relocation Resource Allocation procedure shall be executed by the target RNC when the *Number of Iu Instances* IE received in the *Source RNC to Target RNC Transparent Container* IE in the RELOCATION REQUEST message indicates that two CN domains are involved in relocation of SRNS.
+
+When both the CS and PS user data *Chosen Encryption Algorithm* IE are received within the *Source RNC to Target RNC Transparent Container* IE and if these two received *Chosen Encryption Algorithm* IE are not the same, the target RNC shall fail the Relocation Resource Allocation procedure by sending back a RELOCATION FAILURE message.
+
+The integrity protection (ciphering respectively) alternatives provided in the *Integrity Protection Information* IE (*Encryption Information* IE respectively) of the RELOCATION REQUEST messages received from both CN domains shall have at least one common alternative, otherwise the Relocation Resource Allocation shall be failed by sending back a RELOCATION FAILURE message.
+
+If two CN domains are involved, the following actions shall be taken by the target RNC:
+
+- The target RNC shall utilise the *Permanent NAS UE Identity* IE, received explicitly from each CN domain within the RELOCATION REQUEST messages, to co-ordinate both Iu signalling connections.
+- The target RNC shall generate and send RELOCATION REQUEST ACKNOWLEDGE messages only after all expected RELOCATION REQUEST messages are received and analysed, except for the case where there is at least one of the RABs that has a particular ARP value (see TS 23.060 [21]).
+- In case the SRVCC operation is performed and the source system is E-UTRAN, the target RNC shall generate and send RELOCATION REQUEST ACKNOWLEDGE message to the CN in CS domain if the relocation of SRNS is accepted for the CS domain but not accepted for the PS domain.
+
+- If the relocation is to a target CSG cell where the UE is a non-member of the target CSG, and where there is at least one of the RABs that has a particular ARP value (see TS 23.060 [21]) in one domain, the target RNC shall accept those RABs with a particular ARP value (see TS 23.060 [21]) and fail the other RABs, and send RELOCATION REQUEST ACKNOWLEDGE messages without waiting for the RELOCATION REQUEST message in the other domain.
+- If the target RNC decides to send the *Target RNC to Source RNC Transparent Container* IE via the two CN domains, the target RNC shall ensure that the same *Target RNC to Source RNC Transparent Container* IE is included in RELOCATION REQUEST ACKNOWLEDGE messages transmitted via the two CN domains and related to the same relocation of SRNS.
+
+If the target RNC receives the *UESBI-Iu* IE on the Iu-CS but not on the Iu-PS interface (or vice versa), the RNC shall, if supported, use the *UESBI-Iu* IE for both domains.
+
+## 8.8 Relocation Detect
+
+### 8.8.1 General
+
+The purpose of the Relocation Detect procedure is to indicate to the CN the detection by the RNC of an SRNS relocation execution. The procedure shall be co-ordinated over all Iu signalling connections existing for the UE. The procedure uses connection-oriented signalling.
+
+### 8.8.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant Target RNC
+ participant CN
+ Note left of Target RNC:
+ Target RNC->>CN: RELOCATION DETECT
+ Note right of CN:
+
+```
+
+The diagram illustrates the successful operation of the Relocation Detect procedure. It features two vertical lifelines: 'Target RNC' on the left and 'CN' on the right. A horizontal arrow labeled 'RELOCATION DETECT' points from the Target RNC to the CN. Both lifelines end in a thick horizontal bar at the bottom, representing the timeline of the procedure.
+
+Sequence diagram showing the successful operation of the Relocation Detect procedure. A Target RNC sends a RELOCATION DETECT message to a CN.
+
+**Figure 9: Relocation Detect procedure: Successful operation.**
+
+The target RNC shall send a RELOCATION DETECT message to the CN when a relocation execution trigger is received.
+
+If the type of relocation of SRNS is "UE involved in relocation of SRNS", the relocation execution trigger may be received either from the Uu interface or as an implementation option from the Iur interface. If the type of relocation of SRNS is "UE not involved in relocation of SRNS", the relocation execution trigger is received from the Iur interface.
+
+When the RELOCATION DETECT message is sent, the target RNC shall start SRNC operation.
+
+Upon reception of the RELOCATION DETECT message, the CN may switch the user plane from the source RNC to the target RNC.
+
+### 8.8.3 Abnormal Conditions
+
+#### Interactions with Relocation Complete procedure:
+
+If the RELOCATION COMPLETE message is received by the CN before the reception of the RELOCATION DETECT message, the CN shall handle the RELOCATION COMPLETE message normally.
+
+### 8.8.4 Co-ordination of Two Iu Signalling Connections
+
+When the Relocation Detect procedure is to be initiated by the target RNC, the target RNC shall initiate the Relocation Detect procedure on all Iu signalling connections existing for the UE between the target RNC and the CN.
+
+## 8.9 Relocation Complete
+
+### 8.9.1 General
+
+The purpose of the Relocation Complete procedure is to indicate to the CN the completion by the target RNC of the relocation of SRNS. The procedure shall be co-ordinated over all Iu signalling connections existing for the UE. The procedure uses connection-oriented signalling.
+
+### 8.9.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant Target RNC
+ participant CN
+ Target RNC->>CN: RELOCATION COMPLETE
+
+```
+
+The diagram shows two entities, 'Target RNC' and 'CN', each in a box. Below each box is a vertical line representing a timeline. A horizontal arrow labeled 'RELOCATION COMPLETE' points from the Target RNC's timeline to the CN's timeline.
+
+Sequence diagram showing the Target RNC sending a RELOCATION COMPLETE message to the CN.
+
+**Figure 10: Relocation Complete procedure. Successful operation.**
+
+When the new SRNC-ID and serving RNC Radio Network Temporary Identity are successfully exchanged with the UE by the radio protocols, the target RNC shall initiate the Relocation Complete procedure by sending a RELOCATION COMPLETE message to the CN. Upon reception of the RELOCATION COMPLETE message, the CN should stop the $T_{\text{RELOCcomplete}}$ timer.
+
+If the *Higher bitrates than 16 Mbps flag* IE is included in the RELOCATION COMPLETE message then the CN shall, if supported, use the IE as described in TS 23.060 [21].
+
+If the *Tunnel Information for BBF* IE is received in the RELOCATION COMPLETE message, the CN shall, if supported, use the IE as described in TS 23.139 [65].
+
+### 8.9.3 Abnormal Conditions
+
+If the timer $T_{\text{RELOCcomplete}}$ expires:
+
+- The CN should initiate release of Iu connections towards the source and the target RNC by initiating the Iu Release procedure with an appropriate value for the *Cause* IE, e.g. " $T_{\text{RELOCcomplete}}$ expiry".
+
+#### Interactions with the Relocation Detect procedure:
+
+If the RELOCATION DETECT message is not received by the CN before reception of the RELOCATION COMPLETE message, the CN shall handle the RELOCATION COMPLETE message normally.
+
+### 8.9.4 Co-ordination of Two Iu Signalling Connections
+
+When the Relocation Complete procedure is to be initiated by the target RNC, the target RNC shall initiate the Relocation Complete procedure on all Iu signalling connections existing for the UE between the target RNC and the CN.
+
+## 8.10 Relocation Cancel
+
+### 8.10.1 General
+
+The purpose of the Relocation Cancel procedure is to enable a source RNC to cancel an ongoing relocation of SRNS. The Relocation Cancel procedure may be initiated by the source RNC during and after the Relocation Preparation procedure if either of the following conditions is fulfilled:
+
+1. The source RNC has not yet initiated the execution of relocation of SRNS, neither via the Iur interface nor via the Uu interface.
+2. After having initiated the execution of relocation of SRNS, the UE has returned to the source RNC by transmitting an RRC message which indicates that the UE considers the source RNC as its serving RNC.
+
+The procedure shall be co-ordinated in all Iu signalling connections for which the Relocation Preparation procedure has been initiated. The procedure uses connection oriented signalling.
+
+## 8.10.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant Source RNC
+ participant CN
+ Note left of Source RNC:
+ Source RNC->>CN: RELOCATION CANCEL
+ Note right of CN:
+ CN-->>Source RNC: RELOCATION CANCEL ACKNOWLEDGE
+ Note left of Source RNC:
+ Note right of CN:
+```
+
+Sequence diagram of the Relocation Cancel procedure. It shows two participants: Source RNC and CN. The Source RNC sends a RELOCATION CANCEL message to the CN. The CN responds with a RELOCATION CANCEL ACKNOWLEDGE message back to the Source RNC.
+
+**Figure 11: Relocation Cancel procedure. Successful operation.**
+
+The RNC initiates the procedure by sending a RELOCATION CANCEL message to the CN. This message shall indicate the reason for cancelling the relocation of SRNS by the appropriate value of the *Cause* IE. Upon reception of a RELOCATION CANCEL message, the CN shall send a RELOCATION CANCEL ACKNOWLEDGE message to the source RNC.
+
+Transmission and reception of a RELOCATION CANCEL ACKNOWLEDGE message terminate the procedure in the CN and in the source RNC respectively. After this, the source RNC does not have a prepared relocation for that Iu signalling connection.
+
+### Interactions with Relocation Preparation procedure:
+
+Upon reception of a RELOCATION CANCEL message from the source RNC, the CN shall locally terminate the possibly ongoing Relocation Preparation procedure towards that RNC and abandon the relocation of SRNS.
+
+If the source RNC receives a RELOCATION COMMAND message from the CN after the Relocation Cancel procedure is initiated, the source RNC shall ignore the received RELOCATION COMMAND message.
+
+If the source RNC receives a RELOCATION PREPARATION FAILURE message from the CN after the Relocation Cancel procedure is initiated, then the source RNC shall terminate the ongoing Relocation Cancel procedure.
+
+## 8.10.3 Unsuccessful Operation
+
+Not applicable.
+
+## 8.10.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.10.5 Co-ordination of Two Iu Signalling Connections
+
+If the Relocation Cancel procedure is to be initiated due to other reasons than reception of a RELOCATION PREPARATION FAILURE message, the Relocation Cancel procedure shall be initiated on all Iu signalling connections existing for the UE in which the Relocation Preparation procedure has not terminated unsuccessfully.
+
+# 8.11 SRNS Context Transfer
+
+## 8.11.1 General
+
+The purpose of the SRNS Context Transfer procedure is to trigger the transfer of SRNS contexts from the source RNC to the CN (PS domain) in case of intersystem change or in some further cases described in TS 23.060 [21]. The procedure uses connection oriented signalling.
+
+## 8.11.2 Successful Operation
+
+
+
+Sequence diagram showing the SRNS Context Transfer procedure. The CN (Core Network) sends an SRNS CONTEXT REQUEST message to the RNC (Radio Network Controller). The RNC responds with an SRNS CONTEXT RESPONSE message. The diagram shows two vertical lifelines for RNC and CN. The CN sends a message labeled 'SRNS CONTEXT REQUEST' to the RNC. The RNC then sends a message labeled 'SRNS CONTEXT RESPONSE' back to the CN. Both lifelines have a thick horizontal bar at the bottom, indicating active periods.
+
+**Figure 12: SRNS Context Transfer procedure. Successful operation.**
+
+The CN initiates the procedure by sending an SRNS CONTEXT REQUEST message to the source RNC. The SRNS CONTEXT REQUEST message shall include the list of RABs whose contexts should be transferred, and may include the *RAT Type* IE, when available to indicate the RAT from which the context request originates.
+
+The source RNC shall respond to the CN with an SRNS CONTEXT RESPONSE message containing all the referenced RABs, including both successful and unsuccessful RABs transfers. For each RAB whose transfer is successful, the following context information elements shall be included:
+
+- *RAB ID* IE;
+- always when available, the sequence number for the next downlink GTP-PDU to be sent to the UE, i.e. the *DL GTP-PDU Sequence Number* IE;
+- always when available, the sequence number for the next uplink GTP-PDU to be tunnelled to the GGSN, i.e. the *UL GTP-PDU Sequence Number* IE;
+- always when available, the radio interface sequence number (PDCP) TS 25.323 [17] of the next downlink N-PDU (PDCP SDU) that would have been sent to the UE by a source system, i.e. the *DL N-PDU Sequence Number* IE;
+- always when available, the radio interface sequence number (PDCP) TS 25.323 [17] of the next uplink N-PDU (PDCP SDU) that would have been expected from the UE by a source system, i.e. the *UL N-PDU Sequence Number* IE.
+
+Transmission and reception of the SRNS CONTEXT RESPONSE message terminate the procedure in the UTRAN and in the CN respectively.
+
+## 8.11.3 Unsuccessful Operation
+
+For each RAB for which the UTRAN is not able to transfer the RAB context, e.g. if the RAB ID is unknown to the RNC, the RAB ID is included in the SRNS CONTEXT RESPONSE message together with a *Cause* IE, e.g. "Invalid RAB ID".
+
+## 8.11.4 Abnormal Conditions
+
+Not applicable.
+
+# 8.12 SRNS Data Forwarding Initiation
+
+## 8.12.1 General
+
+The purpose of the SRNS Data Forwarding procedure is to trigger the transfer of N-PDUs from the RNC to the CN (PS domain) in case of intersystem change or in some further cases described in TS 23.060 [21]. The procedure uses connection oriented signalling.
+
+## 8.12.2 Successful Operation
+
+
+
+Diagram of SRNS Data Forwarding Initiation procedure. A CN (Core Network) box is on the right, and an RNC (Radio Network Controller) box is on the left. A horizontal arrow labeled 'SRNS DATA FORWARD COMMAND' points from the CN box to the RNC box. Both boxes have vertical lines extending downwards to a common horizontal baseline.
+
+**Figure 13: SRNS Data Forwarding Initiation procedure. Successful operation.**
+
+The CN initiates the procedure by sending an SRNS DATA FORWARD COMMAND message to the UTRAN. The SRNS DATA FORWARD COMMAND message includes the list of RABs towards the PS domain whose data should be forwarded, and the necessary information for establishing a GTP tunnel to be used for data forwarding. For each indicated RAB, the list shall include the *RAB ID* IE, the *Transport Layer Address* IE and the *Iu Transport Association* IE.
+
+Upon reception of the SRNS DATA FORWARD COMMAND message the RNC starts the timer $T_{DATAfwd}$ .
+
+## 8.12.3 Abnormal Conditions
+
+Not applicable.
+
+# 8.13 SRNS Context Forwarding from Source RNC to CN
+
+## 8.13.1 General
+
+The purpose of this procedure is to transfer SRNS contexts from the source RNC to the CN (PS domain) in case of handover via the CN. The procedure uses connection oriented signalling. SRNS contexts are sent for each concerned RAB among those that are supported by the target system, and for which at least either GTP-PDU or PDCP sequence numbering is available. The SRNS contexts contain the sequence numbers of the next GTP-PDUs to be transmitted in the uplink and downlink directions, if available, and the next PDCP sequence numbers that would have been used to send and receive data from the UE, if available. The Source RNC PDCP context info shall be sent if available.
+
+## 8.13.2 Successful Operation
+
+
+
+Diagram of SRNS Context forwarding from source RNC to CN. A Source RNC box is on the left, and a CN (Core Network) box is on the right. A horizontal arrow labeled 'FORWARD SRNS CONTEXT' points from the Source RNC box to the CN box. Both boxes have vertical lines extending downwards to a common horizontal baseline.
+
+**Figure 14: SRNS Context forwarding from source RNC to CN. Successful operation.**
+
+The source RNC initialises the procedure by sending a FORWARD SRNS CONTEXT message to the CN. The FORWARD SRNS CONTEXT message contains the RAB Context information for each referenced RAB. For each RAB the following information shall be included:
+
+- *RAB ID* IE;
+- always when available, the sequence number for the next downlink GTP-PDU to be sent to the UE, i.e. the *DL GTP-PDU Sequence Number* IE;
+- always when available, the sequence number for the next uplink GTP-PDU to be tunnelled to the GGSN, i.e. the *UL GTP-PDU Sequence Number* IE;
+
+- always when available, the radio interface sequence number (PDCP) TS 25.323 [17] of the next uplink N-PDU (PDCP SDU) that would have been expected from the UE by a source system i.e. the *UL N-PDU Sequence Number* IE;
+- always when available, the radio interface sequence number (PDCP) TS 25.323 [17] of the next downlink N-PDU (PDCP SDU) that would have been sent to the UE by a source system i.e. the *DL N-PDU Sequence Number* IE.
+
+### 8.13.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.14 SRNS Context Forwarding to Target RNC from CN
+
+### 8.14.1 General
+
+The purpose of this procedure is to transfer SRNS contexts from the CN (PS domain) to the target RNC in case of handover via the CN. The procedure uses connection oriented signalling. SRNS contexts are sent for each referenced RAB, for which at least either GTP-PDU or PDCP sequence numbering is available. The SRNS contexts contain the sequence numbers of the next GTP-PDUs to be transmitted in the uplink and downlink directions, if available, and the next PDCP sequence numbers that would have been used to send and receive data from the UE, if available. The source RNC PDCP context info shall be sent if available.
+
+### 8.14.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant Target RNC
+ Note right of CN: FORWARD SRNS CONTEXT
+ CN->>Target RNC: FORWARD SRNS CONTEXT
+ Note left of Target RNC: Received FORWARD SRNS CONTEXT
+```
+
+Diagram showing the successful operation of SRNS Context forwarding from the CN to the Target RNC. The CN sends a FORWARD SRNS CONTEXT message to the Target RNC.
+
+**Figure 15: SRNS Context forwarding to target RNC from CN. Successful operation.**
+
+The CN initialises the procedure by sending FORWARD SRNS CONTEXT message to the target RNC. The FORWARD SRNS CONTEXT message contains the RAB Context information for each referenced RAB. For each RAB the following information shall be included:
+
+- *RAB ID* IE;
+- always when available, the sequence number for the next downlink GTP-PDU to be sent to the UE, i.e. the *DL GTP-PDU Sequence Number* IE;
+- always when available, the sequence number for the next uplink GTP-PDU to be tunnelled to the GGSN, i.e. the *UL GTP-PDU Sequence Number* IE;
+- always when available, the radio interface sequence number (PDCP) TS 25.323 [17] of the next uplink N-PDU (PDCP SDU) that would have been expected from the UE by a source system i.e. the *UL N-PDU Sequence Number* IE;
+- always when available, the radio interface sequence number (PDCP) TS 25.323 [17] of the next downlink N-PDU (PDCP SDU) that would have been sent to the UE by a source system i.e. the *DL N-PDU Sequence Number* IE.
+
+### 8.14.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.15 Paging
+
+### 8.15.1 General
+
+The purpose of the Paging procedure is to enable the CN to request the UTRAN to contact that UE. The procedure uses connectionless signalling.
+
+### 8.15.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ CN->>RNC: PAGING
+
+```
+
+Sequence diagram showing the CN sending a PAGING message to the RNC.
+
+**Figure 16: Paging procedure. Successful operation.**
+
+The CN initiates the procedure by sending a PAGING message. The PAGING message shall contain the following IEs:
+
+- *CN Domain Indicator*
+- *Permanent NAS UE Identity*
+- *DRX Cycle Length Coefficient* (if available)
+
+The PAGING message may contain following IEs:
+
+- *Temporary UE Identity*
+- *Paging Area*
+- *Paging Cause*
+- *Non Searching Indication*
+- *Global CN-ID*
+- *CSG Id List*
+
+The *CN Domain Indicator* IE shall be used by the RNC to identify from which CN domain the paging request originates.
+
+The *Permanent NAS UE Identity* IE (i.e. IMSI) shall be used by the UTRAN paging co-ordination function to check if a signalling connection towards the other CN domain already exists for this UE. In that case, the radio interface paging message shall be sent via that connection instead of using the paging broadcast channel.
+
+The *Temporary UE Identity* IE (e.g. TMSI) is the temporary identity of the user (allocated by that CN Domain) which can be used in a radio interface paging message. If the *Temporary UE Identity* IE is not included in the PAGING message, the RNC shall use the *Permanent NAS UE Identity* instead – if no signalling connection exists.
+
+If NNSF is active, and the *Temporary UE Identity* IE is not included in the PAGING message, the PAGING message shall include the *Global CN-ID* IE and, in case this PAGING message is originated from the CS domain, the RNC may start the $T_{NNSF}$ timer and store the *Permanent NAS UE Identity* IE along with the related *Global CN-ID* IE until the $T_{NNSF}$ timer has expired.
+
+The *Paging Area* IE shall be used by the RNC to identify the area in which the radio interface paging message shall be broadcast in case no signalling connection, as described above, already exists for the UE. If the *Paging Area* IE is not included in the PAGING message, the whole RNC area shall be used as Paging Area – if no signalling connection exists for that UE.
+
+The *Paging Cause* IE shall indicate to the RNC the reason for sending the PAGING message. The paging cause is transferred transparently to the UE.
+
+The *Non Searching Indication* IE shall, if present, be used by the RNC to decide whether the UTRAN paging co-ordination function needs to be activated or not. In the absence of this IE, UTRAN paging co-ordination shall be performed.
+
+The *DRX Cycle Length Coefficient* IE may be included in the PAGING message, and if present, the UTRAN shall, when applicable, use it for calculating the paging occasions for the UE.
+
+A list of CSG IDs may be included in the PAGING message. If included, the UTRAN may use the list of CSG IDs to avoid paging the UE at CSG cells whose CSG ID does not appear in the list.
+
+It should be noted that each PAGING message on the Iu interface relates to only one UE and therefore the RNC has to pack the pages into the relevant radio interface paging message.
+
+The core network is responsible for the paging repetition over the Iu interface.
+
+### 8.15.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.16 Common ID
+
+### 8.16.1 General
+
+The purpose of the Common ID procedure is to inform the RNC about the permanent NAS UE Identity (i.e. IMSI) of a user. This is used by the RNC e.g. to create a reference between the permanent NAS UE identity of the user and the RRC connection of that user for UTRAN paging co-ordination. The procedure may also be used to provide the *SNA Access Information* IE to the RNC or to provide the *Management Based MDT Allowed* IE to the RNC or to provide the *Management Based MDT PLMN List* IE to the RNC.
+
+The procedure uses connection oriented signalling.
+
+### 8.16.2 Successful Operation
+
+
+
+Diagram illustrating the Common ID procedure. A CN (Core Network) box is on the right, and an RNC (Radio Network Controller) box is on the left. A horizontal arrow labeled 'COMMON ID' points from the CN box to the RNC box. Both boxes have vertical lines extending downwards to a thick horizontal bar representing the ground or a common reference line.
+
+**Figure 17: Common ID procedure. Successful operation.**
+
+After having established an Iu signalling connection, and if the Permanent NAS UE identity (i.e. IMSI) is available, the CN shall send to the RNC a COMMON ID message containing the *Permanent NAS UE Identity* IE and optionally the *SNA Access Information* IE. The COMMON ID message may also include the *UESBI-Iu* IE. The RNC shall associate the permanent identity to the RRC Connection of that user and shall save it for the duration of the RRC connection.
+
+The RNC shall, if supported, use the *UESBI-Iu* IE when received in the COMMON ID message. If *UESBI-Iu* IE contains an IMEISV the RNC may use this information to determine the characteristics of the UE for subsequent handling.
+
+If the *CSG Membership Status* IE is included in the COMMON ID message the RAN shall, if supported, take the following actions:
+
+- If the cell that serves the UE is a Hybrid cell, the RNC shall store the value contained in the *CSG Membership Status* IE and replace any previously stored membership status value by this new one. The RNC may use such information to perform differentiated treatment for member and non-member UEs.
+- If the cell that serves the UE is a CSG cell, and the *CSG Membership Status* IE is set to “non-member”, the RNC should initiate actions to ensure that the UE is no longer served by the CSG cell as defined in TS 25.467 [55].
+
+If the *SNA Access Information* IE is contained in the COMMON ID message, the RNC shall store this information and use it to determine whether the UE has access to radio resources in the UTRAN. The RNC shall consider that the UE is authorised to access only the PLMNs identified by the *PLMN identity* IEs in the *SNA Access Information* IE. If the *Authorised SNAs* IE is included for a given PLMN (identified by the *PLMN identity* IE), then the RNC shall consider that the access to radio resources for the concerned UE is restricted to the LAs contained in the SNAs identified by the *SNAC* IEs.
+
+In case of GWCN configuration for a network sharing non-supporting UE, the COMMON ID message shall include, if available, the *Selected PLMN identity* IE. If received, the RNC shall store this information.
+
+In case SRVCC functionality is supported by the UE and CN, the CN shall include *SRVCC Operation Possible* IE in COMMON ID message.
+
+In case rSRVCC functionality is supported by the UE and CN, the CN shall include *rSRVCC Operation Possible* IE in COMMON ID message.
+
+If the *Management Based MDT Allowed* IE is included in the the COMMON ID message, the RNC shall use it, if supported, together with information in the *Management Based MDT PLMN List* IE, if available, to allow subsequent selection of the UE for management based MDT as defined in TS 32.422 [38].
+
+Upon receipt of the COMMON ID message the RNC shall
+
+- store the Subscriber Profile ID for RAT/Frequency priority IE and use it as defined in TS 36.300 [52].
+
+Upon receipt of the COMMON ID message the RNC may
+
+- store the *Last E-UTRAN PLMN Identity* IE and use it as defined in TS 23.272 [66].
+
+## 8.16.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.17 CN Invoke Trace
+
+### 8.17.1 General
+
+When used for signalling based activation, the purpose of the CN Invoke Trace procedure is to inform the RNC that it should begin a trace session with the parameters indicated by the CN and related to the UE, the Iu connection is used for.
+
+When used for management based activation, the purpose of the CN Invoke Trace procedure is to provide the RNC with the equipment identity of the UE for which the RNC should begin a trace recording session.
+
+The procedure uses connection oriented signalling.
+
+### 8.17.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN INVOKE TRACE
+ CN->>RNC: CN INVOKE TRACE
+ Note right of RNC:
+```
+
+The diagram illustrates the successful operation of the CN Invoke Trace procedure. It features two vertical lifelines: 'RNC' on the left and 'CN' on the right. A horizontal arrow labeled 'CN INVOKE TRACE' originates from the CN lifeline and points to the RNC lifeline. Both lifelines terminate at a thick horizontal bar at the bottom, representing the end of the sequence.
+
+Sequence diagram showing the CN Invoke Trace procedure. The CN sends a CN INVOKE TRACE message to the RNC.
+
+**Figure 18: CN Invoke Trace procedure. Successful operation.**
+
+The CN Invoke Trace procedure is invoked by the CN by sending a CN INVOKE TRACE message to the RNC as defined in TS 32.422 [38].
+
+The CN INVOKE TRACE message shall include the following IEs:
+
+- The *Trace Reference* IE, which uniquely identifies the trace session it refers to.
+
+- The *UE Identity* IE, which indicates the UE to which this trace session pertains.
+- The *Trace Propagation Parameters* IE, only in case of a signalling based activation.
+
+If present, the *Trace Propagation Parameters* IE shall include the following IEs:
+
+- The *Trace Recording Session Reference* IE, which is allocated by the CN.
+- The *Trace Depth* IE, which defines how detailed information should be recorded for this trace session in the RNC.
+
+The *Trace Propagation Parameters* IE may also include the *List Of Interfaces To Trace* IE, which defines which interfaces should be traced in the RNC. If the *List Of Interfaces To Trace* IE is not included, the RNC should trace all the following interfaces, if available: Iu-CS, Iu-PS, Uu, Iur and Iub.
+
+Upon receiving the CN INVOKE TRACE message, which includes the *Trace Propagation Parameters* IE, the RNC should begin a trace recording session according to the parameters indicated in the CN INVOKE TRACE message. If the RNC does not support the requested value "Minimum" or "Medium" of the *Trace Depth* IE, the RNC should begin a trace recording session with maximum trace depth.
+
+Upon receiving the CN INVOKE TRACE message, which does not include the *Trace Propagation Parameters* IE, the RNC should begin a trace recording session according to the parameters configured in the RNC for the indicated equipment identity in the CN INVOKE TRACE message.
+
+The RNC may not start a trace recording session if there are insufficient resources available within the RNC.
+
+The *Trace Reference* IE, *UE identity* IE and, if the *Trace Propagation Parameters* IE is present, the *Trace Recording Session Reference* IE are used to tag the trace record to allow simpler construction of the total record by the entity which combines trace records.
+
+If the *MDT Configuration* IE is included in the CN INVOKE TRACE message and includes the *MDT Activation* IE set to "Immediate MDT and Trace" then the RNC shall, if supported, initiate the requested trace function and MDT function as described in TS 32.422 [38].
+
+If the *MDT Configuration* IE is included in the CN INVOKE TRACE message and includes the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", then the RNC shall, if supported, initiate the requested MDT function as described in TS 32.422 [38] and shall ignore the *List of Interfaces to Trace* IE and the *Trace Depth* IE.
+
+If *Trace Collection Entity IP Address* IE is included and if the *MDT Configuration* IE is also included then the RNC shall, if supported, store the Trace Collection Entity IP address and use it when transferring Trace records, otherwise if *MDT Configuration* IE is not included, the RNC may use the Trace Collection Entity IP address when transferring trace records.
+
+If the *MDT Configuration* IE is included in the CN INVOKE TRACE message and includes the *Signalling based MDT PLMN List* IE, then the RNC may used it to propagate the trace function as described in TS 37.320 [64].
+
+#### **Interaction with Relocation and Enhanced Relocation:**
+
+In case of signalling based activation, the order to perform tracing is lost in UTRAN at successful Relocation of SRNS. If the tracing shall continue also after the relocation has been performed, the CN Invoke Trace procedure shall thus be re-initiated from the CN towards the future SRNC after the Relocation Resource Allocation or the Enhanced Relocation procedure has been executed successfully.
+
+### **8.17.2.1 Successful Operation for GERAN Iu mode**
+
+The CN INVOKE TRACE message shall include the *Trace Type* IE to indicate the events and parameters to be recorded.
+
+The message shall include a *Trace Reference* IE which is allocated by the entity which triggered the trace.
+
+The message may include the *OMC ID* IE, which if present, indicates the OMC to which the record is destined.
+
+The message may include the *UE Identity* IE, which if present, indicates the UE to which this record pertains to.
+
+The message may include the *Trigger ID* IE, which if present, indicates the entity which triggered the trace.
+
+The *Trace Reference* and *Trigger ID* IEs are used to tag the trace record to allow simpler construction of the total record by the entity which combines trace records.
+
+### 8.17.3 Abnormal Conditions
+
+If the *MDT Configuration* IE is included in the CN INVOKE TRACE message and the *Trace Collection Entity IP Address* IE is not included, the RNC shall ignore the MDT Configuration.
+
+#### 8.17.3.1 Abnormal Conditions for GERAN Iu mode
+
+Not applicable.
+
+## 8.18 Security Mode Control
+
+### 8.18.1 General
+
+The purpose of the Security Mode Control procedure is to pass ciphering and integrity mode information to the UTRAN. The UTRAN uses this information to select and load the encryption device for user and signalling data with the appropriate parameters, and also to store the appropriate parameters for the integrity algorithm. The procedure uses connection oriented signalling.
+
+### 8.18.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: SECURITY MODE COMMAND
+ Note right of RNC: RNC selects algorithms
+ RNC->>CN: SECURITY MODE COMPLETE
+```
+
+Sequence diagram of the Security Mode Control procedure. It shows two vertical lifelines: RNC on the left and CN on the right. The CN sends a 'SECURITY MODE COMMAND' message to the RNC. The RNC then sends a 'SECURITY MODE COMPLETE' message back to the CN. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 19: Security Mode Control procedure. Successful operation.**
+
+The CN initiates the procedure by sending a SECURITY MODE COMMAND message. The message may contain the *Encryption Information* IE and shall contain the *Integrity Protection Information* IE, specifying, in preferred order with the most preferred first in the list, which ciphering, if any, and integrity protection algorithms may be used by the UTRAN.
+
+The *Permitted Encryption Algorithms* IE within the *Encryption Information* IE may contain "no encryption" within an element of its list in order to allow the RNC not to cipher the respective connection. This can be done either by not starting ciphering or by using the UEA0 algorithm. In the absence of the *Encryption Information* group IE in SECURITY MODE COMMAND message, the RNC shall not start ciphering.
+
+Upon reception of the SECURITY MODE COMMAND message, the UTRAN shall internally select appropriate algorithms, taking into account the UE/UTRAN capabilities. If a signalling connection already exists towards the other core network domain and integrity has been started, the same ciphering and integrity alternatives as being used for that core network domain shall be selected. If a signalling connection already exists towards the other core network domain and the Security Mode Control procedure is ongoing on that core network domain, the same ciphering and integrity alternative shall be selected for the two domains. This means in particular for encryption that if "no encryption" or no *Encryption Information* IE has been received from the first core network domain and integrity has been started but ciphering has not been started, ciphering shall also not be started for the second core network domain. The UTRAN shall then trigger the execution of the corresponding radio interface procedure and, if applicable, start/restart the encryption device and also start/modify the integrity protection.
+
+The CN may send a SECURITY MODE COMMAND message towards the RNC also when integrity protection and possibly ciphering has already been started for an existing signalling connection towards that core network domain. This may be used to activate new integrity protection and ciphering keys. The included integrity protection and ciphering information shall then support (at least) the integrity protection alternative and the ciphering alternative presently being used and the *Key Status* IE shall have the value "New".
+
+When the execution of the radio interface procedure is successfully finished, the UTRAN shall return a SECURITY MODE COMPLETE message to the CN. This message shall include the *Chosen Integrity Protection Algorithm* IE and may include the *Chosen Encryption Algorithm* IE.
+
+The *Chosen Encryption Algorithm* IE shall be included in the SECURITY MODE COMPLETE message if, and only if the *Encryption Information* IE was included in the SECURITY MODE COMMAND message.
+
+The set of permitted algorithms specified in the SECURITY MODE COMMAND message shall remain applicable for subsequent RAB Assignments and Intra-UTRAN Relocations.
+
+In case of a UE with Radio Access Bearers towards both core networks, the user data towards CS shall always be ciphered with the ciphering key received from CS and the user data towards PS with the ciphering key received from PS. The signalling data shall always be ciphered with the last received ciphering key and integrity protected with the last received integrity protection key from any of the two CNs.
+
+### 8.18.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: SECURITY MODE COMMAND
+ CN->>RNC: SECURITY MODE COMMAND
+ Note right of RNC: SECURITY MODE REJECT
+ RNC->>CN: SECURITY MODE REJECT
+```
+
+Sequence diagram illustrating the Security Mode Control procedure. The diagram shows two vertical lifelines: RNC (left) and CN (right). A horizontal arrow labeled 'SECURITY MODE COMMAND' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'SECURITY MODE REJECT' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 20: Security Mode Control procedure. Unsuccessful operation.**
+
+If the UTRAN or the UE is unable to support the ciphering and/or integrity protection algorithms specified in the SECURITY MODE COMMAND message, then the UTRAN shall return to the CN a SECURITY MODE REJECT message with cause value "Requested Ciphering and/or Integrity Protection Algorithms not Supported". If the radio interface Security Mode Control procedure fails, a SECURITY MODE REJECT message shall be sent to the CN with cause value "Failure in the Radio Interface Procedure".
+
+### 8.18.4 Abnormal Conditions
+
+If, when establishing a signalling connection towards a second core network domain, the integrity has already been started by the first domain and the integrity protection and ciphering information specified in the SECURITY MODE COMMAND message does not support the integrity protection alternative and the ciphering alternative presently being used, a SECURITY MODE REJECT message shall be sent to the second core network domain with cause value "Conflict with already existing Integrity protection and/or Ciphering information".
+
+If, upon reception of a SECURITY MODE COMMAND message from a core network domain with an already existing signalling connection from that core network domain and for which integrity protection and possibly ciphering have already been started, the *Key Status* IE has the value "Old", a SECURITY MODE REJECT message shall be returned with cause value "Conflict with already existing Integrity protection and/or Ciphering information".
+
+If, upon reception of a SECURITY MODE COMMAND message from a core network domain with an already existing signalling connection and for which integrity protection and possibly ciphering have already been started, the included integrity protection and ciphering information does not support the integrity protection alternative and the ciphering
+
+alternative presently being used, a SECURITY MODE REJECT message shall be returned with cause value "Conflict with already existing Integrity protection and/or Ciphering information".
+
+## 8.19 Location Reporting Control
+
+### 8.19.1 General
+
+The purpose of the Location Reporting Control procedure is to allow the CN to request information on the location and optionally velocity of a given UE. The procedure uses connection oriented signalling.
+
+### 8.19.2 Successful Operation
+
+
+
+Diagram illustrating the Location Reporting Control procedure. A CN (Core Network) box is on the right, and an RNC (Radio Network Controller) box is on the left. A horizontal arrow labeled 'LOCATION REPORTING CONTROL' points from the CN box to the RNC box. Both boxes have vertical lines extending downwards to a common horizontal baseline.
+
+**Figure 21: Location Reporting Control procedure. Successful operation.**
+
+The CN initiates the procedure by sending a LOCATION REPORTING CONTROL message.
+
+The *Request Type* IE shall indicate to the serving RNC whether:
+
+- to report directly;
+- to stop a direct report;
+- to report periodically;
+- to stop periodic reporting;
+- to report upon change of Service area, or
+- to stop reporting at change of Service Area.
+
+If reporting upon change of Service Area is requested, the Serving RNC shall report whenever the UE moves between Service Areas. For this procedure, only Service Areas that are defined for the PS and CS domains shall be considered.
+
+The *Request Type* IE shall also indicate what type of location information the serving RNC shall report. The location information is either of the following types:
+
+- Service Area Identifier, or
+- Geographical area, including geographical coordinates with or without requested accuracy. If the *Vertical Accuracy Code* IE is included, the *Accuracy Code* IE in the *Request Type* IE shall be present. The *Accuracy Code* IE shall be understood as the horizontal accuracy code.
+
+A request for a direct report or for periodic reporting can be done in parallel with having an active request to report upon change of Service Area for the same UE. The request to report upon change of Service Area shall not be affected by this.
+
+Any of the *Vertical Accuracy Code* IE, *Response Time* IE, *Positioning Priority* IE, *Client Type* IE or *Periodic Location Info* IE shall be included according to the following rules:
+
+- Vertical Accuracy Code shall be included, if available, in connection with Geographical Area,
+- Response time shall be included, if available, in connection with request for start of direct reporting of Geographical Area,
+- Client type shall be included in connection with request for start of direct reporting of Geographical Area and, if available, in request for direct reporting of SAI or periodic reporting,
+
+- Positioning Priority shall be included, if available, in connection with request for start of direct reporting or in connection with request for start of reporting upon change of Service Area,
+- Periodic Location Info shall be included in connection with a request for start of periodic reporting of Geographical Area.
+
+When no *Positioning Priority* IE is included, the RNC shall consider the request as if "Normal Priority" value had been received.
+
+When no *Response Time* IE is included, the RNC shall consider the request as if "Delay Tolerant" value had been received.
+
+#### **Interaction with Relocation and Enhanced Relocation:**
+
+The order to perform location reporting at change of Service Area is lost in UTRAN at successful Relocation of SRNS. If the location reporting at change of Service Area shall continue also after the relocation has been performed, the Location Reporting Control procedure shall thus be re-initiated from the CN towards the future SRNC after the Relocation Resource Allocation procedure or the Enhanced Relocation procedure has been executed successfully.
+
+### 8.19.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.20 Location Report
+
+### 8.20.1 General
+
+The purpose of the Location Report procedure is to provide the UE's location and optionally velocity information to the CN. The procedure uses connection oriented signalling.
+
+### 8.20.2 Successful Operation
+
+
+
+Sequence diagram showing the successful operation of the Location Report procedure. It features two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow labeled 'LOCATION REPORT' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 22: Location Report procedure. Successful operation.**
+
+The serving RNC initiates the procedure by generating a LOCATION REPORT message. The LOCATION REPORT message may be used as a response to a LOCATION REPORTING CONTROL message. Also, when a user enters or leaves a classified zone set by O&M, e.g. a zone where a disaster has occurred, a LOCATION REPORT message including the Service Area of the UE in the *Area Identity* IE shall be sent to the CN. The *Cause* IE shall indicate the appropriate cause value to the CN, e.g. "User Restriction Start Indication" and "User Restriction End Indication". The CN shall react to the LOCATION REPORT message with CN vendor specific actions.
+
+For this procedure, only Service Areas that are defined for the PS and CS domains shall be considered.
+
+In case reporting at change of Service Area is requested by the CN, then the RNC shall issue a LOCATION REPORT message:
+
+- whenever the information given in the previous LOCATION REPORT message or INITIAL UE MESSAGE message is not anymore valid.
+- upon receipt of the first LOCATION REPORTING CONTROL message following a Relocation Resource Allocation procedure, with the *Event* IE included in the *Request Type* IE set to "Change of Service Area", as soon as SAI becomes available in the new SRNC and the relocation procedure has been successfully completed.
+
+In case a Service Area is reported, the RNC shall include in the *Area Identity* IE of the LOCATION REPORT message a Service Area that includes at least one of the cells from which the UE is consuming radio resources.
+
+In case the LOCATION REPORT message is sent as an answer to a request for a direct report, for periodic reporting or for reports at a change of Service Area, the *Request Type* IE from the LOCATION REPORTING CONTROL message shall be included.
+
+If the LOCATION REPORT message is sent as an answer to a request for a direct report of Service Area and the current Service Area can not be determined by the RNC, then the *Area Identity* IE shall be omitted and a cause value shall be included to indicate that the request could not be fulfilled, e.g. "Requested Information Not Available" or "Location Reporting Congestion". The RNC may also include the *Last Known Service Area* IE.
+
+If the RNC can not deliver the location information as requested by the CN, due to either the non-support of the requested event or the non-support of the requested report area, or if the RNC is currently not able to reach the UE, the RNC shall indicate the UE location to be "Undetermined" by omitting the *Area Identity* IE. A cause value shall instead be added to indicate the reason for the undetermined location, e.g. "Requested Request Type not supported", "Location Reporting Congestion" or "No Resource Available".
+
+In case of periodic reporting is requested by the CN, the RNC shall issue the first LOCATION REPORT message one reporting interval as indicated in the *Reporting Interval* IE contained in the LOCATION REPORTING CONTROL message after reception of the LOCATION REPORTING CONTROL message and continue to send LOCATION REPORT messages one reporting interval after the previous LOCATION REPORT message until the desired amount of reports as given in the *Reporting Amount* IE has been attained, or until the periodic reporting is canceled by the CN or aborted by the RNC. When no location estimate is available at the RNC when the reporting criteria are fulfilled (e.g., due to failure of a position method itself), the RNC shall indicate the UE location to be "Undetermined" by omitting the *Area Identity* IE. A cause value shall instead be added to indicate the reason for the undetermined location, e.g. "Periodic Location Information not Available".
+
+If the Location Report procedure was triggered by a LOCATION REPORTING CONTROL message, which included a request to report a geographical area with a specific accuracy, the LOCATION REPORT message shall include:
+
+- the *Geographical Area* IE within the *Area Identity* IE containing either a point with indicated uncertainty or a polygon or an other type, which fulfils the requested accuracy, and
+- the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy fulfilled".
+
+If the Location Report procedure was triggered by a LOCATION REPORTING CONTROL message, which included a request to report with a geographical area and whenever one of the geographic area shapes *Ellipsoid point with uncertainty Ellipse* IE, *Ellipsoid point with altitude and uncertainty Ellipsoid* IE or *Ellipsoid Arc* IE is reported, the *Confidence* IE shall indicate the probability that the UE is located within the uncertainty region of the shape. The value of the *Confidence* IE shall be in the interval of "1" to "100".
+
+If any of the requested accuracy cannot be fulfilled, the LOCATION REPORT message shall include:
+
+- the *Geographical Area* IE within the *Area Identity* IE containing either a point with indicated uncertainty or a polygon or an other type, with the best possible accuracy, and
+- the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy not fulfilled".
+
+If the *Confidence* IE received from the UE has value "0", the RNC shall consider the requested accuracy as not fulfilled and if the received position is reported or forwarded then the confidence and uncertainty shape shall not be included (i.e. either the *Point* IE or the *Ellipsoid point with altitude* IE shall be used).
+
+If, on the other hand, no specific accuracy level was requested in the LOCATION REPORTING CONTROL message, the LOCATION REPORT message shall include the *Geographical Area* IE within the *Area Identity* IE, the reported *Geographical Area* IE may include an accuracy.
+
+The LOCATION REPORT message shall also include, if available, the *Position Data* IE containing the positioning method (or list of positioning methods) used successfully to obtain the location estimate, together with the usage information.
+
+If the Location Report procedure was triggered by a LOCATION REPORTING CONTROL message which included a request to report with a geographical area and in which the *IncludeVelocity* IE was set to "requested", the LOCATION REPORT message shall include a *Velocity Estimate* IE, if available and if the handling of velocity is supported by the RNC.
+
+If the Location Report procedure was triggered by a LOCATION REPORTING CONTROL message, which included a request to report with a geographical area and in which the *Client Type* IE was not included, the RNC shall answer with the *Point* IE, or the *Point With Uncertainty* IE or the *Polygon* IE within the *Geographical Area* IE of the LOCATION REPORT message.
+
+## 8.20.3 Abnormal Conditions
+
+Not applicable.
+
+# 8.21 Data Volume Report
+
+## 8.21.1 General
+
+The Data Volume Report procedure is used by CN to request the unsuccessfully transmitted DL data volume for specific RABs. This procedure only applies to the PS domain. The procedure uses connection oriented signalling.
+
+NOTE: In line with TS32.240 [61], this procedure is not used and the RNC should ignore a DATA VOLUME REPORT REQUEST message if received.
+
+## 8.21.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: DATA VOLUME REPORT REQUEST
+ CN->>RNC: DATA VOLUME REPORT REQUEST
+ Note right of RNC: DATA VOLUME REPORT
+ RNC->>CN: DATA VOLUME REPORT
+```
+
+Sequence diagram of the Data Volume Report procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A message labeled 'DATA VOLUME REPORT REQUEST' is sent from the CN to the RNC, indicated by a long arrow pointing left. A message labeled 'DATA VOLUME REPORT' is sent from the RNC to the CN, indicated by a long arrow pointing right. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 23: Data Volume Report procedure. Successful operation.**
+
+The procedure is initiated by CN by sending DATA VOLUME REPORT REQUEST message to UTRAN. This message shall contain the list of *RAB ID* IEs to identify the RABs for which the unsuccessfully transmitted DL data volume shall be reported.
+
+At reception of a DATA VOLUME REPORT REQUEST message, the UTRAN shall produce a DATA VOLUME REPORT message. For each RAB successfully addressed within the *RAB Data Volume Report List* IE of the DATA VOLUME REPORT REQUEST message, the DATA VOLUME REPORT message shall include in the *Unsuccessfully Transmitted DL Data Volume* IE the amount of unsuccessfully transmitted DL data since the last data volume reported to the CN for the RAB and with the same data volume reference, if present. The message may also contain the *Data Volume Reference* IE.
+
+The message may contain for each RAB successfully addressed a maximum of two *RAB Data Volume Report Item* IEs within the *RAB Data Volume Report List* IE for the case when there is a need to report two different data volumes since the last data volume indication to the CN. The UTRAN shall also reset the data volume counter for the reported RABs. The UTRAN shall send the DATA VOLUME REPORT message to the CN. Transmission and reception of the DATA VOLUME REPORT message terminate the procedure in the UTRAN and in the CN respectively.
+
+The *Data Volume Reference* IE, if included, indicates the time when the data volume is counted.
+
+## 8.21.3 Unsuccessful Operation
+
+The *RAB ID* IE for each RAB for which UTRAN is not able to transfer a data volume report is included in the DATA VOLUME REPORT message together with a *Cause* IE, e.g. "Invalid RAB ID".
+
+## 8.21.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.22 Initial UE Message
+
+### 8.22.1 General
+
+The purpose of the Initial UE Message procedure is to establish an Iu signalling connection between a CN domain and the RNC and to transfer the initial NAS-PDU to the CN node as determined by the NAS Node Selection Function - if this function is active, or otherwise to the default CN node- or by the Rerouting Function (see TS 25.410 [2]) in case of MOCN configuration. The procedure uses connection oriented signalling.
+
+### 8.22.2 Successful Operation
+
+
+
+```
+
+graph LR
+ RNC[RNC] -- "INITIAL UE MESSAGE" --> CN[CN]
+
+```
+
+Diagram illustrating the Initial UE Message procedure. A box labeled RNC is on the left, and a box labeled CN is on the right. A horizontal arrow labeled INITIAL UE MESSAGE points from the RNC to the CN. Both boxes have a thick horizontal line at their base.
+
+**Figure 24: Initial UE Message procedure. Successful operation.**
+
+When the RNC has received from radio interface a NAS message (see TS 24.008 [8]) to be forwarded to a CN domain to which no Iu signalling connection for the UE exists, the RNC shall initiate the Initial UE Message procedure and send the INITIAL UE MESSAGE message to the CN. If NNSF is active, the selection of the CN node is made according to TS 23.236 [26].
+
+In addition to the received NAS-PDU, the RNC shall add the following information to the INITIAL UE MESSAGE message:
+
+- CN domain indicator, indicating the CN domain towards which this message is sent.
+- For CS domain, the LAI which is the last LAI indicated to the UE by the UTRAN via the current RRC connection, or if the UTRAN has not yet indicated any LAI to the UE via the current RRC connection, then the LAI of the cell via which the current RRC connection was established.
+- For PS domain, the LAI+RAC which are the last LAI+RAC indicated to the UE by UTRAN via the current RRC connection, or if the UTRAN has not yet indicated any LAI+RAC to the UE via the current RRC connection, then the LAI+RAC of the cell via which the current RRC connection was established.
+- Service Area corresponding to at least one of the cells from which the UE is consuming radio resources.
+- Iu signalling connection identifier.
+- Global RNC identifier.
+- Selected PLMN Identity, if received from radio interface by a network sharing supporting UE in shared networks.
+- Redirect Attempt Flag, in MOCN configuration for a network sharing non supporting UE in order to indicate that the CN shall respond with a *Redirection Indication* IE or a *Redirection Completed* IE.
+
+The *Iu Signalling Connection Identifier* IE contains an Iu signalling connection identifier which is allocated by the RNC. The value for the *Iu Signalling Connection Identifier* IE shall be allocated so as to uniquely identify an Iu signalling connection for the RNC. The CN should store and remember this identifier for the duration of the Iu connection.
+
+Whereas several processing entities within the CN (e.g. charging, interception, etc.) may make use of the location information given in the *SAI* IE and the *LAI* (and *RAC* for PS domain) IE, the mobility management within the CN shall rely on the information given within the *LAI* IE (respectively *LAI* and *RAC* IEs for PS domain) only.
+
+If the establishment of the Iu signalling connection towards the CN is performed due to an RRC connection establishment originating from a CSG cell and if the UE is CSG capable, the *CSG Id* IE shall be included in the INITIAL UE MESSAGE message.
+
+If the establishment of the Iu signalling connection towards the CN is performed due to an RRC connection establishment originating from a Hybrid cell and if the UE is CSG capable, the *CSG Id* IE and *Cell Access Mode* IE shall be included in the INITIAL UE MESSAGE message.
+
+If the RNC has a co-located L-GW, it shall include the *L-GW Transport Layer Address* IE in the INITIAL UE MESSAGE message.
+
+If the *Higher bitrates than 16 Mbps flag* IE is included in the INITIAL UE MESSAGE message then the CN shall, if supported, use the IE as described in TS 23.060 [21].
+
+If the *Tunnel Information for BBF* IE is received in the INITIAL UE MESSAGE message, the CN shall, if supported, use the IE as described in TS 23.139 [65].
+
+### Interaction with Direct Transfer procedure
+
+In MOCN configuration, if the RNC receives the *Redirection Indication* IE in the DIRECT TRANSFER message from a CN node which is not the last attempted, it shall initiate the Initial UE Message procedure towards another CN operator when possible (or possibly to the same CN in case when CS/PS coordination is required), with the following additional information in the INITIAL UE MESSAGE message:
+
+- *NAS Sequence Number* IE, if received from previously attempted CN operator;
+- *Permanent NAS UE Identity* IE, if received from one of previously attempted CN operators.
+
+### 8.22.2.1 Successful Operation for GERAN Iu-mode
+
+For GERAN Iu-mode, the following shall apply in addition for the successful operation of the Initial UE Message procedure:
+
+- In case of establishment of a signalling connection towards the CS domain in GERAN Iu-mode, the INITIAL UE MESSAGE message shall contain the *GERAN Classmark* IE in order to provide the CN with GERAN-specific information (see TS 43.051 [27]).
+
+## 8.23 Direct Transfer
+
+### 8.23.1 General
+
+The purpose of the Direct Transfer procedure is to carry UE – CN signalling messages over the Iu Interface. The UE – CN signalling messages are not interpreted by the UTRAN, and their content (e.g. MM or CC message) is outside the scope of this specification (see TS 24.008 [8]). The UE – CN signalling messages are transported as a parameter in the DIRECT TRANSFER messages. The procedure uses connection oriented signalling.
+
+### 8.23.2 Successful Operation
+
+#### 8.23.2.1 CN Originated Direct Transfer
+
+
+
+Diagram showing the successful operation of CN originated Direct Transfer. A box labeled 'RNC' is on the left and a box labeled 'CN' is on the right. A horizontal arrow labeled 'DIRECT TRANSFER' points from the 'CN' box to the 'RNC' box. Both boxes have vertical lines extending downwards to a common horizontal baseline.
+
+**Figure 25: Direct Transfer, CN originated. Successful operation.**
+
+If a UE - CN signalling message has to be sent from the CN to the UE, the CN shall send a DIRECT TRANSFER message to the RNC including the UE - CN signalling message as a *NAS-PDU* IE.
+
+If the DIRECT TRANSFER message is sent in the downlink direction, it shall include the *SAPI* IE and shall not include the *LAI + RAC* IE and the *SAI* IE. The use of the *SAPI* IE included in the DIRECT TRANSFER message enables the UTRAN to provide specific service for the transport of the included NAS message.
+
+Upon receipt of the DIRECT TRANSFER message the RNC shall
+
+- store the Subscriber Profile ID for RAT/Frequency priority IE and use it as defined in TS 36.300 [52].
+
+**In case of rerouting in MOCN configuration:**
+
+If the CN can serve the network sharing non-supporting UE and CS/PS coordination is not required, the *NAS-PDU* IE - i.e. the accept NAS message - and the *Redirection completed* IE shall be included in the DIRECT TRANSFER message for the downlink direction.
+
+If the CN cannot serve the network sharing non-supporting UE, the *NAS-PDU* IE - i.e. the reject NAS message - and a *Redirection Completed* IE shall be included in the DIRECT TRANSFER message for the downlink direction, except for some particular reject causes, see Annex N TS 24.008 [8]. For these particular reject causes, the *NAS-PDU* IE and the *Redirection Indication* IE shall be included in the DIRECT TRANSFER message for the downlink direction.
+
+If the CN can serve the network sharing non-supporting UE, but CS/PS coordination is required, the *NAS-PDU* IE - i.e. the reject NAS message - and a *Redirection Indication* IE shall be included in the DIRECT TRANSFER message for the downlink direction.
+
+The *Redirection Indication* IE shall contain:
+
+- The *initial NAS-PDU* IE received from the UE;
+- The *Reject Cause Value* IE;
+- The *NAS Sequence Number* IE, if available for CS;
+- The *Permanent NAS UE Identity* IE, if available.
+
+Upon reception of the downlink DIRECT TRANSFER message including the *Redirection Indication* IE, the RNC shall store as part of the Rerouting Function the associated *Reject Cause Value* IE and *NAS-PDU* IE related to this CN. In case the *Reject Cause Value* IE is set to "CS/PS coordination required", then the RNC shall perform CS/PS coordination based on the received *Permanent NAS UE Identity* IE. In this case the *Reject Cause Value* IE and the associated *NAS-PDU* IE shall not be stored.
+
+In case all attempted CN operators have replied with the *Redirection Indication* IE, the RNC shall select the most appropriate *NAS-PDU* among the *NAS-PDU* IEs received from the attempted CN nodes based on the stored information as part of the Rerouting function and send it back to the UE.
+
+Upon reception of the downlink DIRECT TRANSFER message including the *Redirection Completed* IE, the RNC shall send back the included *NAS-PDU* IE to the UE and terminate the Rerouting Function.
+
+## 8.23.2.2 UTRAN Originated Direct Transfer
+
+
+
+```
+
+graph LR
+ RNC[RNC] -- "DIRECT TRANSFER" --> CN[CN]
+ RNC --- UE[ ]
+ CN --- UE
+ style UE fill:none,stroke:none
+
+```
+
+Diagram showing a Direct Transfer message from RNC to CN. The RNC is on the left and the CN is on the right. A horizontal arrow labeled 'DIRECT TRANSFER' points from the RNC to the CN. Both RNC and CN are connected to a common horizontal line at the bottom, representing the UE.
+
+**Figure 26: Direct Transfer, RNC originated. Successful operation.**
+
+If a UE - CN signalling message has to be sent from the RNC to the CN without interpretation, the RNC shall send a DIRECT TRANSFER message to the CN including the UE - CN signalling message as a *NAS-PDU* IE.
+
+If the DIRECT TRANSFER message shall be sent to the PS domain, the RNC shall also add the *LAI* and the *RAC* IEs, which were the last *LAI + RAC* indicated to the UE by the UTRAN via the current RRC connection, or if the UTRAN had not yet indicated any *LAI + RAC* to the UE via the current RRC connection, then the *LAI + RAC* of the cell via which the current RRC connection was established. If the DIRECT TRANSFER message is sent to the PS domain, the
+
+RNC shall also add a Service Area corresponding to at least one of the cells from which the UE is consuming radio resources. If the DIRECT TRANSFER message is sent in uplink direction, the RNC shall not include the *SAPI* IE.
+
+If the RNC has a co-located L-GW, it shall include the *L-GW Transport Layer Address* IE in the DIRECT TRANSFER message.
+
+### 8.23.3 Abnormal Conditions
+
+If the DIRECT TRANSFER message is sent by the RNC to the PS domain, and any of the *LAI* IE, *RAC* IE or *SAI* IE is missing, the CN shall continue with the Direct Transfer procedure, ignoring the missing IE.
+
+If the DIRECT TRANSFER message is sent by the CN to the RNC without the *SAPI* IE, the RNC shall continue with the Direct Transfer procedure.
+
+If Redirect Attempt Flag was sent in an INITIAL UE MESSAGE and the corresponding DIRECT TRANSFER message is sent by the CN to the RNC without *Redirection Completed* IE or *Redirection Indication* IE, the RNC shall send back the included NAS-PDU IE to the UE and terminate the Rerouting Function.
+
+## 8.24 Void
+
+## 8.25 Overload Control
+
+### 8.25.1 General
+
+This procedure is defined to give some degree of signalling flow control. At the UTRAN side, "Processor Overload" and "Overload in the Capability to Send Signalling Messages to the UE" are catered for, and at the CN side, "Processor Overload" is catered for. The procedure uses connectionless signalling.
+
+The philosophy used is to stem the traffic at source with known effect on the service. The algorithm used is:
+
+At the CN side:
+
+- If $T_{igoc}$ is not running and an OVERLOAD message or "Signalling Point Congested" information is received, the traffic should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce the traffic within the *Number of Steps* IE. At the same time, timers $T_{igoc}$ and $T_{inTC}$ should be started.
+- During $T_{igoc}$ all received OVERLOAD messages or "Signalling Point Congested" information should be ignored.
+- This step by step reduction of traffic should be continued until maximum reduction is obtained by arriving at the last step.
+- If $T_{inTC}$ expires, the traffic should be increased by one step and $T_{inTC}$ should be re-started unless the number of steps by which the traffic is reduced is back to zero.
+
+At the UTRAN side:
+
+- If $T_{igOR}$ is not running and an OVERLOAD message not including the *Priority Class Indicator* IE or "Signalling Point Congested" information is received, all the traffic should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce the traffic within the *Number of Steps* IE. At the same time, timers $T_{igOR}$ and $T_{inTR}$ should be started.
+- If $T_{igOR}$ is not running and an OVERLOAD message including the *Priority Class Indicator* IE is received and a procedure for reduction of all traffic is not being processed, then signalling traffic for the indicated priority class should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce the traffic within the *Number of Steps* IE. At the same time, timers $T_{igOR}$ and $T_{inTR}$ should be started.
+- During $T_{igOR}$ all received OVERLOAD messages or "Signalling Point Congested" information should be ignored.
+- This step-by-step reduction of traffic should be continued until maximum reduction is obtained by arriving at the last step.
+- If $T_{inTR}$ expires, the traffic should be increased by one step and $T_{inTR}$ should be re-started unless the number of steps by which the traffic is reduced is back to zero.
+
+The number of steps and the method for reducing the load are implementation-specific.
+
+There may be other traffic control mechanisms from O&M activities occurring simultaneously.
+
+## 8.25.2 Philosophy
+
+Void.
+
+## 8.25.3 Successful Operation
+
+### 8.25.3.1 Overload at the CN
+
+
+
+Diagram showing Overload at the CN. Successful operation. An RNC box and a CN box are shown. A horizontal arrow labeled 'OVERLOAD' points from the CN box to the RNC box. Both boxes have vertical lines extending downwards to a thick horizontal bar representing the ground or base.
+
+**Figure 27: Overload at the CN. Successful operation.**
+
+The CN should indicate to the RNC that it is in a congested state by sending an OVERLOAD message. The *CN Domain Indicator* IE may be included, if the CN can determine the domain suffering from the signalling traffic overload. A specific CN node shall send this message only towards those RNCs from which it can receive the INITIAL UE MESSAGE message.
+
+Reception of the message by the UTRAN should cause reduction of signalling traffic towards the CN. If the *CN Domain Indicator* IE is included in the OVERLOAD message, and the *Global CN-ID* IE is not, the RNC should apply signalling traffic reduction mechanisms towards the indicated domain. If the *Priority Class Indicator* IE is included then the RNC should take the appropriate action to reduce the traffic for the priority class indicated in the IE.
+
+If the NNSF is active, the CN shall include the *Global CN-ID* IE within the OVERLOAD message, and the RNC should apply signalling traffic reduction mechanisms towards the indicated CN node only.
+
+### 8.25.3.2 Overload at the UTRAN
+
+
+
+Diagram showing Overload at the UTRAN. Successful operation. An RNC box and a CN box are shown. A horizontal arrow labeled 'OVERLOAD' points from the RNC box to the CN box. Both boxes have vertical lines extending downwards to a thick horizontal bar representing the ground or base.
+
+**Figure 28: Overload at the UTRAN. Successful operation.**
+
+If the UTRAN is not capable of sending signalling messages to UEs due to overloaded resources, the UTRAN should send an OVERLOAD message to the CN. The RNC shall include the *Global RNC-ID* IE in this message. The message shall be sent only towards those CN nodes towards which the RNC can send the INITIAL UE MESSAGE message. If the *Priority Class Indicator* IE is included it shall be ignored.
+
+## 8.25.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.26 Reset
+
+### 8.26.1 General
+
+The purpose of the Reset procedure is to initialise the UTRAN in the event of a failure in the CN or vice versa. The procedure uses connectionless signalling.
+
+## 8.26.2 Successful Operation
+
+### 8.26.2.1 Reset Procedure Initiated from the CN
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates Reset
+ CN->>RNC: RESET
+ Note right of RNC: RNC processes Reset
+ RNC->>CN: RESET ACKNOWLEDGE
+```
+
+Sequence diagram for Reset procedure initiated from the CN. The diagram shows two lifelines: RNC and CN. The CN sends a RESET message to the RNC. The RNC responds with a RESET ACKNOWLEDGE message to the CN.
+
+**Figure 29: Reset procedure initiated from the CN. Successful operation.**
+
+In the event of a failure at the CN, which has resulted in the loss of transaction reference information, a RESET message shall be sent to the RNC. When a CN node sends this message towards an RNC for which it is not the default CN node, the *Global CN-ID* IE shall be included. This message is used by the UTRAN to release affected Radio Access Bearers and to erase all affected references for the specific CN node that sent the RESET message, i.e. the CN node indicated by the *Global CN-ID* IE or, if this IE is not included, the default CN node for the indicated CN domain.
+
+After a guard period of $T_{\text{RatC}}$ seconds a RESET ACKNOWLEDGE message shall be returned to the CN, indicating that all references at the UTRAN have been cleared. The RNC does not need to wait for the release of UTRAN radio resources or for the transport network layer signalling to be completed before returning the RESET ACKNOWLEDGE message.
+
+The RNC shall include the *Global RNC-ID* IE in the RESET ACKNOWLEDGE message. The *Global RNC-ID* IE shall not be included in the RESET message.
+
+#### Interactions with other procedures:
+
+In case of interactions with other procedures, the Reset procedure shall always override all other procedures.
+
+### 8.26.2.2 Reset Procedure Initiated from the UTRAN
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: RNC initiates Reset
+ RNC->>CN: RESET
+ Note right of CN: CN processes Reset
+ CN->>RNC: RESET ACKNOWLEDGE
+```
+
+Sequence diagram for Reset procedure initiated from the UTRAN. The diagram shows two lifelines: RNC and CN. The RNC sends a RESET message to the CN. The CN responds with a RESET ACKNOWLEDGE message to the RNC.
+
+**Figure 30: Reset procedure initiated from the UTRAN. Successful operation.**
+
+In the event of a failure at the UTRAN which has resulted in the loss of transaction reference information, a RESET message shall be sent to all CN nodes towards which the RNC has Iu signalling connections established. This message is used by the CN to release affected Radio Access Bearers and to erase all affected references for the sending RNC.
+
+The RNC shall include the *Global RNC-ID* IE in the RESET message.
+
+After a guard period of $T_{\text{RatR}}$ seconds a RESET ACKNOWLEDGE message shall be returned to the UTRAN indicating that all references have been cleared.
+
+When a RESET ACKNOWLEDGE message is sent from a CN node towards an RNC for which the sending CN node is not the default CN node, the *Global CN-ID* IE shall be included.
+
+#### Interactions with other procedures:
+
+In case of interactions with other procedures, the Reset procedure shall always override all other procedures.
+
+### 8.26.3 Abnormal Conditions
+
+#### 8.26.3.1 Abnormal Condition at the CN
+
+If the CN sends a RESET message to the RNC and receives no RESET ACKNOWLEDGE message within a period $T_{\text{RatR}}$ then it shall repeat the entire Reset procedure. The sending of the RESET message shall be repeated a maximum of "n" times where n is an operator matter. After the n-th unsuccessful repetition the procedure shall be stopped and e.g. the maintenance system be informed.
+
+#### 8.26.3.2 Abnormal Condition at the UTRAN
+
+If the RNC sends a RESET message to the CN and receives no RESET ACKNOWLEDGE message within a period $T_{\text{RatC}}$ then it shall repeat the entire Reset procedure. The sending of the RESET message shall be repeated a maximum of "n" times where n is an operator matter. After the n-th unsuccessful repetition the procedure shall be stopped and e.g. the maintenance system be informed.
+
+#### 8.26.3.3 Crossing of Reset Messages
+
+When an entity that has sent a RESET message and is waiting for a RESET ACKNOWLEDGE message, instead receives a RESET message from the peer entity, it shall stop timer $T_{\text{RatC}}$ or $T_{\text{RatR}}$ and send a RESET ACKNOWLEDGE message to the peer entity.
+
+### 8.27 Error Indication
+
+#### 8.27.1 General
+
+The Error Indication procedure is initiated by a node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message.
+
+If the error situation arises due to reception of a message utilising dedicated signalling, then the Error Indication procedure uses connection oriented signalling. Otherwise the procedure uses connectionless signalling.
+
+#### 8.27.2 Successful Operation
+
+
+
+```
+graph LR; CN[CN] -- ERROR INDICATION --> RNC[RNC];
+```
+
+Diagram of the Error Indication procedure, CN originated. Successful operation. The diagram shows two nodes, RNC and CN, connected by a vertical line. The RNC is on the left and the CN is on the right. An arrow labeled 'ERROR INDICATION' points from the CN to the RNC. Both nodes have a horizontal bar at the bottom of their vertical lines, representing the ground or base of the connection.
+
+Figure 31: Error Indication procedure, CN originated. Successful operation.
+
+
+
+Figure 32: Error Indication procedure, RNC originated. Successful operation. The diagram shows a sequence of two vertical lines representing the RNC and CN nodes. A horizontal arrow labeled 'ERROR INDICATION' points from the RNC line to the CN line. Both lines have a thick horizontal bar at the bottom.
+
+**Figure 32: Error Indication procedure, RNC originated. Successful operation.**
+
+When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node.
+
+The ERROR INDICATION message shall contain at least either the *Cause* IE or the *Criticality Diagnostics* IE.
+
+Examples for possible cause values for protocol error indications are:
+
+- "Transfer Syntax Error"
+- "Semantic Error"
+- "Message not compatible with receiver state".
+
+If the ERROR INDICATION message is sent connectionless, the *CN Domain Indicator* IE shall be present.
+
+If the ERROR INDICATION message is sent connectionless towards the CN, the *Global RNC-ID* IE shall be present.
+
+When an ERROR INDICATION message is sent connectionless from a CN node towards an RNC for which the sending CN node is not the default CN node, the *Global CN-ID* IE shall be included.
+
+### 8.27.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.28 CN Deactivate Trace
+
+### 8.28.1 General
+
+The purpose of the CN Deactivate Trace procedure is to inform the RNC to stop the trace session, initiated by a signalling based activation, for the indicated trace reference and related to the UE the Iu connection is used for. The procedure uses connection oriented signalling.
+
+### 8.28.2 Successful Operation
+
+
+
+Figure 33: CN Deactivate Trace procedure. Successful operation. The diagram shows a sequence of two vertical lines representing the RNC and CN nodes. A horizontal arrow labeled 'CN DEACTIVATE TRACE' points from the CN line to the RNC line. Both lines have a thick horizontal bar at the bottom.
+
+**Figure 33: CN Deactivate Trace procedure. Successful operation.**
+
+The CN invokes the CN Deactivate Trace procedure by sending a CN DEACTIVATE TRACE message to the UTRAN as defined in TS 32.422 [38].
+
+The CN DEACTIVATE TRACE message shall contain the *Trace Reference* IE. The RNC shall stop the trace session for the indicated trace reference in the *Trace Reference* IE. In case of simultaneous CS/PS connections, the trace session for the indicated trace reference shall be closed upon reception of the CN DEACTIVATE TRACE message from any of the CN domain, whether it was the one which initiated trace session activation or not.
+
+### 8.28.2.1 Successful Operation for GERAN Iu mode
+
+The CN DEACTIVATE TRACE message shall contain the *Trace Reference* IE and may contain the *Trigger ID* IE. The *Trace Reference* IE and, if present, the *Trigger ID* IE are used to indicate which trace shall be stopped.
+
+## 8.28.3 Abnormal Conditions
+
+Void
+
+# 8.29 Reset Resource
+
+## 8.29.1 General
+
+The purpose of the Reset Resource procedure is to initialise part of the UTRAN in the event of an abnormal failure in the CN or vice versa (e.g. Signalling Transport processor reset). The procedure uses connectionless signalling.
+
+### 8.29.1.1 Reset Resource procedure initiated from the RNC
+
+Void
+
+### 8.29.1.2 Reset Resource procedure initiated from the CN
+
+Void.
+
+## 8.29.2 Successful Operation
+
+### 8.29.2.1 Reset Resource procedure initiated from the RNC
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: RNC initiates procedure
+ RNC->>CN: RESET RESOURCE
+ Note right of CN: CN releases resources
+ CN-->>RNC: RESET RESOURCE ACKNOWLEDGE
+```
+
+Sequence diagram showing the RNC initiated Reset Resource procedure. The RNC sends a RESET RESOURCE message to the CN, and the CN responds with a RESET RESOURCE ACKNOWLEDGE message.
+
+**Figure 34: RNC initiated Reset Resource procedure. Successful operation.**
+
+The RNC initiates the procedure by sending a RESET RESOURCE message to the CN.
+
+The RESET RESOURCE message shall include the *CN Domain Indicator* IE, the *Global RNC-ID* IE, the *Cause* IE with the appropriate cause value (e.g. "Signalling Transport Resource Failure") and a list containing *Iu Signalling Connection Identifier* IEs.
+
+On reception of this message the CN shall release locally the resources and references (i.e. resources and Iu signalling connection identifiers) associated to the Iu signalling connection identifiers indicated in the received message. The CN shall always return the RESET RESOURCE ACKNOWLEDGE message to the RNC when all Iu-related resources and references have been released and shall include the *CN Domain Indicator* IE and a list of *Iu Signalling Connection Identifier* IEs. The list of *Iu Signalling Connection Identifier* IEs within the RESET RESOURCE ACKNOWLEDGE message shall be in the same order as received in the RESET RESOURCE message. Unknown signalling connection identifiers shall be reported as released.
+
+When a RESET RESOURCE ACKNOWLEDGE message is sent from a CN node towards an RNC for which the sending CN node is not the default CN node, the *Global CN-ID* IE shall be included.
+
+Both the CN and the RNC shall provide means to prevent the immediate re-assignment of released Iu signalling connection identifiers to minimise the risk that the Reset Resource procedure releases the same Iu signalling connection identifiers re-assigned to new Iu connections.
+
+## 8.29.2.2 Reset Resource procedure initiated from the CN
+
+
+
+```
+
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: RESET RESOURCE
+ Note right of RNC: RNC releases resources
+ RNC->>CN: RESET RESOURCE ACKNOWLEDGE
+
+```
+
+Sequence diagram for CN initiated Reset Resource procedure. The CN sends a RESET RESOURCE message to the RNC, and the RNC responds with a RESET RESOURCE ACKNOWLEDGE message.
+
+**Figure 35: CN initiated Reset Resource procedure. Successful operation.**
+
+The CN initiates the procedure by sending a RESET RESOURCE message to the RNC.
+
+The RESET RESOURCE message shall include the *CN Domain Indicator* IE, the *Cause* IE with the appropriate cause value (e.g. "Signalling Transport Resource Failure") and a list containing *Iu Signalling Connection Identifier* IEs.
+
+When a RESET RESOURCE message is sent from a CN node towards an RNC for which the sending CN node is not the default CN node, the *Global CN-ID* IE shall be included.
+
+On reception of this message the RNC shall release locally the resources and references (i.e. radio resources and Iu signalling connection identifiers) associated to the specific CN node and Iu signalling connection identifiers indicated in the received message. The *Global RNC-ID* IE shall not be included in the RESET RESOURCE message. If no *Global CN-ID* IE is included in the RESET RESOURCE message to indicate the sending CN node, the default CN node for the indicated CN domain shall be considered as sender. The RNC shall always return the RESET RESOURCE ACKNOWLEDGE message to the CN when all Iu-related resources and references have been released and shall include the *CN Domain Indicator* IE, a list of *Iu Signalling Connection Identifier* IEs and the *Global RNC-ID* IE. The list of *Iu Signalling Connection Identifier* IEs within the RESET RESOURCE ACKNOWLEDGE message shall be in the same order as received in the RESET RESOURCE message. Unknown signalling connection identifiers shall be reported as released.
+
+Both the RNC and the CN shall provide means to prevent the immediate re-assignment of released Iu signalling connection identifiers to minimise the risk that the Reset Resource procedure releases the same Iu signalling connection identifiers re-assigned to new Iu connections.
+
+## 8.30 RAB Modification Request
+
+### 8.30.1 General
+
+The purpose of the RAB Modification Request procedure is to allow the RNC to initiate renegotiation of RABs for a given UE after RAB establishment. The procedure uses connection oriented signalling.
+
+### 8.30.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: RNC initiates procedure
+ RNC->>CN: RAB MODIFY REQUEST
+
+```
+
+Sequence diagram for RAB Modification procedure. The RNC sends a RAB MODIFY REQUEST message to the CN.
+
+**Figure 36: RAB Modification procedure.**
+
+The RNC initiates the procedure by generating a RAB MODIFY REQUEST message towards the CN and shall include a list of *RABs To Be Modified* IEs. For each RAB requested to be modified the *RABs To Be Modified Item* IE of the RAB MODIFY REQUEST message shall include the *RAB ID* IE, and the corresponding *Requested RAB Parameter Values* IE. The *Requested RAB Parameter Values* IE shall either list those RAB parameters the RNC would like
+
+modified and the associated new RAB parameter values it is requesting or shall indicate that the execution of the alternative RAB configuration is requested. For any given RAB, the RNC shall be able to propose modifications to any negotiable RAB parameters.
+
+If the requested maximum bit rate (respectively the requested guaranteed bit rate when applicable) exceeds the maximum value of the *Requested Maximum Bit Rate IE* (respectively *Requested Guaranteed Bit Rate IE*), either the *Extended Requested Maximum Bit Rate IE* (respectively *Extended Requested Guaranteed Bit Rate IE*) shall be used or the *Supported Requested Maximum Bit Rate IE* (respectively *Supported Requested Guaranteed Bit Rate IE*) shall be used.
+
+For a RAB if *Extended Requested Maximum Bit Rate IE* (respectively *Extended Requested Guaranteed Bit Rate IE* when applicable) is signalled in one direction RNC shall signal the *Extended Requested Maximum Bit Rate IE* (respectively *Extended Requested Guaranteed Bit Rate IE*) also in the other direction for this RAB. If *Supported Requested Maximum Bit Rate IE* (respectively *Supported Requested Guaranteed Bit Rate IE*) is used it shall be used in both directions.
+
+If supported the RNC may include the *Supported Requested Maximum Bit Rate IE* (respectively *Supported Requested Guaranteed Bit Rate IE*) in *Requested RAB Parameter Values IE* to define the RAB parameters the RNC would like modified and the associated new RAB parameter values.
+
+If the RNC is allowed to request an alternative RAB Configuration, the RNC may request the CN to trigger the execution of this alternative RAB configuration by including the *Alternative RAB Configuration Request IE* in the RAB MODIFY REQUEST message.
+
+Upon reception of the RAB MODIFY REQUEST message, it is up to the CN to decide how to react to the request.
+
+### 8.30.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.31 Location Related Data
+
+### 8.31.1 General
+
+The purpose of the Location Related Data procedure is to provide the means to handle additional location-related requests over the Iu interface: it allows the CN to either retrieve from the RNC deciphering keys (to be forwarded to the UE) for the broadcast assistance data, or request the RNC to deliver dedicated assistance data to the UE. The procedure uses connection oriented signalling.
+
+### 8.31.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: LOCATION RELATED DATA REQUEST
+ Note right of RNC: RNC processes request
+ RNC->>CN: LOCATION RELATED DATA RESPONSE
+```
+
+Sequence diagram of the Location Related Data procedure. The CN sends a LOCATION RELATED DATA REQUEST message to the RNC, and the RNC responds with a LOCATION RELATED DATA RESPONSE message.
+
+**Figure 37: Location Related Data procedure. Successful operation.**
+
+The CN initiates the procedure by generating a LOCATION RELATED DATA REQUEST message to the RNC.
+
+Upon reception of the LOCATION RELATED DATA REQUEST message, the RNC shall initiate the requested function indicated in the *Location Related Data Request Type IE*.
+
+The *Location Related Data Request Type* IE indicates to the RNC whether:
+
+- to start dedicated assistance data delivery to the UE, or
+- to send deciphering keys for broadcast assistance data to the CN.
+
+If the LOCATION RELATED DATA REQUEST message included a request for dedicated assistance data delivery to the UE, and if the dedicated assistance data was successfully delivered to the UE, the RNC shall respond to the CN with a LOCATION RELATED DATA RESPONSE message containing no data.
+
+If the LOCATION RELATED DATA REQUEST message included a request for deciphering keys of broadcast assistance data, the RNC shall respond to the CN with a LOCATION RELATED DATA RESPONSE message containing the *Broadcast Assistance Data Deciphering Keys* IE.
+
+### 8.31.2.1 Successful Operation for GERAN Iu mode
+
+Upon reception of the LOCATION RELATED DATA REQUEST message, the BSS shall initiate the requested function indicated in the *Location Related Data Request Type* IE or the *Location Related Data Request Type Specific To GERAN Iu Mode* IE.
+
+In the sole case of a request for GERAN Iu mode specific positioning method, E-OTD, defined in TS 43.059 [29], the LOCATION RELATED DATA REQUEST message shall include the *Location Related Data Request Type Specific To GERAN Iu Mode* IE and not the *Location Related Data Request Type* IE.
+
+The *Location Related Data Request Type* IE or the *Location Related Data Request Type Specific To GERAN Iu Mode* IE shall indicate to the BSS whether:
+
+- to start dedicated assistance data delivery to the UE, or
+- to send deciphering keys for broadcast assistance data to the CN.
+
+### 8.31.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC: RNC
+ Note right of CN: CN
+ CN->>RNC: LOCATION RELATED DATA REQUEST
+ RNC-->>CN: LOCATION RELATED DATA FAILURE
+```
+
+Sequence diagram showing the unsuccessful operation of the Location Related Data procedure. The RNC sends a LOCATION RELATED DATA REQUEST message to the CN, and the CN responds with a LOCATION RELATED DATA FAILURE message.
+
+Figure 38: Location Related Data procedure. Unsuccessful operation.
+
+If the RNC was not able to successfully deliver the requested dedicated assistance data to the UE, or if the RNC is not able to provide the requested deciphering keys, the RNC shall send a LOCATION RELATED DATA FAILURE message including the *Cause* IE to the CN. The *Cause* IE shall indicate the appropriate cause value to the CN, e.g. "Dedicated Assistance data Not Available" or "Deciphering Keys Not Available".
+
+### 8.31.4 Abnormal Conditions
+
+#### 8.31.4.1 Abnormal Conditions for GERAN Iu mode
+
+If the *Location Related Data Request Type* IE and *Location Related Data Request Type Specific To GERAN Iu Mode* IE are both included in the LOCATION RELATED DATA REQUEST message, the BSS shall reject the procedure by sending a LOCATION RELATED DATA FAILURE message.
+
+If the *Location Related Data Request Type* IE is set to the value "Deciphering Keys for UE Based OTDOA" or "Dedicated Assistance Data for UE Based OTDOA", the BSS shall reject the procedure by sending a LOCATION RELATED DATA FAILURE message.
+
+## 8.32 Information Transfer
+
+### 8.32.1 General
+
+The purpose of the Information Transfer procedure is to transfer information from the CN to the RNC.
+
+This procedure uses connectionless signalling.
+
+### 8.32.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: INFORMATION TRANSFER INDICATION
+ Note right of RNC: RNC stores information
+ RNC->>CN: INFORMATION TRANSFER CONFIRMATION
+```
+
+Sequence diagram of the Information Transfer procedure. The CN sends an INFORMATION TRANSFER INDICATION message to the RNC, and the RNC responds with an INFORMATION TRANSFER CONFIRMATION message.
+
+**Figure 39: Information Transfer procedure. Successful operation.**
+
+The CN initiates the procedure by sending an INFORMATION TRANSFER INDICATION message to the RNC.
+
+NOTE: The CN should initiate the Information Transfer procedure, if information is available, at least after the CN or the RNC has performed the Reset procedure or whenever the respective information has changed in the CN.
+
+Upon reception of the INFORMATION TRANSFER INDICATION message, the RNC shall store the received information and use it according to its purpose.
+
+The INFORMATION TRANSFER INDICATION message shall contain the following IEs:
+
+- *Information Transfer ID*
+- *Provided Data*
+- *CN Domain Indicator*.
+
+When a CN node sends this message towards an RNC for which it is not the default CN node, the *Global CN-ID* IE shall be included.
+
+If the RNC is able to process the information contained in the *Provided Data* IE, it shall respond with the INFORMATION TRANSFER CONFIRMATION message provided with the same *Information Transfer ID* IE as the one received in the INFORMATION TRANSFER INDICATION message.
+
+The RNC shall include the *Global RNC-ID* IE and the *CN Domain Indicator* IE in the INFORMATION TRANSFER CONFIRMATION message.
+
+If the *Provided Data* IE contains the *Shared Network Information* IE, the RNC shall replace existing Shared Network Information provided in a previous Information Transfer procedure by the newly provided Shared Network Information.
+
+### 8.32.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of RNC:
+ CN->>RNC: INFORMATION TRANSFER INDICATION
+ Note right of RNC:
+ RNC->>CN: INFORMATION TRANSFER FAILURE
+ Note right of CN:
+```
+
+Sequence diagram for Figure 40: Information Transfer procedure. Unsuccessful operation. The diagram shows two lifelines, RNC and CN. The CN sends an INFORMATION TRANSFER INDICATION message to the RNC. The RNC then sends an INFORMATION TRANSFER FAILURE message back to the CN.
+
+**Figure 40: Information Transfer procedure. Unsuccessful operation.**
+
+If the RNC is not able to process the information contained in the *Provided Data* IE the RNC shall regard the Information Transfer procedure as failed and send the INFORMATION TRANSFER FAILURE message to the CN. The message shall include the same value of the *Information Transfer ID* IE as received in the INFORMATION TRANSFER INDICATION message and set the *Cause* IE to an appropriate value.
+
+The RNC shall include the *Global RNC-ID* IE and the *CN Domain Indicator* IE in the INFORMATION TRANSFER FAILURE message.
+
+### 8.32.4 Abnormal Conditions
+
+None.
+
+## 8.33 UE Specific Information
+
+### 8.33.1 General
+
+The purpose of the UE Specific Information procedure is to transfer from the CN to the RNC data related to a particular UE and a particular communication.
+
+The procedure uses connection oriented signalling.
+
+### 8.33.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of RNC:
+ CN->>RNC: UE SPECIFIC INFORMATION INDICATION
+ Note right of RNC:
+```
+
+Sequence diagram for Figure 41: UE Specific Information procedure. Successful operation. The diagram shows two lifelines, RNC and CN. The CN sends a UE SPECIFIC INFORMATION INDICATION message to the RNC.
+
+**Figure 41: UE Specific Information procedure. Successful operation.**
+
+The UE SPECIFIC INFORMATION INDICATION message may include the *UESBI-Iu* IE.
+
+The RNC shall, if supported, use the *UESBI-Iu* IE when received in the UE SPECIFIC INFORMATION INDICATION message. If *UESBI-Iu* IE contains an IMEISV the RNC may use this information to determine the characteristics of the UE for subsequent handling.
+
+## 8.34 Direct Information Transfer
+
+### 8.34.1 General
+
+The purpose of the Direct Information Transfer procedure is to transfer some information from the RNC to the CN or vice versa in unacknowledged mode.
+
+This procedure uses connectionless signalling.
+
+### 8.34.2 Successful Operation
+
+#### 8.34.2.1 Direct Information Transfer initiated from the RNC
+
+
+
+A sequence diagram illustrating the Direct Information Transfer procedure. It features two vertical lifelines: 'RNC' on the left and 'CN' on the right. A single horizontal arrow points from the RNC lifeline to the CN lifeline, labeled 'DIRECT INFORMATION TRANSFER'. Both lifelines terminate at a thick horizontal bar at the bottom.
+
+Sequence diagram showing Direct Information Transfer from RNC to CN.
+
+**Figure 42: Information Request procedure. Successful operation.**
+
+The procedure is initiated with a DIRECT INFORMATION TRANSFER message sent from the RNC to the CN.
+
+The DIRECT INFORMATION TRANSFER message shall include the following IEs:
+
+- Inter-system Information Transfer Type,
+- Global RNC-ID,
+- CN Domain Indicator,
+
+The *Inter-system Information Transfer Type* IE indicates the nature of the transferred information.
+
+When the transferred information is of RIM nature, the *RIM Information* IE within the *RIM Transfer* IE shall contain a BSSGP RIM PDU. The final RAN destination node where the RIM information needs to be routed by the CN shall be indicated in the *RIM Routing Address* IE within the *RIM Transfer* IE and shall include either the identity of a GSM cell to identify a target BSS, or the identity of a Tracking Area and an eNB to identify the target eNB.
+
+#### 8.34.2.1.1 Successful Operation for GERAN Iu mode
+
+In the case of a Direct Information Transfer procedure initiated from GERAN Iu mode BSC, the final RAN destination node where the RIM information needs to be routed by the CN shall be indicated in the *RIM Routing Address* IE within the *RIM Transfer* IE and may include the identity of either a GSM cell to identify a target BSS or the *Target RNC-ID* IE including the *RAC* IE to identify a target RNC.
+
+### 8.34.2.2 Direct Information Transfer initiated from the CN
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN
+ Note right of RNC: RNC
+ CN->>RNC: DIRECT INFORMATION TRANSFER
+ Note left of CN:
+ Note right of RNC:
+```
+
+Sequence diagram showing the Direct Information Transfer procedure. A CN (Core Network) node sends a DIRECT INFORMATION TRANSFER message to an RNC (Radio Network Controller) node. The message is represented by a horizontal arrow pointing from the CN lifeline to the RNC lifeline. Both lifelines end in thick horizontal bars at the bottom.
+
+**Figure 43: Information Request procedure. Successful operation.**
+
+The procedure is initiated with a DIRECT INFORMATION TRANSFER message sent from the CN to the RNC.
+
+The DIRECT INFORMATION TRANSFER message shall include the following IEs:
+
+- Inter-system Information Transfer Type,
+- CN Domain Indicator,
+
+The DIRECT INFORMATION TRANSFER message may include the following IEs:
+
+- Global CN-ID.
+
+The *Global CN-ID* IE shall be included only when the CN node sending the message is not the default CN node of the RNC.
+
+The *Inter-system Information Transfer Type* IE indicates the nature of the transferred information.
+
+When the transferred information is of RIM nature, the *RIM Information* IE within the *RIM Transfer* IE shall contain a BSSGP RIM PDU. The *RIM Routing Address* IE shall not be present since the RNC is the final destination node.
+
+## 8.34.3 Abnormal Conditions
+
+Not applicable.
+
+# 8.35 Uplink Information Exchange
+
+## 8.35.1 General
+
+The purpose of the Uplink Information Exchange procedure is to transfer or request some information to the CN.
+
+This procedure uses connectionless signalling.
+
+## 8.35.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: UPLINK INFORMATION EXCHANGE REQUEST
+ Note right of CN:
+ CN-->>RNC: UPLINK INFORMATION EXCHANGE RESPONSE
+ Note left of RNC:
+
+```
+
+Sequence diagram illustrating the Uplink Information Exchange procedure. The RNC sends a UPLINK INFORMATION EXCHANGE REQUEST to the CN, and the CN responds with a UPLINK INFORMATION EXCHANGE RESPONSE.
+
+**Figure 44: Uplink Information Exchange procedure. Successful operation.**
+
+The procedure is initiated with an UPLINK INFORMATION EXCHANGE REQUEST message sent from the RNC to the CN.
+
+The UPLINK INFORMATION EXCHANGE REQUEST message shall contain the following IEs:
+
+- Information Exchange ID
+- Information Exchange Type
+- CN Domain Indicator
+- Global RNC-ID
+
+The *Information Exchange Type* IE indicates whether the RNC asks the CN to either transfer or request specific information. If the *Information Exchange Type* IE is set to the value "transfer", the RNC shall also include in the UPLINK INFORMATION EXCHANGE REQUEST message the *Information Transfer Type* IE which indicates the nature of the information transferred.
+
+If the *Information Exchange Type* IE is set to the value "request", the RNC shall also include in the UPLINK INFORMATION EXCHANGE REQUEST message the *Information Request Type* IE which indicates the nature of the information requested.
+
+When the transferred information in the *Information Transfer Type* IE relates to a Trace Session in the RNC, the *Trace Activation Indicator* IE indicates whether the Trace Session identified by the *Trace Reference* IE is activated or deactivated in the RNC. In case the Trace Session is activated, the *Equipments To Be Traced* IE gives the Equipment Identity of the UEs that the RNC has to trace. If the *Trace Recording Session Reference* IE, *Trace Collection Entity IP Address* IE, the *IMSI* IE and optionally the *Serving Cell Identifier* IE are included in the message, the CN shall take the information into account for anonymization of MDT data (TS 32.422 [10]).
+
+When the requested information in the *Information Request Type* IE relates to the Multicast Service list for a given UE identified by its Permanent NAS UE Identity in the *Information Request Type* IE, this requested information, i.e. the list of Multicast Services the UE has joined, shall be included in the *Information Requested* IE in the UPLINK INFORMATION EXCHANGE RESPONSE message.
+
+When the requested information in the *Information Request Type* IE relates to the IP Multicast Address and APN for one or several MBMS bearer service identified by their respective TMGIs in the *Information Request Type* IE, this requested information, i.e. IP Multicast Address and APN, shall be included in the *Information Requested* IE in the UPLINK INFORMATION EXCHANGE RESPONSE message.
+
+If the CN node is capable of processing the request or the transfer, the RNC shall be informed by the UPLINK INFORMATION EXCHANGE RESPONSE message. The UPLINK INFORMATION EXCHANGE RESPONSE message shall contain the *Information Exchange ID* IE and the *CN Domain Indicator* IE. If the RNC has not sent the UPLINK INFORMATION EXCHANGE REQUEST message to the default CN node, the UPLINK INFORMATION EXCHANGE RESPONSE message shall also include the *Global CN-ID* IE.
+
+Upon reception of the UPLINK INFORMATION EXCHANGE RESPONSE message including the IP Multicast Address and APN list in the *Information Requested* IE, the RNC shall store this information in the relevant MBMS Service Contexts.
+
+Upon reception of the UPLINK INFORMATION EXCHANGE RESPONSE message including the Multicast Service list in the *Information Requested* IE, the RNC shall perform, for each TMGI received, the corresponding UE linking as described in TS 25.346 [42].
+
+### 8.35.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: UPLINK INFORMATION EXCHANGE REQUEST
+ Note right of CN:
+ CN-->>RNC: UPLINK INFORMATION EXCHANGE FAILURE
+ Note left of RNC:
+```
+
+Sequence diagram showing an unsuccessful Uplink Information Exchange procedure between an RNC and a CN. The RNC sends a UPLINK INFORMATION EXCHANGE REQUEST to the CN, and the CN responds with a UPLINK INFORMATION EXCHANGE FAILURE.
+
+**Figure 45: Uplink Information Exchange procedure. Unsuccessful operation.**
+
+If the CN node is not capable of correctly processing the request or the transfer, the RNC shall be informed by the UPLINK INFORMATION EXCHANGE FAILURE message. The UPLINK INFORMATION EXCHANGE FAILURE message shall contain the *Information Exchange ID* IE and the *CN Domain Indicator* IE. If the RNC has not sent the UPLINK INFORMATION EXCHANGE REQUEST message to the default CN node, the UPLINK INFORMATION EXCHANGE FAILURE message shall include the *Global CN-ID* IE.
+
+The UPLINK INFORMATION EXCHANGE FAILURE message shall inform the RNC about the reason for unsuccessful operation with an appropriate cause value e.g. "MBMS - No Multicast Service For This UE", "MBMS - Unknown UE ID".
+
+### 8.35.4 Abnormal Conditions
+
+Not Applicable.
+
+## 8.36 MBMS Session Start
+
+### 8.36.1 General
+
+The purpose of the MBMS Session Start procedure is to request the UTRAN to notify UEs about an upcoming MBMS Session of a given MBMS Bearer Service and to establish a MBMS RAB and MBMS Iu signalling connection for this MBMS Session. The MBMS Session Start procedure is triggered by the CN (PS domain).
+
+The procedure uses connection oriented signalling.
+
+## 8.36.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of RNC:
+ CN->>RNC: MBMS SESSION START
+ RNC-->>CN: MBMS SESSION START RESPONSE
+ Note right of CN:
+
+```
+
+Sequence diagram showing the MBMS Session Start procedure. The CN (Core Network) sends an MBMS SESSION START message to the RNC (Radio Network Controller). The RNC responds with an MBMS SESSION START RESPONSE message.
+
+**Figure 46: MBMS Session Start procedure. Successful operation.**
+
+The CN initiates the procedure by sending a MBMS SESSION START message.
+
+The MBMS SESSION START message shall contain:
+
+- TMGI;
+- MBMS Bearer Service Type;
+- MBMS Session Identity, if available;
+- Iu Signalling Connection Identifier IE;
+- RAB parameters (including e.g. Allocation/Retention Priority);
+- PDP Type Information, if available;
+- PDP Type Information extension, if available;
+- MBMS Session Duration;
+- MBMS Service Area;
+- Frequency Layer Convergence Flag, if available;
+- RA List of Idle Mode UEs, if available;
+- Global CN-ID IE, only when the MBMS SESSION START message is sent from a CN node towards an RNC for which the sending CN node is not the default CN node;
+- MBMS Session Repetition Number, if available;
+- Time to MBMS Data Transfer;
+- MBMS Counting Information, if available.
+
+Upon reception of the MBMS SESSION START message, the RNC shall store the *Iu Signalling Connection Identifier* IE for the duration of the MBMS Iu signalling connection. The *Iu Signalling Connection Identifier* IE contains an Iu signalling connection identifier which is allocated by the CN. The value for the *Iu Signalling Connection Identifier* IE shall be allocated so as to uniquely identify an Iu signalling connection for the involved CN node.
+
+The *Global CN-ID* IE contains the identity of the CN node that sent the MBMS SESSION START message, and it shall, if included, be stored together with the Iu signalling connection identifier. If the *Global CN-ID* IE is not included, the MBMS SESSION START message shall be considered as coming from the default CN node.
+
+Upon reception of the MBMS SESSION START message, the RNC shall store, if not already, and remember the *TMGI* IE, the *RAB parameters* IE and the other attributes of the session as part of the MBMS Service Context. The *TMGI* IE contains the TMGI identifier which uniquely identifies the MBMS Bearer Service.
+
+If the *MBMS Bearer Service Type* IE is set to "Multicast", upon reception of the MBMS SESSION START message, the RNC shall initiate allocation of requested resources for the MBMS RAB at a proper point in time if at least one of the following two conditions is fulfilled:
+
+- the RNC controls at least one cell contained in the indicated MBMS Service Area and, if the *RA List of Idle Mode UEs* IE is included in MBMS SESSION START message, at least one RNC's RA is contained in this list, or if *Empty/Full RA List of Idle Mode UEs* IE included in MBMS SESSION START message is set to "fulllist",
+- the RNC serves UEs consuming radio resources from cells contained in the indicated MBMS Service Area.
+
+If no mapping is configured for a certain MBMS Service Area Identity in the *MBMS Service Area* IE in the RNC it shall simply ignore it
+
+The RNC may optimise the point in time when the resource allocation is initiated based on the *Time to MBMS Data Transfer* IE.
+
+In case the *RA List of Idle Mode UEs* IE is included in MBMS SESSION START message but none of above conditions is fulfilled, the RNC may decide to wait for either an update of the RA List of Idle Mode UEs or a UE linking to finally establish the MBMS RAB. If the RNC decides so, it shall report it immediately to the CN in the MBMS SESSION START RESPONSE message with the cause value "Successful MBMS Session Start - No Data Bearer Necessary" and maintain an Iu signalling connection.
+
+If the *Empty/Full RA List of Idle Mode UEs* IE included in MBMS SESSION START message is set to "fulllist", the RNC shall initiate the MBMS Notification over the Uu interface in all the cells under its control which belong to the indicated MBMS service area.
+
+If the *MBMS Bearer Service Type* IE is set to "Broadcast", the *MBMS Counting Information IE* shall be included in the MBMS SESSION START message. If the *MBMS Counting Information IE* is set to "counting", the RNC may apply MBMS counting.
+
+If the *MBMS Bearer Service Type* IE is set to "Broadcast" upon reception of the MBMS SESSION START message, the RNC shall initiate allocation of requested resources for the MBMS RAB at a proper point in time if it controls at least one cell contained in the indicated MBMS Service Area.
+
+If the *MBMS Bearer Service Type* IE is set to "Multicast" the *MBMS Counting Information IE* shall be ignored.
+
+The allocation of requested resources shall be made according to the values of the *Allocation/Retention Priority IE* (priority level, pre-emption indicators) and the resource situation as follows:
+
+- The RNC shall consider the priority level of the requested MBMS RAB, when deciding on the resource allocation.
+- The *Queuing Allowed* IE shall be ignored for MBMS RAB.
+- The priority levels and the pre-emption indicators may (singularly or in combination) be used to determine whether the MBMS RAB establishment has to be performed unconditionally and immediately. If the requested MBMS RAB is marked as "may trigger pre-emption" and the resource situation requires so, the RNC may trigger the pre-emption procedure which may then cause the forced release of a lower priority RAB which is marked as "pre-emptable". Whilst the process and the extent of the pre-emption procedure is operator-dependent, the pre-emption indicators, if given in the MBMS SESSION START message, shall be treated as follows:
+ 1. If the *Pre-emption Capability* IE is set to "may trigger pre-emption", then this allocation request may trigger the pre-emption procedure. UTRAN shall only pre-empt RABs (other MBMS RABs or UE specific RABs) with lower priority, in ascending order of priority.
+ 2. If the *Pre-emption Capability* IE is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption procedure.
+ 3. If the *Pre-emption Vulnerability* IE is set to "pre-emptable", then this connection shall be included in the pre-emption process.
+
+4. If the *Pre-emption Vulnerability* IE is set to "not pre-emptable", then this connection shall not be included in the pre-emption process.
+ 5. If the *Priority Level* IE is set to "no priority" the given values for the *Pre-emption Capability* IE and *Pre-emption Vulnerability* IE shall not be considered. Instead the values "shall not trigger pre-emption" and "not pre-emptable" shall prevail.
+- If the *Allocation/Retention Priority* IE is not given in the MBMS SESSION START message, the allocation request shall not trigger the pre-emption process and the connection may be pre-empted and considered to have the value "lowest" as priority level. Moreover, queuing shall not be allowed.
+
+The UTRAN shall use the *PDP Type Information* IE or *PDP Type Information extension* IE to configure any compression algorithms.
+
+The MBMS SESSION START message may contain the *MBMS Synchronisation Information* IE, consisting of the
+
+- *MBMS HC Indicator* IE;
+- *IP Multicast Address* IE;
+- *GTP DL TEID* IE;
+- *IP Source Address* IE, if available.
+
+In case of successful MBMS RAB establishment, if the *MBMS Synchronisation Information* IE was not received within the MBMS SESSION START message, the RNC shall include the *Transport Layer Address* IE and the *Iu Transport Association* IE in the MBMS SESSION START RESPONSE message. The RNC may answer successfully even though the MBMS resources have not been established in all relevant cells.
+
+If NNSF is active, the RNC may receive from several CN nodes for a certain MBMS Bearer Service the MBMS SESSION START message. In this case, if the RNC decides to establish the requested MBMS RAB, it shall only establish one MBMS Iu bearer and shall inform the selected CN node accordingly i.e. with MBMS SESSION START RESPONSE message including the *Transport Layer Address* IE and the *Iu Transport Association* IE.
+
+If the *MBMS Synchronisation Information* IE was received within the MBMS SESSION START message, even if the RNC received related information more than once due to NNSF, if supported, it shall not include the *Transport Layer Address* IE and the *Iu Transport Association* IE in the MBMS SESSION START RESPONSE message and shall join the indicated IP Multicast group only once for the indicated MBMS Service Id. In case of successful joining the indicated IP Multicast group, the RNC shall inform all the CN nodes from which it has received a MBMS SESSION START message for that MBMS service with the *Cause* IE set to "Successful MBMS Session Start – IP Multicast Bearer established". If the *IP Source Address* IE is contained in the *MBMS Synchronisation Information* IE, the RNC shall use this information for joining the IP Multicast group.
+
+If the RNC receives from several CN nodes for a certain MBMS Bearer Service the MBMS SESSION START message and all the MBMS SESSION START messages include the *RA List of Idle Mode UEs* IE, the RNC shall, if supported, maintain an MBMS Iu signalling connection towards all the CN nodes and inform them accordingly i.e. with MBMS SESSION START RESPONSE message and cause value "Successful MBMS Session Start - No Data Bearer Necessary" to all the CN nodes except the one, if any, towards which the RNC confirmed the successful MBMS RAB establishment.
+
+The *MBMS Session Repetition Number* IE may be included in the MBMS SESSION START message in case the *MBMS Session Identity* IE is included in the same message. The *MBMS Session Repetition Number* IE may be used by RNC to recognise retransmissions of a particular session of a MBMS Bearer Service with identical contents. This IE may be used for counting purpose.
+
+When the *Frequency Layer Convergence Flag* IE is set to "no-FLC-flag", the RNC is being requested to not apply any frequency layer convergence mechanism. The service shall then be delivered to all cells of all the MBMS Service Area Identities indicated in the *MBMS Service Area* IE.
+
+Transmission and reception of a MBMS SESSION START RESPONSE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.36.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN:
+ CN->>RNC: MBMS SESSION START
+ Note right of RNC:
+ RNC-->>CN: MBMS SESSION START FAILURE
+ Note right of CN:
+
+```
+
+Sequence diagram showing the MBMS Session Start procedure resulting in a failure. The diagram shows two lifelines: RNC and CN. The CN sends an MBMS SESSION START message to the RNC. The RNC responds with an MBMS SESSION START FAILURE message back to the CN.
+
+**Figure 47: MBMS Session Start procedure. Unsuccessful operation.**
+
+If the RNC is not capable of correctly processing the request (e.g. the MBMS resources could not be established at all in any cell), the CN shall be informed by the MBMS SESSION START FAILURE message.
+
+If the *MBMS Bearer Service Type* IE is set to "Broadcast" upon reception of the MBMS SESSION START message and the RNC doesn't have any cell contained in the indicated MBMS Service Area, it shall report it immediately to the CN in the MBMS SESSION START FAILURE message with the cause value "MBMS - No cell in MBMS Service Area".
+
+If NNSF is active and the RNC received from several CN nodes for a certain MBMS Bearer Service the MBMS SESSION START message, but not all of the MBMS SESSION START messages include the *RA List of Idle Mode UEs* IE, the RNC shall inform the respective CN nodes accordingly i.e. with MBMS SESSION START FAILURE message and cause value "MBMS - Superseded Due To NNSF" to all the CN nodes except the one towards which the RNC confirmed the successful MBMS RAB establishment with MBMS SESSION START RESPONSE message.
+
+When UTRAN reports failure of the MBMS Session Start procedure, the cause value should be precise enough to enable the core network to know the reason for the failure. Typical cause values are: "MBMS - Superseded Due To NNSF", "Requested Traffic Class not Available", "Invalid RAB Parameters Value", "Requested Maximum Bit Rate not Available", "Requested Guaranteed Bit Rate not Available", "Requested Transfer Delay not Achievable", "Invalid RAB Parameters Combination", "Condition Violation for Guaranteed Bit Rate", "Iu Transport Connection Failed to Establish", "No Resource Available".
+
+Transmission and reception of a MBMS SESSION START FAILURE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.36.4 Abnormal Conditions
+
+If, for a MBMS RAB requested to be set up, the *PDP Type Information* IE and/or *PDP Type Information extension* IE is not present, the RNC shall continue with the procedure.
+
+If an MBMS SESSION START message from a given CN Node provides a *TMGI* IE that is used for an already established and running MBMS Session provided by the same CN Node, and the indicated *MBMS Service Area* IE refers to an MBMS Service Area that is partially or completely overlapping with the MBMS Service Area of the already established and running MBMS Session, then the RNC shall return an MBMS SESSION START FAILURE message with the cause value "TMGI in Use and overlapping MBMS Service Area".
+
+If an MBMS SESSION START message from a given CN Node provides a *TMGI* IE that is used for an already established and running MBMS Session provided by another CN Node, and the indicated *MBMS Service Area* IE refers to a different MBMS Service Area that is partially overlapping with the MBMS Service Area of the already established and running MBMS Session, then the RNC shall return an MBMS SESSION START FAILURE message with the cause value "TMGI in Use and overlapping MBMS Service Area".
+
+## 8.37 MBMS Session Update
+
+### 8.37.1 General
+
+The purpose of the MBMS Session Update procedure is to inform the RNC during a MBMS Session whenever the RA List of Idle Mode UEs changes compared to one previously sent. The MBMS Session Update procedure is triggered by the CN (PS domain).
+
+The procedure uses connection oriented signalling.
+
+### 8.37.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: MBMS SESSION UPDATE
+ Note right of RNC: RNC processes update
+ RNC->>CN: MBMS SESSION UPDATE RESPONSE
+
+```
+
+Sequence diagram showing the MBMS Session Update procedure. The CN sends an MBMS SESSION UPDATE message to the RNC, and the RNC responds with an MBMS SESSION UPDATE RESPONSE message.
+
+**Figure 48: MBMS Session Update procedure. Successful operation.**
+
+The CN initiates the procedure by sending a MBMS SESSION UPDATE message.
+
+The MBMS SESSION UPDATE message shall contain the *Delta RA List of Idle Mode UEs* IE and the *Session Update ID* IE.
+
+Upon reception of the MBMS SESSION UPDATE message, if a MBMS RAB has already been established, the RNC shall initiate allocation of additional MBMS radio resources for this MBMS RAB if the RNC controls at least one cell that is part of both the MBMS Service Area and one of the RNC's RAs indicated in the *New RA List of Idle Mode UEs* IE, if this IE is included in the *Delta RA List of Idle Mode UEs* IE group. The RNC may release the existing MBMS radio resources for the cells part of the RNC's RAs indicated in the *RA List with No Idle Mode UEs Any More* IE, if this IE is included in the *Delta RA List of Idle Mode UEs* IE group.
+
+Upon reception of the MBMS SESSION UPDATE message, if no MBMS RAB has yet been established, the RNC shall establish the MBMS RAB if the RNC controls at least one cell that is part of both the MBMS Service Area and one of the RNC's RAs indicated in the *New RA List of Idle Mode UEs* IE, if this IE is included in the *Delta RA List of Idle Mode UEs* IE group. If the previous condition is not fulfilled, the RNC may decide to wait for either another update of the RA List of Idle Mode UEs or a UE linking to finally establish the MBMS RAB.
+
+In case of successful MBMS RAB establishment, the RNC shall include the *Transport Layer Address* IE and the *Iu Transport Association* IE in the MBMS SESSION UPDATE RESPONSE message.
+
+When the update of the RA List of Idle Mode UEs is successfully executed, the UTRAN shall report it to the CN in the MBMS SESSION UPDATE RESPONSE message, which shall include the same *Session Update ID* IE as received in the MBMS SESSION UPDATE message. The RNC may answer successfully even though MBMS resources have not been established in all relevant cells.
+
+Transmission and reception of a MBMS SESSION UPDATE RESPONSE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.37.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of RNC:
+ Note right of CN:
+ CN->>RNC: MBMS SESSION UPDATE
+ RNC-->>CN: MBMS SESSION UPDATE FAILURE
+```
+
+Sequence diagram for MBMS Session Update procedure. Unsuccessful operation. The diagram shows two lifelines: RNC and CN. The CN sends an MBMS SESSION UPDATE message to the RNC. The RNC responds with an MBMS SESSION UPDATE FAILURE message to the CN.
+
+**Figure 49: MBMS Session Update procedure. Unsuccessful operation.**
+
+If the RNC is not capable of correctly processing the request (e.g. additional MBMS resources could not be established at all in any cell), the CN shall be informed by the MBMS SESSION UPDATE FAILURE message, which shall include the same *Session Update ID* IE as received in the MBMS SESSION UPDATE message.
+
+Transmission and reception of a MBMS SESSION UPDATE FAILURE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.37.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.38 MBMS Session Stop
+
+### 8.38.1 General
+
+The purpose of the MBMS Session Stop procedure is to request the UTRAN to notify UEs about the end of a given MBMS Session and to release the corresponding MBMS RAB and MBMS Iu signalling connection for this MBMS Session. The MBMS RAB Session Stop procedure may also be used as the last MBMS session stop to make the RNC aware that a certain Multicast Service is no longer available. The MBMS Session Stop procedure is triggered by the CN (PS domain).
+
+The procedure uses connection oriented signalling.
+
+### 8.38.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of RNC:
+ Note right of CN:
+ CN->>RNC: MBMS SESSION STOP
+ RNC-->>CN: MBMS SESSION STOP RESPONSE
+```
+
+Sequence diagram for MBMS Session Stop procedure. Successful operation. The diagram shows two lifelines: RNC and CN. The CN sends an MBMS SESSION STOP message to the RNC. The RNC responds with an MBMS SESSION STOP RESPONSE message to the CN.
+
+**Figure 50: MBMS Session Stop procedure. Successful operation.**
+
+The CN initiates the procedure by sending a MBMS SESSION STOP message.
+
+Upon reception of the MBMS SESSION STOP message, the RNC shall release all allocated resources for the MBMS RAB, including the MBMS Iu signalling connection used for this MBMS RAB.
+
+The MBMS SESSION STOP message shall include the *MBMS CN De-Registration* IE. If the *MBMS CN De-Registration* IE is set to the value "deregister", the RNC shall also remove all associated MBMS Service Context(s) and release all allocated MBMS resources for the MBMS Bearer Service.
+
+The RNC does not need to wait for the release of all UTRAN radio resources before returning the MBMS SESSION STOP RESPONSE message.
+
+In case of successful release of the MBMS Iu signalling connection, after the MBMS SESSION STOP RESPONSE message has been sent, the CN shall not send further RANAP connection-oriented messages on this particular connection.
+
+Transmission and reception of a MBMS SESSION STOP RESPONSE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.38.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.39 MBMS UE Linking
+
+### 8.39.1 General
+
+The purpose of the MBMS UE Linking procedure is to make the RNC aware that a given UE, with existing Iu-ps signalling connection, joined and/or left one or several Multicast Services.
+
+The procedure uses connection oriented signalling.
+
+### 8.39.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: UE joined/left service
+ CN->>RNC: MBMS UE LINKING REQUEST
+ Note right of RNC: UE linked/unlinked
+ RNC->>CN: MBMS UE LINKING RESPONSE
+```
+
+Sequence diagram of the MBMS UE Linking procedure. The CN sends an MBMS UE LINKING REQUEST to the RNC, and the RNC responds with an MBMS UE LINKING RESPONSE.
+
+**Figure 51: MBMS UE Linking procedure. Successful operation.**
+
+The CN initiates the procedure by sending a MBMS UE LINKING REQUEST message.
+
+The MBMS UE LINKING REQUEST message shall contain the following IEs:
+
+- a list of one or several TMGIs, each identifying the MBMS Bearer Service that the UE joined or left and which has not yet been linked or unlinked respectively in the UTRAN;
+- for each of the MBMS Bearer Services that the UE joined;
+- the PTP RAB ID.
+
+Upon reception of the MBMS UE LINKING REQUEST message, for each TMGI received identifying the MBMS Bearer Service that the UE joined and which has not yet been linked in the UTRAN, the RNC shall perform the corresponding UE linking as described in TS 25.346 [42].
+
+Upon reception of the MBMS UE LINKING REQUEST message, for each TMGI received identifying the MBMS Bearer Service that the UE left and which has not yet been de-linked in the UTRAN, the RNC shall perform the corresponding UE de-linking as described in TS 25.346 [42].
+
+After handling all received TMGI(s), the RNC shall only report to the CN in the MBMS UE LINKING RESPONSE message the unsuccessful linking(s)/de-linking(s) with an appropriate cause value e.g. "MBMS - UE Linking Already Done", "MBMS - UE De-Linking Failure - No Existing UE Linking".
+
+Transmission and reception of a MBMS UE LINKING RESPONSE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.39.3 Unsuccessful Operation
+
+The unsuccessful operation for this Class 1 Elementary procedure is described under the Successful Operation chapter.
+
+### 8.39.4 Abnormal Conditions
+
+Upon reception of the MBMS UE LINKING REQUEST message, if for a given TMGI received identifying the MBMS Bearer Service that the UE joined, the linking has already been done in the UTRAN, the RNC shall consider this linking as unsuccessful but shall proceed with the other ones.
+
+Upon reception of the MBMS UE LINKING REQUEST message, if a given TMGI received identifying the MBMS Bearer Service that the UE left, cannot be found in the UE context, the RNC shall consider this de-linking as unsuccessful but shall proceed with the other ones.
+
+## 8.40 MBMS Registration
+
+### 8.40.1 General
+
+The purpose of the MBMS Registration procedure is to request the CN (PS domain) to register or de-register the RNC for a certain Multicast Service.
+
+The procedure uses connectionless signalling, unless the procedure is used to request CN to de-register the RNC for a Multicast Service which has an existing Iu signalling connection towards the RNC i.e. during a MBMS Session. In this last case, the procedure uses connection oriented signalling.
+
+### 8.40.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: MBMS REGISTRATION REQUEST
+ Note right of CN:
+ CN-->>RNC: MBMS REGISTRATION RESPONSE
+ Note left of RNC:
+```
+
+The diagram illustrates the interaction between an RNC (Radio Network Controller) and a CN (Core Network) for a successful MBMS Registration procedure. It is a sequence diagram with two vertical lifelines. The RNC lifeline is on the left and the CN lifeline is on the right. A solid horizontal arrow points from the RNC to the CN, labeled "MBMS REGISTRATION REQUEST". A solid horizontal arrow points from the CN back to the RNC, labeled "MBMS REGISTRATION RESPONSE". Both lifelines end with a thick horizontal bar at the bottom.
+
+Sequence diagram of the MBMS Registration procedure showing a successful operation between an RNC and a CN.
+
+**Figure 52: MBMS Registration procedure. Successful operation.**
+
+The RNC initiates the procedure by sending a MBMS REGISTRATION REQUEST message.
+
+The MBMS REGISTRATION REQUEST message shall contain the following IEs:
+
+- MBMS Registration Request type;
+- TMGI;
+- The associated IP Multicast Address and the APN corresponding to the MBMS Bearer Service identified by the TMGI, only in the case the *MBMS Registration Request type* IE is set to "register";
+- Global RNC-ID, if connectionless signalling.
+
+If the CN node is capable of processing the request, the RNC shall be informed by the MBMS REGISTRATION RESPONSE message.
+
+In case of connectionless signalling the MBMS REGISTRATION RESPONSE message shall contain the same TMGI as received in the MBMS REGISTRATION REQUEST message.
+
+If the RNC has not sent the MBMS REGISTRATION REQUEST message with the *MBMS Registration Request Type* IE set to "register", to the default CN node, the MBMS REGISTRATION RESPONSE message shall also include the *Global CN-ID* IE.
+
+Upon reception of the MBMS REGISTRATION RESPONSE message as a response to a connectionless MBMS REGISTRATION REQUEST message with the *MBMS Registration Request Type* IE set to "deregister", the RNC shall remove all associated MBMS resources and context(s) corresponding to the MBMS Bearer Service identified by the TMGI included in the MBMS REGISTRATION REQUEST message.
+
+Upon reception of the MBMS REGISTRATION RESPONSE message as a response to a connection oriented MBMS REGISTRATION REQUEST message with the *MBMS Registration Request Type* IE set to "deregister", the RNC shall release the MBMS Iu signalling connection and the RAB, if any, identified by the TMGI included in the MBMS REGISTRATION REQUEST message.
+
+Transmission and reception of a MBMS REGISTRATION RESPONSE message terminate the procedure in the CN and in the UTRAN respectively.
+
+### 8.40.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: MBMS REGISTRATION REQUEST
+ Note right of CN:
+ CN-->>RNC: MBMS REGISTRATION FAILURE
+ Note left of RNC:
+```
+
+Sequence diagram showing the MBMS Registration procedure for an unsuccessful operation. The RNC sends an MBMS REGISTRATION REQUEST to the CN, and the CN responds with an MBMS REGISTRATION FAILURE.
+
+**Figure 53: MBMS Registration procedure. Unsuccessful operation.**
+
+If the CN node is not capable of correctly processing the request, the RNC shall be informed by the MBMS REGISTRATION FAILURE message.
+
+In case of connectionless signalling, the MBMS REGISTRATION FAILURE message shall contain the same TMGI as received in the MBMS REGISTRATION REQUEST message.
+
+The MBMS REGISTRATION FAILURE message shall inform the RNC about the reason for unsuccessful operation thanks to appropriate cause value e.g. "TMGI Unknown", "IP Multicast Address And APN Not Valid", "MBMS De-Registration Rejected Due To Implicit Registration", "MBMS - Request Superseded", "MBMS De-Registration During Session Not Allowed".
+
+In case of connectionless signalling, if the RNC has not sent the MBMS REGISTRATION REQUEST message with the *MBMS Registration Request Type* IE set to "register", to the default CN node, the MBMS REGISTRATION FAILURE message shall also include the *Global CN-ID* IE.
+
+Transmission and reception of a MBMS REGISTRATION FAILURE message terminate the procedure in the CN and in the UTRAN respectively.
+
+## 8.40.4 Abnormal Conditions
+
+Not applicable.
+
+# 8.41 MBMS CN De-Registration
+
+## 8.41.1 General
+
+The purpose of the MBMS CN De-Registration procedure is to make the RNC aware that a certain Multicast Service is no longer available. The MBMS CN De-Registration procedure is triggered by the CN (PS domain).
+
+The procedure uses connectionless signalling.
+
+## 8.41.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant CN
+ participant RNC
+ Note left of CN: CN initiates procedure
+ CN->>RNC: MBMS CN DE-REGISTRATION REQUEST
+ Note right of RNC: RNC removes context and resources
+ RNC->>CN: MBMS CN DE-REGISTRATION RESPONSE
+```
+
+Sequence diagram of the MBMS CN De-Registration procedure. It shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled 'MBMS CN DE-REGISTRATION REQUEST'. A second horizontal arrow points from the RNC lifeline to the CN lifeline, labeled 'MBMS CN DE-REGISTRATION RESPONSE'. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 54: MBMS CN De-Registration procedure. Successful operation.**
+
+The CN initiates the procedure by sending a MBMS CN DE-REGISTRATION REQUEST message.
+
+The MBMS CN DE-REGISTRATION REQUEST message shall contain the following IEs:
+
+- TMGI;
+- Global CN-ID IE, only when the MBMS CN DE-REGISTRATION REQUEST message is sent from a CN node towards an RNC for which the sending CN node is not the default CN node.
+
+If the *Global CN-ID* IE is not included, the MBMS CN DE-REGISTRATION REQUEST message shall be considered as coming from the default CN node.
+
+Upon reception of the MBMS CN DE-REGISTRATION REQUEST message, the RNC shall remove all associated MBMS context(s) and resources corresponding to the MBMS Bearer Service identified by the indicated TMGI and shall report it to the CN by sending the MBMS CN DE-REGISTRATION RESPONSE message.
+
+Upon reception of the MBMS CN DE-REGISTRATION REQUEST message, if no existing MBMS Bearer Service can be identified by the indicated TMGI in the RNC, it shall consider this MBMS CN De-Registration procedure unsuccessful and shall report it to the CN by sending the MBMS CN DE-REGISTRATION RESPONSE message with the appropriate cause value e.g. "TMGI unknown".
+
+The MBMS CN DE-REGISTRATION RESPONSE message shall contain the *Global RNC-ID* IE and the same TMGI as received in the MBMS CN DE-REGISTRATION REQUEST message.
+
+Transmission and reception of a MBMS CN DE-REGISTRATION RESPONSE message terminate the procedure in the UTRAN and in the CN respectively.
+
+### 8.41.3 Unsuccessful Operation
+
+The unsuccessful operation for this Class 1 Elementary procedure is described under the Successful Operation chapter.
+
+### 8.41.4 Abnormal Conditions
+
+If NNSF is active, the RNC may receive from several CN nodes for a certain MBMS Bearer Service the MBMS CN DE-REGISTRATION REQUEST message. In this case the RNC will only proceed with the first MBMS CN DE-REGISTRATION REQUEST message received and will inform the respective CN nodes accordingly i.e. with MBMS CN DE-REGISTRATION RESPONSE message and cause value "TMGI unknown" to all the CN nodes except the one towards which the RNC confirmed the successful the MBMS CN De-Registration procedure with MBMS CN DE-REGISTRATION RESPONSE message including no cause value.
+
+## 8.42 MBMS RAB Establishment Indication
+
+### 8.42.1 General
+
+The purpose of the MBMS RAB Establishment Indication procedure is to inform the CN (PS domain) of the establishment of the MBMS RAB corresponding to the MBMS Iu signalling connection used for this procedure.
+
+The procedure uses connection oriented signalling.
+
+### 8.42.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: MBMS RAB ESTABLISHMENT INDICATION
+ Note right of CN:
+ Note left of RNC:
+ Note right of CN:
+```
+
+Sequence diagram showing the MBMS RAB Establishment Indication procedure. An RNC box is on the left and a CN box is on the right. A horizontal arrow points from the RNC to the CN, labeled 'MBMS RAB ESTABLISHMENT INDICATION'. Both boxes have vertical lines extending downwards to a horizontal bar at the bottom, representing lifelines.
+
+**Figure 55: MBMS RAB Establishment Indication procedure. Successful operation.**
+
+When the RNC has not yet established the MBMS RAB for a particular Multicast Service and is informed that a given UE joined this particular Multicast Service, the RNC shall initiate the MBMS RAB Establishment Indication procedure and send the MBMS RAB ESTABLISHMENT INDICATION message to the CN. If NNSF is active, the selection of the CN node is implementation dependant.
+
+The MBMS RAB ESTABLISHMENT INDICATION message shall include the *Transport Layer Address* IE and the *Iu Transport Association* IE.
+
+### 8.42.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.43 MBMS RAB Release
+
+### 8.43.1 General
+
+The purpose of the MBMS RAB Release procedure is to enable the UTRAN to request the release of an MBMS RAB. The MBMS RAB is defined for the PS domain only.
+
+The procedure uses connection oriented signalling.
+
+### 8.43.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: MBMS RAB RELEASE REQUEST
+ Note right of CN:
+ CN-->>RNC: MBMS RAB RELEASE
+ Note left of RNC:
+ Note right of CN:
+```
+
+Sequence diagram for MBMS RAB Release procedure. Successful operation. The diagram shows two vertical lifelines for RNC and CN. The RNC sends an 'MBMS RAB RELEASE REQUEST' message to the CN. The CN responds with an 'MBMS RAB RELEASE' message back to the RNC. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 56: MBMS RAB Release procedure. Successful operation.**
+
+The RNC initiates the procedure by generating a MBMS RAB RELEASE REQUEST message towards the CN. The MBMS RAB RELEASE REQUEST message is sent on the Iu connection related to the MBMS RAB to be released. The included cause value indicates the reason for the release, e.g. "RAB pre-empted", "Release due to UTRAN Generated Reason", "MBMS - No Data Bearer Necessary".
+
+The CN should according to the MBMS RAB RELEASE REQUEST message initiate the release of all MBMS resources related to the Iu connection.
+
+For MBMS Multicast service the Iu signalling connection should not be released.
+
+The RNC may at reception of MBMS RAB RELEASE initiate release of the related MBMS bearer resources.
+
+#### **MBMS Broadcast service, interaction with MBMS Session Stop:**
+
+For MBMS Broadcast service the CN may initiate the appropriate release procedure for the MBMS Session related to the Iu signalling connection and invoke the MBMS Session Stop procedure.
+
+### 8.43.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: MBMS RAB RELEASE REQUEST
+ Note right of CN:
+ CN-->>RNC: MBMS RAB RELEASE FAILURE
+ Note left of RNC:
+ Note right of CN:
+```
+
+Sequence diagram for MBMS RAB Release procedure. Unsuccessful operation. The diagram shows two vertical lifelines for RNC and CN. The RNC sends an 'MBMS RAB RELEASE REQUEST' message to the CN. The CN responds with an 'MBMS RAB RELEASE FAILURE' message back to the RNC. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 57: MBMS RAB RELEASE procedure. Unsuccessful operation.**
+
+If the CN node is not capable of correctly processing the request, the RNC shall be informed by the MBMS RAB RELEASE FAILURE message.
+
+The MBMS RAB RELEASE FAILURE message shall inform the RNC about the reason for the unsuccessful operation with an appropriate cause value.
+
+### 8.43.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.44 Enhanced Relocation Complete
+
+### 8.44.1 General
+
+The purpose of the Enhanced Relocation Complete procedure is to inform the CN that the resources have been allocated by the target RNC. The target RNC provides necessary information to the CN to switch the user plane to the target RNC.
+
+The procedure uses connection oriented signalling.
+
+### 8.44.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: ENHANCED RELOCATION COMPLETE REQUEST
+ Note right of CN:
+ CN-->>RNC: ENHANCED RELOCATION COMPLETE RESPONSE
+
+```
+
+Sequence diagram showing the Enhanced Relocation Complete procedure. The RNC sends an ENHANCED RELOCATION COMPLETE REQUEST message to the CN, and the CN responds with an ENHANCED RELOCATION COMPLETE RESPONSE message.
+
+**Figure 58: Enhanced Relocation Complete procedure. Successful operation.**
+
+The RNC initiates the procedure by sending the ENHANCED RELOCATION COMPLETE REQUEST message to the CN.
+
+If the *RABs Setup List* IE in the ENHANCED RELOCATION COMPLETE REQUEST message does not include all RABs previously established for the UE, the CN shall consider the non included RABs as implicitly released by the RNC.
+
+For each RAB the resource allocation was successful towards the PS domain or towards the CS domain when an ALCAP is not used, the RNC shall include the *Transport Layer Address* IE and the *Iu Transport Association* IE in the *RABs Setup List* IE in the ENHANCED RELOCATION COMPLETE REQUEST message. If any alternative RAB parameter values have been used when allocating the resources, these RAB parameter values shall be included in the ENHANCED RELOCATION COMPLETE REQUEST message within the *Assigned RAB Parameter Values* IE.
+
+NOTE: If ALCAP is not used, the RNC shall include the same kind of TNL information (i.e. IPv4 or IPv6) as received from the source RNC in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message.
+
+The target RNC shall include the *Chosen Integrity Protection Algorithm* IE (*Chosen Encryption Algorithm* IE respectively) within the ENHANCED RELOCATION COMPLETE REQUEST message, if, and only if the *Integrity Protection Key* IE (*Ciphering Key* IE respectively) was included within the *Source RNC To Target RNC Transparent Container* IE of the RANAP ENHANCED RELOCATION INFORMATION message.
+
+If the *Higher bitrates than 16 Mbps flag* IE is included in the ENHANCED RELOCATION COMPLETE REQUEST message then the CN shall, if supported, use the IE as described in TS 23.060 [21].
+
+If the *CSG Id* IE and the *Cell Access Mode* IE set to "hybrid" are received in the ENHANCED RELOCATION COMPLETE REQUEST message, the CN shall provide the *CSG Membership Status* IE of the UE to the target side.
+
+After all necessary updates including the DL transport layer information have been successfully completed in the CN, the CN shall send the ENHANCED RELOCATION COMPLETE RESPONSE message to the RNC.
+
+In case the CN failed to setup for at least one of the RABs included the *RABs Setup List* IE in the ENHANCED RELOCATION COMPLETE REQUEST message, the CN shall include the RABs it failed to setup in the *RABs To Be Released List* IE in the ENHANCED RELOCATION COMPLETE RESPONSE message. In this case, the RNC shall
+
+release the resource for the RABs and the RNC shall regard the RABs indicated in the *RABs To Be Released List* IE as being fully released.
+
+The ENHANCED RELOCATION COMPLETE RESPONSE message shall contain the *User Plane Information* IE.
+
+The ENHANCED RELOCATION COMPLETE RESPONSE message shall contain the *Transport Layer Address* IE and the *Binding ID* IE for each RAB towards the CS domain when an ALCAP is used.
+
+In case the CN decides to change the uplink transport layer information when an ALCAP is not used it may include the *Transport Layer Address* IE and the *Binding ID* IE within the *RABs Setup List* IE in the ENHANCED RELOCATION COMPLETE RESPONSE message.
+
+The ENHANCED RELOCATION COMPLETE RESPONSE message may contain the *RAB Parameters* IE for each RAB towards the CS domain in RAB Setup List.
+
+If the *RAB Parameters* IE is included in the ENHANCED RELOCATION COMPLETE RESPONSE the RNC shall
+
+- replace the previously provided RAB Parameter for the RAB. The RNC shall use the received RAB Parameter for the RAB.
+
+If the *RAB Parameters* IE is not contained in the ENHANCED RELOCATION COMPLETE RESPONSE message, the RNC shall use the previously provided RAB parameters.
+
+The ENHANCED RELOCATION COMPLETE RESPONSE message may contain the *UE Aggregate Maximum Bit Rate* IE to control the aggregate data rate of non-GBR traffic for this UE.
+
+If the *UE Aggregate Maximum Bit Rate* IE is contained in the ENHANCED RELOCATION COMPLETE RESPONSE message, the RNC shall, if supported,
+
+- replace the previously provided UE Aggregate Maximum Bit Rate Parameter for this UE. The RNC shall use the received UE Aggregate Maximum Bit Rate Parameter for this UE.
+
+If the *UE Aggregate Maximum Bit Rate* IE is not contained in the ENHANCED RELOCATION COMPLETE RESPONSE message, the RNC shall, if supported, use the previously provided UE Aggregate Maximum Bit Rate Parameter.
+
+In case SIPTO at Iu-PS functionality is supported by the UTRAN, the following applies in addition for the successful operation of Enhanced Relocation Complete procedure:
+
+- If the *MSISDN* IE is present in the ENHANCED RELOCATION COMPLETE RESPONSE message, then the UTRAN may offload the RAB(s) where the *Offload RAB Parameters* IE is present in the *RABs Setup Item IEs* IE. The *Access Point Name* IE and the *Charging Characteristics* IE within the *Offload RAB Parameters* IE and the *MSISDN* IE may only be used for the SIPTO at Iu-PS function and according to the description in TS 23.060 [21].
+
+If the *CSG Membership Status* IE is included in the ENHANCED RELOCATION COMPLETE RESPONSE message the RAN shall, if supported, take the following:
+
+- If the cell that serves the UE is a Hybrid cell, the RNC shall store the value contained in the *CSG Membership Status* IE and replace any previously stored membership status value by this new one. The RNC may use such information to perform differentiated treatment for member and non-member UEs.
+
+If the *Tunnel Information for BBF* IE is received in the ENHANCED RELOCATION COMPLETE REQUEST message, the CN shall, if supported, use the IE as described in TS 23.139 [65].
+
+### 8.44.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: ENHANCED RELOCATION COMPLETE REQUEST
+ Note right of CN:
+ CN-->>RNC: ENHANCED RELOCATION COMPLETE FAILURE
+ Note left of RNC:
+ Note right of CN:
+```
+
+The diagram illustrates the interaction between an RNC and a CN for an unsuccessful Enhanced Relocation Complete procedure. It starts with the RNC sending an 'ENHANCED RELOCATION COMPLETE REQUEST' message to the CN. The CN then responds with an 'ENHANCED RELOCATION COMPLETE FAILURE' message back to the RNC. Both entities are shown with a horizontal bar at the bottom, indicating active lifelines.
+
+Sequence diagram for Unsuccessful Enhanced Relocation Complete procedure.
+
+**Figure 59: Enhanced Relocation Complete procedure. Unsuccessful operation.**
+
+If a failure occurs in the CN during the execution of the relocation procedure, the CN shall send the ENHANCED RELOCATION COMPLETE FAILURE message to the RNC with an appropriate cause value. The RNC shall assume the Iu resources between the old source RNC and the CN node being released by the respective CN node.
+
+## 8.45 Enhanced Relocation Complete Confirm
+
+### 8.45.1 General
+
+The purpose of the Enhanced Relocation Complete Confirm procedure is to indicate the CN (applicable towards the CS domain only) to switch the bearers towards the target RNC. The procedure uses connection-oriented signalling.
+
+### 8.45.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: ENHANCED RELOCATION COMPLETE CONFIRM
+ Note right of CN:
+ Note left of RNC:
+ Note right of CN:
+```
+
+The diagram illustrates the interaction between an RNC and a CN for a successful Enhanced Relocation Complete Confirm procedure. It shows the RNC sending an 'ENHANCED RELOCATION COMPLETE CONFIRM' message to the CN. Both entities are shown with a horizontal bar at the bottom, indicating active lifelines.
+
+Sequence diagram for Successful Enhanced Relocation Complete Confirm procedure.
+
+**Figure 60: Enhanced Relocation Complete Confirm procedure. Successful operation.**
+
+The RNC shall initialise the Enhanced Relocation Complete Confirm procedure by sending the ENHANCED RELOCATION COMPLETE CONFIRM message. If the RNC is not able to successfully initialise RABs for which an Iu user plane initialisation is necessary, it shall provide respective information within the *RABs Failed To Initialise List* IE with an appropriate cause value.
+
+## 8.46 SRVCC Preparation
+
+### 8.46.1 General
+
+The purpose of the SRVCC Preparation procedure is the reception of the security parameters from the PS CN domain needed for successful SRVCC operation as described in TS 23.216 [54].
+
+The procedure uses connection oriented signalling.
+
+## 8.46.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note left of RNC:
+ RNC->>CN: SRVCC CS KEYS REQUEST
+ Note right of CN:
+ CN-->>RNC: SRVCC CS KEYS RESPONSE
+ Note left of RNC:
+```
+
+Sequence diagram for SRVCC Preparation procedure. Successful operation. The diagram shows two lifelines: RNC and CN. The RNC sends an SRVCC CS KEYS REQUEST message to the CN. The CN responds with an SRVCC CS KEYS RESPONSE message to the RNC.
+
+**Figure 61: SRVCC Preparation procedure. Successful operation.**
+
+The RNC shall determine if the SRVCC operation as described in TS 23.216 [54] is required. In such case the RNC shall initiate the SRVCC Preparation procedure by sending an SRVCC CS KEYS REQUEST message to the source SGSN.
+
+The SGSN shall respond to the RNC with SRVCC CS KEYS RESPONSE message containing the *Integrity Protection Key IE*, the *Encryption Key IE* and the *SRVCC Information IE*.
+
+## 8.46.3 Abnormal Conditions
+
+Not applicable.
+
+# 8.47 UE Radio Capability Match
+
+## 8.47.1 General
+
+The purpose of the UE Radio Capability Match procedure is to enable the SGSN to request for an indication on whether the UE capabilities match the network configuration for voice continuity. The procedure uses connection oriented signalling.
+
+## 8.47.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC
+ participant SGSN
+ Note left of RNC:
+ SGSN->>RNC: UE RADIO CAPABILITY MATCH REQUEST
+ Note right of RNC:
+ RNC-->>SGSN: UE RADIO CAPABILITY MATCH RESPONSE
+ Note left of RNC:
+```
+
+Sequence diagram for UE Radio Capability Match procedure: Successful operation. The diagram shows two lifelines: RNC and SGSN. The SGSN sends a UE RADIO CAPABILITY MATCH REQUEST message to the RNC. The RNC responds with a UE RADIO CAPABILITY MATCH RESPONSE message to the SGSN.
+
+**Figure 62: UE Radio Capability Match procedure: Successful operation.**
+
+The SGSN initiates the procedure by sending a UE RADIO CAPABILITY MATCH REQUEST message to the RNC. The RNC shall, if supported, respond with a UE RADIO CAPABILITY MATCH RESPONSE message.
+
+## 8.47.3 Unsuccessful Operation
+
+Not applicable.
+
+## 8.47.4 Abnormal Conditions
+
+Not applicable.
+
+---
+
+## 9 Elements for RANAP Communication
+
+### 9.1 Message Functional Definition and Content
+
+#### 9.1.1 General
+
+Subclause 9.1 presents the contents of RANAP messages in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence.
+
+NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [18].
+
+## 9.1.2 Message Contents
+
+### 9.1.2.1 Presence
+
+All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 4.
+
+**Table 4: Meaning of abbreviations used in RANAP messages**
+
+| Abbreviation | Meaning |
+|--------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| M | IEs marked as Mandatory (M) shall always be included in the message. |
+| O | IEs marked as Optional (O) may or may not be included in the message. |
+| C | IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. |
+
+### 9.1.2.2 Criticality
+
+Each Information Element or Group of Information Elements may have criticality information applied to it. Following cases are possible:
+
+**Table 5: Meaning of content within "Criticality" column**
+
+| Abbreviation | Meaning |
+|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| – | No criticality information is applied explicitly. |
+| YES | Criticality information is applied. This is usable only for non-repeatable IEs |
+| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. |
+| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. |
+
+### 9.1.2.3 Range
+
+The Range column indicates the allowed number of copies of repetitive IEs/IE groups.
+
+### 9.1.2.4 Assigned Criticality
+
+This column provides the actual criticality information as defined in subclause 10.3.2, if applicable.
+
+## 9.1.3 RAB ASSIGNMENT REQUEST
+
+This message is sent by the CN to request the establishment, modification or release of one or more RABs for the same UE.
+
+Direction: CN→RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|--------------------|-----------------------|-----------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs To Be Setup Or Modified List | O | | | | YES | ignore |
+| >RABs To Be Setup Or Modified Item IEs | | 1 to | | | | |
+| >>First Setup Or Modify Item | M | | | Grouping reason: same criticality. | EACH | reject |
+| >>>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>>NAS Synchronisation Indicator | O | | 9.2.3.18 | | - | |
+| >>>RAB Parameters | O | | 9.2.1.3 | Includes all necessary parameters for RABs (both for MSC and SGSN) including QoS. | - | |
+| >>>User Plane Information | O | | | | - | |
+| >>>>User Plane Mode | M | | 9.2.1.18 | | - | |
+| >>>>UP Mode Versions | M | | 9.2.1.19 | | - | |
+| >>>Transport Layer Information | O | | | | - | |
+| >>>>Transport Layer Address | M | | 9.2.2.1 | | - | |
+| >>>>Iu Transport Association | M | | 9.2.2.2 | | - | |
+| >>>Service Handover | O | | 9.2.1.41 | | - | |
+| >>>E-UTRAN Service Handover | O | | 9.2.1.90 | | YES | ignore |
+| >>>Correlation ID | O | | 9.2.2.5 | | - | |
+| >>Second Setup Or Modify Item | M | | | Grouping reason: same criticality. | EACH | ignore |
+| >>>PDP Type Information | O | | 9.2.1.40 | | - | |
+| >>>Data Volume Reporting Indication | O | | 9.2.1.17 | | - | |
+| >>>DL GTP-PDU Sequence Number | O | | 9.2.2.3 | | - | |
+| >>>UL GTP-PDU Sequence Number | O | | 9.2.2.4 | | - | |
+| >>>DL N-PDU Sequence Number | O | | 9.2.1.33 | | - | |
+| >>>UL N-PDU Sequence Number | O | | 9.2.1.34 | | - | |
+| >>>Alternative RAB Parameter Values | O | | 9.2.1.43 | | YES | ignore |
+| >>>GERAN BSC Container | O | | 9.2.1.58 | | YES | ignore |
+
+| | | | | | | |
+|-----------------------------------|---|--------------------|-----------|---------------------------------------------------------------------------------------------------------------------|------|--------|
+| >>>PDP Type Information extension | O | | 9.2.1.40a | The PDP Type Information extension IE can only be included if PDP Type Information IE is not present. | YES | ignore |
+| >>>Offload RAB parameters | O | | 9.2.1.94 | Applicable only for SIPTO at lu-PS. | YES | ignore |
+| RABs To Be Released List | O | | | | YES | ignore |
+| >RABs To Be Released Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.91 | | YES | ignore |
+| MSISDN | O | | 9.2.1.95 | Applicable only for SIPTO at lu-PS. | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.4 RAB ASSIGNMENT RESPONSE
+
+This message is sent by the RNC to report the outcome of the request from the RAB ASSIGNMENT REQUEST message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|--------------------|-----------------------|----------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs Setup Or Modified List | O | | | | YES | ignore |
+| >RABs Setup Or Modified Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>Transport Layer Address | O | | 9.2.2.1 | | - | |
+| >>Iu Transport Association | O | | 9.2.2.2 | | - | |
+| >>DL Data Volumes | O | | | | - | |
+| >>>Data Volume List | | 1 to | | | - | |
+| >>>>Unsuccessfull y Transmitted DL Data Volume | M | | 9.2.3.12 | | - | |
+| >>>>Data Volume Reference | O | | 9.2.3.13 | | - | |
+| >>Assigned RAB Parameter Values | O | | 9.2.1.44 | | YES | ignore |
+| RABs Released List | O | | | | YES | ignore |
+| >RABs Released Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>DL Data Volumes | O | | | | - | |
+| >>>Data Volume List | | 1 to | | | - | |
+| >>>>Unsuccessfull y Transmitted DL Data Volume | M | | 9.2.3.12 | | - | |
+| >>>>Data Volume Reference | O | | 9.2.3.13 | | - | |
+| >>DL GTP-PDU Sequence Number | O | | 9.2.2.3 | | - | |
+| >>UL GTP-PDU Sequence Number | O | | 9.2.2.4 | | - | |
+| RABs Queued List | O | | | | YES | ignore |
+| >RABs Queued Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| RABs Failed To Setup Or Modify List | O | | | | YES | ignore |
+| >RABs Failed To Setup Or Modify Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| RABs Failed To Release List | O | | | | YES | ignore |
+| >RABs Failed To | | 1 to | | | EACH | ignore |
+
+| | | | | | | |
+|-------------------------------------------------------------------|---|--------------------|----------|----------------------------------------------------|------|--------|
+| Release Item IEs | | | | | | |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>Cause | M | | 9.2.1.4. | | - | |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| GERAN Iu mode specific RABs Failed To Setup Or Modify List | O | | | This applies only in GERAN Iu mode case. | YES | ignore |
+| >GERAN Iu mode specific RABs Failed To Setup Or Modify Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | The same RAB ID must only be present in one group. | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| >>GERAN Classmark | O | | 9.2.1.57 | | - | |
+
+| Range bound | Explanation |
+|-------------|--------------------------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+| maxnoofVol | Maximum no. of reported data volume for one RAB. Value is 2. |
+
+## 9.1.5 RAB RELEASE REQUEST
+
+This message is sent by the RNC to request the CN to release one or more RABs for the same UE.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| RABs To Be Released List | M | | | | YES | ignore |
+| >RABs To Be Released Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.6 IU RELEASE REQUEST
+
+This message is sent by the RNC to request the CN to release the Iu connection.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+
+## 9.1.7 IU RELEASE COMMAND
+
+This message is sent by the CN to order the RNC to release all resources related to the Iu connection.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|-------|------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| End Of CSFB | O | | 9.2.1.111 | | YES | ignore |
+| Out Of UTRAN | O | | 9.2.1.112 | | YES | ignore |
+| Last E-UTRAN PLMN Identity | O | | 9.2.3.33
Selected PLMN Identity | Indicates the E-UTRAN PLMN ID where the UE formerly requested CS Fallback to UTRAN. | YES | ignore |
+
+## 9.1.8 IU RELEASE COMPLETE
+
+This message is sent by the RNC as a response to the IU RELEASE COMMAND message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs Data Volume Report List | O | | | | YES | ignore |
+| >RABs Data Volume Report Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>RAB Data Volume Report List | O | | | | - | |
+| >>>RAB Data Volume Report Item IEs | | 1 to | | | - | |
+| >>>>Unsuccessfully Transmitted DL Data Volume | M | | 9.2.3.12 | | - | |
+| >>>>Data Volume Reference | O | | 9.2.3.13 | | - | |
+| RABs Released List | O | | | | YES | ignore |
+| >RABs Released Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>DL GTP-PDU Sequence Number | O | | 9.2.2.3 | | - | |
+| >>UL GTP-PDU Sequence Number | O | | 9.2.2.4 | | - | |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|--------------------------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+| maxnoofVol | Maximum no. of reported data volume for one RAB. Value is 2. |
+
+## 9.1.9 RELOCATION REQUIRED
+
+This message is sent by the source RNC to inform the CN that a relocation is to be performed.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|--------------------------------------------|-------|-----------------------|--------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Relocation Type | M | | 9.2.1.23 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Source ID | M | | 9.2.1.24 | | YES | ignore |
+| Target ID | M | | 9.2.1.25 | | YES | reject |
+| MS Classmark 2 | C –
ifGSMCStarget | | 9.2.1.26 | | YES | reject |
+| MS Classmark 3 | C –
ifGSMCStarget | | 9.2.1.27 | | YES | ignore |
+| Source To Target Transparent Container | C –
ifUMTStarget
or
ifEUTRAtarget | | 9.2.1.30A | | YES | reject |
+| Old BSS To New BSS Information | O | | 9.2.1.29 | Can optionally be used if GSM target but not used for UMTS target. | YES | ignore |
+| GERAN Classmark | O | | 9.2.1.57 | | YES | ignore |
+| Source BSS To Target BSS Transparent Container | O | | 9.2.1.79 | Shall be included if, and only if, GSM PS domain is target. | YES | ignore |
+| SRVCC HO Indication | O | | 9.2.1.88 | | YES | reject |
+| CSG Id | O | | 9.2.1.85 | | YES | reject |
+| Cell Access Mode | O | | 9.2.1.93 | | YES | reject |
+| rSRVCC HO Indication | O | | 9.2.1.114 | | YES | reject |
+
+| Condition | Explanation |
+|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ifGSMCStarget | This IE shall be present if the Target ID IE contains a CGI IE and Source BSS To Target BSS Transparent Container is not included. |
+| ifUMTStarget | This IE shall be present if the Target ID IE contains a Target RNC-ID IE. |
+| ifEUTRAtarget | This IE shall be present if the Target ID IE contains a Target eNB-ID IE or if the Target ID IE contains a Target RNC-ID IE containing a Corresponding RNC-ID. |
+
+## 9.1.10 RELOCATION REQUEST
+
+This message is sent by the CN to request the target RNC to allocate necessary resources for a relocation.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|--------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Permanent NAS UE Identity | O | | 9.2.3.1 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Source To Target Transparent Container | M | | 9.2.1.30a | Encoded as the Source RNC To Target RNC Transparent Container IE defined in subclause 9.2.1.28. | YES | reject |
+| RABs To Be Setup List | O | | | | YES | reject |
+| >RABs To Be Setup Item IEs | | 1 to | | | EACH | reject |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>NAS Synchronisation Indicator | O | | 9.2.3.18 | | - | |
+| >>RAB Parameters | M | | 9.2.1.3 | | - | |
+| >>Data Volume ReportingIndication | C – ifPS | | 9.2.1.17 | | - | |
+| >>PDP Type Information | C – ifPS | | 9.2.1.40 | | - | |
+| >>User Plane Information | M | | | | - | |
+| >>>User Plane Mode | M | | 9.2.1.18 | | - | |
+| >>>UP Mode Versions | M | | 9.2.1.19 | | - | |
+| >>Transport Layer Address | M | | 9.2.2.1 | | - | |
+| >>Iu Transport Association | M | | 9.2.2.2 | | - | |
+| >>Service Handover | O | | 9.2.1.41 | | - | |
+| >>Alternative RAB Parameter Values | O | | 9.2.1.43 | | YES | ignore |
+| >>GERAN BSC Container | O | | 9.2.1.58 | | YES | ignore |
+| >>E-UTRAN Service Handover | O | | 9.2.1.90 | | YES | ignore |
+| >>PDP Type Information extension | O | | 9.2.1.40a | The PDP Type Information extension IE can only be included if PDP Type Information IE is present. | YES | ignore |
+| >>Offload RAB parameters | O | | 9.2.1.94 | Applicable only for SIPTO at Iu-PS | YES | ignore |
+| Integrity Protection Information | O | | 9.2.1.11 | Integrity Protection Information includes key and permitted algorithms. | YES | ignore |
+
+| | | | | | | |
+|-------------------------------------|---|--------------------------------------|---------------------------------|------------------------------------------------------------------------------|------|--------|
+| Encryption Information | O | | 9.2.1.12 | Encryption Information includes key and permitted algorithms. | YES | ignore |
+| Iu Signalling Connection Identifier | M | | 9.2.1.38 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | reject |
+| SNA Access Information | O | | 9.2.3.24 | | YES | ignore |
+| UESBI-Iu | O | | 9.2.1.59 | | YES | ignore |
+| Selected PLMN Identity | O | | 9.2.3.33 | | YES | ignore |
+| CN MBMS Linking Information | O | | | | YES | ignore |
+| >Joined MBMS Bearer Service IEs | | 1 to | | | EACH | ignore |
+| >>TMGI | M | | 9.2.3.37 | The same TMGI must only be present in one group. | - | - |
+| >>PTP RAB ID | M | | 9.2.1.75 | | - | - |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.91 | | YES | ignore |
+| CSG Id | O | | 9.2.1.85 | | YES | reject |
+| CSG Membership Status | O | | 9.2.1.92 | | YES | ignore |
+| MSISDN | O | | 9.2.1.95 | Applicable only for SIPTO at Iu-PS. | YES | ignore |
+| Anchor PLMN Identity | O | | Selected PLMN Identity 9.2.3.33 | Indicates the PS core network operator in case of SRVCC (see TS 23.251 [39]) | YES | ignore |
+
+| Condition | Explanation |
+|-----------|--------------------------------------------------------------------------------------|
+| IfPS | This IE shall be present if the CN domain indicator IE is set to "PS domain". |
+
+| Range bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+| maxnoofMulticastServicesPerUE | Maximum no. of Multicast Services that a UE can join and leave respectively. Value is 128. |
+
+## 9.1.11 RELOCATION REQUEST ACKNOWLEDGE
+
+This message is sent by the target RNC to inform the CN about the result of the resource allocation for the requested relocation.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|--------------------|-----------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Target To Source Transparent Container | O | | 9.2.1.30b | Encoded as the Target RNC To Source RNC Transparent Container IE defined in subclause 9.2.1.30. | YES | ignore |
+| RABs Setup List | O | | | | YES | ignore |
+| > RABs Setup Item IEs | | 1 to | | | EACH | reject |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Transport Layer Address | O | | 9.2.2.1 | IPv6 or IPv4 address if no other TLA included.
IPv4 address if other TLA included. | - | |
+| >>Iu Transport Association | O | | 9.2.2.2 | Related to TLA above. | - | |
+| >>Assigned RAB Parameter Values | O | | 9.2.1.44 | | YES | ignore |
+| >>Transport Layer Address | O | | 9.2.2.1 | IPv6 address if included. | YES | ignore |
+| >>Iu Transport Association | O | | 9.2.2.2 | Related to TLA above. | YES | ignore |
+| RABs Failed To Setup List | O | | | | YES | ignore |
+| > RABs Failed To Setup Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| Chosen Integrity Protection Algorithm | O | | 9.2.1.13 | Indicates the Integrity Protection algorithm that will be used by the target RNC. | YES | ignore |
+| Chosen Encryption Algorithm | O | | 9.2.1.14 | Indicates the Encryption algorithm that will be used by the target RNC. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| New BSS To Old BSS Information | O | | 9.2.1.47 | Defined in TS 48.008 [11]. | YES | ignore |
+| CSG Id | O | | 9.2.1.85 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.12 RELOCATION COMMAND
+
+This message is sent by the CN to the source RNC to inform that resources for the relocation are allocated in the target RNC (in case of intra-system relocation) or in the target system (in case of inter-system relocation).
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|--------------------|-----------------------|---------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Target To Source Transparent Container | O | | 9.2.1.30B | | YES | reject |
+| L3 Information | O | | 9.2.1.31 | | YES | ignore |
+| RABs To Be Released List | O | | | | YES | ignore |
+| >RABs To Be Released Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| RABs Subject To Data Forwarding List | O | | | | YES | ignore |
+| >RABs Subject To Data Forwarding Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Transport Layer Address | M | | 9.2.2.1 | IPv6 or IPv4 address if no other TLA included.
IPv4 address if other TLA included. | - | |
+| >>lu Transport Association | M | | 9.2.2.2 | Related to TLA above. | - | |
+| >>Transport Layer Address | O | | 9.2.2.1 | IPv6 address if included. | YES | ignore |
+| >>lu Transport Association | O | | 9.2.2.2 | Related to TLA above. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Inter-System Information Transparent Container | O | | 9.2.1.48 | | YES | ignore |
+| Target BSS to Source BSS Transparent Container | O | | 9.2.1.80 | | YES | ignore |
+| SRVCC Information | O | | 9.2.1.89 | | YES | reject |
+| rSRVCC Information | O | | 9.2.1.115 | | YES | reject |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.13 RELOCATION DETECT
+
+This message is sent by the target RNC to inform the CN that the relocation execution trigger has been received.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+
+## 9.1.14 RELOCATION COMPLETE
+
+This message is sent by the target RNC to inform the CN that the relocation is completed.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|----------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Higher bitrates than 16 Mbps flag | O | | 9.2.3.54 | May only be included towards the PS domain. | YES | ignore |
+| Tunnel Information for BBF | O | | Tunnel Information 9.2.2.6 | Indicating HNB's Local IP Address assigned by the broadband access provider, UDP port Number. | YES | ignore |
+
+## 9.1.15 RELOCATION PREPARATION FAILURE
+
+This message is sent by the CN to the source RNC if the relocation preparation failed.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Inter-System Information Transparent Container | O | | 9.2.1.48 | | YES | ignore |
+
+## 9.1.16 RELOCATION FAILURE
+
+This message is sent by the target RNC to inform the CN that the requested resource allocation failed.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|-----------------------|----------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| New BSS to Old BSS Information | O | | 9.2.1.47 | Defined in TS 48.008 [11]. | YES | ignore |
+| GERAN Classmark | O | | 9.2.1.57 | | YES | ignore |
+
+## 9.1.17 RELOCATION CANCEL
+
+This message is sent by the source RNC to the CN to cancel an ongoing relocation.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+
+## 9.1.18 RELOCATION CANCEL ACKNOWLEDGE
+
+This message is sent by the CN to the source RNC when the relocation has been cancelled.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.19 SRNS CONTEXT REQUEST
+
+This message is sent by the CN to the source RNC to indicate the PS RABs for which context transfer shall be performed.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs Subject To Data Forwarding List | M | | | | YES | ignore |
+| >RABs Subject To Data Forwarding Item IEs | | 1 to | | | EACH | reject |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| RAT Type | O | | 9.2.3.52 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.20 SRNS CONTEXT RESPONSE
+
+This message is sent by the source RNC as a response to SRNS CONTEXT REQUEST message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs Contexts List | O | | | | YES | ignore |
+| >RABs Contexts Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>DL GTP-PDU Sequence Number | O | | 9.2.2.3 | | - | |
+| >>UL GTP-PDU Sequence Number | O | | 9.2.2.4 | | - | |
+| >>DL N-PDU Sequence Number | O | | 9.2.1.33 | | - | |
+| >>UL N-PDU Sequence Number | O | | 9.2.1.34 | | - | |
+| RABs Contexts Failed To Transfer List | O | | | | YES | ignore |
+| >RABs Contexts Failed To Transfer Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.21 SRNS DATA FORWARD COMMAND
+
+This message is sent by the CN to the RNC to trigger the transfer of N-PDUs from the RNC to the CN in intersystem change or in some further cases described in TS 23.060 [21].
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| RABs Subject To Data Forwarding List | O | | | | YES | ignore |
+| >RABs Subject To Data Forwarding Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Transport Layer Address | M | | 9.2.2.1 | | - | |
+| >>Iu Transport Association | M | | 9.2.2.2 | | - | |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.22 FORWARD SRNS CONTEXT
+
+This message is sent either by the source RNC to the CN or by the CN to the target RNC to transfer the SRNS Context.
+
+Direction: CN → RNC and RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| RAB Contexts List | M | | | | YES | ignore |
+| >RAB Contexts Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>DL GTP-PDU Sequence Number | O | | 9.2.2.3 | | - | |
+| >>UL GTP-PDU Sequence Number | O | | 9.2.2.4 | | - | |
+| >>DL N-PDU Sequence Number | O | | 9.2.1.33 | | - | |
+| >>UL N-PDU Sequence Number | O | | 9.2.1.34 | | - | |
+| Source RNC PDCP context info | O | | 9.2.1.54 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.23 PAGING
+
+This message is sent by the CN to request the UTRAN to page a specific UE.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------|----------|---------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| Permanent NAS UE Identity | M | | 9.2.3.1 | | YES | ignore |
+| Temporary UE Identity | O | | 9.2.3.2 | | YES | ignore |
+| Paging Area ID | O | | 9.2.1.21 | | YES | ignore |
+| Paging Cause | O | | 9.2.3.3 | | YES | ignore |
+| Non Searching Indication | O | | 9.2.1.22 | | YES | ignore |
+| DRX Cycle Length Coefficient | O | | 9.2.1.37 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| CSG Id List | | 0 to | | | YES | ignore |
+| >CSG Id | M | | 9.2.1.85 | | | |
+
+| Range bound | Explanation |
+|---------------|--------------------------------------------------------------|
+| maxnoofCSGIds | Maximum no. of CSG Ids within the CSG Id List. Value is 256. |
+
+## 9.1.24 COMMON ID
+
+This message is sent by the CN to inform the RNC about the permanent NAS UE identity for a user. It may include additional information.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|-------|------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Permanent NAS UE Identity | M | | 9.2.3.1 | | YES | ignore |
+| SNA Access Information | O | | 9.2.3.24 | | YES | ignore |
+| UESBI-lu | O | | 9.2.1.59 | | YES | ignore |
+| Selected PLMN Identity | O | | 9.2.3.33 | | YES | ignore |
+| Subscriber Profile ID for RAT/Frequency priority | O | | 9.2.1.86 | | YES | ignore |
+| SRVCC operation possible | O | | 9.2.1.87 | | YES | ignore |
+| CSG Membership Status | O | | 9.2.1.92 | | YES | ignore |
+| Management Based MDT Allowed | O | | 9.2.1.110 | | YES | ignore |
+| Management Based MDT PLMN List | O | | MDT PLMN List
9.2.1.116 | | YES | ignore |
+| rSRVCC operation possible | O | | 9.2.1.121 | | YES | ignore |
+| Last E-UTRAN PLMN Identity | O | | 9.2.3.33
Selected PLMN Identity | Indicates the E-UTRAN PLMN ID where the UE formerly requested CS Fallback to UTRAN. | YES | ignore |
+
+## 9.1.25 CN INVOKE TRACE
+
+This message is sent by the CN to request the RNC to start a trace recording session.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|-----------------------|-------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Trace Type | O | | 9.2.1.6 | Mandatory for GERAN Iu Mode. Not applicable to UTRAN. | YES | ignore |
+| Trace Reference | M | | 9.2.1.8 | | YES | ignore |
+| Trigger ID | O | | 9.2.1.7 | Mandatory for GERAN Iu Mode. Not applicable to UTRAN. | YES | ignore |
+| UE Identity | O | | 9.2.1.9 | Mandatory for UTRAN. Optional for GERAN Iu Mode. | YES | ignore |
+| OMC ID | O | | 9.2.1.10 | Mandatory for GERAN Iu Mode. Not applicable to UTRAN. | YES | ignore |
+| Trace Propagation Parameters | O | | 9.2.1.68 | Optional for UTRAN. Not applicable to GERAN Iu Mode. | YES | ignore |
+| MDT Configuration | O | | 9.2.1.97 | | YES | ignore |
+| Trace Collection Entity IP Address | O | | 9.2.2.1 | | YES | ignore |
+
+## 9.1.26 SECURITY MODE COMMAND
+
+This message is sent by the CN to trigger the integrity and ciphering functions over the radio interface.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------|----------|-------|-----------------------|---------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Integrity Protection Information | M | | 9.2.1.11 | Integrity information includes key and permitted algorithms. | YES | reject |
+| Encryption Information | O | | 9.2.1.12 | Encryption information includes key and permitted algorithms. | YES | ignore |
+| Key Status | M | | 9.2.1.36 | | YES | reject |
+
+## 9.1.27 SECURITY MODE COMPLETE
+
+This message is sent by the RNC as a successful response to a SECURITY MODE COMMAND message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Chosen Integrity Protection Algorithm | M | | 9.2.1.13 | | YES | reject |
+| Chosen Encryption Algorithm | O | | 9.2.1.14 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.28 SECURITY MODE REJECT
+
+This message is sent by the RNC as an unsuccessful response to a SECURITY MODE COMMAND message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.29 LOCATION REPORTING CONTROL
+
+This message is sent by the CN to initiate, modify or stop location reporting from the RNC to the CN.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Request Type | M | | 9.2.1.16 | | YES | ignore |
+| Vertical Accuracy Code | O | | 9.2.1.46a | | YES | ignore |
+| Response Time | O | | 9.2.1.46b | | YES | ignore |
+| Positioning Priority | O | | 9.2.1.46c | | YES | ignore |
+| Client Type | O | | 9.2.1.46d | | YES | ignore |
+| Include Velocity | O | | 9.2.1.81 | | YES | ignore |
+| Periodic Location Info | O | | 9.2.1.82 | | YES | ignore |
+
+## 9.1.30 LOCATION REPORT
+
+This message is sent by the RNC to the CN with information about the UE location.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Area Identity | O | | 9.2.3.10 | | YES | ignore |
+| Cause | O | | 9.2.1.4 | | YES | ignore |
+| Request Type | O | | 9.2.1.16 | | YES | ignore |
+| Last Known Service Area | O | | 9.2.3.22 | | YES | ignore |
+| Position Data | O | | 9.2.3.27 | Optional for UTRAN only. | YES | ignore |
+| Position Data Specific To GERAN Iu Mode | O | | 9.2.3.28 | Coded as the value part of the Positioning Data IE defined in TS 49.031 [34]. Optional for GERAN Iu mode only. Not applicable for UTRAN. | YES | ignore |
+| Accuracy Fulfilment Indicator | O | | 9.2.3.29 | | YES | ignore |
+| Velocity Estimate | O | | 9.2.3.51 | | YES | ignore |
+
+## 9.1.31 DATA VOLUME REPORT REQUEST
+
+This message is sent by the CN to request unsuccessfully transmitted data volumes for specific RABs.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs Data Volume Report List | M | | | | YES | ignore |
+| >RABs Data Volume Report Item IEs | | 1 to | | | EACH | reject |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.32 DATA VOLUME REPORT
+
+This message is sent by the RNC and informs the CN about unsuccessfully transmitted data volumes for requested RABs.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| RABs Data Volume Report List | O | | | | YES | ignore |
+| > RABs Data Volume Report Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >> RAB Data Volume Report List | O | | | | - | |
+| >>> RAB Data Volume Report Item IEs | | 1 to | | | - | |
+| >>>>Unsuccessfully Transmitted DL Data Volume | M | | 9.2.3.12 | | - | |
+| >>>>Data Volume Reference | O | | 9.2.3.13 | | - | |
+| RABs Failed To Report List | O | | | | YES | ignore |
+| > RABs Failed To Report Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|--------------------------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+| maxnoofVol | Maximum no. of reported data volume for one RAB. Value is 2. |
+
+## 9.1.33 INITIAL UE MESSAGE
+
+This message is sent by the RNC to transfer the radio interface initial layer 3 message to the CN.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|-------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| LAI | M | | 9.2.3.6 | | YES | ignore |
+| RAC | C - ifPS | | 9.2.3.7 | | YES | ignore |
+| SAI | M | | 9.2.3.9 | | YES | ignore |
+| NAS-PDU | M | | 9.2.3.5 | | YES | ignore |
+| Iu Signalling Connection Identifier | M | | 9.2.1.38 | | YES | ignore |
+| Global RNC-ID | M | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| GERAN Classmark | O | | 9.2.1.57 | | YES | ignore |
+| Selected PLMN Identity | O | | 9.2.3.33 | | YES | ignore |
+| NAS Sequence Number | O | | 9.2.3.34 | | YES | ignore |
+| Permanent NAS UE Identity | O | | 9.2.3.1 | | YES | ignore |
+| Redirect Attempt Flag | O | | 9.2.3.50 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| CSG Id | O | | 9.2.1.85 | | YES | reject |
+| Cell Access Mode | O | | 9.2.1.93 | | YES | reject |
+| L-GW Transport Layer Address | O | | Transport Layer Address 9.2.2.1 | Indicating the Transport Layer address of the L-GW if the L-GW is co-located with the RNC. | YES | ignore |
+| Higher bitrates than 16 Mbps flag | O | | 9.2.3.54 | May only be included towards the PS domain. | YES | ignore |
+| Tunnel Information for BBF | O | | Tunnel Information 9.2.2.6 | Indicating HNB's Local IP Address assigned by the broadband access provider, UDP port Number. | YES | ignore |
+
+| Condition | Explanation |
+|-----------|--------------------------------------------------------------------------------------|
+| ifPS | This IE shall be present if the CN Domain Indicator IE is set to "PS domain". |
+
+## 9.1.34 DIRECT TRANSFER
+
+This message is sent by both the CN and the RNC and is used for carrying NAS information over the Iu interface.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| NAS-PDU | M | | 9.2.3.5 | | YES | ignore |
+| LAI | O | | 9.2.3.6 | | YES | ignore |
+| RAC | O | | 9.2.3.7 | | YES | ignore |
+| SAI | O | | 9.2.3.9 | | YES | ignore |
+| SAPI | O | | 9.2.3.8 | | YES | ignore |
+| Redirection Indication | O | | 9.2.3.36 | | YES | ignore |
+| Redirection Completed | O | | 9.2.3.35 | | YES | ignore |
+| Subscriber Profile ID for RAT/Frequency priority | O | | 9.2.1.86 | | YES | ignore |
+| L-GW Transport Layer Address | O | | Transport Layer Address 9.2.2.1 | Indicating the Transport Layer address of the L-GW if the L-GW is co-located with RNC. It can only be transmitted from the RNC to the CN. | YES | ignore |
+
+### 9.1.35 CN INFORMATION BROADCAST REQUEST
+
+Void.
+
+### 9.1.36 CN INFORMATION BROADCAST CONFIRM
+
+Void.
+
+### 9.1.37 CN INFORMATION BROADCAST REJECT
+
+Void.
+
+### 9.1.38 OVERLOAD
+
+This message is sent by either the CN or the RNC to indicate that the control plane of the node is overloaded.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Number Of Steps | O | | 9.2.1.32 | | YES | ignore |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| CN Domain Indicator | O | | 9.2.1.5 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| Priority Class Indicator | O | | 9.2.1.109 | | YES | ignore |
+
+## 9.1.39 RESET
+
+This message is sent by both the CN and the RNC and is used to request that the other node be reset.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+## 9.1.40 RESET ACKNOWLEDGE
+
+This message is sent by both the CN and the RNC as a response to a RESET message.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+## 9.1.41 ERROR INDICATION
+
+This message is sent by both the CN and the RNC and is used to indicate that some error has been detected in the node.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connection oriented or connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Cause | O | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| CN Domain Indicator | O | | 9.2.1.5 | | YES | ignore |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+## 9.1.42 CN DEACTIVATE TRACE
+
+This message is sent by the CN to request the RNC to stop a trace session for the indicated trace reference.
+
+Direction: CN $\leftarrow$ RNC.
+
+Signalling bearer mode: Connection Oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------|----------|-------|-----------------------|------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Trace Reference | M | | 9.2.1.8 | | YES | ignore |
+| Trigger ID | O | | 9.2.1.7 | Optional for GERAN Iu Mode. Not applicable to UTRAN. | YES | ignore |
+
+## 9.1.43 RANAP RELOCATION INFORMATION
+
+This message is part of a special RANAP Relocation Information procedure, and is sent between RNCs during Relocation.
+
+Direction: RNC - RNC.
+
+Signalling bearer mode: Not applicable.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|--------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Direct Transfer Information List | O | | | | YES | ignore |
+| > Direct Transfer Information Item IEs | | 1 to | | Information received in one or more DIRECT TRANSFER messages and that needs to be transferred to target RNC for further transmission to the UE. | EACH | ignore |
+| >>NAS-PDU | M | | 9.2.3.5 | | - | |
+| >>SAPI | M | | 9.2.3.8 | | - | |
+| >>CN Domain Indicator | M | | 9.2.1.5 | | - | |
+| RAB Contexts List | O | | | | YES | ignore |
+| > RAB Contexts Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>DL GTP-PDU Sequence Number | O | | 9.2.2.3 | | - | |
+| >>UL GTP-PDU Sequence Number | O | | 9.2.2.4 | | - | |
+| >>DL N-PDU Sequence Number | O | | 9.2.1.33 | | - | |
+| >>UL N-PDU Sequence Number | O | | 9.2.1.34 | | - | |
+| Source RNC PDCP context info | O | | 9.2.1.54 | | YES | ignore |
+| RNSAP Relocation parameters | O | | 9.2.1.101 | Applicable only to RNSAP relocation. | YES | reject |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofDT | Maximum no. of DT information. Value is 15. |
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.44 RESET RESOURCE
+
+This message is sent by either the CN or the RNC. The sending entity informs the receiving entity that it requests the receiving entity to release resources and references associated to the Iu signalling connection identifiers of the message.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Reset Resource List | M | | | | YES | ignore |
+| >Reset Resource Item IEs | | 1 to
| | | EACH | reject |
+| >>Iu Signalling Connection Identifier | M | | 9.2.1.38 | | - | |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------------------------|
+| maxnoofluSigConIds | Maximum no. of Iu signalling connection identifiers. Value is 250. |
+
+The maximum number of Iu signalling connection identifiers contained in the RESET RESOURCE message shall not exceed the range bound specified for the maxnoofluSigConIds (max. no. of Iu signalling connection identifiers) as indicated in the table above.
+
+## 9.1.45 RESET RESOURCE ACKNOWLEDGE
+
+This message is sent by either the CN or the RNC to inform the RNC or the CN that the RESET RESOURCE message has been received.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|---------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Reset Resource List | M | | | | YES | ignore |
+| >Reset Resource Item IEs | | 1 to | | This list shall be in the same order as the list received in the RESET RESOURCE message. | EACH | reject |
+| >>lu Signalling Connection Identifier | M | | 9.2.1.38 | | - | |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------------------------|
+| maxnoofluSigConlds | Maximum no. of lu signalling connection identifiers. Value is 250. |
+
+## 9.1.46 RAB MODIFY REQUEST
+
+This message is sent by the RNC to the CN to request modification of one or more RABs for the same UE.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|--------------------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| RABs To Be Modified List | M | | | | YES | ignore |
+| >RABs To Be Modified Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | Uniquely identifies the RAB for a specific CN domain, for a particular UE. | - | |
+| >>Requested RAB Parameter Values | M | | 9.2.1.45 | Includes RAB parameters for which different values than what was originally negotiated are being requested. | - | |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.47 LOCATION RELATED DATA REQUEST
+
+This message is sent by the CN either to initiate delivery of dedicated assistance data from the RNC to the UE, or to retrieve deciphering keys for the broadcast assistance data.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|-------------------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Location Related Data Request Type | O | | 9.2.3.19 | Mandatory for UTRAN. Optional for GERAN Iu Mode. | YES | reject |
+| Location Related Data Request Type Specific To GERAN Iu Mode | O | | 9.2.3.26 | Optional for GERAN Iu Mode only. Not applicable for UTRAN. | YES | reject |
+| Requested GANSS Assistance Data | C – ifDedAssGANSS | | 9.2.3.53 | | YES | reject |
+
+| Condition | Explanation |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ifDedAssGANSS | This IE shall be present if the Requested Location Related Data Type IE is set to 'Dedicated Assistance Data for Assisted GANSS' or 'Dedicated Assistance Data for Assisted GPS and GANSS'. |
+
+## 9.1.48 LOCATION RELATED DATA RESPONSE
+
+This message is sent by the RNC as a successful response to a LOCATION RELATED DATA REQUEST message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Broadcast Assistance Data
Deciphering Keys | O | | 9.2.3.20 | Deciphering keys for UE based OTDOA or Assisted GPS. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Broadcast GANSS
Assistance Data
Deciphering Keys | O | | 9.2.3.20 | Deciphering keys for Assisted GANSS. | YES | ignore |
+
+## 9.1.49 LOCATION RELATED DATA FAILURE
+
+This message is sent by the RNC to report an unsuccessful response to a LOCATION RELATED DATA REQUEST message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.50 INFORMATION TRANSFER INDICATION
+
+This message is sent by the CN to transfer information to an RNC.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Information Transfer ID | M | | 9.2.1.55 | | YES | reject |
+| Provided Data | M | | 9.2.1.56 | | YES | reject |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+
+## 9.1.51 INFORMATION TRANSFER CONFIRMATION
+
+This message is sent by the RNC as a successful response to an INFORMATION TRANSFER INDICATION message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Information Transfer ID | M | | 9.2.1.55 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Global RNC-ID | M | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+## 9.1.52 INFORMATION TRANSFER FAILURE
+
+This message is sent by the RNC as an unsuccessful response to an INFORMATION TRANSFER INDICATION message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Information Transfer ID | M | | 9.2.1.55 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Global RNC-ID | M | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+## 9.1.53 UE SPECIFIC INFORMATION INDICATION
+
+This message is sent by the CN to inform the RNC about information related to this connection.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| UESBI-lu | O | | 9.2.1.59 | | YES | ignore |
+
+## 9.1.54 DIRECT INFORMATION TRANSFER
+
+This message is sent by both the RNC and the CN in order to transfer specific information.
+
+Direction: RNC → CN and CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Inter-system Information Transfer Type | O | | 9.2.1.62 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+## 9.1.55 UPLINK INFORMATION EXCHANGE REQUEST
+
+This message is sent by the RNC to the CN in order to transfer or request specific information. The nature of the exchange i.e. transfer or request of specific information is indicated within the *Information Exchange Type* IE. The nature of the information to be transferred is indicated within the *Information Transfer Type* IE. The nature of the information requested is indicated within the *Information Request Type* IE.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------|-------------------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Information Exchange ID | M | | 9.2.1.71 | | YES | reject |
+| Information Exchange Type | M | | 9.2.1.72 | | YES | reject |
+| Information Transfer Type | C –
iftransfer | | 9.2.1.63 | | YES | reject |
+| Information Request Type | C –
ifrequest | | 9.2.1.73 | | YES | reject |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | reject |
+| Global RNC-ID | M | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | reject |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+| Condition | Explanation |
+|------------|-------------------------------------------------------------------------------------------|
+| iftransfer | This IE shall be present if the Information Exchange Type IE is set to "transfer". |
+| ifrequest | This IE shall be present if the Information Exchange Type IE is set to "request". |
+
+## 9.1.56 UPLINK INFORMATION EXCHANGE RESPONSE
+
+This message is sent by the CN to the RNC as a successful response to the UPLINK INFORMATION EXCHANGE REQUEST message.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Information Exchange ID | M | | 9.2.1.71 | | YES | ignore |
+| Information Requested | O | | 9.2.1.74 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.57 UPLINK INFORMATION EXCHANGE FAILURE
+
+This message is sent by the CN to the RNC as an unsuccessful response to the UPLINK INFORMATION EXCHANGE REQUEST message.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Information Exchange ID | M | | 9.2.1.71 | | YES | ignore |
+| CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.58 MBMS SESSION START
+
+This message is sent by the CN to establish a MBMS Iu signalling connection and if needed a MBMS RAB.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| TMGI | M | | 9.2.3.37 | | YES | reject |
+| MBMS Session Identity | O | | 9.2.3.38 | | YES | ignore |
+| MBMS Bearer Service Type | M | | 9.2.3.39 | | YES | reject |
+| Iu Signalling Connection Identifier | M | | 9.2.1.38 | | YES | reject |
+| RAB parameters | M | | 9.2.1.3 | | YES | reject |
+| PDP Type Information | O | | 9.2.1.40 | | YES | ignore |
+| MBMS Session Duration | M | | 9.2.3.40 | | YES | reject |
+| MBMS Service Area | M | | 9.2.3.41 | | YES | reject |
+| Frequency Layer Convergence Flag | O | | 9.2.1.76 | | YES | ignore |
+| RA List of Idle Mode UEs | O | | 9.2.3.42 | | YES | ignore |
+| Global CN-ID IE | O | | 9.2.1.46 | | YES | reject |
+| MBMS Session Repetition Number | O | | 9.2.3.48 | | YES | ignore |
+| Time to MBMS Data Transfer | M | | 9.2.3.49 | | YES | reject |
+| MBMS Counting Information | O | | 9.2.3.39a | | YES | ignore |
+| MBMS Synchronisation Information | O | | | | YES | ignore |
+| >MBMS HC Indicator | M | | 9.2.1.84 | | - | |
+| >IP Multicast Address | M | | OCTET STRING (4..16) | | - | |
+| >GTP DL TEID | M | | OCTET STRING (4) | For details and range, see TS 29.281 [59]. | - | |
+| >IP Source Address | O | | OCTET STRING (4..16) | | YES | reject |
+| PDP Type Information extension | O | | 9.2.1.40 a | The PDP Type Information extension IE can only be included if PDP Type Information IE is not present. | YES | Ignore |
+
+## 9.1.59 MBMS SESSION START RESPONSE
+
+This message is sent by the RNC to report the successful outcome of the request from the MBMS SESSION START message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Transport Layer Information | O | | | | YES | ignore |
+| >Transport Layer Address | M | | 9.2.2.1 | | YES | ignore |
+| >Iu Transport Association | M | | 9.2.2.2 | | YES | ignore |
+| Cause | O | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.60 MBMS SESSION START FAILURE
+
+This message is sent by the RNC to report the unsuccessful outcome of the request from the MBMS SESSION START message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.61 MBMS SESSION UPDATE
+
+This message is sent by the CN to inform the RNC whenever the RA List of Idle Mode UEs changes compared to one previously sent.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Session Update ID | M | | 9.2.1.77 | | YES | reject |
+| Delta RA List of Idle Mode UEs | M | | 9.2.3.43 | | YES | reject |
+
+## 9.1.62 MBMS SESSION UPDATE RESPONSE
+
+This message is sent by the RNC to report the successful outcome of the request from the MBMS SESSION UPDATE message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Session Update ID | M | | 9.2.1.77 | | YES | ignore |
+| Transport Layer Information | O | | | | YES | ignore |
+| >Transport Layer Address | M | | 9.2.2.1 | | YES | ignore |
+| >Iu Transport Association | M | | 9.2.2.2 | | YES | ignore |
+| Cause | O | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.63 MBMS SESSION UPDATE FAILURE
+
+This message is sent by the RNC to report the unsuccessful outcome of the request from the MBMS SESSION UPDATE message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Session Update ID | M | | 9.2.1.77 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.64 MBMS SESSION STOP
+
+This message is sent by the CN to release a MBMS Iu signalling connection and its associated MBMS RAB.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| MBMS CN De-Registration | M | | 9.2.3.44 | | YES | reject |
+
+## 9.1.65 MBMS SESSION STOP RESPONSE
+
+This message is sent by the RNC to report the outcome of the request from the MBMS SESSION STOP message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | O | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.66 MBMS UE LINKING REQUEST
+
+This message is sent by the CN to make the RNC aware that a given UE, with existing Iu-ps signalling connection, joined/left one or several Multicast Services.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|---------------------------------------|-----------------------|--------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Joined MBMS Bearer Services List | O | | | | YES | reject |
+| >Joined MBMS Bearer Service IEs | | 1 to | | | EACH | reject |
+| >>TMGI | M | | 9.2.3.37 | The same TMGI must only be present in one group. | - | - |
+| >>PTP RAB ID | M | | 9.2.1.75 | | - | - |
+| Left MBMS Bearer Services List | O | | | | YES | reject |
+| >Left MBMS Bearer Service IEs | | 1 to | | | EACH | reject |
+| >>TMGI | M | | 9.2.3.37 | The same TMGI must only be present in one group. | - | - |
+
+| Range bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------|
+| maxnoofMulticastServicesPerUE | Maximum no. of Multicast Services that a UE can join and leave respectively. Value is 128. |
+
+## 9.1.67 MBMS UE LINKING RESPONSE
+
+This message is sent by the RNC to report the outcome of the request from the MBMS UE LINKING REQUEST message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------|----------|---------------------------------------|-----------------------|--------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Unsuccessful Linking List | O | | | | YES | ignore |
+| >Unsuccessful Linking IEs | | 1 to | | | EACH | ignore |
+| >>TMGI | M | | 9.2.3.37 | The same TMGI must only be present in one group. | - | - |
+| >>Cause | M | | 9.2.1.4 | | - | - |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------|
+| maxnoofMulticastServicesPerUE | Maximum no. of Multicast Services that a UE can join and leave respectively. Value is 128. |
+
+## 9.1.68 MBMS REGISTRATION REQUEST
+
+This message is sent by the RNC to request the CN to register or de-register the RNC for a certain Multicast Service.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connectionless or connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|------------------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| MBMS Registration Request Type | M | | 9.2.3.45 | | YES | reject |
+| TMGI | M | | 9.2.3.37 | | YES | reject |
+| IP Multicast Address | C-
ifRegister | | OCTET
STRING | | YES | reject |
+| APN | C-
ifRegister | | OCTET
STRING | | YES | reject |
+| Global RNC-ID | O | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | reject |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+| Condition | Explanation |
+|------------|------------------------------------------------------------------------------------------------|
+| IfRegister | This IE shall be present if the MBMS Registration Request Type IE is set to "register". |
+
+## 9.1.69 MBMS REGISTRATION RESPONSE
+
+This message is sent by the CN to the RNC as a successful response to the MBMS REGISTRATION REQUEST message.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless or connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| TMGI | O | | 9.2.3.37 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.70 MBMS REGISTRATION FAILURE
+
+This message is sent by the CN to the RNC as an unsuccessful response to the MBMS REGISTRATION REQUEST message.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless or connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| TMGI | O | | 9.2.3.37 | | YES | ignore |
+| Global CN-ID | O | | 9.2.1.46 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.71 MBMS CN DE-REGISTRATION REQUEST
+
+This message is sent by the CN to make the RNC aware that a certain Multicast Service is no longer available.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| TMGI | M | | 9.2.3.37 | | YES | reject |
+| Global CN-ID | O | | 9.2.1.46 | | YES | reject |
+
+## 9.1.72 MBMS CN DE-REGISTRATION RESPONSE
+
+This message is sent by the RNC to the CN as a response to the MBMS CN DE-REGISTRATION REQUEST message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connectionless.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| TMGI | M | | 9.2.3.37 | | YES | ignore |
+| Global RNC-ID | M | | 9.2.1.39 | If the Extended RNC-ID IE is included in the message, the RNC-ID IE in the Global RNC-ID IE shall be ignored. | YES | ignore |
+| Cause | O | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+
+### 9.1.73 MBMS RAB ESTABLISHMENT INDICATION
+
+This message is sent by the RNC to the CN to inform the CN of the establishment of the MBMS RAB corresponding to the MBMS Iu signalling connection used by this message.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Transport Layer Information | M | | | | YES | ignore |
+| >Transport Layer Address | M | | 9.2.2.1 | | YES | ignore |
+| >Iu Transport Association | M | | 9.2.2.2 | | YES | ignore |
+
+### 9.1.74 MBMS RAB RELEASE REQUEST
+
+This message is sent by the RNC to request the CN to release the MBMS RAB.
+
+Direction: RNC → CN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+
+### 9.1.75 MBMS RAB RELEASE
+
+This message is sent by the CN to order the RNC to release all MBMS resources related to the Iu connection.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.76 MBMS RAB RELEASE FAILURE
+
+This message is sent by the CN to the RNC as an unsuccessful response to the MBMS RAB RELEASE REQUEST message.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.77 ENHANCED RELOCATION COMPLETE REQUEST
+
+This message is sent by the RNC to inform the CN that an enhanced relocation is completed.
+
+Direction: RNC → CN
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|--------------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Old Iu Signalling Connection Identifier | M | | Iu Signalling Connection Identifier 9.2.1.38 | | YES | reject |
+| Iu Signalling Connection Identifier | M | | 9.2.1.38 | | YES | reject |
+| Relocation Source RNC-ID | M | | Global RNC-ID 9.2.1.39 | If the Relocation Source Extended RNC-ID IE is included in the message, the Global RNC-ID IE in the Relocation Source RNC-ID IE shall be ignored. | YES | reject |
+| Relocation Source Extended RNC-ID | O | | Extended RNC Id 9.2.1.39a | The Relocation Source Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| Relocation Target RNC-ID | M | | Global RNC-ID 9.2.1.39 | If the Relocation Target Extended RNC-ID IE is included in the message, the RNC-ID IE in the Target RNC-ID IE shall be ignored. | YES | reject |
+| Relocation Target Extended RNC-ID | O | | 9.2.1.39a | The Relocation Target Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| RABs Setup List | O | | | | YES | reject |
+| > RABs Setup Item IEs | | 1 to | | | EACH | reject |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Transport Layer Address | O | | 9.2.2.1 | IPv6 or IPv4 address. | - | |
+| >>Iu Transport Association | O | | 9.2.2.2 | Related to TLA above. | - | |
+| >>Assigned RAB Parameter Values | O | | 9.2.1.44 | | - | |
+| Chosen Integrity Protection | O | | 9.2.1.13 | Indicates the | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|----------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------|
+| Algorithm | | | | Integrity Protection algorithm that will be used by the target RNC. | | |
+| Chosen Encryption Algorithm | O | | 9.2.1.14 | Indicates the Encryption algorithm that will be used by the target RNC. | YES | ignore |
+| Higher bitrates than 16 Mbps flag | O | | 9.2.3.54 | May only be included towards the PS domain. | YES | ignore |
+| CSG Id | O | | 9.2.1.85 | Applicable only to Enhanced Relocation from RNC towards hybrid cell | YES | reject |
+| Cell Access Mode | O | | 9.2.1.93 | Applicable only to Enhanced Relocation from RNC towards hybrid cell | YES | reject |
+| Tunnel Information for BBF | O | | Tunnel Information 9.2.2.6 | Indicating HNB's Local IP Address assigned by the broadband access provider, UDP port Number. | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.78 ENHANCED RELOCATION COMPLETE RESPONSE
+
+This message is sent by the CN to inform the RNC that an enhanced relocation is completed in CN.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|--------------------|-----------------------|---------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| RABs Setup List | O | | | | YES | ignore |
+| >RABs Setup Item IEs | | 1 to | | | EACH | reject |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>RAB Parameters | O | | 9.2.1.3 | | - | |
+| >>User Plane Information | M | | | | | |
+| >>>User Plane Mode | M | | 9.2.1.18 | | - | |
+| >>>UP Mode Versions | M | | 9.2.1.19 | | - | |
+| >>Transport Layer Address | O | | 9.2.2.1 | | - | |
+| >>Iu Transport Association | O | | 9.2.2.2 | Related to TLA above. | - | |
+| >>Offload RAB parameters | O | | 9.2.1.94 | Applicable only for SIPTO at Iu-PS. | YES | ignore |
+| RABs To Be Released List | O | | | | YES | ignore |
+| >RABs To Be Released Item | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.91 | | YES | ignore |
+| MSISDN | O | | 9.2.1.95 | Applicable only for SIPTO at Iu-PS. | YES | ignore |
+| CSG Membership Status | O | | 9.2.1.92 | Applicable only to Enhanced Relocation from RNC towards hybrid cell | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.79 ENHANCED RELOCATION COMPLETE FAILURE
+
+This message is sent by the CN to inform the RNC that a failure has occurred in the CN during the enhanced relocation procedure.
+
+Direction: CN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Cause | M | | 9.2.1.4 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.80 ENHANCED RELOCATION COMPLETE CONFIRM
+
+This message is sent by the RNC to inform the CN that an enhanced relocation is completed.
+
+Direction: RNC → CN
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| RABs Failed To Initialise List | O | | | | YES | ignore |
+| >RABs Failed To Initialise Item IEs | | 1 to | | | EACH | ignore |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>Cause | M | | 9.2.1.4 | | - | |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.81 RANAP ENHANCED RELOCATION INFORMATION REQUEST
+
+This message is part of a special RANAP Enhanced Relocation Information procedure, and is sent between RNCs during enhanced relocation.
+
+Direction: RNC → RNC.
+
+Signalling bearer mode: Not applicable.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------|----------|--------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Source RNC To Target RNC Transparent Container | M | | 9.2.1.28 | | YES | reject |
+| Old Iu Signalling Connection Identifier CS domain | O | | 9.2.1.38 | | YES | ignore |
+| Global CN-ID CS domain | O | | 9.2.1.46 | | YES | reject |
+| Old Iu Signalling Connection Identifier PS domain | O | | 9.2.1.38 | | YES | ignore |
+| Global CN-ID PS domain | O | | 9.2.1.46 | | YES | reject |
+| RABs To Be Setup List | O | | | | YES | reject |
+| >RABs To Be Setup Item IEs | | 1 to | | | EACH | reject |
+| >>CN Domain Indicator | M | | 9.2.1.5 | | - | |
+| >>RAB ID | M | | 9.2.1.2 | | - | |
+| >>RAB Parameters | M | | 9.2.1.3 | | - | |
+| >>Data Volume Reporting Indication | C – ifPS | | 9.2.1.17 | | - | |
+| >>PDP Type Information | C – ifPS | | 9.2.1.40 | | - | |
+| >>User Plane Information | M | | | | | |
+| >>>User Plane Mode | M | | 9.2.1.18 | | - | |
+| >>>UP Mode Versions | M | | 9.2.1.19 | | - | |
+| >>Data Forwarding TNL Information | O | | | | | |
+| >>>Transport Layer Address | M | | 9.2.2.1 | | | |
+| >>>Transport Association | M | | Iu Transport Association 9.2.2.2 | Related to TLA above. | | |
+| >>Source Side Iu UL TNL Information | O | | | | | |
+| >>>Transport Layer Address | M | | 9.2.2.1 | | - | |
+| >>>Iu Transport Association | M | | 9.2.2.2 | | - | |
+| >>Service Handover | O | | 9.2.1.41 | | - | |
+| >>Alternative RAB Parameter Values | O | | 9.2.1.43 | | - | |
+| >>E-UTRAN Service Handover | O | | 9.2.1.90 | | YES | ignore |
+| >>PDP Type Information extension | O | | 9.2.1.40a | The PDP Type Information extension IE can only be included if PDP Type Information IE is present. | YES | ignore |
+| SNA Access Information | O | | 9.2.3.24 | | YES | ignore |
+| UESBI-Iu | O | | 9.2.1.59 | | YES | ignore |
+| Selected PLMN Identity | O | | 9.2.3.33 | | YES | ignore |
+| CN MBMS Linking Information | O | | | | YES | ignore |
+| >Joined MBMS Bearer Service IEs | | 1 to | | | EACH | ignore |
+| >>TMGI | M | | 9.2.3.37 | | - | |
+| >>PTP RAB ID | M | | 9.2.1.75 | | - | |
+| Integrity Protection Information | O | | 9.2.1.11 | Integrity Protection Information includes key | YES | ignore |
+
+| | | | | | | |
+|-------------------------------|---|--|-----------|---------------------------------------------------------------------------------------------|-----|--------|
+| | | | | and permitted algorithms. | | |
+| Encryption Information | O | | 9.2.1.12 | Integrity Protection Information includes key and permitted algorithms. | YES | ignore |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.91 | | YES | ignore |
+| RAB Parameters List | O | | 9.2.1.102 | Applicable only to RNSAP relocation. | YES | reject |
+| CSG Id | O | | 9.2.1.85 | Applicable only to Enhanced Relocation from RNC towards a hybrid cell and RNSAP relocation. | YES | reject |
+| CSG Membership Status | O | | 9.2.1.92 | Applicable only to Enhanced Relocation from RNC towards a hybrid cell and RNSAP relocation. | YES | reject |
+| Anchor PLMN Identity | O | | 9.2.3.33 | Indicates the PS core network operator in case of SRVCC (see TS 23.251 [39]). | YES | ignore |
+
+| Condition | Explanation |
+|-----------|--------------------------------------------------------------------------------------|
+| IfPS | This IE shall be present if the CN domain indicator IE is set to "PS domain". |
+
+| Range bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+| maxnoofMulticastServicesPerUE | Maximum no. of Multicast Services that a UE can join and leave respectively. Value is 128. |
+
+## 9.1.82 RANAP ENHANCED RELOCATION INFORMATION RESPONSE
+
+This message is the response message of a special RANAP Enhanced Relocation Information procedure, and is sent between RNCs during enhanced relocation.
+
+Direction: RNC → RNC.
+
+Signalling bearer mode: Not applicable.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|--------------------|----------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Target RNC To Source RNC Transparent Container | O | | 9.2.1.30 | | YES | ignore |
+| RABs Setup List | O | | | | YES | ignore |
+| >RABs Setup Item IEs | | 1 to | | | EACH | reject |
+| >>CN Domain Indicator | M | | 9.2.1.5 | | - | - |
+| >>RAB ID | M | | 9.2.1.2 | | - | - |
+| >>Data Forwarding Information | O | | | | - | |
+| >>>DL Forwarding Transport Layer Address | M | | Transport Layer Address 9.2.2.1 | | - | |
+| >>>DL Forwarding Transport Association | M | | Iu Transport Association 9.2.2.2 | Related to TLA above. | - | |
+| >>Assigned RAB Parameter Values | O | | 9.2.1.44 | | - | |
+| RABs Failed To Setup List | O | | | | YES | ignore |
+| >RABs Failed To Setup Item IEs | | 1 to | | | EACH | ignore |
+| >>CN Domain Indicator | M | | 9.2.1.5 | | - | - |
+| >>RAB ID | M | | 9.2.1.2 | | - | - |
+| >>Cause | M | | 9.2.1.4 | | - | - |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+## 9.1.83 SRVCC CS KEYS REQUEST
+
+This message is sent by the source RNC to the source SGSN to request security information for SRVCC operation.
+
+Direction: RNC → SGSN.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+
+## 9.1.84 SRVCC CS KEYS RESPONSE
+
+This message is sent by the source SGSN to the source RNC. It contains information necessary for SRVCC operation.
+
+Direction: SGSN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | reject |
+| Integrity Protection Key | M | | BIT STRING (128) | | YES | reject |
+| Encryption Key | M | | BIT STRING (128) | | YES | reject |
+| SRVCC Information | M | | 9.2.1.89 | | YES | reject |
+| Criticality Diagnostics | O | | 9.2.1.35 | | YES | ignore |
+
+## 9.1.85 UE RADIO CAPABILITY MATCH REQUEST
+
+This message is sent by the SGSN in order to request indications about compatibility between UE radio capabilities and network configuration.
+
+Direction: SGSN → RNC.
+
+Signalling bearer mode: Connection oriented.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+
+## 9.1.86 UE RADIO CAPABILITY MATCH RESPONSE
+
+This message is sent by the RNC in order to transfer indications about compatibility between UE radio capabilities and network configuration
+
+Direction: RNC → SGSN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.1 | | YES | ignore |
+| Voice Support Match Indicator | M | | 9.2.1.113 | | YES | ignore |
+
+## 9.2 Information Element Definitions
+
+### 9.2.0 General
+
+Subclause 9.2 presents the RANAP IE definitions in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence.
+
+When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:
+
+- The first bit (leftmost bit) contains the most significant bit (MSB);
+- The last bit (rightmost bit) contains the least significant bit (LSB);
+- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information;
+
+### 9.2.1 Radio Network Layer Related IEs
+
+#### 9.2.1.1 Message Type
+
+The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|
+| Message Type | | | | Assumed max no of messages is 256. |
+| >Procedure Code | M | | (RAB Assignment,
RAB Release Request,
Iu Release Request,
Iu Release,
Relocation Preparation,
Relocation Resource Allocation,
Relocation Detect,
Relocation Complete
Relocation Cancel,
SRNS Context Transfer,
SRNS Data Forwarding Initiation,
SRNS Context Forwarding from Source RNC to CN,
SRNS Context Forwarding to Target RNC from CN,
Paging,
Common ID,
CN Invoke Trace,
Security Mode Control,
Location Reporting Control
Location Report,
Data Volume Report,
Initial UE Message
Direct Transfer,
Overload Control,
Reset,
Error Indication,
CN Deactivate Trace,
RANAP Relocation Information,
RANAP Enhanced Relocation Information
Reset Resource,
...
RAB Modify Request,
Location Related Data,
Information Transfer,
UE Specific Information,
Direct Information Transfer,
Uplink Information Exchange,
MBMS Session Start,
MBMS Session Update,
MBMS Session Stop,
MBMS UE Linking,
MBMS Registration,
MBMS CN De-Registration,
MBMS RAB Establishment Indication,
MBMS RAB Release,
Enhanced Relocation Complete,
Enhanced Relocation Complete Confirm,
SRVCC Preparation | |
+
+| | | | | |
+|------------------|---|--|-------------------------------------------------------------------------------------|--|
+| | | | ) | |
+| >Type of Message | M | | CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome, ...) | |
+
+### 9.2.1.2 RAB ID
+
+This element uniquely identifies a radio access bearer for a specific CN domain for a particular UE, which makes the RAB ID unique over one Iu connection. The RAB ID shall remain the same for the duration of the RAB even when the RAB is relocated to another Iu connection.
+
+The purpose of the element is to bind data stream from the Non Access Stratum point of view (e.g. bearer of call or PDP context) and radio access bearer in Access Stratum. The value is also used in the RNC to relate Radio Bearers to a RAB. The content of this information element is transferred unchanged from the CN node (i.e. MSC or SGSN) via the RNC to the UE by RANAP messages and RRC messages. For RRC messages refer to TS 25.331 [10].
+
+The element contains binary representation of either the Stream Identifier (SI) for CS domain or the Network Service Access Point Identifier (NSAPI) for PS domain. These identifiers are coded in the RAB ID element in accordance with the coding of the *Stream Identifier* IE and with the coding of the *NSAPI* IE in TS 24.008 [8].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RAB ID | M | | BIT STRING (8) | |
+
+### 9.2.1.3 RAB Parameters
+
+The purpose of the *RAB parameters* IE group and other parameters within the *RAB parameters* IE group is to indicate all RAB attributes as defined in TS 23.107 [7] for both directions.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RAB parameters | | | | | | |
+| >Traffic Class | M | | ENUMERATED
(conversational,
streaming,
interactive,
background,
...) | Desc.: This IE indicates the type of application for which the Radio Access Bearer service is optimised. | - | |
+| >RAB Asymmetry Indicator | M | | ENUMERATED
(Symmetric bidirectional,
Asymmetric Unidirectional downlink,
Asymmetric Unidirectional Uplink,
Asymmetric Bidirectional,
...) | Desc.: This IE indicates asymmetry or symmetry of the RAB and traffic direction. | - | |
+| >Maximum Bit Rate | M | 1 to
Separate
TrafficDirections> | INTEGER
(1..16,000,000) | Desc.: This IE indicates the maximum number of bits delivered by UTRAN and to UTRAN at a SAP within a period of time, divided by the duration of the period.
The unit is: bit/s
This IE shall be ignored if Supported Maximum Bite Rate IE is present.
Usage:
When nbr-SeparateTrafficDirections is equal to 2, then Maximum Bit Rate attribute for downlink is signalled first, then Maximum Bit Rate attribute for uplink. | - | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------|------------------------|---------------------------------------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RAB parameters | | | | | | |
+| >Guaranteed Bit Rate | C-iftrafficConv-Stream | 1 to | INTEGER (0..16,000,000) | Desc.: This IE indicates the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. The unit is: bit/s.
This IE shall be ignored if Supported Guaranteed Bite Rate IE is present.
Usage:
- 1. When nbr-SeparateTrafficDirections is equal to 2, then Guaranteed Bit Rate for downlink is signalled first, then Guaranteed Bit Rate for uplink.
- 2. Delay and reliability attributes only apply up to the guaranteed bit rate.
- 3. Conditional valuefor the case of Support Mode for pre-defined SDU sizes:
Set to highest not rate controllable bitrate, where bitrate is either - – one of the RAB subflow combination bitrate IEs (when present)
- or
- – one of the calculated values given when dividing the compound Subflow combination SDU sizes by the value of the IE Maximum SDU Size and then multiplying this result by the value of the IE Maximum Bit Rate.
| - | |
+| >Delivery Order | M | | ENUMERATED (delivery order requested, delivery order not requested) | Desc: This IE indicates whether the RAB shall provide in-sequence SDU delivery or not.
Usage:
Delivery order requested: in sequence delivery shall be guaranteed by UTRAN on all RAB SDUs
Delivery order not requested: in sequence delivery is not required from UTRAN.
| - | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|------------------------|-----------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RAB parameters | | | | | | |
+| >Maximum SDU Size | M | | INTEGER (0..32768) | Desc.: This IE indicates the maximum allowed SDU size.
The unit is: bit.
Usage:
Conditional value:
Set to largest RAB Subflow Combination compound SDU size (when present) among the different RAB Subflow Combinations. | - | |
+| >SDU parameters | | 1 to | See below | Desc.: This IE contains the parameters characterizing the RAB SDUs
Usage:
Given per subflow with first occurrence corresponding to subflow#1 etc... | - | |
+| >Transfer Delay | C-iftrafficConv-Stream | | INTEGER (0..65535) | Desc.: This IE indicates the maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a RAB, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP
The unit is: millisecond. | - | |
+| >Traffic Handling Priority | C-iftrafficInteraction | | INTEGER {spare (0), highest (1), ..., lowest (14), no priority (15)} (0..15) | Desc.: This IE specifies the relative importance for handling of all SDUs belonging to the radio access bearer compared to the SDUs of other bearers
Usage:
Values between 1 and 14 are ordered in decreasing order of priority, '1' being the highest and '14' the lowest.
Value 0 shall be treated as a logical error if received. | - | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|------------------------|-----------------------------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RAB parameters | | | | | | |
+| >Allocation/
Retention
priority | O | | See below | Desc.: This IE specifies the relative importance compared to other Radio access bearers for allocation and retention of the Radio access bearer.
Usage:
If this IE is not received, the request is regarded as it cannot trigger the pre-emption process and it is vulnerable to the pre-emption process. | - | |
+| >Source
Statistics
Descriptor | C-iftrafficConv-Stream | | ENUMERATED (speech, unknown, ...) | Desc.: This IE specifies characteristics of the source of submitted SDUs. | - | |
+| >Relocation
Requirement | O | | ENUMERATED (lossless, none, ..., realtime) | This IE shall be present for RABs towards the PS domain, otherwise it shall not be present.
Desc.: This IE is no longer used.
Usage:
It shall always be set to "none" when sent and it shall always be ignored when received.
Note: If the IE is not received, the procedure should continue based on the other IEs/IE Groups. | - | |
+| >Signalling
Indication | O | | ENUMERATED (signalling, ..) | Desc.: Indicates the signalling nature of the submitted SDUs. | YES | ignore |
+| >Extended
Maximum Bit
Rate | O | 1 to
Separate
TrafficDir
ections> | INTEGER (16,000,001..256,000,000) | Desc.: This IE indicates the maximum number of bits delivered by UTRAN and to UTRAN at a SAP within a period of time, divided by the duration of the period.
The unit is: bit/s.
Usage:
When nbr-SeparateTrafficDirections is equal to 2, then Maximum Bit Rate attribute for downlink is signalled first, then Maximum Bit Rate attribute for uplink. | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|---------------------------------------|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RAB parameters | | | | | | |
+| >Extended Guaranteed Bit Rate | O | 1 to | INTEGER (16,000,001..256,000,000) | Desc.: This IE indicates the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. The unit is: bit/s.
Usage:
1. When nbr-SeparateTrafficDirections is equal to 2, then Guaranteed Bit Rate for downlink is signalled first, then Guaranteed Bit Rate for uplink.
2. Delay and reliability attributes only apply up to the guaranteed bit rate. | YES | reject |
+| >Supported Maximum Bit Rate | | 0 to | INTEGER (1..1,000,000,000, ...) | Desc.: This IE indicates the maximum number of bits delivered by UTRAN and to UTRAN at a SAP within a period of time, divided by the duration of the period.
The unit is: bit/s.
Usage:
When nbr-SeparateTrafficDirections is equal to 2, then Maximum Bit Rate attribute for downlink is signalled first, then Maximum Bit Rate attribute for uplink. | YES | reject |
+| >Supported Guaranteed Bit Rate | | 0 to | INTEGER (1..1,000,000,000, ...) | Desc.: This IE indicates the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. The unit is: bit/s.
Usage:
When nbr-SeparateTrafficDirections is equal to 2, then Guaranteed Bit Rate for downlink is signalled first, then Guaranteed Bit Rate for uplink.
Delay and reliability attributes only apply up to the guaranteed bit rate. | YES | reject |
+
+| Range Bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| nbr-SeparateTrafficDirections | Number of Traffic Directions being signalled separately.
Set to 2 if RAB asymmetry indicator is asymmetric bidirectional.
Set to 1 in all other cases. |
+
+| Range Bound | Explanation |
+|--------------------|-------------------------------------------------|
+| maxRABSubflows | Maximum number of Subflows per RAB. Value is 7. |
+
+| Condition | Explanation |
+|----------------------|---------------------------------------------------------------------------------------------------|
+| lftrafficConv-Stream | This IE shall be present if the Traffic Class IE is set to "Conversational" or "Streaming" |
+| lftrafficInteractiv | This IE shall be present if the Traffic Class IE is set to "Interactive" |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------------------|----------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| SDU parameters | | | | | | |
+| >SDU Error Ratio | C-
ifErroneousSDU | | | Desc.: This IE indicates the fraction of SDUs lost or detected as erroneous.
This is a Reliability attribute
Usage:
The attribute is coded as follows:
Mantissa * 10 -exponent | - | |
+| >>Mantissa | M | | INTEGER (1..9) | | | |
+| >>Exponent | M | | INTEGER (1..6) | | | |
+| >Residual Bit Error Ratio | M | | | Desc.: This IE indicates the undetected bit error ratio for each subflow in the delivered SDU.
This is a Reliability attribute.
Usage:
The attribute is coded as follows:
Mantissa * 10 -exponent | - | |
+| >>Mantissa | M | | INTEGER (1..9) | | | |
+| >>Exponent | M | | INTEGER (1..8) | | | |
+| >Delivery Of Erroneous SDU | M | | ENUMERATED (yes, no, no-error-detection-consideration) | Desc.: This IE indicates whether SDUs with detected errors shall be delivered or not. In case of unequal error protection, the attribute is set per subflow
This is a Reliability attribute.
Usage:
Yes: error detection applied, erroneous SDU delivered
No: Error detection is applied, erroneous SDU discarded
no-error-detection-consideration: SDUs delivered without considering error detection.
If the RNC receives this IE set to 'Yes' and the User Plane Mode IE is set to 'transparent mode', it should consider it as 'no-error-detection-consideration'. | - | |
+| >SDU format information Parameter | O | 1 to | See below | Desc.: This IE contains the list of possible exact sizes of SDUs and/or RAB Subflow Combination bit | - | |
+
+| | | | | | | |
+|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+| | | | | rates.
Given per RAB
Subflow
Combination with
first occurrence
corresponding to
RAB Subflow
Combination
number 1.
It shall always be
present for rate
controllable RABs. | | |
+|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+
+| Range Bound | Explanation |
+|---------------------------|----------------------------------------------------------|
+| maxRABSubflowCombinations | Maximum number of RAB Subflow Combinations. Value is 64. |
+
+| Condition | Explanation |
+|------------------|----------------------------------------------------------------------------------------------|
+| IfErroneousSDU | This IE shall be present if the Delivery Of Erroneous SDU IE is set to "Yes" or "No". |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| SDU Format Information Parameter | | | | At least one of the Subflow SDU size IE and the RAB Subflow Combination bit rate IE shall be present when SDU format information Parameter IE is present. For the case subflow SDUs are transmitted at constant time interval, only one of the two IEs shall be present. Whenever only one IE is included, it shall be the same for all RAB Subflow Combinations. | - | |
+| >Subflow SDU Size | O | | INTEGER (0..4095) | Desc.: This IE indicates the exact size of the SDU. The unit is: bit.
Usage: This IE is only used for RABs that have predefined SDU size(s). It shall be present for RABs having more than one subflow. For RABs having only one subflow, this IE shall be present only when the RAB is rate controllable and the SDU size of some RAB Subflow Combination(s) is different than the IE Maximum SDU Size . When this IE is not present and SDU format information Parameter is present, then the Subflow SDU size for the only existing subflow takes the value of the IE Maximum SDU size . | - | |
+| >RAB Subflow Combination Bit Rate | O | | INTEGER (0..16,000,000) | Desc.: This IE indicates the RAB Subflow Combination bit rate. The unit is: bit/s.
Usage: When this IE is not present and SDU format information parameter is present then all Subflow SDUs are transmitted (when there is data to be transmitted) at a constant time interval. The value of this IE shall not exceed the maximum value of | - | |
+
+| | | | | | | |
+|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+| | | | | the IEs ' Maximum Bit Rate '.
The value 0 of RAB Subflow Combination bitrate indicates that the RAB uses discontinuous transfer of the SDUs. | | |
+|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Allocation/
Retention Priority | | | | | - | |
+| >Priority Level | M | | INTEGER {spare (0), highest (1), ..., lowest (14), no priority (15)} (0..15) | Desc.: This IE indicates the priority of the request.
Usage:
Values between 1 and 14 are ordered in decreasing order of priority, '1' being the highest and '14' the lowest.
Value 0 shall be treated as a logical error if received.
The priority level and the pre-emption indicators may be used to determine whether the request has to be performed unconditionally and immediately. | | |
+| >Pre-emption Capability | M | | ENUMERATE D(shall not trigger pre-emption, may trigger pre-emption) | Desc.: This IE indicates the pre-emption capability of the request on other RABs
Usage:
The RAB shall not pre-empt other RABs or, the RAB may pre-empt other RABs
The Pre-emption Capability indicator applies to the allocation of resources for a RAB and as such it provides the trigger to the pre-emption procedures/processes of the RNS. | | |
+| >Pre-emption Vulnerability | M | | ENUMERATE D(not pre-emptable, pre-emptable) | Desc.: This IE indicates the vulnerability of the RAB to pre-emption of other RABs.
Usage:
The RAB shall not be pre-empted by other RABs or the RAB may be pre-empted by other RABs.
Pre-emption Vulnerability indicator applies for the entire duration of the RAB, unless modified and as such indicates whether the RAB is a target of the pre-emption procedures/processes of the RNS. | | |
+| >Queuing Allowed | M | | ENUMERATE D(queuing not allowed, queuing allowed) | Desc.: This IE indicates whether the request can be placed into a resource allocation queue or not. | | |
+
+| | | | | | | |
+|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+| | | | | Usage:
Queuing of the RAB
is allowed
Queuing of the RAB
is not allowed
Queuing allowed
indicator applies for
the entire duration of
the RAB, unless
modified. | | |
+|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+
+### 9.2.1.4 Cause
+
+The purpose of the *Cause* IE is to indicate the reason for a particular event for the RANAP protocol.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|
+| Choice Cause | | | | |
+| > Radio Network Layer | | | | |
+| >>Radio Network Layer Cause | M | | INTEGER
(RAB pre-empted(1),
Trelocoverall Expiry(2),
Trelocrep Expiry(3),
Treloccomplete Expiry(4),
Tqueuing Expiry(5),
Relocation Triggered(6),
Unable to Establish During Relocation(8),
Unknown Target RNC(9),
Relocation Cancelled(10),
Successful Relocation(11),
Requested Ciphering and/or Integrity Protection Algorithms not Supported(12),
Conflict with already existing Integrity protection and/or Ciphering information (13),
Failure in the Radio Interface Procedure(14),
Release due to UTRAN Generated Reason(15),
User Inactivity(16),
Time Critical Relocation(17),
Requested Traffic Class not Available(18),
Invalid RAB Parameters Value(19),
Requested Maximum Bit Rate not Available(20),
Requested Maximum Bit Rate for DL not Available(33),
Requested Maximum Bit Rate for UL not Available(34),
Requested Guaranteed Bit Rate not Available(21),
Requested Guaranteed Bit Rate for DL not Available(35),
Requested Guaranteed Bit Rate for UL not Available(36),
Requested Transfer Delay not Achievable(22),
Invalid RAB Parameters Combination(23),
Condition Violation for SDU Parameters(24),
Condition Violation for Traffic Handling Priority(25),
Condition Violation for Guaranteed Bit Rate(26),
User Plane Versions not Supported(27),
Iu UP Failure(28),
TRELOCAlloc Expiry (7),
Relocation Failure in Target CN/RNC or Target System (29),
Invalid RAB ID(30),
No remaining RAB(31),
Interaction with other | Value range is 1 – 64. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Choice Cause | | | | |
+| >Radio Network Layer | | | procedure(32),
Repeated Integrity Checking Failure(37),
Requested Request Type not supported(38),
Request superseded(39),
Release due to UE generated signalling connection release(40),
Resource Optimisation Relocation(41),
Requested Information Not Available(42),
Relocation desirable for radio reasons (43),
Relocation not supported in Target RNC or Target system(44),
Directed Retry (45),
Radio Connection With UE Lost(46),
RNC unable to establish all RFCs (47),
Deciphering Keys Not Available(48),
Dedicated Assistance data Not Available(49),
Relocation Target not allowed(50),
Location Reporting Congestion(51),
Reduce Load in Serving Cell (52),
No Radio Resources Available in Target cell (53),
GERAN lu-mode failure (54),
Access Restricted Due to Shared Networks(55),
Incoming Relocation Not Supported Due To PUESBINE Feature(56),
Traffic Load In The Target Cell Higher Than In The Source Cell(57),
MBMS - No Multicast Service For This UE(58),
MBMS - Unknown UE ID(59),
Successful MBMS Session Start - No Data Bearer Necessary(60),
MBMS - Superseded Due To NNSF(61),
MBMS - UE Linking Already Done(62),
MBMS - UE De-Linking Failure - No Existing UE Linking(63),
TMGI Unknown(64)) | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| Choice Cause | | | | |
+| > Radio Network Layer | | | | |
+| > Radio Network Layer | | | | |
+| >>Transport Layer Cause | M | | INTEGER
(
Signalling Transport
Resource Failure(65),
Iu Transport Connection
Failed to Establish(66)) | Value range is 65 – 80. |
+| > NAS | | | | |
+| >>NAS Cause | M | | INTEGER
(User Restriction Start
Indication(81),
User Restriction End
Indication(82),
Normal Release(83) ,
CSG Subscription
Expiry(84)) | Value range is 81 – 96. |
+| > Protocol | | | | |
+| >>Protocol Cause | M | | INTEGER
(Transfer Syntax Error(97),
Semantic Error (98),
Message not compatible with
receiver state (99),
Abstract Syntax Error
(Reject) (100),
Abstract Syntax Error (Ignore
and Notify) (101),
Abstract Syntax Error
(Falsely Constructed
Message) (102)) | Value range is 97 – 112. |
+| > Miscellaneous | | | | |
+| >>Miscellaneous Cause | M | | INTEGER
(O&M Intervention(113),
No Resource Available(114),
Unspecified Failure(115),
Network Optimisation(116)) | Value range is 113 – 128. |
+| > Non-standard | | | | |
+| >>Non-standard Cause | M | | INTEGER
() | Value range is 129 – 256.
Cause value 256 shall
not be used. |
+| > Radio Network Layer
Extension | | | | |
+| >>Radio Network Layer
Cause Extension | M | | INTEGER
(IP Multicast Address And
APN Not Valid(257),
MBMS De-Registration
Rejected Due To Implicit
Registration(258),
MBMS - Request
Superseded(259),
MBMS De-Registration
During Session Not
Allowed(260),
MBMS - No Data Bearer
Necessary(261) ,
Periodic Location Information
not Available(262),
GTP Resources
Unavailable(263),
TMGI in Use and
Overlapping MBMS Service
Area (264),
MBMS – No cell in MBMS
Service Area (265), | Value range is 257 – 512. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Choice Cause | | | | |
+| >Radio Network Layer | | | | |
+| | | | No lu CS UP relocation (266)
, Successful MBMS Session Start – IP Multicast Bearer established (267),
CS Fallback triggered (268),
invalid CSG Id (269)) | |
+
+The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action.
+
+| Radio Network Layer cause | Meaning |
+|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Deciphering Keys Not Available | The action failed because RNC is not able to provide requested deciphering keys. |
+| Conflict with already existing Integrity protection and/or Ciphering information | The action was not performed due to that the requested security mode configuration was in conflict with the already existing security mode configuration. |
+| Condition Violation For Guaranteed Bit Rate | The action was not performed due to condition violation for guaranteed bit rate. |
+| Condition Violation For SDU Parameters | The action was not performed due to condition violation for SDU parameters. |
+| Condition Violation For Traffic Handling Priority | The action was not performed due to condition violation for traffic handling priority. |
+| Dedicated Assistance data Not Available | The action failed because RNC is not able to successfully deliver the requested dedicated assistance data to the UE. |
+| Directed Retry | The reason for action is Directed Retry |
+| Failure In The Radio Interface Procedure | Radio interface procedure has failed. |
+| Incoming Relocation Not Supported Due To PUESBINE Feature | The incoming relocation cannot be accepted by the target RNC because of the PUESBINE feature. |
+| Interaction With Other Procedure | Relocation was cancelled due to interaction with other procedure. |
+| Invalid RAB ID | The action failed because the RAB ID is unknown in the RNC. |
+| Invalid RAB Parameters Combination | The action failed due to invalid RAB parameters combination. |
+| Invalid RAB Parameters Value | The action failed due to invalid RAB parameters value. |
+| Iu UP Failure | The action failed due to Iu UP failure. |
+| No remaining RAB | The reason for the action is no remaining RAB. |
+| RAB Pre-empted | The reason for the action is that RAB is pre-empted. |
+| Radio Connection With UE Lost | The action is requested due to losing radio connection to the UE |
+| Release Due To UE Generated Signalling Connection Release | Release requested due to UE generated signalling connection release. |
+| Release Due To UTRAN Generated Reason | Release is initiated due to UTRAN generated reason. |
+| Relocation Cancelled | The reason for the action is relocation cancellation. |
+| Relocation Desirable for Radio Reasons | The reason for requesting relocation is radio related. |
+| Relocation Failure In Target CN/RNC Or Target System | Relocation failed due to a failure in target CN/RNC or target system. |
+| Relocation Not Supported In Target RNC Or Target System | Relocation failed because relocation was not supported in target RNC or target system. |
+| Relocation Target not allowed | Relocation to the indicated target cell is not allowed for the UE in question. |
+| Relocation Triggered | The action failed due to relocation. |
+| Repeated Integrity Checking Failure | The action is requested due to repeated failure in integrity checking. |
+| Request Superseded | The action failed because there was a second request on the same RAB. |
+| Requested Ciphering And/Or Integrity Protection Algorithms Not Supported | The UTRAN or the UE is unable to support the requested ciphering and/or integrity protection algorithms. |
+| Requested Guaranteed Bit Rate For DL Not Available | The action failed because requested guaranteed bit rate for DL is not available. |
+| Requested Guaranteed Bit Rate For UL Not Available | The action failed because requested guaranteed bit rate for UL is not available. |
+| Requested Guaranteed Bit Rate Not Available | The action failed because requested guaranteed bit rate is not available. |
+| Requested Information Not Available | The action failed because requested information is not available. |
+| Requested Maximum Bit Rate For DL Not Available | The action failed because requested maximum bit rate for DL is not available. |
+| Requested Maximum Bit Rate For UL Not Available | The action failed because requested maximum bit rate for UL is not available. |
+| Requested Maximum Bit Rate Not Available | The action failed because requested maximum bit rate is not available. |
+| Requested Request Type Not Supported | The RNC is not supporting the requested location request type either because it doesn't support the requested event or |
+
+| | |
+|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | it doesn't support the requested report area. |
+| Location Reporting Congestion | The action was not performed due to an inability to support location reporting caused by overload. |
+| Requested Traffic Class Not Available | The action failed because requested traffic class is not available. |
+| Requested Transfer Delay Not Achievable | The action failed because requested transfer delay is not achievable. |
+| Resource Optimisation Relocation | The reason for requesting relocation is resource optimisation. |
+| Successful Relocation | The reason for the action is completion of successful relocation. |
+| Time Critical Relocation | Relocation is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection is likely to be dropped if relocation is not performed. |
+| T QUEUING Expiry | The action failed due to expiry of the timer T QUEUING . |
+| T RELOCalloc Expiry | Relocation Resource Allocation procedure failed due to expiry of the timer T RELOCalloc . |
+| T RELOCcomplete Expiry | The reason for the action is expiry of timer T RELOCcomplete . |
+| T RELOCoverall Expiry | The reason for the action is expiry of timer T RELOCoverall . |
+| T RELOCprep Expiry | Relocation Preparation procedure is cancelled when timer T RELOCprep expires. |
+| Unable To Establish During Relocation | RAB failed to establish during relocation because it cannot be supported in the target RNC or the RAB did not exist in the source RNC. |
+| Unknown Target RNC | Relocation rejected because the target RNC is not known to the CN. |
+| User Inactivity | The action is requested due to user inactivity on one or several non real time RABs e.g. in order to optimise radio resource. |
+| User Plane Versions Not Supported | The action failed because requested user plane versions were not supported. |
+| RNC unable to establish all RFCs | RNC couldn't establish all RAB subflow combinations indicated within the RAB Parameters IE. |
+| Reduce Load in Serving Cell | Load on serving cell needs to be reduced. |
+| No Radio Resources Available in Target Cell | Load on target cell is too high. |
+| GERAN Iu-mode failure | The RAB establishment/modification/relocation failed because the GERAN BSC cannot provide an appropriate RAB due to limited capabilities within GERAN. |
+| Access Restricted Due to Shared Networks | Access is not permitted in the cell due to Shared Networks. |
+| Traffic Load In The Target Cell Higher Than In The Source Cell | Relocation to reduce load in the source cell is rejected, as the target cell's traffic load is higher than that in the source cell. |
+| MBMS - No Multicast Service For This UE | The request for the Multicase Service list of one UE was not fulfilled because the UE does not have any active multicast service. |
+| MBMS - Unknown UE ID | The request for the Multicase Service list of one UE was not fulfilled because the CN does not know the UE. |
+| Successful MBMS Session Start - No Data Bearer Necessary | The MBMS Session Start procedure was successfully performed, but the RNC does not have any interested UE. |
+| MBMS - Superseded Due To NNSF | The MBMS Session Start procedure was rejected because of successful operation towards another CN node. |
+| MBMS - UE Linking Already Done | The UE linking failed, because the UE has already been linked to the given Multicast service. |
+| MBMS - UE De-Linking Failure - No Existing UE Linking | The UE de-linking failed, because the UE had not been linked to the given Multicast service. |
+| TMGI Unknown | The requested MBMS action failed because the indicated TMGI is unknown. |
+| Successful MBMS Session Start – IP Multicast Bearer established | The RNC was able to join the indicated IP Multicast Group. |
+
+| Radio Network Layer cause extension | Meaning |
+|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IP Multicast Address And APN Not Valid | The MBMS registration failed because the IP Multicast Address and APN are not valid. |
+| MBMS De-Registration Rejected Due To Implicit Registration | The MBMS De-registration was rejected because of implicit registration. |
+| MBMS - Request Superseded | The MBMS Registration or De-registration was superseded due to another ongoing procedure. |
+| MBMS De-Registration During Session Not Allowed | The MBMS De-registration is not allowed during the MBMS session. |
+| MBMS - No Data Bearer Necessary | The RNC no longer have any UEs interested in the MBMS data bearer. |
+| Periodic Location Information not Available | No UE position estimate was available when the periodic report was triggered. |
+| GTP Resources Unavailable | The RNC initiates RAB Release Request procedure with this error cause value if it received a GTP-U error indication. |
+| TMGI in Use and overlapping MBMS Service Area | The RNC has an MBMS Session up and running with that TMGI, a parallel MBMS session with the same TMGI in another overlapping MBMS Service Area is not allowed. |
+| MBMS - No Cell in MBMS Service Area | The RNC does not have any cell of the indicated MBMS Service Area. |
+| No Iu CS UP relocation | The relocation is triggered by CS call and the source RNC has no Iu CS user plane. |
+| CS Fallback triggered | The relocation was triggered for CS Fallback reason at the source side. |
+| Invalid CSG Id | The CSG ID provided to the target UTRAN was found invalid. |
+
+| Transport Layer cause | Meaning |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------|
+| Iu Transport Connection Failed to Establish | The action failed because the Iu Transport Network Layer connection could not be established. |
+| Signalling Transport Resource Failure | Signalling transport resources have failed (e.g. processor reset ). |
+
+| NAS cause | Meaning |
+|-----------------------------------|------------------------------------------------------------------------------|
+| Normal Release | The release is normal. |
+| User Restriction Start Indication | A location report is generated due to entering a classified area set by O&M. |
+| User Restriction End Indication | A location report is generated due to leaving a classified area set by O&M. |
+| CSG Subscription Expiry | The action is due to the UE becoming a non-member of the currently used CSG. |
+
+| Protocol cause | Meaning |
+|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerning criticality indicated "reject". |
+| Abstract Syntax Error (Ignore And Notify) | The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". |
+| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences. |
+| Message Not Compatible With Receiver State | The received message was not compatible with the receiver state. |
+| Semantic Error | The received message included a semantic error. |
+| Transfer Syntax Error | The received message included a transfer syntax error. |
+
+| Miscellaneous cause | Meaning |
+|----------------------------|-------------------------------------------------------|
+| Network Optimisation | The action is performed for network optimisation. |
+| No Resource Available | No requested resource is available. |
+| O&M Intervention | The action is due to O&M intervention. |
+| Unspecified Failure | Sent when none of the specified cause values applies. |
+
+### 9.2.1.5 CN Domain Indicator
+
+Indicates the CN domain from which the message originates or to which the message is sent.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-----------------------------------|-----------------------|
+| CN Domain Indicator | M | | ENUMERATED (CS domain, PS domain) | |
+
+### 9.2.1.6 Trace Type
+
+Indicates the type of trace information to be recorded. Applicable to GERAN Iu Mode only, not applicable to UTRAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------|
+| Trace Type | M | | OCTET STRING (1) | Coded as the Trace Type specified in 3GPP TS, as defined in TS 52.008 [62]. |
+
+### 9.2.1.7 Trigger ID
+
+Indicates the identity of the entity which initiated the trace. Applicable to GERAN Iu Mode only, not applicable to UTRAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|----------------------------|
+| Trigger ID | M | | OCTET STRING (3..22) | Typically an OMC identity. |
+
+NOTE: Due to inconsistency in the definition of Trigger ID between TS 25.413 and TS 29.002 [24], it shall be ensured that the *Trigger ID* IE is coded with at least the minimum number of required octets.
+
+### 9.2.1.8 Trace Reference
+
+Identifies a trace session and is globally unique within one PLMN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------|-----------------------|
+| Trace Reference | M | | OCTET STRING (2..3) | |
+
+### 9.2.1.9 UE Identity
+
+This element identifies the element to be traced i.e. a subscriber or a user equipment.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Choice UE Identity | | | | |
+| > IMSI | | | | |
+| >>IMSI | M | | OCTET STRING (SIZE (3..8)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit,
- two digits per octet,
- - bit 4 to 1 of octet n encoding digit ,
- - bit 8 to 5 of octet n encoding digit .
Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.
|
+| > IMEI | | | | |
+| >>IMEI | M | | OCTET STRING (SIZE (8)) | - - hexadecimal digits 0 to F, two hexadecimal digits per octet,
- - each hexadecimal digit encoded 0000 to 1111,
- - 1111 used as filler for bits 8 to 5 of last octet,
- - bit 4 to 1 of octet n encoding digit ,
- - bit 8 to 5 of octet n encoding digit .
Number of hexadecimal digits shall be 15.
|
+| > IMEISV | | | | |
+| >>IMEISV | M | | OCTET STRING (SIZE (8)) | - - hexadecimal digits 0 to F, two hexadecimal digits per octet,
- - each hexadecimal digit encoded 0000 to 1111,
- - bit 4 to 1 of octet n encoding digit ,
- - bit 8 to 5 of octet n encoding digit .
Number of hexadecimal digits shall be 16.
|
+
+### 9.2.1.10 OMC ID
+
+A variable length element indicating the destination address of the Operation and Maintenance Center (OMC) to which trace information is to be sent. Applicable to GERAN Iu Mode only, not applicable to UTRAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------|
+| OMC ID | M | | OCTET STRING (3..22) | Coded as the OMC ID specified in UMTS TS, as defined in GSM TS 12.20 [25]. |
+
+NOTE: Due to inconsistency in the definition of OMC ID between TS 25.413 and TS 29.002 [24], it shall be ensured that the *OMC ID* IE is coded with at least the minimum number of required octets.
+
+### 9.2.1.11 Integrity Protection Information
+
+This element contains the integrity protection information (key and permitted algorithms).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------|----------|---------|--------------------------------------------------|-----------------------------------------------|
+| Integrity Protection Information | | | | |
+| > Permitted Integrity Protection Algorithms | | 1 to 16 | | |
+| >>Integrity Protection Algorithm | M | | INTEGER ( standard UIA1 (0), standard UIA2 (1) ) | Value range is 0 to 15. Only two values used. |
+| >Integrity Protection Key | M | | BIT STRING (128) | |
+
+### 9.2.1.12 Encryption Information
+
+This element contains the user data encryption information (key and permitted algorithms) used to control any encryption equipment at the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|---------|--------------------------------------------------------------------|-------------------------------------------------|
+| Encryption Information | | | | |
+| > Permitted Encryption Algorithms | | 1 to 16 | | |
+| >>Encryption Algorithm | M | | INTEGER (no encryption (0), standard UEA1 (1), standard UEA2 (2) ) | Value range is 0 to 15. Only three values used. |
+| >Encryption Key | M | | Bit string (128) | |
+
+### 9.2.1.13 Chosen Integrity Protection Algorithm
+
+This element indicates the integrity protection algorithm being used by the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------|----------|-------|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Chosen Integrity Protection Algorithm | M | | INTEGER ( standard UIA1 (0), standard UIA2 (1), no value (15) ) | Value range is 0 to 15. Only two values used over Iu interface. The value "no value" shall only be used in case of RANAP signalling over MAP/E TS 29.108 [23]. |
+
+### 9.2.1.14 Chosen Encryption Algorithm
+
+This element indicates the encryption algorithm being used by the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------|----------|-------|--------------------------------------------------------------------|-------------------------------------------------|
+| Chosen Encryption Algorithm | M | | INTEGER (no encryption (0), standard UEA1 (1), standard UEA2 (2) ) | Value range is 0 to 15. Only three values used. |
+
+### 9.2.1.15 Categorisation Parameters
+
+Void.
+
+### 9.2.1.16 Request Type
+
+This element indicates the type of location request to be handled by the RNC; the related reported area is either a Service Area or a Geographical Area.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request Type | | | | |
+| >Event | M | | ENUMERATED(
Stop Change of service area,
Direct, Change of service area, ..., Stop Direct, Periodic, Stop Periodic) | |
+| >Report Area | M | | ENUMERATED(
Service Area, Geographical Area, ...) | When the Event IE is set to "Stop Change of service area" or to "Stop Direct", the value of the Report area IE shall be the same as in the LOCATION REPORTING CONTROL message that initiated the location reporting. |
+| >Accuracy Code | O | | INTEGER (0..127) | The requested accuracy "r" is derived from the "accuracy code" k by $r = 10 \times (1.1^k - 1)$ .
The Accuracy Code IE shall be understood as the horizontal accuracy code. |
+
+### 9.2.1.17 Data Volume Reporting Indication
+
+This information element indicates whether or not the RNC has to calculate the unsuccessfully transmitted NAS data amount for a given RAB and to report the amount of unsuccessfully transmitted NAS data when the RAB is released.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|-------|---------------------------------------|-----------------------|
+| Data Volume Reporting Indication | M | | ENUMERATED (do report, do not report) | |
+
+### 9.2.1.18 User Plane Mode
+
+This element indicates the mode of operation of the Iu User plane requested for realising the RAB. The Iu User plane modes are defined in TS 25.415 [6].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|---------------------------------------------------------------------------|---------------------------------------------------------------|
+| User Plane Mode | M | | ENUMERATED (transparent mode, support mode for predefined SDU sizes, ...) | This IE contains the mode of operation of the Iu UP protocol. |
+
+### 9.2.1.19 UP Mode Versions
+
+*UP mode versions* IE is an information element that is sent by CN to RNC. It is a bit string that indicates the versions for the selected Iu UP mode that are required and supported by the CN. The Iu User plane mode versions shall be defined and coded as the "Iu UP Mode versions supported" field defined in TS 25.415 [6]. This reference is applicable for both the transparent mode and the support mode for predefined SDU sizes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------|
+| UP Mode Versions | M | | BIT STRING (16) | Indicates the versions of the selected UP mode that are required and supported by the CN. |
+
+### 9.2.1.20 Chosen UP Version
+
+Void.
+
+### 9.2.1.21 Paging Area ID
+
+This element identifies the area where a PAGING message shall be broadcasted. The Paging area ID is either a Location Area ID or a Routing Area ID.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Paging Area ID | | | | |
+| >LAI | | | | |
+| >>LAI | M | | 9.2.3.6 | |
+| >RAI | | | | |
+| >>RAI | | | | |
+| >>>LAI | M | | 9.2.3.6 | |
+| >>>RAC | M | | 9.2.3.7 | |
+
+### 9.2.1.22 Non Searching Indication
+
+This parameter allows the RNC not to search Common ID when receiving a PAGING message from the CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|---------------------------------------|-----------------------|
+| Non Searching Indication | M | | ENUMERATED (non-searching, searching) | |
+
+### 9.2.1.23 Relocation Type
+
+This information element indicates whether the relocation of SRNS is to be executed with or without involvement of the UE. If the UE is involved then a radio interface handover command shall be sent to the UE to trigger the execution of the relocation. If the UE is not involved then the relocation execution is triggered via Iur.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|--------------------------------------------------------------------------------------------|-----------------------|
+| Relocation Type | M | | ENUMERATED (UE not involved in relocation of SRNS, UE involved in relocation of SRNS, ...) | |
+
+### 9.2.1.24 Source ID
+
+The *Source ID* IE identifies the source for the relocation of SRNS. The Source ID may be e.g. the source RNC-ID (for UMTS-UMTS relocation and UMTS to LTE relocation) or the SAI of the relocation source (in case of UMTS to GSM relocation).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Choice Source ID | | | | | - | |
+| > Source RNC-ID | | | | | - | |
+| >>PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
| - | |
+| >>RNC-ID | M | | INTEGER (0..4095) | If the Extended RNC-ID IE is included in the Source ID IE, the RNC-ID IE shall be ignored. | - | |
+| >>Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| > SAI | | | | | | |
+| >>SAI | M | | 9.2.3.9 | | - | |
+
+### 9.2.1.25 Target ID
+
+The *Target ID* IE identifies the target for the relocation of SRNS. The target ID may be e.g. the target RNC-ID (for UMTS-UMTS relocation) or the Cell Global ID of the relocation target (in case of UMTS to GSM relocation). In case of UMTS to E-UTRAN relocation, the *Target ID* may be either the eNB-ID or the Corresponding RNC-ID of the relocation target.
+
+NOTE: The mapping between the Corresponding RNC-ID and the actual eNB-ID of the relocation target is defined by the network operator and is outside the scope of this specification. Preferably the Target RNC ID used for an eNB contains the LAI and RAC mapped from the GUMMEI of the MME serving the target eNB as specified within TS 23.003 [19]. This avoids configuration of additional identity resolutions and also guarantees that LAIs used for E-UTRAN and UTRAN are mutually exclusive.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Choice Target ID | | | | | - | |
+| >Target RNC-ID | | | | | - | |
+| >>Target RNC-ID | M | | | | | |
+| >>>LAI | M | | 9.2.3.6 | | - | |
+| >>>RAC | O | | 9.2.3.7 | | - | |
+| >>>RNC-ID | M | | INTEGER (0..4095) | If the Extended RNC-ID IE is included in the Target ID IE, the RNC-ID IE shall be ignored.
In case of UMTS to E-UTRAN relocation, if included, this IE will contain the Corresponding RNC-ID of the target eNB. | - | |
+| >>>Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| >CGI | | | | | - | |
+| >>CGI | M | | | | | |
+| >>>PLMN identity | M | | OCTET STRING (SIZE (3)) | - digits 0 to 9, encoded 0000 to 1001,
- 1111 used as filler digit, two digits per octet,
- bits 4 to 1 of octet n encoding digit 2n-1,
- bits 8 to 5 of octet n encoding digit 2n.
- The PLMN identity consists of 3 digits from MCC followed by either
- a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
or
- 3 digits from MNC (in case of a 3 digit MNC). | - | |
+| >>>LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. | - | |
+| >>>CI | M | | OCTET STRING (2) | | - | |
+| >>>RAC | O | | 9.2.3.7 | | YES | ignore |
+| >Target eNB-ID | | | | | | |
+| >>Target eNB-ID | | | | | | |
+| >>>PLMN identity | M | | OCTET STRING (SIZE (3)) | - digits 0 to 9, encoded 0000 to 1001,
- 1111 used as filler digit, two digits per octet,
- bits 4 to 1 of octet n encoding digit 2n-1,
- bits 8 to 5 of octet n encoding digit 2n.
- The PLMN identity consists of 3 digits | - | |
+
+| | | | | | | |
+|------------------|---|--|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|
+| | | | | from MCC followed by either
- a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
or
- 3 digits from MNC (in case of a 3 digit MNC). | | |
+| >>>Choice eNB ID | | | | | - | |
+| >>>>Macro eNB ID | M | | BIT STRING (20) | Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of each cell served by the eNodeB. | - | |
+| >>>>Home eNB ID | M | | BIT STRING (28) | Equal to the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of the cell served by the eNodeB.
NOTE:
Inter-system handover to a Home eNB is not supported in Rel-8. | - | |
+| >>>Selected TAI | M | | 9.2.1.30C | Contains the TAC of the target cell and the PLMN selected for that target cell. | - | |
+
+### 9.2.1.26 MS Classmark 2
+
+The coding of this element is described in TS 25.331 [10].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|----------------------------------------------------------------------------------|
+| MS Classmark 2 | M | | OCTET STRING | Coded as the Mobile Station Classmark 2 IE, as defined in TS 25.331 [10]. |
+
+### 9.2.1.27 MS Classmark 3
+
+The coding of this element is described in TS 25.331 [10].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|----------------------------------------------------------------------------------|
+| MS Classmark 3 | M | | OCTET STRING | Coded as the Mobile Station Classmark 3 IE, as defined in TS 25.331 [10]. |
+
+### 9.2.1.28 Source RNC to Target RNC Transparent Container
+
+The *Source RNC to Target RNC Transparent Container* IE is an information element that is produced by the source RNC and is transmitted to the target RNC. In inter-system handovers to UTRAN, the IE is transmitted from the external relocation source to the target RNC.
+
+This IE is transparent to the CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------------------|-------------------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RRC Container | M | | OCTET STRING | | - | |
+| Number of lu Instances | M | | INTEGER (1..2) | | - | |
+| Relocation Type | M | | 9.2.1.23 | | - | |
+| Chosen Integrity Protection Algorithm | O | | 9.2.1.13 | Indicates the integrity protection algorithm. | - | |
+| Integrity Protection Key | O | | Bit String (128) | | - | |
+| Chosen Encryption Algorithm | O | | 9.2.1.14 | Indicates the algorithm for ciphering of signalling data. | - | |
+| Ciphering Key | O | | Bit String (128) | | - | |
+| Chosen Encryption Algorithm | O | | 9.2.1.14 | Indicates the algorithm for ciphering of CS user data. | - | |
+| Chosen Encryption Algorithm | O | | 9.2.1.14 | Indicates the algorithm for ciphering of PS user data. | - | |
+| d-RNTI | C - ifUEnotinvol ved | | INTEGER (0..1048575 ) | | - | |
+| Target Cell ID | C - ifUEinvolved | | INTEGER (0..2684354 55) | This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3] or Cell Identity IE as defined in TS 25.331[10] if the target is a HNB TS 25.467 [55]. | - | |
+| RAB TrCH Mapping | O | 1 to | | | - | |
+| >RAB ID | M | | 9.2.1.2 | | - | |
+| > RAB Subflow | M | 1 to | | The RAB Subflows shall be presented in an order that corresponds to the order in which the RBs are presented per RAB in the RRC container included in this IE. | - | |
+| >> Transport Channel IDs | | | | | - | |
+| >>>DCH ID | O | | INTEGER (0..255) | The DCH ID is the identifier of an active dedicated transport channel. It is unique for each active DCH among the active DCHs simultaneously allocated for the same UE. | - | |
+| >>>DSCH ID | O | | INTEGER (0..255) | The DSCH ID is the identifier of an | - | |
+
+| | | | | | | |
+|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------|--|--|
+| | | | | active downlink shared transport channel. It is unique for each DSCH among the active DSCHs simultaneously allocated for the same UE. | | |
+|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------|--|--|
+
+| | | | | | | |
+|--------------------------|---|---------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| >>>USCH ID | O | | INTEGER (0..255) | The USCH ID is the identifier of an active uplink shared transport channel. It is unique for each USCH among the active USCHs simultaneously allocated for the same UE. | - | |
+| >>>HS-DSCH MAC-d Flow ID | O | | INTEGER (0..7) | The HS-DSCH MAC-d Flow ID is the identifier of an HS-DSCH MAC-d flow over Iur. | YES | ignore |
+| >>>E-DCH MAC-d Flow ID | O | | INTEGER (0..7) | The E-DCH MAC-d Flow ID is the identifier of an E-DCH MAC-d flow over Iur. | YES | ignore |
+| >CN Domain Indicator | M | | 9.2.1.5 | | YES | ignore |
+| SRB TrCH Mapping | O | 1 to | | | GLOBAL | reject |
+| >SRB ID | M | | INTEGER (1..32) | The SRB ID is the absolute value of the SRB. | - | |
+| >DCH ID | O | | INTEGER (0..255) | The DCH ID is the identifier of an active dedicated transport channel over Iur. It is unique for each active DCH among the active DCHs simultaneously allocated for the same UE. | - | |
+| >DSCH ID | O | | INTEGER (0..255) | The DSCH ID is the identifier of an active downlink shared transport channel over Iur. It is unique for each DSCH among the active DSCHs simultaneously allocated for the same UE. | - | |
+| >USCH ID | O | | INTEGER (0..255) | The USCH ID is the identifier of an active uplink shared transport channel over Iur. It is unique for each USCH among the active USCHs simultaneously allocated for the same UE. | - | |
+| >HS-DSCH MAC-d Flow ID | O | | INTEGER (0..7) | The HS-DSCH MAC-d Flow ID is the identifier of an HS-DSCH MAC-d flow over Iur. | YES | ignore |
+| >E-DCH MAC-d Flow ID | O | | INTEGER (0..7) | The E-DCH MAC-d Flow ID is the | YES | ignore |
+
+| | | | | | | |
+|--------------------------------------------------|---|--|----------------------------------------------------|-------------------------------------------------------------------------------------|-----|--------|
+| | | | | identifier of an E-DCH MAC-d flow over Iur. | | |
+| Cell Load Information Group | O | | 9.2.1.60 | For "Cell Load-Based Inter-System Handover". | YES | ignore |
+| Trace Recording Session Information | O | | 9.2.1.66 | | YES | ignore |
+| MBMS Linking Information | O | | ENUMERATED (UE-has-joined-Multicast-Services, ...) | | YES | ignore |
+| d-RNTI for No IuCS UP | O | | INTEGER (0..1048575) | | YES | reject |
+| UE History Information | O | | OCTET STRING | Defined in TS 36.413 [49]. | YES | ignore |
+| Subscriber Profile ID for RAT/Frequency priority | O | | 9.2.1.86 | | YES | ignore |
+| SRVCC Information | O | | 9.2.1.89 | Included only in case of intra-UMTS SRVCC. | YES | reject |
+| PS RAB To Be Replaced | O | | RAB ID 9.2.1.2 | Included only in case of intra-UMTS SRVCC. | YES | reject |
+| CSFB Information | O | | ENUMERATED (CSFB, CSFB High Priority, ...) | | YES | ignore |
+| IRAT Measurement Configuration | O | | 9.2.1.96 | | YES | ignore |
+| Management Based MDT Allowed | O | | 9.2.1.110 | | YES | ignore |
+| Management Based MDT PLMN List | O | | MDT PLMN List 9.2.1.116 | | YES | ignore |
+| Last E-UTRAN PLMN Identity | O | | 9.2.3.33 Selected PLMN Identity | Indicates the E-UTRAN PLMN ID where the UE formerly requested CS Fallback to UTRAN. | YES | ignore |
+
+| Condition | Explanation |
+|-----------------|--------------------------------------------------------------------------------------------------------------|
+| IfUEnotinvolved | This IE shall be present if the Relocation type IE is set to "UE not involved in relocation of SRNS". |
+| IfUEinvolved | This IE shall be present if the Relocation type IE is set to "UE involved in relocation of SRNS". |
+
+| Range bound | Explanation |
+|----------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+| maxRABSubflows | Maximum no. of subflows per RAB. Value is 7. |
+| maxnoofSRBs | Maximum no. of SRBs per RAB. Value is 8. |
+
+## 9.2.1.29 Old BSS to New BSS Information
+
+The coding of this element is described in TS 48.008 [11].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| Old BSS To New BSS Information | M | | OCTET STRING | Coded as the Old BSS to New BSS information elements field of the Old BSS to New BSS Information IE defined in TS 48.008 [11]. |
+
+### 9.2.1.30 Target RNC to Source RNC Transparent Container
+
+The *Target RNC to Source RNC Transparent Container* IE is an information element that is produced by the target RNC and is transmitted to the source RNC. In inter-system handovers to UTRAN, the IE is transmitted from the target RNC to the external relocation source.
+
+This IE is transparent to CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------|
+| RRC Container | M | | OCTET STRING | |
+| d-RNTI | O | | INTEGER (0..1048575) | May be included to allow the triggering of the Relocation Detect procedure from the Iur Interface. |
+
+### 9.2.1.30a Source to Target Transparent Container
+
+The *Source to Target Transparent Container* IE is an information element that is provided by the source RAN node to the target RAN node.
+
+This IE is transparent to CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Source to Target Transparent Container | M | | OCTET STRING | This IE includes a transparent container from the source RAN node to the target RAN node. In inter-system handovers from UTRAN, the IE is encoded according to the specifications of the target system.
Note: In the current version of this specification, this IE may either carry the Source RNC to Target RNC Transparent Container or the Source eNB to Target eNB Transparent Container IE as defined in TS 36.413 [49]. |
+
+### 9.2.1.30b Target to Source Transparent Container
+
+The *Target to Source Transparent Container* IE is an information element that is provided by the target RAN node to the source RAN node.
+
+This IE is transparent to CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Target to Source Transparent Container | M | | OCTET STRING | Note: In the current version of this specification, this IE may either carry the Target RNC to Source RNC Transparent Container or the Target eNB to Source eNB Transparent Container IE as defined in TS 36.413 [49]. |
+
+### 9.2.1.30c TAI
+
+This element is used to uniquely identify a Tracking Area as defined in TS 36.413 [49].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- The Selected PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
- or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| TAC | M | | OCTET STRING (SIZE (2)) | |
+
+### 9.2.1.31 L3 Information
+
+The coding of this element is described in TS 48.008 [11].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| L3 Information | M | | OCTET STRING | Coded as the value part of the Layer 3 Information IE defined in TS 48.008 [11] (i.e. excluding the Element Identifier and the Length fields). |
+
+### 9.2.1.32 Number of Steps
+
+Indicates the number of steps to reduce traffic in overload situation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------|-----------------------|
+| Number Of Steps | M | | INTEGER (1..16) | |
+
+### 9.2.1.33 DL N-PDU Sequence Number
+
+This IE indicates the radio interface sequence number (PDCP) TS 25.323 [17] of the next downlink N-PDU (PDCP SDU) that would have been sent to the UE by a source system.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DL N-PDU Sequence Number | M | | INTEGER (0 ..65535) | This IE indicates the sequence number of the next DL N-PDU that would have been sent to the UE by a source system. This is the 16 bit sequence number. |
+
+### 9.2.1.34 UL N-PDU Sequence Number
+
+This IE indicates the radio interface sequence number (PDCP) TS 25.323 [17] of the next uplink N-PDU (PDCP SDU) that would have been expected from the UE by a source system.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UL N-PDU Sequence Number | M | | INTEGER (0 ..65535) | This IE indicates the sequence number of the next UL N-PDU that would have been expected from the UE by a source system. This is the 16 bit sequence number. |
+
+### 9.2.1.35 Criticality Diagnostics
+
+The *Criticality Diagnostics* IE is sent by the RNC or the CN when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing.
+
+For further details on how to use the *Criticality Diagnostics* IE, see Annex A.2.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Criticality Diagnostics | | | | | | |
+| >Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error. | | |
+| >Triggering Message | O | | ENUMERATE D(initiating message, successful outcome, unsuccessful outcome, outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | | |
+| >Procedure Criticality | O | | ENUMERATE D(reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | | |
+| Information Element Criticality Diagnostics | | 0 to | | | | |
+| >IE Criticality | M | | ENUMERATE D(reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | | |
+| >IE ID | M | | INTEGER (0..65535) | The IE ID of the not understood or missing IE. | | |
+| >Repetition Number | O | | INTEGER (0..255) | The Repetition Number IE gives
- in case of a not understood IE:
The number of occurrences of the reported IE up to and including the not understood occurrence - in case of a missing IE:
The number of occurrences up to but not including the missing occurrence.
Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.
| | |
+| >Message Structure | O | | 9.2.1.42 | The Message Structure IE describes | YES | ignore |
+
+| | | | | | | |
+|----------------|---|--|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|
+| | | | | the structure where the not understood or missing IE was detected.
This IE is included if the not understood IE is not the top level of the message. | | |
+| >Type of Error | M | | ENUMERATE
D(not understood, missing, ...) | | YES | ignore |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------------------------------------------------------------------|
+| maxnooferrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256. |
+
+### 9.2.1.36 Key Status
+
+This IE tells if the keys included in a SECURITY MODE COMMAND message are new or if they have been used previously.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------|-----------------------|
+| Key Status | M | | ENUMERATED (old, new, ...) | |
+
+### 9.2.1.37 DRX Cycle Length Coefficient
+
+This IE indicates the DRX cycle length coefficient (k) as defined in TS 25.331 [10].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|-----------------------|-----------------------|
+| DRX Cycle Length Coefficient | M | | INTEGER (6..9) | |
+
+### 9.2.1.38 Iu Signalling Connection Identifier
+
+This IE uniquely identifies an Iu signalling connection between a given RNC and a given CN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Iu Signalling Connection Identifier | M | | BIT STRING (SIZE(24)) | The most significant bit of this IE shall indicate the node, that has assigned the value.
MSB = "0": assigned by the RNC;
MSB = "1": assigned by the CN. |
+
+### 9.2.1.39 Global RNC-ID
+
+The Global RNC-ID is used to globally identify an RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| RNC-ID | M | | INTEGER (0..4095) | If the Extended RNC-ID IE is included in the message, the RNC-ID IE shall be ignored. |
+
+### 9.2.1.39a Extended RNC-ID
+
+The Extended RNC-ID is used to identify an RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Extended RNC-ID | M | | INTEGER (4096..65535) | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.
Note: Application of the Extended RNC-ID IE to very large networks is FFS.
|
+
+### 9.2.1.40 PDP Type Information
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-----------------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PDP Type Information | M | 1 to | ENUMERATED(empty, PPP, OSP:IHOSS, IPv4, IPv6,...) | PDP Type is defined in TS 24.008 [8], and the restrictions on usage shall comply with TS 24.008 [8].
Usage:
When the IE is repeated then PDP Type for downlink is signalled first, followed by PDP Type for uplink; when the IE is not repeated, the PDP Type shall apply to both uplink and downlink.
OSP:IHOSS: This value shall not be used.
|
+
+| Range bound | Explanation |
+|----------------------|-----------------------------------------------------------------|
+| maxnoofPDPDirections | Number of directions for which PDP Type is signalled separately |
+
+### 9.2.1.40a PDP Type Information extension
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-----------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PDP Type Information extension | M | 1 to | ENUMERATED(IPv4 and IPv6,...) | PDP Type is defined in TS 24.008 [8], and the restrictions on usage shall comply with TS 24.008 [8].
Usage:
When the IE is repeated then PDP Type for downlink is signalled first, followed by PDP Type for uplink; when the IE is not repeated, the PDP Type shall apply to both uplink and downlink. |
+
+| Range bound | Explanation |
+|----------------------|-----------------------------------------------------------------|
+| maxnoofPDPDirections | Number of directions for which PDP Type is signalled separately |
+
+### 9.2.1.41 Service Handover
+
+This IE tells if intersystem handover to GSM should, should not, or shall not be performed for a given RAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Service Handover | M | | ENUMERATED (Handover to GSM should be performed, Handover to GSM should not be performed, Handover to GSM shall not be performed, ...) | |
+
+### 9.2.1.42 Message Structure
+
+The *Message Structure* IE gives information for each level with assigned criticality in a hierarchical message structure from top level down to the lowest level above the reported level for the occurred error (reported in the *Information Element Criticality Diagnostics* IE).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message structure | | 1 to | | The first repetition of the Message Structure IE corresponds to the top level of the message. The last repetition of the Message Structure IE corresponds to the level above the reported level for the occurred error of the message. | GLOBAL | ignore |
+| >IE ID | M | | INTEGER (0..65535) | The IE ID of this level's IE containing the not understood or missing IE. | - | |
+| >Repetition Number | O | | INTEGER (1..256) | The Repetition Number IE gives, if applicable, the number of occurrences of this level's reported IE up to and including the occurrence containing the not understood or missing IE.
Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.
| - | |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------------------------------------|
+| maxnooflevels | Maximum no. of message levels to report. The value for maxnooflevels is 256. |
+
+### 9.2.1.43 Alternative RAB Parameter Values
+
+The purpose of the *Alternative RAB Parameter Values* IE is to indicate that:
+
+- Either RAB QoS negotiation is allowed for certain RAB parameters and, in some cases, to indicate also which alternative values to be used in the negotiation;
+- Or an alternative RAB configuration can be requested by the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------|--------------------------------------|----------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Alternative RAB parameter values | | | | | | |
+| >Alternative Maximum Bit Rate information | O | | | Included only if negotiation is allowed for this IE. | - | |
+| >>Type of Alternative Maximum Bit Rate Information | M | | ENUMERATED (Unspecified, Value range, Discrete values,...) | Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE. | | |
+| >>Alternative Maximum Bit Rates | C - ifValueRangeorDiscreteValuesM BR | 1 to | | For Value Range, one value limit is given here and the other given by Maximum Bit Rate in the RAB Parameters IE. For Discrete Values; 1 to 16 discrete values can be given. | | |
+| >>>Bit Rate | M | 1 to | INTEGER (1..16,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink. | | |
+| >Alternative Guaranteed Bit Rate Information | O | | | Included only if negotiation is allowed for this IE. | - | |
+| >>Type of Alternative Guaranteed Bit Rate Information | M | | ENUMERATED (Unspecified, Value range, Discrete values,...) | Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE. | | |
+| >>Alternative Guaranteed Bit Rates | C - ifValueRangeorDiscreteValuesG BR | 1 to | | For Value Range, one value limit is given here and the other given by Guaranteed Bit Rate in the RAB Parameters IE. For Discrete Values, 1 to 16 discrete values can be given. | | |
+| >>>Bit Rate | M | 1 to | INTEGER (1..16,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink. | | |
+| >Alternative RAB Configuration | O | | RAB Parameters 9.2.1.3 | Indicates the possibility for RNC to request CN to execute the included alternative RAB configuration, e.g., for network-initiated SCUDIF purpose TS 23.172 [43]. | YES | ignore |
+| >Extended Alternative Guaranteed Bit Rate Information | O | | | Included only if negotiation is allowed for this IE. | YES | ignore |
+| >>Type of Extended Alternative Guaranteed Bit | M | | ENUMERATED (Unspecified, Value range, Discrete values,...) | Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is | | |
+
+| | | | | | | |
+|--------------------------------------------------------------|------------------------------------------|----------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|
+| Rate Information | | | | allowed to assign any value equal or below the ones indicated in the RAB Parameters IE. | | |
+| >>Extended Alternative Guaranteed Bit Rates | C - ifValueRangeDiscreteValuesGBR | 1 to <nrb-Alternative Values> | | For Value Range, one value limit is given here and the other given by Extended Guaranteed Bit Rate in the RAB Parameters IE.
For Discrete Values; 1 to 16 discrete values can be given. | | |
+| >>>Extended Bit Rate | M | 1 to <nbr-Separate TrafficDirections> | INTEGER (16,000,001..256,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink. | | |
+| >Extended Alternative Maximum Bit Rate Information | O | | | Included only if negotiation is allowed for this IE. | YES | ignore |
+| >>Type of Extended Alternative Maximum Bit Rate Information | M | | ENUMERATED (Unspecified, Value range, Discrete values,...) | Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE. | | |
+| >>Extended Alternative Maximum Bit Rates | C - ifValueRangeDiscreteValuesMBR | 1 to <nrb-Alternative Values> | | For Value Range, one value limit is given here and the other given by Extended Maximum Bit Rate in the RAB Parameters IE.
For Discrete Values; 1 to 16 discrete values can be given. | | |
+| >>>Extended Bit Rate | M | 1 to <nbr-Separate TrafficDirections> | INTEGER (16,000,001..256,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink. | | |
+| >Supported Alternative Maximum Bit Rate Information | O | | | Included only if negotiation is allowed for this IE. | EACH | reject |
+| >>Type of Supported Alternative Maximum Bit Rate Information | M | | ENUMERATED (Unspecified, Value range, Discrete values,...) | Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE. | - | |
+| >>Supported Alternative Maximum Bit Rates | C - ifValueRangeDiscreteValuesGBR | 1 to <nrb-Alternative Values> | | For Value Range, one value limit is given here and the other given by Supported Maximum Bit Rate in the RAB Parameters IE.
For Discrete Values; 1 to 16 discrete values can be given. | - | |
+| >>>Supported Bit Rate | | 1 to <nbr-Separate TrafficDir | INTEGER (1..1,000,000,000,...) | When nbr-SeparateTrafficDirections is equal to 2, then the Supported Bit Rate attribute for downlink is | - | |
+
+| | | | | | | |
+|------------------------------------------------------------------------------|-------------------------------------|---------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|
+| | | ections> | | signalled first, then the Supported Bit Rate attribute for uplink. | | |
+| >Supported Alternative Guaranteed Bit Rate Information | O | | | Included only if negotiation is allowed for this IE. | EACH | reject |
+| >>Type of Supported Alternative Guaranteed Bit Rate Information | M | | ENUMERATED (Unspecified, Value range, Discrete values,...) | Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE. | - | |
+| >>Supported Alternative Guaranteed Bit Rates | C - ifValueRangeorDiscreteValuesGBR | 1 to | | For Value Range, one value limit is given here and the other given by Supported Guaranteed Bit Rate in the RAB Parameters IE. For Discrete Values; 1 to 16 discrete values can be given. | - | |
+| >>>Supported Bit Rate | | 1 to | INTEGER (1..1,000,000,000,...) | When nbr-SeparateTrafficDirections is equal to 2, then the Supported Bit Rate attribute for downlink is signalled first, then the Supported Bit Rate attribute for uplink. | - | |
+
+| Range Bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| nbr-AlternativeValues | Maximum number of alternative values. Value is 1 in case of Value Range and 16 in case of Discrete Values. |
+| nbr-SeparateTrafficDirections | Number of Traffic Directions being signalled separately. Set to 2 if RAB asymmetry indicator is asymmetric bidirectional. Set to 1 in all other cases. |
+
+| Condition | Explanation |
+|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| ifValueRangeorDiscreteValuesMBR | This IE shall be present if the Type of Alternative Maximum Bit Rates Information IE is set to "Value range" or "Discrete values". |
+| ifValueRangeorDiscreteValuesGBR | This IE shall be present if the Type of Guaranteed Bit Rates Information IE is set to "Value range" or "Discrete values". |
+
+## 9.2.1.44 Assigned RAB Parameter Values
+
+The purpose of the *Assigned RAB Parameter Values* IE is to indicate that RAB QoS negotiation has been performed for certain RAB parameters and which values have been chosen.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|--------------------------------------|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Assigned RAB parameter values | | | | | | |
+| >Assigned Maximum Bit Rate | O | 1 to | INTEGER (1..16,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then Assigned Maximum Bit Rate attribute for downlink is signalled first, then Assigned Maximum Bit Rate attribute for uplink. | - | |
+| >Assigned Guaranteed Bit Rate | O | 1 to | INTEGER (0..16,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then Assigned Guaranteed Bit Rate for downlink is signalled first, then Assigned Guaranteed Bit Rate for uplink. | - | |
+| >Extended Assigned Maximum Bit Rate | O | 1 to | INTEGER (16,000,001..256,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then Assigned Maximum Bit Rate attribute for downlink is signalled first, then Assigned Maximum Bit Rate attribute for uplink. | YES | reject |
+| >Extended Assigned Guaranteed Bit Rate | O | 1 to | INTEGER (16,000,001..256,000,000) | When nbr-SeparateTrafficDirections is equal to 2, then Assigned Guaranteed Bit Rate for downlink is signalled first, then Assigned Guaranteed Bit Rate for uplink. | YES | reject |
+| >Supported Assigned Maximum Bit Rate | O | 0 to | INTEGER (1..1,000,000, 000, ...) | When nbr-SeparateTrafficDirections is equal to 2, then Supported Assigned Maximum Bit Rate attribute for downlink is signalled first, then Supported Assigned Maximum Bit Rate attribute for uplink. | YES | ignore |
+| >Supported Assigned Guaranteed Bit Rate | O | 0 to | INTEGER (1..1,000,000, 000, ...) | When nbr-SeparateTrafficDirections is equal to 2, then Supported Assigned Guaranteed Bit Rate for downlink is signalled first, then Supported Assigned Guaranteed Bit Rate for uplink. | YES | ignore |
+
+| Range Bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| nbr-SeparateTrafficDirections | Number of Traffic Directions being signalled separately.
Set to 2 if RAB asymmetry indicator is asymmetric bidirectional.
Set to 1 in all other cases. |
+
+#### 9.2.1.45 Requested RAB Parameter Values
+
+The purpose of *Requested RAB Parameter Values* IE is to either indicate the RAB parameters for which the included different values are being requested, or indicate that the execution of the alternative RAB configuration is requested.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|--------------------------------------|-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Requested RAB Parameter Values | | | | | | |
+| >Requested Maximum Bit Rate | O | 1 to | INTEGER (1..16,000,000 ) | When nbr-SeparateTrafficDirections is equal to 2, Requested Maximum Bit Rate attribute for downlink is signalled first, then Requested Maximum Bit Rate attribute for uplink. | - | |
+| >Requested Guaranteed Bit Rate | O | 1 to | INTEGER (0..16,000,000 ) | When nbr-SeparateTrafficDirections is equal to 2, Requested Guaranteed Bit Rate for downlink is signalled first, then Requested Guaranteed Bit Rate for uplink. | - | |
+| >Alternative RAB Configuration Request | O | | ENUMERATED (Alternative RAB configuration Requested, ...) | Indicates a request to trigger the execution of the alternative RAB Configuration e.g. for network-initiated SCUDIF purpose TS 23.172 [43]. | YES | ignore |
+| >Extended Requested Maximum Bit Rate | O | 1 to | INTEGER (16,000,001..256,000,000) | When nbr-SeparateTrafficDirections is equal to 2, Requested Maximum Bit Rate attribute for downlink is signalled first, then Requested Maximum Bit Rate attribute for uplink. | YES | reject |
+| >Extended Requested Guaranteed Bit Rate | O | 1 to | INTEGER (16,000,001..256,000,000) | When nbr-SeparateTrafficDirections is equal to 2, Requested Guaranteed Bit Rate for downlink is signalled first, then Requested Guaranteed Bit Rate for uplink. | YES | reject |
+| >Supported Requested Maximum Bit Rate | O | 0 to | INTEGER (1..1,000,000,000, ...) | When nbr-SeparateTrafficDirections is equal to 2, Supported Requested Maximum Bit Rate attribute for downlink is signalled first, then Supported Requested Maximum Bit Rate attribute for uplink. | YES | reject |
+| >Supported Requested Guaranteed Bit Rate | O | 0 to | INTEGER (1..1,000,000,000, ...) | When nbr-SeparateTrafficDirections is equal to 2, Supported Requested Guaranteed Bit Rate for downlink is signalled first, | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|-------|-----------------------|----------------------------------------------------------|-------------|----------------------|
+| Requested RAB Parameter Values | | | | | | |
+| | | | | then Supported Requested Guaranteed Bit Rate for uplink. | | |
+
+| Range bound | Explanation |
+|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| nbr-SeparateTrafficDirections | Number of Traffic Directions being signalled separately.
Set to 2 if RAB Asymmetry Indicator is asymmetric bidirectional.
Set to 1 in all other cases. |
+
+### 9.2.1.46 Global CN-ID
+
+Global CN-ID is used to globally identify a CN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
- or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| CN-ID | M | | INTEGER (0..4095) | |
+
+### 9.2.1.46a Vertical Accuracy Code
+
+This element includes information about the requested vertical accuracy.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------|
+| Vertical Accuracy Code | M | | INTEGER (0..127) | The requested accuracy "v" is derived from the "accuracy code" k by $v = 45 \times (1.025^k - 1)$ . |
+
+### 9.2.1.46b Response Time
+
+This element includes information about the requested response time.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|---------------------------------------------|-------------------------------------|
+| Response Time | M | | ENUMERATED (Low Delay, Delay Tolerant, ...) | The value refers to TS 22.071 [30]. |
+
+### 9.2.1.46c Positioning Priority
+
+This element includes information about the requested positioning priority.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|-----------------------------------------------------------|-------------------------------------|
+| Positioning Priority | M | | ENUMERATED(
High Priority,
Normal Priority,
...) | The value refers to TS 22.071 [30]. |
+
+### 9.2.1.46d Client Type
+
+This element includes information about the client type.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|
+| Client Type | M | | ENUMERATED(
Emergency Services, Value Added Services, PLMN Operator Services, Lawful Intercept Services, PLMN Operator - broadcast services, PLMN Operator - O&M, PLMN Operator - anonymous statistics, PLMN Operator - Target MS service support, ...) | Identifies the type of client. |
+
+### 9.2.1.47 New BSS to Old BSS Information
+
+The coding of this element is described in TS 48.008 [11].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|-----------------------|-------------------------------------|
+| New BSS To Old BSS Information | M | | OCTET STRING | Contents defined in TS 48.008 [11]. |
+
+### 9.2.1.48 Inter-System Information Transparent Container
+
+The *Inter-System Information Transparent Container* IE is an information element that is produced by the external relocation target system and is transmitted to a source RNC. This IE is transparent to the CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|--------------------------------|-----------------------|
+| Downlink Cell Load Information | O | | Cell Load Information 9.2.1.49 | For the Downlink. |
+| Uplink Cell Load Information | O | | Cell Load Information 9.2.1.49 | For the Uplink. |
+
+### 9.2.1.49 Cell Load Information
+
+The *Cell Load Information* IE contains the load information of a specific (serving or target) cell for either the Downlink or the Uplink. If the RNC supports cell load-based inter-system handover, this information shall be understood, when available, as the current traffic load in the target cell if included in a RELOCATION PREPARATION FAILURE message, or the traffic load in the target cell assuming a successful completion of the handover in progress if included in a RELOCATION COMMAND message.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|-----------------------|
+| Cell Capacity Class Value | M | | 9.2.1.50 | |
+| Load Value | M | | 9.2.1.51 | |
+| RT Load Value | O | | 9.2.1.52 | |
+| NRT Load Information Value | O | | 9.2.1.53 | |
+
+### 9.2.1.50 Cell Capacity Class Value
+
+The *Cell Capacity Class Value* IE is the value that classifies the cell capacity with regards to the other cells. The *Cell Capacity Class Value* IE only indicates resources that are configured for traffic purposes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Cell Capacity Class Value | M | | INTEGER (1..100,...) | Value 1 shall indicate the minimum cell capacity, and 100 shall indicate the maximum cell capacity. There should be linear relation between cell capacity and Cell Capacity Class Value. |
+
+### 9.2.1.51 Load Value
+
+The *Load Value* IE contains the total cell load relative to the maximum planned load. It is defined as the load percentage of the Cell Capacity Class.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Load Value | M | | INTEGER (0..100) | Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. Load Value should be measured on a linear scale. |
+
+### 9.2.1.52 RT Load Value
+
+The *RT Load Value* IE indicates in percents the ratio of the load generated by Real Time traffic relative to the measured Load Value. Real Time traffic corresponds to the Conversational and Streaming traffic classes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RT Load Value | M | | INTEGER (0..100) | |
+
+### 9.2.1.53 NRT Load Information Value
+
+The *NRT Load Information Value* IE indicates the load situation on the cell for the Non Real-Time traffic. Non Real Time traffic corresponds to the Interactive and Background traffic classes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NRT Load Information Value | M | | INTEGER (0..3) | Mapping of the status:
0: low: The NRT load is low.
1: medium: The NRT load is medium.
2: high: NRT load is high.
Probability to admit a new user is low.
3: overloaded: NRT overload.
The probability to admit a new user is low, packets are discarded and the source is recommended to reduce the data flow. |
+
+#### 9.2.1.54 Source RNC PDCP context info
+
+The purpose of the *Source RNC PDCP context info* IE is to transfer RNC PDCP context information from a source RNC to a target RNC during an SRNS relocation.
+
+This IE is transparent to CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RRC Container | M | | OCTET STRING | |
+
+#### 9.2.1.55 Information Transfer ID
+
+Indicates the identity of an information transfer.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|---------------------------------|-----------------------|
+| Information Transfer ID | M | | INTEGER (0..2 20 -1) | |
+
+#### 9.2.1.56 Provided Data
+
+Provides the data that is transferred in an information transfer.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Provided Data | | | | |
+| > SNA | | | | |
+| >>Shared Network Information | M | | 9.2.3.23 | |
+
+#### 9.2.1.57 GERAN Classmark
+
+The purpose of the *GERAN Classmark* IE is to transfer GERAN-specific information to the CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------|-------------------------------------|
+| GERAN Classmark | M | | OCTET STRING | Contents defined in TS 48.008 [11]. |
+
+#### 9.2.1.58 GERAN BSC Container
+
+The purpose of the *GERAN BSC Container* IE is to transfer GERAN-specific information from the CN to the GERAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-----------------------|-------------------------------------|
+| GERAN BSC Container | M | | OCTET STRING | Contents defined in TS 48.008 [11]. |
+
+### 9.2.1.59 UESBI-Iu
+
+The purpose of the *UESBI-Iu* IE is to either transfer the UE Specific Behaviour Information as defined in TR 25.994 [31] and TR 25.995 [32] or IMEISV from the CN to the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UESBI-IuA | O | | BIT STRING (1..128) | The UESBI-IuA provides either compliance status information about the UE with regards to specific behaviours described in TR 25.994 [31] or a bit string length 64 containing IMEISV. Length 64 is reserved for IMEISV other bit string lengths may be used for UESBI.
TR 25.994 [31] defines the mapping between the descriptions in TR 25.994 [31] and the UESBI-IuA.
Each bit on a certain position is associated with a certain behaviour described in TR 25.994 [31].
|
+| UESBI-IuB | O | | BIT STRING (1..128) | The UESBI-IuB provides compliance status information about the UE with regards to specific behaviours described in TR 25.995 [32].
TR 25.995 [32] defines the mapping between the descriptions in TR 25.995 [32] and the UESBI-IuB.
Each bit on a certain position is associated with a certain behaviour described in TR 25.995 [32].
|
+
+### 9.2.1.60 Cell Load Information Group
+
+The *Cell Load Information Group* IE is an information element that is produced by source system BSC and is transmitted to target system RNC via transparent containers. This IE contains the load information of the source cell for either the Downlink or the Uplink or both as well as the source cell identifier the included cell load information corresponds to. If the RNC supports cell load-based inter-system handover, this information shall be understood, when available, as the current traffic load in the indicated source cell prior to the relocation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|--------------------------------|-----------------------------------------------------------------------------------------|
+| Source Cell Identifier | M | | 9.2.1.61 | The source cell identifier the downlink and uplink cell load information correspond to. |
+| Downlink Cell Load Information | O | | Cell Load Information 9.2.1.49 | For the Downlink. |
+| Uplink Cell Load Information | O | | Cell Load Information 9.2.1.49 | For the Uplink. |
+
+### 9.2.1.61 Source Cell Identifier
+
+The *Source Cell Identifier* IE identifies the involved cell of the source system for the relocation of SRNS. The *Source Cell Identifier* IE may be e.g. source GERAN Source Cell ID (in case of GSM to UMTS relocation) or the UTRAN Source Cell ID (in case of UMTS to GSM relocation).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Choice Source Cell Identifier | | | | |
+| >UTRAN | | | | |
+| >>UTRAN Source Cell ID | M | | | |
+| >>>PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1- bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| >>>Source Cell ID | M | | INTEGER (0..268435455) | This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3]. |
+| >GERAN | | | | |
+| >>GERAN Source Cell ID | M | | | |
+| >>>PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| >>>LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. |
+| >>>CI | M | | OCTET STRING (2) | |
+
+### 9.2.1.62 Inter-system Information Transfer Type
+
+Indicates the type of information that the RNC requests to transfer.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Inter-system Information Transfer Type | | | | |
+| > RIM | | | | |
+| >> RIM Transfer | M | | 9.2.3.30 | |
+
+### 9.2.1.63 Information Transfer Type
+
+Indicates the type of information that the RNC requests to transfer.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Information Transfer Type | | | | |
+| > RNC Trace | | | | |
+| >> RNC Trace Session Information | M | | 9.2.1.64 | |
+
+### 9.2.1.64 RNC Trace Session Information
+
+Indicates the information on a Trace Session activated by Management in the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|---------------|-------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Trace Reference | M | | 9.2.1.8 | | - | - |
+| Trace Activation Indicator | M | | ENUMERATED (Activated, Deactivated) | | - | - |
+| Equipments To Be Traced | C-IfActivated | | 9.2.1.65 | | - | - |
+| Trace Recording Session Reference | O | | 9.2.1.67 | | YES | ignore |
+| IMSI | O | | OCTET STRING (SIZE (3..8)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit,
- two digits per octet,
- - bit 4 to 1 of octet n encoding digit 2n-1
- - bit 8 to 5 of octet n encoding digit 2n
-Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.
| YES | ignore |
+| Trace Collection Entity IP Address | O | | Transport Layer Address 9.2.2.1 | | YES | ignore |
+| Serving Cell Identifier | O | | UTRAN Cell Identifier 9.2.1.122 | Immediate MDT only. | YES | ignore |
+
+| Condition | Explanation |
+|-------------|---------------------------------------------------------------------------------------------|
+| ifActivated | This IE shall be present if the Trace Activation Indicator IE is set to "Activated". |
+
+### 9.2.1.65 Equipments To Be Traced
+
+Indicates the UEs that the RNC has to trace using a list of Equipment Identities or a mask on an Equipment Identity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------|----------|-------------------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Choice Equipments To Be Traced | | | | |
+| >IMEI List | | | | |
+| >>IMEI List | | 1 to | | |
+| >>>IMEI | M | | OCTET STRING (SIZE (8)) | - - hexadecimal digits 0 to F, two hexadecimal digits per octet,
- - each hexadecimal digit encoded 0000 to 1111,
- - 1111 used as filler for bits 8 to 5 of last octet
- - bit 4 to 1 of octet n encoding digit 2n-1
- - bit 8 to 5 of octet n encoding digit 2n
Number of hexadecimal digits shall be 15.
|
+| >IMEISV List | | | | |
+| >>IMEISV List | | 1 to | | |
+| >>>IMEISV | M | | OCTET STRING (SIZE (8)) | - - hexadecimal digits 0 to F, two hexadecimal digits per octet,
- - each hexadecimal digit encoded 0000 to 1111,
- - bit 4 to 1 of octet n encoding digit 2n-1
- - bit 8 to 5 of octet n encoding digit 2n
Number of hexadecimal digits shall be 16.
|
+| >IMEI Group | | | | |
+| >>IMEI | M | | OCTET STRING (SIZE (8)) | - - hexadecimal digits 0 to F, two hexadecimal digits per octet,
- - each hexadecimal digit encoded 0000 to 1111,
- - 1111 used as filler for bits 8 to 5 of last octet
- - bit 4 to 1 of octet n encoding digit 2n-1
- - bit 8 to 5 of octet n encoding digit 2n
Number of hexadecimal digits shall be 15.
|
+| >>IMEI Mask | M | | BIT STRING (SIZE (7)) | |
+| >IMEISV Group | | | | |
+| >>IMEISV | M | | OCTET STRING (SIZE (8)) | - - hexadecimal digits 0 to F, two hexadecimal digits per octet,
- - each hexadecimal digit encoded 0000 to 1111,
- - bit 4 to 1 of octet n encoding digit 2n-1
- - bit 8 to 5 of octet n encoding digit 2n
Number of hexadecimal digits shall be 16.
|
+
+| | | | | |
+|---------------|--|--|--------------------------|--|
+| >>IMEISV Mask | | | BIT STRING
(SIZE (8)) | |
+|---------------|--|--|--------------------------|--|
+
+| Range Bound | Explanation |
+|------------------|--------------------------------------------------------------------------------|
+| MaxUEsToBeTraced | Maximum number of UEs To Be Traced by the RNC in a Trace Session. Value is 64. |
+
+The IMEI Group is identified by all the IMEI values whose digits 1 to 8 are equal to the corresponding digits of the *IMEI* IE and whose digits n+9 are equal to the corresponding digits of the *IMEI* IE if the bit bn of the *IMEI Mask* IE is equal to 1.
+
+The IMEISV Group is identified by all the IMEISV values whose digits 1 to 8 are equal to the corresponding digits of the *IMEISV* IE and whose digits n+9 are equal to the corresponding digits of the *IMEI* IE if the bit bn of the *IMEISV Mask* IE is equal to 1.
+
+### 9.2.1.66 Trace Recording Session Information
+
+Provides the information on a Trace Record being generated in the Source RNC at the time of.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------|-----------------------|-----------------------|
+| Trace Reference | M | | 9.2.1.8 | |
+| Trace Recording Session Reference | M | | 9.2.1.67 | |
+
+### 9.2.1.67 Trace Recording Session Reference
+
+Identifier of a Trace Record.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------|-----------------------|-----------------------|
+| Trace Recording Session Reference | M | | INTEGER
(0..65535) | |
+
+### 9.2.1.68 Trace Propagation Parameters
+
+Indicates the trace parameters to activate a trace session by a trace parameter propagation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------|-----------------------|-----------------------|
+| Trace Recording Session Reference | M | | 9.2.1.67 | |
+| Trace Depth | M | | 9.2.1.69 | |
+| List Of Interfaces To Trace | O | | 9.2.1.70 | |
+
+### 9.2.1.69 Trace Depth
+
+Indicates how detailed information should be recorded for this trace session in the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|---------------------------------------------------------|-----------------------|
+| Trace Depth | M | | ENUMERATED(
Minimum,
Medium,
Maximum, ...
) | See TS 32.422 [38]. |
+
+### 9.2.1.70 List Of Interfaces To Trace
+
+Indicates the interface(s) to be traced by RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------------------------|---------------------------------------------------------|-----------------------|
+| List Of Interfaces To Trace | | | | |
+| >Interfaces To Trace | | 1 to
| | |
+| >>Interface | M | | ENUMERATED(lu-CS,
lu-PS,
Iur,
Iub,
Uu, ...) | |
+
+| Range bound | Explanation |
+|---------------|----------------------------------------------------------------------------------------|
+| maxInterfaces | Maximum no. of different UTRAN interfaces to trace. The value for maxInterfaces is 16. |
+
+### 9.2.1.71 Information Exchange ID
+
+Indicates the identity of an information exchange.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|------------------------|-----------------------|
+| Information Exchange ID | M | | INTEGER
(0..2^20-1) | |
+
+### 9.2.1.72 Information Exchange Type
+
+Indicates the nature of the information exchange i.e. transfer or request of specific information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|---------------------------------------|-----------------------|
+| Information Exchange Type | M | | ENUMERATED(transfer,
request, ...) | |
+
+### 9.2.1.73 Information Request Type
+
+Indicates the type of information requested by the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Information Request Type | | | | |
+| >MBMS IP MC Address and APN Request | | | | |
+| >>MBMS IP Multicast Address and APN Request | M | | 9.2.1.78 | |
+| >Permanent NAS UE ID | | | | |
+| >>Permanent NAS UE Identity | M | | 9.2.3.1 | |
+
+### 9.2.1.74 Information Requested
+
+Provides the RNC with the requested information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Information Requested | | | | |
+| >Requested MBMS IP MC Address and APN | | | | |
+| >>Requested MBMS IP Multicast Address and APN | M | | 9.2.3.46 | |
+| >Requested MC Service List | | | | |
+| >>Requested Multicast Service List | M | | 9.2.3.47 | |
+
+### 9.2.1.75 PTP RAB ID
+
+This element uniquely identifies a MBMS PTP radio bearer for a particular UE.
+
+The value is used in the RNC to relate MBMS PTP Radio Bearers to a MBMS RAB. The content of this information element is transferred unchanged from the SGSN via the RNC to the UE by RANAP messages and RRC messages. For RRC messages refer to TS 25.331 [10].
+
+The element contains binary representation of the Network Service Access Point Identifier (NSAPI). This identifier is coded in the PTP RAB ID element in accordance with the coding of the *NSAPI* IE in TS 24.008 [8].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| PTP RAB ID | M | | BIT STRING (8) | |
+
+### 9.2.1.76 Frequency Layer Convergence Flag
+
+Indicates to the RNC the requirement to not apply Frequency Layer Convergence for a given MBMS Bearer Service.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|-------|-------------------------------|-----------------------|
+| Frequency Layer Convergence Flag | M | | ENUMERATED (no-FLC-flag, ...) | |
+
+### 9.2.1.77 Session Update ID
+
+Indicates the identity of a Session Update procedure.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------|----------|-------|---------------------------------|-----------------------|
+| Session Update ID | M | | INTEGER (0..2 20 -1) | |
+
+### 9.2.1.78 MBMS IP Multicast Address and APN Request
+
+Indicates the list of MBMS Bearer Services identified by their respective TMGIs, for which the IP Multicast Address and APN are requested by the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|---------------------------------------|-----------------------|-----------------------|
+| MBMS IP Multicast Address and APN Request | | | | |
+| >TMGI | M | 1 to | 9.2.3.37 | |
+
+| Range bound | Explanation |
+|--------------------------------|----------------------------------------------------------------------------------|
+| maxnoofMulticastServicesPerRNC | Maximum no. of Multicast Services that a RNC can have context for. Value is 512. |
+
+### 9.2.1.79 Source BSS to Target BSS Transparent Container
+
+The coding of this element is described in TS 48.018 [36].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------|
+| Source BSS to Target BSS Transparent Container | M | | OCTET STRING | Coded as the value (V) part of the Source BSS to Target BSS Transparent Container IE defined in TS 48.018 [36]. |
+
+### 9.2.1.80 Target BSS to Source BSS Transparent Container
+
+This IE contains information provided by the external inter-system handover target.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------|
+| Target BSS to Source BSS Transparent Container | M | | OCTET STRING | Coded as the value (V) part of the Target BSS to Source BSS Transparent Container IE defined in TS 48.018 [36]. |
+
+### 9.2.1.81 Include Velocity
+
+This element indicates that the Location Report may include the UE's velocity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|-----------------------|-----------------------|
+| Include Velocity | M | | ENUMERATED(requested) | |
+
+### 9.2.1.82 Periodic Location Info
+
+The *Periodic Location Info* IE contains the periodic reporting interval and reporting amount for periodic location.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------|----------|-------|------------------------|------------------------------------------------------|
+| Reporting Amount | M | | INTEGER(1..863999,...) | This IE indicates the amount of periodic reports. |
+| Reporting Interval | M | | INTEGER(1..863999,...) | This IE indicates the reporting interval in seconds. |
+
+### 9.2.1.83 Last Visited UTRAN Cell Information
+
+The Last Visited UTRAN Cell Information contains information about a cell that is to be used for RRM purposes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| UTRAN Cell ID | | 1 | | | - | |
+| >PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1- bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
| - | |
+| >Cell ID | M | | INTEGER (0..268435455) | This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3]. | - | |
+| Cell Type | M | | ENUMERATED(macro, micro, pico, femto, ...) | Defined in TS 25.104 [50]. | - | |
+| Time UE Stayed In Cell | M | | INTEGER (0..4095) | The duration of the time the UE stayed in the cell in seconds. If the UE stays in a cell more than 4095s, this IE is set to 4095. | - | |
+| Time UE stayed in Cell Enhanced Granularity | O | | INTEGER (0..40950) | The duration of the time the UE stayed in the cell in 1/10 seconds. If the UE stays in a cell more than 4095s, this IE is set to 40950. | YES | ignore |
+| HO Cause Value | O | | Cause 9.2.1.4 | The cause for the outgoing relocation. | YES | ignore |
+
+### 9.2.1.84 MBMS HC Indicator
+
+This element indicates whether the payload of user data packets of the MBMS RAB are provided with compressed IP header. Respective information within SYNC-protocol data frames are defined in TS 25.446 [51].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------|----------|-------|----------------------------------------------------------|-----------------------|
+| MBMS HC Indicator | M | | ENUMERATED (uncompressed header, compressed header, ...) | |
+
+### 9.2.1.85 CSG Id
+
+This information element indicates the identifier of the Closed Subscriber Group, as defined in TS 23.003 [19].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------|-----------------------|
+| CSG Id | M | | BIT STRING (SIZE (27)) | |
+
+### 9.2.1.86 Subscriber Profile ID for RAT/Frequency priority
+
+The *Subscriber Profile ID* IE for RAT/Frequency Selection Priority is used to define camp priorities in Idle mode and to control inter-RAT/inter-frequency handover in Active mode TS 23.401 [48].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Subscriber Profile ID for RAT/Frequency Priority | M | | INTEGER (1..256) | |
+
+### 9.2.1.87 SRVCC operation possible
+
+This information element is set by the CN to provide an indication that both UE and CN are SRVCC-capable.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|---------------------------------|-----------------------|
+| SRVCC operation possible | M | | ENUMERATED (SRVCC possible,...) | |
+
+### 9.2.1.88 SRVCC HO Indication
+
+This information element is set by the source RNC to provide an indication that RAB bearers may be subjected to handover via SRVCC means.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-------------------------------------|-----------------------|
+| SRVCC HO Indication | M | | ENUMERATED (PS and CS, CS only,...) | |
+
+### 9.2.1.89 SRVCC Information
+
+This IE contains information for SRVCC operation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|-------------------------------------------------------|
+| SRVCC Information | | | | |
+| >NONCE | M | | BIT STRING (128) | The usage of NONCE IE is described in TS 33.102 [60]. |
+
+### 9.2.1.90 E-UTRAN Service Handover
+
+This IE tells if intersystem mobility to E-UTRAN, e.g., handover or redirection, shall not be performed for a given RAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|--------------------------------------------------------------|-----------------------|
+| E-UTRAN Service Handover | M | | ENUMERATED (Handover to E-UTRAN shall not be performed, ...) | |
+
+### 9.2.1.91 UE Aggregate Maximum Bit Rate
+
+The *UE Aggregate Maximum Bitrate* IE is applicable for all non-GBR bearers per UE which is defined for the Downlink and the Uplink direction and provided by the CN to the RNC. At least one of the *UE Aggregate Maximum*
+
+*Bit Rate Downlink* IE and *UE Aggregate Maximum Bit Rate Uplink* IE shall be included in the *UE Aggregate Maximum Bit Rate* IE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UE Aggregate Maximum Bit Rate | | | | Desc:
Applicable for non-GBR bearers |
+| >UE Aggregate Maximum Bit Rate Downlink | O | | INTEGER
(1..1,000,000 ,000) | Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in DL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present. |
+| >UE Aggregate Maximum Bit Rate Uplink | O | | INTEGER
(1..1,000,000 ,000) | Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in UL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present. |
+
+### 9.2.1.92 CSG Membership Status
+
+This element indicates the Membership status of the UE to a particular CSG.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|----------------------------------------|-----------------------|
+| CSG Membership Status | M | | ENUMERATED
(member, non-member,...) | |
+
+### 9.2.1.93 Cell Access Mode
+
+This information element indicates that the cell operates in Hybrid Access mode as defined in TS 22.220 [56].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|----------------------------|-----------------------|
+| Cell Access Mode | M | | ENUMERATED
(hybrid,...) | |
+
+### 9.2.1.94 Offload RAB Parameters
+
+The purpose of the *Offload RAB parameters* IE is to provide information related to the handling of the SIPTO at Iu-PS function, as specified in TS 23.060 [21].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------|
+| Access Point Name | M | | OCTET STRING (1..255) | This IE indicates the Access Point Name of the RAB to be offloaded. Defined in TS 23.003 [19]. |
+| Charging Characteristics | M | | OCTET STRING (2) | This IE indicates the charging characteristics of the RAB to be offloaded. Defined in TS 29.060 [57]. |
+
+### 9.2.1.95 MSISDN
+
+The purpose of the *MSISDN* IE (TS 29.060 [57]) is to indicate the primary MSISDN of the subscriber for the handling of the SIPTO at Iu-PS function, as specified in TS 23.060 [21].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------|--------------------------------------------------------------|
+| MSISDN | M | | OCTET STRING (SIZE (1..9)) | Coded as the MSISDN IE, as defined in TS 29.002 [24]. |
+
+### 9.2.1.96 IRAT Measurement Configuration
+
+The *IRAT Measurement Configuration* IE contains information for instructing the incoming UE to continue measuring the cells of the source RAT after a successful inter-system handover. It is used by the source RAT to specify the minimum radio quality and the period of time measurements should last for triggering a HO report for unnecessary HO to another RAT. A subset of source RAT frequencies to measure may be specified. The measurement bandwidth of a carrier frequency may also be specified in order to improve the measurement accuracy and reduce measurement time. The *IRAT Measurement Configuration* IE shall contain at least one of the RSRP or RSRQ thresholds. If only one of the thresholds is present, the target RAT will use the present threshold to compare against the measurement results received from the UE. HO Report should be sent if there is either a single source RAT cell whose measurement results exceed the threshold for the whole measurement duration, or a group of source RAT cells together provide such coverage. The cells that exceed the threshold in the first UE measurement report are included in the HO Report. If both thresholds are present, the received radio measurements must exceed both the RSRP and the RSRQ thresholds in order to satisfy the indicated radio conditions.
+
+When the HO Report is sent from RNC at the end of the configured measurement duration, it shall set the *HO Report Type* IE to "Unnecessary HO to another RAT". If the measurement period expires due to an inter-RAT handover towards LTE executed within the configured measurement duration, the RNC shall set the *HO Report Type* IE in the HO Report to "Early IRAT Handover".
+
+No HO Report shall be sent in case no E-UTRAN cell could be included, or if the indicated period of time is interrupted by an inter-RAT handover to a RAT different than LTE or by an intra-UMTS handover with SRNC relocation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|---------------------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RSRP | O | | INTEGER (0..97) | Threshold of RSRP. | - | - |
+| RSRQ | O | | INTEGER (0..34) | Threshold of RSRQ. | - | - |
+| IRAT Measurement Parameters | M | | | | - | - |
+| >Measurement Duration | M | | INTEGER (1..100) | The period of time following the successful IRAT handover, during which the target RAT instructs the UE to measure cells of the source RAT. Unit: [second]. | - | - |
+| >E-UTRA frequencies | | 0 to | | If present, designates the specific E-UTRAN frequencies which the target RAT may instruct the UE to measure. | - | - |
+| >>E-ARFCN | M | | INTEGER (0..65535) | EARFCN of the downlink carrier frequency TS 36.101 [58]. | - | - |
+| >>Measurement Bandwidth | O | | ENUMERATED(6,15,25,50,75,100) | Measurement bandwidth of the carrier frequency as defined in TS 25.331 [10]. | - | - |
+| >>E-ARFCN-Extended | O | | INTEGER (65536..262143, ...) | EARFCN of the downlink carrier frequency TS 36.101 [58]. If this IE is present, the value signalled in the IE "E-ARFCN" is ignored. | YES | reject |
+
+| Range bound | Explanation |
+|-------------------|---------------------------------------------------|
+| maxnoofEUTRAFreqs | Maximum no of EUTRA centre frequencies to measure |
+
+### 9.2.1.97 MDT Configuration
+
+The purpose of the *MDT Configuration* IE is to provide configuration information for the MDT function.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| MDT Activation | M | | ENUMERATED(Immediate MDT only, Logged MDT only, Immediate MDT and Trace, ...) | | - | - |
+| CHOICE MDT Area Scope | M | | | | - | - |
+| >Cell Based | | | | | - | - |
+| >>Cell ID List | | 1 to | | | - | - |
+| >>>Cell-ID | M | INTEGER (0..268435455) | | This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3]. The Cell is derived using the current serving PLMN. | - | - |
+| >LA Based | | | | | - | - |
+| >>LAI List | | 1 to | | | - | - |
+| >>>LAI | M | | 9.2.3.6 | | - | - |
+| >RA Based | | | | | - | - |
+| >>RAI List | | 1 to | | | - | - |
+| >>>RAI | | | | This element identifies an area in which the MDT Configuration applies. | - | - |
+| >>>>LAI | M | | 9.2.3.6 | | - | - |
+| >>>>RAC | M | | 9.2.3.7 | | - | - |
+| >PLMN Area Based | | | NULL | | - | - |
+| CHOICE MDT mode | | | | | - | - |
+| >immediate MDT | | | | | - | - |
+| >>Measurements to Activate | M | | BITSTRING (SIZE(8)) | Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [64].
First Bit = M1,
Second Bit = M2,
Third Bit = M3,
Fourth Bit = M4,
Fifth Bit = M5,
Sixth Bit = M6
Seventh Bit = M7.
Eighth bit = logging of M1 or M2 from event triggered measurement reports according to existing RRM configuration [31]. Value '1' indicates | - | - |
+
+| | | | | | | |
+|--------------------------------|--------|--|--------------------------------------------------------------------------|---------------------------------------------------------------------|-----|--------|
+| | | | | “activate” and value ‘0’ indicates “do not activate”. | | |
+| >>M1 Report | C-ifM1 | | 9.2.1.98 | M1: FDD only: CPICH RSCP and CPICH Ec/No measurement by UE. | - | - |
+| >>M2 Report | C-ifM2 | | 9.2.1.99 | M2: TDD only: P-CCPCH RSCP and Timeslot ISCP for UTRA 1.28 TDD. | - | - |
+| >>M4 Report | C-ifM4 | | 9.2.1.117 | M4: UPH measurement by UE. | YES | ignore |
+| >>M5 Report | C-ifM5 | | 9.2.1.118 | M5: RTWP measurement by NodeB. | YES | ignore |
+| >>M6 Report | C-ifM6 | | 9.2.1.119 | M6: Data volume measurement by RNC. | YES | ignore |
+| >>M7 Report | C-ifM7 | | 9.2.1.120 | M7: Throughput measurement by RNC. | YES | ignore |
+| >logged MDT | | | | | - | - |
+| >>logging interval | M | | ENUMERATED (1.28, 2.56, 5.12, 10.24, 20.48, 30.72, 40.96 and 61.44, ...) | The unit of this IE is second. This IE is defined in TS 25.331[10]. | - | - |
+| >>logging duration | M | | ENUMERATED (10, 20, 40, 60, 90 and 120, ...) | The unit of this IE is minute. This IE is defined in TS 25.331[10]. | - | - |
+| Signalling based MDT PLMN List | | | MDT PLMN List 9.2.1.116 | | YES | ignore |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------------------|
+| maxnoofCellID | Maximum no. of Cell ID subject for MDT scope. Value is 32. |
+| maxnoofLAIs | Maximum no. of LAI subject for MDT scope. Value is 8. |
+| maxnoofRAIs | Maximum no of RAI subject for MDT scope. Value is 8. |
+
+| Condition | Explanation |
+|-----------|----------------------------------------------------------------------------------------------------|
+| ifM1 | This IE shall be present if the Measurements to Activate IE has the first bit set to “1”. |
+| ifM2 | This IE shall be present if the Measurements to Activate IE has the second bit set to “1”. |
+| ifM4 | This IE shall be present if the Measurements to Activate IE has the fourth bit set to “1”. |
+| ifM5 | This IE shall be present if the Measurements to Activate IE has the fifth bit set to “1”. |
+| ifM6 | This IE shall be present if the Measurements to Activate IE has the sixth bit set to “1”. |
+| ifM7 | This IE shall be present if the Measurements to Activate IE has the seventh bit set to “1”. |
+
+#### 9.2.1.98 M1 Report
+
+This IE defines the parameters for M1 report, FDD report of UE radio measurements as specified in TS 32.422 [38].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|
+| CHOICE M1 Report trigger | | | | |
+| >Periodic | | | | |
+| >>MDT Report Parameters | M | | 9.2.1.100 | |
+| >event1F | | | | |
+| >>Measurement quantity | M | | ENUMERATED(
CPICH Ec/N0,
CPICH RSCP,
pathloss, ...) | |
+| >>threshold | M | | INTEGER(-120..165) | Range used depends on measurement quantity.
CPICH RSCP -120..-25 dBm
CPICH Ec/No -24..0 dB
Pathloss 30..165dB |
+
+#### 9.2.1.99 M2 Report
+
+This IE defines the parameters for a M2 report, TDD report of UE radio measurements as specified in TS 32.422 [38].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE M2 Report trigger | | | | |
+| >Periodic | | | | |
+| >>MDT Report Parameters | M | | 9.2.1.100 | |
+| >Event1I | | | | |
+| >>threshold | M | | INTEGER(-120..-25) | |
+
+#### 9.2.1.100 MDT Report parameters
+
+This IE defines the report parameters for MDT periodic reports of measurements M1 and M2 as specified in TS 32.422 [38].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| Report interval | M | | ENUMERATED (
ms250, ms500,
ms1000, ms2000,
ms3000, ms4000,
ms6000, ms12000,
ms16000, ms20000,
ms24000, ms32000,
ms64000, ...,
ms8000, ms28000) | This IE is defined in TS 25.331[10]. |
+| Report amount | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, ...) | |
+
+#### 9.2.1.101 RNSAP Relocation Parameters
+
+This IE provides additional information for RNSAP Relocation.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------------------|----------|-------|-----------------------|-----------------------|
+| RAB Parameters List | O | | 9.2.1.102 | |
+| Location Reporting Transfer Information | O | | 9.2.1.105 | |
+| Trace Information | O | | 9.2.1.106 | |
+| Source SAI | O | | SAI
9.2.3.9 | |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------------------|
+| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. |
+
+#### 9.2.1.102 RAB Parameters List
+
+This IE provides RAB specific information for RNSAP Relocation.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------------|----------|---------------------------|-----------------------|-----------------------|
+| Relocation Parameters List | | 1 to
RABs> | | |
+| >RAB ID | M | | 9.2.1.2 | |
+| >CN Domain Indicator | M | | 9.2.1.5 | |
+| >RAB Data Volume Report | O | | 9.2.1.103 | |
+| >UP Information | O | | 9.2.1.104 | |
+
+#### 9.2.1.103 RAB Data Volume Report
+
+This information element indicates the data volume (octets) and the time when it was counted that was unsuccessfully transmitted over the radio interface in the DL direction for a RAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------|----------|-------------------------|----------------------------------------------------|-----------------------|
+| RAB Data Volume Report | | | | |
+| >RAB Data Volume Report Item IEs | | 1 to
ol> | | |
+| >>Unsuccessfully Transmitted DL Data Volume | M | | Unsuccessfully transmitted data volume
9.2.3.12 | |
+| >>Data Volume Reference | O | | 9.2.3.13 | |
+
+| Range bound | Explanation |
+|-------------|--------------------------------------------------------------|
+| maxnoofVol | Maximum no. of reported data volume for one RAB. Value is 2. |
+
+#### 9.2.1.104 UP Information
+
+| Information Element/Group name | Presence | Range | Type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Frame Sequence Number UL | M | | Frame Sequence Number 9.2.1.107 | | - | - |
+| Frame Sequence Number DL | M | | Frame Sequence Number 9.2.1.107 | | - | - |
+| PDU Type 14 Frame Sequence Number UL | M | | PDU Type 14 Frame Sequence Number 9.2.1.108 | | - | - |
+| PDU Type 14 Frame Sequence Number DL | M | | PDU Type 14 Frame Sequence Number 9.2.1.108 | | - | - |
+| Data PDU Type | M | | ENUMERATED (PDU type 0, PDU type 1,...) | | - | - |
+| UP Initialisation Frame | M | | OCTET STRING | Coded as in TS 25.415 [6] subclause 6.6.23.4.1, Frame Payload Part only. | - | - |
+| Timing Difference UL-DL | O | | OCTET STRING (SIZE(1)) | Coded as the Time Alignment IE in TS 25.415 [6]. Specifies the difference in time at the Source RNC between reception of the DL user data frame with the frame number indicated in the Frame Sequence Number DL IE and the transmission of the UL user data frame with the frame number indicated in the Frame Sequence Number UL IE. | YES | ignore |
+
+| Range bound | Explanation |
+|-----------------|-------------------------------------------------|
+| maxnoofRFCIs | Maximum no. of RFCIs for one RAB. Value is 63. |
+| maxnoofSubFlows | Maximum no of Subflows for one RFCI. Value is 7 |
+
+#### 9.2.1.105 Location Reporting Transfer Information
+
+The *Location Reporting Transfer Information* IE contains information about location reporting function requested and started in the Source RNC. Only Request Types for periodic reporting and reporting upon change of Service Area are contained.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|------------------|-------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
+| Report Change of Service Area Indicator | O | | ENUMERATED (requested, ...) | |
+| Periodic Reporting Indicator | O | | ENUMERATED (periodic SAI, periodic Geo, ...) | |
+| Direct Reporting Indicator | O | | ENUMERATED (direct SAI, direct Geo, ...) | |
+| Vertical Accuracy Code | C-ifGeoRequested | | 9.2.1.46a | |
+| Positioning Priority Change SAI | C-ifChangeSAI | | Positioning Priority 9.2.1.46c | |
+| Positioning Priority Direct | O | | Positioning Priority 9.2.1.46c | May be included if direct reporting or reporting upon change of Service Area is requested. |
+| Client Type Periodic | O | | Client Type 9.2.1.46d | May be included if periodic reporting is requested. |
+| Client Type Direct | O | | Client Type 9.2.1.46d | Included if direct reporting of Geographical Area is requested. Maybe included if direct reporting of SAI is requested. |
+| Response Time | C-ifDirectGeo | | 9.2.1.46b | |
+| Include Velocity | O | | 9.2.1.81 | May be included if the Periodic Reporting Indicator IE is set to "Geo Requested" |
+| Periodic Location Info | C-ifPeriodicGeo | | 9.2.1.82 | |
+
+| Condition | Explanation |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IfGeoRequested | This IE shall be present if the Periodic Reporting Indicator IE is set to "periodic Geo" or if the Direct Reporting Indicator IE is set to "direct Geo". |
+| IfChangeSAI | This IE shall be present if the Periodic Reporting Indicator IE is set to "periodic SAI" or if the Direct Reporting Indicator IE is set to "direct SAI". |
+| IfPeriodicGeo | This IE shall be included if the Periodic Reporting Indicator IE is set to "Geo Requested" |
+| IfDirectGeo | This IE shall be present if the Direct Reporting Indicator IE is set to "direct Geo". |
+
+#### 9.2.1.106 Trace Information
+
+The Trace Information contains information needed by the target RNC to maintain trace continuity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|-----------------------|-----------------------|
+| Trace Reference | M | | 9.2.1.8 | |
+| UE Identity | M | | 9.2.1.9 | |
+| Trace Propagation Parameters | O | | 9.2.1.68 | |
+
+#### 9.2.1.107 Frame Sequence Number
+
+The *Frame Sequence Number* IE is used for RNSAP Relocation and contains information needed by the target RNC to maintain continuity for numbering IuUP user data frames of PDU type 0 and 1 (see TS 25.415 [16]).
+
+| Information Element/Group name | Presence | Range | IE Type and reference | Semantics description |
+|--------------------------------|----------|-------|-----------------------|-----------------------|
+| Frame Sequence Number | | | INTEGER(0..15) | |
+
+#### 9.2.1.108 PDU Type 14 Frame Sequence Number
+
+The *PDU Type 14 Frame Sequence Number* IE is used for RNSAP Relocation and contains information needed by the target RNC to maintain continuity for numbering IuUP user data frames of PDU type 14 (see TS 25.415 [16]).
+
+| Information Element/Group name | Presence | Range | IE Type and reference | Semantics description |
+|-----------------------------------|----------|-------|-----------------------|-----------------------|
+| PDU Type 14 Frame Sequence Number | | | INTEGER(0..3) | |
+
+#### 9.2.1.109 Priority Class Indicator
+
+This information element indicates that overload has occurred and traffic for the indicated priority class should be reduced.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Priority Class Indicator | M | | BIT STRING(SIZE(8)) | Each bit represents a priority class, as specified below. If a bit is set to "1", the signalling traffic of the respective priority class should be reduced.
Bit (0) = Delay Tolerant traffic limited.
Bits (1..7) reserved for future use. |
+
+#### 9.2.1.110 Management Based MDT Allowed
+
+This element indicates that the UE may perform management based MDT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|---------------------------|-----------------------|
+| Management Based MDT Allowed | | | ENUMERATED (Allowed, ...) | |
+
+#### 9.2.1.111 End Of CSFB
+
+This element indicates that the Iu connection being released was established as a result of CS fallback.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------------|-----------------------|
+| End Of CSFB | | | ENUMERATED (end Of CSFB, ...) | |
+
+#### 9.2.1.112 Out Of UTRAN
+
+This element indicates that the UE has already moved from UTRAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------------------------|-----------------------|
+| Out Of UTRAN | | | ENUMERATED (cell reselection to EUTRAN, ...) | |
+
+#### 9.2.1.113 Voice Support Match Indicator
+
+This element indicates if the SRVCC and frequency supported by the UE match those the network relies upon for voice coverage.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|--------------------------------------------|-----------------------|
+| Voice Support Match Indicator | M | | ENUMERATED( Supported, Not Supported, ...) | |
+
+#### 9.2.1.114 rSRVCC HO Indication
+
+This information element is set by the source RNC to provide an indication that RAB bearers may be subjected to handover via rSRVCC means.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|---------------------------|-----------------------|
+| rSRVCC HO Indication | M | | ENUMERATED (PS only, ...) | |
+
+#### 9.2.1.115 rSRVCC Information
+
+This IE contains information for rSRVCC operation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|----------------------------|-----------------------------------------------------------------------------|
+| rSRVCC Information | | | | |
+| >NONCE | M | | BIT STRING (128) | The usage of NONCE IE is described in TS 33.102 [60] and in TS 33.401 [63]. |
+| >IMS information | M | | OCTET STRING (SIZE(1..32)) | The usage of IMS information is described in TS 23.216 [54]. |
+
+#### 9.2.1.116 MDT PLMN List
+
+The purpose of the *MDT PLMN List* IE is to provide the list of PLMN allowed for MDT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|----------------------|---------------------------------|-----------------------|
+| MDT PLMN List | | 1.. | | |
+| >PLMN Identity | M | | Selected PLMN Identity 9.2.3.33 | |
+
+| Range bound | Explanation |
+|-----------------|-------------------------------------------|
+| maxnoofMDTPLMNs | Maximum no. of MDT PLMN Ids. Value is 16. |
+
+#### 9.2.1.117 M4 Report
+
+This IE defines the parameters for UE Power Headroom (M4) measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|-------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE Collection mode | | | | |
+| > All | | | NULL | All available measurements are logged |
+| > Periodic and event triggered periodic | | | | One sample collected per period |
+| >>M4 Collection period | M | | ENUMERATED(ms100, ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ...) | |
+| >>M4 Threshold | O | | INTEGER(0..31) | If included, logging shall be initiated when UPH value falls below the indicated threshold, and then for each period, until UPH value goes above the threshold.
The mapping is defined in TS25.123 (TDD) and TS25.133 (FDD). |
+
+#### 9.2.1.118 M5 Report
+
+This IE defines the parameters for RTWP (M5) measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|------------------------------------------------------------------------------|---------------------------------------|
+| CHOICE Collection mode | | | | |
+| > When available | | | NULL | All available measurements are logged |
+| > Periodic | | | | One sample collected per period |
+| >>M5 Collection period | M | | ENUMERATED(ms100, ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ...) | |
+
+#### 9.2.1.119 M6 Report
+
+This IE defines the parameters for data volume (M6) measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| M6 Collection Period | M | | ENUMERATED (ms1000, ms2000, ms3000, ms4000, ms6000, ms8000, ms12000, ms16000, ms20000, ms24000, ms28000, ms32000, ms64000, ...) | |
+| M6 Links to log | M | | ENUMERATED(uplink, downlink, both-uplink-and-downlink, ...) | |
+
+#### 9.2.1.120 M7 Report
+
+This IE defines the parameters for data volume (M7) measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| M7 Collection Period | M | | ENUMERATED
(ms1000, ms2000,
ms3000, ms4000,
ms6000, ms8000,
ms12000, ms16000,
ms20000, ms24000,
ms28000, ms32000,
ms64000, ...) | |
+| M7 Links to log | M | | ENUMERATED(uplink,
downlink, both-
uplink-and-downlink,
...) | |
+
+#### 9.2.1.121 rSRVCC operation possible
+
+This information element is set by the CN to provide an indication that both UE and CN are rSRVCC-capable.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-------------------------------------|-----------------------|
+| rSRVCC operation possible | M | | ENUMERATED
(rSRVCC possible,...) | |
+
+#### 9.2.1.122 UTRAN Cell Identifier
+
+The *UTRAN Cell Identifier* IE identifies a global UTRAN cell.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING
(SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit - bits 8 to 5 of octet n encoding digit .
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| Cell ID | M | | INTEGER
(0..268435455) | This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3]. |
+
+### 9.2.2 Transport Network Layer Related IEs
+
+#### 9.2.2.1 Transport Layer Address
+
+For the PS domain, or for the CS domain in order to allow transport bearer establishment without ALCAP, this information element is an IP address to be used for the user plane transport. For the CS domain, in case of transport bearer establishment with ALCAP, this address is to be used for Transport Network Control Plane signalling to set up the transport bearer.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Transport Layer Address | M | | BIT STRING (1..160, ...) | The Radio Network Layer is not supposed to interpret the address information. It should pass it to the transport layer for interpretation.
For details on the Transport Layer Address, see TS 25.414 [9]. |
+
+#### 9.2.2.2 Iu Transport Association
+
+This element is used to associate the RAB and the corresponding transport bearer. For the CS domain this information element is either the Binding ID to be used in Transport Network Control Plane signalling during set up of the transport bearer or it contains the UDP port in order to allow transport bearer establishment without ALCAP. In PS domain this information element is the GTP Tunnel Endpoint Identifier.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Choice Iu Transport Association | | | | |
+| >TEID | | | | |
+| >>GTP TEID | M | | OCTET STRING (4) | For details and range, see TS 29.281 [59] |
+| >Binding ID | | | | |
+| >>Binding ID | M | | OCTET STRING (4) | If the Binding ID includes an UDP port, the UDP port is included in octet 1 and 2. The first octet of the UDP port field shall be included in the first octet of the Binding ID. |
+
+#### 9.2.2.3 DL GTP-PDU Sequence Number
+
+This IE indicates the sequence number of the GTP-PDU which is the next to be sent to the UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------|
+| DL GTP-PDU Sequence Number | M | | INTEGER (0 ..65535) | This IE indicates the sequence number of the GTP-PDU which is next to be sent to the UE. |
+
+#### 9.2.2.4 UL GTP-PDU Sequence Number
+
+This IE indicates the sequence number of the GTP-PDU which is the next to be sent to the SGSN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------|
+| UL GTP-PDU Sequence Number | M | | INTEGER (0 ..65535) | This IE indicates the sequence number of the GTP-PDU which is next to be sent to the SGSN. |
+
+#### 9.2.2.5 Correlation ID
+
+This IE contains the GTP Tunnel Endpoint Identifier or GRE key to be used for the user plane transport between RNC and the L-GW as specified in TS 23.401 [48].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|-----------------------|
+| Correlation ID | M | | OCTET STRING (4) | |
+
+#### 9.2.2.6 Tunnel Information
+
+The *Tunnel Information* IE indicates the transport layer address and UDP port number
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|---------------------------------------------------------------------|
+| Transport Layer Address | M | | 9.2.2.1 | HNB's Transport Layer Address. |
+| UDP Port Numbers | O | | OCTET STRING (2) | UDP Port Numbers if NAT/NAPT is deployed in the BBF access network. |
+
+### 9.2.3 NAS Related IEs
+
+#### 9.2.3.1 Permanent NAS UE Identity
+
+This element is used to identify the UE commonly in the UTRAN and in the CN. The RNC uses it to find other existing signalling connections of the same UE (e.g. RRC or Iu signalling connections). It is an IMSI.
+
+NOTE: IMSI is specified in TS 23.003 [19].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Choice Permanent NAS UE Identity | | | | |
+| >IMSI | | | | |
+| >>IMSI | | | OCTET STRING (SIZE (3..8)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bit 4 to 1 of octet n encoding digit 2n-1,
- - bit 8 to 5 of octet n encoding digit 2n.
- Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity.
When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.
|
+
+#### 9.2.3.2 Temporary UE ID
+
+Temporary Mobile Subscriber Identity, used for security reasons to hide the identity of a subscriber.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Temporary UE ID | | | | |
+| > TMSI | | | | |
+| >>TMSI | M | | OCTET
STRING (4) | |
+| > P-TMSI | | | | |
+| >>P-TMSI | M | | OCTET
STRING (4) | |
+
+#### 9.2.3.3 Paging Cause
+
+This element indicates the cause for paging a UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Paging Cause | M | | ENUMERATED(
Terminating
Conversational Call,
Terminating
Streaming
Call,
Terminating
Interactive
Call,
Terminating
Background
Call,
Terminating
Low Priority
Signalling,
...,
Terminating
High Priority
Signalling) | |
+
+#### 9.2.3.4 NAS Broadcast Information
+
+Void
+
+#### 9.2.3.5 NAS PDU
+
+This information element contains a CN – UE or UE – CN message that is transferred without interpretation in the RNC. Typically it contains call control, session management, supplementary services, short message service and mobility management messages.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| NAS PDU | M | | OCTET
STRING | |
+
+#### 9.2.3.6 LAI
+
+This element is used to uniquely identify a Location Area.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
- or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. |
+
+#### 9.2.3.7 RAC
+
+This element is used to identify a Routing Area within a Location Area. It is used for PS services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RAC | M | | OCTET STRING (1) | |
+
+#### 9.2.3.8 SAPI
+
+The *SAPI* IE is used to indicate the specific service to provide for the included NAS message.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------------|-----------------------|
+| SAPI | M | | ENUMERATED (SAPI 0, SAPI 3, ...) | |
+
+#### 9.2.3.9 SAI
+
+The *SAI* IE (Service Area Identifier) (see TS 25.401 [3]) is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN. For this protocol, only a Service Area that is defined to be applicable to both the PS and the CS domains shall be used.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
- or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. |
+| SAC | M | | OCTET STRING (2) | |
+
+#### 9.2.3.10 Area Identity
+
+*This information element is used for indicating the location of a UE and is either a Service Area or a Geographical Area.*
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------|----------|-------|-----------------------|-----------------------|
+| Choice Area Identity | | | | |
+| > SAI | | | | |
+| >>SAI | M | | 9.2.3.9 | |
+| > Geo | | | | |
+| >>Geographical Area | M | | 9.2.3.11 | |
+
+#### 9.2.3.11 Geographical Area
+
+The *Geographical Area* IE is used to identify an area using geographical coordinates. The reference system is the same as the one used in TS 23.032 [20].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------|
+| Choice Geographical Area | | | | |
+| >Point | | | | |
+| >>Point | M | | See below | Ellipsoid point. |
+| >Point With Uncertainty | | | | |
+| >>Point With Uncertainty | M | | See below | Ellipsoid point with uncertainty circle. |
+| >Polygon | | | | |
+| >>Polygon | M | | See below | List of Ellipsoid points. |
+| >Ellipsoid point with uncertainty Ellipse | | | | |
+| >>Ellipsoid point with uncertainty Ellipse | M | | See below | Ellipsoid point with uncertainty Ellipse. |
+| >Ellipsoid point with altitude | | | | |
+| >>Ellipsoid point with altitude | M | | See below | Ellipsoid point with altitude. |
+| >Ellipsoid point with altitude and uncertainty Ellipsoid | | | | |
+| >>Ellipsoid point with altitude and uncertainty Ellipsoid | M | | See below | Ellipsoid point with altitude and uncertainty Ellipsoid. |
+| >Ellipsoid Arc | | | | |
+| >>Ellipsoid Arc | M | | See below | Ellipsoid Arc. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|-----------------------|
+| Point | | | | |
+| >Geographical Coordinates | M | | See below | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------|
+| Point With Uncertainty | | | | |
+| >Geographical Coordinates | M | | See below | |
+| >Uncertainty Code | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ . |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|----------------------|-----------------------|-----------------------|
+| Polygon | | | | |
+| >Geographical Coordinates | M | 1 to | See below | |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------|
+| maxnoofPoints | Maximum no. of points in polygon. Value is 15. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Ellipsoid point with uncertainty Ellipse | | | | |
+| >Geographical Coordinates | M | | See below | |
+| >Uncertainty Ellipse | M | | See below | |
+| >Confidence | M | | INTEGER (0..127) | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|----------|-------|-----------------------|-----------------------|
+| Ellipsoid point with altitude | | | | |
+| >Geographical Coordinates | M | | See below | |
+| >Altitude and direction | M | | See below | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Ellipsoid point with altitude and uncertainty Ellipsoid | | | | |
+| >Geographical Coordinates | M | | See below | |
+| >Altitude and direction | M | | See below | |
+| >Uncertainty Ellipse | M | | See below | |
+| >Uncertainty Altitude | M | | INTEGER (0..127) | |
+| >Confidence | M | | INTEGER (0..127) | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Ellipsoid Arc | | | | |
+| >Geographical Coordinates | M | | See below | |
+| >Inner radius | M | | INTEGER (0..2 16 -1) | The relation between the value (N) and the radius (r) in meters it describes is $5N \leq r < 5(N+1)$ , except for $N=2^{16}-1$ for which the range is extended to include all greater values of (r). |
+| >Uncertainty radius | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ . |
+| >Offset angle | M | | INTEGER (0..179) | The relation between the value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ . |
+| >Included angle | M | | INTEGER (0..179) | The relation between the value (N) and the angle (a) in degrees it describes is $2N < a \leq 2(N+1)$ . |
+| >Confidence | M | | INTEGER (0..127) | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| Geographical Coordinates | | | | |
+| >Latitude Sign | M | | ENUMERATED (North, South) | |
+| >Degrees Of Latitude | M | | INTEGER (0..2 23 -1) | The IE value (N) is derived by this formula: $N \leq 2^{23} \times X / 90 < N+1$ X being the latitude in degree (0°.. 90°). |
+| >Degrees Of Longitude | M | | INTEGER (-2 23 ..2 23 -1) | The IE value (N) is derived by this formula: $N \leq 2^{24} \times X / 360 < N+1$ X being the longitude in degree (-180°..+180°). |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Uncertainty Ellipse | | | | |
+| >Uncertainty semi-major | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ . |
+| >Uncertainty semi-minor | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ . |
+| >Orientation of major axis | M | | INTEGER (0..179) | The relation between the IE value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ . The values 90..179 shall not be used. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Altitude and direction | | | | |
+| >Direction of Altitude | M | | ENUMERATED (Height, Depth) | |
+| >Altitude | M | | INTEGER (0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). |
+
+#### 9.2.3.12 Unsuccessfully Transmitted Data Volume
+
+This information element indicates the data volume (octets) that is unsuccessfully transmitted over the radio interface in the DL direction for a given RAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------|----------|-------|---------------------------------|-----------------------|
+| Unsuccessfully Transmitted Data Volume | M | | INTEGER (0..2 32 -1) | Unit is octet. |
+
+#### 9.2.3.13 Data Volume Reference
+
+This information element indicates the time when the data volume is counted. It is an operator/vendor specific matter to assign meanings for the different integer values.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-----------------------|-----------------------|
+| Data Volume Reference | M | | INTEGER (0..255) | |
+
+#### 9.2.3.14 Information Identity
+
+Void
+
+#### 9.2.3.15 Information Priority
+
+Void
+
+#### 9.2.3.16 Information Control
+
+Void
+
+#### 9.2.3.17 CN Broadcast Area
+
+Void
+
+#### 9.2.3.18 NAS Synchronisation Indicator
+
+This information element contains transparent NAS information that is transferred without interpretation in the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------|
+| NAS Synchronisation Indicator | M | | BIT STRING (4) | The coding of this IE, transparent for RNC, is described in the subclause "Speech Codec Selection" of TS 24.008 [8]. |
+
+#### 9.2.3.19 Location Related Data Request Type
+
+This element indicates the type of the requested location related data for the indicated positioning method, and provides the assistance data for the Assisted GPS positioning method.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|--------------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Requested Location Related Data Type | M | | ENUMERATED(
Deciphering Keys for UE Based OTDOA,
Deciphering Keys for Assisted GPS,
Dedicated Assistance Data for UE Based OTDOA,
Dedicated Assistance Data for Assisted GPS,
...,
Deciphering keys for Assisted GANSS,
Dedicated Assistance Data for Assisted GANSS,
Deciphering keys for Assisted GPS and GANSS,
Dedicated Assistance Data for Assisted GPS and GANSS) | |
+| Requested GPS Assistance Data | C –
ifDedAssGPS | | 9.2.3.21 | |
+
+| Condition | Explanation |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ifDedAssGPS | This IE shall be present if the Requested Location Related Data Type IE is set to 'Dedicated Assistance Data for Assisted GPS' or 'Dedicated Assistance Data for Assisted GPS and GANSS'. |
+
+#### 9.2.3.20 Broadcast Assistance Data Deciphering keys
+
+*This information element is used for indicating the deciphering keys that will be used by the UE for deciphering of broadcast assistance data.*
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------|
+| Ciphering Key Flag | M | | BIT STRING (SIZE(1)) | Indicates the current Ciphering Key Flag that is used for the broadcast assistance data messages in the location area. |
+| Current Deciphering key | M | | BIT STRING (SIZE(56)) | Current deciphering key that is used for deciphering broadcast assistance data. |
+| Next Deciphering key | M | | BIT STRING (SIZE(56)) | Next deciphering key that will be used for deciphering broadcast assistance data. |
+
+#### 9.2.3.21 Requested GPS Assistance Data
+
+This information element is used for indicating the requested GPS assistance data.
+
+This IE is transparent to CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|----------------------------|----------------------------------------------------------------------------------------------|
+| Requested GPS Assistance Data | | | OCTET STRING (SIZE(1..38)) | For the corresponding Information Element Definition see "gpsAssistanceData" TS 24.080 [22]. |
+
+#### 9.2.3.22 Last Known Service Area
+
+*This information element is used for indicating the last known Service Area and the elapsed time since the UE was known to be in this Service Area. The last known Service Area is reported when the current Service Area is unknown to the RNC.*
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SAI | M | | 9.2.3.9 | |
+| Age of SAI | M | | INTEGER (0..32767) | The value represents the elapsed time in minutes since the reported last known SAI was stored by the RNC.
Value "0" shall not be used.
Value "32767" indicates that the age of SAI is at least 32767 minutes old. |
+
+#### 9.2.3.23 Shared Network Information
+
+For each LA contained in this IE, it provides the SNA(s) the LA belongs to.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMNs In Shared Network | | 1 to | | |
+| >PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, two digits per octet,
- - each digit encoded 0000 to 1001,
- - 1111 used as filler
- - bit 4 to 1 of octet n encoding digit 2n-1,
- - bit 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| >LA List | | 1 to | | |
+| >>LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. |
+| >>List Of SNAs Containing LA | | 1 to | | |
+| >>>SNAC | M | | 9.2.3.25 | |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------------------------------------------------------|
+| maxPLMNsSN | Maximum no. of PLMNs involved in a Shared Network agreement. The value for maxPLMNsSN is 32. |
+| maxLAs | Maximum no. of LAs in a PLMN. The value for maxLAs is 65536. |
+| maxSNAs | Maximum no. of SNAs in a PLMN. The value for maxSNAs is 65536. |
+
+#### 9.2.3.24 SNA Access Information
+
+Provides information on the area(s) in the PLMN(s) the UE is authorised to access.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Authorised PLMNs | | 1 to | | |
+| >PLMN Identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, two digits per octet,
- - each digit encoded 0000 to 1001,
- - 1111 used as filler,
- - bit 4 to 1 of octet n encoding digit 2n-1,
- - bit 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| >Authorised SNAs List | O | | | |
+| >>Authorised SNAs | | 1 to | | |
+| >>>SNAC | M | | 9.2.3.25 | |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------------------------------------------------------|
+| maxPLMNsSN | Maximum no. of PLMNs involved in a Shared Network agreement. The value for maxPLMNsSN is 32. |
+| maxSNAs | Maximum no. of SNAs in a PLMN. The value for maxSNAs is 65536. |
+
+#### 9.2.3.25 SNAC
+
+Indicates the Identity of an SNA according to TS 23.003 [19].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| SNAC | M | | INTEGER (0..65535) | |
+
+#### 9.2.3.26 Location Related Data Request Type Specific To GERAN Iu Mode
+
+This element indicates the type of the requested location related data for the indicated specific positioning method supported only within GERAN Iu mode.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Location Related Data Request Type Specific To GERAN Iu mode | | | ENUMERATED(
Deciphering
Keys for E-OTD,
Dedicated
Mobile-Assisted
E-OTD
Assistance
Data,
Dedicated
Mobile-Based
E-OTD
Assistance
Data, ...) | |
+
+#### 9.2.3.27 Position Data
+
+This IE provides data related to the positioning methods in relation with the Location Report procedure.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|---------------------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Positioning Data Discriminator | M | | BIT STRING (SIZE(4)) | The positioning data discriminator defines the type of data provided for each positioning method:
0000 indicates the presence of the Positioning Data Set IE (that reports the usage of each non-GNSS method that was successfully used to obtain the location estimate) and the optional presence of the GNSS Positioning Data Set IE;
0001 indicates the presence of the GNSS Positioning Data Set IE (that reports the usage of each GNSS method that was successfully used to obtain the location estimate) and the absence of the Positioning Data Set IE.
1 octet of data is provided for each positioning method included.
All other values are reserved.
| — | |
+| Positioning Data Set | C-ifDiscriminator=0 | | | | — | |
+
+| | | | | | | |
+|-------------------------------|---|---------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|
+| >Positioning Method and Usage | | 1 to | OCTET STRING SIZE((1)) | Coding of positioning method (bits 8-4):
00000 Reserved (NOTE);
00001 Reserved (NOTE);
00010 Reserved (NOTE);
00011 Reserved (NOTE);
00100 Reserved (NOTE);
00101 Mobile Assisted GPS;
00110 Mobile Based GPS;
00111 Conventional GPS;
01000 U-TDOA;
01001 OTDOA;
01010 IPDL;
01011 RTT;
01100 Cell ID;
01101 to 01111 reserved for other location technologies;
10000 to 11111 reserved for network specific positioning methods.
Coding of usage (bits 3-1):
000 Attempted unsuccessfully due to failure or interruption - not used.
001 Attempted successfully: results not used to generate location - not used.
010 Attempted successfully: results used to verify but not generate location - not used.
011 Attempted successfully: results used to generate location.
100 Attempted successfully: case where MS supports multiple mobile based positioning methods and the actual method or methods used by the MS cannot be determined.
NOTE: Reserved because of GERAN use only.
| - | |
+| GANSS Positioning Data Set | O | | | | YES | ignore |
+
+| | | | | | | |
+|----------------------------------------------|--|---------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|
+| >GANSS
Positioning
Method and
Usage | | 1 to
NSSSet> | OCTET
STRING
(SIZE(1)) | Coding of positioning method (bits 8-7):
00 MS-Based;
01 MS-Assisted;
10 Conventional;
11 Reserved.
Coding of GANSS ID (bits 6-4):
000 Galileo;
001 SBAS;
010 Modernized GPS;
011 QZSS;
100 GLONASS;
other values reserved.
Coding of usage (bits 3-1):
011 Attempted successfully:
results used to generate
location;
100 Attempted successfully:
case where MS supports
multiple mobile based
positioning methods and the
actual method or methods
used by the MS cannot be
determined.
| – | |
+|----------------------------------------------|--|---------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|
+
+| Condition | Explanation |
+|---------------------|-------------------------------------------------------------------------------|
+| C-ifDiscriminator=0 | This IE is present if the Positioning Data Discriminator IE is set to "0000". |
+
+| Range bound | Explanation |
+|-------------|-------------------------------------------|
+| maxSet | Maximum size of the data set. Value is 9. |
+| maxGANSSSet | Maximum size of the data. Value is 9. |
+
+#### 9.2.3.28 Position Data Specific To GERAN Iu Mode
+
+This IE provides data related to the positioning methods which are supported only within GERAN Iu mode in relation with the Location Report procedure. The coding of this element is described in TS 49.031 [34].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------|
+| Position Data Specific To GERAN Iu Mode | M | | OCTET STRING | Coded as the value part of the Positioning Data IE or GANSS Positioning Data IE defined in TS 49.031 [34]. |
+
+#### 9.2.3.29 Accuracy Fulfilment Indicator
+
+This IE indicates whether the returned position estimate satisfies the requested accuracy or not.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|-------------------------------------------------------------------------------------------|-----------------------|
+| Accuracy Fulfilment Indicator | M | | ENUMERATED
(requested accuracy fulfilled,
requested accuracy not fulfilled,
...) | |
+
+#### 9.2.3.30 RIM Transfer
+
+This IE contains the RIM Information (e.g. NACC information) and additionally in uplink transfer the RIM routing address of the destination of this RIM information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-----------------------|-----------------------|
+| RIM Information | M | | 9.2.3.31 | |
+| RIM Routing Address | O | | 9.2.3.32 | |
+
+#### 9.2.3.31 RIM Information
+
+This IE contains the RIM Information (e.g. NACC information) i.e. the BSSGP RIM PDU from the RIM application part contained in the RNC, or the BSSGP RIM PDU to be forwarded to the RIM application part in the RNC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------|----------------------------------------------------------|
+| RIM Information | M | | OCTET STRING | Contains the BSSGP RIM PDU as defined in TS 48.018 [36]. |
+
+#### 9.2.3.32 RIM Routing Address
+
+This IE identifies the destination node where the RIM Information needs to be routed by the CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Choice RIM Routing Address | | | | | - | |
+| > Target RNC-ID | | | | | | |
+| >> Target RNC-ID | M | | | Applicable to GERAN Iu mode, not applicable to UTRAN. | - | |
+| >>>LAI | M | | 9.2.3.6 | | - | |
+| >>>RAC | O | | 9.2.3.7 | | - | |
+| >>>RNC-ID | M | | INTEGER (0..4095) | If the Extended RNC-ID IE is included in the Target RNC-ID IE, the RNC-ID IE shall be ignored. | - | |
+| >>>Extended RNC-ID | O | | 9.2.1.39a | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| > GERAN-Cell-ID | | | | | | |
+| >> GERAN-Cell-ID | M | | | | - | |
+| >>>LAI | M | | 9.2.3.6 | | - | |
+| >>>RAC | M | | 9.2.3.7 | | - | |
+| >>>CI | M | | OCTET STRING (2) | | - | |
+| > Target eNB-ID | | | | | | |
+| >> Target eNB-ID | M | | | | - | |
+| >>>PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit,
- two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
| | |
+| >>>CHOICE eNB ID | | | | | | |
+| >>>>Macro eNB ID | | | BIT STRING (20) | Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of each cell served by the eNodeB. | - | |
+
+| | | | | | | |
+|-----------------|---|--|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|
+| >>>>Home eNB ID | | | BIT STRING (28) | Equal to the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of the cell served by the eNodeB.
NOTE:
Inter-system route to a Home eNB is only supported for Enhanced CS Fallback purpose in this release. | - | |
+| >>>Selected TAI | M | | 9.2.1.30C | Contains the TAC of the target cell and the PLMN selected for that target cell. | - | |
+
+#### 9.2.3.33 Selected PLMN Identity
+
+This information element indicates the selected core network operator in shared networks.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Selected PLMN identity | M | | OCTET STRING (SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The Selected PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+
+#### 9.2.3.34 NAS Sequence Number
+
+This IE is transparent for UTRAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-----------------------|--------------------------------------------------------------|
+| NAS Sequence Number | M | | BIT STRING (SIZE(2)) | Contains the value of the N(SD) as defined in TS 24.008 [8]. |
+
+#### 9.2.3.35 Redirection Completed
+
+This IE indicates to RNC that the redirection is completed.
+
+Direction: CN → RNC
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|--------------------------------------------|-----------------------|
+| Redirection Completed | M | | ENUMERATED
(redirection completed, ...) | |
+
+#### 9.2.3.36 Redirection Indication
+
+This IE is used by a CN to request rerouting by the RNC to another CN operator. It is only used in MOCN configuration for network sharing non-supporting UEs.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Initial NAS-PDU | M | | 9.2.3.5 | The initial NAS-PDU received from UE | YES | ignore |
+| Reject Cause Value | M | | ENUMERATED
(PLMN not allowed, location area not allowed, roaming not allowed in this location area, no suitable cell in location area, GPRS services not allowed in this PLMN, CS/PS coordination required, ..., Network failure, Not authorized for this CSG) | This IE lists cause values which meaning is defined in TS 24.008 [8] with the exception of "CS/PS coordination required" that will never be forwarded to the UE. | YES | ignore |
+| NAS Sequence Number | O | | 9.2.3.34 | | YES | ignore |
+| Permanent NAS UE Identity | O | | 9.2.3.1 | | YES | ignore |
+
+#### 9.2.3.37 TMGI
+
+The TMGI uniquely identifies the MBMS Bearer Service.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M | | OCTET STRING
(SIZE (3)) | - - digits 0 to 9, encoded 0000 to 1001,
- - 1111 used as filler digit, two digits per octet,
- - bits 4 to 1 of octet n encoding digit 2n-1,
- - bits 8 to 5 of octet n encoding digit 2n.
- - The PLMN identity consists of 3 digits from MCC followed by either
- - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)
- or
- - 3 digits from MNC (in case of a 3 digit MNC).
|
+| Service ID | M | | OCTET STRING
(SIZE (3)) | |
+
+#### 9.2.3.38 MBMS Session Identity
+
+The MBMS Session Identity identifies the session of a MBMS Bearer Service in UTRAN and is used by the UE to recognise repetitions of a session.
+
+This IE is transparent to RAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-------------------------|-----------------------------------------------------------------------------|
+| MBMS Session Identity | M | | OCTET STRING (SIZE (1)) | Coded as the MBMS Session Identity IE, as defined in TS 29.061 [44]. |
+
+#### 9.2.3.39 MBMS Bearer Service Type
+
+Indicates the type of the MBMS Bearer Service.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|----------------------------------------|-----------------------|
+| MBMS Bearer Service Type | M | | ENUMERATED (multicast, broadcast, ...) | |
+
+#### 9.2.3.39a MBMS Counting Information
+
+Indicates to the RNC whether MBMS Counting procedures can be applied in MBMS Broadcast Mode.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|------------------------------------------|-----------------------|
+| MBMS Counting Information | M | | ENUMERATED (counting, not counting, ...) | |
+
+#### 9.2.3.40 MBMS Session Duration
+
+This IE defines the duration of the MBMS Session.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-------------------------|------------------------------------------------------------------------------------|
+| MBMS Session Duration | M | | OCTET STRING (SIZE (3)) | Coded as the value part of MBMS-Session-Duration AVP as defined in TS 29.061 [44]. |
+
+#### 9.2.3.41 MBMS Service Area
+
+The MBMS Service Area IE consists of a list of one or several MBMS Service Area Identities where each MBMS Service Area Identity is frequency agnostic and can be mapped onto one or more cells.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------|----------|-------|-----------------------|--------------------------------------------------------------------------|
+| MBMS Service Area | M | | OCTET STRING | Value part coded per MBMS Service Area AVP as defined in TS 29.061 [44]. |
+
+#### 9.2.3.42 RA List of Idle Mode UEs
+
+Indicates the list of RAs where idle-mode UEs interested in a given Multicast Service are.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|-------------------------|------------------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Choice RA List of Idle Mode UEs | | | | | | |
+| > Not Empty RA List of Idle Mode UEs | | | | The same RAC+LAI combination must only be present once. | | |
+| >> RA of Idle Mode UEs | | 1 to | | Each RAC in this list gives a valid RAI only if combined with an LAI of the same index contained in the LA of Idle Mode UEs IE. | | |
+| >>> RAC | M | | 9.2.3.7 | | | |
+| >> LA List of Idle Mode UEs | C-
IfRAofIdleModeUEs | | | | YES | reject |
+| >>> LA of Idle Mode UEs | | 1 to | | | | |
+| >>>> LAI | M | | 9.2.3.6 | | - | |
+| > Empty/Full RA List of Idle Mode UEs | | | | | | |
+| >> Empty/Full RA List of Idle Mode UEs | | | ENUMERATED
(emptylist, fulllist,...) | | | |
+
+| Range bound | Explanation |
+|-------------|---------------------------------------------------------------------------------------------------------------------------------|
+| maxMBMSRA | Maximum no. of Routing Areas where idle-mode UEs interested in a given Multicast Service are. The value for maxMBMSRA is 65536. |
+
+| Condition | Explanation |
+|-------------------|----------------------------------------------------------------------------|
+| IfRAofIdleModeUEs | This IE shall be present if the RA of Idle Mode UEs IE is included. |
+
+#### 9.2.3.43 Delta RA List of Idle Mode UEs
+
+Indicates the list of new RAs where idle-mode UEs interested in a given Multicast Service became or moved to, as well as the list of RAs where there is no interested idle-mode UEs in a given Multicast Service any longer.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|-------------------------------------|------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Delta RA List of Idle Mode UEs | | | | The same RAC+LAI combination must only be present once. | | |
+| >New RA List of Idle Mode UEs | O | | | | | |
+| >>New RA of Idle Mode UEs | | 1 to | | Each RAC in this list gives a valid RAI only if combined with an LAI of the same index contained in the LA of Idle Mode UEs IE. | | |
+| >>>RAC | M | | 9.2.3.7 | | | |
+| >RA List with No Idle Mode UEs Any More | O | | | | | |
+| >>RA with No Idle Mode UEs Any More | | 1 to | | Each RAC in this list gives a valid RAI only if combined with an LAI of the same index contained in the LA of Idle Mode UEs IE. | | |
+| >>>RAC | M | | 9.2.3.7 | | | |
+| >New LA List of Idle Mode UEs | C- IfNewRAListofIdleModeUEs | | | | YES | reject |
+| >>New LA of Idle Mode UEs | | 1 to | | | | |
+| >>>LAI | M | | 9.2.3.6 | | | |
+| >LA List with No Idle Mode UEs Any More | C- IfRAListWithNoIdleModeUEsAnyMore | | | | YES | reject |
+| >>LA with No Idle Mode UEs Any More | | 1 to | | | | |
+| >>>LAI | M | | 9.2.3.6 | | | |
+
+| Range bound | Explanation |
+|-------------|---------------------------------------------------------------------------------------------------------------------------------|
+| maxMBMSRA | Maximum no. of Routing Areas where idle-mode UEs interested in a given Multicast Service are. The value for maxMBMSRA is 65536. |
+
+| Condition | Explanation |
+|----------------------------------|-----------------------------------------------------------------------------------------------|
+| IfNewRAListofIdleModeUEs | This IE shall be present if the New RA List of Idle Mode UEs IE is included. |
+| IfRAListWithNoIdleModeUEsAnyMore | This IE shall be present if the RA List with No Idle Mode UEs Any More IE is included. |
+
+##### 9.2.3.4.4 MBMS CN De-Registration
+
+Indicates whether the MBMS Session Stop procedure is a normal Session Stop or a total de-registration for a given MBMS Bearer Service.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|------------------------------------------------------------|-----------------------|
+| MBMS CN De-Registration | M | | ENUMERATED(
normal
session stop,
deregister,
) | |
+
+#### 9.2.3.45 MBMS Registration Request Type
+
+Indicates the type of the MBMS Registration Request.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|----------------------------------------------|-----------------------|
+| MBMS Registration Request Type | M | | ENUMERATED(
register,
deregister,
) | |
+
+#### 9.2.3.46 Requested MBMS IP Multicast Address and APN
+
+Informs the RNC about the requested pairs of IP Multicast Address and APN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------|----------|------------------------------------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| MBMS IP Multicast Address and APN list | | 1 to
| | |
+| >TMGI | M | | 9.2.3.37 | |
+| >IP Multicast Address | M | | OCTET STRING
(4..16) | Transparent information to RAN.
Octet string size 4 represents IPv4 address.
Octet string size 16 represents IPv6 address. |
+| >APN | M | | OCTET STRING
(1..255) | Transparent information to RAN. |
+
+| Range bound | Explanation |
+|--------------------------------|-------------------------------------------------------------------------------------|
+| maxnoofMulticastServicesPerRNC | Maximum no. of Multicast Services that a RNC can have context for.
Value is 512. |
+
+#### 9.2.3.47 Requested Multicast Service List
+
+Informs the RNC about the requested Multicast Service list for a particular UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-----------------------------------------------|-----------------------|------------------------------------------|
+| TMGI | | 1 to
| 9.2.3.37 | The same TMGI must only be present once. |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------------------------------|
+| maxnoofMulticastServicesJoinedPerUE | Maximum no. of Multicast Services that a UE can join respectively.
Value is 128. |
+
+#### 9.2.3.48 MBMS Session Repetition Number
+
+Informs the RNC about the repetitions of a particular session of a MBMS Bearer Service.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------|
+| MBMS Session Repetition Number | M | | OCTET STRING (SIZE (1)) | Coded as the value part of MBMS-Session - Repetition-Number AVP as defined in TS 29.061 [44]. |
+
+#### 9.2.3.49 Time to MBMS Data Transfer
+
+This IE denotes the time occurring between the transmission of the MBMS SESSION START message to the RNS and the actual start of the data transfer. The coding of this element is described in TS 48.018 [36].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------|
+| Time to MBMS Data Transfer | M | | OCTET STRING (SIZE (1)) | Coded as the value part of Time to MBMS Data Transfer IE defined in TS 48.018 [36]. |
+
+#### 9.2.3.50 Redirect Attempt Flag
+
+This IE indicates that the CN should respond with a *Redirection Indication* IE or a *Redirection completed* IE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-----------------------|-----------------------|
+| Redirect Attempt Flag | M | | NULL | |
+
+#### 9.2.3.51 Velocity Estimate
+
+The *Velocity Estimate* IE is used to describe the UE's velocity. The reference system is the same as used in TS 23.032 [20].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------|
+| Choice Velocity Estimate | | | | |
+| > Horizontal Velocity | | | | |
+| >> Horizontal Velocity | M | | See below | Horizontal speed and bearing (the direction of travel). |
+| > Horizontal with Vertical Velocity | | | | |
+| >> Horizontal with Vertical Velocity | M | | See below | Horizontal speed, bearing (the direction of travel), and vertical speed. |
+| > Horizontal Velocity with Uncertainty | | | | |
+| >> Horizontal Velocity with Uncertainty | M | | See below | Horizontal speed, bearing (the direction of travel), and the uncertainty of the reported speed. |
+| > Horizontal with Vertical Velocity and Uncertainty | | | | |
+| >> Horizontal with Vertical Velocity and Uncertainty | M | | See below | Horizontal speed, bearing (the direction of travel), vertical speed and the uncertainty of the reported speed. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|-----------------------|-----------------------|
+| Horizontal Velocity | | | | |
+| >Horizontal Speed and Bearing | M | | See below | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Horizontal with Vertical Velocity | | | | |
+| >Horizontal Speed and Bearing | M | | See below | |
+| >Vertical Velocity | M | | See below | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Horizontal Velocity with Uncertainty | | | | |
+| >Horizontal Speed and Bearing | M | | See below | |
+| >>Uncertainty Speed | M | | INTEGER (0..255) | Uncertainty speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Horizontal with Vertical Velocity and Uncertainty | | | | |
+| >Horizontal Speed and Bearing | M | | See below | |
+| >>Vertical Velocity | M | | See below | |
+| >>Horizontal Uncertainty Speed | M | | INTEGER (0..255) | Horizontal Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified. |
+| >>Vertical Uncertainty Speed | M | | INTEGER (0..255) | Vertical Uncertainty speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|-------|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Horizontal Speed and Bearing | | | | |
+| >Bearing | M | | INTEGER (0..359) | The direction of movement is given in degrees where '0' represents North, '90' represents East, etc. |
+| >Horizontal Speed | M | | INTEGER (0..< 2 11 -1) | The relationship between (N) and the horizontal speed (h) in kilometers per hour it describes is:
$N \leq h < N + 0.5$ (N=0)
$N - 0.5 \leq h < N + 0.5$ (0 < N < 2 11 -1)
$N - 0.5 \leq h$ (N = 2 11 -1). |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Vertical Velocity | | | | |
+| >Vertical Speed | M | | INTEGER (0..2 8 -1) | The relationship between (N) and the vertical speed (v) in kilometers per hour it describes is:
$N \leq v < N + 0.5$ (N = 0)
$N - 0.5 \leq v < N + 0.5$ (0 < N < 2 8 -1)
$N - 0.5 \leq v$ (N = 2 8 -1). |
+| >Vertical Speed Direction | M | | ENUMERATED (upward, downward) | |
+
+#### 9.2.3.52 RAT Type
+
+Indicates the RAT from which the context request originates.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------------|----------------------------------------------------------------------------------|
+| RAT Type | O | | ENUMERATED(UTRAN, GERAN, ...) | GERAN means GERAN Gb mode. UTRAN means UTRAN but may also include GERAN Iu mode. |
+
+#### 9.2.3.53 Requested GANSS Assistance Data
+
+This information element is used for indicating the requested GANSS assistance data.
+
+This IE is transparent to CN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-------|-----------------------------|------------------------------------------------------------------------------------------------|
+| Requested GANSS Assistance Data | | | OCTET STRING (SIZE(1..201)) | For the corresponding Information Element Definition see "ganssAssistanceData" TS 24.080 [22]. |
+
+#### 9.2.3.54 Higher bitrates than 16 Mbps flag
+
+This information element indicates whether the UE is capable of handling NAS QoS extensions introduced in Rel-7, or not. See also TS 23.060 [21].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------|-------------------------------------------|-----------------------|
+| Higher bitrates than 16 Mbps flag | | | ENUMERATED
(allowed, not-allowed, ...) | |
+
+## 9.3 Message and Information Element Abstract Syntax (with ASN.1)
+
+### 9.3.0 General
+
+RANAP ASN.1 definition conforms with ITU-T Rec. X.680 [14] and ITU-T Rec. X.681 [15].
+
+The ASN.1 definition specifies the structure and content of RANAP messages. RANAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a RANAP message according to the PDU definitions module and with the following additional rules:
+
+- IEs shall be ordered (in an IE container) in the order they appear in object set definitions..
+- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
+
+NOTE: "IE" means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE IDs.
+
+If a RANAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in subclause 10.3.6.
+
+Subclause 9.3 presents the Abstract Syntax of RANAP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this subclause and the tabular format in subclause 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence.
+
+### 9.3.1 Usage of private message mechanism for non-standard use
+
+The private message mechanism for non-standard use may be used:
+
+- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability;
+- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
+
+The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
+
+### 9.3.2 Elementary Procedure Definitions
+
+```
+-- *****
+--
+-- Elementary Procedure definitions
+--
+-- *****
+```
+
+```
+RANAP-PDU-Descriptions {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ umts-Access (20) modules (3) ranap (0) version1 (1) ranap-PDU-Descriptions (0)}
+```
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+```
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+```
+
+```
+IMPORTS
+ Criticality,
+ ProcedureCode
+FROM RANAP-CommonDataTypes
+
+ Iu-ReleaseCommand,
+ Iu-ReleaseComplete,
+ RelocationCommand,
+ RelocationPreparationFailure,
+ RelocationRequired,
+ RelocationRequest,
+ RelocationRequestAcknowledgement,
+ RelocationFailure,
+ RelocationCancel,
+ RelocationCancelAcknowledgement,
+ EnhancedRelocationCompleteRequest,
+ EnhancedRelocationCompleteResponse,
+ EnhancedRelocationCompleteFailure,
+ EnhancedRelocationCompleteConfirm,
+ SRNS-ContextRequest,
+ SRNS-ContextResponse,
+ SecurityModeCommand,
+ SecurityModeComplete,
+ SecurityModeReject,
+ DataVolumeReportRequest,
+ DataVolumeReport,
+ Reset,
+ ResetAcknowledgement,
+ RAB-ReleaseRequest,
+ Iu-ReleaseRequest,
+ RelocationDetect,
+ RelocationComplete,
+ Paging,
+ CommonID,
+ CN-InvokeTrace,
+ CN-DeactivateTrace,
+ LocationReportingControl,
+ LocationReport,
+ InitialUE-Message,
+ DirectTransfer,
+ Overload,
+ ErrorIndication,
+ SRNS-DataForwardCommand,
+ ForwardSRNS-Context,
+ RAB-AssignmentRequest,
+ RAB-AssignmentResponse,
+ RAB-ModifyRequest,
+ PrivateMessage,
+ ResetResource,
+ ResetResourceAcknowledgement,
+ RANAP-RelocationInformation,
+ RANAP-EnhancedRelocationInformationRequest,
+ RANAP-EnhancedRelocationInformationResponse,
+ LocationRelatedDataRequest,
+ LocationRelatedDataResponse,
+ LocationRelatedDataFailure,
+ InformationTransferIndication,
+ InformationTransferConfirmation,
+ InformationTransferFailure,
+ UESpecificInformationIndication,
+ DirectInformationTransfer,
+ UplinkInformationExchangeRequest,
+ UplinkInformationExchangeResponse,
+ UplinkInformationExchangeFailure,
+ MBMSessionStart,
+ MBMSessionStartResponse,
+ MBMSessionStartFailure,
+ MBMSessionUpdate,
+ MBMSessionUpdateResponse,
+ MBMSessionUpdateFailure,
+ MBMSessionStop,
+ MBMSessionStopResponse,
+ MBMSUELinkingRequest,
+ MBMSUELinkingResponse,
+ MBMSRegistrationRequest,
+ MBMSRegistrationResponse,
+ MBMSRegistrationFailure,
+```
+
+```
+
+MBMSCNDe-RegistrationRequest,
+MBMSCNDe-RegistrationResponse,
+MBMSRABEstablishmentIndication,
+MBMSRABReleaseRequest,
+MBMSRABRelease,
+MBMSRABReleaseFailure,
+SRVCC-CSKeysRequest,
+SRVCC-CSKeysResponse,
+UeRadioCapabilityMatchRequest,
+UeRadioCapabilityMatchResponse
+FROM RANAP-PDU-Contents
+
+id-LocationRelatedData,
+id-CN-DeactivateTrace,
+id-CN-InvokeTrace,
+id-CommonID,
+id-DataVolumeReport,
+id-DirectTransfer,
+id-ErrorIndication,
+id-ForwardSRNS-Context,
+id-InformationTransfer,
+id-InitialUE-Message,
+id-Iu-Release,
+id-Iu-ReleaseRequest,
+id-LocationReport,
+id-LocationReportingControl,
+id-OverloadControl,
+id-Paging,
+id-privateMessage,
+id-RAB-Assignment,
+id-RAB-ReleaseRequest,
+id-RAB-ModifyRequest,
+id-RANAP-Relocation,
+id-RANAPenhancedRelocation,
+id-RelocationCancel,
+id-RelocationComplete,
+id-RelocationDetect,
+id-RelocationPreparation,
+id-RelocationResourceAllocation,
+id-enhancedRelocationComplete,
+id-enhancedRelocationCompleteConfirm,
+id-Reset,
+id-SRNS-ContextTransfer,
+id-SRNS-DataForward,
+id-SecurityModeControl,
+id-ResetResource,
+id-UESpecificInformation,
+id-DirectInformationTransfer,
+id-UplinkInformationExchange,
+id-MBMSessionStart,
+id-MBMSessionUpdate,
+id-MBMSessionStop,
+id-MBMSUELinking,
+id-MBMSRegistration,
+id-MBSCNDe-Registration-Procedure,
+id-MBMSRABEstablishmentIndication,
+id-MBMSRABRelease,
+id-SRVCCPreparation,
+id-UeRadioCapabilityMatch
+
+FROM RANAP-Constants;
+
+-- *****
+--
+-- Interface Elementary Procedure Class
+--
+-- *****
+
+RANAP-ELEMENTARY-PROCEDURE ::= CLASS {
+ &InitiatingMessage ,
+ &SuccessfulOutcome OPTIONAL,
+ &UnsuccessfulOutcome OPTIONAL,
+ &Outcome OPTIONAL,
+ &procedureCode ProcedureCode UNIQUE,
+ &criticality Criticality DEFAULT ignore
+}
+WITH SYNTAX {
+ INITIATING MESSAGE &InitiatingMessage
+}
+
+```
+
+```
+
+ [SUCCESSFUL OUTCOME &SuccessfulOutcome]
+ [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]
+ [OUTCOME &Outcome]
+ PROCEDURE CODE &procedureCode
+ [CRITICALITY &criticality]
+ }
+
+ -- *****
+ --
+ -- Interface PDU Definition
+ --
+ -- *****
+
+ RANAP-PDU ::= CHOICE {
+ initiatingMessage InitiatingMessage,
+ successfulOutcome SuccessfulOutcome,
+ unsuccessfulOutcome UnsuccessfulOutcome,
+ outcome Outcome,
+ ...
+ }
+
+ InitiatingMessage ::= SEQUENCE {
+ procedureCode RANAP-ELEMENTARY-PROCEDURE.&procedureCode ({RANAP-ELEMENTARY-PROCEDURES}),
+ criticality RANAP-ELEMENTARY-PROCEDURE.&criticality ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value RANAP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode})
+ }
+
+ SuccessfulOutcome ::= SEQUENCE {
+ procedureCode RANAP-ELEMENTARY-PROCEDURE.&procedureCode ({RANAP-ELEMENTARY-PROCEDURES}),
+ criticality RANAP-ELEMENTARY-PROCEDURE.&criticality ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value RANAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode})
+ }
+
+ UnsuccessfulOutcome ::= SEQUENCE {
+ procedureCode RANAP-ELEMENTARY-PROCEDURE.&procedureCode ({RANAP-ELEMENTARY-PROCEDURES}),
+ criticality RANAP-ELEMENTARY-PROCEDURE.&criticality ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value RANAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode})
+ }
+
+ Outcome ::= SEQUENCE {
+ procedureCode RANAP-ELEMENTARY-PROCEDURE.&procedureCode ({RANAP-ELEMENTARY-PROCEDURES}),
+ criticality RANAP-ELEMENTARY-PROCEDURE.&criticality ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value RANAP-ELEMENTARY-PROCEDURE.&Outcome ({RANAP-ELEMENTARY-PROCEDURES}{@procedureCode})
+ }
+
+ -- *****
+ --
+ -- Interface Elementary Procedure List
+ --
+ -- *****
+
+ RANAP-ELEMENTARY-PROCEDURES RANAP-ELEMENTARY-PROCEDURE ::= {
+ RANAP-ELEMENTARY-PROCEDURES-CLASS-1 |
+ RANAP-ELEMENTARY-PROCEDURES-CLASS-2 |
+ RANAP-ELEMENTARY-PROCEDURES-CLASS-3 ,
+ ...
+ }
+
+ RANAP-ELEMENTARY-PROCEDURES-CLASS-1 RANAP-ELEMENTARY-PROCEDURE ::= {
+ iu-Release |
+ relocationPreparation |
+ relocationResourceAllocation |
+ relocationCancel |
+ sRNS-ContextTransfer |
+ securityModeControl |
+ dataVolumeReport |
+ reset |
+ resetResource ,
+ ...
+ }
+
+```
+
+```
+
+locationRelatedData |
+informationTransfer |
+uplinkInformationExchange |
+mBMSSessionStart |
+mBMSSessionUpdate |
+mBMSSessionStop |
+mBMSUELinking |
+mBMSRegistration |
+mBMSCNDe-Registration |
+mBMSRABRelease |
+enhancedRelocationComplete |
+rANAP-enhancedRelocation |
+sRVCCPreparation |
+ueRadioCapabilityMatch }
+
+RANAP-ELEMENTARY-PROCEDURES-CLASS-2 RANAP-ELEMENTARY-PROCEDURE ::= {
+ rAB-ReleaseRequest |
+ iu-ReleaseRequest |
+ relocationDetect |
+ relocationComplete |
+ paging |
+ commonID |
+ cN-InvokeTrace |
+ cN-DeactivateTrace |
+ locationReportingControl |
+ locationReport |
+ initialUE-Message |
+ directTransfer |
+ overloadControl |
+ errorIndication |
+ sRNS-DataForward |
+ forwardSRNS-Context |
+ privateMessage |
+ rANAP-Relocation ,
+ ...,
+ rAB-ModifyRequest |
+ uESpecificInformation |
+ directInformationTransfer |
+ mBMSRABEstablishmentIndication |
+ enhancedRelocationCompleteConfirm
+}
+
+RANAP-ELEMENTARY-PROCEDURES-CLASS-3 RANAP-ELEMENTARY-PROCEDURE ::= {
+ rAB-Assignment ,
+ ...
+}
+
+-- *****
+--
+-- Interface Elementary Procedures
+--
+-- *****
+
+iu-Release RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE Iu-ReleaseCommand
+ SUCCESSFUL OUTCOME Iu-ReleaseComplete
+ PROCEDURE CODE id-Iu-Release
+ CRITICALITY reject
+}
+
+relocationPreparation RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RelocationRequired
+ SUCCESSFUL OUTCOME RelocationCommand
+ UNSUCCESSFUL OUTCOME RelocationPreparationFailure
+ PROCEDURE CODE id-RelocationPreparation
+ CRITICALITY reject
+}
+
+relocationResourceAllocation RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RelocationRequest
+ SUCCESSFUL OUTCOME RelocationRequestAcknowledge
+ UNSUCCESSFUL OUTCOME RelocationFailure
+ PROCEDURE CODE id-RelocationResourceAllocation
+ CRITICALITY reject
+}
+
+relocationCancel RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RelocationCancel
+}
+
+```
+
+```
+ SUCCESSFUL OUTCOME RelocationCancelAcknowledge
+ PROCEDURE CODE id-RelocationCancel
+ CRITICALITY reject
+ }
+
+ sRNS-ContextTransfer RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE sRNS-ContextRequest
+ SUCCESSFUL OUTCOME sRNS-ContextResponse
+ PROCEDURE CODE id-sRNS-ContextTransfer
+ CRITICALITY reject
+ }
+
+ securityModeControl RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SecurityModeCommand
+ SUCCESSFUL OUTCOME SecurityModeComplete
+ UNSUCCESSFUL OUTCOME SecurityModeReject
+ PROCEDURE CODE id-SecurityModeControl
+ CRITICALITY reject
+ }
+
+ dataVolumeReport RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE DataVolumeReportRequest
+ SUCCESSFUL OUTCOME DataVolumeReport
+ PROCEDURE CODE id-DataVolumeReport
+ CRITICALITY reject
+ }
+
+ reset RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE Reset
+ SUCCESSFUL OUTCOME ResetAcknowledge
+ PROCEDURE CODE id-Reset
+ CRITICALITY reject
+ }
+
+ rAB-ReleaseRequest RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RAB-ReleaseRequest
+ PROCEDURE CODE id-RAB-ReleaseRequest
+ CRITICALITY ignore
+ }
+
+ iu-ReleaseRequest RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE Iu-ReleaseRequest
+ PROCEDURE CODE id-Iu-ReleaseRequest
+ CRITICALITY ignore
+ }
+
+ relocationDetect RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RelocationDetect
+ PROCEDURE CODE id-RelocationDetect
+ CRITICALITY ignore
+ }
+
+ relocationComplete RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RelocationComplete
+ PROCEDURE CODE id-RelocationComplete
+ CRITICALITY ignore
+ }
+
+ paging RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE Paging
+ PROCEDURE CODE id-Paging
+ CRITICALITY ignore
+ }
+
+ commonID RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE CommonID
+ PROCEDURE CODE id-CommonID
+ CRITICALITY ignore
+ }
+
+ cN-InvokeTrace RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE CN-InvokeTrace
+ PROCEDURE CODE id-CN-InvokeTrace
+ CRITICALITY ignore
+ }
+
+ cN-DeactivateTrace RANAP-ELEMENTARY-PROCEDURE ::= {
+```
+
+```
+ INITIATING MESSAGE CN-DeactivateTrace
+ PROCEDURE CODE id-CN-DeactivateTrace
+ CRITICALITY ignore
+ }
+
+ locationReportingControl RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE LocationReportingControl
+ PROCEDURE CODE id-LocationReportingControl
+ CRITICALITY ignore
+ }
+
+ locationReport RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE LocationReport
+ PROCEDURE CODE id-LocationReport
+ CRITICALITY ignore
+ }
+
+ initialUE-Message RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE InitialUE-Message
+ PROCEDURE CODE id-InitialUE-Message
+ CRITICALITY ignore
+ }
+
+ directTransfer RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE DirectTransfer
+ PROCEDURE CODE id-DirectTransfer
+ CRITICALITY ignore
+ }
+
+ overloadControl RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE Overload
+ PROCEDURE CODE id-OverloadControl
+ CRITICALITY ignore
+ }
+
+ errorIndication RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ErrorIndication
+ PROCEDURE CODE id-ErrorIndication
+ CRITICALITY ignore
+ }
+
+ sRNS-DataForward RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE sRNS-DataForwardCommand
+ PROCEDURE CODE id-sRNS-DataForward
+ CRITICALITY ignore
+ }
+
+ forwardSRNS-Context RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ForwardSRNS-Context
+ PROCEDURE CODE id-ForwardSRNS-Context
+ CRITICALITY ignore
+ }
+
+ rAB-Assignment RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RAB-AssignmentRequest
+ OUTCOME RAB-AssignmentResponse
+ PROCEDURE CODE id-RAB-Assignment
+ CRITICALITY reject
+ }
+
+ privateMessage RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE PrivateMessage
+
+ PROCEDURE CODE id-privateMessage
+ CRITICALITY ignore
+ }
+
+ resetResource RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ResetResource
+ SUCCESSFUL OUTCOME ResetResourceAcknowledge
+ PROCEDURE CODE id-ResetResource
+ CRITICALITY reject
+ }
+
+ rRANAP-Relocation RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RANAP-RelocationInformation
+ PROCEDURE CODE id-RANAP-Relocation
+ CRITICALITY ignore
+ }
+```
+
+```
+ }
+
+ rAB-ModifyRequest RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RAB-ModifyRequest
+ PROCEDURE CODE id-RAB-ModifyRequest
+ CRITICALITY ignore
+ }
+
+ locationRelatedData RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE LocationRelatedDataRequest
+ SUCCESSFUL OUTCOME LocationRelatedDataResponse
+ UNSUCCESSFUL OUTCOME LocationRelatedDataFailure
+ PROCEDURE CODE id-LocationRelatedData
+ CRITICALITY reject
+ }
+
+ informationTransfer RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE InformationTransferIndication
+ SUCCESSFUL OUTCOME InformationTransferConfirmation
+ UNSUCCESSFUL OUTCOME InformationTransferFailure
+ PROCEDURE CODE id-InformationTransfer
+ CRITICALITY reject
+ }
+
+ uESpecificInformation RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE UESpecificInformationIndication
+ PROCEDURE CODE id-UESpecificInformation
+ CRITICALITY ignore
+ }
+
+ directInformationTransfer RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE DirectInformationTransfer
+ PROCEDURE CODE id-DirectInformationTransfer
+ CRITICALITY ignore
+ }
+
+ uplinkInformationExchange RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE UplinkInformationExchangeRequest
+ SUCCESSFUL OUTCOME UplinkInformationExchangeResponse
+ UNSUCCESSFUL OUTCOME UplinkInformationExchangeFailure
+ PROCEDURE CODE id-UplinkInformationExchange
+ CRITICALITY reject
+ }
+
+ mBMSSessionStart RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSSessionStart
+ SUCCESSFUL OUTCOME MBMSSessionStartResponse
+ UNSUCCESSFUL OUTCOME MBMSSessionStartFailure
+ PROCEDURE CODE id-MBMSSessionStart
+ CRITICALITY reject
+ }
+
+ mBMSSessionUpdate RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSSessionUpdate
+ SUCCESSFUL OUTCOME MBMSSessionUpdateResponse
+ UNSUCCESSFUL OUTCOME MBMSSessionUpdateFailure
+ PROCEDURE CODE id-MBMSSessionUpdate
+ CRITICALITY reject
+ }
+
+ mBMSSessionStop RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSSessionStop
+ SUCCESSFUL OUTCOME MBMSSessionStopResponse
+ PROCEDURE CODE id-MBMSSessionStop
+ CRITICALITY reject
+ }
+
+ mBMSUELinking RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSUELinkingRequest
+ OUTCOME MBMSUELinkingResponse
+ PROCEDURE CODE id-MBMSUELinking
+ CRITICALITY reject
+ }
+
+ mBMSRegistration RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSRegistrationRequest
+ SUCCESSFUL OUTCOME MBMSRegistrationResponse
+ UNSUCCESSFUL OUTCOME MBMSRegistrationFailure
+ }
+
+```
+
+```
+
+ PROCEDURE CODE id-MBMSRegistration
+ CRITICALITY reject
+ }
+
+ mBMSCNDe-Registration RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSCNDe-RegistrationRequest
+ SUCCESSFUL OUTCOME MBMSCNDe-RegistrationResponse
+ PROCEDURE CODE id-MBMSCNDe-Registration-Procedure
+ CRITICALITY reject
+ }
+
+ mBMSRABEstablishmentIndication RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSRABEstablishmentIndication
+ PROCEDURE CODE id-MBMSRABEstablishmentIndication
+ CRITICALITY ignore
+ }
+
+ mBMSRABRelease RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MBMSRABReleaseRequest
+ SUCCESSFUL OUTCOME MBMSRABRelease
+ UNSUCCESSFUL OUTCOME MBMSRABReleaseFailure
+ PROCEDURE CODE id-MBMSRABRelease
+ CRITICALITY reject
+ }
+
+ enhancedRelocationComplete RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE EnhancedRelocationCompleteRequest
+ SUCCESSFUL OUTCOME EnhancedRelocationCompleteResponse
+ UNSUCCESSFUL OUTCOME EnhancedRelocationCompleteFailure
+ PROCEDURE CODE id-enhancedRelocationComplete
+ CRITICALITY reject
+ }
+
+ enhancedRelocationCompleteConfirm RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE EnhancedRelocationCompleteConfirm
+ PROCEDURE CODE id-enhancedRelocationCompleteConfirm
+ CRITICALITY ignore
+ }
+
+ rANAP-enhancedRelocation RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RANAP-EnhancedRelocationInformationRequest
+ SUCCESSFUL OUTCOME RANAP-EnhancedRelocationInformationResponse
+ PROCEDURE CODE id-RANAPenhancedRelocation
+ CRITICALITY reject
+ }
+
+ sRVCCPreparation RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SRVCC-CSKeysRequest
+ OUTCOME SRVCC-CSKeysResponse
+ PROCEDURE CODE id-SRVCCPreparation
+ CRITICALITY reject
+ }
+
+ ueRadioCapabilityMatch RANAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE UeRadioCapabilityMatchRequest
+ OUTCOME UeRadioCapabilityMatchResponse
+ PROCEDURE CODE id-UeRadioCapabilityMatch
+ CRITICALITY ignore
+ }
+
+END
+
+```
+
+### 9.3.3 PDU Definitions
+
+```
+
+-- *****
+--
+-- PDU definitions for RANAP.
+--
+-- *****
+
+RANAP-PDU-Contents {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ umts-Access (20) modules (3) ranap (0) version1 (1) ranap-PDU-Contents (1) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+```
+
+```
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+```
+
+### IMPORTS
+
+```
+AccuracyFulfilmentIndicator,
+APN,
+BroadcastAssistanceDataDecipheringKeys,
+LocationRelatedDataRequestType,
+LocationRelatedDataRequestTypeSpecificToGERANIuMode,
+DataVolumeReference,
+CellLoadInformation,
+AreaIdentity,
+CN-DomainIndicator,
+Cause,
+Cell-Access-Mode,
+ClientType,
+CriticalityDiagnostics,
+ChosenEncryptionAlgorithm,
+ChosenIntegrityProtectionAlgorithm,
+ClassmarkInformation2,
+ClassmarkInformation3,
+CSG-Id,
+CSG-Id-List,
+CSG-Membership-Status,
+DL-GTP-PDU-SequenceNumber,
+DL-N-PDU-SequenceNumber,
+DataVolumeReportingIndication,
+DeltaRAListofIdleModeUEs,
+DRX-CycleLengthCoefficient,
+EncryptionInformation,
+EncryptionKey,
+E-UTRAN-Service-Handover,
+ExtendedRNC-ID,
+FrequencyLayerConvergenceFlag,
+GERAN-BSC-Container,
+GERAN-Classmark,
+GlobalCN-ID,
+GlobalRNC-ID,
+GTP-TEI,
+IncludeVelocity,
+InformationExchangeID,
+InformationExchangeType,
+InformationRequested,
+InformationRequestType,
+InformationTransferID,
+InformationTransferType,
+InterSystemInformationTransferType,
+IntegrityProtectionInformation,
+IntegrityProtectionKey,
+InterSystemInformation-TransparentContainer,
+IPMulticastAddress,
+IuSignallingConnectionIdentifier,
+IuTransportAssociation,
+KeyStatus,
+L3-Information,
+LAI,
+LastKnownServiceArea,
+Correlation-ID,
+MBMS-PTP-RAB-ID,
+MBMSBearerServiceType,
+MBMSCountingInformation,
+MBMSCNDe-Registration,
+MBMSHCIndicator,
+MBMSRegistrationRequestType,
+MBMSServiceArea,
+MBMSSessionDuration,
+MBMSSessionIdentity,
+MBMSSessionRepetitionNumber,
+MSISDN,
+NAS-PDU,
+NAS-SequenceNumber,
+NAS-SynchronisationIndicator,
+NewBSS-To-OldBSS-Information,
+NonSearchingIndication,
+NumberOfSteps,
+```
+
+Offload-RAB-Parameters,
+Offload-RAB-Parameters-APN,
+Offload-RAB-Parameters-ChargingCharacteristics,
+OMC-ID,
+OldBSS-ToNewBSS-Information,
+PagingAreaID,
+PagingCause,
+PDP-TypeInformation,
+PDP-TypeInformation-extension,
+PermanentNAS-UE-ID,
+PLMNIdentity,
+PositionData,
+PositionDataSpecificToGERANIuMode,
+PositioningPriority,
+ProvidedData,
+RAB-ID,
+RAB-Parameters,
+RAC,
+RANListofIdleModeUEs,
+RAT-Type,
+RedirectAttemptFlag,
+RedirectionCompleted,
+RejectCauseValue,
+RelocationType,
+RequestedGANSSAssistanceData,
+RequestType,
+Requested-RAB-Parameter-Values,
+ResponseTime,
+RRC-Container,
+RSRVCC-Operation-Possible,
+SAI,
+SAPI,
+Service-Handover,
+SessionUpdateID,
+SNA-Access-Information,
+SourceBSS-ToTargetBSS-TransparentContainer,
+SourceID,
+Source-ToTarget-TransparentContainer,
+SourceRNC-ToTargetRNC-TransparentContainer,
+SRVCC-HO-Indication,
+SRVCC-Information,
+SRVCC-Operation-Possible,
+TargetBSS-ToSourceBSS-TransparentContainer,
+TargetID,
+Target-ToSource-TransparentContainer,
+TargetRNC-ToSourceRNC-TransparentContainer,
+TemporaryUE-ID,
+TimeToMBMSDataTransfer,
+TMGI,
+TracePropagationParameters,
+TraceReference,
+TraceType,
+UnsuccessfullyTransmittedDataVolume,
+TransportLayerAddress,
+TriggerID,
+UE-AggregateMaximumBitRate,
+UE-ID,
+UESBI-Iu,
+UL-GTP-PDU-SequenceNumber,
+UL-N-PDU-SequenceNumber,
+UP-ModeVersions,
+UserPlaneMode,
+VelocityEstimate,
+VerticalAccuracyCode,
+VoiceSupportMatchIndicator,
+Alt-RAB-Parameters,
+Ass-RAB-Parameters,
+PeriodicLocationInfo,
+SubscriberProfileIDforRFP,
+RNSAPRelocationParameters,
+RABParametersList,
+MDT-Configuration,
+Priority-Class-Indicator,
+Management-Based-MDT-Allowed,
+HigherBitratesThan16MbpsFlag,
+End-Of-CSFB,
+Out-Of-UTRAN,
+RSRVCC-HO-Indication,
+
+RSRVCC-Information,
+MDT-PLMN-List,
+TunnelInformation
+
+FROM RANAP-IEs
+
+PrivateIE-Container{},
+ProtocolExtensionContainer{},
+ProtocolIE-ContainerList{},
+ProtocolIE-ContainerPair{},
+ProtocolIE-ContainerPairList{},
+ProtocolIE-Container{},
+RANAP-PRIVATE-IEs,
+RANAP-PROTOCOL-EXTENSION,
+RANAP-PROTOCOL-IEs,
+RANAP-PROTOCOL-IES-PAIR
+
+FROM RANAP-Containers
+
+maxNrOfDTs,
+maxNrOfErrors,
+maxNrOfIuSigConIds,
+maxNrOfRABs,
+maxNrOfVol,
+maxnoofMulticastServicesPerUE,
+
+id-AccuracyFulfilmentIndicator,
+id-APN,
+id-AreaIdentity,
+id-Alt-RAB-Parameters,
+id-Ass-RAB-Parameters,
+id-BroadcastAssistanceDataDecipheringKeys,
+id-LocationRelatedDataRequestType,
+id-CN-DomainIndicator,
+id-Cause,
+id-Cell-Access-Mode,
+id-ChosenEncryptionAlgorithm,
+id-ChosenIntegrityProtectionAlgorithm,
+id-ClassmarkInformation2,
+id-ClassmarkInformation3,
+id-ClientType,
+id-CNMBMSLinkingInformation,
+id-CriticalityDiagnostics,
+id-CSG-Id,
+id-CSG-Id-List,
+id-CSG-Membership-Status,
+id-DeltaRAListofIdleModeUEs,
+id-DRX-CycleLengthCoefficient,
+id-DirectTransferInformationItem-RANAP-RelocInf,
+id-DirectTransferInformationList-RANAP-RelocInf,
+id-DL-GTP-PDU-SequenceNumber,
+id-EncryptionInformation,
+id-EncryptionKey,
+id-ExtendedRNC-ID,
+id-FrequenceLayerConvergenceFlag,
+id-GERAN-BSC-Container,
+id-GERAN-Classmark,
+id-GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item,
+id-GERAN-Iumode-RAB-FailedList-RABAssgntResponse,
+id-GlobalCN-ID,
+id-GlobalCN-IDCS,
+id-GlobalCN-IDPS,
+id-GlobalRNC-ID,
+id-IncludeVelocity,
+id-InformationExchangeID,
+id-InformationExchangeType,
+id-InformationRequested,
+id-InformationRequestType,
+id-InformationTransferID,
+id-InformationTransferType,
+id-IntegrityProtectionInformation,
+id-IntegrityProtectionKey,
+id-InterSystemInformationTransferType,
+id-InterSystemInformation-TransparentContainer,
+id-IPMulticastAddress,
+id-IuSigConId,
+id-OldIuSigConId,
+id-OldIuSigConIdCS,
+id-OldIuSigConIdPS,
+
+id-IuSigConIdItem,
+id-IuSigConIdList,
+id-IuTransportAssociation,
+id-JoinedMBMSBearerServicesList,
+id-KeyStatus,
+id-L3-Information,
+id-LAI,
+id-LastKnownServiceArea,
+id-LeftMBMSBearerServicesList,
+id-LocationRelatedDataRequestTypeSpecificToGERANIuMode,
+id-MBMSBearerServiceType,
+id-MBMSCountingInformation,
+id-MBMSCNDe-Registration,
+id-MBMSRegistrationRequestType,
+id-MBMSSynchronisationInformation,
+id-MBMSServiceArea,
+id-MBMSSessionDuration,
+id-MBMSSessionIdentity,
+id-MBMSSessionRepetitionNumber,
+id-MSISDN,
+id-NAS-PDU,
+id-NAS-SequenceNumber,
+id-NewBSS-To-OldBSS-Information,
+id-NonSearchingIndication,
+id-NumberOfSteps,
+id-Offload-RAB-Parameters,
+id-OMC-ID,
+id-OldBSS-ToNewBSS-Information,
+id-PagingAreaID,
+id-PagingCause,
+id-PDP-TypeInformation,
+id-PDP-TypeInformation-extension,
+id-PermanentNAS-UE-ID,
+id-PositionData,
+id-PositionDataSpecificToGERANIuMode,
+id-PositioningPriority,
+id-ProvidedData,
+id-RAB-ContextItem,
+id-RAB-ContextList,
+id-RAB-ContextFailedtoTransferItem,
+id-RAB-ContextFailedtoTransferList,
+id-RAB-ContextItem-RANAP-RelocInf,
+id-RAB-ContextList-RANAP-RelocInf,
+id-RAB-DataForwardingItem,
+id-RAB-DataForwardingItem-SRNS-CtxReq,
+id-RAB-DataForwardingList,
+id-RAB-DataForwardingList-SRNS-CtxReq,
+id-RAB-DataVolumeReportItem,
+id-RAB-DataVolumeReportList,
+id-RAB-DataVolumeReportRequestItem,
+id-RAB-DataVolumeReportRequestList,
+id-RAB-FailedItem,
+id-RAB-FailedList,
+id-RAB-FailedList-EnhRelocInfoRes,
+id-RAB-FailedItem-EnhRelocInfoRes,
+id-RAB-FailedtoReportItem,
+id-RAB-FailedtoReportList,
+id-RAB-ID,
+id-RAB-ModifyList,
+id-RAB-ModifyItem,
+id-RAB-Parameters,
+id-RAB-QueuedItem,
+id-RAB-QueuedList,
+id-RAB-ReleaseFailedList,
+id-RAB-ReleaseItem,
+id-RAB-ReleasedItem-IuRelComp,
+id-RAB-ReleaseList,
+id-RAB-ReleasedItem,
+id-RAB-ReleasedList,
+id-RAB-ReleasedList-IuRelComp,
+id-RAB-RelocationReleaseItem,
+id-RAB-RelocationReleaseList,
+id-RAB-SetupItem-RelocReq,
+id-RAB-SetupItem-RelocReqAck,
+id-RAB-SetupList-RelocReq,
+id-RAB-SetupList-RelocReqAck,
+id-RAB-SetupList-EnhRelocInfoReq,
+id-RAB-SetupItem-EnhRelocInfoReq,
+
+id-RAB-SetupList-EnhRelocInfoRes,
+id-RAB-SetupItem-EnhRelocInfoRes,
+id-RAB-SetupList-EnhancedRelocCompleteReq,
+id-RAB-SetupItem-EnhancedRelocCompleteReq,
+id-RAB-SetupList-EnhancedRelocCompleteRes,
+id-RAB-SetupItem-EnhancedRelocCompleteRes,
+id-RAB-SetupOrModifiedItem,
+id-RAB-SetupOrModifiedList,
+id-RAB-SetupOrModifyItem,
+id-RAB-SetupOrModifyList,
+id-RAB-ToBeReleasedItem-EnhancedRelocCompleteRes,
+id-RAB-ToBeReleasedList-EnhancedRelocCompleteRes,
+id-RAC,
+id-RAListofIdleModeUEs,
+id-RAT-Type,
+id-RedirectAttemptFlag,
+id-RedirectionCompleted,
+id-RedirectionIndication,
+id-RejectCauseValue,
+id-RelocationType,
+id-Relocation-SourceRNC-ID,
+id-Relocation-SourceExtendedRNC-ID,
+id-Relocation-TargetRNC-ID,
+id-Relocation-TargetExtendedRNC-ID,
+id-RequestedGANSSAssistanceData,
+id-RequestType,
+id-ResponseTime,
+id-RSRVCC-Operation-Possible,
+id-SAI,
+id-SAPI,
+id-SelectedPLMN-ID,
+id-SessionUpdateID,
+id-SNA-Access-Information,
+id-SourceBSS-ToTargetBSS-TransparentContainer,
+id-SourceRNC-ID,
+id-SourceExtendedRNC-ID,
+id-SourceID,
+id-Source-ToTarget-TransparentContainer,
+id-SourceRNC-PDCP-context-info,
+id-SRVCC-HO-Indication,
+id-SRVCC-Information,
+id-SRVCC-Operation-Possible,
+id-TargetBSS-ToSourceBSS-TransparentContainer,
+id-TargetID,
+id-Target-ToSource-TransparentContainer,
+id-TemporaryUE-ID,
+id-TimeToMBMSDataTransfer,
+id-TMGI,
+id-TracePropagationParameters,
+id-TraceReference,
+id-TraceType,
+id-TransportLayerAddress,
+id-TransportLayerInformation,
+id-TriggerID,
+id-UE-AggregateMaximumBitRate,
+id-UE-ID,
+id-UESBI-Iu,
+id-UL-GTP-PDU-SequenceNumber,
+id-UnsuccessfullLinkingList,
+id-VelocityEstimate,
+id-VerticalAccuracyCode,
+id-VoiceSupportMatchIndicator,
+id-PeriodicLocationInfo,
+id-BroadcastGANSSAssistanceDataDecipheringKeys,
+id-SubscriberProfileIDforRFP,
+id-E-UTRAN-Service-Handover,
+id-IP-Source-Address,
+id-LGW-TransportLayerAddress,
+id-Correlation-ID,
+id-MDT-Configuration,
+id-RNSAPRelocationParameters,
+id-RABParametersList,
+id-Priority-Class-Indicator,
+id-Management-Based-MDT-Allowed,
+id-HigherBitratesThan16MbpsFlag,
+id-Trace-Collection-Entity-IP-Address,
+id-End-Of-CSFB,
+id-Out-Of-UTRAN,
+
+```
+
+ id-RSRVCC-HO-Indication,
+ id-RSRVCC-Information,
+ id-AnchorPLMN-ID,
+ id-Management-Based-MDT-PLMN-List,
+ id-Tunnel-Information-for-BBF,
+ id-LastE-UTRANPLMNIdentity
+FROM RANAP-Constants;
+
+-- *****
+--
+-- Common Container Lists
+--
+-- *****
+
+RAB-IE-ContainerList { RANAP-PROTOCOL-IES : IEsSetParam } ::= ProtocolIE-
+ContainerList { 1, maxNrOfRABs, { IEsSetParam} }
+RAB-IE-ContainerPairList { RANAP-PROTOCOL-IES-PAIR : IEsSetParam } ::= ProtocolIE-
+ContainerPairList { 1, maxNrOfRABs, { IEsSetParam} }
+ProtocolError-IE-ContainerList { RANAP-PROTOCOL-IES : IEsSetParam } ::= ProtocolIE-
+ContainerList { 1, maxNrOfRABs, { IEsSetParam} }
+IuSigConId-IE-ContainerList { RANAP-PROTOCOL-IES : IEsSetParam } ::= ProtocolIE-
+ContainerList { 1, maxNrOfIuSigConIds, { IEsSetParam} }
+DirectTransfer-IE-ContainerList { RANAP-PROTOCOL-IES : IEsSetParam } ::= ProtocolIE-
+ContainerList { 1, maxNrOfDTs, { IEsSetParam} }
+
+-- *****
+--
+-- Iu RELEASE ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Iu Release Command
+--
+-- *****
+
+Iu-ReleaseCommand ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {Iu-ReleaseCommandIEs} },
+ protocolExtensions ProtocolExtensionContainer { {Iu-ReleaseCommandExtensions} }
+ OPTIONAL,
+ ...
+}
+
+Iu-ReleaseCommandIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+mandatory },
+ ...
+}
+
+Iu-ReleaseCommandExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-End-Of-CSFB CRITICALITY ignore EXTENSION End-Of-CSFB PRESENCE
+optional } |
+ { ID id-Out-Of-UTRAN CRITICALITY ignore EXTENSION Out-Of-UTRAN PRESENCE
+optional } |
+ { ID id-LastE-UTRANPLMNIdentity CRITICALITY ignore EXTENSION PLMNIdentity PRESENCE
+optional },
+ ...
+}
+
+-- *****
+--
+-- Iu Release Complete
+--
+-- *****
+
+Iu-ReleaseComplete ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {Iu-ReleaseCompleteIEs} },
+ protocolExtensions ProtocolExtensionContainer { {Iu-ReleaseCompleteExtensions} }
+ OPTIONAL,
+ ...
+}
+
+Iu-ReleaseCompleteIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataVolumeReportList CRITICALITY ignore TYPE RAB-DataVolumeReportList
+PRESENCE optional } |
+ { ID id-RAB-ReleasedList-IuRelComp CRITICALITY ignore TYPE RAB-ReleasedList-IuRelComp
+PRESENCE optional } |
+
+```
+
+```
+
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+ }
+
+ RAB-DataVolumeReportList ::= RAB-IE-ContainerList { {RAB-DataVolumeReportItemIEs} }
+
+ RAB-DataVolumeReportItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataVolumeReportItem CRITICALITY ignore TYPE RAB-DataVolumeReportItem
+ PRESENCE mandatory },
+ ...
+ }
+
+ RAB-DataVolumeReportItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ dl-UnsuccessfullyTransmittedDataVolume DataVolumeList OPTIONAL
+ -- This IE shall always be present although its presence is optional --,
+ iE-Extensions ProtocolExtensionContainer { {RAB-DataVolumeReportItem-ExtIEs} }
+ OPTIONAL,
+ ...
+ }
+
+ RAB-DataVolumeReportItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ RAB-ReleasedList-IuRelComp ::= RAB-IE-ContainerList { {RAB-ReleasedItem-IuRelComp-IEs} }
+ }
+
+ RAB-ReleasedItem-IuRelComp-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ReleasedItem-IuRelComp CRITICALITY ignore TYPE RAB-ReleasedItem-IuRelComp
+ PRESENCE mandatory },
+ ...
+ }
+
+ RAB-ReleasedItem-IuRelComp ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ dL-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL,
+ uL-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-ReleasedItem-IuRelComp-ExtIEs} }
+ OPTIONAL,
+ ...
+ }
+
+ RAB-ReleasedItem-IuRelComp-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ Iu-ReleaseCompleteExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ -- ***************************************************************************
+ --
+ -- RELOCATION PREPARATION ELEMENTARY PROCEDURE
+ --
+ -- ***************************************************************************
+
+ -- ***************************************************************************
+ --
+ -- Relocation Required
+ --
+ -- ***************************************************************************
+
+ RelocationRequired ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationRequiredIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationRequiredExtensions} }
+ OPTIONAL,
+ ...
+ }
+
+ RelocationRequiredIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RelocationType CRITICALITY reject TYPE RelocationType
+ PRESENCE mandatory } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory } |
+ }
+
+```
+
+```
+
+ { ID id-SourceID CRITICALITY ignore TYPE SourceID PRESENCE
+mandatory } |
+ { ID id-TargetID CRITICALITY reject TYPE TargetID PRESENCE
+mandatory } |
+ { ID id-ClassmarkInformation2 CRITICALITY reject TYPE ClassmarkInformation2
+ PRESENCE conditional
+ -- This IE shall be present if the Target ID IE contains a CGI IE and Source BSS To Target BSS
+Transparent Container is not included -- } |
+ { ID id-ClassmarkInformation3 CRITICALITY ignore TYPE ClassmarkInformation3
+ PRESENCE conditional
+ -- This IE shall be present if the Target ID IE contains a CGI IE and Source BSS To Target BSS
+Transparent Container is not included -- } |
+ { ID id-Source-ToTarget-TransparentContainer
+ CRITICALITY reject TYPE Source-ToTarget-TransparentContainer PRESENCE
+conditional
+ -- This IE shall be present if the Target ID IE contains a RNC-ID IE or eNB-ID --
+ } |
+ { ID id-OldBSS-ToNewBSS-Information CRITICALITY ignore TYPE OldBSS-ToNewBSS-Information
+ PRESENCE optional } ,
+ ...
+}
+
+RelocationRequiredExtensions RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 5 to enable GERAN support over Iu-cs --
+ { ID id-GERAN-Classmark CRITICALITY ignore EXTENSION GERAN-
+Classmark PRESENCE optional} |
+-- Extension for Release 6 to enable Inter-RAT PS Handover between UTRAN and GERAN A/Gb --
+ { ID id-SourceBSS-ToTargetBSS-TransparentContainer CRITICALITY ignore EXTENSION SourceBSS-
+ToTargetBSS-TransparentContainer PRESENCE optional} |
+-- Extension for Release 8 for SRVCC operation --
+ { ID id-SRVCC-HO-Indication CRITICALITY reject EXTENSION SRVCC-HO-
+Indication PRESENCE optional} |
+-- Extension for Release 9 to communicate to the CN the CSG id of the target cell --
+ { ID id-CSG-Id CRITICALITY reject EXTENSION CSG-Id
+ PRESENCE optional} |
+-- Extension for Release 9 to communicate to the CN the hybrid access status of the target cell --
+ { ID id-Cell-Access-Mode CRITICALITY reject EXTENSION Cell-Access-
+Mode PRESENCE optional} |
+-- Extension for Release 11 for rSRVCC operation --
+ { ID id-RSRVCC-HO-Indication CRITICALITY reject EXTENSION RSRVCC-HO-
+Indication PRESENCE optional},
+ ...
+}
+
+-- ***************************************************************************
+--
+-- Relocation Command
+--
+-- ***************************************************************************
+
+RelocationCommand ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationCommandIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationCommandExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationCommandIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Target-ToSource-TransparentContainer
+ CRITICALITY reject TYPE Target-ToSource-TransparentContainer PRESENCE
+optional } |
+ { ID id-L3-Information CRITICALITY ignore TYPE L3-Information PRESENCE
+optional } |
+ { ID id-RAB-RelocationReleaseList CRITICALITY ignore TYPE RAB-RelocationReleaseList
+ PRESENCE optional } |
+ { ID id-RAB-DataForwardingList CRITICALITY ignore TYPE RAB-DataForwardingList
+ PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+RAB-RelocationReleaseList ::= RAB-IE-ContainerList { {RAB-RelocationReleaseItemIEs} }
+
+RAB-RelocationReleaseItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-RelocationReleaseItem CRITICALITY ignore TYPE RAB-RelocationReleaseItem
+ PRESENCE mandatory },
+ ...
+}
+
+```
+
+```
+
+}
+
+RAB-RelocationReleaseItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ iE-Extensions ProtocolExtensionContainer { {RAB-RelocationReleaseItem-ExtIEs} }
+} OPTIONAL,
+...
+}
+
+RAB-RelocationReleaseItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-DataForwardingList ::= RAB-IE-ContainerList { {RAB-DataForwardingItemIEs} }
+
+RAB-DataForwardingItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataForwardingItem CRITICALITY ignore TYPE RAB-DataForwardingItem
+ PRESENCE mandatory },
+ ...
+}
+
+RAB-DataForwardingItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ transportLayerAddress TransportLayerAddress,
+ iuTransportAssociation IuTransportAssociation,
+ iE-Extensions ProtocolExtensionContainer { {RAB-DataForwardingItem-ExtIEs} }
+} OPTIONAL,
+...
+}
+
+RAB-DataForwardingItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to allow transfer of a second pair of TLA and association --
+ {ID id-TransportLayerAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE
+ optional} |
+ {ID id-IuTransportAssociation CRITICALITY ignore EXTENSION IuTransportAssociation
+ PRESENCE optional},
+ ...
+}
+
+RelocationCommandExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable Inter RAN Load Information Exchange over Iu --
+ { ID id-InterSystemInformation-TransparentContainer CRITICALITY ignore EXTENSION
+ InterSystemInformation-TransparentContainer PRESENCE optional} |
+ -- Extension for Release 6 to enable Inter-RAT PS Handover between UTRAN and GERAN A/Gb --
+ { ID id-TargetBSS-ToSourceBSS-TransparentContainer CRITICALITY ignore EXTENSION TargetBSS-
+ ToSourceBSS-TransparentContainer PRESENCE optional} |
+ -- Extension for Release 8 for SRVCC operation --
+ { ID id-SRVCC-Information CRITICALITY reject EXTENSION SRVCC-
+ Information PRESENCE optional} |
+ -- Extension for Release 11 for rSRVCC operation --
+ { ID id-RSRVCC-Information CRITICALITY reject EXTENSION RSRVCC-
+ Information PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- Relocation Preparation Failure
+--
+-- *****
+
+RelocationPreparationFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationPreparationFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationPreparationFailureExtensions} }
+} OPTIONAL,
+...
+}
+
+RelocationPreparationFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+RelocationPreparationFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable Inter RAN Load Information Exchange over Iu --
+
+```
+
+```
+
+ { ID id-InterSystemInformation-TransparentContainer CRITICALITY ignore EXTENSION
+ InterSystemInformation-TransparentContainer PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- RELOCATION RESOURCE ALLOCATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Relocation Request
+--
+-- *****
+
+RelocationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationRequestExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-PermanentNAS-UE-ID CRITICALITY ignore TYPE PermanentNAS-UE-ID
+ PRESENCE optional } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory } |
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator
+ PRESENCE mandatory } |
+ { ID id-Source-ToTarget-TransparentContainer
+ CRITICALITY reject TYPE SourceRNC-ToTargetRNC-TransparentContainer
+ PRESENCE mandatory } |
+ { ID id-RAB-SetupList-RelocReq CRITICALITY reject TYPE RAB-SetupList-RelocReq
+ PRESENCE optional } |
+ { ID id-IntegrityProtectionInformation CRITICALITY ignore TYPE
+ IntegrityProtectionInformation PRESENCE optional } |
+ { ID id-EncryptionInformation CRITICALITY ignore TYPE EncryptionInformation
+ PRESENCE optional } |
+ { ID id-IuSigConId CRITICALITY ignore TYPE IuSignallingConnectionIdentifier PRESENCE mandatory
+},
+ ...
+}
+
+RAB-SetupList-RelocReq ::= RAB-IE-ContainerList { {RAB-SetupItem-RelocReq-IEs} }
+
+RAB-SetupItem-RelocReq-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupItem-RelocReq CRITICALITY reject TYPE RAB-SetupItem-RelocReq
+ PRESENCE mandatory },
+ ...
+}
+
+RAB-SetupItem-RelocReq ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ nAS-SynchronisationIndicator NAS-SynchronisationIndicator OPTIONAL,
+ rAB-Parameters RAB-Parameters,
+ dataVolumeReportingIndication DataVolumeReportingIndication OPTIONAL
+ -- This IE shall be present if the CN domain indicator IE is set to "PS domain" --,
+ pDP-TypeInformation PDP-TypeInformation OPTIONAL
+ -- This IE shall be present if the CN domain indicator IE is set to "PS domain" --,
+ userPlaneInformation UserPlaneInformation,
+ transportLayerAddress TransportLayerAddress,
+ iuTransportAssociation IuTransportAssociation,
+ service-Handover Service-Handover OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-SetupItem-RelocReq-ExtIEs} }
+ OPTIONAL,
+ ...
+}
+
+RAB-SetupItem-RelocReq-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 to enable RAB Quality of Service negotiation over Iu --
+ { ID id-Alt-RAB-Parameters CRITICALITY ignore EXTENSION Alt-RAB-Parameters
+ PRESENCE optional} |
+ -- Extension for Release 5 to enable GERAN support over Iu-cs --
+ { ID id-GERAN-BSC-Container CRITICALITY ignore EXTENSION GERAN-BSC-Container
+ PRESENCE optional} |
+ -- Extension for Release 8 to enable handover restriction to E-UTRAN --
+
+```
+
+```
+
+ { ID id-E-UTRAN-Service-Handover CRITICALITY ignore EXTENSION E-UTRAN-Service-
+Handover PRESENCE optional}|
+-- Extension for Release 9 to enable a new value --
+ { ID id-PDP-TypeInformation-extension CRITICALITY ignore EXTENSION PDP-TypeInformation-
+extension PRESENCE optional}|
+-- Extension for Release 10 to enable offload at Iu-PS for UTRAN --
+ { ID id-Offload-RAB-Parameters CRITICALITY ignore EXTENSION Offload-RAB-Parameters
+ PRESENCE optional},
+ ...
+}
+
+UserPlaneInformation ::= SEQUENCE {
+ userPlaneMode UserPlaneMode,
+ uP-ModeVersions UP-ModeVersions,
+ iE-Extensions ProtocolExtensionContainer { {UserPlaneInformation-ExtIEs} }
+ OPTIONAL,
+ ...
+}
+
+UserPlaneInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RelocationRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 4 --
+ { ID id-GlobalCN-ID CRITICALITY reject EXTENSION GlobalCN-ID
+ PRESENCE optional}|
+-- Extension for Release 5 to enable shared networks in connected mode --
+ { ID id-SNA-Access-Information CRITICALITY ignore EXTENSION SNA-Access-Information
+ PRESENCE optional}|
+-- Extension for Release 5 to enable specific behaviour by the RNC in relation with early UE
+handling --
+ { ID id-UESBI-Iu CRITICALITY ignore EXTENSION UESBI-Iu
+ PRESENCE optional}|
+-- Extension for Release 6 to convey the selected PLMN id in network sharing mobility scenarios --
+ { ID id-SelectedPLMN-ID CRITICALITY ignore EXTENSION PLMNIdentity
+ PRESENCE optional}|
+-- Extension for Release 6 to enable MBMS UE linking at relocation --
+ { ID id-CNMBMSLinkingInformation CRITICALITY ignore EXTENSION CNMBMSLinkingInformation
+ PRESENCE optional}|
+ { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate
+ PRESENCE optional}|
+-- Extension for Release 9 to communicate to the target cell the CSG id reported by the source --
+ { ID id-CSG-Id CRITICALITY reject EXTENSION CSG-Id
+ PRESENCE optional}|
+-- Extension for Release 9 for enabling UE prioritisation during access to hybrid cells --
+ { ID id-CSG-Membership-Status CRITICALITY ignore EXTENSION CSG-Membership-Status
+ PRESENCE optional}|
+-- Extension for Release 10 to enable offload at Iu-PS for UTRAN --
+ { ID id-MSISDN CRITICALITY ignore EXTENSION MSISDN
+ PRESENCE optional}|
+-- Extension for Release 11 to support rSRVCC in case of network sharing --
+ { ID id-AnchorPLMN-ID CRITICALITY ignore EXTENSION PLMNIdentity
+ PRESENCE optional},
+ ...
+}
+
+CNMBMSLinkingInformation ::= SEQUENCE {
+ joinedMBMSBearerService-IEs JoinedMBMSBearerService-IEs,
+ iE-Extensions ProtocolExtensionContainer { {CNMBMSLinkingInformation-ExtIEs} }
+ OPTIONAL,
+ ...
+}
+
+CNMBMSLinkingInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+JoinedMBMSBearerService-IEs ::= SEQUENCE (SIZE (1.. maxnoofMulticastServicesPerUE)) OF
+SEQUENCE {
+ tMGI TMGI,
+ mBMS-PTP-RAB-ID MBMS-PTP-RAB-ID,
+ iE-Extensions ProtocolExtensionContainer { {JoinedMBMSBearerService-ExtIEs} }
+OPTIONAL,
+ ...
+}
+
+JoinedMBMSBearerService-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+
+```
+
+```
+
+ ...
+ }
+
+ -- *****
+ --
+ -- Relocation Request Acknowledge
+ --
+ -- *****
+
+ RelocationRequestAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationRequestAcknowledgeIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationRequestAcknowledgeExtensions} }
+ OPTIONAL,
+ ...
+ }
+
+ RelocationRequestAcknowledgeIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Target-ToSource-TransparentContainer
+ CRITICALITY ignore TYPE TargetRNC-ToSourceRNC-TransparentContainer
+ PRESENCE optional } |
+ { ID id-RAB-SetupList-RelocReqAck CRITICALITY ignore TYPE RAB-SetupList-RelocReqAck
+ PRESENCE optional } |
+ { ID id-RAB-FailedList CRITICALITY ignore TYPE RAB-FailedList PRESENCE
+ optional } |
+ { ID id-ChosenIntegrityProtectionAlgorithm CRITICALITY ignore TYPE
+ ChosenIntegrityProtectionAlgorithm PRESENCE optional } |
+ { ID id-ChosenEncryptionAlgorithm CRITICALITY ignore TYPE ChosenEncryptionAlgorithm
+ PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+ }
+
+ RAB-SetupList-RelocReqAck ::= RAB-IE-ContainerList { {RAB-SetupItem-RelocReqAck-IEs} }
+
+ RAB-SetupItem-RelocReqAck-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupItem-RelocReqAck CRITICALITY reject TYPE RAB-SetupItem-RelocReqAck
+ PRESENCE mandatory },
+ ...
+ }
+
+ RAB-SetupItem-RelocReqAck ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ transportLayerAddress TransportLayerAddress OPTIONAL,
+ iuTransportAssociation IuTransportAssociation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-SetupItem-RelocReqAck-ExtIEs} }
+ OPTIONAL,
+ ...
+ }
+
+ RAB-SetupItem-RelocReqAck-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 to enable RAB Quality of Service negotiation over Iu --
+ {ID id-Ass-RAB-Parameters CRITICALITY ignore EXTENSION Ass-RAB-Parameters PRESENCE
+ optional } |
+ -- Extension for Release 5 to allow transfer of a second pair of TLA and association --
+ {ID id-TransportLayerAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE
+ optional } |
+ {ID id-IuTransportAssociation CRITICALITY ignore EXTENSION IuTransportAssociation PRESENCE
+ optional},
+ ...
+ }
+
+ RAB-FailedList ::= RAB-IE-ContainerList { {RAB-FailedItemIEs} }
+
+ RAB-FailedItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-FailedItem CRITICALITY ignore TYPE RAB-FailedItem PRESENCE
+ mandatory },
+ ...
+ }
+
+ RAB-FailedItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { {RAB-FailedItem-ExtIEs} }
+ OPTIONAL,
+ ...
+ }
+
+```
+
+```
+
+RAB-FailedItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RelocationRequestAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable Inter RAN Load Information Exchange over Iu --
+ { ID id-NewBSS-To-OldBSS-Information CRITICALITY ignore EXTENSION NewBSS-To-OldBSS-Information
+ PRESENCE optional } |
+ { ID id-CSG-Id CRITICALITY ignore EXTENSION CSG-Id
+ PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- Relocation Failure
+--
+-- *****
+
+RelocationFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationFailureExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+RelocationFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable Inter RAN Load Information Exchange over Iu --
+ { ID id-NewBSS-To-OldBSS-Information CRITICALITY ignore EXTENSION NewBSS-To-OldBSS-
+ Information PRESENCE optional } |
+ -- Extension for Release 5 to enable GERAN support over Iu-cs --
+ { ID id-GERAN-Classmark CRITICALITY ignore EXTENSION GERAN-Classmark
+ PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- RELOCATION CANCEL ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Relocation Cancel
+--
+-- *****
+
+RelocationCancel ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationCancelIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationCancelExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationCancelIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory },
+ ...
+}
+
+RelocationCancelExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- Relocation Cancel Acknowledge
+--
+-- *****
+
+```
+
+```
+
+RelocationCancelAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationCancelAcknowledgeIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationCancelAcknowledgeExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationCancelAcknowledgeIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+RelocationCancelAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- SRNS CONTEXT TRANSFER OPERATION
+--
+-- *****
+--
+-- *****
+--
+-- SRNS Context Request
+--
+-- *****
+
+SRNS-ContextRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SRNS-ContextRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {SRNS-ContextRequestExtensions} }
+ OPTIONAL,
+ ...
+}
+
+SRNS-ContextRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataForwardingList-SRNS-CtxReq CRITICALITY ignore TYPE RAB-DataForwardingList-
+ SRNS-CtxReq PRESENCE mandatory },
+ ...
+}
+
+RAB-DataForwardingList-SRNS-CtxReq ::= RAB-IE-ContainerList { {RAB-DataForwardingItem-SRNS-
+ CtxReq-IEs} }
+
+RAB-DataForwardingItem-SRNS-CtxReq-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataForwardingItem-SRNS-CtxReq CRITICALITY reject TYPE RAB-DataForwardingItem-
+ SRNS-CtxReq PRESENCE mandatory },
+ ...
+}
+
+RAB-DataForwardingItem-SRNS-CtxReq ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ iE-Extensions ProtocolExtensionContainer { {RAB-DataForwardingItem-SRNS-
+ CtxReq-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-DataForwardingItem-SRNS-CtxReq-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SRNS-ContextRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- The SGSN may include the IE, when available to indicate the RAT from which the context request
+ originates, to correct measurement points in SRNC. --
+ {ID id-RAT-Type CRITICALITY ignore EXTENSION RAT-Type PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- SRNS Context Response
+--
+-- *****
+
+SRNS-ContextResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SRNS-ContextResponseIEs} },
+
+```
+
+```
+
+ protocolExtensions ProtocolExtensionContainer { {SRNS-ContextResponseExtensions} }
+ OPTIONAL,
+ ...
+}
+
+SRNS-ContextResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ContextList CRITICALITY ignore TYPE RAB-ContextList
+ PRESENCE optional } |
+ { ID id-RAB-ContextFailedtoTransferList CRITICALITY ignore TYPE RAB-
+ ContextFailedtoTransferList PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+RAB-ContextList ::= RAB-IE-ContainerList { {RAB-ContextItemIEs} }
+
+RAB-ContextItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ContextItem CRITICALITY ignore TYPE RAB-ContextItem
+ PRESENCE mandatory },
+ ...
+}
+
+RAB-ContextItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ dl-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL,
+ ul-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL,
+ dl-N-PDU-SequenceNumber DL-N-PDU-SequenceNumber OPTIONAL,
+ ul-N-PDU-SequenceNumber UL-N-PDU-SequenceNumber OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-ContextItem-ExtIEs} }
+ OPTIONAL,
+ ...
+}
+
+RAB-ContextItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-ContextFailedtoTransferList ::= RAB-IE-ContainerList { {RABs-
+ ContextFailedtoTransferItemIEs} }
+
+RABs-ContextFailedtoTransferItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ContextFailedtoTransferItem CRITICALITY ignore TYPE RABs-
+ ContextFailedtoTransferItem PRESENCE mandatory },
+ ...
+}
+
+RABs-ContextFailedtoTransferItem::= SEQUENCE {
+ rAB-ID RAB-ID,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { RABs-ContextFailedtoTransferItem-
+ ExtIEs} } OPTIONAL,
+ ...
+}
+
+RABs-ContextFailedtoTransferItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SRNS-ContextResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- SECURITY MODE CONTROL ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Security Mode Command
+--
+-- *****
+
+SecurityModeCommand ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SecurityModeCommandIEs} },
+
+```
+
+```
+
+ protocolExtensions ProtocolExtensionContainer { {SecurityModeCommandExtensions} }
+ OPTIONAL,
+ ...
+ }
+
+ SecurityModeCommandIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-IntegrityProtectionInformation CRITICALITY reject TYPE
+ IntegrityProtectionInformation PRESENCE mandatory } |
+ { ID id-EncryptionInformation CRITICALITY ignore TYPE EncryptionInformation
+ PRESENCE optional } |
+ { ID id-KeyStatus CRITICALITY reject TYPE KeyStatus
+ PRESENCE mandatory},
+ ...
+ }
+
+ SecurityModeCommandExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ -- *****
+ --
+ -- Security Mode Complete
+ --
+ -- *****
+
+ SecurityModeComplete ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SecurityModeCompleteIEs} },
+ protocolExtensions ProtocolExtensionContainer { {SecurityModeCompleteExtensions} }
+ OPTIONAL,
+ ...
+ }
+
+ SecurityModeCompleteIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-ChosenIntegrityProtectionAlgorithm CRITICALITY reject TYPE
+ ChosenIntegrityProtectionAlgorithm PRESENCE mandatory } |
+ { ID id-ChosenEncryptionAlgorithm CRITICALITY ignore TYPE ChosenEncryptionAlgorithm
+ PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+ }
+
+ SecurityModeCompleteExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ -- *****
+ --
+ -- Security Mode Reject
+ --
+ -- *****
+
+ SecurityModeReject ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SecurityModeRejectIEs} },
+ protocolExtensions ProtocolExtensionContainer { {SecurityModeRejectExtensions} }
+ OPTIONAL,
+ ...
+ }
+
+ SecurityModeRejectIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+ }
+
+ SecurityModeRejectExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ -- *****
+ --
+ -- DATA VOLUME REPORT ELEMENTARY PROCEDURE
+ --
+ -- *****
+ -- *****
+
+```
+
+```
+
+--
+-- Data Volume Report Request
+--
+-- *****
+
+DataVolumeReportRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {DataVolumeReportRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {DataVolumeReportRequestExtensions} }
+ OPTIONAL,
+ ...
+}
+
+DataVolumeReportRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataVolumeReportRequestList CRITICALITY ignore TYPE RAB-
+ DataVolumeReportRequestList PRESENCE mandatory },
+ ...
+}
+
+RAB-DataVolumeReportRequestList ::= RAB-IE-ContainerList { {RAB-
+DataVolumeReportRequestItemIEs} }
+
+RAB-DataVolumeReportRequestItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataVolumeReportRequestItem CRITICALITY reject TYPE RAB-
+ DataVolumeReportRequestItem PRESENCE mandatory },
+ ...
+}
+
+RAB-DataVolumeReportRequestItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ iE-Extensions ProtocolExtensionContainer { {RAB-DataVolumeReportRequestItem-
+ ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-DataVolumeReportRequestItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DataVolumeReportRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- Data Volume Report
+--
+-- *****
+
+DataVolumeReport ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {DataVolumeReportIEs} },
+ protocolExtensions ProtocolExtensionContainer { {DataVolumeReportExtensions} }
+ OPTIONAL,
+ ...
+}
+
+DataVolumeReportIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataVolumeReportList CRITICALITY ignore TYPE RAB-DataVolumeReportList
+ PRESENCE optional } |
+ { ID id-RAB-FailedtoReportList CRITICALITY ignore TYPE RAB-FailedtoReportList
+ PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+DataVolumeReportExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-FailedtoReportList ::= RAB-IE-ContainerList { {RABs-failed-to-reportItemIEs} }
+
+RABs-failed-to-reportItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-FailedtoReportItem CRITICALITY ignore TYPE RABs-failed-to-reportItem
+ PRESENCE mandatory },
+ ...
+}
+
+RABs-failed-to-reportItem ::= SEQUENCE {
+
+```
+
+```
+
+ rAB-ID RAB-ID,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { RABs-failed-to-reportItem-ExtIEs} }
+ OPTIONAL,
+ ...
+ }
+
+RABs-failed-to-reportItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****************************************************************
+--
+-- RESET ELEMENTARY PROCEDURE
+--
+-- *****************************************************************
+
+-- *****************************************************************
+--
+-- Reset
+--
+-- *****************************************************************
+
+Reset ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ResetIEs} },
+ protocolExtensions ProtocolExtensionContainer { {ResetExtensions} }
+ OPTIONAL,
+ ...
+}
+
+ResetIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+mandatory } |
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator
+ PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE
+optional },
+ ...
+}
+
+ResetExtensions RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 4 --
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID
+ PRESENCE optional } |
+-- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE
+optional },
+ ...
+}
+
+-- *****************************************************************
+--
+-- Reset Acknowledge
+--
+-- *****************************************************************
+
+ResetAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ResetAcknowledgeIEs} },
+ protocolExtensions ProtocolExtensionContainer { {ResetAcknowledgeExtensions} }
+ OPTIONAL,
+ ...
+}
+
+ResetAcknowledgeIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator
+ PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE
+optional },
+ ...
+}
+
+ResetAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 4 --
+
+```
+
+```
+
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID
+ PRESENCE optional } |
+-- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE
+ optional },
+ ...
+ }
+-- *****
+--
+-- RESET RESOURCE ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Reset Resource
+--
+-- *****
+
+ResetResource ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ResetResourceIEs} },
+ protocolExtensions ProtocolExtensionContainer { {ResetResourceExtensions} }
+ OPTIONAL,
+ ...
+}
+
+ResetResourceIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator
+ PRESENCE mandatory } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+ mandatory } |
+ { ID id-IuSigConIdList CRITICALITY ignore TYPE ResetResourceList
+ PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE
+ optional },
+ ...
+}
+
+ResetResourceList ::= IuSigConId-IE-ContainerList{ {ResetResourceItemIEs} }
+
+ResetResourceItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-IuSigConIdItem CRITICALITY reject TYPE ResetResourceItem
+ PRESENCE mandatory },
+ ...
+}
+
+ResetResourceItem ::= SEQUENCE {
+ iuSigConId IuSignallingConnectionIdentifier,
+ iE-Extensions ProtocolExtensionContainer { { ResetResourceItem-ExtIEs} }
+ OPTIONAL,
+ ...
+}
+
+ResetResourceItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ResetResourceExtensions RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 4 --
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID
+ PRESENCE optional } |
+-- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID
+ PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- Reset Resource Acknowledge
+--
+-- *****
+
+ResetResourceAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ResetResourceAcknowledgeIEs} },
+ protocolExtensions ProtocolExtensionContainer { {ResetResourceAcknowledgeExtensions} }
+ OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ ...
+ }
+
+ ResetResourceAcknowledgeIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator
+ PRESENCE mandatory } |
+ { ID id-IuSigConIdList CRITICALITY ignore TYPE ResetResourceAckList
+ PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE
+ optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+ }
+
+ ResetResourceAckList ::= IuSigConId-IE-ContainerList { {ResetResourceAckItemIEs} }
+
+ ResetResourceAckItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-IuSigConIdItem CRITICALITY reject TYPE ResetResourceAckItem
+ PRESENCE mandatory },
+ ...
+ }
+
+ ResetResourceAckItem ::= SEQUENCE {
+ iuSigConId IuSignallingConnectionIdentifier,
+ iE-Extensions ProtocolExtensionContainer { { ResetResourceAckItem-ExtIEs} }
+ OPTIONAL,
+ ...
+ }
+
+ ResetResourceAckItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ ResetResourceAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 --
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID
+ PRESENCE optional } |
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE
+ optional },
+ ...
+ }
+
+ -- *****
+ --
+ -- RAB RELEASE REQUEST ELEMENTARY PROCEDURE
+ --
+ -- *****
+
+ -- *****
+ --
+ -- RAB Release Request
+ --
+ -- *****
+
+ RAB-ReleaseRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RAB-ReleaseRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RAB-ReleaseRequestExtensions} }
+ OPTIONAL,
+ ...
+ }
+
+ RAB-ReleaseRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ReleaseList CRITICALITY ignore TYPE RAB-ReleaseList
+ PRESENCE mandatory },
+ ...
+ }
+
+ RAB-ReleaseList ::= RAB-IE-ContainerList { {RAB-ReleaseItemIEs} }
+
+ RAB-ReleaseItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ReleaseItem CRITICALITY ignore TYPE RAB-ReleaseItem
+ PRESENCE mandatory },
+ ...
+ }
+
+ RAB-ReleaseItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+
+```
+
+```
+
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { {RAB-ReleaseItem-ExtIEs} }
+ OPTIONAL,
+ ...
+}
+
+RAB-ReleaseItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-ReleaseRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- ****************************************************************************
+--
+-- Iu RELEASE REQUEST ELEMENTARY PROCEDURE
+--
+-- ****************************************************************************
+
+-- ****************************************************************************
+--
+-- Iu Release Request
+--
+-- ****************************************************************************
+
+Iu-ReleaseRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {Iu-ReleaseRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {Iu-ReleaseRequestExtensions} }
+ OPTIONAL,
+ ...
+}
+
+Iu-ReleaseRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+mandatory },
+ ...
+}
+
+Iu-ReleaseRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- ****************************************************************************
+--
+-- RELOCATION DETECT ELEMENTARY PROCEDURE
+--
+-- ****************************************************************************
+
+-- ****************************************************************************
+--
+-- Relocation Detect
+--
+-- ****************************************************************************
+
+RelocationDetect ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationDetectIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationDetectExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationDetectIEs RANAP-PROTOCOL-IES ::= {
+ ...
+}
+
+RelocationDetectExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- ****************************************************************************
+--
+-- RELOCATION COMPLETE ELEMENTARY PROCEDURE
+--
+-- ****************************************************************************
+
+-- ****************************************************************************
+--
+```
+
+```
+
+-- Relocation Complete
+--
+-- ****************************************************************************
+
+RelocationComplete ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RelocationCompleteIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RelocationCompleteExtensions} }
+ OPTIONAL,
+ ...
+}
+
+RelocationCompleteIEs RANAP-PROTOCOL-IES ::= {
+ ...
+}
+
+RelocationCompleteExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 9 to enable the CN to handle potential UE NAS QoS issues related to higher
+bitrates --
+ { ID id-HigherBitratesThan16MbpsFlag CRITICALITY ignore EXTENSION
+HigherBitratesThan16MbpsFlag PRESENCE optional} |
+ -- Extension for Release 11 to support BBAI --
+ { ID id-Tunnel-Information-for-BBF CRITICALITY ignore EXTENSION TunnelInformation
+ PRESENCE optional},
+ ...
+}
+
+-- ****************************************************************************
+--
+-- ENHANCED RELOCATION COMPLETE ELEMENTARY PROCEDURE
+--
+-- ****************************************************************************
+
+-- ****************************************************************************
+--
+-- Enhanced Relocation Complete Request
+--
+-- ****************************************************************************
+
+EnhancedRelocationCompleteRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {EnhancedRelocationCompleteRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {EnhancedRelocationCompleteRequestExtensions} }
+ OPTIONAL,
+ ...
+}
+
+EnhancedRelocationCompleteRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-OldIuSigConId CRITICALITY reject TYPE IuSignallingConnectionIdentifier PRESENCE
+mandatory } |
+ { ID id-IuSigConId CRITICALITY reject TYPE IuSignallingConnectionIdentifier PRESENCE
+mandatory } |
+ { ID id-Relocation-SourceRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID
+ PRESENCE mandatory } |
+ { ID id-Relocation-SourceExtendedRNC-ID CRITICALITY ignore TYPE ExtendedRNC-ID
+ PRESENCE optional } |
+ { ID id-Relocation-TargetRNC-ID CRITICALITY reject TYPE GlobalRNC-ID
+ PRESENCE mandatory } |
+ { ID id-Relocation-TargetExtendedRNC-ID CRITICALITY reject TYPE ExtendedRNC-ID
+ PRESENCE optional } |
+ { ID id-RAB-SetupList-EnhancedRelocCompleteReq CRITICALITY reject TYPE RAB-SetupList-
+EnhancedRelocCompleteReq PRESENCE optional }
+ , ...
+}
+
+RAB-SetupList-EnhancedRelocCompleteReq ::= RAB-IE-ContainerList { { RAB-SetupItem-
+EnhancedRelocCompleteReq-IEs} }
+
+RAB-SetupItem-EnhancedRelocCompleteReq-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupItem-EnhancedRelocCompleteReq CRITICALITY reject TYPE RAB-SetupItem-
+EnhancedRelocCompleteReq PRESENCE mandatory },
+ ...
+}
+
+RAB-SetupItem-EnhancedRelocCompleteReq ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ transportLayerAddressReq1 TransportLayerAddress OPTIONAL,
+ iuTransportAssociationReq1 IuTransportAssociation OPTIONAL,
+ ass-RAB-Parameters Ass-RAB-Parameters OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ iE-Extensions ProtocolExtensionContainer { { RAB-SetupItem-
+EnhancedRelocCompleteReq-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-SetupItem-EnhancedRelocCompleteReq-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+EnhancedRelocationCompleteRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ChosenIntegrityProtectionAlgorithm CRITICALITY ignore EXTENSION
+ChosenIntegrityProtectionAlgorithm PRESENCE optional}|
+ { ID id-ChosenEncryptionAlgorithm CRITICALITY ignore EXTENSION
+ChosenEncryptionAlgorithm PRESENCE optional}|
+-- Extension for Release 9 to enable the CN to handle potential UE NAS QoS issues related to higher
+bitrates --
+ { ID id-HigherBitratesThan16MbpsFlag CRITICALITY ignore EXTENSION
+HigherBitratesThan16MbpsFlag PRESENCE optional}|
+-- Extensions for Release 11 to enable enhanced relocation from RNC to hybrid cell -
+ { ID id-CSG-Id CRITICALITY reject EXTENSION CSG-Id
+ PRESENCE optional}|
+ { ID id-Cell-Access-Mode CRITICALITY reject EXTENSION Cell-Access-Mode
+ PRESENCE optional}|
+-- Extension for Release 11 to support BBAI --
+ { ID id-Tunnel-Information-for-BBF CRITICALITY ignore EXTENSION TunnelInformation
+ PRESENCE optional},
+ ...
+}
+
+-- ****************************************************************************
+--
+-- Enhanced Relocation Complete Response
+--
+-- ****************************************************************************
+
+EnhancedRelocationCompleteResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {EnhancedRelocationCompleteResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer {
+{EnhancedRelocationCompleteResponseExtensions} } OPTIONAL,
+ ...
+}
+
+EnhancedRelocationCompleteResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupList-EnhancedRelocCompleteRes CRITICALITY ignore TYPE RAB-SetupList-
+EnhancedRelocCompleteRes PRESENCE optional} |
+ { ID id-RAB-ToBeReleasedList-EnhancedRelocCompleteRes CRITICALITY ignore TYPE RAB-
+ToBeReleasedList-EnhancedRelocCompleteRes PRESENCE optional} |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+RAB-SetupList-EnhancedRelocCompleteRes ::= RAB-IE-ContainerList { {RAB-SetupItem-
+EnhancedRelocCompleteRes-IEs} }
+
+RAB-SetupItem-EnhancedRelocCompleteRes-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupItem-EnhancedRelocCompleteRes CRITICALITY reject TYPE RAB-SetupItem-
+EnhancedRelocCompleteRes PRESENCE mandatory },
+ ...
+}
+
+RAB-SetupItem-EnhancedRelocCompleteRes ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ rAB-Parameters RAB-Parameters OPTIONAL,
+ userPlaneInformation UserPlaneInformation,
+ transportLayerAddressRes1 TransportLayerAddress OPTIONAL,
+ iuTransportAssociationRes1 IuTransportAssociation OPTIONAL,
+ rab2beReleasedList RAB-ToBeReleasedList-EnhancedRelocCompleteRes OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { RAB-SetupItem-
+EnhancedRelocCompleteRes-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-SetupItem-EnhancedRelocCompleteRes-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 10 to enable Offload at Iu-ps for UTRAN --
+ { ID id-Offload-RAB-Parameters CRITICALITY ignore EXTENSION Offload-RAB-Parameters
+ PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+}
+
+RAB-ToBeReleasedList-EnhancedRelocCompleteRes ::= RAB-IE-ContainerList { {RAB-ToBeReleasedItem-
+EnhancedRelocCompleteRes-IEs} }
+
+RAB-ToBeReleasedItem-EnhancedRelocCompleteRes-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ToBeReleasedItem-EnhancedRelocCompleteRes CRITICALITY ignore TYPE RAB-
+ToBeReleasedItem-EnhancedRelocCompleteRes PRESENCE mandatory },
+ ...
+}
+
+RAB-ToBeReleasedItem-EnhancedRelocCompleteRes ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { RAB-ToBeReleasedItem-
+EnhancedRelocCompleteRes-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-ToBeReleasedItem-EnhancedRelocCompleteRes-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+EnhancedRelocationCompleteResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate
+ PRESENCE optional}|
+ -- Extension for Release 10 to enable Offload at Iu-ps for UTRAN --
+ { ID id-MSISDN CRITICALITY ignore EXTENSION MSISDN
+ PRESENCE optional}|
+ -- Extension for Release 11 to enable enhanced relocation from RNC to hybrid cell -
+ { ID id-CSG-Membership-Status CRITICALITY ignore EXTENSION CSG-Membership-Status
+ PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- Enhanced Relocation Complete Failure
+--
+-- *****
+
+EnhancedRelocationCompleteFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {EnhancedRelocationCompleteFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer {
+{EnhancedRelocationCompleteFailureExtensions} } OPTIONAL,
+ ...
+}
+
+EnhancedRelocationCompleteFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE
+mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics
+ PRESENCE optional },
+ ...
+}
+
+EnhancedRelocationCompleteFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- Enhanced Relocation Complete Confirm
+--
+-- *****
+
+EnhancedRelocationCompleteConfirm ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {EnhancedRelocationCompleteConfirmIEs} },
+ protocolExtensions ProtocolExtensionContainer {
+{EnhancedRelocationCompleteConfirmExtensions} } OPTIONAL,
+ ...
+}
+
+EnhancedRelocationCompleteConfirmIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-FailedList CRITICALITY ignore TYPE RAB-FailedList PRESENCE
+optional },
+ ...
+}
+
+```
+
+```
+EnhancedRelocationCompleteConfirmExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+-- *****
+--
+-- PAGING ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Paging
+--
+-- *****
+```
+
+```
+Paging ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {PagingIEs} },
+ protocolExtensions ProtocolExtensionContainer { {PagingExtensions} }
+ OPTIONAL,
+ ...
+}
+```
+
+```
+PagingIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator
+ PRESENCE mandatory } |
+ { ID id-PermanentNAS-UE-ID CRITICALITY ignore TYPE PermanentNAS-UE-ID
+ PRESENCE mandatory } |
+ { ID id-TemporaryUE-ID CRITICALITY ignore TYPE TemporaryUE-ID
+ PRESENCE optional } |
+ { ID id-PagingAreaID CRITICALITY ignore TYPE PagingAreaID
+ PRESENCE optional } |
+ { ID id-PagingCause CRITICALITY ignore TYPE PagingCause
+ PRESENCE optional } |
+ { ID id-NonSearchingIndication CRITICALITY ignore TYPE NonSearchingIndication
+ PRESENCE optional } |
+ { ID id-DRX-CycleLengthCoefficient CRITICALITY ignore TYPE DRX-CycleLengthCoefficient
+ PRESENCE optional } ,
+ ...
+}
+```
+
+```
+PagingExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable NNSF --
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID PRESENCE
+ optional } |
+ -- Extension for Release 8 to support CSG --
+ { ID id-CSG-Id-List CRITICALITY ignore EXTENSION CSG-Id-List PRESENCE
+ optional },
+ ...
+}
+```
+
+```
+-- *****
+--
+-- COMMON ID ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Common ID
+--
+-- *****
+```
+
+```
+CommonID ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {CommonID-IEs} },
+ protocolExtensions ProtocolExtensionContainer { {CommonIDExtensions} }
+ OPTIONAL,
+ ...
+}
+```
+
+```
+CommonID-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-PermanentNAS-UE-ID CRITICALITY ignore TYPE PermanentNAS-UE-ID
+ PRESENCE mandatory },
+ ...
+}
+```
+
+```
+
+CommonIDExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable shared networks in connected mode --
+ { ID id-SNA-Access-Information CRITICALITY ignore EXTENSION SNA-Access-Information
+ PRESENCE optional }|
+ -- Extension for Release 5 to enable specific behaviour by the RNC in relation with early UE
+ handling --
+ { ID id-UESBI-Iu CRITICALITY ignore EXTENSION UESBI-Iu
+ PRESENCE optional }|
+ -- Extension for Release 6 to indicate the selected plmn in GWCN configuration for network sharing
+ non-supporting UEs --
+ { ID id-SelectedPLMN-ID CRITICALITY ignore EXTENSION PLMNIdentity
+ PRESENCE optional }|
+ -- Extension for Release 8 to indicate the Subscriber Profile ID for RAT/Frequency Selection
+ Priority --
+ { ID id-SubscriberProfileIDforRFP CRITICALITY ignore EXTENSION SubscriberProfileIDforRFP
+ PRESENCE optional }|
+ -- Extension for Release 8 for SRVCC operation --
+ { ID id-SRVCC-Operation-Possible CRITICALITY ignore EXTENSION SRVCC-Operation-Possible
+ PRESENCE optional }|
+ -- Extension for Release 9 to allow for UE prioritisation during access to hybrid cells --
+ { ID id-CSG-Membership-Status CRITICALITY ignore EXTENSION CSG-Membership-Status
+ PRESENCE optional }|
+ -- Extension for Release 10 to indicate Management Based MDT Allowed --
+ { ID id-Management-Based-MDT-Allowed CRITICALITY ignore EXTENSION Management-Based-MDT-
+ Allowed PRESENCE optional }|
+ -- Extension for Release 11 to indicate MDT PLMN List --
+ { ID id-Management-Based-MDT-PLMN-List CRITICALITY ignore EXTENSION MDT-PLMN-List
+ PRESENCE optional }|
+ -- Extension for Release 11 rSRVCC operation --
+ { ID id-RSRVCC-Operation-Possible CRITICALITY ignore EXTENSION RSRVCC-Operation-Possible
+ PRESENCE optional }|
+ -- Extension for Release 11 to indicate the last E-UTRAN PLMN Identity --
+ { ID id-LastE-UTRANPLMNIdentity CRITICALITY ignore EXTENSION PLMNIdentity
+ PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- CN INVOKE TRACE ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+
+```
+
+```
+
+--
+-- CN Invoke Trace
+--
+-- *****
+
+CN-InvokeTrace ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {CN-InvokeTraceIEs} },
+ protocolExtensions ProtocolExtensionContainer { {CN-InvokeTraceExtensions} } OPTIONAL,
+ ...
+}
+
+CN-InvokeTraceIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TraceType CRITICALITY ignore TYPE TraceType PRESENCE optional } |
+ -- This information is mandatory for GERAN Iu Mode, not applicable to UTRAN --
+ { ID id-TraceReference CRITICALITY ignore TYPE TraceReference PRESENCE mandatory } |
+ { ID id-TriggerID CRITICALITY ignore TYPE TriggerID PRESENCE optional } |
+ -- This information is mandatory for GERAN Iu Mode, not applicable to UTRAN --
+ { ID id-UE-ID CRITICALITY ignore TYPE UE-ID PRESENCE optional } |
+ -- This information is mandatory for UTRAN, optional for GERAN Iu mode --
+ { ID id-OMC-ID CRITICALITY ignore TYPE OMC-ID PRESENCE optional },
+ -- This information is mandatory for GERAN Iu Mode, not applicable to UTRAN --
+ ...
+}
+
+CN-InvokeTraceExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 6 to enable signalling based activation for Subscriber and Equipment Trace over Iu interface --
+ { ID id-TracePropagationParameters CRITICALITY ignore EXTENSION TracePropagationParameters PRESENCE optional } |
+ -- Extension for Release 10 to support MDT--
+ { ID id-MDT-Configuration CRITICALITY ignore EXTENSION MDT-Configuration PRESENCE optional } |
+ -- Extension for Release 10 to support MDT--
+ { ID id-Trace-Collection-Entity-IP-Address CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- CN DEACTIVATE TRACE ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- CN Deactivate Trace
+--
+-- *****
+
+CN-DeactivateTrace ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {CN-DeactivateTraceIEs} },
+ protocolExtensions ProtocolExtensionContainer { {CN-DeactivateTraceExtensions} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+}
+
+CN-DeactivateTraceIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TraceReference CRITICALITY ignore TYPE TraceReference PRESENCE mandatory } |
+ { ID id-TriggerID CRITICALITY ignore TYPE TriggerID PRESENCE optional },
+ -- This information is optional for GERAN Iu Mode, not applicable to UTRAN --
+ ...
+}
+
+CN-DeactivateTraceExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- LOCATION REPORTING CONTROL ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Location Reporting Control
+--
+-- *****
+
+LocationReportingControl ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {LocationReportingControlIEs} },
+ protocolExtensions ProtocolExtensionContainer { {LocationReportingControlExtensions} } OPTIONAL,
+ ...
+}
+
+LocationReportingControlIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RequestType CRITICALITY ignore TYPE RequestType PRESENCE mandatory },
+ ...
+}
+
+LocationReportingControlExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 to enhance the location request over Iu --
+ { ID id-VerticalAccuracyCode CRITICALITY ignore EXTENSION VerticalAccuracyCode PRESENCE optional } |
+ -- Extension for Release 4 to enhance the location request over Iu --
+ { ID id-ResponseTime CRITICALITY ignore EXTENSION ResponseTime PRESENCE optional } |
+ -- Extension for Release 4 to enhance the location request over Iu --
+ { ID id-PositioningPriority CRITICALITY ignore EXTENSION PositioningPriority PRESENCE optional } |
+ -- Extension for Release 4 to enhance the location request over Iu --
+ { ID id-ClientType CRITICALITY ignore EXTENSION ClientType PRESENCE optional } |
+ -- Extension for Release 7 to allow the request of velocity over Iu --
+ { ID id-IncludeVelocity CRITICALITY ignore EXTENSION IncludeVelocity PRESENCE optional } |
+ -- Extension for Release 7 to allow periodic reporting over Iu --
+ { ID id-PeriodicLocationInfo CRITICALITY ignore EXTENSION PeriodicLocationInfo PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+}
+
+-- *****
+--
+-- LOCATION REPORT ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Location Report
+--
+-- *****
+
+LocationReport ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {LocationReportIEs} },
+ protocolExtensions ProtocolExtensionContainer { {LocationReportExtensions} } OPTIONAL,
+ ...
+}
+
+LocationReportIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-AreaIdentity CRITICALITY ignore TYPE AreaIdentity PRESENCE optional } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } |
+ { ID id-RequestType CRITICALITY ignore TYPE RequestType PRESENCE optional } ,
+ ...
+}
+
+LocationReportExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 to enable report of Last Known Service Area with its Age over Iu --
+ { ID id-LastKnownServiceArea CRITICALITY ignore EXTENSION LastKnownServiceArea PRESENCE optional } |
+ -- Extension for Release 5 to pass the positioning methods that have been used --
+ { ID id-PositionData CRITICALITY ignore EXTENSION PositionData PRESENCE optional } |
+ -- Extension for Release 5 to pass the positioning methods that have been used for GERAN Iu mode --
+ { ID id-PositionDataSpecificToGERANIuMode CRITICALITY ignore EXTENSION PositionDataSpecificToGERANIuMode PRESENCE optional } |
+ -- This extension is optional for GERAN Iu mode only, not applicable for UTRAN --
+ -- Extension for Release 6 to indicate whether the returned position estimate satisfies the requested accuracy or not --
+ { ID id-AccuracyFulfilmentIndicator CRITICALITY ignore EXTENSION AccuracyFulfilmentIndicator PRESENCE optional } |
+ -- Extension for Release 7 to provide a velocity estimate --
+ { ID id-VelocityEstimate CRITICALITY ignore EXTENSION VelocityEstimate PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- INITIAL UE MESSAGE ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+
+```
+
+```
+
+-- Initial UE Message
+--
+-- *****
+
+InitialUE-Message ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {InitialUE-MessageIEs} },
+ protocolExtensions ProtocolExtensionContainer { {InitialUE-MessageExtensions} } OPTIONAL,
+ ...
+}
+
+InitialUE-MessageIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-LAI CRITICALITY ignore TYPE LAI PRESENCE mandatory } |
+ { ID id-RAC CRITICALITY ignore TYPE RAC PRESENCE conditional
+ -- This IE shall be present if the CN Domain Indicator IE is set to "PS domain" -- } |
+ { ID id-SAI CRITICALITY ignore TYPE SAI PRESENCE mandatory } |
+ { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory } |
+ { ID id-IuSigConId CRITICALITY ignore TYPE IuSignallingConnectionIdentifier PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE mandatory },
+ ...
+}
+
+InitialUE-MessageExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable GERAN support over Iu-cs --
+ { ID id-GERAN-Classmark CRITICALITY ignore EXTENSION GERAN-Classmark PRESENCE optional}|
+ -- Extension for Release 6 to convey the selected PLMN id in shared networks --
+ { ID id-SelectedPLMN-ID CRITICALITY ignore EXTENSION PLMNIdentity PRESENCE optional}|
+ -- Extension for Release 6 to enable rerouting in MOCN configuration for network sharing non-supporting UEs --
+ { ID id-PermanentNAS-UE-ID CRITICALITY ignore EXTENSION PermanentNAS-UE-ID PRESENCE optional}|
+ -- Extension for Release 6 to enable rerouting in MOCN configuration for network sharing non-supporting UEs --
+ { ID id-NAS-SequenceNumber CRITICALITY ignore EXTENSION NAS-SequenceNumber PRESENCE optional}|
+ -- Extension for Release 6 to indicate rerouting in MOCN configuration for network sharing non-supporting UEs --
+ { ID id-RedirectAttemptFlag CRITICALITY ignore EXTENSION RedirectAttemptFlag PRESENCE optional}|
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional}|
+ -- Extension for Release 8 to support CSG --
+ { ID id-CSG-Id CRITICALITY reject EXTENSION CSG-Id PRESENCE optional}|
+ -- Extension for Release 9 to allow communication of the cell access mode --
+ { ID id-Cell-Access-Mode CRITICALITY reject EXTENSION Cell-Access-Mode PRESENCE optional}|
+ -- Extension for Release 10 to support LIPA --
+ { ID id-LGW-TransportLayerAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}|
+ -- Extension for Release 9 to enable the CN to handle potential UE NAS QoS issues related to higher bitrates --
+ { ID id-HigherBitratesThan16MbpsFlag CRITICALITY ignore EXTENSION HigherBitratesThan16MbpsFlag PRESENCE optional}|
+ -- Extension for Release 11 to support BBAI --
+ { ID id-Tunnel-Information-for-BBF CRITICALITY ignore EXTENSION TunnelInformation PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+
+```
+
+```
+
+-- DIRECT TRANSFER ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Direct Transfer
+--
+-- *****
+
+DirectTransfer ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {DirectTransferIEs} },
+ protocolExtensions ProtocolExtensionContainer { {DirectTransferExtensions} } OPTIONAL,
+ ...
+}
+
+DirectTransferIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory}|
+ { ID id-LAI CRITICALITY ignore TYPE LAI PRESENCE optional}|
+ { ID id-RAC CRITICALITY ignore TYPE RAC PRESENCE optional}|
+ { ID id-SAI CRITICALITY ignore TYPE SAI PRESENCE optional}|
+ { ID id-SAPI CRITICALITY ignore TYPE SAPI PRESENCE optional},
+ ...
+}
+
+DirectTransferExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 6 to enable rerouting in MOCN configuration for network sharing non-supporting UEs --
+ { ID id-RedirectionIndication CRITICALITY ignore EXTENSION RedirectionIndication PRESENCE optional}|
+ -- Extension for Release 6 to indicate the MOCN rerouting is completed --
+ { ID id-RedirectionCompleted CRITICALITY ignore EXTENSION RedirectionCompleted PRESENCE optional}|
+ -- Extension for Release 8 to indicate the Subscriber Profile ID for RAT/Frequency Selection Priority --
+ { ID id-SubscriberProfileIDforRFP CRITICALITY ignore EXTENSION SubscriberProfileIDforRFP PRESENCE optional}|
+ -- Extension for Release 10 to support LIPA --
+ { ID id-LGW-TransportLayerAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional},
+ ...
+}
+
+RedirectionIndication ::= ProtocolIE-Container { {RedirectionIndication-IEs} }
+
+RedirectionIndication-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory }|
+ { ID id-RejectCauseValue CRITICALITY ignore TYPE RejectCauseValue PRESENCE mandatory}|
+ { ID id-NAS-SequenceNumber CRITICALITY ignore TYPE NAS-SequenceNumber PRESENCE optional}|
+ { ID id-PermanentNAS-UE-ID CRITICALITY ignore TYPE PermanentNAS-UE-ID PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- OVERLOAD CONTROL ELEMENTARY PROCEDURE
+
+```
+
+```
+
+--
+-- *****
+--
+-- *****
+--
+-- Overload
+--
+-- *****
+
+Overload ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {OverloadIEs} },
+ protocolExtensions ProtocolExtensionContainer { {OverloadExtensions} } OPTIONAL,
+ ...
+}
+
+OverloadIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-NumberOfSteps CRITICALITY ignore TYPE NumberOfSteps PRESENCE optional } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional },
+ ...
+}
+
+OverloadExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 99 to enable the indication to the RNC which CN domain is suffering the signalling traffic overload --
+ { ID id-CN-DomainIndicator CRITICALITY ignore EXTENSION CN-DomainIndicator PRESENCE optional } |
+ -- Extension for Release 5 to enable NNSF --
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID PRESENCE optional } |
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional } |
+ -- Extension for Release 10 to support Low Priority overload --
+ { ID id-Priority-Class-Indicator CRITICALITY ignore EXTENSION Priority-Class-Indicator PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- ERROR INDICATION ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Error Indication
+--
+-- *****
+
+ErrorIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ErrorIndicationIEs} },
+ protocolExtensions ProtocolExtensionContainer { {ErrorIndicationExtensions} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ErrorIndicationIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } |
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE optional } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional },
+ ...
+}
+
+ErrorIndicationExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 --
+ { ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID PRESENCE optional } |
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- SRNS DATA FORWARD ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- SRNS Data Forward Command
+--
+-- *****
+
+SRNS-DataForwardCommand ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SRNS-DataForwardCommandIEs} },
+ protocolExtensions ProtocolExtensionContainer { {SRNS-DataForwardCommandExtensions} } OPTIONAL,
+ ...
+}
+
+SRNS-DataForwardCommandIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-DataForwardingList CRITICALITY ignore TYPE RAB-DataForwardingList PRESENCE optional },
+ ...
+}
+
+SRNS-DataForwardCommandExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- FORWARD SRNS CONTEXT ELEMENTARY PROCEDURE
+--
+-- *****
+
+```
+
+```
+
+-- *****
+--
+-- Forward SRNS Context
+--
+-- *****
+
+ForwardSRNS-Context := SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ForwardSRNS-ContextIEs} },
+ protocolExtensions ProtocolExtensionContainer { {ForwardSRNS-ContextExtensions} } OPTIONAL,
+ ...
+}
+
+ForwardSRNS-ContextIEs RANAP-PROTOCOL-IES := {
+ { ID id-RAB-ContextList CRITICALITY ignore TYPE RAB-ContextList PRESENCE mandatory },
+ ...
+}
+
+ForwardSRNS-ContextExtensions RANAP-PROTOCOL-EXTENSION := {
+ -- Extension for Release 5 to enable relocation of Source RNC PDCP context info --
+ { ID id-SourceRNC-PDCP-context-info CRITICALITY ignore EXTENSION RRC-Container PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- RAB ASSIGNMENT ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- RAB Assignment Request
+--
+-- *****
+
+RAB-AssignmentRequest := SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RAB-AssignmentRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RAB-AssignmentRequestExtensions} } OPTIONAL,
+ ...
+}
+
+RAB-AssignmentRequestIEs RANAP-PROTOCOL-IES := {
+ { ID id-RAB-SetupOrModifyList CRITICALITY ignore TYPE RAB-SetupOrModifyList PRESENCE optional } |
+ { ID id-RAB-ReleaseList CRITICALITY ignore TYPE RAB-ReleaseList PRESENCE optional },
+ ...
+}
+
+RAB-SetupOrModifyList := RAB-IE-ContainerPairList { {RAB-SetupOrModifyItem-IEs} }
+
+RAB-SetupOrModifyItem-IEs RANAP-PROTOCOL-IES-PAIR := {
+
+```
+
+```
+
+{ ID id-RAB-SetupOrModifyItem
+ FIRST CRITICALITY reject
+ FIRST TYPE RAB-SetupOrModifyItemFirst
+ SECOND CRITICALITY ignore
+ SECOND TYPE RAB-SetupOrModifyItemSecond
+ PRESENCE mandatory },
+...
+}
+
+RAB-SetupOrModifyItemFirst ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ nAS-SynchronisationIndicator NAS-SynchronisationIndicator OPTIONAL,
+ rAB-Parameters RAB-Parameters OPTIONAL,
+ userPlaneInformation UserPlaneInformation OPTIONAL,
+ transportLayerInformation TransportLayerInformation OPTIONAL,
+ service-Handover Service-Handover OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-SetupOrModifyItemFirst-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TransportLayerInformation ::= SEQUENCE {
+ transportLayerAddress TransportLayerAddress,
+ iuTransportAssociation IuTransportAssociation,
+ iE-Extensions ProtocolExtensionContainer { {TransportLayerInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TransportLayerInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-SetupOrModifyItemFirst-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 8 to enable handover restriction to E-UTRAN --
+ { ID id-E-UTRAN-Service-Handover CRITICALITY ignore EXTENSION E-UTRAN-Service-Handover PRESENCE optional}|
+ -- Extension for Release 10 to support LIPA --
+ { ID id-Correlation-ID CRITICALITY ignore EXTENSION Correlation-ID PRESENCE optional},
+ ...
+}
+
+RAB-SetupOrModifyItemSecond ::= SEQUENCE {
+ pDP-TypeInformation PDP-TypeInformation OPTIONAL,
+ dataVolumeReportingIndication DataVolumeReportingIndication OPTIONAL,
+ dl-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL,
+ ul-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL,
+ dl-N-PDU-SequenceNumber DL-N-PDU-SequenceNumber OPTIONAL,
+ ul-N-PDU-SequenceNumber UL-N-PDU-SequenceNumber OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-SetupOrModifyItemSecond-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-SetupOrModifyItemSecond-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 4 to enable RAB Quality of Service negotiation over Iu --
+ { ID id-Alt-RAB-Parameters CRITICALITY ignore EXTENSION Alt-RAB-Parameters PRESENCE optional}|
+
+```
+
+```
+
+-- Extension for Release 5 to enable GERAN support over Iu-cs --
+ { ID id-GERAN-BSC-Container CRITICALITY ignore EXTENSION GERAN-BSC-Container PRESENCE optional}|
+-- Extension for Release Release 9 to enable a new value --
+ { ID id-PDP-TypeInformation-extension CRITICALITY ignore EXTENSION PDP-TypeInformation-extension PRESENCE optional}|
+-- Extension for Release 10 to enable Offload at Iu-ps for UTRAN --
+ { ID id-Offload-RAB-Parameters CRITICALITY ignore EXTENSION Offload-RAB-Parameters PRESENCE optional},
+ ...
+}
+
+RAB-AssignmentRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate PRESENCE optional}|
+-- Extension for Release 10 to enable Offload at Iu-ps for UTRAN --
+ { ID id-MSISDN CRITICALITY ignore EXTENSION MSISDN PRESENCE optional},
+ ...
+}
+
+-- **************************************************************
+--
+-- RAB Assignment Response
+--
+-- **************************************************************
+
+RAB-AssignmentResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RAB-AssignmentResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RAB-AssignmentResponseExtensions} } OPTIONAL,
+ ...
+}
+
+RAB-AssignmentResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupOrModifiedList CRITICALITY ignore TYPE RAB-SetupOrModifiedList PRESENCE optional } |
+ { ID id-RAB-ReleasedList CRITICALITY ignore TYPE RAB-ReleasedList PRESENCE optional } |
+
+ { ID id-RAB-QueuedList CRITICALITY ignore TYPE RAB-QueuedList PRESENCE optional } |
+ { ID id-RAB-FailedList CRITICALITY ignore TYPE RAB-FailedList PRESENCE optional } |
+ { ID id-RAB-ReleaseFailedList CRITICALITY ignore TYPE RAB-ReleaseFailedList PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+RAB-SetupOrModifiedList ::= RAB-IE-ContainerList { {RAB-SetupOrModifiedItemIEs} }
+
+RAB-SetupOrModifiedItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupOrModifiedItem CRITICALITY ignore TYPE RAB-SetupOrModifiedItem PRESENCE mandatory },
+ ...
+}
+
+RAB-SetupOrModifiedItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ transportLayerAddress TransportLayerAddress OPTIONAL,
+ iuTransportAssociation IuTransportAssociation OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+dl-dataVolumes DataVolumeList OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {RAB-SetupOrModifiedItem-ExtIEs} } OPTIONAL,
+...
+}
+
+RAB-SetupOrModifiedItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 4 to enable RAB Quality of Service negotiation over Iu --
+{ ID id-Ass-RAB-Parameters CRITICALITY ignore EXTENSION Ass-RAB-Parameters PRESENCE optional },
+...
+}
+
+RAB-ReleasedList ::= RAB-IE-ContainerList { {RAB-ReleasedItemIEs} }
+
+RAB-ReleasedItemIEs RANAP-PROTOCOL-IES ::= {
+{ ID id-RAB-ReleasedItem CRITICALITY ignore TYPE RAB-ReleasedItem PRESENCE mandatory },
+...
+}
+
+RAB-ReleasedItem ::= SEQUENCE {
+rAB-ID RAB-ID,
+dl-dataVolumes DataVolumeList OPTIONAL,
+dL-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL,
+uL-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {RAB-ReleasedItem-ExtIEs} } OPTIONAL,
+...
+}
+
+RAB-ReleasedItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+DataVolumeList ::= SEQUENCE (SIZE (1..maxNrOfVol)) OF
+SEQUENCE {
+dl-UnsuccessfullyTransmittedDataVolume UnsuccessfullyTransmittedDataVolume,
+dataVolumeReference DataVolumeReference OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {DataVolumeList-ExtIEs} } OPTIONAL,
+...
+}
+
+DataVolumeList-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+RAB-QueuedList ::= RAB-IE-ContainerList { {RAB-QueuedItemIEs} }
+
+RAB-QueuedItemIEs RANAP-PROTOCOL-IES ::= {
+{ ID id-RAB-QueuedItem CRITICALITY ignore TYPE RAB-QueuedItem PRESENCE mandatory },
+...
+}
+
+```
+
+```
+
+RAB-QueuedItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ iE-Extensions ProtocolExtensionContainer { {RAB-QueuedItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-QueuedItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-ReleaseFailedList ::= RAB-FailedList
+
+RAB-AssignmentResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable GERAN support over Iu-cs --
+ { ID id-GERAN-Iumode-RAB-FailedList-RABAssgntResponse CRITICALITY ignore EXTENSION GERAN-Iumode-RAB-FailedList-RABAssgntResponse
+ PRESENCE optional} ,
+ ...
+}
+
+GERAN-Iumode-RAB-FailedList-RABAssgntResponse ::= RAB-IE-ContainerList { {GERAN-Iumode-RAB-Failed-RABAssgntResponse-ItemIEs} }
+
+GERAN-Iumode-RAB-Failed-RABAssgntResponse-ItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item CRITICALITY ignore TYPE GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item PRESENCE
+ mandatory } ,
+ ...
+}
+
+GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ cause Cause,
+ gERAN-Classmark GERAN-Classmark OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- PRIVATE MESSAGE
+--
+-- *****
+
+PrivateMessage ::= SEQUENCE {
+ privateIEs PrivateIE-Container { {PrivateMessage-IEs} },
+ ...
+}
+
+```
+
+```
+
+PrivateMessage-IEs RANAP-PRIVATE-IES ::= {
+ ...
+}
+
+-- *****
+--
+-- RANAP RELOCATION INFORMATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+RANAP-RelocationInformation ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RANAP-RelocationInformationIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RANAP-RelocationInformationExtensions} } OPTIONAL,
+ ...
+}
+
+RANAP-RelocationInformationIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-DirectTransferInformationList-RANAP-RelocInf
+ CRITICALITY ignore TYPE DirectTransferInformationList-RANAP-RelocInf
+ PRESENCE optional } |
+ { ID id-RAB-ContextList-RANAP-RelocInf CRITICALITY ignore TYPE RAB-ContextList-RANAP-RelocInf PRESENCE optional },
+ ...
+}
+
+DirectTransferInformationList-RANAP-RelocInf ::= DirectTransfer-IE-ContainerList { {DirectTransferInformationItemIEs-RANAP-RelocInf} }
+
+DirectTransferInformationItemIEs-RANAP-RelocInf RANAP-PROTOCOL-IES ::= {
+ { ID id-DirectTransferInformationItem-RANAP-RelocInf
+ CRITICALITY ignore TYPE DirectTransferInformationItem-RANAP-RelocInf
+ PRESENCE mandatory },
+ ...
+}
+
+DirectTransferInformationItem-RANAP-RelocInf ::= SEQUENCE {
+ nAS-PDU NAS-PDU,
+ sAPI SAPI,
+ cN-DomainIndicator CN-DomainIndicator,
+ iE-Extensions ProtocolExtensionContainer { {RANAP-DirectTransferInformationItem-ExtIEs-RANAP-RelocInf} } OPTIONAL,
+ ...
+}
+
+RANAP-DirectTransferInformationItem-ExtIEs-RANAP-RelocInf RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-ContextList-RANAP-RelocInf ::= RAB-IE-ContainerList { {RAB-ContextItemIEs-RANAP-RelocInf} }
+
+RAB-ContextItemIEs-RANAP-RelocInf RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ContextItem-RANAP-RelocInf CRITICALITY ignore TYPE RAB-ContextItem-RANAP-RelocInf PRESENCE mandatory },
+ ...
+}
+
+```
+
+```
+
+}
+
+RAB-ContextItem-RANAP-RelocInf ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ dl-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL,
+ ul-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL,
+ dl-N-PDU-SequenceNumber DL-N-PDU-SequenceNumber OPTIONAL,
+ ul-N-PDU-SequenceNumber UL-N-PDU-SequenceNumber OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RAB-ContextItem-ExtIEs-RANAP-RelocInf} } OPTIONAL,
+ ...
+}
+
+RAB-ContextItem-ExtIEs-RANAP-RelocInf RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RANAP-RelocationInformationExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable relocation of Source RNC PDCP context info --
+ { ID id-SourceRNC-PDCP-context-info CRITICALITY ignore EXTENSION RRC-Container PRESENCE optional} |
+ -- Extension for Release 10 to enable RNSAP Relocation --
+ { ID id-RNSAPRelocationParameters CRITICALITY reject EXTENSION RNSAPRelocationParameters PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- RANAP ENHANCED RELOCATION INFORMATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- RANAP Enhanced Relocation Information Request
+--
+-- *****
+
+RANAP-EnhancedRelocationInformationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RANAP-EnhancedRelocationInformationRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RANAP-EnhancedRelocationInformationRequestExtensions} } OPTIONAL,
+ ...
+}
+
+RANAP-EnhancedRelocationInformationRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Source-ToTarget-TransparentContainer
+ CRITICALITY reject TYPE SourceRNC-ToTargetRNC-TransparentContainer PRESENCE mandatory } |
+ { ID id-OldIuSigConIdCS CRITICALITY ignore TYPE IuSignallingConnectionIdentifier PRESENCE optional } |
+ { ID id-GlobalCN-IDCS CRITICALITY reject TYPE GlobalCN-ID PRESENCE optional} |
+ { ID id-OldIuSigConIdPS CRITICALITY ignore TYPE IuSignallingConnectionIdentifier PRESENCE optional } |
+ { ID id-GlobalCN-IDPS CRITICALITY reject TYPE GlobalCN-ID PRESENCE optional} |
+ { ID id-RAB-SetupList-EnhRelocInfoReq CRITICALITY reject TYPE RAB-SetupList-EnhRelocInfoReq PRESENCE optional } |
+}
+
+```
+
+```
+
+ { ID id-SNA-Access-Information CRITICALITY ignore TYPE SNA-Access-Information PRESENCE optional} |
+ { ID id-UESBI-Iu CRITICALITY ignore TYPE UESBI-Iu PRESENCE optional}|
+ { ID id-SelectedPLMN-ID CRITICALITY ignore TYPE PLMNIdentity PRESENCE optional }|
+ { ID id-CNBMSSLinkingInformation CRITICALITY ignore TYPE CNBMSSLinkingInformation PRESENCE optional},
+ ...
+}
+
+RAB-SetupList-EnhRelocInfoReq ::= RAB-IE-ContainerList { { RAB-SetupItem-EnhRelocInfoReq-IEs} }
+
+RAB-SetupItem-EnhRelocInfoReq-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupItem-EnhRelocInfoReq CRITICALITY reject TYPE RAB-SetupItem-EnhRelocInfoReq PRESENCE mandatory },
+ ...
+}
+
+RAB-SetupItem-EnhRelocInfoReq ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ cN-DomainIndicator CN-DomainIndicator,
+ rAB-Parameters RAB-Parameters,
+ dataVolumeReportingIndication DataVolumeReportingIndication OPTIONAL,
+ -- This IE shall be present if the CN domain indicator IE is set to "PS domain" --,
+ pDP-TypeInformation PDP-TypeInformation OPTIONAL,
+ -- This IE shall be present if the CN domain indicator IE is set to "PS domain" --,
+ userPlaneInformation UserPlaneInformation,
+ dataForwardingInformation TNLInformationEnhRelInfoReq OPTIONAL,
+ sourceSideIuULTNLInfo TNLInformationEnhRelInfoReq OPTIONAL,
+
+ service-Handover Service-Handover OPTIONAL,
+ alt-RAB-Parameters Alt-RAB-Parameters OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { RAB-SetupItem-EnhRelocInfoReq-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-SetupItem-EnhRelocInfoReq-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 8 to enable handover restriction to E-UTRAN --
+ { ID id-E-UTRAN-Service-Handover CRITICALITY ignore EXTENSION E-UTRAN-Service-Handover PRESENCE optional }|
+-- Extension for Release Release 9 to enable a new value --
+ { ID id-PDP-TypeInformation-extension CRITICALITY ignore EXTENSION PDP-TypeInformation-extension PRESENCE optional },
+ ...
+}
+
+TNLInformationEnhRelInfoReq ::=SEQUENCE{
+ transportLayerAddress TransportLayerAddress,
+ iuTransportAssociation IuTransportAssociation,
+ iE-Extensions ProtocolExtensionContainer { { TNLInformationEnhRelInfoReq-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TNLInformationEnhRelInfoReq-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+RANAP-EnhancedRelocationInformationRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-IntegrityProtectionInformation CRITICALITY ignore EXTENSION IntegrityProtectionInformation PRESENCE optional} |
+ { ID id-EncryptionInformation CRITICALITY ignore EXTENSION EncryptionInformation PRESENCE optional} |
+ { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate PRESENCE optional} |
+ -- Extension for Release 10 to enable RNSAP Relocation --
+ { ID id-RABParametersList CRITICALITY reject EXTENSION RABParametersList PRESENCE optional} |
+ { ID id-CSG-Id CRITICALITY reject EXTENSION CSG-Id PRESENCE optional} |
+ { ID id-CSG-Membership-Status CRITICALITY reject EXTENSION CSG-Membership-Status PRESENCE optional} |
+ -- Extension for Release 11 to support rSRVCC in case of network sharing -
+ { ID id-AnchorPLMN-ID CRITICALITY ignore EXTENSION PLMNIdentity PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- RANAP Enhanced Relocation Information Response
+--
+-- *****
+
+RANAP-EnhancedRelocationInformationResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RANAP-EnhancedRelocationInformationResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RANAP-EnhancedRelocationInformationResponseExtensions} } OPTIONAL,
+ ...
+}
+
+RANAP-EnhancedRelocationInformationResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Target-ToSource-TransparentContainer
+ CRITICALITY ignore TYPE TargetRNC-ToSourceRNC-TransparentContainer PRESENCE optional } |
+ { ID id-RAB-SetupList-EnhRelocInfoRes CRITICALITY ignore TYPE RAB-SetupList-EnhRelocInfoRes PRESENCE optional} |
+ { ID id-RAB-FailedList-EnhRelocInfoRes CRITICALITY ignore TYPE RAB-FailedList-EnhRelocInfoRes PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+RAB-SetupList-EnhRelocInfoRes ::= RAB-IE-ContainerList { { RAB-SetupItem-EnhRelocInfoRes-IEs} }
+
+RAB-SetupItem-EnhRelocInfoRes-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-SetupItem-EnhRelocInfoRes CRITICALITY reject TYPE RAB-SetupItem-EnhRelocInfoRes PRESENCE mandatory },
+ ...
+}
+
+RAB-SetupItem-EnhRelocInfoRes ::= SEQUENCE {
+ cN-DomainIndicator CN-DomainIndicator,
+ rAB-ID RAB-ID,
+ dataForwardingInformation TNLIInformationEnhRelInfoRes OPTIONAL,
+ ass-RAB-Parameters Ass-RAB-Parameters OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { RAB-SetupItem-EnhRelocInfoRes-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+}
+
+RAB-SetupItem-EnhRelocInfoRes-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-FailedList-EnhRelocInfoRes ::= RAB-IE-ContainerList { { RAB-FailedItem-EnhRelocInfoRes-IEs} }
+
+RAB-FailedItem-EnhRelocInfoRes-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-FailedItem-EnhRelocInfoRes CRITICALITY reject TYPE RAB-FailedItem-EnhRelocInfoRes PRESENCE mandatory },
+ ...
+}
+
+RAB-FailedItem-EnhRelocInfoRes ::= SEQUENCE {
+ cN-DomainIndicator CN-DomainIndicator,
+ rAB-ID RAB-ID,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { RAB-FailedItem-EnhRelocInfoRes-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-FailedItem-EnhRelocInfoRes-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TNLInformationEnhRelInfoRes ::=SEQUENCE{
+ dl-forwardingTransportLayerAddress TransportLayerAddress,
+ dl-forwardingTransportAssociation IuTransportAssociation,
+ iE-Extensions ProtocolExtensionContainer { { TNLInformationEnhRelInfoRes-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TNLInformationEnhRelInfoRes-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RANAP-EnhancedRelocationInformationResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+-- *****
+--
+-- RAB MODIFICATION REQUEST ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- RAB Modify Request
+--
+-- *****
+
+```
+
+```
+
+RAB-ModifyRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {RAB-ModifyRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {RAB-ModifyRequestExtensions} } OPTIONAL,
+ ...
+}
+
+RAB-ModifyRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ModifyList CRITICALITY ignore TYPE RAB-ModifyList PRESENCE mandatory},
+ ...
+}
+
+RAB-ModifyList ::= RAB-IE-ContainerList { {RAB-ModifyItemIEs} }
+
+RAB-ModifyItemIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-RAB-ModifyItem CRITICALITY ignore TYPE RAB-ModifyItem PRESENCE mandatory },
+ ...
+}
+
+RAB-ModifyItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ requested-RAB-Parameter-Values Requested-RAB-Parameter-Values,
+ iE-Extensions ProtocolExtensionContainer { {RAB-ModifyItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-ModifyItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-ModifyRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- LOCATION RELATED DATA ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Location Related Data Request
+--
+-- *****
+
+LocationRelatedDataRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {LocationRelatedDataRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {LocationRelatedDataRequestExtensions} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+LocationRelatedDataRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-LocationRelatedDataRequestType CRITICALITY reject TYPE LocationRelatedDataRequestType PRESENCE optional },
+ -- This IE is mandatory for UTRAN, optional for GERAN Iu Mode --
+ ...
+}
+
+LocationRelatedDataRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable LCS support for GERAN Iu mode --
+ { ID id-LocationRelatedDataRequestTypeSpecificToGERANIuMode CRITICALITY reject EXTENSION LocationRelatedDataRequestTypeSpecificToGERANIuMode
+ PRESENCE optional }|
+ -- The previous extension is optional for GERAN Iu Mode only, not applicable for UTRAN --
+ -- Extension for Release 7 to request GANSS Assistance Data. This IE shall be present if the Requested Location Related Data Type IE is set to
+ -- 'Dedicated Assistance Data for Assisted GANSS' or 'Dedicated Assistance Data for Assisted GPS and GANSS'--
+ { ID id-RequestedGANSSAssistanceData CRITICALITY reject EXTENSION RequestedGANSSAssistanceData
+ PRESENCE conditional },
+ ...
+}
+
+-- *****
+--
+-- Location Related Data Response
+--
+-- *****
+
+LocationRelatedDataResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { LocationRelatedDataResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { LocationRelatedDataResponseExtensions} } OPTIONAL,
+ ...
+}
+
+LocationRelatedDataResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-BroadcastAssistanceDataDecipheringKeys CRITICALITY ignore TYPE BroadcastAssistanceDataDecipheringKeys PRESENCE optional },
+ ...
+}
+
+LocationRelatedDataResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for error handling
+ { ID id-CriticalityDiagnostics CRITICALITY ignore EXTENSION CriticalityDiagnostics PRESENCE optional }|
+ { ID id-BroadcastGANSSAssistanceDataDecipheringKeys CRITICALITY ignore EXTENSION BroadcastAssistanceDataDecipheringKeys PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- Location Related Data Failure
+--
+-- *****
+
+LocationRelatedDataFailure ::= SEQUENCE {
+
+```
+
+```
+
+ protocolIEs ProtocolIE-Container { { LocationRelatedDataFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { { LocationRelatedDataFailureExtensions} } OPTIONAL,
+ ...
+}
+
+LocationRelatedDataFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory },
+ ...
+}
+
+LocationRelatedDataFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for error handling
+ { ID id-CriticalityDiagnostics CRITICALITY ignore EXTENSION CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- INFORMATION TRANSFER ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Information Transfer Indication
+--
+-- *****
+
+InformationTransferIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { InformationTransferIndicationIEs} },
+ protocolExtensions ProtocolExtensionContainer { { InformationTransferIndicationExtensions} } OPTIONAL,
+ ...
+}
+
+InformationTransferIndicationIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InformationTransferID CRITICALITY reject TYPE InformationTransferID PRESENCE mandatory } |
+ { ID id-ProvidedData CRITICALITY reject TYPE ProvidedData PRESENCE mandatory } |
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-GlobalCN-ID CRITICALITY ignore TYPE GlobalCN-ID PRESENCE optional},
+ ...
+}
+
+InformationTransferIndicationExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- Information Transfer Confirmation
+--
+-- *****
+
+```
+
+```
+
+-- *****
+InformationTransferConfirmation ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { InformationTransferConfirmationIEs} },
+ protocolExtensions ProtocolExtensionContainer { { InformationTransferConfirmationExtensions} } OPTIONAL,
+ ...
+}
+
+InformationTransferConfirmationIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InformationTransferID CRITICALITY ignore TYPE InformationTransferID PRESENCE mandatory } |
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE mandatory },
+ ...
+}
+
+InformationTransferConfirmationExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- Information Transfer Failure
+--
+-- *****
+
+InformationTransferFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { InformationTransferFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { { InformationTransferFailureExtensions} } OPTIONAL,
+ ...
+}
+
+InformationTransferFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InformationTransferID CRITICALITY ignore TYPE InformationTransferID PRESENCE mandatory } |
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE mandatory },
+ ...
+}
+
+InformationTransferFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+-- *****
+
+```
+
+```
+
+--
+-- UE SPECIFIC INFORMATION ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- UE Specific Information Indication
+--
+-- *****
+
+UESpecificInformationIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {UESpecificInformationIndicationIEs} },
+ protocolExtensions ProtocolExtensionContainer { {UESpecificInformationIndicationExtensions} } OPTIONAL,
+ ...
+}
+
+UESpecificInformationIndicationIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-UESBI-Iu CRITICALITY ignore TYPE UESBI-Iu PRESENCE optional },
+ ...
+}
+
+UESpecificInformationIndicationExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- DIRECT INFORMATION TRANSFER ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Direct Information Transfer
+--
+-- *****
+
+DirectInformationTransfer ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { DirectInformationTransferIEs} },
+ protocolExtensions ProtocolExtensionContainer { { DirectInformationTransferExtensions} } OPTIONAL,
+ ...
+}
+
+DirectInformationTransferIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InterSystemInformationTransferType CRITICALITY ignore TYPE InterSystemInformationTransferType PRESENCE optional } |
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional } |
+ { ID id-GlobalCN-ID CRITICALITY ignore TYPE GlobalCN-ID PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+}
+
+DirectInformationTransferExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- UPLINK INFORMATION EXCHANGE ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- Uplink Information Exchange Request
+--
+-- *****
+
+UplinkInformationExchangeRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { UplinkInformationExchangeRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { { UplinkInformationExchangeRequestExtensions} } OPTIONAL,
+ ...
+}
+
+UplinkInformationExchangeRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InformationExchangeID CRITICALITY reject TYPE InformationExchangeID PRESENCE mandatory } |
+ { ID id-InformationExchangeType CRITICALITY reject TYPE InformationExchangeType PRESENCE mandatory } |
+ { ID id-InformationTransferType CRITICALITY reject TYPE InformationTransferType PRESENCE conditional
+ -- This IE shall be present if the Information Exchange Type IE is set to "transfer" -- } |
+ { ID id-InformationRequestType CRITICALITY reject TYPE InformationRequestType PRESENCE conditional
+ -- This IE shall be present if the Information Exchange Type IE is set to "request" -- } |
+ { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY reject TYPE GlobalRNC-ID PRESENCE mandatory },
+ ...
+}
+
+UplinkInformationExchangeRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- Uplink Information Exchange Response
+--
+-- *****
+
+```
+
+```
+
+UplinkInformationExchangeResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { UplinkInformationExchangeResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { UplinkInformationExchangeResponseExtensions} } OPTIONAL,
+ ...
+}
+
+UplinkInformationExchangeResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID PRESENCE mandatory } |
+ { ID id-InformationRequested CRITICALITY ignore TYPE InformationRequested PRESENCE optional } |
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-GlobalCN-ID CRITICALITY ignore TYPE GlobalCN-ID PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+UplinkInformationExchangeResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- Uplink Information Exchange Failure
+--
+-- *****
+
+UplinkInformationExchangeFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { UplinkInformationExchangeFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { { UplinkInformationExchangeFailureExtensions} } OPTIONAL,
+ ...
+}
+
+UplinkInformationExchangeFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID PRESENCE mandatory } |
+ { ID id-CN-DomainIndicator CRITICALITY ignore TYPE CN-DomainIndicator PRESENCE mandatory } |
+ { ID id-GlobalCN-ID CRITICALITY ignore TYPE GlobalCN-ID PRESENCE optional } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+UplinkInformationExchangeFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS SESSION START PROCEDURE
+--
+-- *****
+
+```
+
+```
+
+-- *****
+--
+-- MBMS Session Start
+--
+-- *****
+
+MBMSSessionStart ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionStartIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionStartExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionStartIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TMGI CRITICALITY reject TYPE TMGI PRESENCE mandatory } |
+ { ID id-MBMSSessionIdentity CRITICALITY ignore TYPE MBMSSessionIdentity PRESENCE optional } |
+ { ID id-MBMSBearerServiceType CRITICALITY reject TYPE MBMSBearerServiceType PRESENCE mandatory } |
+ { ID id-IuSigConId CRITICALITY reject TYPE IuSignallingConnectionIdentifier PRESENCE mandatory } |
+ { ID id-RAB-Parameters CRITICALITY reject TYPE RAB-Parameters PRESENCE mandatory } |
+ { ID id-PDP-TypeInformation CRITICALITY ignore TYPE PDP-TypeInformation PRESENCE optional } |
+ { ID id-MBMSSessionDuration CRITICALITY reject TYPE MBMSSessionDuration PRESENCE mandatory } |
+ { ID id-MBMSServiceArea CRITICALITY reject TYPE MBMSServiceArea PRESENCE mandatory } |
+ { ID id-FrequenceLayerConvergenceFlag CRITICALITY ignore TYPE FrequenceLayerConvergenceFlag PRESENCE optional } |
+ { ID id-RAListofIdleModeUEs CRITICALITY ignore TYPE RAListofIdleModeUEs PRESENCE optional } |
+ { ID id-GlobalCN-ID CRITICALITY reject TYPE GlobalCN-ID PRESENCE optional } |
+ { ID id-MBMSSessionRepetitionNumber CRITICALITY ignore TYPE MBMSSessionRepetitionNumber PRESENCE optional } |
+ { ID id-TimeToMBMSDataTransfer CRITICALITY reject TYPE TimeToMBMSDataTransfer PRESENCE mandatory },
+ ...
+}
+
+MBMSSessionStartExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 6 to enable MBMS counting in broadcast mode --
+ { ID id-MBMSCountingInformation CRITICALITY ignore EXTENSION MBMSCountingInformation PRESENCE optional } |
+ { ID id-MBMSSynchronisationInformation CRITICALITY ignore EXTENSION MBMSSynchronisationInformation PRESENCE optional } |
+ -- Extension for Release Release 9 to enable a new value --
+ { ID id-PDP-TypeInformation-extension CRITICALITY ignore EXTENSION PDP-TypeInformation-extension PRESENCE optional },
+ ...
+}
+
+MBMSSynchronisationInformation ::= SEQUENCE {
+ mBMSHCIndicator MBMSHCIndicator,
+ iPMulticastAddress IPMulticastAddress,
+ gTPDLTEID GTP-TEI,
+ iE-Extensions ProtocolExtensionContainer { { MBMSSynchronisationInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBMSSynchronisationInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-IP-Source-Address CRITICALITY reject EXTENSION IPMulticastAddress PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- MBMS Session Start Response
+--
+-- *****
+
+MBMSSessionStartResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionStartResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionStartResponseExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionStartResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TransportLayerInformation CRITICALITY ignore TYPE TransportLayerInformation PRESENCE optional } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+MBMSSessionStartResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS Session Start Failure
+--
+-- *****
+
+MBMSSessionStartFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionStartFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionStartFailureExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionStartFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+MBMSSessionStartFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS SESSION UPDATE PROCEDURE
+--
+-- *****
+
+```
+
+```
+
+-- *****
+-- *****
+--
+-- MBMS Session Update
+--
+-- *****
+
+MBMSSessionUpdate ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionUpdateIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionUpdateExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionUpdateIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-SessionUpdateID CRITICALITY reject TYPE SessionUpdateID PRESENCE mandatory } |
+ { ID id-DeltaRAListofIdleModeUEs CRITICALITY reject TYPE DeltaRAListofIdleModeUEs PRESENCE mandatory },
+ ...
+}
+
+MBMSSessionUpdateExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS Session Update Response
+--
+-- *****
+
+MBMSSessionUpdateResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionUpdateResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionUpdateResponseExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionUpdateResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-SessionUpdateID CRITICALITY ignore TYPE SessionUpdateID PRESENCE mandatory } |
+ { ID id-TransportLayerInformation CRITICALITY ignore TYPE TransportLayerInformation PRESENCE optional } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+MBMSSessionUpdateResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+
+```
+
+```
+
+-- MBMS Session Update Failure
+--
+-- *****
+
+MBMSSessionUpdateFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionUpdateFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionUpdateFailureExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionUpdateFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-SessionUpdateID CRITICALITY ignore TYPE SessionUpdateID PRESENCE mandatory } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+MBMSSessionUpdateFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS SESSION STOP PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- MBMS Session Stop
+--
+-- *****
+
+MBMSSessionStop ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionStopIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionStopExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionStopIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-MBMSCNDe-Registration CRITICALITY reject TYPE MBMSCNDe-Registration PRESENCE mandatory },
+ ...
+}
+
+MBMSSessionStopExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+
+```
+
+```
+
+-- MBMS Session Stop Response
+--
+-- *****
+
+MBMSSessionStopResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSSessionStopResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSSessionStopResponseExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSSessionStopResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+MBMSSessionStopResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS UE LINKING PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- MBMS UE Linking Request
+--
+-- *****
+
+MBMSUELinkingRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSUELinkingRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSUELinkingRequestExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSUELinkingRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-JoinedMBMSBearerServicesList CRITICALITY reject TYPE JoinedMBMSBearerService-IEs PRESENCE optional } |
+ { ID id-LeftMBMSBearerServicesList CRITICALITY reject TYPE LeftMBMSBearerService-IEs PRESENCE optional } ,
+ ...
+}
+
+LeftMBMSBearerService-IEs ::= SEQUENCE (SIZE (1.. maxnoofMulticastServicesPerUE)) OF
+ SEQUENCE {
+ tMGI TMGI,
+ iE-Extensions ProtocolExtensionContainer { {LeftMBMSBearerService-ExtIEs} } OPTIONAL,
+ ...
+ }
+}
+
+```
+
+```
+
+LeftMBMSBearerService-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MBMSUELinkingRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS UE Linking Response
+--
+-- *****
+
+MBMSUELinkingResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSUELinkingResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSUELinkingResponseExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSUELinkingResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-UnsuccessfullLinkingList CRITICALITY ignore TYPE UnsuccessfullLinking-IEs PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+UnsuccessfullLinking-IEs ::= SEQUENCE (SIZE (1.. maxnoofMulticastServicesPerUE)) OF
+ SEQUENCE {
+ tMGI TMGI,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { {UnsuccessfullLinking-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+UnsuccessfullLinking-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MBMSUELinkingResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS REGISTRATION PROCEDURE
+--
+-- *****
+
+-- *****
+
+```
+
+```
+
+--
+-- MBMS Registration Request
+--
+-- *****
+
+MBMSRegistrationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSRegistrationRequestIEs } },
+ protocolExtensions ProtocolExtensionContainer { { MBMSRegistrationRequestExtensions } } OPTIONAL,
+ ...
+}
+
+MBMSRegistrationRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-MBMSRegistrationRequestType CRITICALITY reject TYPE MBMSRegistrationRequestType PRESENCE mandatory } |
+ { ID id-TMGI CRITICALITY reject TYPE TMGI PRESENCE mandatory } |
+ { ID id-IPMulticastAddress CRITICALITY reject TYPE IPMulticastAddress PRESENCE conditional } |
+ -- This IE shall be present if the MBMS Registration Request Type IE is set to "register" -- } |
+ { ID id-APN CRITICALITY reject TYPE APN PRESENCE conditional } |
+ -- This IE shall be present if the MBMS Registration Request Type IE is set to "register" -- } |
+ { ID id-GlobalRNC-ID CRITICALITY reject TYPE GlobalRNC-ID PRESENCE optional },
+ ...
+}
+
+MBMSRegistrationRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- MBMS Registration Response
+--
+-- *****
+
+MBMSRegistrationResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSRegistrationResponseIEs } },
+ protocolExtensions ProtocolExtensionContainer { { MBMSRegistrationResponseExtensions } } OPTIONAL,
+ ...
+}
+
+MBMSRegistrationResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TMGI CRITICALITY ignore TYPE TMGI PRESENCE optional } |
+ { ID id-GlobalCN-ID CRITICALITY ignore TYPE GlobalCN-ID PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+MBMSRegistrationResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- MBMS Registration Failure
+--
+-- *****
+
+MBMSRegistrationFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSRegistrationFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSRegistrationFailureExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSRegistrationFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TMGI CRITICALITY ignore TYPE TMGI PRESENCE optional } |
+ { ID id-GlobalCN-ID CRITICALITY ignore TYPE GlobalCN-ID PRESENCE optional } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+}
+
+MBMSRegistrationFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS CN DE-REGISTRATION PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- MBMS CN De-Registration Request
+--
+-- *****
+
+MBMSCNDe-RegistrationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSCNDe-RegistrationRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSCNDe-RegistrationRequestExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSCNDe-RegistrationRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TMGI CRITICALITY reject TYPE TMGI PRESENCE mandatory } |
+ { ID id-GlobalCN-ID CRITICALITY reject TYPE GlobalCN-ID PRESENCE optional } ,
+ ...
+}
+
+MBMSCNDe-RegistrationRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+
+```
+
+```
+
+ ...
+ }
+
+ -- *****
+ --
+ -- MBMS CN De-Registration Response
+ --
+ -- *****
+
+ MBMSCNDe-RegistrationResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSCNDe-RegistrationResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSCNDe-RegistrationResponseExtensions} } OPTIONAL,
+ ...
+ }
+
+ MBMSCNDe-RegistrationResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TMGI CRITICALITY ignore TYPE TMGI PRESENCE mandatory } |
+ { ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE mandatory } |
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } |
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
+ ...
+ }
+
+ MBMSCNDe-RegistrationResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+ }
+
+ -- *****
+ --
+ -- MBMS RAB ESTABLISHMENT INDICATION PROCEDURE
+ --
+ -- *****
+
+ -- *****
+ --
+ -- MBMS RAB Establishment Indication
+ --
+ -- *****
+
+ MBMSRABEstablishmentIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { MBMSRABEstablishmentIndicationIEs} },
+ protocolExtensions ProtocolExtensionContainer { { MBMSRABEstablishmentIndicationExtensions} } OPTIONAL,
+ ...
+ }
+
+ MBMSRABEstablishmentIndicationIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-TransportLayerInformation CRITICALITY ignore TYPE TransportLayerInformation PRESENCE mandatory } ,
+ ...
+ }
+
+```
+
+```
+
+}
+
+MBMSRABEstablishmentIndicationExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS RAB RELEASE PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- MBMS RAB Release Request
+--
+-- *****
+
+MBMSRABReleaseRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {MBMSRABReleaseRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {MBMSRABReleaseRequestExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSRABReleaseRequestIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory },
+ ...
+}
+
+MBMSRABReleaseRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS RAB Release
+--
+-- *****
+
+MBMSRABRelease ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {MBMSRABReleaseIEs} },
+ protocolExtensions ProtocolExtensionContainer { {MBMSRABReleaseExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSRABReleaseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+}
+
+MBMSRABReleaseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- MBMS RAB Release Failure
+--
+-- *****
+
+MBMSRABReleaseFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {MBMSRABReleaseFailureIEs} },
+ protocolExtensions ProtocolExtensionContainer { {MBMSRABReleaseFailureExtensions} } OPTIONAL,
+ ...
+}
+
+MBMSRABReleaseFailureIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+MBMSRABReleaseFailureExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- SRVCC PREPARATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- SRVCC CS Keys Request
+--
+-- *****
+
+SRVCC-CSKeysRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SRVCC-CSKeysRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {SRVCC-CSKeysRequestExtensions} } OPTIONAL,
+ ...
+}
+
+SRVCC-CSKeysRequestIEs RANAP-PROTOCOL-IES ::= {
+ ...
+}
+
+```
+
+```
+
+SRVCC-CSKeysRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- SRVCC CS Keys Response
+--
+-- *****
+
+SRVCC-CSKeysResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {SRVCC-CSKeysResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { {SRVCC-CSKeysResponseExtensions} } OPTIONAL,
+ ...
+}
+
+SRVCC-CSKeysResponseIEs RANAP-PROTOCOL-IES ::= {
+ { ID id-IntegrityProtectionKey CRITICALITY reject TYPE IntegrityProtectionKey PRESENCE mandatory }|
+ { ID id-EncryptionKey CRITICALITY reject TYPE EncryptionKey PRESENCE mandatory }|
+ { ID id-SRVCC-Information CRITICALITY reject TYPE SRVCC-Information PRESENCE mandatory }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+SRVCC-CSKeysResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- UE RADIO CAPABILITY MATCH PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- UE Radio Capability Match Request
+--
+-- *****
+
+UeRadioCapabilityMatchRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {UeRadioCapabilityMatchRequestIEs} },
+ protocolExtensions ProtocolExtensionContainer { {UeRadioCapabilityMatchRequestExtensions} } OPTIONAL,
+ ...
+}
+
+UeRadioCapabilityMatchRequestIEs RANAP-PROTOCOL-IES ::= {
+ ...
+}
+
+```
+
+```
+
+UeRadioCapabilityMatchRequestExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+-- UE Radio Capability Match Response
+--
+-- *****
+
+UeRadioCapabilityMatchResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {UeRadioCapabilityMatchResponseIEs} },
+ protocolExtensions ProtocolExtensionContainer { {UeRadioCapabilityMatchResponseExtensions} } OPTIONAL,
+ ...
+}
+
+UeRadioCapabilityMatchResponseIEs RANAP-PROTOCOL-IEs ::= {
+ { ID id-VoiceSupportMatchIndicator CRITICALITY reject TYPE VoiceSupportMatchIndicator PRESENCE mandatory },
+ ...
+}
+
+UeRadioCapabilityMatchResponseExtensions RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+END
+
+```
+
+### 9.3.4 Information Element Definitions
+
+```
+
+-- *****
+--
+-- Information Element Definitions
+--
+-- *****
+
+RANAP-IEs {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ umts-Access (20) modules (3) ranap (0) version1 (1) ranap-IEs (2) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+IMPORTS
+ maxNrOfCSGs,
+ maxNrOfErrors,
+ maxNrOfPDPDirections,
+ maxNrOfPoints,
+
+```
+
+```
+maxNrOfRABs,
+maxNrOfSRBs,
+maxNrOfSeparateTrafficDirections,
+maxRAB-Subflows,
+maxRAB-SubflowCombination,
+maxNrOfLevels,
+maxNrOfAltValues,
+maxNrOfSNAs,
+maxNrOfFLAs,
+maxNrOfPLMNSN,
+maxSet,
+maxNrOfHSDSCHMACdFlows-1,
+maxNrOfUEsToBeTraced,
+maxNrOfInterfaces,
+maxnoofMulticastServicesPerRNC,
+maxMBMSSA,
+maxMBMSRA,
+maxnoofMulticastServicesPerUE,
+maxNrOfEDCHMACdFlows-1,
+maxGANSSSet,
+maxNrOfEUTRAFreqs,
+maxNrOfCellIds,
+maxNrOfRAIs,
+maxNrOfLAIs,
+maxNrOfVol,
+maxSizeOfIMSInfo,
+maxnoofMDTPLMNs,
+
+id-CN-DomainIndicator,
+id-MessageStructure,
+id-SRB-TrCH-Mapping,
+id-TypeOfError,
+id-hS-DSCH-MAC-d-Flow-ID,
+id-SignallingIndication,
+id-CellLoadInformationGroup,
+id-TraceRecordingSessionInformation,
+id-MBMSLinkingInformation,
+id-AlternativeRABConfiguration,
+id-AlternativeRABConfigurationRequest,
+id-E-DCH-MAC-d-Flow-ID,
+id-RAC,
+id-Alt-RAB-Parameter-ExtendedGuaranteedBitrateInf,
+id-Alt-RAB-Parameter-ExtendedMaxBitrateInf,
+id-Ass-RAB-Parameter-ExtendedGuaranteedBitrateList,
+id-Ass-RAB-Parameter-ExtendedMaxBitrateList,
+id-RAB-Parameter-ExtendedGuaranteedBitrateList,
+id-RAB-Parameter-ExtendedMaxBitrateList,
+id-Requested-RAB-Parameter-ExtendedMaxBitrateList,
+id-Requested-RAB-Parameter-ExtendedGuaranteedBitrateList,
+id-LAoIdleModeUEs,
+```
+
+```
+id-newLAListofIdleModeUEs,
+id-LAListwithNoIdleModeUEsAnyMore,
+id-ExtendedRNC-ID,
+id-GANSS-PositioningDataSet,
+id-d-RNTI-for-NoIuCSUP,
+id-UE-History-Information,
+id-SubscriberProfileIDforRFP,
+id-Alt-RAB-Parameter-SupportedGuaranteedBitrateInf,
+id-Alt-RAB-Parameter-SupportedMaxBitrateInf,
+id-Ass-RAB-Parameter-SupportedGuaranteedBitrateList,
+id-Ass-RAB-Parameter-SupportedMaxBitrateList,
+id-RAB-Parameter-SupportedGuaranteedBitrateList,
+id-RAB-Parameter-SupportedMaxBitrateList,
+id-Requested-RAB-Parameter-SupportedMaxBitrateList,
+id-Requested-RAB-Parameter-SupportedGuaranteedBitrateList,
+id-PSRABtoBeReplaced,
+id-SRVCC-Information,
+id-CSG-Id,
+id-CSFB-Information,
+id-IRAT-Measurement-Configuration,
+id-Management-Based-MDT-Allowed,
+id-Time-UE-StayedInCell-EnhancedGranularity,
+id-HO-Cause,
+id-TraceRecordingSessionReference,
+id-IMSI,
+id-Management-Based-MDT-PLMN-List,
+id-SignallingBasedMDTPLMNList,
+id-M4Report,
+id-M5Report,
+id-M6Report,
+id-M7Report,
+id-TimingDifferenceULDL,
+id-Trace-Collection-Entity-IP-Address,
+id-Serving-Cell-Identifier,
+id-EARFCN-Extended,
+id-LastE-UTRANPLMNIdentity
+
+FROM RANAP-Constants
+
+ Criticality,
+ ProcedureCode,
+ ProtocolIE-ID,
+ TriggeringMessage
+FROM RANAP-CommonDataTypes
+
+ ProtocolExtensionContainer{},
+ RANAP-PROTOCOL-EXTENSION
+FROM RANAP-Containers;
+```
+
+```
+
+-- A
+
+AccuracyFulfilmentIndicator ::= ENUMERATED{
+ requested-Accuracy-Fulfilled,
+ requested-Accuracy-Not-Fulfilled,
+ ...
+}
+
+AllocationOrRetentionPriority ::= SEQUENCE {
+ priorityLevel PriorityLevel,
+ pre-emptionCapability Pre-emptionCapability,
+ pre-emptionVulnerability Pre-emptionVulnerability,
+ queuingAllowed QueuingAllowed,
+ iE-Extensions ProtocolExtensionContainer { {AllocationOrRetentionPriority-ExtIEs} } OPTIONAL,
+ ...
+}
+
+AllocationOrRetentionPriority-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Alt-RAB-Parameters ::= SEQUENCE {
+ altMaxBitrateInf Alt-RAB-Parameter-MaxBitrateInf OPTIONAL,
+ altGuaranteedBitRateInf Alt-RAB-Parameter-GuaranteedBitrateInf OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {Alt-RAB-Parameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Alt-RAB-Parameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 6 to indicate an alternative RAB configuration --
+ { ID id-AlternativeRABConfiguration CRITICALITY ignore EXTENSION RAB-Parameters PRESENCE optional }|
+ -- Extension for Release 7 to indicate an alternative list of Extended Guaranteed Bitrates --
+ { ID id-Alt-RAB-Parameter-ExtendedGuaranteedBitrateInf CRITICALITY ignore EXTENSION Alt-RAB-Parameter-ExtendedGuaranteedBitrateInf PRESENCE optional }|
+ -- Extension for Release 7 to indicate an alternative list of Extended Maximum Bitrates --
+ { ID id-Alt-RAB-Parameter-ExtendedMaxBitrateInf CRITICALITY ignore EXTENSION Alt-RAB-Parameter-ExtendedMaxBitrateInf PRESENCE optional }|
+ -- Extension for Release 8 to indicate an alternative list of Supported Maximum Bitrates --
+ { ID id-Alt-RAB-Parameter-SupportedMaxBitrateInf CRITICALITY reject EXTENSION Alt-RAB-Parameter-SupportedMaxBitrateInf PRESENCE optional }|
+ -- Extension for Release 8 to indicate an alternative list of Supported Guaranteed Bitrates --
+ { ID id-Alt-RAB-Parameter-SupportedGuaranteedBitrateInf CRITICALITY reject EXTENSION Alt-RAB-Parameter-SupportedGuaranteedBitrateInf PRESENCE optional },
+ ...
+}
+
+Alt-RAB-Parameter-ExtendedGuaranteedBitrateInf ::= SEQUENCE {
+ altExtendedGuaranteedBitrateType Alt-RAB-Parameter-GuaranteedBitrateType,
+ altExtendedGuaranteedBitrates Alt-RAB-Parameter-ExtendedGuaranteedBitrates OPTIONAL
+ -- This IE shall be present if the Type of Extended Guaranteed Bit Rates Information IE is set to "Value range" or "Discrete values" --,
+ ...
+}
+
+```
+
+```
+Alt-RAB-Parameter-ExtendedGuaranteedBitrates ::= SEQUENCE (SIZE (1..maxNrOfAltValues)) OF
+ Alt-RAB-Parameter-ExtendedGuaranteedBitrateList
+
+Alt-RAB-Parameter-ExtendedGuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedGuaranteedBitrate
+
+Alt-RAB-Parameter-GuaranteedBitrateInf ::= SEQUENCE {
+ altGuaranteedBitrateType Alt-RAB-Parameter-GuaranteedBitrateType,
+ altGuaranteedBitrates Alt-RAB-Parameter-GuaranteedBitrates OPTIONAL
+ -- This IE shall be present if the Type of Guaranteed Bit Rates Information IE is set to "Value range" or "Discrete values" --,
+ ...
+}
+
+Alt-RAB-Parameter-GuaranteedBitrateType ::= ENUMERATED{
+ unspecified,
+ value-range,
+ discrete-values,
+ ...
+}
+
+Alt-RAB-Parameter-GuaranteedBitrates ::= SEQUENCE (SIZE (1..maxNrOfAltValues)) OF
+ Alt-RAB-Parameter-GuaranteedBitrateList
+
+Alt-RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF GuaranteedBitrate
+
+Alt-RAB-Parameter-SupportedGuaranteedBitrateInf ::= SEQUENCE {
+ altSupportedGuaranteedBitrateType Alt-RAB-Parameter-GuaranteedBitrateType,
+ altSupportedGuaranteedBitrates Alt-RAB-Parameter-SupportedGuaranteedBitrates OPTIONAL
+ -- This IE shall be present if the Type of Supported Guaranteed Bit Rates Information IE is set to "Value range" or "Discrete values" --,
+ iE-Extensions ProtocolExtensionContainer { { Alt-RAB-Parameter-SupportedGuaranteedBitrateInf-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Alt-RAB-Parameter-SupportedGuaranteedBitrateInf-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Alt-RAB-Parameter-SupportedGuaranteedBitrates ::= SEQUENCE (SIZE (1..maxNrOfAltValues)) OF
+ SupportedRAB-ParameterBitrateList
+
+Alt-RAB-Parameter-ExtendedMaxBitrateInf ::= SEQUENCE {
+ altExtendedMaxBitrateType Alt-RAB-Parameter-MaxBitrateType,
+ altExtendedMaxBitrates Alt-RAB-Parameter-ExtendedMaxBitrates OPTIONAL
+ -- This IE shall be present if the Type of Extended Alternative Maximum Bit Rates Information IE is set to "Value range" or "Discrete values" --,
+ ...
+}
+
+Alt-RAB-Parameter-ExtendedMaxBitrates ::= SEQUENCE (SIZE (1..maxNrOfAltValues)) OF
+```
+
+```
+Alt-RAB-Parameter-ExtendedMaxBitrateList
+
+Alt-RAB-Parameter-ExtendedMaxBitrateList := SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedMaxBitrate
+
+Alt-RAB-Parameter-MaxBitrateInf := SEQUENCE {
+ altMaxBitrateType Alt-RAB-Parameter-MaxBitrateType,
+ altMaxBitrates Alt-RAB-Parameter-MaxBitrates OPTIONAL
+ -- This IE shall be present if the Type of Alternative Maximum Bit Rates Information IE is set to "Value range" or "Discrete values" --,
+ ...
+}
+
+Alt-RAB-Parameter-MaxBitrateType := ENUMERATED{
+ unspecified,
+ value-range,
+ discrete-values,
+ ...
+}
+
+Alt-RAB-Parameter-MaxBitrates := SEQUENCE (SIZE (1..maxNrOfAltValues)) OF
+ Alt-RAB-Parameter-MaxBitrateList
+
+Alt-RAB-Parameter-MaxBitrateList := SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF MaxBitrate
+
+Alt-RAB-Parameter-SupportedMaxBitrateInf := SEQUENCE {
+ altSupportedMaxBitrateType Alt-RAB-Parameter-MaxBitrateType,
+ altSupportedMaxBitrates Alt-RAB-Parameter-SupportedMaxBitrates OPTIONAL
+ -- This IE shall be present if the Type of Supported Alternative Maximum Bit Rates Information IE is set to "Value range" or "Discrete values" --,
+ iE-Extensions ProtocolExtensionContainer { { Alt-RAB-Parameter-SupportedMaxBitrateInf-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Alt-RAB-Parameter-SupportedMaxBitrateInf-ExtIEs RANAP-PROTOCOL-EXTENSION := {
+ ...
+}
+
+Alt-RAB-Parameter-SupportedMaxBitrates := SEQUENCE (SIZE (1..maxNrOfAltValues)) OF
+ SupportedRAB-ParameterBitrateList
+
+AlternativeRABConfigurationRequest := ENUMERATED{
+ alternative-RAB-configuration-Requested,
+ ...
+}
+
+APN := OCTET STRING (SIZE (1..255))
+-- Reference: 23.003
+
+AreaIdentity := CHOICE {
+```
+
+```
+
+ sAI SAI,
+ geographicalArea GeographicalArea,
+ ...
+}
+
+Ass-RAB-Parameters ::= SEQUENCE {
+ assMaxBitrateInf Ass-RAB-Parameter-MaxBitrateList OPTIONAL,
+ assGuaranteedBitRateInf Ass-RAB-Parameter-GuaranteedBitrateList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {Ass-RAB-Parameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Ass-RAB-Parameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate an extended assigned Guaranteed Bitrate --
+ { ID id-Ass-RAB-Parameter-ExtendedGuaranteedBitrateList CRITICALITY reject EXTENSION Ass-RAB-Parameter-ExtendedGuaranteedBitrateList
+ PRESENCE optional } |
+ -- Extension for Release 7 to indicate an extended assigned Maximum Bitrate --
+ { ID id-Ass-RAB-Parameter-ExtendedMaxBitrateList CRITICALITY reject EXTENSION Ass-RAB-Parameter-ExtendedMaxBitrateList PRESENCE
+ optional } |
+ -- Extension for Release 8 to indicate an supported assigned Maximum Bitrate --
+ { ID id-Ass-RAB-Parameter-SupportedMaxBitrateList CRITICALITY ignore EXTENSION SupportedRAB-ParameterBitrateList PRESENCE optional } |
+ -- Extension for Release 8 to indicate an supported assigned Guaranteed Bitrate --
+ { ID id-Ass-RAB-Parameter-SupportedGuaranteedBitrateList CRITICALITY ignore EXTENSION SupportedRAB-ParameterBitrateList PRESENCE
+ optional },
+ ...
+}
+
+Ass-RAB-Parameter-ExtendedGuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedGuaranteedBitrate
+
+Ass-RAB-Parameter-ExtendedMaxBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedMaxBitrate
+
+Ass-RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF GuaranteedBitrate
+
+Ass-RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF MaxBitrate
+
+AuthorisedPLMNs ::= SEQUENCE (SIZE (1..maxNrOfPLMNsSN)) OF
+ SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ authorisedSNAsList AuthorisedSNAs OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {AuthorisedPLMNs-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+AuthorisedPLMNs-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AuthorisedSNAs ::= SEQUENCE (SIZE (1..maxNrOfSNAs)) OF SNAC
+
+```
+
+-- B
+
+```
+BindingID ::= OCTET STRING (SIZE (4))
+
+BroadcastAssistanceDataDecipheringKeys ::= SEQUENCE {
+ cipheringKeyFlag BIT STRING (SIZE (1)),
+ currentDecipheringKey BIT STRING (SIZE (56)),
+ nextDecipheringKey BIT STRING (SIZE (56)),
+ ...
+}
+```
+
+-- C
+
+```
+Cause ::= CHOICE {
+ radioNetwork CauseRadioNetwork,
+ transmissionNetwork CauseTransmissionNetwork,
+ nAS CauseNAS,
+ protocol CauseProtocol,
+ misc CauseMisc,
+ non-Standard CauseNon-Standard,
+ ...,
+ radioNetworkExtension CauseRadioNetworkExtension
+}
+```
+
+```
+CauseMisc ::= INTEGER {
+ om-intervention (113),
+ no-resource-available (114),
+ unspecified-failure (115),
+ network-optimisation (116)
+} (113..128)
+```
+
+```
+CauseNAS ::= INTEGER {
+ user-restriction-start-indication (81),
+ user-restriction-end-indication (82),
+ normal-release (83),
+ csg-subscription-expiry(84)
+} (81..96)
+```
+
+```
+CauseProtocol ::= INTEGER {
+ transfer-syntax-error (97),
+ semantic-error (98),
+ message-not-compatible-with-receiver-state (99),
+ abstract-syntax-error-reject (100),
+ abstract-syntax-error-ignore-and-notify (101),
+ abstract-syntax-error-falsely-constructed-message (102)
+} (97..112)
+```
+
+```
+CauseRadioNetwork ::= INTEGER {
+ rab-pre-empted (1),
+ trelocoverall-expiry (2),
+ trelocprep-expiry (3),
+ treloccomplete-expiry (4),
+ tqueing-expiry (5),
+ relocation-triggered (6),
+ trellocalloc-expiry (7),
+ unable-to-establish-during-relocation (8),
+ unknown-target-rnc (9),
+ relocation-cancelled (10),
+ successful-relocation (11),
+ requested-ciphering-and-or-integrity-protection-algorithms-not-supported (12),
+ conflict-with-already-existing-integrity-protection-and-or-ciphering-information (13),
+ failure-in-the-radio-interface-procedure (14),
+ release-due-to-utran-generated-reason (15),
+ user-inactivity (16),
+ time-critical-relocation (17),
+ requested-traffic-class-not-available (18),
+ invalid-rab-parameters-value (19),
+ requested-maximum-bit-rate-not-available (20),
+ requested-guaranteed-bit-rate-not-available (21),
+ requested-transfer-delay-not-achievable (22),
+ invalid-rab-parameters-combination (23),
+ condition-violation-for-sdu-parameters (24),
+ condition-violation-for-traffic-handling-priority (25),
+ condition-violation-for-guaranteed-bit-rate (26),
+ user-plane-versions-not-supported (27),
+ iu-up-failure (28),
+ relocation-failure-in-target-CN-RNC-or-target-system (29),
+ invalid-RAB-ID (30),
+ no-remaining-rab (31),
+ interaction-with-other-procedure (32),
+ requested-maximum-bit-rate-for-dl-not-available (33),
+ requested-maximum-bit-rate-for-ul-not-available (34),
+ requested-guaranteed-bit-rate-for-dl-not-available (35),
+ requested-guaranteed-bit-rate-for-ul-not-available (36),
+ repeated-integrity-checking-failure (37),
+ requested-request-type-not-supported (38),
+ request-superseded (39),
+ release-due-to-UE-generated-signalling-connection-release (40),
+ resource-optimisation-relocation (41),
+ requested-information-not-available (42),
+ relocation-desirable-for-radio-reasons (43),
+ relocation-not-supported-in-target-RNC-or-target-system (44),
+ directed-retry (45),
+ radio-connection-with-UE-Lost (46),
+ rNC-unable-to-establish-all-RFCs (47),
+ deciphering-keys-not-available (48),
+ dedicated-assistance-data-not-available (49),
+}
+```
+
+```
+relocation-target-not-allowed (50),
+location-reporting-congestion (51),
+reduce-load-in-serving-cell (52),
+no-radio-resources-available-in-target-cell (53),
+gERAN-Iumode-failure (54),
+access-restricted-due-to-shared-networks (55),
+incomig-relocation-not-supported-due-to-PUESBINE-feature (56),
+traffic-load-in-the-target-cell-higher-than-in-the-source-cell (57),
+mBMS-no-multicast-service-for-this-UE (58),
+mBMS-unknown-UE-ID (59),
+successful-MBMS-session-start-no-data-bearer-necessary (60),
+mBMS-superseded-due-to-NNSF (61),
+mBMS-UE-linking-already-done (62),
+mBMS-UE-de-linking-failure-no-existing-UE-linking (63),
+tMGI-unknown (64)
+} (1..64)
+
+CauseRadioNetworkExtension ::= INTEGER {
+ iP-multicast-address-and-APN-not-valid (257),
+ mBMS-de-registration-rejected-due-to-implicit-registration (258),
+ mBMS-request-superseded (259),
+ mBMS-de-registration-during-session-not-allowed (260),
+ mBMS-no-data-bearer-necessary (261),
+ periodicLocationInformationNotAvailable (262),
+ gTP-Resources-Unavailable (263),
+ tMGI-inUse-overlapping-MBMS-service-area (264),
+ mBMS-no-cell-in-MBMS-service-area (265),
+ no-Iu-CS-UP-relocation (266),
+ successful-MBMS-Session-Start-IP-Multicast-Bearer-established (267),
+ cS-fallback-triggered (268),
+ invalid-CSG-Id (269)
+} (257..512)
+
+CauseNon-Standard ::= INTEGER (129..256)
+-- Cause value 256 shall not be used --
+
+CauseTransmissionNetwork ::= INTEGER {
+ signalling-transport-resource-failure (65),
+ iu-transport-connection-failed-to-establish (66)
+} (65..80)
+
+Cell-Access-Mode ::= ENUMERATED {
+ hybrid,
+ ...
+}
+
+CellBased ::= SEQUENCE {
+ cellIdList CellIdList,
+ iE-Extensions ProtocolExtensionContainer { {CellBased-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ }
+
+CellBased-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellIdList ::= SEQUENCE (SIZE (1..maxNrOfCellIds)) OF
+ Cell-Id
+
+Cell-Id ::= INTEGER (0..268435455)
+
+Cell-Capacity-Class-Value ::= INTEGER (1..100,...)
+
+CellLoadInformation ::= SEQUENCE {
+ cell-Capacity-Class-Value Cell-Capacity-Class-Value,
+ loadValue LoadValue,
+ rTLoadValue RTLoadValue OPTIONAL,
+ nRTLoadInformationValue NRTLoadInformationValue OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CellLoadInformation-ExtIEs } } OPTIONAL,
+ ...
+}
+
+CellLoadInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellLoadInformationGroup ::= SEQUENCE {
+ sourceCellID SourceCellID,
+ uplinkCellLoadInformation CellLoadInformation OPTIONAL,
+ downlinkCellLoadInformation CellLoadInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CellLoadInformationGroup-ExtIEs } } OPTIONAL,
+ ...
+}
+
+CellLoadInformationGroup-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellType ::= ENUMERATED {
+ macro,
+ micro,
+ pico,
+ femto,
+ ...
+}
+
+ClientType ::= ENUMERATED {
+ emergency-Services,
+ value-Added-Services,
+ pLMN-Operator-Services,
+```
+
+```
+lawful-Intercept-Services,
+pLMN-Operator-Broadcast-Services,
+pLMN-Operator-O-et-M,
+pLMN-Operator-Anonymous-Statistics,
+pLMN-Operator-Target-MS-Service-Support,
+...
+}
+
+CriticalityDiagnostics ::= SEQUENCE {
+ procedureCode ProcedureCode OPTIONAL,
+ triggeringMessage TriggeringMessage OPTIONAL,
+ procedureCriticality Criticality OPTIONAL,
+ iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CriticalityDiagnostics-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF
+ SEQUENCE {
+ iECriticality Criticality,
+ iE-ID ProtocolIE-ID,
+ repetitionNumber RepetitionNumber0 OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+CriticalityDiagnostics-IE-List-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 99 to enable reporting the message structure down to the erroneous IE --
+ { ID id-MessageStructure CRITICALITY ignore EXTENSION MessageStructure PRESENCE optional } |
+ -- Extension for Release 99 to enable reporting if a reported error is due to a not understood or a missing IE --
+ { ID id-TypeOfError CRITICALITY ignore EXTENSION TypeOfError PRESENCE mandatory },
+ ...
+}
+
+MessageStructure ::= SEQUENCE (SIZE (1..maxNrOfLevels)) OF
+ SEQUENCE {
+ iE-ID ProtocolIE-ID,
+ repetitionNumber RepetitionNumber1 OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {MessageStructure-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+MessageStructure-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+CGI ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ LAC LAC,
+ CI CI,
+ iE-Extensions ProtocolExtensionContainer { {CGI-ExtIEs} } OPTIONAL
+}
+
+CGI-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 6 to enable Inter-RAT PS Handover between UTRAN and GERAN A/Gb --
+ { ID id-RAC CRITICALITY ignore EXTENSION RAC PRESENCE optional },
+ ...
+}
+
+ChosenEncryptionAlgorithm ::= EncryptionAlgorithm
+
+ChosenIntegrityProtectionAlgorithm ::= IntegrityProtectionAlgorithm
+
+CI ::= OCTET STRING (SIZE (2))
+
+ClassmarkInformation2 ::= OCTET STRING
+
+ClassmarkInformation3 ::= OCTET STRING
+
+CN-DomainIndicator ::= ENUMERATED {
+ cs-domain,
+ ps-domain
+}
+
+CN-ID ::= INTEGER (0..4095)
+
+Correlation-ID ::= OCTET STRING (SIZE (4))
+
+CSFB-Information ::= ENUMERATED {
+ csfb,
+ csfb-high-priority,
+ ...
+}
+
+CSG-Id ::= BIT STRING (SIZE (27))
+
+CSG-Id-List ::= SEQUENCE (SIZE (1..maxNrOfCSGs)) OF
+ CSG-Id
+
+CSG-Membership-Status ::= ENUMERATED {
+ member,
+ non-member,
+ ...
+}
+
+-- D
+```
+
+```
+
+DataPDUType ::= ENUMERATED {
+ pDUType0,
+ pDUType1,
+ ...
+}
+
+DataVolumeReference ::= INTEGER (0..255)
+
+DataVolumeReportingIndication ::= ENUMERATED {
+ do-report,
+ do-not-report
+}
+
+DCH-ID ::= INTEGER (0..255)
+
+DeliveryOfErroneousSDU ::= ENUMERATED {
+ yes,
+ no,
+ no-error-detection-consideration
+}
+
+DeliveryOrder ::= ENUMERATED {
+ delivery-order-requested,
+ delivery-order-not-requested
+}
+
+DeltaRAListofIdleModeUEs ::= SEQUENCE {
+ newRAListofIdleModeUEs NewRAListofIdleModeUEs OPTIONAL,
+ rAListwithNoIdleModeUEsAnyMore RAListwithNoIdleModeUEsAnyMore OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {DeltaRAListofIdleModeUEs-ExtIEs} } OPTIONAL
+}
+
+NewRAListofIdleModeUEs ::= SEQUENCE (SIZE (1..maxMBMSRA)) OF
+ RAC
+
+RAListwithNoIdleModeUEsAnyMore ::= SEQUENCE (SIZE (1..maxMBMSRA)) OF
+ RAC
+
+DeltaRAListofIdleModeUEs-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-newRAListofIdleModeUEs CRITICALITY reject EXTENSION LAListofIdleModeUEs PRESENCE conditional } |
+ -- This IE shall be present if the New RA List of Idle Mode UEs IE is included. --
+ { ID id-LAListwithNoIdleModeUEsAnyMore CRITICALITY reject EXTENSION LAListofIdleModeUEs PRESENCE conditional },
+ -- This IE shall be present if the RA List with No Idle Mode UEs Any More IE is included. --
+ ...
+}
+
+ForwardingIndication ::= ENUMERATED {
+ forwarding-admitted,
+ ...
+}
+
+```
+
+```
+ }
+
+ DL-GTP-PDU-SequenceNumber ::= INTEGER (0..65535)
+
+ DL-N-PDU-SequenceNumber ::= INTEGER (0..65535)
+
+ D-RNTI ::= INTEGER (0..1048575)
+
+ DRX-CycleLengthCoefficient ::= INTEGER (6..9)
+
+ DSCH-ID ::= INTEGER (0..255)
+
+ -- E
+
+ EARFCN-Extended ::= INTEGER (65536..262143, ...)
+
+ E-DCH-MAC-d-Flow-ID ::= INTEGER (0.. maxNrOfEDCHMACdFlows-1)
+
+ ENB-ID ::= CHOICE {
+ macroENB-ID BIT STRING (SIZE(20)),
+ homeENB-ID BIT STRING (SIZE(28)),
+ ...
+ }
+
+ EncryptionAlgorithm ::= INTEGER { no-encryption (0), standard-UMTS-encryption-algorithm-UEA1 (1), standard-UMTS-encryption-algorithm-UEA2 (2) } (0..15)
+
+ EncryptionInformation ::= SEQUENCE {
+ permittedAlgorithms PermittedEncryptionAlgorithms,
+ key EncryptionKey,
+ iE-Extensions ProtocolExtensionContainer { {EncryptionInformation-ExtIEs} } OPTIONAL
+ }
+
+ EncryptionInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ EncryptionKey ::= BIT STRING (SIZE (128))
+ -- Reference: 33.102
+
+ End-Of-CSFB ::= ENUMERATED{
+ end-of-CSFB,
+ ...
+ }
+
+ EquipmentsToBeTraced ::= CHOICE {
+ iMEIlist IMEIList,
+ iMEISVlist IMEISVList,
+ iMEIgroup IMEIGroup,
+ }
+```
+
+```
+ iMEISVgroup IMEISVGroup,
+ ...
+}
+
+E-UTRAN-Service-Handover ::= ENUMERATED {
+ handover-to-E-UTRAN-shall-not-be-performed,
+ ...
+}
+
+Event ::= ENUMERATED {
+ stop-change-of-service-area,
+ direct,
+ change-of-servicearea,
+ ...,
+ stop-direct,
+ periodic,
+ stop-periodic
+}
+
+Event1F-Parameters ::= SEQUENCE {
+ measurementQuantity MeasurementQuantity,
+ threshold INTEGER(-120..165),
+ ...
+}
+
+Event1I-Parameters ::= SEQUENCE {
+ threshold INTEGER(-120..-25),
+ ...
+}
+
+ExtendedGuaranteedBitrate ::= INTEGER (16000001..256000000)
+-- Unit is bits per sec
+
+ExtendedMaxBitrate ::= INTEGER (16000001..256000000)
+-- Unit is bits per sec
+
+ExtendedRNC-ID ::= INTEGER (4096..65535)
+
+-- F
+
+FrameSequenceNumber ::= INTEGER(0..15)
+
+FrequencyLayerConvergenceFlag ::= ENUMERATED {
+ no-FLC-flag,
+ ...
+}
+
+-- G
+
+GANSS-PositioningDataSet ::= SEQUENCE(SIZE(1..maxGANSSSet)) OF GANSS-PositioningMethodAndUsage
+```
+
+```
+GANSS-PositioningMethodAndUsage ::= OCTET STRING (SIZE(1))
+
+GeographicalArea ::= CHOICE {
+ point GA-Point,
+ pointWithUncertainty GA-PointWithUncertainty,
+ polygon GA-Polygon,
+ ...,
+ pointWithUncertaintyEllipse GA-PointWithUncertaintyEllipse,
+ pointWithAltitude GA-PointWithAltitude,
+ pointWithAltitudeAndUncertaintyEllipsoid GA-PointWithAltitudeAndUncertaintyEllipsoid,
+ ellipsoidArc GA-EllipsoidArc
+}
+
+GeographicalCoordinates ::= SEQUENCE {
+ latitudeSign ENUMERATED { north, south },
+ latitude INTEGER (0..8388607),
+ longitude INTEGER (-8388608..8388607),
+ iE-Extensions ProtocolExtensionContainer { {GeographicalCoordinates-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GeographicalCoordinates-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-AltitudeAndDirection ::= SEQUENCE {
+ directionOfAltitude ENUMERATED {height, depth},
+ altitude INTEGER (0..32767),
+ ...
+}
+
+GA-EllipsoidArc ::= SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ innerRadius INTEGER (0..65535),
+ uncertaintyRadius INTEGER (0..127),
+ offsetAngle INTEGER (0..179),
+ includedAngle INTEGER (0..179),
+ confidence INTEGER (0..127),
+ iE-Extensions ProtocolExtensionContainer { { GA-EllipsoidArc-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GA-EllipsoidArc-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-Point ::= SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ iE-Extensions ProtocolExtensionContainer { {GA-Point-ExtIEs} } OPTIONAL,
+}
+```
+
+```
+ ...
+}
+
+GA-Point-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-PointWithAltitude ::= SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ altitudeAndDirection GA-AltitudeAndDirection,
+ iE-Extensions ProtocolExtensionContainer { { GA-PointWithAltitude-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GA-PointWithAltitude-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-PointWithAltitudeAndUncertaintyEllipsoid ::= SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ altitudeAndDirection GA-AltitudeAndDirection,
+ uncertaintyEllipse GA-UncertaintyEllipse,
+ uncertaintyAltitude INTEGER (0..127),
+ confidence INTEGER (0..127),
+ iE-Extensions ProtocolExtensionContainer { { GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-PointWithUncertainty ::= SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ iE-Extensions ProtocolExtensionContainer { { GA-PointWithUncertainty-ExtIEs} } OPTIONAL,
+ uncertaintyCode INTEGER (0..127)
+}
+
+GA-PointWithUncertainty-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-PointWithUncertaintyEllipse ::= SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ uncertaintyEllipse GA-UncertaintyEllipse,
+ confidence INTEGER (0..127),
+ iE-Extensions ProtocolExtensionContainer { { GA-PointWithUncertaintyEllipse-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+GA-PointWithUncertaintyEllipse-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-Polygon ::= SEQUENCE (SIZE (1..maxNrOfPoints)) OF
+ SEQUENCE {
+ geographicalCoordinates GeographicalCoordinates,
+ iE-Extensions ProtocolExtensionContainer { {GA-Polygon-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+GA-Polygon-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GA-UncertaintyEllipse ::= SEQUENCE {
+ uncertaintySemi-major INTEGER (0..127),
+ uncertaintySemi-minor INTEGER (0..127),
+ orientationOfMajorAxis INTEGER (0..179), -- The values 90..179 shall not be used.
+ ...
+}
+
+GERAN-BSC-Container ::= OCTET STRING
+ -- GERAN BSC Container as defined in TS 48.008 [11] --
+
+GERAN-Cell-ID ::= SEQUENCE {
+ LAI LAI,
+ rAC RAC,
+ CI CI,
+ iE-Extensions ProtocolExtensionContainer { {GERAN-Cell-ID-ExtIEs} } OPTIONAL
+}
+
+GERAN-Cell-ID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GERAN-Classmark ::= OCTET STRING
+ -- GERAN Classmark as defined in TS 48.008 [11] --
+
+GlobalCN-ID ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ cN-ID CN-ID
+}
+
+GlobalRNC-ID ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ rNC-ID RNC-ID
+}
+```
+
+```
+GTP-TEI ::= OCTET STRING (SIZE (4))
+
+GuaranteedBitrate ::= INTEGER (0..16000000)
+-- Unit is bits per sec
+
+-- H
+
+HigherBitratesThan16MbpsFlag ::= ENUMERATED{
+ allowed,
+ not-allowed,
+ ...
+}
+
+HS-DSCH-MAC-d-Flow-ID ::= INTEGER (0.. maxNrOfHSDSCHMACdFlows-1)
+
+-- I
+
+IMEI ::= OCTET STRING (SIZE (8))
+-- Reference: 23.003
+
+IMEIGroup ::= SEQUENCE {
+ iMEI IMEI,
+ iMEIMask BIT STRING (SIZE (7)),
+ iE-Extensions ProtocolExtensionContainer { { IMEIGroup-ExtIEs} } OPTIONAL
+}
+
+IMEIGroup-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IMEIList ::= SEQUENCE (SIZE (1..maxNrOfUEsToBeTraced)) OF IMEI
+
+IMEISV ::= OCTET STRING (SIZE (8))
+-- Reference: 23.003
+
+IMEISVGroup ::= SEQUENCE {
+ iMEISV IMEISV,
+ iMEISVMask BIT STRING (SIZE (7)),
+ iE-Extensions ProtocolExtensionContainer { { IMEISVGroup-ExtIEs} } OPTIONAL
+}
+
+IMEISVGroup-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IMEISVList ::= SEQUENCE (SIZE (1..maxNrOfUEsToBeTraced)) OF IMEISV
+
+ImmediateMDT ::= SEQUENCE {
+```
+
+```
+
+ measurementsToActivate MeasurementsToActivate,
+ m1report M1Report OPTIONAL,
+ -- Included in case of event-triggered reporting for measurement M1
+ m2report M2Report OPTIONAL,
+ -- Included in case of event-triggered reporting for measurement M2
+ ...,
+ iE-Extensions ProtocolExtensionContainer { { ImmediateMDT-ExtIEs } } OPTIONAL
+}
+
+ImmediateMDT-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ {ID id-M4Report CRITICALITY ignore EXTENSION M4Report PRESENCE optional}|
+ -- Included in case that measurement M4 is activated
+ {ID id-M5Report CRITICALITY ignore EXTENSION M5Report PRESENCE optional}|
+ -- Included in case that measurement M5 is activated
+ {ID id-M6Report CRITICALITY ignore EXTENSION M6Report PRESENCE optional}|
+ -- Included in case that measurement M6 is activated
+ {ID id-M7Report CRITICALITY ignore EXTENSION M7Report PRESENCE optional}|
+ -- Included in case that measurement M7 is activated
+ ...
+}
+
+IMSI ::= TBCD-STRING (SIZE (3..8))
+-- Reference: 23.003
+
+IncludeVelocity ::= ENUMERATED {
+ requested
+}
+
+InformationExchangeID ::= INTEGER (0.. 1048575)
+
+InformationExchangeType ::= ENUMERATED {
+ transfer,
+ request,
+ ...
+}
+
+InformationRequested ::= CHOICE {
+ requestedMBMSIPMulticastAddressandAPNRequest RequestedMBMSIPMulticastAddressandAPNRequest,
+ requestedMulticastServiceList RequestedMulticastServiceList,
+ ...
+}
+
+InformationRequestType ::= CHOICE {
+ mBMSIPMulticastAddressandAPNRequest MBMSIPMulticastAddressandAPNRequest,
+ permanentNAS-UE-ID PermanentNAS-UE-ID,
+ ...
+}
+
+InformationTransferID ::= INTEGER (0.. 1048575)
+
+```
+
+```
+InformationTransferType ::= CHOICE {
+ rNCTraceInformation RNCTraceInformation,
+ ...
+}
+
+IntegrityProtectionAlgorithm ::= INTEGER {
+ standard-UMTS-integrity-algorithm-UIA1 (0), standard-UMTS-integrity-algorithm-UIA2 (1),
+ no-value (15)
+} (0..15)
+
+IntegrityProtectionInformation ::= SEQUENCE {
+ permittedAlgorithms PermittedIntegrityProtectionAlgorithms,
+ key IntegrityProtectionKey,
+ iE-Extensions ProtocolExtensionContainer { { IntegrityProtectionInformation-ExtIEs } } OPTIONAL
+}
+
+IntegrityProtectionInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IntegrityProtectionKey ::= BIT STRING (SIZE (128))
+
+InterSystemInformationTransferType ::= CHOICE {
+ rIM-Transfer RIM-Transfer,
+ ...
+}
+
+InterSystemInformation-TransparentContainer ::= SEQUENCE {
+ downlinkCellLoadInformation CellLoadInformation OPTIONAL,
+ uplinkCellLoadInformation CellLoadInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { InterSystemInformation-TransparentContainer-ExtIEs } } OPTIONAL,
+ ...
+}
+
+InterSystemInformation-TransparentContainer-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IPMulticastAddress ::= OCTET STRING (SIZE (4..16))
+-- Reference: 23.003
+
+IuSignallingConnectionIdentifier ::= BIT STRING (SIZE (24))
+
+IuTransportAssociation ::= CHOICE {
+ gTP-TEI GTP-TEI,
+ bindingID BindingID,
+ ...
+}
+```
+
+-- J
+-- K
+
+KeyStatus := ENUMERATED {
+ old,
+ new,
+ ...
+}
+-- L
+
+LA-LIST := SEQUENCE (SIZE (1..maxNrOfLAs)) OF
+ SEQUENCE {
+ LAC LAC,
+ listOf-SNAs ListOf-SNAs,
+ iE-Extensions ProtocolExtensionContainer { { LA-LIST-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+LA-LIST-ExtIEs RANAP-PROTOCOL-EXTENSION := {
+ ...
+}
+
+LAC := OCTET STRING (SIZE (2))
+
+LAI := SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ LAC LAC,
+ iE-Extensions ProtocolExtensionContainer { { LAI-ExtIEs} } OPTIONAL
+}
+
+LAI-ExtIEs RANAP-PROTOCOL-EXTENSION := {
+ ...
+}
+
+LastKnownServiceArea := SEQUENCE {
+ SAI SAI,
+ ageOfSAI INTEGER (0..32767),
+ iE-Extensions ProtocolExtensionContainer { { LastKnownServiceArea-ExtIEs} } OPTIONAL,
+ ...
+}
+
+LastKnownServiceArea-ExtIEs RANAP-PROTOCOL-EXTENSION := {
+ ...
+}
+
+LastVisitedUTRANCell-Item := SEQUENCE {
+ uTRAN-CellID UTRAN-CellID,
+ cellType CellType,
+ time-UE-StayedInCell Time-UE-StayedInCell,
+ iE-Extensions ProtocolExtensionContainer { { LastVisitedUTRANCell-Item-ExtIEs} } OPTIONAL,
+
+```
+
+ ...
+ }
+
+ LastVisitedUTRANCell-Item-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Rel-11 to support enhanced granularity for time UE stayed in cell --
+ { ID id-Time-UE-StayedInCell-EnhancedGranularity CRITICALITY ignore EXTENSION Time-UE-StayedInCell-EnhancedGranularity PRESENCE optional }|
+ { ID id-HO-Cause CRITICALITY ignore EXTENSION Cause PRESENCE optional },
+ ...
+ }
+
+ Links-to-log ::= ENUMERATED {uplink, downlink, both-uplink-and-downlink, ...}
+
+ ListOf-SNAs ::= SEQUENCE (SIZE (1..maxNrOfSNAs)) OF SNAC
+
+ ListOfInterfacesToTrace ::= SEQUENCE (SIZE (1..maxNrOfInterfaces)) OF InterfacesToTraceItem
+
+ InterfacesToTraceItem ::= SEQUENCE {
+ interface ENUMERATED {iu-cs, iu-ps, iur, iub, uu, ...},
+ iE-Extensions ProtocolExtensionContainer { {InterfacesToTraceItem-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ InterfacesToTraceItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ LoadValue ::= INTEGER (0..100)
+
+ LocationRelatedDataRequestType ::= SEQUENCE {
+ requestedLocationRelatedDataType RequestedLocationRelatedDataType,
+ requestedGPSAssistanceData RequestedGPSAssistanceData OPTIONAL,
+ -- This IE shall be present if the Requested Location Related Data Type IE is set to 'Dedicated Assistance Data for Assisted GPS' or
+ -- 'Dedicated Assistance Data for Assisted GPS and GANSS'
+ ...
+ }
+
+ LocationRelatedDataRequestTypeSpecificToGERANIuMode ::= ENUMERATED {
+ decipheringKeysEOTD,
+ dedicatedMobileAssistedEOTDAssistanceData,
+ dedicatedMobileBasedEOTDAssistanceData,
+ ...
+ }
+
+ LocationReportingTransferInformation ::= SEQUENCE {
+ reportChangeOfSAI ReportChangeOfSAI OPTIONAL,
+ periodicReportingIndicator PeriodicReportingIndicator OPTIONAL,
+ directReportingIndicator DirectReportingIndicator OPTIONAL,
+ verticalAccuracyCode VerticalAccuracyCode OPTIONAL,
+ positioningPriorityChangeSAI PositioningPriority OPTIONAL,
+ positioningPriorityDirect PositioningPriority OPTIONAL,
+ }
+
+```
+
+```
+ clientTypePeriodic ClientType OPTIONAL,
+ clientTypeDirect ClientType OPTIONAL,
+ responseTime ResponseTime OPTIONAL,
+ includeVelocity IncludeVelocity OPTIONAL,
+ periodicLocationInfo PeriodicLocationInfo OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { LocationReportingTransferInformation-ExtIEs } } OPTIONAL,
+ ...
+ }
+
+ LocationReportingTransferInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ ReportChangeOfSAI ::= ENUMERATED {
+ requested,
+ ...
+ }
+
+ PeriodicReportingIndicator ::= ENUMERATED {
+ periodicSAI,
+ periodicGeo,
+ ...
+ }
+
+ DirectReportingIndicator ::= ENUMERATED {
+ directSAI,
+ directGeo,
+ ...
+ }
+
+ L3-Information ::= OCTET STRING
+
+ -- M
+
+ M1Report ::= CHOICE {
+ periodic MDT-Report-Parameters,
+ event1F Event1F-Parameters,
+ ...
+ }
+
+ M2Report ::= CHOICE {
+ periodic MDT-Report-Parameters,
+ event1I Event1I-Parameters,
+ ...
+ }
+
+ M4Report ::= CHOICE {
+ all NULL,
+ m4-collection-parameters M4-Collection-Parameters,
+ ...
+ }
+```
+
+```
+ }
+
+M4-Collection-Parameters ::= SEQUENCE {
+ m4-period M4-Period,
+ m4-threshold M4-Threshold OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { M4-Collection-Parameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M4-Collection-Parameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+M4-Period ::= ENUMERATED {ms100, ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ...}
+
+M4-Threshold ::= INTEGER (0..31)
+
+M5Report ::= CHOICE {
+ when-available NULL,
+ m5-period M5-Period,
+ ...
+}
+
+M5-Period ::= ENUMERATED {ms100, ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ...}
+
+M6Report ::= SEQUENCE {
+ m6-period M6-Period,
+ m6-links-to-log Links-to-log,
+ iE-Extensions ProtocolExtensionContainer { { M6Report-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M6Report-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+M6-Period ::= ENUMERATED {ms1000, ms2000, ms3000, ms4000, ms6000, ms8000, ms12000, ms16000, ms20000, ms24000, ms28000, ms32000, ms64000, ...}
+
+M7Report ::= SEQUENCE {
+ m7-period M7-Period,
+ m7-links-to-log Links-to-log,
+ iE-Extensions ProtocolExtensionContainer { { M7Report-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M7Report-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+
+M7-Period ::= ENUMERATED {ms1000, ms2000, ms3000, ms4000, ms6000, ms8000, ms12000, ms16000, ms20000, ms24000, ms28000, ms32000, ms64000, ...}
+
+Management-Based-MDT-Allowed ::= ENUMERATED {
+ allowed, ... }
+
+MaxBitrate ::= INTEGER (1..16000000)
+-- Unit is bits per sec
+
+MaxSDU-Size ::= INTEGER (0..32768)
+-- MaxSDU-Size
+-- Unit is bit
+
+MBMS-PTP-RAB-ID ::= BIT STRING (SIZE (8))
+
+MBMSBearerServiceType ::= ENUMERATED {
+ multicast,
+ broadcast,
+ ...
+}
+
+MBMSCNDe-Registration ::= ENUMERATED {
+ normalsessionstop,
+ deregister,
+ ...
+}
+
+MBMSCountingInformation ::= ENUMERATED {
+ counting,
+ notcounting,
+ ...
+}
+
+MBMSHCIndicator ::= ENUMERATED {
+ uncompressed-header,
+ compressed-header,
+ ...
+}
+
+MBMSIPMulticastAddressandAPNRequest ::= SEQUENCE (SIZE (1..maxnoofMulticastServicesPerRNC)) OF
+ TMGI
+
+MBMSLinkingInformation ::= ENUMERATED {
+ uE-has-joined-multicast-services,
+ ...
+}
+
+MBMSRegistrationRequestType ::= ENUMERATED {
+```
+
+```
+
+ register,
+ deregister,
+ ...
+ }
+
+ MBMSServiceArea ::= OCTET STRING
+
+ MBMSSessionDuration ::= OCTET STRING (SIZE (3))
+
+ MBMSSessionIdentity ::= OCTET STRING (SIZE (1))
+
+ MBMSSessionRepetitionNumber ::= OCTET STRING (SIZE (1))
+
+ MDT-Activation ::= ENUMERATED { immediateMDTonly,
+ loggedMDTonly,
+ immediateMDTandTrace,
+ ... }
+
+ MDTAreaScope ::= CHOICE {
+ cellbased CellBased,
+ labased LABased,
+ rabased RABased,
+ plmn-area-based NULL,
+ ...
+ }
+
+ MDT-Configuration ::= SEQUENCE {
+ mdtActivation MDT-Activation,
+ mdtAreaScope MDTAreaScope,
+ mdtMode MDTMode,
+ iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ MDT-Configuration-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-SignallingBasedMDTPLMNList CRITICALITY ignore EXTENSION MDT-PLMN-List PRESENCE optional },
+ ...
+ }
+
+ MDTMode ::= CHOICE {
+ immediateMDT ImmediateMDT,
+ loggedMDT LoggedMDT,
+ ...
+ }
+
+ MDT-PLMN-List ::= SEQUENCE (SIZE (1..maxnoofMDTPLMNs)) OF
+ PLMNidentity
+
+```
+
+```
+MDT-Report-Parameters ::= SEQUENCE {
+ reportInterval ReportInterval,
+ reportAmount ReportAmount,
+ ...
+}
+
+MeasurementQuantity ::= ENUMERATED {
+ cpichEcNo,
+ cpichRSCP,
+ pathloss,
+ ...
+}
+
+MeasurementsToActivate ::= BIT STRING (SIZE (8))
+
+MSISDN ::= OCTET STRING (SIZE (1..9))
+
+-- N
+
+NAS-PDU ::= OCTET STRING
+
+NAS-SequenceNumber ::= BIT STRING (SIZE (2))
+-- Reference: 24.008
+
+NAS-SynchronisationIndicator ::= BIT STRING (SIZE (4))
+
+NewBSS-To-OldBSS-Information ::= OCTET STRING
+
+NonSearchingIndication ::= ENUMERATED {
+ non-searching,
+ searching
+}
+
+NRTLoadInformationValue ::= INTEGER (0..3)
+
+NumberOfIuInstances ::= INTEGER (1..2)
+
+NumberOfSteps ::= INTEGER (1..16)
+
+-- O
+
+Offload-RAB-Parameters ::= SEQUENCE {
+ accessPointName Offload-RAB-Parameters-APN,
+ chargingCharacteristics Offload-RAB-Parameters-ChargingCharacteristics,
+ iE-Extensions ProtocolExtensionContainer { { Offload-RAB-Parameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Offload-RAB-Parameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+
+ ...
+}
+
+Offload-RAB-Parameters-APN ::= OCTET STRING (SIZE (1..255))
+
+Offload-RAB-Parameters-ChargingCharacteristics ::= OCTET STRING (SIZE (2))
+
+OldBSS-ToNewBSS-Information ::= OCTET STRING
+
+OMC-ID ::= OCTET STRING (SIZE (3..22))
+-- Reference: GSM TS 12.20 [25]
+
+Out-Of-UTRAN ::= ENUMERATED{
+ cell-reselection-to-EUTRAN,
+ ...
+}
+
+-- P
+
+PagingAreaID ::= CHOICE {
+ LAI LAI,
+ rAI RAI,
+ ...
+}
+
+PagingCause ::= ENUMERATED {
+ terminating-conversational-call,
+ terminating-streaming-call,
+ terminating-interactive-call,
+ terminating-background-call,
+ terminating-low-priority-signalling,
+ ...,
+ terminating-high-priority-signalling
+}
+
+PDP-TypeInformation ::= SEQUENCE (SIZE (1..maxNrOfPDPDirections)) OF
+ PDP-Type
+
+PDP-Type ::= ENUMERATED {
+ empty,
+ ppp,
+ osp-ihoss -- this value shall not be used -- ,
+ ipv4,
+ ipv6,
+ ...
+}
+
+PDP-TypeInformation-extension ::= SEQUENCE (SIZE (1..maxNrOfPDPDirections)) OF
+ PDP-Type-extension
+
+PDP-Type-extension ::= ENUMERATED {
+
+```
+
+```
+ ipv4-and-ipv6,
+ ...
+}
+
+PDUType14FrameSequenceNumber := INTEGER(0..3)
+
+PeriodicLocationInfo := SEQUENCE {
+ reportingAmount INTEGER (1..8639999, ...),
+ reportingInterval INTEGER (1..8639999, ...),
+ iE-Extensions ProtocolExtensionContainer { { PeriodicLocationInfo-ExtIEs } } OPTIONAL,
+ ...
+}
+
+PeriodicLocationInfo-ExtIEs RANAP-PROTOCOL-EXTENSION := {
+ ...
+}
+
+PermanentNAS-UE-ID := CHOICE {
+ IMSI IMSI,
+ ...
+}
+
+PermittedEncryptionAlgorithms := SEQUENCE (SIZE (1..16)) OF
+ EncryptionAlgorithm
+
+PermittedIntegrityProtectionAlgorithms := SEQUENCE (SIZE (1..16)) OF
+ IntegrityProtectionAlgorithm
+
+LABased := SEQUENCE {
+ laiList LAI-List,
+ iE-Extensions ProtocolExtensionContainer { { LABased-ExtIEs } } OPTIONAL,
+ ...
+}
+
+LABased-ExtIEs RANAP-PROTOCOL-EXTENSION := {
+ ...
+}
+
+LAI-List := SEQUENCE (SIZE (1..maxNrOfLAIs)) OF
+ LAI
+
+LoggedMDT := SEQUENCE {
+ loggingInterval LoggingInterval,
+ loggingDuration LoggingDuration,
+ iE-Extensions ProtocolExtensionContainer { { LoggedMDT-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+ }
+
+ LoggedMDT-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ LoggingInterval ::= ENUMERATED {
+ s1d28,
+ s2d56,
+ s5d12,
+ s10d24,
+ s20d48,
+ s30d72,
+ s40d96,
+ s61d44,
+ ...
+ }
+
+ LoggingDuration ::= ENUMERATED {
+ min10,
+ min20,
+ min40,
+ min60,
+ min90,
+ min120,
+ ...
+ }
+
+ PLMNIdentity ::= TBCD-STRING (SIZE (3))
+
+ PLMNs-in-shared-network ::= SEQUENCE (SIZE (1..maxNrOfPLMNsSN)) OF
+ SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ lA-LIST lA-LIST,
+ iE-Extensions ProtocolExtensionContainer { { PLMNs-in-shared-network-ExtIEs } } OPTIONAL,
+ ...
+ }
+
+ PLMNs-in-shared-network-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ Port-Number ::= OCTET STRING (SIZE (2))
+
+ PositioningDataDiscriminator ::= BIT STRING (SIZE (4))
+
+ PositioningDataSet ::= SEQUENCE (SIZE (1..maxSet)) OF PositioningMethodAndUsage
+
+ PositioningMethodAndUsage ::= OCTET STRING (SIZE (1))
+```
+
+```
+PositioningPriority ::= ENUMERATED {
+ high-Priority,
+ normal-Priority,
+ ...
+}
+
+PositionData ::= SEQUENCE {
+ positioningDataDiscriminator PositioningDataDiscriminator,
+ positioningDataSet PositioningDataSet OPTIONAL,
+ -- This IE shall be present if the PositioningDataDiscriminator IE is set to the value "0000" --
+ iE-Extensions ProtocolExtensionContainer { {PositionData-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PositionData-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-GANSS-PositioningDataSet CRITICALITY ignore EXTENSION GANSS-PositioningDataSet PRESENCE optional },
+ ...
+}
+
+PositionDataSpecificToGERANIuMode ::= OCTET STRING
+
+Pre-emptionCapability ::= ENUMERATED {
+ shall-not-trigger-pre-emption,
+ may-trigger-pre-emption
+}
+
+Pre-emptionVulnerability ::= ENUMERATED {
+ not-pre-emptable,
+ pre-emptable
+}
+
+PriorityLevel ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15)
+
+Priority-Class-Indicator ::= BIT STRING (SIZE(8))
+
+ProvidedData ::= CHOICE {
+ shared-network-information Shared-Network-Information,
+ ...
+}
+
+P-TMSI ::= OCTET STRING (SIZE (4))
+
+-- Q
+
+QueuingAllowed ::= ENUMERATED {
+ queueing-not-allowed,
+ queueing-allowed
+}
+```
+
+```
+
+-- R
+RAB-AsymmetryIndicator ::= ENUMERATED {
+ symmetric-bidirectional,
+ asymmetric-unidirectional-downlink,
+ asymmetric-unidirectional-uplink,
+ asymmetric-bidirectional,
+ ...
+}
+
+RABased ::= SEQUENCE {
+ raiList RAI-List,
+ iE-Extensions ProtocolExtensionContainer { {RABased-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RABased-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAI-List ::= SEQUENCE (SIZE (1..maxNrOfRAIs)) OF
+ RAI
+
+RABDataVolumeReport ::= SEQUENCE (SIZE (1..maxNrOfVol)) OF
+ SEQUENCE {
+ dl-UnsuccessfullyTransmittedDataVolume UnsuccessfullyTransmittedDataVolume,
+ dataVolumeReference DataVolumeReference OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RABDataVolumeReport-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+RABDataVolumeReport-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAB-ID ::= BIT STRING (SIZE (8))
+
+RAB-Parameter-ExtendedGuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedGuaranteedBitrate
+
+RAB-Parameter-ExtendedMaxBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedMaxBitrate
+
+RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF GuaranteedBitrate
+--This IE shall be ignored if Supported Guaranteed Bit rate is present--
+
+RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF MaxBitrate
+--This IE shall be ignored if Supported Maximum Bit rate is present--
+
+RAB-Parameters ::= SEQUENCE {
+ trafficClass TrafficClass,
+
+```
+
+```
+
+rAB-AsymmetryIndicator RAB-AsymmetryIndicator,
+maxBitrate RAB-Parameter-MaxBitrateList,
+guaranteedBitRate RAB-Parameter-GuaranteedBitrateList OPTIONAL
+-- This IE shall be present the traffic class IE is set to "Conversational" or "Streaming" --,
+deliveryOrder DeliveryOrder,
+maxSDU-Size MaxSDU-Size,
+sDU-Parameters SDU-Parameters,
+transferDelay TransferDelay OPTIONAL
+-- This IE shall be present the traffic class IE is set to "Conversational" or "Streaming" --,
+trafficHandlingPriority TrafficHandlingPriority OPTIONAL
+-- This IE shall be present the traffic class IE is set to "Interactive" --,
+allocationOrRetentionPriority AllocationOrRetentionPriority OPTIONAL,
+sourceStatisticsDescriptor SourceStatisticsDescriptor OPTIONAL
+-- This IE shall be present the traffic class IE is set to "Conversational" or "Streaming" --,
+relocationRequirement RelocationRequirement OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {RAB-Parameters-ExtIEs} } OPTIONAL,
+...
+}
+
+RAB-Parameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+-- Extension for Release 5 to enable indication that Interactive User Plane data is of a signalling nature --
+{ ID id-SignallingIndication CRITICALITY ignore EXTENSION SignallingIndication PRESENCE optional }|
+-- Extension for Release 7 to indicate an Extended Guaranteed Bitrate --
+{ ID id-RAB-Parameter-ExtendedGuaranteedBitrateList CRITICALITY reject EXTENSION RAB-Parameter-ExtendedGuaranteedBitrateList PRESENCE
+optional }|
+-- Extension for Release 7 to indicate an Extended Maximum Bitrate --
+{ ID id-RAB-Parameter-ExtendedMaxBitrateList CRITICALITY reject EXTENSION RAB-Parameter-ExtendedMaxBitrateList PRESENCE optional }|
+-- Extension for Release 8 to indicate an Supported Maximum Bitrate --
+{ ID id-RAB-Parameter-SupportedMaxBitrateList CRITICALITY reject EXTENSION SupportedRAB-ParameterBitrateList PRESENCE optional }|
+-- Extension for Release 8 to indicate an Supported Guaranteed Bitrate --
+{ ID id-RAB-Parameter-SupportedGuaranteedBitrateList CRITICALITY reject EXTENSION SupportedRAB-ParameterBitrateList PRESENCE optional },
+...
+}
+
+RABParametersList ::= SEQUENCE (SIZE (1.. maxNrOfRABs)) OF SEQUENCE {
+rab-Id RAB-ID,
+cn-domain CN-DomainIndicator,
+rabDataVolumeReport RABDataVolumeReport OPTIONAL,
+upInformation UPInformation OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { { RABParametersList-ExtIEs } } OPTIONAL,
+...
+}
+
+RABParametersList-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+RAB-SubflowCombinationBitRate ::= INTEGER (0..16000000)
+
+RAB-TrCH-Mapping ::= SEQUENCE ( SIZE (1..maxNrOfRABs)) OF
+
+```
+
+```
+ RAB-TrCH-MappingItem
+
+RAB-TrCH-MappingItem ::= SEQUENCE {
+ rAB-ID RAB-ID,
+ trCH-ID-List TrCH-ID-List,
+ iE-Extensions ProtocolExtensionContainer { { RAB-TrCH-MappingItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAB-TrCH-MappingItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 99 to enable transfer of RAB Subflow mapping onto Iur transport channel Ids for a given indicated domain --
+ { ID id-CN-DomainIndicator CRITICALITY ignore EXTENSION CN-DomainIndicator PRESENCE optional },
+ ...
+}
+
+RAC ::= OCTET STRING (SIZE (1))
+
+RAI ::= SEQUENCE {
+ LAI LAI,
+ rAC RAC,
+ iE-Extensions ProtocolExtensionContainer { { RAI-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAI-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RAListofIdleModeUEs ::= CHOICE {
+ notEmptyRAListofIdleModeUEs NotEmptyRAListofIdleModeUEs,
+ emptyFullRAListofIdleModeUEs ENUMERATED { emptylist,fulllist,... },
+ ...
+}
+
+NotEmptyRAListofIdleModeUEs ::= SEQUENCE {
+ rAofIdleModeUEs RAofIdleModeUEs,
+ iE-Extensions ProtocolExtensionContainer { { NotEmptyRAListofIdleModeUEs-ExtIEs} } OPTIONAL
+}
+
+RAofIdleModeUEs ::= SEQUENCE (SIZE (1..maxMBMSRA)) OF
+ RAC
+
+NotEmptyRAListofIdleModeUEs-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-LAofIdleModeUEs CRITICALITY reject EXTENSION LAListofIdleModeUEs PRESENCE conditional },
+ -- This IE shall be present if the RA of Idle Mode UEs IE is included. --
+ ...
+}
+
+LAListofIdleModeUEs ::= SEQUENCE (SIZE (1..maxMBMSRA)) OF
+ LAI
+```
+
+```
+RAT-Type ::= ENUMERATED {
+ utran,
+ geran,
+ ...
+}
+
+RateControlAllowed ::= ENUMERATED {
+ not-allowed,
+ allowed
+}
+
+RedirectAttemptFlag ::= NULL
+
+RedirectionCompleted ::= ENUMERATED {
+ redirection-completed,
+ ...
+}
+
+RejectCauseValue ::= ENUMERATED {
+ pLMN-Not-Allowed,
+ location-Area-Not-Allowed,
+ roaming-Not-Allowed-In-This-Location-Area,
+ no-Suitable-Cell-In-Location-Area,
+ gPRS-Services-Not-Allowed-In-This-PLMN,
+ cS-PS-coordination-required,
+ ...,
+ network-failure,
+ not-authorized-for-this-CSG
+}
+
+RelocationRequirement ::= ENUMERATED {
+ lossless,
+ none,
+ ...,
+ realtime
+}
+
+RelocationType ::= ENUMERATED {
+ ue-not-involved,
+ ue-involved,
+ ...
+}
+
+RepetitionNumber0 ::= INTEGER (0..255)
+
+RepetitionNumber1 ::= INTEGER (1..256)
+```
+
+```
+ReportArea ::= ENUMERATED {
+ service-area,
+ geographical-area,
+ ...
+}
+
+ReportInterval ::= ENUMERATED {
+ ms250,
+ ms500,
+ ms1000,
+ ms2000,
+ ms3000,
+ ms4000,
+ ms6000,
+ ms12000,
+ ms16000,
+ ms20000,
+ ms24000,
+ ms32000,
+ ms64000,
+ ...,
+ ms8000,
+ ms28000
+}
+
+ReportAmount ::= ENUMERATED { n1, n2, n4, n8, n16, n32, n64, infinity, ... }
+
+RequestedGPSAssistanceData ::= OCTET STRING (SIZE (1 .. 38 ))
+ -- gpsAssistanceData as defined in 24.080 --
+
+RequestedGANSsAssistanceData ::= OCTET STRING (SIZE (1 .. 201 ))
+ -- ganssAssistanceData as defined in 24.080 --
+
+RequestedLocationRelatedDataType ::= ENUMERATED {
+ decipheringKeysUEBasedOTDOA,
+ decipheringKeysAssistedGPS,
+ dedicatedAssistanceDataUEBasedOTDOA,
+ dedicatedAssistanceDataAssistedGPS,
+ ...,
+ -- Release 7 extension elements --
+ decipheringKeysAssistedGANSs,
+ dedicatedAssistanceDataAssistedGANSs,
+ decipheringKeysAssistedGPSandGANSs,
+ dedicatedAssistanceDataAssistedGPSandGANSs
+}
+
+RequestedMBMSIPMulticastAddressandAPNRequest ::= SEQUENCE (SIZE (1..maxnoofMulticastServicesPerRNC)) OF
+ MBMSIPMulticastAddressandAPNlist
+
+MBMSIPMulticastAddressandAPNlist ::= SEQUENCE {
+```
+
+```
+
+ TMGI TMGI,
+ iPMulticastAddress IPMulticastAddress,
+ aPN APN,
+ iE-Extensions ProtocolExtensionContainer { {MBMSIPMulticastAddressandAPNlist-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBMSIPMulticastAddressandAPNlist-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RequestedMulticastServiceList ::= SEQUENCE (SIZE (1.. maxnoofMulticastServicesPerUE)) OF
+ TMGI
+
+Requested-RAB-Parameter-Values ::= SEQUENCE {
+ requestedMaxBitrates Requested-RAB-Parameter-MaxBitrateList OPTIONAL,
+ requestedGuaranteedBitrates Requested-RAB-Parameter-GuaranteedBitrateList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { Requested-RAB-Parameter-Values-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Requested-RAB-Parameter-Values-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 6 to enable RNC to request the execution of an alternative RAB configuration --
+ { ID id-AlternativeRABConfigurationRequest CRITICALITY ignore EXTENSION AlternativeRABConfigurationRequest PRESENCE optional }|
+ -- Extension for Release 7 to request an Extended Maximum Bitrate --
+ { ID id-Requested-RAB-Parameter-ExtendedMaxBitrateList CRITICALITY reject EXTENSION Requested-RAB-Parameter-ExtendedMaxBitrateList PRESENCE
+optional }|
+ -- Extension for Release 7 to request an Extended Guaranteed Bitrate --
+ { ID id-Requested-RAB-Parameter-ExtendedGuaranteedBitrateList CRITICALITY reject EXTENSION Requested-RAB-Parameter-
+ExtendedGuaranteedBitrateList PRESENCE optional }|
+ -- Extension for Release 8 to request an Supported Maximum Bitrate --
+ { ID id-Requested-RAB-Parameter-SupportedMaxBitrateList CRITICALITY reject EXTENSION SupportedRAB-ParameterBitrateList PRESENCE optional }|
+ -- Extension for Release 8 to request an Supported Guaranteed Bitrate --
+ { ID id-Requested-RAB-Parameter-SupportedGuaranteedBitrateList CRITICALITY reject EXTENSION SupportedRAB-ParameterBitrateList PRESENCE
+optional },
+ ...
+}
+
+Requested-RAB-Parameter-ExtendedMaxBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedMaxBitrate
+
+Requested-RAB-Parameter-ExtendedGuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF ExtendedGuaranteedBitrate
+
+Requested-RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF MaxBitrate
+
+Requested-RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF GuaranteedBitrate
+
+RequestType ::= SEQUENCE {
+ event Event,
+ reportArea ReportArea,
+}
+
+```
+
+```
+
+ accuracyCode INTEGER (0..127) OPTIONAL,
+ ...
+}
+
+ResidualBitErrorRatio ::= SEQUENCE {
+ mantissa INTEGER (1..9),
+ exponent INTEGER (1..8),
+ iE-Extensions ProtocolExtensionContainer { {ResidualBitErrorRatio-ExtIEs} } OPTIONAL
+}
+-- ResidualBitErrorRatio = mantissa * 10^-exponent
+
+ResidualBitErrorRatio-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ResponseTime ::= ENUMERATED {
+ lowdelay,
+ delaytolerant,
+ ...
+}
+
+RIMInformation ::= OCTET STRING
+
+RIM-Transfer ::= SEQUENCE {
+ rIMInformation RIMInformation,
+ rIMRoutingAddress RIMRoutingAddress OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RIM-Transfer-ExtIEs} } OPTIONAL
+}
+
+RIM-Transfer-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RIMRoutingAddress ::= CHOICE {
+ targetRNC-ID TargetRNC-ID,
+ gERAN-Cell-ID GERAN-Cell-ID,
+ ... /
+ targeteNB-ID TargetENB-ID
+}
+
+RNC-ID ::= INTEGER (0..4095)
+-- RNC-ID ::= BIT STRING (SIZE (12))
+-- Harmonized with RNSAP and NBAP definitions
+
+RNCTraceInformation ::= SEQUENCE {
+ traceReference TraceReference,
+ traceActivationIndicator ENUMERATED {activated, deactivated},
+ equipmentsToBeTraced EquipmentsToBeTraced OPTIONAL,
+}
+
+```
+
+```
+
+ -- This IE shall be present if the Trace Activation Indicator IE is set to "Activated".
+ iE-Extensions ProtocolExtensionContainer { { RNCTraceInformation-ExtIEs} } OPTIONAL
+ }
+
+ RNCTraceInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 11 to enable anonymization MDT for area based MDT --
+ {ID id-TraceRecordingSessionReference CRITICALITY ignore EXTENSION TraceRecordingSessionReference PRESENCE optional}|
+ {ID id-IMSI CRITICALITY ignore EXTENSION IMSI PRESENCE optional}|
+ {ID id-Trace-Collection-Entity-IP-Address CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}|
+ {ID id-Serving-Cell-Identifier CRITICALITY ignore EXTENSION UTRAN-CellID PRESENCE optional},
+ ...
+ }
+
+ RNSAPRelocationParameters ::= SEQUENCE {
+ rabParametersList RABParametersList OPTIONAL,
+ locationReporting LocationReportingTransferInformation OPTIONAL,
+ traceInformation TraceInformation OPTIONAL,
+ sourceSAI SAI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { RNSAPRelocationParameters-ExtIEs } } OPTIONAL,
+ ...
+ }
+
+ RNSAPRelocationParameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ RRC-Container ::= OCTET STRING
+
+ RTLoadValue ::= INTEGER (0..100)
+
+ RSRVCC-HO-Indication ::= ENUMERATED {
+ ps-only,
+ ...
+ }
+
+ RSRVCC-Information ::= SEQUENCE {
+ nonce BIT STRING (SIZE (128)),
+ IMSInformation OCTET STRING (SIZE(1.. maxSizeOfIMSInfo)),
+ iE-Extensions ProtocolExtensionContainer { { RSRVCC-Information-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ RSRVCC-Information-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ RSRVCC-Operation-Possible ::= ENUMERATED {
+ rsrvcc-possible,
+ ...
+ }
+
+```
+
+```
+ }
+
+ -- S
+
+ SAC ::= OCTET STRING (SIZE (2))
+ SAI ::= SEQUENCE {
+ pLMNIdentity pLMNIdentity,
+ LAC LAC,
+ SAC SAC,
+ iE-Extensions ProtocolExtensionContainer { {SAI-ExtIEs} } OPTIONAL
+ }
+
+ SAI-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ SAPI ::= ENUMERATED {
+ sapi-0,
+ sapi-3,
+ ...
+ }
+
+ SessionUpdateID ::= INTEGER (0.. 1048575)
+ Shared-Network-Information ::= SEQUENCE {
+ pLMNs-in-shared-network PLMNs-in-shared-network,
+ iE-Extensions ProtocolExtensionContainer { {Shared-Network-Information-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ Shared-Network-Information-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ SignallingIndication ::= ENUMERATED {
+ signalling,
+ ...
+ }
+
+ SDU-ErrorRatio ::= SEQUENCE {
+ mantissa INTEGER (1..9),
+ exponent INTEGER (1..6),
+ iE-Extensions ProtocolExtensionContainer { {SDU-ErrorRatio-ExtIEs} } OPTIONAL
+ }
+
+ -- SDU-ErrorRatio = mantissa * 10^exponent
+
+ SDU-ErrorRatio-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ SDU-FormatInformationParameters ::= SEQUENCE (SIZE (1..maxRAB-SubflowCombination)) OF
+ SEQUENCE {
+```
+
+```
+ subflowSDU-Size SubflowSDU-Size OPTIONAL,
+ rAB-SubflowCombinationBitRate RAB-SubflowCombinationBitRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {SDU-FormatInformationParameters-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ SDU-FormatInformationParameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ SDU-Parameters ::= SEQUENCE (SIZE (1..maxRAB-Subflows)) OF
+ SEQUENCE {
+ sDU-ErrorRatio SDU-ErrorRatio OPTIONAL
+ -- This IE shall be present if the Delivery Of Erroneous SDU IE is set to "Yes" or "No" --,
+ residualBitErrorRatio ResidualBitErrorRatio,
+ deliveryOfErroneousSDU DeliveryOfErroneousSDU,
+ sDU-FormatInformationParameters SDU-FormatInformationParameters OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {SDU-Parameters-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ SDU-Parameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ SNA-Access-Information ::= SEQUENCE {
+ authorisedPLMNs AuthorisedPLMNs,
+ iE-Extensions ProtocolExtensionContainer { {SNA-Access-Information-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ SNA-Access-Information-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ SNAC ::= INTEGER (0..65535)
+
+ Service-Handover ::= ENUMERATED {
+ handover-to-GSM-should-be-performed,
+ handover-to-GSM-should-not-be-performed,
+ handover-to-GSM-shall-not-be-performed,
+ ...
+ }
+
+ Source-ToTarget-TransparentContainer ::= OCTET STRING
+ -- This IE is a transparent container, the IE shall be encoded not as an OCTET STRING but according to the type specifications of the target system.
+ -- Note: In the current version of this specification, this IE may either carry the Source RNC to Target RNC Transparent Container or the Source eNB to Target eNB Transparent Container IE as
+ -- defined in TS 36.413 [49]
+```
+
+```
+SourceNodeB-ToTargetNodeB-TransparentContainer ::= OCTET STRING
+```
+
+```
+SourceCellID ::= CHOICE {
+ sourceUTRANCellID SourceUTRANCellID,
+ sourceGERANCellID CGI,
+ ...
+}
+```
+
+```
+SourceBSS-ToTargetBSS-TransparentContainer ::= OCTET STRING
+```
+
+```
+SourceID ::= CHOICE {
+ sourceRNC-ID SourceRNC-ID,
+ sAI SAI,
+ ...
+}
+```
+
+```
+SourceRNC-ID ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ rNC-ID RNC-ID,
+ iE-Extensions ProtocolExtensionContainer { {SourceRNC-ID-ExtIEs} } OPTIONAL
+}
+```
+
+```
+SourceRNC-ID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+```
+
+```
+SourceRNC-ToTargetRNC-TransparentContainer ::= SEQUENCE {
+ rRC-Container RRC-Container,
+ numberOfIuInstances NumberOfIuInstances,
+ relocationType RelocationType,
+ chosenIntegrityProtectionAlgorithm ChosenIntegrityProtectionAlgorithm OPTIONAL,
+ integrityProtectionKey IntegrityProtectionKey OPTIONAL,
+ chosenEncryptionAlgorithmForSignalling ChosenEncryptionAlgorithm OPTIONAL,
+ cipheringKey EncryptionKey OPTIONAL,
+ chosenEncryptionAlgorithmForCS ChosenEncryptionAlgorithm OPTIONAL,
+ chosenEncryptionAlgorithmForPS ChosenEncryptionAlgorithm OPTIONAL,
+ d-RNTI D-RNTI OPTIONAL
+ -- This IE shall be present if the Relocation type IE is set to "UE not involved in relocation of SRNS" --,
+ targetCellId TargetCellId OPTIONAL
+ -- This IE shall be present if the Relocation type IE is set to "UE involved in relocation of SRNS" --,
+ rAB-TrCH-Mapping RAB-TrCH-Mapping OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {SourceRNC-ToTargetRNC-TransparentContainer-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SourceRNC-ToTargetRNC-TransparentContainer-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+
+-- Extension for Release 99 to enable transfer of SRB mapping onto Iur transport channel Ids --
+{ID id-SRB-TrCH-Mapping CRITICALITY reject EXTENSION SRB-TrCH-Mapping PRESENCE optional}|
+-- Extension for Release 5 to enable Inter RAN Load Information Exchange over Iu --
+{ID id-CellLoadInformationGroup CRITICALITY ignore EXTENSION CellLoadInformationGroup PRESENCE optional}|
+-- Extension for Release 6 to provide Trace Recording Session Information to the Target RNC --
+{ID id-TraceRecordingSessionInformation CRITICALITY ignore EXTENSION TraceRecordingSessionInformation PRESENCE optional}|
+-- Extension for Release 6 to indicate to the Target RNC that the UE has activated Multicast Service --
+{ID id-MBMSLinkingInformation CRITICALITY ignore EXTENSION MBMSLinkingInformation PRESENCE optional}|
+{ID id-d-RNTI-for-NoIuCSUP CRITICALITY reject EXTENSION D-RNTI PRESENCE optional}|
+{ID id-UE-History-Information CRITICALITY ignore EXTENSION UE-History-Information PRESENCE optional}|
+{ID id-SubscriberProfileIDforRFP CRITICALITY ignore EXTENSION SubscriberProfileIDforRFP PRESENCE optional}|
+-- Extension for Release 8 to transfer to the Target RNC parameters required for SRVCC operation --
+{ID id-SRVCC-Information CRITICALITY reject EXTENSION SRVCC-Information PRESENCE optional}|
+{ID id-PSRABtoBeReplaced CRITICALITY reject EXTENSION RAB-ID PRESENCE optional}|
+-- Extension for Release 9 to transfer to the Target RNC parameters required for CSFB operation --
+{ID id-CSFB-Information CRITICALITY ignore EXTENSION CSFB-Information PRESENCE optional}|
+-- Extension for Release 10 to indicate to the Target RNC the need of continued IRAT measurement --
+{ID id-IRAT-Measurement-Configuration CRITICALITY ignore EXTENSION IRAT-Measurement-Configuration PRESENCE optional}|
+-- Extension for Release 10 to indicate Management Based MDT Allowed --
+{ID id-Management-Based-MDT-Allowed CRITICALITY ignore EXTENSION Management-Based-MDT-Allowed PRESENCE optional}|
+-- Extension for Release 11 to indicate Management Based MDT PLMN List --
+{ID id-Management-Based-MDT-PLMN-List CRITICALITY ignore EXTENSION MDT-PLMN-List PRESENCE optional}|
+-- Extension for Release 11 to indicate the last E-UTRAN PLMN Identity --
+{ID id-LastE-UTRANPLMNIdentity CRITICALITY ignore EXTENSION PLMNIdentity PRESENCE optional},
+...
+}
+
+IRAT-Measurement-Configuration ::= SEQUENCE {
+ rSRP INTEGER (0..97) OPTIONAL,
+ rSRQ INTEGER (0..34) OPTIONAL,
+ iRATMeasurementParameters IRATMeasurementParameters,
+ iE-Extensions ProtocolExtensionContainer { {IRAT-Measurement-Configuration-ExtIEs} } OPTIONAL}
+
+IRAT-Measurement-Configuration-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IRATMeasurementParameters ::= SEQUENCE {
+ measurementDuration INTEGER (1..100),
+ eUTRANFrequencies EUTRANFrequencies OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { IRATMeasurementParameters-ExtIEs} } OPTIONAL}
+
+IRATMeasurementParameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+EUTRANFrequencies ::= SEQUENCE (SIZE (1..maxNrOfEUTRAFreqs)) OF SEQUENCE {
+ earfcn INTEGER (0..65535),
+ measBand MeasBand OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {EUTRANFrequencies-ExtIEs} } OPTIONAL}
+
+```
+
+```
+MeasBand ::= ENUMERATED {
+ v6,
+ v15,
+ v25,
+ v50,
+ v75,
+ v100
+}
+
+EUTRANFrequencies-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ { ID id-EARFCN-Extended CRITICALITY reject EXTENSION EARFCN-Extended PRESENCE optional},
+ ...
+}
+
+SubscriberProfileIDforRFP ::= INTEGER (1..256)
+
+SourceStatisticsDescriptor ::= ENUMERATED {
+ speech,
+ unknown,
+ ...
+}
+
+SupportedRAB-ParameterBitrateList ::= SEQUENCE (SIZE (1..maxNrOfSeparateTrafficDirections)) OF SupportedBitrate
+
+SupportedBitrate ::= INTEGER (1..10000000000, ...)
+-- Unit is bits per sec
+
+SourceUTRANCellID ::= SEQUENCE {
+ pLMNIdentity pLMNIdentity,
+ uTRANCellID TargetCellId,
+ iE-Extensions ProtocolExtensionContainer { {SourceUTRANCellID-ExtIEs} } OPTIONAL
+}
+
+SourceUTRANCellID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SRB-ID ::= INTEGER (1..32)
+
+SRB-TrCH-Mapping ::= SEQUENCE ( SIZE (1..maxNrOfSRBs)) OF
+ SRB-TrCH-MappingItem
+
+SRB-TrCH-MappingItem ::= SEQUENCE {
+ sRB-ID sRB-ID,
+ trCH-ID TrCH-ID,
+ iE-Extensions ProtocolExtensionContainer { { SRB-TrCH-MappingItem-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SRB-TrCH-MappingItem-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SRVCC-HO-Indication ::= ENUMERATED {
+ ps-and-cs,
+ cs-only,
+ ...
+}
+
+SRVCC-Information ::= SEQUENCE {
+ nonce BIT STRING (SIZE (128)),
+ iE-Extensions ProtocolExtensionContainer { { SRVCC-Information-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SRVCC-Information-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SRVCC-Operation-Possible ::= ENUMERATED {
+ srvcc-possible,
+ ...
+}
+
+SubflowSDU-Size ::= INTEGER (0..4095)
+-- Unit is bit
+
+-- T
+TAC ::= OCTET STRING (SIZE (2))
+
+TAI ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ tAC TAC,
+ iE-Extensions ProtocolExtensionContainer { { TAI-ExtIEs} } OPTIONAL
+}
+
+TAI-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Target-ToSource-TransparentContainer ::= OCTET STRING
+-- This IE is a transparent container, the IE shall be encoded not as an OCTET STRING but according to the type specifications of the target system.
+-- Note: In the current version of this specification, this IE may either carry the Target RNC to Source RNC Transparent Container or the Target eNB to Source eNB Transparent Container IE as
+-- defined in TS 36.413 [49]
+```
+
+```
+
+TargetNodeB-ToSourceNodeB-TransparentContainer ::= OCTET STRING
+
+TargetBSS-ToSourceBSS-TransparentContainer ::= OCTET STRING
+
+TargetCellId ::= INTEGER (0..268435455)
+
+TargetID ::= CHOICE {
+ targetRNC-ID TargetRNC-ID,
+ cGI CGI,
+ ...
+ targeteNB-ID TargeteNB-ID
+}
+
+TargeteNB-ID ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ eNB-ID eNB-ID,
+ iE-Extensions ProtocolExtensionContainer { {TargeteNB-ID-ExtIEs} } OPTIONAL,
+ selectedTAI TAI,
+ ...
+}
+
+TargeteNB-ID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TargetRNC-ID ::= SEQUENCE {
+ LAI LAI,
+ rAC RAC OPTIONAL,
+ rNC-ID RNC-ID,
+ iE-Extensions ProtocolExtensionContainer { {TargetRNC-ID-ExtIEs} } OPTIONAL
+}
+
+TargetRNC-ID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 7 to indicate extended RNC-ID --
+ { ID id-ExtendedRNC-ID CRITICALITY reject EXTENSION ExtendedRNC-ID PRESENCE optional },
+ ...
+}
+
+TargetRNC-ToSourceRNC-TransparentContainer ::= SEQUENCE {
+ rRC-Container RRC-Container,
+ d-RNTI D-RNTI OPTIONAL
+ -- May be included to allow the triggering of the Relocation Detect procedure from the Iur Interface --,
+ iE-Extensions ProtocolExtensionContainer { {TargetRNC-ToSourceRNC-TransparentContainer-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TargetRNC-ToSourceRNC-TransparentContainer-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+ }
+
+ TBCD-STRING ::= OCTET STRING
+
+ TemporaryUE-ID ::= CHOICE {
+ tMSI TMSI,
+ p-TMSI P-TMSI,
+ ...
+ }
+
+ Time-UE-StayedInCell ::= INTEGER (0..4095)
+
+ Time-UE-StayedInCell-EnhancedGranularity ::= INTEGER (0..40950)
+
+ TimeToMBMSDataTransfer ::= OCTET STRING(SIZE(1))
+
+ TimingDifferenceULDL ::= OCTET STRING (SIZE(1))
+
+ TMGI ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ serviceID OCTET STRING (SIZE (3)),
+ iE-Extensions ProtocolExtensionContainer { {TMGI-ExtIEs} } OPTIONAL
+ }
+
+ TMGI-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ TMSI ::= OCTET STRING (SIZE (4))
+
+ TraceDepth ::= ENUMERATED {
+ minimum,
+ medium,
+ maximum,
+ ...
+ }
+
+ TraceInformation ::= SEQUENCE {
+ traceReference TraceReference,
+ ue-identity UE-ID,
+ tracePropagationParameters TracePropagationParameters OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { TraceInformation-ExtIEs } } OPTIONAL,
+ ...
+ }
+
+ TraceInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ TracePropagationParameters ::= SEQUENCE {
+```
+
+```
+ traceRecordingSessionReference TraceRecordingSessionReference,
+ traceDepth TraceDepth,
+ listOfInterfacesToTrace ListOfInterfacesToTrace OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { TracePropagationParameters-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ TracePropagationParameters-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ TraceRecordingSessionInformation ::= SEQUENCE {
+ traceReference TraceReference,
+ traceRecordingSessionReference TraceRecordingSessionReference,
+ iE-Extensions ProtocolExtensionContainer { { TraceRecordingSessionInformation-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ TraceRecordingSessionInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ TraceRecordingSessionReference ::= INTEGER (0..65535)
+
+ TraceReference ::= OCTET STRING (SIZE (2..3))
+
+ TraceType ::= OCTET STRING (SIZE (1))
+ -- Reference: GSM TS 12.08
+
+ TrafficClass ::= ENUMERATED {
+ conversational,
+ streaming,
+ interactive,
+ background,
+ ...
+ }
+
+ TrafficHandlingPriority ::= INTEGER { spare (0), highest (1), lowest (14), no-priority-used (15) } (0..15)
+
+ TransferDelay ::= INTEGER (0..65535)
+ -- Unit is millisecond
+
+ UnsuccessfullyTransmittedDataVolume ::= INTEGER (0..4294967295)
+
+ TransportLayerAddress ::= BIT STRING (SIZE (1..160, ...))
+
+ TrCH-ID ::= SEQUENCE {
+ dCH-ID DCH-ID OPTIONAL,
+ dSCH-ID DSCH-ID OPTIONAL,
+ uSCH-ID USCH-ID OPTIONAL,
+ }
+
+```
+
+```
+
+ iE-Extensions ProtocolExtensionContainer { { TrCH-ID-ExtIEs } } OPTIONAL,
+ ...
+}
+
+TrCH-ID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ -- Extension for Release 5 to enable transfer of HS-DSCH-MAC-d-Flow-ID onto Iur transport channel ID --
+ { ID id-hS-DSCH-MAC-d-Flow-ID CRITICALITY ignore EXTENSION HS-DSCH-MAC-d-Flow-ID PRESENCE optional } |
+ -- Extension for Release 6 to enable transfer of E-DCH-MAC-d-Flow-ID onto Iur transport channel ID --
+ { ID id-E-DCH-MAC-d-Flow-ID CRITICALITY ignore EXTENSION E-DCH-MAC-d-Flow-ID PRESENCE optional },
+ ...
+}
+
+TrCH-ID-List ::= SEQUENCE (SIZE (1..maxRAB-Subflows)) OF
+ TrCH-ID
+
+TriggerID ::= OCTET STRING (SIZE (3..22))
+
+TunnelInformation ::= SEQUENCE {
+ transportLayerAddress TransportLayerAddress,
+ uDP-Port-Number Port-Number OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { Tunnel-Information-ExtIEs } } OPTIONAL,
+ ...
+}
+
+Tunnel-Information-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TypeOfError ::= ENUMERATED {
+ not-understood,
+ missing,
+ ...
+}
+
+-- U
+
+UE-AggregateMaximumBitRate ::= SEQUENCE {
+ uE-AggregateMaximumBitRateDownlink UE-AggregateMaximumBitRateDownlink OPTIONAL,
+ uE-AggregateMaximumBitRateUplink UE-AggregateMaximumBitRateUplink OPTIONAL,
+ ...
+}
+
+UE-AggregateMaximumBitRateDownlink ::= INTEGER (1..10000000000)
+-- Unit is bits per sec
+
+UE-AggregateMaximumBitRateUplink ::= INTEGER (1..10000000000)
+-- Unit is bits per sec
+
+```
+
+UE-History-Information ::= OCTET STRING
+
+UE-ID ::= CHOICE {
+
+ imsi IMSI,
+ imei IMEI,
+ ...
+ imeisv IMEISV
+
+}
+
+UESBI-Iu ::= SEQUENCE {
+
+ uESBI-IuA UESBI-IuA OPTIONAL,
+ uESBI-IuB UESBI-IuB OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { UESBI-Iu-ExtIEs } } OPTIONAL,
+ ...
+ }
+
+UESBI-Iu-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+ }
+
+UESBI-IuA ::= BIT STRING (SIZE(1..128))
+
+-- Reference: TR25.994 --
+
+UESBI-IuB ::= BIT STRING (SIZE(1..128))
+
+-- Reference: TR25.995 --
+
+UL-GTP-PDU-SequenceNumber ::= INTEGER (0..65535)
+
+UL-N-PDU-SequenceNumber ::= INTEGER (0..65535)
+
+UPInformation ::= SEQUENCE {
+
+ frameSeqNoUL FrameSequenceNumber,
+ frameSeqNoDL FrameSequenceNumber,
+ pdu14FrameSeqNoUL PDUType14FrameSequenceNumber,
+ pdu14FrameSeqNoDL PDUType14FrameSequenceNumber,
+ dataPDUType DataPDUType,
+ upinitialisationFrame UPInitialisationFrame,
+ iE-Extensions ProtocolExtensionContainer { { UPInformation-ExtIEs } } OPTIONAL,
+ ...
+ }
+
+UPInformation-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+
+ {ID id-TimingDifferenceULDL CRITICALITY ignore EXTENSION TimingDifferenceULDL PRESENCE optional},
+
+ ...
+ }
+
+UPInitialisationFrame ::= OCTET STRING
+
+```
+UP-ModeVersions ::= BIT STRING (SIZE (16))
+USCH-ID ::= INTEGER (0..255)
+
+UserPlaneMode ::= ENUMERATED {
+ transparent-mode,
+ support-mode-for-predefined-SDU-sizes,
+ ...
+}
+
+UTRAN-CellID ::= SEQUENCE {
+ pLMNIdentity PLMNIdentity,
+ cellID TargetCellId,
+ iE-Extensions ProtocolExtensionContainer { { UTRAN-CellID-ExtIEs } } OPTIONAL
+}
+
+UTRAN-CellID-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- V
+
+VelocityEstimate ::= CHOICE {
+ horizontalVelocity HorizontalVelocity,
+ horizontalWithVerticalVelocity HorizontalWithVerticalVelocity,
+ horizontalVelocityWithUncertainty HorizontalVelocityWithUncertainty,
+ horizontalWithVeritcalVelocityAndUncertainty HorizontalWithVerticalVelocityAndUncertainty,
+ ...
+}
+
+HorizontalVelocity ::= SEQUENCE {
+ horizontalSpeedAndBearing HorizontalSpeedAndBearing,
+ iE-Extensions ProtocolExtensionContainer { { HorizontalVelocity-ExtIEs } } OPTIONAL,
+ ...
+}
+
+HorizontalVelocity-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+HorizontalWithVerticalVelocity ::= SEQUENCE {
+ horizontalSpeedAndBearing HorizontalSpeedAndBearing,
+ veritcalVelocity VerticalVelocity,
+ iE-Extensions ProtocolExtensionContainer { { HorizontalWithVerticalVelocity-ExtIEs } } OPTIONAL,
+ ...
+}
+
+HorizontalWithVerticalVelocity-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ }
+
+ HorizontalVelocityWithUncertainty ::= SEQUENCE {
+ horizontalSpeedAndBearing HorizontalSpeedAndBearing,
+ uncertaintySpeed INTEGER (0..255),
+ iE-Extensions ProtocolExtensionContainer { { HorizontalVelocityWithUncertainty-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ HorizontalVelocityWithUncertainty-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ HorizontalWithVerticalVelocityAndUncertainty ::= SEQUENCE {
+ horizontalSpeedAndBearing HorizontalSpeedAndBearing,
+ veritcalVelocity VerticalVelocity,
+ horizontalUncertaintySpeed INTEGER (0..255),
+ verticalUncertaintySpeed INTEGER (0..255),
+ iE-Extensions ProtocolExtensionContainer { { HorizontalWithVerticalVelocityAndUncertainty-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ HorizontalWithVerticalVelocityAndUncertainty-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ HorizontalSpeedAndBearing ::= SEQUENCE {
+ bearing INTEGER (0..359),
+ horizontalSpeed INTEGER (0..2047)
+ }
+
+ VerticalVelocity ::= SEQUENCE {
+ veritcalSpeed INTEGER (0..255),
+ veritcalSpeedDirection VerticalSpeedDirection
+ }
+
+ VerticalSpeedDirection ::= ENUMERATED {
+ upward,
+ downward
+ }
+
+ VerticalAccuracyCode ::= INTEGER (0..127)
+
+ VoiceSupportMatchIndicator ::= ENUMERATED {
+ supported,
+ not-supported,
+ ...
+ }
+```
+
+END
+
+### 9.3.5 Common Definitions
+
+```
+
+-- *****
+--
+-- Common definitions
+--
+-- *****
+
+RANAP-CommonDataTypes {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ umts-Access (20) modules (3) ranap (0) version1 (1) ranap-CommonDataTypes (3) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+Criticality ::= ENUMERATED { reject, ignore, notify }
+
+Presence ::= ENUMERATED { optional, conditional, mandatory }
+
+PrivateIE-ID ::= CHOICE {
+ local INTEGER (0..65535),
+ global OBJECT IDENTIFIER
+}
+
+ProcedureCode ::= INTEGER (0..255)
+
+ProtocolExtensionID ::= INTEGER (0..65535)
+
+ProtocolIE-ID ::= INTEGER (0..65535)
+
+TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessfull-outcome, outcome }
+
+END
+
+```
+
+### 9.3.6 Constant Definitions
+
+```
+
+-- *****
+--
+-- Constant definitions
+--
+-- *****
+
+RANAP-Constants {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ umts-Access (20) modules (3) ranap (0) version1 (1) ranap-Constants (4) }
+
+```
+
+```
+DEFINITIONS AUTOMATIC TAGS ::=
+```
+
+```
+BEGIN
+```
+
+```
+-- *****
+--
+-- Elementary Procedures
+--
+-- *****
+```
+
+```
+id-RAB-Assignment INTEGER ::= 0
+id-Iu-Release INTEGER ::= 1
+id-RelocationPreparation INTEGER ::= 2
+id-RelocationResourceAllocation INTEGER ::= 3
+id-RelocationCancel INTEGER ::= 4
+id-SRNS-ContextTransfer INTEGER ::= 5
+id-SecurityModeControl INTEGER ::= 6
+id-DataVolumeReport INTEGER ::= 7
+id-Reset INTEGER ::= 9
+id-RAB-ReleaseRequest INTEGER ::= 10
+id-Iu-ReleaseRequest INTEGER ::= 11
+id-RelocationDetect INTEGER ::= 12
+id-RelocationComplete INTEGER ::= 13
+id-Paging INTEGER ::= 14
+id-CommonID INTEGER ::= 15
+id-CN-InvokeTrace INTEGER ::= 16
+id-LocationReportingControl INTEGER ::= 17
+id-LocationReport INTEGER ::= 18
+id-InitialUE-Message INTEGER ::= 19
+id-DirectTransfer INTEGER ::= 20
+id-OverloadControl INTEGER ::= 21
+id-ErrorIndication INTEGER ::= 22
+id-SRNS-DataForward INTEGER ::= 23
+id-ForwardSRNS-Context INTEGER ::= 24
+id-privateMessage INTEGER ::= 25
+id-CN-DeactivateTrace INTEGER ::= 26
+id-ResetResource INTEGER ::= 27
+id-RANAP-Relocation INTEGER ::= 28
+id-RAB-ModifyRequest INTEGER ::= 29
+id-LocationRelatedData INTEGER ::= 30
+id-InformationTransfer INTEGER ::= 31
+id-UESpecificInformation INTEGER ::= 32
+id-UplinkInformationExchange INTEGER ::= 33
+id-DirectInformationTransfer INTEGER ::= 34
+id-MBMSsessionStart INTEGER ::= 35
+id-MBMSsessionUpdate INTEGER ::= 36
+id-MBMSsessionStop INTEGER ::= 37
+id-MBMSUELinking INTEGER ::= 38
+id-MBMSRegistration INTEGER ::= 39
+```
+
+```
+
+id-MBMSNCDe-Registration-Procedure INTEGER ::= 40
+id-MBMSRABEstablishmentIndication INTEGER ::= 41
+id-MBMSRABRelease INTEGER ::= 42
+id-enhancedRelocationComplete INTEGER ::= 43
+id-enhancedRelocationCompleteConfirm INTEGER ::= 44
+id-RANAPenhancedRelocation INTEGER ::= 45
+id-SRVCCPreparation INTEGER ::= 46
+id-UeRadioCapabilityMatch INTEGER ::= 47
+
+-- *****
+--
+-- Extension constants
+--
+-- *****
+
+maxPrivateIEs INTEGER ::= 65535
+maxProtocolExtensions INTEGER ::= 65535
+maxProtocolIEs INTEGER ::= 65535
+
+-- *****
+--
+-- Lists
+--
+-- *****
+
+maxNrOfDTs INTEGER ::= 15
+maxNrOfErrors INTEGER ::= 256
+maxNrOfIuSigConIds INTEGER ::= 250
+maxNrOfPDPDirections INTEGER ::= 2
+maxNrOfPoints INTEGER ::= 15
+maxNrOfRABs INTEGER ::= 256
+maxNrOfSeparateTrafficDirections INTEGER ::= 2
+maxNrOfSRBs INTEGER ::= 8
+maxNrOfVol INTEGER ::= 2
+maxNrOfLevels INTEGER ::= 256
+maxNrOfAltValues INTEGER ::= 16
+maxNrOfPLMNsSN INTEGER ::= 32
+maxNrOfLAs INTEGER ::= 65536
+maxNrOfSNAs INTEGER ::= 65536
+maxNrOfUEsToBeTraced INTEGER ::= 64
+maxNrOfInterfaces INTEGER ::= 16
+maxRAB-Subflows INTEGER ::= 7
+maxRAB-SubflowCombination INTEGER ::= 64
+maxSet INTEGER ::= 9
+maxNrOfHSDSCHMACdFlows-1 INTEGER ::= 7
+maxnoofMulticastServicesPerUE INTEGER ::= 128
+maxnoofMulticastServicesPerRNC INTEGER ::= 512
+maxMBMSSA INTEGER ::= 256
+maxMBMSRA INTEGER ::= 65536
+
+```
+
+```
+
+maxNrOfEDCHMACdFlows-1 INTEGER ::= 7
+maxGANSSSSet INTEGER ::= 9
+maxNrOfCSGs INTEGER ::= 256
+maxNrOfEUTRAFreqs INTEGER ::= 8
+maxNrOfCellIds INTEGER ::= 32
+maxNrOfRAIs INTEGER ::= 8
+maxNrOfLAIIs INTEGER ::= 8
+maxSizeOfIMSInfo INTEGER ::= 32
+maxnoofMDTPLMNs INTEGER ::= 16
+
+-- *****
+--
+-- IEs
+--
+-- *****
+
+id-AreaIdentity INTEGER ::= 0
+id-CN-DomainIndicator INTEGER ::= 3
+id-Cause INTEGER ::= 4
+id-ChosenEncryptionAlgorithm INTEGER ::= 5
+id-ChosenIntegrityProtectionAlgorithm INTEGER ::= 6
+id-ClassmarkInformation2 INTEGER ::= 7
+id-ClassmarkInformation3 INTEGER ::= 8
+id-CriticalityDiagnostics INTEGER ::= 9
+id-DL-GTP-PDU-SequenceNumber INTEGER ::= 10
+id-EncryptionInformation INTEGER ::= 11
+id-IntegrityProtectionInformation INTEGER ::= 12
+id-IuTransportAssociation INTEGER ::= 13
+id-L3-Information INTEGER ::= 14
+id-LAI INTEGER ::= 15
+id-NAS-PDU INTEGER ::= 16
+id-NonSearchingIndication INTEGER ::= 17
+id-NumberOfSteps INTEGER ::= 18
+id-OMC-ID INTEGER ::= 19
+id-OldBSS-ToNewBSS-Information INTEGER ::= 20
+id-PagingAreaID INTEGER ::= 21
+id-PagingCause INTEGER ::= 22
+id-PermanentNAS-UE-ID INTEGER ::= 23
+id-RAB-ContextItem INTEGER ::= 24
+id-RAB-ContextList INTEGER ::= 25
+id-RAB-DataForwardingItem INTEGER ::= 26
+id-RAB-DataForwardingItem-SRNS-CtxReq INTEGER ::= 27
+id-RAB-DataForwardingList INTEGER ::= 28
+id-RAB-DataForwardingList-SRNS-CtxReq INTEGER ::= 29
+id-RAB-DataVolumeReportItem INTEGER ::= 30
+id-RAB-DataVolumeReportList INTEGER ::= 31
+id-RAB-DataVolumeReportRequestItem INTEGER ::= 32
+id-RAB-DataVolumeReportRequestList INTEGER ::= 33
+id-RAB-FailedItem INTEGER ::= 34
+id-RAB-FailedList INTEGER ::= 35
+
+```
+
+```
+id-RAB-ID INTEGER ::= 36
+id-RAB-QueuedItem INTEGER ::= 37
+id-RAB-QueuedList INTEGER ::= 38
+id-RAB-ReleaseFailedList INTEGER ::= 39
+id-RAB-ReleaseItem INTEGER ::= 40
+id-RAB-ReleaseList INTEGER ::= 41
+id-RAB-ReleasedItem INTEGER ::= 42
+id-RAB-ReleasedList INTEGER ::= 43
+id-RAB-ReleasedList-IuRelComp INTEGER ::= 44
+id-RAB-RelocationReleaseItem INTEGER ::= 45
+id-RAB-RelocationReleaseList INTEGER ::= 46
+id-RAB-SetupItem-RelocReq INTEGER ::= 47
+id-RAB-SetupItem-RelocReqAck INTEGER ::= 48
+id-RAB-SetupList-RelocReq INTEGER ::= 49
+id-RAB-SetupList-RelocReqAck INTEGER ::= 50
+id-RAB-SetupOrModifiedItem INTEGER ::= 51
+id-RAB-SetupOrModifiedList INTEGER ::= 52
+id-RAB-SetupOrModifyItem INTEGER ::= 53
+id-RAB-SetupOrModifyList INTEGER ::= 54
+id-RAC INTEGER ::= 55
+id-RelocationType INTEGER ::= 56
+id-RequestType INTEGER ::= 57
+id-SAI INTEGER ::= 58
+id-SAPI INTEGER ::= 59
+id-SourceID INTEGER ::= 60
+id-Source-ToTarget-TransparentContainer INTEGER ::= 61
+id-TargetID INTEGER ::= 62
+id-Target-ToSource-TransparentContainer INTEGER ::= 63
+id-TemporaryUE-ID INTEGER ::= 64
+id-TraceReference INTEGER ::= 65
+id-TraceType INTEGER ::= 66
+id-TransportLayerAddress INTEGER ::= 67
+id-TriggerID INTEGER ::= 68
+id-UE-ID INTEGER ::= 69
+id-UL-GTP-PDU-SequenceNumber INTEGER ::= 70
+id-RAB-FailedtoReportItem INTEGER ::= 71
+id-RAB-FailedtoReportList INTEGER ::= 72
+id-KeyStatus INTEGER ::= 75
+id-DRX-CycleLengthCoefficient INTEGER ::= 76
+id-IuSigConIdList INTEGER ::= 77
+id-IuSigConIdItem INTEGER ::= 78
+id-IuSigConId INTEGER ::= 79
+id-DirectTransferInformationItem-RANAP-RelocInf INTEGER ::= 80
+id-DirectTransferInformationList-RANAP-RelocInf INTEGER ::= 81
+id-RAB-ContextItem-RANAP-RelocInf INTEGER ::= 82
+id-RAB-ContextList-RANAP-RelocInf INTEGER ::= 83
+id-RAB-ContextFailedtoTransferItem INTEGER ::= 84
+id-RAB-ContextFailedtoTransferList INTEGER ::= 85
+id-GlobalRNC-ID INTEGER ::= 86
+id-RAB-ReleasedItem-IuRelComp INTEGER ::= 87
+```
+
+Error:
+
+96
+
+Error: Reference source not found
+
+```
+id-MessageStructure INTEGER ::= 88
+id-Alt-RAB-Parameters INTEGER ::= 89
+id-Ass-RAB-Parameters INTEGER ::= 90
+id-RAB-ModifyList INTEGER ::= 91
+id-RAB-ModifyItem INTEGER ::= 92
+id-TypeOfError INTEGER ::= 93
+id-BroadcastAssistanceDataDecipheringKeys INTEGER ::= 94
+id-LocationRelatedDataRequestType INTEGER ::= 95
+id-GlobalCN-ID INTEGER ::= 96
+id-LastKnownServiceArea INTEGER ::= 97
+id-SRB-TrCH-Mapping INTEGER ::= 98
+id-InterSystemInformation-TransparentContainer INTEGER ::= 99
+id-NewBSS-To-OldBSS-Information INTEGER ::= 100
+id-SourceRNC-PDCP-context-info INTEGER ::= 103
+id-InformationTransferID INTEGER ::= 104
+id-SNA-Access-Information INTEGER ::= 105
+id-ProvidedData INTEGER ::= 106
+id-GERAN-BSC-Container INTEGER ::= 107
+id-GERAN-Classmark INTEGER ::= 108
+id-GERAN-Iumode-RAB-Failed-RABAssgntResponse-Item INTEGER ::= 109
+id-GERAN-Iumode-RAB-FailedList-RABAssgntResponse INTEGER ::= 110
+id-VerticalAccuracyCode INTEGER ::= 111
+id-ResponseTime INTEGER ::= 112
+id-PositioningPriority INTEGER ::= 113
+id-ClientType INTEGER ::= 114
+id-LocationRelatedDataRequestTypeSpecificToGERANIuMode INTEGER ::= 115
+id-SignallingIndication INTEGER ::= 116
+id-hS-DSCH-MAC-d-Flow-ID INTEGER ::= 117
+id-UESBI-Iu INTEGER ::= 118
+id-PositionData INTEGER ::= 119
+id-PositionDataSpecificToGERANIuMode INTEGER ::= 120
+id-CellLoadInformationGroup INTEGER ::= 121
+id-AccuracyFulfilmentIndicator INTEGER ::= 122
+id-InformationTransferType INTEGER ::= 123
+id-TraceRecordingSessionInformation INTEGER ::= 124
+id-TracePropagationParameters INTEGER ::= 125
+id-InterSystemInformationTransferType INTEGER ::= 126
+id-SelectedPLMN-ID INTEGER ::= 127
+id-RedirectionCompleted INTEGER ::= 128
+id-RedirectionIndication INTEGER ::= 129
+id-NAS-SequenceNumber INTEGER ::= 130
+id-RejectCauseValue INTEGER ::= 131
+id-APN INTEGER ::= 132
+id-CNMBMSLinkingInformation INTEGER ::= 133
+id-DeltaRAListofIdleModeUEs INTEGER ::= 134
+id-FrequenceLayerConvergenceFlag INTEGER ::= 135
+id-InformationExchangeID INTEGER ::= 136
+id-InformationExchangeType INTEGER ::= 137
+id-InformationRequested INTEGER ::= 138
+id-InformationRequestType INTEGER ::= 139
+```
+
+```
+
+id-IPMulticastAddress INTEGER ::= 140
+id-JoinedMBMSBearerServicesList INTEGER ::= 141
+id-LeftMBMSBearerServicesList INTEGER ::= 142
+id-MBMSBearerServiceType INTEGER ::= 143
+id-MBMSCNDe-Registration INTEGER ::= 144
+id-MBMSServiceArea INTEGER ::= 145
+id-MBMSsessionDuration INTEGER ::= 146
+id-MBMSsessionIdentity INTEGER ::= 147
+id-PDP-TypeInformation INTEGER ::= 148
+id-RAB-Parameters INTEGER ::= 149
+id-RAListofIdleModeUEs INTEGER ::= 150
+id-MBMSRegistrationRequestType INTEGER ::= 151
+id-SessionUpdateID INTEGER ::= 152
+id-TMGI INTEGER ::= 153
+id-TransportLayerInformation INTEGER ::= 154
+id-UnsuccessfulLinkingList INTEGER ::= 155
+id-MBMSLinkingInformation INTEGER ::= 156
+id-MBMSsessionRepetitionNumber INTEGER ::= 157
+id-AlternativeRABConfiguration INTEGER ::= 158
+id-AlternativeRABConfigurationRequest INTEGER ::= 159
+id-E-DCH-MAC-d-Flow-ID INTEGER ::= 160
+id-SourceBSS-ToTargetBSS-TransparentContainer INTEGER ::= 161
+id-TargetBSS-ToSourceBSS-TransparentContainer INTEGER ::= 162
+id-TimeToMBMSDataTransfer INTEGER ::= 163
+id-IncludeVelocity INTEGER ::= 164
+id-VelocityEstimate INTEGER ::= 165
+id-RedirectAttemptFlag INTEGER ::= 166
+id-RAT-Type INTEGER ::= 167
+id-PeriodicLocationInfo INTEGER ::= 168
+id-MBMSCountingInformation INTEGER ::= 169
+id-170-not-to-be-used-for-IE-ids INTEGER ::= 170
+id-ExtendedRNC-ID INTEGER ::= 171
+id-Alt-RAB-Parameter-ExtendedGuaranteedBitrateInf INTEGER ::= 172
+id-Alt-RAB-Parameter-ExtendedMaxBitrateInf INTEGER ::= 173
+id-Ass-RAB-Parameter-ExtendedGuaranteedBitrateList INTEGER ::= 174
+id-Ass-RAB-Parameter-ExtendedMaxBitrateList INTEGER ::= 175
+id-RAB-Parameter-ExtendedGuaranteedBitrateList INTEGER ::= 176
+id-RAB-Parameter-ExtendedMaxBitrateList INTEGER ::= 177
+id-Requested-RAB-Parameter-ExtendedMaxBitrateList INTEGER ::= 178
+id-Requested-RAB-Parameter-ExtendedGuaranteedBitrateList INTEGER ::= 179
+id-LAofIdleModeUEs INTEGER ::= 180
+id-newLAListofIdleModeUEs INTEGER ::= 181
+id-LAListwithNoIdleModeUEsAnyMore INTEGER ::= 182
+id-183-not-to-be-used-for-IE-ids INTEGER ::= 183
+id-GANSS-PositioningDataSet INTEGER ::= 184
+id-RequestedGANSSAssistanceData INTEGER ::= 185
+id-BroadcastGANSSAssistanceDataDecipheringKeys INTEGER ::= 186
+id-d-RNTI-for-NoIuCSUP INTEGER ::= 187
+id-RAB-SetupList-EnhancedRelocCompleteReq INTEGER ::= 188
+id-RAB-SetupItem-EnhancedRelocCompleteReq INTEGER ::= 189
+
+```
+
+```
+
+id-RAB-SetupList-EnhancedRelocCompleteRes INTEGER ::= 190
+id-RAB-SetupItem-EnhancedRelocCompleteRes INTEGER ::= 191
+id-RAB-SetupList-EnhRelocInfoReq INTEGER ::= 192
+id-RAB-SetupItem-EnhRelocInfoReq INTEGER ::= 193
+id-RAB-SetupList-EnhRelocInfoRes INTEGER ::= 194
+id-RAB-SetupItem-EnhRelocInfoRes INTEGER ::= 195
+id-OldIuSigConId INTEGER ::= 196
+id-RAB-FailedList-EnhRelocInfoRes INTEGER ::= 197
+id-RAB-FailedItem-EnhRelocInfoRes INTEGER ::= 198
+id-Global-ENB-ID INTEGER ::= 199
+id-UE-History-Information INTEGER ::= 200
+id-MBMSSynchronisationInformation INTEGER ::= 201
+id-SubscriberProfileIDforRFP INTEGER ::= 202
+id-CSG-Id INTEGER ::= 203
+id-OldIuSigConIdCS INTEGER ::= 204
+id-OldIuSigConIdPS INTEGER ::= 205
+id-GlobalCN-IDCS INTEGER ::= 206
+id-GlobalCN-IDPS INTEGER ::= 207
+id-SourceExtendedRNC-ID INTEGER ::= 208
+id-RAB-ToBeReleasedItem-EnhancedRelocCompleteRes INTEGER ::= 209
+id-RAB-ToBeReleasedList-EnhancedRelocCompleteRes INTEGER ::= 210
+id-SourceRNC-ID INTEGER ::= 211
+id-Relocation-TargetRNC-ID INTEGER ::= 212
+id-Relocation-TargetExtendedRNC-ID INTEGER ::= 213
+id-Alt-RAB-Parameter-SupportedGuaranteedBitrateInf INTEGER ::= 214
+id-Alt-RAB-Parameter-SupportedMaxBitrateInf INTEGER ::= 215
+id-Ass-RAB-Parameter-SupportedGuaranteedBitrateList INTEGER ::= 216
+id-Ass-RAB-Parameter-SupportedMaxBitrateList INTEGER ::= 217
+id-RAB-Parameter-SupportedGuaranteedBitrateList INTEGER ::= 218
+id-RAB-Parameter-SupportedMaxBitrateList INTEGER ::= 219
+id-Requested-RAB-Parameter-SupportedMaxBitrateList INTEGER ::= 220
+id-Requested-RAB-Parameter-SupportedGuaranteedBitrateList INTEGER ::= 221
+id-Relocation-SourceRNC-ID INTEGER ::= 222
+id-Relocation-SourceExtendedRNC-ID INTEGER ::= 223
+id-EncryptionKey INTEGER ::= 224
+id-IntegrityProtectionKey INTEGER ::= 225
+id-SRVCC-HO-Indication INTEGER ::= 226
+id-SRVCC-Information INTEGER ::= 227
+id-SRVCC-Operation-Possible INTEGER ::= 228
+id-CSG-Id-List INTEGER ::= 229
+id-PSRABtobeReplaced INTEGER ::= 230
+id-E-UTRAN-Service-Handover INTEGER ::= 231
+id-UE-AggregateMaximumBitRate INTEGER ::= 233
+id-CSG-Membership-Status INTEGER ::= 234
+id-Cell-Access-Mode INTEGER ::= 235
+id-IP-Source-Address INTEGER ::= 236
+id-CSFB-Information INTEGER ::= 237
+id-PDF-TypeInformation-extension INTEGER ::= 238
+id-MSISDN INTEGER ::= 239
+id-Offload-RAB-Parameters INTEGER ::= 240
+
+```
+
+```
+
+id-LGW-TransportLayerAddress INTEGER ::= 241
+id-Correlation-ID INTEGER ::= 242
+id-IRAT-Measurement-Configuration INTEGER ::= 243
+id-MDT-Configuration INTEGER ::= 244
+id-Priority-Class-Indicator INTEGER ::= 245
+id-RNSAPRelocationParameters INTEGER ::= 247
+id-RABParametersList INTEGER ::= 248
+id-Management-Based-MDT-Allowed INTEGER ::= 249
+id-HigherBitratesThan16MbpsFlag INTEGER ::= 250
+id-Trace-Collection-Entity-IP-Address INTEGER ::= 251
+id-End-Of-CSFB INTEGER ::= 252
+id-Time-UE-StayedInCell-EnhancedGranularity INTEGER ::= 253
+id-Out-Of-UTRAN INTEGER ::= 254
+id-TraceRecordingSessionReference INTEGER ::= 255
+id-IMSI INTEGER ::= 256
+id-HO-Cause INTEGER ::= 257
+id-VoiceSupportMatchIndicator INTEGER ::= 258
+id-RSRVCC-HO-Indication INTEGER ::= 259
+id-RSRVCC-Information INTEGER ::= 260
+id-AnchorPLMN-ID INTEGER ::= 261
+id-Tunnel-Information-for-BBF INTEGER ::= 262
+id-Management-Based-MDT-PLMN-List INTEGER ::= 263
+id-SignallingBasedMDTPLMNList INTEGER ::= 264
+id-M4Report INTEGER ::= 265
+id-M5Report INTEGER ::= 266
+id-M6Report INTEGER ::= 267
+id-M7Report INTEGER ::= 268
+id-TimingDifferenceULDL INTEGER ::= 269
+id-Serving-Cell-Identifier INTEGER ::= 270
+id-EARFCN-Extended INTEGER ::= 271
+id-RSRVCC-Operation-Possible INTEGER ::= 272
+id-LastE-UTRANPLMNIdentity INTEGER ::= 277
+
+```
+
+END
+
+### 9.3.7 Container Definitions
+
+```
+
+-- *****
+--
+-- Container definitions
+--
+-- *****
+
+RANAP-Containers {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ umts-Access (20) modules (3) ranap (0) version1 (1) ranap-Containers (5) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+```
+
+BEGIN
+
+```
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+```
+
+IMPORTS
+
+```
+ Criticality,
+ Presence,
+ PrivateIE-ID,
+ ProtocolExtensionID,
+ ProtocolIE-ID
+```
+
+FROM RANAP-CommonDataTypes
+
+```
+ maxPrivateIEs,
+ maxProtocolExtensions,
+ maxProtocolIEs
+```
+
+FROM RANAP-Constants;
+
+```
+-- *****
+--
+-- Class Definition for Protocol IEs
+--
+-- *****
+```
+
+RANAP-PROTOCOL-IES ::= CLASS {
+
+```
+ &id ProtocolIE-ID UNIQUE,
+ &criticality Criticality,
+ &Value,
+ &presence Presence
+}
+```
+
+WITH SYNTAX {
+
+```
+ ID &id
+ CRITICALITY &criticality
+ TYPE &Value
+ PRESENCE &presence
+}
+```
+
+```
+-- *****
+--
+-- Class Definition for Protocol IEs
+--
+-- *****
+```
+
+RANAP-PROTOCOL-IES-PAIR ::= CLASS {
+
+```
+ &id ProtocolIE-ID UNIQUE,
+ &firstCriticality Criticality,
+ &FirstValue,
+```
+
+```
+
+ &secondCriticality Criticality,
+ &SecondValue,
+ &presence Presence
+ }
+ WITH SYNTAX {
+ ID &id
+ FIRST CRITICALITY &firstCriticality
+ FIRST TYPE &FirstValue
+ SECOND CRITICALITY &secondCriticality
+ SECOND TYPE &SecondValue
+ PRESENCE &presence
+ }
+
+ -- *****
+ --
+ -- Class Definition for Protocol Extensions
+ --
+ -- *****
+
+ RANAP-PROTOCOL-EXTENSION ::= CLASS {
+ &id ProtocolExtensionID UNIQUE,
+ &criticality Criticality,
+ &Extension,
+ &presence Presence
+ }
+ WITH SYNTAX {
+ ID &id
+ CRITICALITY &criticality
+ EXTENSION &Extension
+ PRESENCE &presence
+ }
+
+ -- *****
+ --
+ -- Class Definition for Private IEs
+ --
+ -- *****
+
+ RANAP-PRIVATE-IES ::= CLASS {
+ &id PrivateIE-ID,
+ &criticality Criticality,
+ &Value,
+ &presence Presence
+ }
+ WITH SYNTAX {
+ ID &id
+ CRITICALITY &criticality
+ TYPE &Value
+ PRESENCE &presence
+ }
+
+```
+
+```
+
+-- *****
+--
+-- Container for Protocol IEs
+--
+-- *****
+
+ProtocolIE-Container {RANAP-PROTOCOL-IES : IEsSetParam} ::=
+ SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+ ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Field {RANAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {
+ id RANAP-PROTOCOL-IES.&id {{IEsSetParam}},
+ criticality RANAP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}},
+ value RANAP-PROTOCOL-IES.&value {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container for Protocol IE Pairs
+--
+-- *****
+
+ProtocolIE-ContainerPair {RANAP-PROTOCOL-IES-PAIR : IEsSetParam} ::=
+ SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+ ProtocolIE-FieldPair {{IEsSetParam}}
+
+ProtocolIE-FieldPair {RANAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE {
+ id RANAP-PROTOCOL-IES-PAIR.&id {{IEsSetParam}},
+ firstCriticality RANAP-PROTOCOL-IES-PAIR.&firstCriticality {{IEsSetParam}{@id}},
+ firstValue RANAP-PROTOCOL-IES-PAIR.&FirstValue {{IEsSetParam}{@id}},
+ secondCriticality RANAP-PROTOCOL-IES-PAIR.&secondCriticality {{IEsSetParam}{@id}},
+ secondValue RANAP-PROTOCOL-IES-PAIR.&SecondValue {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container Lists for Protocol IE Containers
+--
+-- *****
+
+ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, RANAP-PROTOCOL-IES : IEsSetParam} ::=
+ SEQUENCE (SIZE (lowerBound..upperBound)) OF
+ ProtocolIE-Container {{IEsSetParam}}
+
+ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, RANAP-PROTOCOL-IES-PAIR : IEsSetParam} ::=
+ SEQUENCE (SIZE (lowerBound..upperBound)) OF
+ ProtocolIE-ContainerPair {{IEsSetParam}}
+
+-- *****
+
+```
+
+```
+--
+-- Container for Protocol Extensions
+--
+-- *****
+
+ProtocolExtensionContainer {RANAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::=
+ SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
+ ProtocolExtensionField {{ExtensionSetParam}}
+
+ProtocolExtensionField {RANAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
+ id RANAP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}),
+ criticality RANAP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}),
+ extensionValue RANAP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id})
+}
+
+-- *****
+--
+-- Container for Private IEs
+--
+-- *****
+
+PrivateIE-Container {RANAP-PRIVATE-IES : IESetParam} ::=
+ SEQUENCE (SIZE (1.. maxPrivateIEs)) OF
+ PrivateIE-Field {{IESetParam}}
+
+PrivateIE-Field {RANAP-PRIVATE-IES : IESetParam} ::= SEQUENCE {
+ id RANAP-PRIVATE-IES.&id ({IESetParam}),
+ criticality RANAP-PRIVATE-IES.&criticality ({IESetParam}{@id}),
+ value RANAP-PRIVATE-IES.&Value ({IESetParam}{@id})
+}
+
+END
+```
+
+## 9.4 Message Transfer Syntax
+
+RANAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Rec. X.691 [13].
+
+## 9.5 Timers
+
+### $T_{\text{RELOCprep}}$
+
+- Specifies the maximum time for Relocation Preparation procedure in the source RNC.
+
+### $T_{\text{RELOCoverall}}$
+
+- Specifies the maximum time for the protection of overall Relocation procedure in the source RNC.
+
+### $T_{\text{RELOCalloc}}$
+
+- Specifies the maximum time for Relocation Resource Allocation procedure in the CN.
+
+### $T_{\text{RELOCcomplete}}$
+
+- Specifies the maximum time for waiting the relocation completion in the CN.
+
+### $T_{\text{RABAsstgt}}$
+
+- Specifies the maximum time in the CN for the whole RAB Assignment procedure.
+
+### $T_{\text{QUEUING}}$
+
+- Specifies the maximum time in the RNC for queuing of the request of RAB establishment or modification.
+
+### $T_{\text{DATAfwd}}$
+
+- Specifies the maximum time for GTP-PDU forwarding at the source RNC during relocation of SRNS.
+
+### $T_{\text{igOC}}$
+
+- While this timer is running, all OVERLOAD messages or signalling point congested information received at the CN are ignored.
+
+### $T_{\text{igOR}}$
+
+- While this timer is running, all OVERLOAD messages or signalling point congested information received at the RNC are ignored.
+
+### $T_{\text{inTC}}$
+
+- While this timer is running, the CN is not allowed to increase traffic.
+
+### $T_{\text{inTR}}$
+
+- While this timer is running, the RNC is not allowed to increase traffic.
+
+### $T_{\text{RatC}}$
+
+- Specifies the maximum time for Reset procedure in the RNC.
+
+### $T_{\text{RatC}}$
+
+- Specifies a guard period in the RNC before sending a RESET ACKNOWLEDGE message.
+
+### $T_{\text{RatR}}$
+
+- Specifies the maximum time for Reset procedure in the CN.
+
+### $T_{\text{RatR}}$
+
+- Specifies a guard period in the CN before sending a RESET ACKNOWLEDGE message.
+
+ $T_{\text{NNSF}}$
+
+- Specifies the maximum time the RNC may store *Permanent NAS UE Identity* IE (and the related *Global CN-ID* IE) when NNSF is active.
+
+# 10 Handling of Unknown, Unforeseen and Erroneous Protocol Data
+
+## 10.1 General
+
+Protocol Error cases can be divided into three classes:
+
+- Transfer Syntax Error.
+- Abstract Syntax Error.
+- Logical Error.
+
+Protocol errors can occur in the following functions within a receiving node:
+
+
+
+The diagram shows two boxes on the left and one on the right. The top-left box is labeled 'RANAP functional entity'. The bottom-left box is labeled 'ASN.1 Decoding'. A dashed double-headed arrow points between these two boxes. To the right of the top-left box is a bracket pointing to a list containing 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom-left box is a bracket pointing to 'Transfer Syntax Errors'. A large vertical arrow on the far right points upwards, spanning the height of both the top and bottom lists of errors.
+
+Diagram illustrating the relationship between RANAP functional entity, ASN.1 Decoding, and the resulting protocol errors.
+
+**Figure 10.1: Protocol Errors in RANAP.**
+
+The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1.
+
+## 10.2 Transfer Syntax Error
+
+A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error.
+
+Examples for Transfer Syntax Errors are:
+
+- Violation of value ranges in ASN.1 definition of messages. e.g.: If an IE has a defined value range of 0 to 10 (ASN.1: INTEGER (0..10)), and 12 will be received, then this will be treated as a transfer syntax error.
+- Violation in list element constraints. e.g.: If a list is defined as containing 1 to 10 elements, and 12 elements will be received, than this case will be handled as a transfer syntax error.
+- Missing mandatory elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message).
+- Wrong order of elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message).
+
+## 10.3 Abstract Syntax Error
+
+### 10.3.1 General
+
+An Abstract Syntax Error occurs when the receiving functional RANAP entity:
+
+1. receives IEs or IE groups that cannot be understood (unknown IE ID);
+2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message);
+3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message.
+4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group;
+5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message.
+
+Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure.
+
+If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error that belong to cases 1-3 act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6.
+
+### 10.3.2 Criticality Information
+
+In the RANAP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended, i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4.
+
+In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5).
+
+The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are:
+
+- Reject IE.
+- Ignore IE and Notify Sender.
+- Ignore IE.
+
+The following rules restrict when a receiving entity may consider an IE, an IE group, or an EP not comprehended (not implemented), and when action based on criticality information is applicable:
+
+1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by a receiving entity (some may still remain unsupported).
+2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied.
+
+### 10.3.3 Presence Information
+
+For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, RANAP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class RANAP-PROTOCOL-IES, RANAP-PROTOCOL-IES-PAIR, RANAP-PROTOCOL-EXTENSION or RANAP-PRIVATE-IES.
+
+The presence field of the indicated classes supports three values:
+
+1. Optional;
+2. Conditional;
+3. Mandatory.
+
+If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group.
+
+If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition is false according to the version of the specification used by the receiver, an abstract syntax error occurs due to this erroneously present conditional IE/IE group.
+
+### 10.3.4 Not comprehended IE/IE group
+
+#### 10.3.4.1 Procedure Code
+
+The receiving node shall treat the different types of received criticality information of the *Procedure Code* IE according to the following:
+
+##### Reject IE:
+
+- If a message is received with a *Procedure Code* IE marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure.
+
+##### Ignore IE and Notify Sender:
+
+- If a message is received with a *Procedure Code* IE marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure.
+
+##### Ignore IE:
+
+- If a message is received with a *Procedure Code* IE marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure.
+
+When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE.
+
+#### 10.3.4.1A Type of Message
+
+When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value.
+
+#### 10.3.4.2 IEs other than the Procedure Code and Type of Message
+
+The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following:
+
+##### Reject IE:
+
+- If a message *initiating* a procedure is received containing one or more IEs/IE group marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE group using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the
+
+initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+
+- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure.
+- If a *response* message is received containing one or more IEs marked with "*Reject IE*", that the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
+
+##### Ignore IE and Notify Sender:
+
+- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored.
+- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure.
+
+##### Ignore IE:
+
+- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.
+- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.
+
+When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex A2) also the *Message Structure* IE shall be included.
+
+When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex A2) also the *Message Structure* IE shall be included.
+
+### 10.3.5 Missing IE or IE group
+
+The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of this specification used by the receiver:
+
+#### Reject IE:
+
+- if a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Reject IE"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- if a received message initiating a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "Reject IE", the receiving node shall terminate the procedure and initiate the Error Indication procedure.
+- if a received response message is missing one or more IEs/IE groups with specified criticality "Reject IE", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
+
+#### Ignore IE and Notify Sender:
+
+- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.
+- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.
+
+#### Ignore IE:
+
+- if a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message.
+- if a received response message is missing one or more IEs/IE groups with specified criticality "Ignore IE", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message.
+
+When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex A2) also the *Message Structure* IE shall be included.
+
+When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex A2) also the *Message Structure* IE shall be included.
+
+### 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present
+
+If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following:
+
+- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)".
+- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
+
+When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered.
+
+## 10.4 Logical Error
+
+Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IEs/IE groups containing the erroneous values.
+
+### Class 1:
+
+Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are:
+
+- Semantic Error.
+- Message not compatible with receiver state.
+
+Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error.
+
+Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
+
+### Class 2:
+
+Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error.
+
+### Class 3:
+
+Where the logical error occurs in a request message of a class 3 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are:
+
+- Semantic Error.
+- Message not compatible with receiver state.
+
+Where the logical error is contained in a request message of a class 3 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error.
+
+Where the logical error exists in a response message of a class 3 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
+
+## 10.5 Exceptions
+
+The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10.
+
+- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling.
+- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
+- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure.
+
+# --- 11 Special Procedures for RNC to RNC Communication
+
+## 11.1 General
+
+This subclause specifies special procedures that are used for RNC to RNC communication, and that use other transport means than the RANAP procedures specified in clause 8.
+
+## 11.2 RANAP Relocation Information
+
+### 11.2.1 General
+
+The purpose of the RANAP Relocation Information procedure is to handle the RANAP-related information that is carried transparently during relocation from a source RNC to a target RNC by RNSAP via the Iur Interface.
+
+### 11.2.2 Operation
+
+When during relocation it becomes necessary in the source RNC to generate RANAP information for transfer to the relocation target, the RNC shall form a RANAP RELOCATION INFORMATION message. The message shall be encoded according to the encoding rules specified for RANAP in the similar manner as for the normal RANAP messages. The outcome of the encoding will be an octet string, which shall not be sent to the CN via the Iu Interface, but shall be given to the appropriate local process for transparent transfer to the target RNC.
+
+When the RANAP process in the target RNC receives an octet string containing a RANAP RELOCATION INFORMATION message that had been transparently transferred from the source RNC, it shall decode it according to the encoding rules specified for RANAP. This process is similar to receiving any normal RANAP message. The decoded information shall be passed to the appropriate processes in the RNC.
+
+The RANAP RELOCATION INFORMATION message may contain the *Direct Transfer Information List* IE, the *RAB Contexts List* IE and the *Source RNC PDCP context info* IE. If present, the *Direct Transfer Information List* IE shall contain the *NAS-PDU* IE, the *SAPI* IE and the *CN Domain Indicator* IE. If present, the *RAB Contexts List* IE shall contain for each addressed RAB:
+
+- the RAB ID IE;
+
+- if available, the DL GTP-PDU Sequence Number IE;
+- if available, the UL GTP-PDU Sequence Number IE;
+- if available, the DL N-PDU Sequence Number IE;
+- if available, the UL N-PDU Sequence Number IE.
+
+#### **Handling in case of RNSAP Relocation:**
+
+In case of RNSAP Relocation for each CS RAB operated in support mode (see TS 25.415 [6] for the definition of “support mode”) the source RNC shall include within the RANAP RELOCATION INFORMATION message the *RNSAP Relocation Parameters* IE containing the *RAB Parameters List* IE which shall include the *UP Information* IE. For each CS RAB operated in support mode for which the user data frame numbering is based on time the source RNC shall include the *Timing Difference UL-DL* IE within the *UP Information* IE.
+
+In case of RNSAP Relocation for each PS RAB for which data volume reporting was configured, the source RNC shall include the *RAB Data Volume Reports* IE within the *RAB Parameters List* IE included in the RANAP RELOCATION INFORMATION message.
+
+In case Location Reporting was configured at the source RNC for periodic reporting and/or report upon change of Service area and/or direct reporting, the source RNC shall include the *Location Reporting Transfer Information* IE within the RANAP RELOCATION INFORMATION message.
+
+The *Periodic Reporting Indicator* IE within the *Location Reporting Transfer Information* IE shall be set to “periodic SAI” if periodic reporting is requested and the location information is requested to be a Service Area Identifier, to “periodic Geo” if periodic reporting is requested and the location information is requested to be a geographical area.
+
+The *Direct Reporting Indicator* IE within the *Location Reporting Transfer Information* IE shall be set to “direct SAI” if periodic reporting is requested and the location information is requested to be a Service Area Identifier, to “direct Geo” if periodic reporting is requested and the location information is requested to be a geographical area.
+
+The conditions for the presence of further IEs within the *Location Reporting Transfer Information* are specified in subclause 8.19.2.
+
+If signalling based trace activation was triggered at the source RNC, the RANAP RELOCATION INFORMATION shall contain the *UE Identity* IE and the *Trace Propagation Parameters* IE in order to continue tracing at the target RNC accordingly.
+
+## **11.3 RANAP Enhanced Relocation Information**
+
+### **11.3.1 General**
+
+The purpose of the RANAP Enhanced Relocation Information procedure is to handle the RANAP-related information that is carried transparently during enhanced relocation from a source RNC to a target RNC by RNSAP via the Iur Interface.
+
+### **11.3.2 Operation**
+
+When during enhanced relocation it becomes necessary in the source RNC to generate RANAP information for transfer to the relocation target, the source RNC shall form a RANAP ENHANCED RELOCATION INFORMATION REQUEST message. The message shall be encoded according to the encoding rules specified for RANAP in the similar manner as for the normal RANAP messages. The outcome of the encoding will be an octet string, which shall be given to the appropriate local process for transparent transfer to the target RNC.
+
+When the RANAP process in the target RNC receives an octet string containing a RANAP ENHANCED RELOCATION INFORMATION REQUEST message that had been transparently transferred from the source RNC, it shall decode it according to the encoding rules specified for RANAP. This process is similar to receiving any normal RANAP message. The decoded information shall be passed to the appropriate processes in the RNC.
+
+Upon reception of the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the target RNC shall initiate allocation of requested resources.
+
+The RANAP ENHANCED RELOCATION INFORMATION REQUEST message shall contain the following IE:
+
+- *Source RNC To Target RNC Transparent Container IE*;
+
+The RANAP ENHANCED RELOCATION INFORMATION REQUEST message may contain the following IEs:
+
+- *Old Iu Signalling Connection Identifier CS domain IE*; if a connection to the CS domain exist;
+- *Old Iu Signalling Connection Identifier PS domain IE*; if a connection to the PS domain exist;
+- *Global CN-ID for CS*, if a connection to the CS domain exist;
+- *Global CN-ID for PS*, if a connection to the PS domain exist;
+- *RABs to be Setup List*;
+- *SNA Access Information IE* (if available);
+- *UESBI-Iu IE* (if available);
+- *Selected PLMN identity IE* if in MOCN or GWCN configuration;
+- *CN MBMS Linking Information IE* (if available);
+- *UE Aggregate Maximum Bit Rate IE*;
+- *Anchor PLMN Identity IE* (if available).
+
+For each RAB requested to relocate in the RABs to be Setup List, the RANAP ENHANCED RELOCATION INFORMATION REQUEST message shall contain the following IEs in the *RABs To Be Setup List IE*:
+
+- *RAB ID IE*;
+- *CN domain indicator IE*;
+- *RAB parameters IE*;
+- *User Plane Information IE*;
+- *Source Side Iu UL TNL Information IE*;
+- *Data Volume Reporting Indication IE* (only for PS);
+- *PDP Type Information IE* (only for PS).
+
+For each RAB requested to relocate the message may include the following IEs:
+
+- *Data Forwarding TNL Information IE*;
+- *Service Handover IE*;
+- *Alternative RAB Parameter Values IE*;
+- *E-UTRAN Service Handover IE*;
+- *PDP Type Information extension IE* (may be included if *PDP Type Information IE* is included).
+
+If the *Data Forwarding TNL Information IE* is included in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, it indicates Iur UP resources, made available by the source RNC for forwarding of UL user data.
+
+- Note: The *Source Side Iu UL TNL Information IE* (in contrary to the *Data Forwarding TNL Information IE*) contains information to enable the target RNC to start transmission of user data towards the CN once the relocations has been successfully executed.
+
+If the *UE Aggregate Maximum Bit Rate IE* is included in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the target side shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non-GBR traffic for this UE.
+
+The RANAP ENHANCED RELOCATION INFORMATION REQUEST message shall contain the information (if any) required by the target RNC to build at least the same set of RABs as existing for the UE before the relocation and
+
+therefore the RANAP ENHANCED RELOCATION INFORMATION REQUEST may contain the *RABs to be SETUP List* IE.
+
+The resource allocation actions executed by the target RNC are:
+
+If the *Relocation Type* IE is set to "UE involved in relocation of SRNS":
+
+- The target RNC should not accept a requested RAB if the RAB did not exist in the source RNC before the relocation;
+- The target RNC may accept a requested RAB only if the RAB can be supported by the target RNC;
+- Other RABs shall be rejected by the target RNC in the RANAP ENHANCED RELOCATION INFORMATION RESPONSE message with an appropriate value in the *Cause* IE, e.g. "Unable to Establish During Relocation";
+- The target RNC shall include information adapted to the resulting RAB configuration in the target to source RNC transparent container to be included in the RANAP ENHANCED RELOCATION INFORMATION RESPONSE message sent to the source RNC;
+- If any alternative RAB parameter values have been used when allocating the resources, these RAB parameter values shall be included in the RANAP ENHANCED RELOCATION INFORMATION RESPONSE message within the *Assigned RAB Parameter Values* IE;
+- If *d-RNTI for No IuCS UP* IE is contained in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the target RNC shall use this information to configure the resource for the UE over Iur during the relocation.
+
+If the *Relocation Type* IE is set to "UE not involved in relocation of SRNS":
+
+- The target RNC shall not accept a requested RAB if the RAB did not exist in the source RNC before the relocation;
+- The target RNC may accept a RAB only if the radio bearer(s) for the RAB either exist(s) already and can be used for the RAB by the target RNC, or do(es) not exist before the relocation but can be established in order to support the RAB in the target RNC;
+- If existing radio bearers are not related to any RAB that is accepted by the target RNC, the radio bearers shall be ignored during the relocation of SRNS and the radio bearers shall be released by the radio interface protocols after completion of relocation of SRNS;
+- Usage of alternative RAB parameter values is not applicable for any relocation of type "UE not involved in relocation of SRNS".
+
+If the *UE History Information* IE is included in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message and the target RNC is configured to collect the information, the target RNC shall, if supported, collect information defined in the *UE History Information* IE.
+
+The *Global CN ID* IE and *Old Iu Signalling Identifier* IE (for PS and/or for CS) are used by the target RNC to establish new Iu Signalling connection(s) between the target RNC towards the CS and/or PS domain.
+
+The RANAP ENHANCED RELOCATION INFORMATION REQUEST message may also include an alternative RAB configuration for a RAB specified in the *Alternative RAB configuration* IE in the *Alternative RAB Parameter Values* IE. If *Alternative RAB configuration* IE for a RAB is included in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the target RNC is allowed to use the alternative configuration.
+
+The RNC shall, if supported, use the *UESBI-Iu* IE when included in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message. If *UESBI-Iu* IE contains an IMEISV the RNC may use this information to determine the characteristics of the UE for subsequent handling.
+
+If the *CN MBMS Linking Information* IE is included in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the RNC shall, if supported, use the *CN MBMS Linking Information* IE to perform suitable UE linking as described in TS 25.346 [42].
+
+If the *SNA Access Information* IE is contained in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the target RNC shall store this information and use it to determine whether the UE has access to radio resources in the UTRAN. The target RNC shall consider that the UE is authorised to access only the PLMNs
+
+identified by the *PLMN identity* IE in the *SNA Access Information* IE. If the *Authorised SNAs* IE is included for a given PLMN (identified by the *PLMN identity* IE), then the target RNC shall consider that the access to radio resources for the concerned UE is restricted to the LAs contained in the SNAs identified by the *SNAC* IEs.
+
+If the *SNA Access Information* IE is not contained in the RANAP ENHANCED RELOCATION INFORMATION REQUEST message, the target RNC shall consider that no access restriction applies to the UE in the UTRAN.
+
+If the *Trace Recording Session Information* IE is provided within the *Source RNC to Target RNC Transparent Container* IE, the Target RNC should store that information to include it in a potential future Trace Record for that UE.
+
+After all necessary resources for accepted RABs including the initialised Iu user plane, are successfully allocated, the target RNC shall send a RANAP ENHANCED RELOCATION INFORMATION RESPONSE message to the source RNC.
+
+For each RAB successfully setup the RNC shall include the following IEs in the *RABs Setup List* IE:
+
+- *RAB ID*.
+
+For each RAB the target RNC has admitted to execute data forwarding, the target RNC shall include the *Data Forwarding Information* IE in the RANAP ENHANCED RELOCATION INFORMATION RESPONSE message. If no ALCAP is used, the RNC shall include the *DL Forwarding Transport Layer Address* IE and the *DL Forwarding Transport Association* IE within the *Data Forwarding Information* IE in the RANAP ENHANCED RELOCATION INFORMATION RESPONSE message.
+
+If applicable, the target RNC shall have executed the initialisation of the user plane mode between the source and the target RNC as requested by the source RNC in the *User Plane Mode* IE. If the target RNC can not initialise the requested user plane mode for any of the user plane mode versions in the *UP Mode Versions* IE according to the rules for initialisation of the respective user plane mode versions, as described in TS 25.415 [6], the target RNC may either decide to not relocate the respective RAB or to omit data forwarding for that RAB.
+
+For each RAB the RNC is not able to setup during the Enhanced Relocation Information procedure, the RNC shall include the *CN Domain Indicator* IE *RAB ID* IE and the *Cause* IE within the *RABs Failed To Setup* IE. The resources associated with the RABs indicated as failed to set up shall not be released in the source RNC until the relocation is completed. This is in order to make a return to the old configuration possible in case of a failed or cancelled relocation.
+
+The RANAP ENHANCED RELOCATION INFORMATION RESPONSE message sent to the source RNC shall, if applicable, include the *Target RNC To Source RNC Transparent Container* IE.
+
+#### **Handling in case of RNSAP Relocation:**
+
+In case of RNSAP Relocation for each CS RAB operated in support mode (see TS 25.415 [6] for the definition of “support mode”) the source RNC shall include within the RANAP ENHANCED RELOCATION INFORMATION REQUEST message the *RAB Parameters List* IE which shall include the *UP Information* IE. For each CS RAB operated in support mode for which the user data frame numbering is based on time the source RNC shall include the *Timing Difference UL-DL* IE within the *UP Information* IE.
+
+The source RNC shall also include within the RANAP ENHANCED RELOCATION INFORMATION REQUEST message
+
+- the *CSG Id* IE (if available),
+- the *CSG Membership Status* IE (if available).
+
+#### **Handling in case of Enhanced Relocation between RNC and hybrid cell:**
+
+The source RNC shall also include within the RANAP ENHANCED RELOCATION INFORMATION REQUEST message the *CSG Id* IE, if available. If the *CSG Id* IE is included, the *CSG Membership Status* IE shall be included as well.
+
+# Annex A (informative): RANAP guidelines
+
+## A.1 Rules for building RANAP messages
+
+### A.1.1 Rules for RANAP messages that shall contain the CN Domain Indicator IE
+
+Based on the principles described in TS 25.401 [3], the following rules can be deduced:
+
+- 1) The following RANAP messages initiating a connection oriented signalling connection shall contain the *CN Domain Indicator* IE: INITIAL UE MESSAGE message and RELOCATION REQUEST message.
+- 2) Any RANAP message belonging to class 1 procedures and which uses connectionless signalling shall contain the *CN Domain Indicator* IE.
+- 3) The following RANAP messages belonging to class 2 procedures and using connectionless signalling shall contain the *CN Domain Indicator* IE: PAGING message and ERROR INDICATION message, the OVERLOAD message in DL direction (see chapter 8.25.3.1) may contain the *CN Domain Indicator* IE.
+
+## A.2 Guidelines for Usage of the Criticality Diagnostics IE
+
+### A.2.1 EXAMPLE MESSAGE Layout
+
+Assume the following message format:
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-----------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | | | YES | reject |
+| A | M | | | | YES | reject |
+| B | M | | | | YES | reject |
+| >E | | 1.. | | | EACH | ignore |
+| >>F | | 1.. | | | - | |
+| >>>G | | 0..3, ... | | | EACH | ignore |
+| >>H | | 1.. | | | EACH | ignore |
+| >>>G | | 0..3, ... | | | EACH | ignore and notify |
+| >>G | M | | | | YES | reject |
+| >>J | | 1.. | | | - | |
+| >>>G | | 0..3, ... | | | EACH | reject |
+| C | M | | | | YES | reject |
+| >K | | 1.. | | | EACH | ignore and notify |
+| >>L | | 1.. | | | - | |
+| >>>M | O | | | | - | |
+| D | M | | | | YES | reject |
+
+NOTE 1: The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of "ordinary" ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Container.
+
+For the corresponding ASN.1 layout, see subclause A.2.4.
+
+### A.2.2 Example on a Received EXAMPLE MESSAGE
+
+Assume further more that a received message based on the above tabular format is according to the figure below.
+
+
+
+The diagram illustrates the structure of a received RANAP message across four levels:
+
+- Level 1 (top level):** Contains four boxes labeled A, B, C, and D.
+- Level 2:** Contains two boxes labeled E and K. Box E is connected to box B. Box K is connected to box C.
+- Level 3:** Contains five boxes labeled F, H, G, J, and L. Box F is connected to box E. Box H is connected to box E. Box G is connected to box E. Box J is connected to box K. Box L is connected to box K.
+- Level 4:** Contains seven boxes labeled G. Three are connected to box F, one to box H, one to box J, and two to box L.
+
+**Legend:**
+
+- 1st repetition
+- 2nd repetition
+- ...
+- Nth repetition
+
+**IE based on a protocol container**
+
+**IE being an "ordinary" ASN.1 type**
+
+A hierarchical diagram showing the content of a received RANAP message across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C). Level 3 contains F (under E), H (under E), G (under E), J (under K), and L (under K). Level 4 contains seven G boxes: three under F, one under H, one under J, and two under L. Below the diagram is a legend for repetitions (1st, 2nd, Nth) and a legend for IE types (IE based on a protocol container, IE being an 'ordinary' ASN.1 type).
+
+Figure A.1: Example of content of a received RANAP message based on the EXAMPLE MESSAGE
+
+### A.2.3 Content of Criticality Diagnostics
+
+#### A.2.3.1 Example 1
+
+
+
+Level 1 (top level)
+
+Level 2
+
+Level 3
+
+Level 4
+
+Included in the *Message Structure IE*.
+
+Included in the *Information Element Criticality Diagnostics IE*:
+
+- IE ID IE
+- Repetition Number IE
+
+Diagram illustrating the hierarchy of Information Elements (IEs) in a RANAP message. The diagram shows four levels: Level 1 (top level) with IEs A, B, C, and D; Level 2 with IE E (connected to B) and IE K (connected to C); Level 3 with IEs F, H, G, J, and L (connected to E and K); and Level 4 with multiple instances of IE G (connected to F, H, G, J, and L). IE E is shown with four repetitions. IE J is shown with three dashed boxes, indicating it is not comprehended. IE G is shown with seven instances, with the eleventh instance (instance 11 of the third repetition of IE G under IE J) highlighted in grey. Arrows indicate that IE E is included in the Message Structure IE and that the grey instance of IE G is included in the Information Element Criticality Diagnostics IE. A list below the diagram specifies the contents of the Information Element Criticality Diagnostics IE: a) IE ID IE, b) Repetition Number IE.
+
+**Figure A.2: Example of a received RANAP message containing a not comprehended IE**
+
+If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure A.2 above, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows:
+
+| IE name | Value | Comment |
+|---------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 4. |
+| IE ID | id-G | IE ID from the reported level, i.e. level 4. |
+| Repetition Number | 11 | Repetition number on the reported level, i.e. level 4.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the eleventh occurrence of IE G within the IE E (level 2).) |
+| Type of Error | not understood | |
+| Message Structure, first repetition | | |
+| >IE ID | id-B | IE ID from level 1. |
+| Message Structure, second repetition | | |
+| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. |
+| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. |
+
+NOTE 2: The IE J on level 3 cannot be included in the *Message Structure IE* since they have no criticality of their own.
+
+NOTE 3: The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).
+
+#### A.2.3.2 Example 2
+
+
+
+Level 1 (top level)
+
+Level 2
+
+Level 3
+
+Level 4
+
+Included in the *Message Structure IE*.
+
+Included in the *Information Element Criticality Diagnostics IE*:
+
+- a) *IE ID IE*
+- b) *Repetition Number IE*
+
+A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C). Level 3 contains F (under E), H (under E), G (under E), J (under K), and L (under K). Level 4 contains multiple instances of G (under F, H, G, J, and L). Annotations indicate that IE C is included in the Message Structure IE, and IEs F, H, G, J, and L are included in the Information Element Criticality Diagnostics IE. Sub-points a) IE ID IE and b) Repetition Number IE are listed under the diagnostics IE.
+
+**Figure A.3: Example of a received RANAP message containing a not comprehended IE**
+
+If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 below IE K in the structure shown in the figure A.3 above, this will be reported within the *Information Element Criticality Diagnostics IE* as follows:
+
+| IE name | Value | Comment |
+|---------------------------------------------------|-------------------|---------------------------------------------------------------------|
+| IE Criticality | ignore and notify | Criticality for IE on the reported level, i.e. level 2. |
+| IE ID | id-K | IE ID from the reported level, i.e. level 2. |
+| Repetition Number | 3 | Repetition number on the reported level, i.e. level 2. |
+| Type of Error | not understood | |
+| Message Structure, first repetition | | |
+| >IE ID | id-C | IE ID from the lowest level above the reported level, i.e. level 1. |
+
+NOTE 4: The IE L on level 3 cannot be reported individually included in the *Message Structure IE* since it has no criticality of its own.
+
+#### A.2.3.3 Example 3
+
+
+
+Level 1 (top level)
+
+Level 2
+
+Level 3
+
+Level 4
+
+Included in the *Message Structure IE*.
+
+Included in the *Information Element Criticality Diagnostics IE*:
+
+- IE ID IE*
+- Repetition Number IE*
+
+Diagram illustrating a hierarchical structure of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with repetitions 1, 2, 3, 4) and K. Level 3 contains F, H (with repetitions 1, 2), G, J, and L. Level 4 contains multiple instances of G, with one instance in H having repetitions 1, 2, 3. Arrows indicate relationships: from B to E, from E to H, from C to K, and from K to H. Text labels indicate that the structure is 'Included in the Message Structure IE' and 'Included in the Information Element Criticality Diagnostics IE'.
+
+**Figure A.4: Example of a received RANAP message containing a not comprehended IE**
+
+If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure A.4 above, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows:
+
+| IE name | Value | Comment |
+|---------------------------------------------|-------------------|---------------------------------------------------------------------------------|
+| IE Criticality | ignore and notify | Criticality for IE on the reported level, i.e. level 4. |
+| IE ID | id-G | IE ID from the reported level, i.e. level 4. |
+| Repetition Number | 2 | Repetition number on the reported level, i.e. level 4. |
+| Type of Error | not understood | |
+| Message Structure, first repetition | | |
+| >IE ID | id-B | IE ID from level 1. |
+| Message Structure, second repetition | | |
+| >IE ID | id-E | IE ID from level 2. |
+| >Repetition Number | 3 | Repetition number from level 2. |
+| Message Structure, third repetition | | |
+| >IE ID | id-H | IE ID from the lowest level above the reported level, i.e. level 3. |
+| >Repetition Number | 1 | Repetition number from the lowest level above the reported level, i.e. level 3. |
+
+NOTE 5: The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected erroneous repetition, counted below the same instance of the previous level with assigned criticality (instance 1 of IE H on level 3).
+
+#### A.2.3.4 Example 4
+
+
+
+Diagram illustrating a received RANAP message structure with nested Information Elements (IEs) across four levels. Level 1 (top level) contains IEs A, B, C, and D. Level 2 contains IE E (under B) and IE K (under C). Level 3 contains IEs F, H, G (grey, marked with error), J, and L. Level 4 contains multiple instances of IE G. Arrows indicate the hierarchy and specific references: an arrow from C points to E, labeled 'Included in the Message Structure IE.'; an arrow from the grey IE G points to the text 'Included in the Information Element Criticality Diagnostics IE: a) IE ID IE b) Repetition Number IE'.
+
+**Figure A.5: Example of a received RANAP message containing a not comprehended IE**
+
+If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure A.5 above, this will be reported within the *Information Element Criticality Diagnostics* IE within the *Criticality Diagnostics* IE as follows:
+
+| IE name | Value | Comment |
+|---------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 3. |
+| IE ID | id-G | IE ID from the reported level, i.e. level 3. |
+| Repetition Number | 5 | Repetition number on the reported level, i.e. level 3.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the fifth occurrence of IE G within the IE E (level 2).) |
+| Type of Error | not understood | |
+| Message Structure, first repetition | | |
+| >IE ID | id-B | IE ID from level 1. |
+| Message Structure, second repetition | | |
+| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. |
+| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. |
+
+NOTE 6: The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).
+
+#### A.2.3.5 Example 5
+
+
+
+Diagram illustrating a received RANAP message with a missing IE. The diagram shows four levels of hierarchy. Level 1 (top level) contains IEs A, B, C, and D. Level 2 contains IE E (with instances 1, 2, 3, 4) and IE K. Level 3 contains IEs F, H, G (shaded grey), J, and L. Level 4 contains multiple instances of IE G (labeled 1, 2, 3; 4; 5, 6, 7; 8; 9, 10, 11; 12, 3). Arrows indicate relationships: from C to B, from B to E, from E to F, H, G, J, L, and from K to L. A note 'Included in the Message Structure IE.' points to the B-C relationship. Another note 'Included in the Information Element Criticality Diagnostics IE:' points to instance 4 of IE G at Level 4, with sub-points 'a) IE ID IE' and 'b) Repetition Number IE'.
+
+**Figure A.6: Example of a received RANAP message with a missing IE**
+
+If the instance marked as grey in the IE G in the IE E shown in the figure A.6 above, is missing this will be reported within the *Information Element Criticality Diagnostics* IE within the *Criticality Diagnostics* IE as follows:
+
+| IE name | Value | Comment |
+|---------------------------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 3. |
+| IE ID | id-G | IE ID from the reported level, i.e. level 3. |
+| Repetition Number | 4 | Repetition number up to the missing IE on the reported level, i.e. level 3. (Since the IE E (level 2) is the lowest level included in the Message Structure IE there have been four occurrences of IE G within the IE E (level 2) up to the missing occurrence. |
+| Type of Error | missing | |
+| Message Structure, first repetition | | |
+| >IE ID | id-B | IE ID from level 1. |
+| Message Structure, second repetition | | |
+| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. |
+| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. |
+
+NOTE 7: The repetition number of the reported IE indicates the number of repetitions of IE G received up to but not including the missing occurrence, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).
+
+### A.2.4 ASN.1 of EXAMPLE MESSAGE
+
+```
+
+ExampleMessage ::= SEQUENCE {
+ ProtocolIEs ProtocolIE-Container {{ExampleMessage-IEs}},
+ ProtocolExtensions ProtocolExtensionContainer {{ExampleMessage-Extensions}} OPTIONAL,
+ ...
+}
+
+ExampleMessage-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-A CRITICALITY reject TYPE A PRESENCE mandatory} |
+ { ID id-B CRITICALITY reject TYPE B PRESENCE mandatory} |
+ { ID id-C CRITICALITY reject TYPE C PRESENCE mandatory} |
+ { ID id-D CRITICALITY reject TYPE D PRESENCE mandatory} ,
+ ...
+}
+
+B ::= SEQUENCE {
+ e E-List,
+ iE-Extensions ProtocolExtensionContainer { {B-ExtIEs} } OPTIONAL,
+ ...
+}
+
+B-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Container { {E-IEs} }
+
+E-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-E CRITICALITY ignore TYPE E PRESENCE mandatory },
+ ...
+}
+
+E ::= SEQUENCE {
+ f F-List,
+ h H-List,
+ g G-List1,
+ j J-List,
+ iE-Extensions ProtocolExtensionContainer { {E-ExtIEs} } OPTIONAL,
+ ...
+}
+
+E-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+F-List ::= SEQUENCE (SIZE (1..maxF)) OF F
+
+F ::= SEQUENCE {
+ g G-List2 OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {F-ExtIEs} } OPTIONAL,
+ ...
+}
+
+F-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G2-IEs} }
+
+G2-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-G CRITICALITY ignore TYPE G PRESENCE mandatory },
+ ...
+}
+
+H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Container { {H-IEs} }
+
+H-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-H CRITICALITY ignore TYPE H PRESENCE mandatory },
+ ...
+}
+
+H ::= SEQUENCE {
+ g G-List3 OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {H-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+H-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G3-IEs} }
+
+G3-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-G CRITICALITY notify TYPE G PRESENCE mandatory },
+ ...
+}
+
+G-List1 ::= ProtocolIE-Container { {G1-IEs} }
+
+G1-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-G CRITICALITY reject TYPE G PRESENCE mandatory },
+ ...
+}
+
+J-List ::= SEQUENCE (SIZE (1..maxJ)) OF J
+
+J ::= SEQUENCE {
+ g G-List4 OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {J-ExtIEs} } OPTIONAL,
+ ...
+}
+
+J-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G4-IEs} }
+
+G4-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-G CRITICALITY reject TYPE G PRESENCE mandatory },
+ ...
+}
+
+C ::= SEQUENCE {
+ k K-List,
+ iE-Extensions ProtocolExtensionContainer { {C-ExtIEs} } OPTIONAL,
+ ...
+}
+
+C-ExtIEsA -PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+K-List ::= SEQUENCE (SIZE (1..maxK)) OF ProtocolIE-Container { {K-IEs} }
+
+K-IEs RANAP-PROTOCOL-IES ::= {
+ { ID id-K CRITICALITY notify TYPE K PRESENCE mandatory },
+ ...
+}
+
+K ::= SEQUENCE {
+ l L-List,
+ iE-Extensions ProtocolExtensionContainer { {K-ExtIEs} } OPTIONAL,
+ ...
+}
+
+K-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+L-List ::= SEQUENCE (SIZE (1..maxL)) OF L
+
+L ::= SEQUENCE {
+ m M OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {L-ExtIEs} } OPTIONAL,
+ ...
+}
+
+L-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ExampleMessage-Extensions RANAP-PROTOCOL-EXTENSION ::= {
+```
+
+Error:
+
+125
+
+Error: Reference source not found
+
+} ...
+
+# Annex B (informative): RANAP Transparent containers content
+
+Transparent containers are used in order to transfer information from one RAN node to another RAN node. Depending on the particular scenario the behaviour of both involved RAN nodes may be either specified according to the same radio system or according to different radio systems. During an inter-system handover the source RAN node has to adopt to the target RAN node and its requirements.
+
+In RANAP, for intra-system relocation and inter-system handover to and from E-UTRAN, there is a single transparent container defined for transporting information from the source to the target RAN node and a single transparent container for transporting information from the target to the source RAN node during relocation/handover preparation: the *Source to Target Transparent Container* IE and the *Target to Source Transparent Container* IE, which may carry either UTRAN or E-UTRAN specific information.
+
+Note: The definition of generic transparent containers for relocation/handover purposes allows to transport them through the core network in a RAT-agnostic way. Inter-system handover to GERAN is not affected by this scheme.
+
+Therefore the container content is encoded according to the rules which are specified for in the target radio system. In subclause 8.6.2, it is described how the transparent container shall be encoded with respect to the scenario in which it is used.
+
+The table below is showing all possible scenarios and definitions according to which the content of the transparent container shall be encoded. Additionally the reference to the specification defining particular IE is given.
+
+**Table B.1: Specification of Transparent Containers referenced in RANAP.**
+
+| Scenario | Source to Target Transparent Container IE in RANAP: RELOCATION REQUIRED message | | Target to Source Transparent Container IE in RANAP: RELOCATION COMMAND message | |
+|-----------------------------------------|----------------------------------------------------------------------------------------|-----------------------------|---------------------------------------------------------------------------------------|-----------------------------|
+| | Name of the IE | Definition in specification | Name of the IE | Definition in specification |
+| Intra UTRAN relocation | Source RNC to Target RNC Transparent Container | 25.413 | Target RNC to Source RNC Transparent Container | 25.413 |
+| Inter-system handover to E-UTRAN | Source eNB to Target eNB Transparent Container | 36.413 | Target eNB to Source eNB Transparent Container | 36.413 |
+
+# --- Annex C (informative): Processing of Transparent Containers at the SGSN
+
+Irrespective of the mobility scenario (inter-RAT or intra-UMTS), the SGSN always processes the *Source to Target Transparent Container* IE and the *Target to Source Transparent Container* IE in the following way:
+
+- The SGSN shall convey to the RNC the information received within
+ - the GTPv1-C "UTRAN transparent field" of the "UTRAN Transparent Container" IE across the Gn interface (see subclause 7.7.38 of TS 29.060 [35]), or
+ - the GTPv2 "F-container field" of the "F-Container" IE across the S3/S16 interface (see subclause 8.48 of TS 29.274 [36])
+
+by including it in either the *Source to Target Transparent Container* IE or the *Target to Source Transparent Container* of the corresponding RANAP message.
+
+- The SGSN shall convey to the GTP peer the information received within either the *Source to Target Transparent Container* IE or the *Target to Source Transparent Container* IE by including it in
+ - the GTPv1-C "UTRAN transparent field" of the "UTRAN Transparent Container" IE across the Gn interface (see subclause 7.7.38 of TS 29.060 [35]), or
+ - the GTPv2 "F-container field" of the "F-Container" IE across the S3/S16 interface (see subclause 8.48 of TS 29.274 [36]).
+
+# --- Annex D (informative): Change History
+
+| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New |
+|-------|------------------------|-------------------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------|-------|
+| 06 | RP-99746 | - | | Approved at TSG RAN #6 and placed under Change Control | 3.0.0 |
+| 07 | - | - | | Approved at TSG RAN #7 | 3.1.0 |
+| 08 | - | - | | Approved at TSG RAN #8 | 3.2.0 |
+| 09 | RP-000373 | 124-
136,
138,
168-
171,
173,
174 | | Approved at TSG RAN #9 | 3.3.0 |
+| 09 | RP-000374 | 175,
177-
179,
181-
184 | | Approved at TSG RAN #9 | 3.3.0 |
+| 10 | RP-000613
RP-000695 | 185-
191,
194-
199,
201,
203-
207,
210-
214,
219,
221-
232,
234,
235 | | Approved at TSG RAN #10 | 3.4.0 |
+| 11 | RP-010110 | 236,
238,
240-
243,
245-
246,
248,
249,
253-
258,
260,
261,
263,
266 | | Approved at TSG RAN #11 | 3.5.0 |
+| 11 | RP-010111 | 268,
275 | | Approved at TSG RAN #11 | 3.5.0 |
+| 11 | RP-010158 | 271 | | Approved at TSG RAN #11 and placed under Change Control | 4.0.0 |
+| 11 | RP-010189 | 265 | | Approved at TSG RAN #11 and placed under Change Control | 4.0.0 |
+| 11 | RP-010156 | 272,
273,
274 | | Approved at TSG RAN #11 and placed under Change Control | 4.0.0 |
+| 11 | RP-010155 | 252 | | Approved at TSG RAN #11 and placed under Change Control | 4.0.0 |
+| 11 | RP-010163 | 250 | | Approved at TSG RAN #11 and placed under Change Control | 4.0.0 |
+| 12 | RP-010454 | 277,
279,
281,
285,
287,
289,
291,
294,
296,
299 | | Approved at TSG RAN #12 | 4.1.0 |
+| 12 | RP-010375 | 301,
315,
317,
319, | | Approved at TSG RAN #12 | 4.1.0 |
+
+| | | | | | |
+|--|--|-----|--|--|--|
+| | | 323 | | | |
+|--|--|-----|--|--|--|
+
+| | | | | | |
+|----|-----------|-------------|---|------------------------------------------------------------------------------------------------------------------------|-------|
+| 12 | RP-010392 | 303,
320 | | Approved at TSG RAN #12 | 4.1.0 |
+| 13 | RP-010578 | 324 | 1 | Correction to the Error handling of the ERROR INDICATION message | 4.2.0 |
+| 13 | RP-010578 | 326 | 1 | Alignment of Conditional Presence with RAN3 Specification Principles | 4.2.0 |
+| 13 | RP-010578 | 328 | | NAS Synchronisation Indicator also at RAB Establishment | 4.2.0 |
+| 13 | RP-010578 | 329 | 2 | Old BSS to New BSS IE optional in UMTS to GSM handover | 4.2.0 |
+| 13 | RP-010578 | 330 | | Order of elements in bitstrings | 4.2.0 |
+| 13 | RP-010578 | 337 | | Data Forwarding related IEs in RELOCATION COMMAND message | 4.2.0 |
+| 13 | RP-010578 | 339 | 1 | Error handling of the Erroneously Present Conditional IEs | 4.2.0 |
+| 13 | RP-010578 | 345 | 1 | Rapporteurs corrections in RANAP | 4.2.0 |
+| 13 | RP-010578 | 347 | 3 | Inconsistency in definition of parameters used in INVOKE_TRACE message | 4.2.0 |
+| 13 | RP-010579 | 359 | 1 | Clarification of chapter 10 | 4.2.0 |
+| 13 | RP-010579 | 364 | 1 | Condition of SDU format information IE | 4.2.0 |
+| 13 | RP-010579 | 368 | 1 | Relocation Requirement not to be used | 4.2.0 |
+| 13 | RP-010594 | 297 | 2 | Clarification on User Plane Version Indication | 4.2.0 |
+| 13 | RP-010594 | 302 | 7 | Release 4 additions in Iu to support new positioning methods | 4.2.0 |
+| 13 | RP-010698 | 244 | 7 | N-to-M relation between CN and UTRAN | 4.2.0 |
+| 14 | RP-010895 | 361 | 3 | CR on Priority range | 4.3.0 |
+| 14 | RP-010848 | 365 | | Bitstrings ordering | 4.3.0 |
+| 14 | RP-010848 | 369 | 2 | UP Versions not supported | 4.3.0 |
+| 14 | RP-010848 | 371 | 1 | Location Report Area | 4.3.0 |
+| 14 | RP-010848 | 378 | 1 | Reason for LOCATION REPORT message is not clear | 4.3.0 |
+| 14 | RP-010848 | 380 | 1 | Corrections to RRC information containers | 4.3.0 |
+| 14 | RP-010848 | 383 | | Procedure Code Criticality in Error Indication | 4.3.0 |
+| 14 | RP-010848 | 386 | 2 | Addition of amendment to clarify the PER encoding of bitstrings | 4.3.0 |
+| 14 | RP-010848 | 388 | 2 | Chosen Integrity Protection Algorithm IE over MAP/E interface | 4.3.0 |
+| 14 | RP-010848 | 390 | | Rapporteurs corrections in RANAP (MCC/MNC) | 4.3.0 |
+| 14 | RP-010849 | 394 | 1 | Clarification on Location Request not fulfilled | 4.3.0 |
+| 14 | RP-010849 | 396 | 1 | Subflow SDU Size clarification | 4.3.0 |
+| 14 | RP-010849 | 400 | | Correction the Clause 10 Error Handling | 4.3.0 |
+| 14 | RP-010871 | 363 | 1 | Cause value for not accepted relocation request | 4.3.0 |
+| 14 | RP-010871 | 367 | 1 | Correction to Release 4 additions in Iu to support new positioning methods | 4.3.0 |
+| 14 | RP-010871 | 372 | | Chapter A.2.1 (EXAMPLE MESSAGE Layout) missing in version 4.2.0 | 4.3.0 |
+| 14 | RP-010871 | 373 | 1 | N-to-M relation between CN and UTRAN impacts on CN initiated Reset Resource procedure | 4.3.0 |
+| 14 | RP-010871 | 374 | | Stop Direct Report | 4.3.0 |
+| 14 | RP-010871 | 384 | 1 | MCC implementation CR for corrections to Release 4 additions in Iu to support new positioning methods. | 4.3.0 |
+| 14 | RP-010871 | 397 | 1 | Correction to LCS Vertical Accuracy | 4.3.0 |
+| 15 | RP-020164 | 402 | | Question regarding SRNS Context Transfer and SRNS Data Forwarding Initiation | 4.4.0 |
+| 15 | RP-020164 | 407 | | Intersystem Change and inter-system Handover corrections | 4.4.0 |
+| 15 | RP-020164 | 418 | | RAB Modification Parameters | 4.4.0 |
+| 15 | RP-020164 | 422 | 1 | Delivery of erroneous SDUs | 4.4.0 |
+| 15 | RP-020164 | 424 | 2 | Handling of Global RNC-ID in Reset and Reset resource | 4.4.0 |
+| 15 | RP-020164 | 426 | 2 | RABs concerned by contexts transfer | 4.4.0 |
+| 15 | RP-020164 | 432 | | Alignment of definition of Guaranteed Bitrate with 25.415 | 4.4.0 |
+| 15 | RP-020262 | 435 | 4 | Inclusion of "Age of Location IE into LOCATION REPORT" | 4.4.0 |
+| 15 | RP-020179 | 408 | | Requirements on user plane initialisation moved to 25.415 | 4.4.0 |
+| 15 | RP-020179 | 429 | 1 | Correction to LCS Vertical Accuracy Code IE | 4.4.0 |
+| 15 | RP-020189 | 419 | 3 | Introduction of IP Transport option in UTRAN | 5.0.0 |
+| 15 | RP-020257 | 431 | 1 | NNSF Functional Description | 5.0.0 |
+| 15 | RP-020188 | 409 | 2 | Transport Layer Address at RAB modification | 5.0.0 |
+| 15 | RP-020188 | 428 | 3 | Implementation of Handover/Relocation Solution for Inter-RAN Load Information Exchange between RAN and GERAN for Rel'5 | 5.0.0 |
+| 16 | RP-020423 | 404 | 6 | Release 5 additions of ROHC context relocation support during SRNS relocation | 5.1.0 |
+| 16 | RP-020401 | 437 | | Criticality Information Decoding Failure Handling | 5.1.0 |
+| 16 | RP-020401 | 440 | 2 | Erroneous Security Mode Control procedure | 5.1.0 |
+| 16 | RP-020401 | 443 | | Correction of Target RNC-ID | 5.1.0 |
+| 16 | RP-020401 | 444 | 1 | SDU Format Information Presence | 5.1.0 |
+| 16 | RP-020417 | 448 | | Extension container for Last Known Service Area IE | 5.1.0 |
+
+| | | | | | |
+|----|-----------|-----|---|-------------------------------------------------------------------------------------------------------------------------------------------------|-------|
+| 16 | RP-020401 | 451 | | "EXTENSION INDICATION" PROPOSAL | 5.1.0 |
+| 16 | RP-020417 | 453 | | Correction of wrong implementation for CR429 | 5.1.0 |
+| 16 | RP-020401 | 462 | 1 | RNL-TNL coordination in RANAP | 5.1.0 |
+| 16 | RP-020401 | 465 | 2 | Correction of RNC lu Coordinated relocation | 5.1.0 |
+| 16 | RP-020421 | 466 | 1 | IPv4-IPv6 interworking for data forwarding | 5.1.0 |
+| 16 | RP-020401 | 469 | 1 | Clarification for the usage of the cause value | 5.1.0 |
+| 16 | RP-020417 | 479 | 1 | Correction due to the wrong implementation of CR326&244 and error in the CR424 | 5.1.0 |
+| 17 | RP-020606 | 481 | | Erroneous criticality in DATA VOLUME REPORT REQUEST a.o. | 5.2.0 |
+| 17 | RP-020600 | 484 | 2 | Handling of security at relocation | 5.2.0 |
+| 17 | RP-020629 | 488 | 1 | CRRM Corrections | 5.2.0 |
+| 17 | RP-020600 | 495 | 1 | Codec change during SRNS relocation | 5.2.0 |
+| 17 | RP-020606 | 503 | 1 | New cause value for RAB release request | 5.2.0 |
+| 17 | RP-020625 | 504 | 2 | Shared Networks in connected mode – Information Transfer | 5.2.0 |
+| 17 | RP-020624 | 506 | 2 | GERAN specific impacts on the lu-cs interface | 5.2.0 |
+| 17 | RP-020600 | 509 | 1 | Correction to RANAP cause value range | 5.2.0 |
+| 17 | RP-020606 | 513 | | LCS alignment with stage 2 | 5.2.0 |
+| 17 | RP-020643 | 515 | | Signalling enhancements for GERAN lu Mode LCS | 5.2.0 |
+| 18 | RP-020517 | 517 | | Correction to RANAP RESET procedure | 5.3.0 |
+| 18 | RP-020522 | 522 | 1 | Rel4 Common CR after RANAP review | 5.3.0 |
+| 18 | RP-020526 | 526 | 4 | Correction to enable Rel4 extensions in Location Reporting Control procedure. | 5.3.0 |
+| 18 | RP-020529 | 529 | 2 | Correction of RAB Subflows and SRBs mapping onto the transport channel identifiers of lur in the Source RNC to Target RNC transparent container | 5.3.0 |
+| 18 | RP-020532 | 532 | 1 | Correction of coding of GSM IEs | 5.3.0 |
+| 18 | RP-020533 | 533 | 1 | New cause codes for Network sharing in connected mode | 5.3.0 |
+| 18 | RP-020535 | 535 | 1 | Encoding of information elements. | 5.3.0 |
+| 19 | RP-030060 | 546 | 1 | Addition of RAB Subflows mapping onto the transport channel identifiers of lur in the Source RNC to Target RNC transparent container for HSDPA | 5.4.0 |
+| 19 | RP-030067 | 550 | | Alignment of "Uncertainty Ellipse" with RRC | 5.4.0 |
+| 19 | RP-030056 | 552 | 1 | Duplicated lu connection identifiers | 5.4.0 |
+| 19 | RP-030060 | 557 | 1 | Inclusion of IMS Signalling Indication into R5 RANAP | 5.4.0 |
+| 19 | RP-030060 | 558 | | Correction to RANAP due to GERAN lu mode | 5.4.0 |
+| 19 | RP-030056 | 562 | | Essential correction of IMSI coding | 5.4.0 |
+| 20 | RP-030314 | 570 | 2 | Essential Correction of lu Release Issue | 5.5.0 |
+| 20 | RP-030326 | 572 | 1 | Correction of Failure message used for logical errors | 5.5.0 |
+| 20 | RP-030339 | 573 | 2 | Introduction of Early UE Handling – Bitmap Option | 5.5.0 |
+| 20 | RP-030316 | 576 | 2 | lu UP Initialisation during RAB modification | 5.5.0 |
+| 21 | RP-030445 | 578 | | Alignment of title and sub-clause text of chapter 10.3.4.2 | 5.6.0 |
+| 21 | RP-030437 | 584 | 1 | Essential Correction of lu Release Request | 5.6.0 |
+| 21 | RP-030439 | 586 | 2 | Introduction of positioning methods over lu | 5.6.0 |
+| 21 | RP-030439 | 590 | 1 | Alignment of RANAP and RNSAP CRRM solutions | 5.6.0 |
+| 21 | RP-030439 | 594 | | RNC use of IMSI within Relocation Resource Allocation | 5.6.0 |
+| 21 | RP-030446 | 595 | | Removal of the note in chapter 10 | 5.6.0 |
+| 22 | RP-030671 | 597 | - | Backwards Compatibility for LCS- Limited Solution | 5.7.0 |
+| 22 | RP-030676 | 601 | 2 | Serious Correction for Rescue handover | 5.7.0 |
+| 22 | RP-030676 | 604 | - | Serious Correction for Security in Multi-domain calls | 5.7.0 |
+| 22 | RP-030715 | 606 | 2 | Correction of RAB Release Request Inter-working | 5.7.0 |
+| 22 | RP-030676 | 607 | 3 | RANAP Review issue 2: Correction of Position Data | 5.7.0 |
+| 22 | RP-030676 | 608 | - | RANAP Review issue 3: LCS Accuracy | 5.7.0 |
+| 22 | RP-030671 | 613 | 1 | Add IE "Criticality Diagnostics" for LOCATION RELATED DATA FAILURE message | 5.7.0 |
+| 22 | RP-030686 | 614 | 1 | RT Load Value Clarification | 5.7.0 |
+| 22 | RP-030671 | 618 | 1 | Correction of Reference section | 5.7.0 |
+| 22 | RP-030676 | 620 | 1 | Corrections to the data volume reporting function | 5.7.0 |
+| 22 | RP-030676 | 622 | 2 | Big clarification CR based on RANAP Rel-5 review | 5.7.0 |
+| 22 | RP-030676 | 623 | 2 | Correction to CRRM lu solution | 5.7.0 |
+| 22 | - | - | - | Introduction of Release 6 specification | 6.0.0 |
+| 23 | RP-040053 | 641 | | Alignment with 23.032 correction of Included Angle for Ellipsoid Arc | 6.1.0 |
+| 23 | RP-040062 | 634 | | Correction of GERAN related Release 5 IEs | 6.1.0 |
+| 23 | RP-040062 | 636 | 1 | Causes used in RANAP | 6.1.0 |
+| 23 | RP-040062 | 638 | | Inaccuracies in the specification of the Overload procedure | 6.1.0 |
+| 23 | RP-040062 | 643 | 1 | Clarification on lu reset procedure | 6.1.0 |
+
+| | | | | | |
+|---------|-----------|------|----|----------------------------------------------------------------------------------------------------|-------|
+| 23 | RP-040062 | 652 | | Integrity Status Correction | 6.1.0 |
+| 23 | RP-040062 | 654 | | Coding of Discontinuous Transmission/No_Data mode | 6.1.0 |
+| 24 | RP-040216 | 658 | | Introduction of an indication of achieved accuracy in Location Report procedure over Iu interface. | 6.2.0 |
+| 24 | RP-040174 | 662 | 3 | Data Volume Reporting Correction | 6.2.0 |
+| 24 | RP-040174 | 667 | 1 | SNA Coding correction | 6.2.0 |
+| 24 | RP-040182 | 668 | 2 | Introduction of RIM mechanisms for NACC over the Iu interface | 6.2.0 |
+| 24 | RP-040174 | 672 | | Correction of Transport Layer Address and Iu Transport Association handling in RAB Assignment | 6.2.0 |
+| 24 | RP-040183 | 673 | 1 | Management Based Activation in the UTRAN over the Iu | 6.2.0 |
+| 24 | RP-040183 | 674 | 1 | Enhancement of Trace handling during Relocation | 6.2.0 |
+| 24 | RP-040183 | 675 | 1 | Modification of CN Invoke Trace for Subscriber and Equipment Trace support over Iu | 6.2.0 |
+| 25 | RP-040298 | 681 | 4 | Addition of Relocation Failure cause code to match GERAN cause code | 6.3.0 |
+| 25 | RP-040299 | 692 | 3 | Data Volume Reporting Correction | 6.3.0 |
+| 25 | RP-040299 | 696 | 2 | Service Handover Timing and Priority | 6.3.0 |
+| 25 | RP-040299 | 700 | 1 | presence of ciphering key in the RANAP container | 6.3.0 |
+| 26 | RP-040439 | 701 | | Indication of selected PLMN in shared networks | 6.4.0 |
+| 26 | RP-040439 | 702 | 1 | Rerouting in MOCN | 6.4.0 |
+| 26 | RP-040437 | 706 | 2 | MBMS stage 3 support over Iu | 6.4.0 |
+| 26 | RP-040439 | 715 | 2 | Support of full Mobility/Backwards Compatibility in Network Sharing | 6.4.0 |
+| 26 | RP-040441 | 719 | | Correction of reference to outdated ITU-T recommendations | 6.4.0 |
+| | | | | space removed in ASN.1 from "MBMSSessionStartResponse" | 6.4.1 |
+| 27 | RP-050057 | 721 | 3 | MBMS Session Repetition Number on Session Start | 6.5.0 |
+| 27 | RP-050057 | 724 | 3 | MBMS RAB Management | 6.5.0 |
+| 27 | RP-050052 | 730 | 2 | Essential Correction on Direct Transfer Messages | 6.5.0 |
+| 27 | RP-050057 | 734 | | MBMS Contexts | 6.5.0 |
+| 27 | RP-050057 | 737 | 3 | MBMS IE codings | 6.5.0 |
+| 27 | RP-050057 | 738 | | MBMS Session Failure | 6.5.0 |
+| 27 | RP-050059 | 739 | 2 | Support of Network-initiated Scudif (revision of R3-041734) | 6.5.0 |
+| 27 | RP-050052 | 740 | 1 | Correction of RANAP Containers and CRRM | 6.5.0 |
+| 28 | RP-050227 | 741 | | MBMS Session Duration IE | 6.6.0 |
+| 28 | RP-050229 | 742 | 1 | Addition of E-DCH MAC-d Flow ID in transparent Container | 6.6.0 |
+| 28 | RP-050233 | 743 | 1 | Correction to the RANAP in Iu-Flex Paging without IMSI. | 6.6.0 |
+| 28 | RP-050227 | 745 | 2 | Enhancement for MBMS SESSION START message | 6.6.0 |
+| 28 | RP-050233 | 747 | 1 | Presence information for RAC in Target ID towards PS domain | 6.6.0 |
+| 28 | RP-050217 | 749 | | Correction of CR729 | 6.6.0 |
+| 28 | RP-050227 | 750 | 1 | Correction of MBMS figure title | 6.6.0 |
+| 28 | RP-050236 | 752 | | Release after rerouting attempt | 6.6.0 |
+| 28 | RP-050236 | 753 | | No Relocation during MOCN Rerouting | 6.6.0 |
+| 28 | RP-050217 | 763 | | Correction of Cell Load Information Group | 6.6.0 |
+| 28 | RP-050233 | 768 | | Correction of queuing at relocation | 6.6.0 |
+| 29 | RP-050443 | 773 | | MBMS applies for the PS domain | 6.7.0 |
+| 29 | RP-050473 | 782 | | Inclusion of Inter-RAT PS Handover between UTRAN and GERAN A/Gb | 6.7.0 |
+| 29 | RP-050444 | 784 | 1 | Clarification of the Relocation Cancel and Relocation Preparation | 6.7.0 |
+| 30 | RP-050692 | 791 | 1 | Introduction of the Time to MBMS Data Transfer | 6.8.0 |
+| 30 | RP-050693 | 796 | | Correction of SCUDIF Relocation | 6.8.0 |
+| 30 | RP-050693 | 797 | 1 | Error Handling of unused IEs | 6.8.0 |
+| 30 | RP-050693 | 801 | 1 | Rewording of interaction text from CR784 | 6.8.0 |
+| 30 | RP-050693 | 803 | 1 | Rapporteur's Review of 25.413 | 6.8.0 |
+| 30 | RP-050692 | 804 | 1 | MBMS Service Area List IE Encoding Correction | 6.8.0 |
+| 03/2006 | - | - | | Release 7 version created based on v6.8.0 | 7.0.0 |
+| 31 | RP-060072 | 0770 | 10 | Enabling the Providing of Velocity | 7.1.0 |
+| 31 | RP-060061 | 0806 | | Correction of IE name in procedure text for MBMS Session Update | 7.1.0 |
+| 31 | RP-060061 | 0810 | 2 | Correction of signaling bearer mode for MBMS Registration Failure | 7.1.0 |
+| 31 | RP-060061 | 0825 | 2 | PS/CS coordination in shared RAN for MOCN | 7.1.0 |
+| 31 | RP-060061 | 0827 | 2 | Inclusion of redirect attempt flag in Initial UE Message | 7.1.0 |
+| 31 | RP-060061 | 0829 | | SRB mapping toward HS-DSCH and E-DCH MAC-d flows | 7.1.0 |
+| 31 | RP-060062 | 0831 | 1 | Iu Release when detecting double Iu | 7.1.0 |
+| 32 | RP-060288 | 0834 | 4 | Correction of performance measurement point IRATHO.SuccOutPSUE | 7.2.0 |
+| 32 | RP-060289 | 0835 | 1 | Clarification on setting the Accuracy Fulfilment Indicator IE by the RNC | 7.2.0 |
+| 32 | RP-060278 | 0843 | 3 | SI/PSI information transfer for PS handover | 7.2.0 |
+| 32 | RP-060386 | 0844 | 2 | Correction of positioning confidence reporting inconsistencies | 7.2.0 |
+| 32 | RP-060278 | 0849 | | Unclear presence of Selected PLMN identity IE in case of network | 7.2.0 |
+
+| | | | | | |
+|--|--|--|--|----------------------------|--|
+| | | | | sharing non supporting UEs | |
+|--|--|--|--|----------------------------|--|
+
+| | | | | | |
+|---------|-----------|------|---|-----------------------------------------------------------------------------------------------------------|-------|
+| 32 | RP-060278 | 0851 | 1 | Handling of preserved nrt RABs | 7.2.0 |
+| 32 | RP-060278 | 0853 | 1 | Target RNC ID in RIM Routing Information towards an RNC | 7.2.0 |
+| 33 | RP-060499 | 0856 | 1 | Criticality Diagnostics IE for MBMS RAB Release | 7.3.0 |
+| 33 | RP-060514 | 0857 | 2 | Status of Service Handover IE | 7.3.0 |
+| 33 | RP-060514 | 0858 | | Alignment of PLMN identity | 7.3.0 |
+| 33 | RP-060499 | 0860 | | Correction of the Meaning of cause value | 7.3.0 |
+| 33 | RP-060510 | 0861 | 1 | Addition of Periodic Location Procedures | 7.3.0 |
+| 33 | RP-060579 | 0871 | 2 | Inclusion of the MBMS Counting Information IE to the MBMS Session Start Request | 7.3.0 |
+| 33 | RP-060590 | 0873 | | Removal of MBMS SAI Semantic Description in RANAP | 7.3.0 |
+| 34 | RP-060724 | 0854 | 2 | Introduction of inter-RAT DTM Handover | 7.4.0 |
+| 34 | RP-060713 | 0865 | 4 | Introduction of new ciphering algorithm UEA2 and integrity protection algorithm UIA2 | 7.4.0 |
+| 34 | RP-060698 | 0879 | 2 | Conditions for MBMS RAB set up | 7.4.0 |
+| 34 | RP-060706 | 0883 | 5 | Introducing Direct Tunnel in RANAP | 7.4.0 |
+| 34 | RP-060698 | 0885 | 3 | RNC Rejection of MBMS Session Setup with a TMGI already used for another ongoing MBMS session | 7.4.0 |
+| 34 | RP-060698 | 0889 | 1 | MBMS session Repetition Number Corrections | 7.4.0 |
+| 35 | RP-070063 | 0891 | 2 | Direct Tunnel Correction | 7.5.0 |
+| 35 | RP-070063 | 0895 | 2 | Signalling RABs | 7.5.0 |
+| 35 | RP-070063 | 0898 | 1 | Mandatory use of transport layer information | 7.5.0 |
+| 35 | RP-070063 | 0900 | | Modification of Rules for Building RANAP Messages | 7.5.0 |
+| 35 | RP-070054 | 0902 | 2 | Correction on MBMS SESSION START and MBMS SESSION UPDATE | 7.5.0 |
+| 35 | RP-070061 | 0906 | 3 | Introduction of MIMO in RANAP | 7.5.0 |
+| 35 | RP-070056 | 0908 | 2 | MBMS Session setup of a parallel session of the same service in a distinct MBMS service area | 7.5.0 |
+| 35 | RP-070054 | 0910 | | Update of MBMS Session Duration | 7.5.0 |
+| 36 | RP-070474 | 0905 | 5 | Introduction of Extended RNC-ID | 7.6.0 |
+| 36 | RP-070322 | 0914 | 3 | Clarification on distinguishing MBMS Service Areas of Multiple parallel MBMS Sessions of the same service | 7.6.0 |
+| 36 | RP-070339 | 0924 | 2 | Frequency Layer Convergence | 7.6.0 |
+| 36 | RP-070337 | 0925 | 2 | Introduction of GANSS (Galileo and Additional Navigation Systems) in RANAP | 7.6.0 |
+| 37 | RP-070567 | 0928 | 1 | Correction to GANSS Location Related Data Request | 7.7.0 |
+| 37 | RP-070565 | 0930 | | MBMS broadcast RAB Set Up | 7.7.0 |
+| 37 | RP-070578 | 0932 | | Correction for RNC ID | 7.7.0 |
+| 37 | RP-070578 | 0934 | 1 | Maximum number of lu Signalling Connection Identifiers | 7.7.0 |
+| 37 | RP-070581 | 0935 | | UE Involved Relocation for source RNC not having lu-cs UP | 7.7.0 |
+| 38 | RP-070838 | 0939 | 1 | ASN1-Tabular alignment for GANSS feature in TS25.413 | 7.8.0 |
+| 38 | RP-070837 | 0941 | | Explicit references to TRs 25.994 and 25.995 | 7.8.0 |
+| 38 | RP-070842 | 0942 | | Rapporteurs Review | 7.8.0 |
+| 38 | RP-070844 | 0943 | 2 | Introduction of cause value for CS-triggered relocation | 7.8.0 |
+| 40 | RP-080297 | 0950 | | Correction of the Release of MBMS Signalling Connection | 7.9.0 |
+| 09/2008 | - | - | | Rel-8 version created based on v7.9.0 | 8.0.0 |
+| 41 | RP-080589 | 0952 | 2 | Introduction of Enhanced Relocation | 8.0.0 |
+| 41 | - | - | | ASN.1 error corrected | 8.0.1 |
+| 42 | RP-080852 | 0953 | | Support for additional navigation satellite systems in RANAP | 8.1.0 |
+| 42 | RP-080849 | 0959 | 3 | Introduction of UE History Information | 8.1.0 |
+| 42 | RP-080849 | 0960 | 1 | Introduction of MBMS Improved Solution | 8.1.0 |
+| 42 | RP-080848 | 0961 | 3 | Inter-RAT Mobility to/from E-UTRAN | 8.1.0 |
+| 42 | RP-080855 | 0962 | | Introduction of the Subscriber Profile ID for RAT/Frequency priority | 8.1.0 |
+| 42 | RP-080840 | 0963 | | ASN.1 changes for enhanced relocation | 8.1.0 |
+| 42 | RP-080854 | 0965 | 2 | RANAP changes to support the use of CSG Identifiers | 8.1.0 |
+| 42 | RP-080856 | 0966 | | Removal of Recovery and Restoration from 23.060 | 8.1.0 |
+| 43 | RP-090083 | 0971 | | Cause value mapping for CSFB | 8.2.0 |
+| 43 | RP-090079 | 0974 | 2 | Clarification of usage of MBMS RAB release for MBMS broadcast | 8.2.0 |
+| 43 | RP-090075 | 0977 | 2 | Clarification of usage of Extended MBR and GBR | 8.2.0 |
+| 43 | RP-090076 | 0978 | | Clarification on Source ID | 8.2.0 |
+| 43 | RP-090078 | 0979 | 1 | Editorial Updates TS 25.413 | 8.2.0 |
+| 43 | RP-090245 | 0980 | | Transparent Container content – informative annex | 8.2.0 |
+| 43 | RP-090093 | 0981 | | Introduction of HSPA SRVCC | 8.2.0 |
+| 43 | RP-090079 | 0982 | 2 | Further Corrections for Enhanced Relocation | 8.2.0 |
+| 43 | RP-090081 | 0983 | | Inclusion of CSG ID in initial UE message | 8.2.0 |
+| 43 | RP-090078 | 0984 | | Clarification on ASN.1 for Generic Container | 8.2.0 |
+
+| | | | | | |
+|------------|-----------|------|---|---------------------------------------------------------------------------------------------------------------------|--------|
+| 43 | RP-090263 | 0985 | | Rename of Source RNC ID in ENHANCD RELOCATION COMPLETE REQUEST | 8.3.0 |
+| March 2009 | - | - | - | ASN.1 debugging before freezing | 8.3.1 |
+| 44 | RP-090638 | 0988 | | Addition of Integrity Protection Information IE and Encryption Information IE into Enhanced SRNS Relocation | 8.3.0 |
+| 44 | RP-090641 | 0989 | 4 | RANAP changes to support paging optimisation | 8.3.0 |
+| 44 | RP-090633 | 0994 | | Correction of extended alternative bit rate | 8.3.0 |
+| 44 | RP-090633 | 0996 | | Structure of procedure text for Relocation Preparation | 8.3.0 |
+| 44 | RP-090635 | 0998 | 1 | Interaction between Enhanced Relocation and RAB Assignment Procedure | 8.3.0 |
+| 44 | RP-090642 | 0999 | 1 | Correction of introduction of HSPA SRVCC | 8.3.0 |
+| 44 | RP-090642 | 1000 | | Correction of the Global CN-ID for the PS domain | 8.3.0 |
+| 44 | RP-090636 | 1002 | | Introduction of E-UTRAN Service Handover IE | 8.3.0 |
+| 45 | RP-090770 | 1015 | | Correction of ASN.1 Target Cell ID missing | 8.4.0 |
+| 09/2009 | - | - | | Rel-9 version created based on v8.4.0 | 9.0.0 |
+| 45 | RP-090777 | 1009 | 2 | Introduction of UE-AMBR Concept in UMTS | 9.0.0 |
+| 46 | RP-091191 | 1008 | 4 | Support for paging optimization with CSG membership changes | 9.1.0 |
+| 46 | RP-091191 | 1018 | 1 | Target Cell ID for HNB in-bound HO | 9.1.0 |
+| 46 | RP-091191 | 1037 | 1 | Inclusion of CSG information for access control in 3G handover procedures and UE prioritization in 3G hybrid cells. | 9.1.0 |
+| 47 | RP-100219 | 1038 | - | Correction of CSG Cell and Hybrid Cell Definition | 9.2.0 |
+| 47 | RP-100222 | 1039 | 1 | Clarification on the Access Control of Non-CSG UE During Inbound Handover | 9.2.0 |
+| 47 | RP-100222 | 1041 | 1 | Handling of CSG ID check failure in hybrid cells | 9.2.0 |
+| 47 | RP-100215 | 1043 | - | Correct name of Target eNB ID to align with 36.413 | 9.2.0 |
+| 47 | RP-100228 | 1044 | - | Inter RAT Mobility Load Balancing on Iu | 9.2.0 |
+| 47 | RP-100222 | 1047 | - | Correct wrong CSG ID reference | 9.2.0 |
+| 47 | RP-100229 | 1048 | 1 | Description of Transparent Container Encoding | 9.2.0 |
+| 47 | RP-100229 | 1049 | - | Rapporteur's update for RANAP protocol | 9.2.0 |
+| 47 | RP-100219 | 1051 | 2 | Addition of IP Source Address in MBMS Synchronisation Information in MBMS Session Start | 9.2.0 |
+| 47 | RP-100348 | 1053 | 4 | CSG expiry Handling | 9.2.0 |
+| 47 | RP-100214 | 1056 | 1 | Correction of CSFB | 9.2.0 |
+| 48 | RP-100592 | 1058 | 1 | UTRAN Trace ID Abnormal Conditions | 9.3.0 |
+| 48 | RP-100595 | 1059 | - | Some Corrections to the Inbound Mobility Procedure | 9.3.0 |
+| 48 | RP-100599 | 1061 | 4 | Introduction of IPv4 and IPv6 Dual Stack option | 9.3.0 |
+| 48 | RP-100595 | 1063 | 1 | Correct the description on the Relocation Failure handling | 9.3.0 |
+| 48 | RP-100599 | 1064 | 3 | Release 7 QoS subscription data for Pre-Release 7 UE | 9.3.0 |
+| 48 | RP-100599 | 1067 | 1 | Enhancement of Location Reporting functionality interaction with Enhanced Relocation | 9.3.0 |
+| 49 | RP-100907 | 1074 | - | Correction of Forwarding TNL IE for Enhanced Relocation | 9.4.0 |
+| 49 | RP-100907 | 1075 | - | Correction of the interaction between CN Invoke Trace and Enhanced Relocation | 9.4.0 |
+| 49 | RP-100907 | 1076 | - | Correction of inconsistencies between tabular, procedural text and ASN.1 code for Enhanced Relocation | 9.4.0 |
+| 50 | RP-101269 | 1081 | | Correction of Inter-system SRVCC | 9.5.0 |
+| 12/2010 | | | | Rel-10 version created based on v9.5.0 | 10.0.0 |
+| 50 | RP-101389 | 1084 | | Introduction of the SIPTO at Iu-PS Function | 10.0.0 |
+| 50 | RP-101389 | 1086 | 2 | LIPA Impact In RAN3 | 10.0.0 |
+| 50 | RP-101304 | 1087 | 2 | Inter-RAT MRO for Detection of too early inter-RAT handover with no RLF | 10.0.0 |
+| 01/2011 | | | | Editorial change: highlighting removed | 10.0.1 |
+| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.0 |
+| 51 | RP-110226 | 1090 | | Correction to Integrity Protection Information and Encryption Information | 10.1.0 |
+| 51 | RP-110239 | 1091 | 1 | Addition of MeasurementBandwidth and ASN.1 clean-up for IRAT measurement configuration | 10.1.0 |
+| 51 | RP-110230 | 1094 | 1 | Introduction of MDT | 10.1.0 |
+| 51 | RP-110231 | 1095 | 1 | Additional IEs needed to support optimized HNB-HNB mobility | 10.1.0 |
+| 51 | RP-110233 | 1096 | 3 | Introduction of Low Priority Traffic Overload support | 10.1.0 |
+| 51 | RP-110226 | 1099 | 2 | Clarification on TEID value range for RANAP | 10.1.0 |
+| 51 | RP-110225 | 1100 | 1 | the description usage of NONCE in RNC | 10.1.0 |
+| 52 | RP-110695 | 1104 | 3 | User consent indication for MDT in RANAP | 10.2.0 |
+| 52 | RP-110713 | 1111 | 1 | Clarification to detection of unnecessary IRAT handover | 10.2.0 |
+| 52 | RP-110681 | 1114 | 2 | Correction of SRVCC from LTE to UMTS | 10.2.0 |
+
+| | | | | | |
+|----|-----------|------|---|--------------------------------------------------------------------------------------------------------------------------|--------|
+| 52 | RP-110684 | 1115 | - | Correction of References | 10.2.0 |
+| 52 | RP-110686 | 1116 | 2 | General clean-up before Rel-10 ASN.1 closure | 10.2.0 |
+| 52 | RP-110695 | 1118 | 2 | MDT UTRAN amendments | 10.2.0 |
+| 53 | RP-111197 | 1120 | 1 | Addition of SRVCC preparation into message type tabular | 10.3.0 |
+| 53 | RP-111195 | 1122 | - | Correct definition of condition IfM2 in MDT Configuration | 10.3.0 |
+| 53 | RP-111195 | 1123 | 3 | Clarification on MDT Recording Session Reference in MDT Configuration | 10.3.0 |
+| 53 | RP-111195 | 1124 | 2 | Area scope RAI list in MDT configuration | 10.3.0 |
+| 53 | RP-111195 | 1130 | 2 | Definition of value of bit in Measurements to Activate | 10.3.0 |
+| 53 | RP-111193 | 1132 | 2 | Correction of Rel-7 QoS handling for Pre-Rel-7 UEs | 10.3.0 |
+| 53 | RP-111196 | 1133 | - | Correction of some generic references to dated references | 10.3.0 |
+| 53 | RP-111195 | 1134 | 1 | Small correction on unnecessary IRAT HO | 10.3.0 |
+| 53 | RP-111198 | 1139 | - | Alignment of the transparent containers' IE names with CT4 specifications | 10.3.0 |
+| 54 | RP-111651 | 1140 | - | Introduction of the annex on the processing of transparent containers at SGSN | 10.4.0 |
+| 54 | RP-111649 | 1141 | 2 | Addition of TCE IP in CN INVOKE TRACE | 10.4.0 |
+| 54 | RP-111646 | 1143 | - | Correction of Emergency Call | 10.4.0 |
+| 54 | RP-111651 | 1148 | 1 | Fast Return after CSFB | 10.4.0 |
+| 54 | RP-111651 | 1149 | 1 | Correction of Routing | 10.4.0 |
+| 55 | RP-120232 | 1153 | 1 | Correction on unnecessary HO | 10.5.0 |
+| 56 | RP-120743 | 1166 | 1 | Correction to assigned criticality of L-GW Transport Layer Address | 10.6.0 |
+| 56 | RP-120752 | 1167 | 1 | Introduction of the new IE for cell reselection from UTRA connected mode | 11.0.0 |
+| 56 | RP-120752 | 1172 | 1 | Improved granularity for the time UE stayed in cell | 11.0.0 |
+| 57 | RP-121130 | 1177 | 2 | Correction on handover to a CSG cell with an emergency call | 11.1.0 |
+| 57 | RP-121135 | 1190 | 2 | Addition of HO cause value to the UE history information in RANAP | 11.1.0 |
+| 57 | RP-121140 | 1194 | 3 | Introduction of UE Radio Capability Match procedure | 11.1.0 |
+| 57 | RP-121140 | 1195 | 1 | Introduction of Anonymization of MDT data for area based MDT in UTRAN | 11.1.0 |
+| 58 | RP-121736 | 1196 | - | ASN.1 correction | 11.2.0 |
+| 58 | RP-121736 | 1197 | - | Improved granularity for the time UE stayed in cell for enhanced relocation | 11.2.0 |
+| 58 | RP-121728 | 1198 | - | Introduction of rSRVCC | 11.2.0 |
+| 58 | RP-121728 | 1202 | 2 | Introduction of the support for rSRVCC network sharing | 11.2.0 |
+| 58 | RP-121737 | 1203 | - | Rapporteur editorial corrections | 11.2.0 |
+| 58 | RP-121730 | 1204 | 2 | Multi-PLMN MDT | 11.2.0 |
+| 58 | RP-121732 | 1208 | 1 | Introduction of connectivity between HNB and RNC via HNB-GW for RNSAP signaling: Enhanced Relocation between HNB and RNC | 11.2.0 |
+| 58 | RP-121730 | 1209 | 2 | Introduction of new MDT measurements | 11.2.0 |
+| 58 | RP-121739 | 1211 | 2 | New Information for BBF access | 11.2.0 |
+| 58 | RP-121736 | 1214 | 2 | Clarification of E-UTRAN Service Handover IE for inter-RAT roaming restrictions | 11.2.0 |
+| 59 | RP-130207 | 1217 | - | Addition of missing values for MDT report interval | 11.3.0 |
+| 59 | RP-130224 | 1219 | - | Introduction of the missing ASN.1 definition for Timing Difference UL-DL IE | 11.3.0 |
+| 59 | RP-130212 | 1220 | 3 | ASN.1 review for RANAP | 11.3.0 |
+| 59 | RP-130206 | 1222 | 1 | Correction of rSRVCC capability indicator | 11.3.0 |
+| 59 | RP-130211 | 1223 | 2 | Addition of TCE IP and Cell Identifier for Anonymization MDT | 11.3.0 |
+| 59 | RP-130237 | 1224 | 1 | Extending maxEARFCN | 11.3.0 |
+| 60 | RP-130638 | 1225 | - | Clarification on Positioning Data Discriminator IE | 11.4.0 |
+| 60 | RP-130643 | 1226 | - | Correction of BBAI information | 11.4.0 |
+| 60 | RP-130637 | 1227 | 1 | Provide IMEISV to RNC to identify UE characteristics | 11.4.0 |
+| 60 | RP-130643 | 1228 | 2 | Resolution of ambiguity around reject causes in MOCN | 11.4.0 |
+| 60 | RP-130643 | 1234 | 2 | Redirect indication for NAS rejection cause #17 and #25 | 11.4.0 |
+| 60 | RP-130643 | 1235 | 2 | Clarification on CS/PS coordination | 11.4.0 |
+| 60 | RP-130639 | 1238 | 1 | Correction of SRVCC procedure in case of PS handover failure | 11.4.0 |
+| 62 | RP-131902 | 1251 | 2 | Correction on relocation with an emergency call | 11.5.0 |
+| 63 | RP-140294 | 1261 | 1 | Introduction of Last E-UTRAN PLMN Identity for CSFB | 11.6.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25414/220869911a1ecfa1dd4aa6d750319aad_img.jpg b/marked/Rel-11/25_series/25414/220869911a1ecfa1dd4aa6d750319aad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93932f188ce7e4b74ddc603e6a5a6a05a24566e9
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/220869911a1ecfa1dd4aa6d750319aad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a60495cb9d117f412983ed796e270b935dad1440e3eaca85f2be5eb27697b35
+size 40648
diff --git a/marked/Rel-11/25_series/25414/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-11/25_series/25414/43837b056625d3d6ce615e4c02f163bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a171d632fab331847d432deaf301fa723d6f5a4a
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/43837b056625d3d6ce615e4c02f163bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35580dcc3531f67d9e1caa872b80d48d45857f258f64fc41116dfd2fd542160b
+size 13465
diff --git a/marked/Rel-11/25_series/25414/536951b2bbd94325ae266d8d1363df8f_img.jpg b/marked/Rel-11/25_series/25414/536951b2bbd94325ae266d8d1363df8f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3dda2ab1f5c542379a79466abad0c75feb0cb2cf
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/536951b2bbd94325ae266d8d1363df8f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c476c928dc53a265f32645152fffdde69e378c2261077365c971894304506c7
+size 27046
diff --git a/marked/Rel-11/25_series/25414/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Rel-11/25_series/25414/5e92d9e8e9ce204e405bff2367f88176_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a01b1da3cd9adbc8007142a91c58349ba6508e1
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/5e92d9e8e9ce204e405bff2367f88176_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bbfedaa235b519e608fd665d6cbed757a81cd26791b76cb6ca7a1c4fe0addcb
+size 13458
diff --git a/marked/Rel-11/25_series/25414/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/25_series/25414/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42db586948dc292a248f5331a66013ec2c29b0e2
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b994987f62f56caf282ad8a5049088fcbfaa2b810e49d7b936bab7e282453cc2
+size 46576
diff --git a/marked/Rel-11/25_series/25414/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-11/25_series/25414/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..377527cc25a7a1b59dffc5fced76f4174d2790f3
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3500167ed4ee9aada56727e520195dff5dab49c29c2bab3d28583830aeae2c02
+size 44088
diff --git a/marked/Rel-11/25_series/25414/raw.md b/marked/Rel-11/25_series/25414/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a6f0e48703ff10a3a67052e0c080c585043ae524
--- /dev/null
+++ b/marked/Rel-11/25_series/25414/raw.md
@@ -0,0 +1,704 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|-------------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Data Link Layer ..... | 8 |
+| 4.1 ATM Transport Option ..... | 8 |
+| 4.2 IP Transport Option..... | 8 |
+| 5 Circuit switched domain ..... | 9 |
+| 5.1 Transport network user plane..... | 9 |
+| 5.1.1 General ..... | 9 |
+| 5.1.2 ATM Transport Option..... | 9 |
+| 5.1.2.1 ATM Adaptation Layer 2 ..... | 9 |
+| 5.1.2.1.1 AAL2-Segmentation and Reassembly Service Specific Convergence Sublayer (I.366.1)..... | 9 |
+| 5.1.2.1.2 AAL2-specification (I.363.2)..... | 9 |
+| 5.1.3 IP Transport Option..... | 9 |
+| 5.1.3.1 General..... | 9 |
+| 5.1.3.2 UDP/IP..... | 10 |
+| 5.1.3.3 RTP..... | 10 |
+| 5.1.3.3.1 RTP Header..... | 10 |
+| 5.1.3.3.1.4 Contributing Source (CSRC) count..... | 10 |
+| 5.1.3.3.1.5 Marker Bit ..... | 10 |
+| 5.1.3.3.1.6 Payload Type..... | 10 |
+| 5.1.3.3.1.7 Sequence Number..... | 11 |
+| 5.1.3.3.1.8 Timestamp..... | 11 |
+| 5.1.3.3.1.9 Synchronisation Source (SSRC)..... | 11 |
+| 5.1.3.3.1.10 CSRC list..... | 11 |
+| 5.1.3.3.2 RTP Payload..... | 11 |
+| 5.1.3.4 RTCP ..... | 11 |
+| 5.1.3.5 Diffserv code point marking..... | 11 |
+| 5.2 Transport network control plane ..... | 11 |
+| 5.2.1 General ..... | 11 |
+| 5.2.2 Transport Signalling for the ATM Transport Option..... | 12 |
+| 5.2.2.1 Signalling protocol (ALCAP)..... | 12 |
+| 5.2.2.1.1 AAL2 Signalling Protocol (Q.2630.2)..... | 12 |
+| 5.2.2.2 Signalling transport converter..... | 12 |
+| 5.2.2.2.1 AAL2 MTP3B Signalling Transport Converter (Q.2150.1)..... | 12 |
+| 5.2.2.3 MTP3b (Q.2210)..... | 12 |
+| 5.2.2.4 SSCF-NNI (Q.2140)..... | 12 |
+| 5.2.2.5 SSCOP (Q.2110)..... | 13 |
+| 5.2.2.6 ATM Adaptation Layer Type 5 (I.363.5) ..... | 13 |
+| 5.3 Interworking between ATM and IP Transport Options ..... | 13 |
+| 5.3.1 Introduction ..... | 13 |
+| 5.3.2 Interworking Alternatives..... | 13 |
+| 6 Packet switched domain..... | 13 |
+| 6.1 Transport network user plane..... | 13 |
+| 6.1.1 General ..... | 13 |
+| 6.1.2 ATM Transport Option..... | 14 |
+| 6.1.2.1 General..... | 14 |
+| 6.1.2.2 GTP-U..... | 14 |
+| 6.1.2.3 UDP /IP..... | 14 |
+| 6.1.2.4 ATM Adaptation Layer Type 5 (I.363.5) ..... | 14 |
+| 6.1.2.5 IP/ATM..... | 15 |
+| 6.1.3 IP Transport Option..... | 15 |
+
+| | | |
+|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| 6.1.3.1 | General..... | 15 |
+| 6.1.3.2 | GTP-U..... | 15 |
+| 6.1.3.3 | UDP /IP..... | 15 |
+| 6.1.3.4 | Diffserv code point marking ..... | 16 |
+| 6.2 | Transport network control plane ..... | 16 |
+| 7 | Broadcast Domain..... | 16 |
+| 7.1 | Transport network user plane..... | 16 |
+| 7.1.1 | General ..... | 16 |
+| 7.1.2 | ATM Transport Option..... | 16 |
+| 7.1.2.1 | General..... | 16 |
+| 7.1.2.2 | TCP/IP ..... | 16 |
+| 7.1.2.3 | ATM Adaptation Layer Type 5 (I.363.5) ..... | 17 |
+| 7.1.2.4 | IP/ATM..... | 17 |
+| 7.1.3 | IP Transport Option..... | 17 |
+| 7.1.3.1 | General..... | 17 |
+| 7.1.3.3 | TCP /IP ..... | 17 |
+| 7.1.3.4 | Diffserv code point marking ..... | 17 |
+| 7.2 | Transport network control plane ..... | 17 |
+| Annex A (informative): | IP-ATM Interworking ..... | 19 |
+| A.1 | Application of IP tunnelling in IP-ATM interworking alternative 1 in case of no direct ATM connectivity at the IP&ATM dual stack RNC/CN-node ..... | 19 |
+| A.2 | Application of IP-ALCAP in IP-ATM interworking alternative 2 ..... | 19 |
+| Annex B (informative): | Change history..... | 20 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the standards for user data transport protocols and related signalling protocols to establish user plane transport bearers over the UTRAN Iu 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] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [2] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation layer specification: Type 2 AAL".
+- [3] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation layer specification: Type 5 AAL".
+- [4] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2".
+- [5] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan".
+- [6] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".
+- [7] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer - Service Specific Coordination Function for Support of Signalling at the Network Node Interface (SSCF-NNI)".
+- [8] ITU-T Recommendation Q.2150.1 (1999-12): "AAL type 2 signalling transport converter on broadband MTP".
+- [9] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
+- [10] ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)".
+- [11] ITU-T Recommendation X.213 (1995-11): "Information technology - Open systems interconnection - Network Service Definitions".
+- [12] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [13] IETF RFC 791 (1981-09): "Internet Protocol".
+- [14] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
+- [15] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM".
+- [16] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
+- [17] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".
+- [18] IETF RFC 793 (1981-09): "Transmission Control Protocol".
+
+- [19] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers".
+- [20] ITU-T Implementor's guide (1999-12) for recommendation Q.2210 (1996-07).
+- [21] ITU-T Recommendation Q.2630.2 (2000-12): "AAL type 2 signalling protocol (Capability Set 2)".
+- [22] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications".
+- [23] IETF RFC 1890 (1996-01): "RTP Profile for Audio and Video Conferences with Minimal Control".
+- [24] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols"
+- [25] IETF RFC 1661 (1994-07): "The Point-to-Point Protocol (PPP)".
+- [26] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [27] IETF RFC 2507 (1999-02): "IP header compression".
+- [28] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [29] IETF RFC 2686 (1996-09): "The Multi-Class Extension to Multi-Link PPP".
+- [30] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [31] Void
+- [32] IETF RFC 3153 (2001-08): "PPP Multiplexing".
+- [33] IETF RFC 2364 (1998-07): "PPP over AAL5".
+- [34] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture".
+- [35] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing".
+- [36] 3GPP TS 25.401: "UTRAN overall description".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Access Link Control Application Part (ALCAP):** generic name for the transport signalling protocols used to set-up and teardown transport bearers
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|------------------------------------------|
+| AAL | ATM Adaptation Layer |
+| AESA | ATM End System Address |
+| ALCAP | Access Link Control Application Part |
+| ARP | Address Resolution Protocol |
+| ATM | Asynchronous Transfer Mode |
+| CN | Core Network |
+| GTP | GPRS Tunnelling Protocol |
+| HDLC | High-level Data Link Control |
+| IP | Internet Protocol |
+| LC | Link Characteristics |
+| LIS | Logical IP Subnet |
+| MTP3b | Message Transfer Part level 3 for Q.2140 |
+| NSAP | Network Service Access Point |
+
+| | |
+|----------|---------------------------------------------------------------|
+| PDU | Protocol Data Unit |
+| PPP | Point-to-Point Protocol |
+| RFC | Request For Comment |
+| RNC | Radio Network Controller |
+| RTCP | Real-time Transport Control Protocol |
+| RTP | Real-time Transport Protocol |
+| SA | Service Area |
+| SABP | Service Area Broadcast Protocol |
+| SABS | Service Area Broadcast Service |
+| SAR | Segmentation and Reassembly |
+| SCSF-NNI | Service Specific Coordination Function-Network Node Interface |
+| SSCOP | Service Specific Connection Oriented Protocol |
+| SSCS | Service Specific Convergence Sublayer |
+| SSRC | Synchronisation Source |
+| TCP | Transmission Control Protocol |
+| TEID | Tunnel Endpoint Identifier |
+| UDP | User Datagram Protocol |
+| VC | Virtual Circuit |
+
+# 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the transport network user plane and the transport network control plane according to ITU-T Recommendation I.361 [1]. The structure of the cell header used in the UTRAN Iu interface is the cell header format and encoding at NNI (see figure 3/I.361).
+
+## 4.2 IP Transport Option
+
+An RNC/CN-node supporting IP transport option on the Iu interface shall support PPP protocol with HDLC framing (IETF RFC 1661 [25], IETF RFC 1662 [26]).
+
+NOTE: This does not preclude the single implementation and use of any other protocols (e.g. PPPMux /AAL5/ATM (IETF RFC 3153 [32], IETF RFC 2364 [33]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [34]), etc.) fulfilling the UTRAN requirements toward the upper layers.
+
+An RNC/CN-node supporting IP transport option on the Iu interface and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [27]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [28], IETF RFC 2686 [29]). In this case the negotiation of header compression (IETF RFC 2507 [27]) over PPP shall be performed via IETF RFC 2509 [30].
+
+# 5 Circuit switched domain
+
+## 5.1 Transport network user plane
+
+### 5.1.1 General
+
+There are two options for the transport layer for data streams over Iu-CS:
+
+- 1) ATM based Transport (ATM transport option)
+- 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+
+
+| |
+|--------------------------|
+| AAL-2 SAR SSCS (I.366.1) |
+| AAL2 (I.363.2) |
+| ATM (I.361) |
+| Physical Layer |
+
+Protocol Stack
+for the ATM transport option
+
+| |
+|--------------------------------------------|
+| RTP (RFC 1889) |
+| UDP (RFC 768) |
+| IPv6 (RFC 2460)
IPv4 optional (RFC 791) |
+| Data Link Layer |
+| Physical Layer |
+
+Protocol Stack
+for the IP transport option
+
+Figure 1: Transport network layer for data streams over Iu-CS. The diagram shows two protocol stacks. The left stack, labeled 'Protocol Stack for the ATM transport option', consists of four layers: AAL-2 SAR SSCS (I.366.1), AAL2 (I.363.2), ATM (I.361), and Physical Layer. The right stack, labeled 'Protocol Stack for the IP transport option', consists of five layers: RTP (RFC 1889), UDP (RFC 768), IPv6 (RFC 2460) with IPv4 optional (RFC 791), Data Link Layer, and Physical Layer.
+
+**Figure 1. Transport network layer for data streams over Iu-CS.**
+
+### 5.1.2 ATM Transport Option
+
+#### 5.1.2.1 ATM Adaptation Layer 2
+
+##### 5.1.2.1.1 AAL2-Segmentation and Reassembly Service Specific Convergence Sublayer (I.366.1)
+
+Service Specific Segmentation and Reassembly (SSSAR) sublayer of ITU-T Recommendation I.366.1 [4] is used for the segmentation and reassembly of AAL2 SDUs (i.e., only SSSAR is used from ITU-T Recommendation I.366.1).
+
+##### 5.1.2.1.2 AAL2-specification (I.363.2)
+
+AAL2 shall be used according to ITU-T Recommendation I.363.2 [2].
+
+### 5.1.3 IP Transport Option
+
+#### 5.1.3.1 General
+
+In the IP transport option RTP over UDP over IP shall be supported as the transport for data streams on the Iu-CS interface. The data link layer is as specified in subclause 4.2.
+
+The transport bearer is identified by the UDP port number and the IP address (source UDP port number, destination UDP port number, source IP address, destination IP address).
+
+The source IP address and destination IP address exchanged via RANAP on the Iu-CS interface shall use the NSAP structure. See sub clause 6.1.8.2 in TS 25.401 [36].
+
+#### 5.1.3.2 UDP/IP
+
+The path protocol used shall be UDP (IETF RFC 768 [12]).
+
+An IP RNC/CN-node shall support IPv6. The support of IPv4 is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall send downstream packets of a given RAB to the RNC IP address / UDP port (received in RANAP) associated to that particular RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address / UDP port (received in RANAP) associated to that particular RAB. If there is no RNC IP address / UDP port yet associated to the packet processing function in the CN for a RAB not yet finally set-up, the packet processing function in the CN for that RAB shall extract the source IP address / UDP port from the first received IP packet to identify the peer IP/UDP entity. The packet processing function in the RNC shall use the same source IP address / UDP port as is sent to CN in RANAP.
+
+The RNC/CN-node shall use two consecutive port numbers for the RTP bearer and for the optional RTCP connection that transport a single Iu UP connection. Two such consecutive port numbers are termed “port number block” in what follows. The first port number shall be even and shall be assigned to the RTP protocol. The next port number shall be assigned to the RTCP protocol. This port shall be reserved even if the optional RTCP protocol is not used.
+
+Each RNC/CN-node shall administer the port numbers it intends to use for RTP/RTCP port number blocks.
+
+#### 5.1.3.3 RTP
+
+RTP (IETF RFC 1889 [22]) shall be applied.
+
+##### 5.1.3.3.1 RTP Header
+
+The RTP Header Fields shall be used as described in the following subclauses:
+
+###### 5.1.3.3.1.1 Version
+
+RTP Version 2 shall be used.
+
+###### 5.1.3.3.1.2 Padding
+
+Padding shall not be used.
+
+###### 5.1.3.3.1.3 Extension
+
+The RTP Header shall not have an extension.
+
+###### 5.1.3.3.1.4 Contributing Source (CSRC) count
+
+There are zero CSRCs.
+
+###### 5.1.3.3.1.5 Marker Bit
+
+The marker bit is ignored.
+
+###### 5.1.3.3.1.6 Payload Type
+
+A dynamic Payload Type (IETF RFC 1890 [23]) shall be used. Values in the Range between 96 and 127 shall be used. The value shall be ignored in the receiving entity.
+
+###### 5.1.3.3.1.7 Sequence Number
+
+The sequence number shall be supplied by the source of an RTP PDU. The sink of an RTP PDU may ignore the sequence number or it may use it to obtain statistics about the link quality and / or to correct out-of-sequence delivery, e.g. by dropping out-of-sequence packets.
+
+###### 5.1.3.3.1.8 Timestamp
+
+The timestamp shall be supplied by the source of an RTP PDU. A clock frequency of 16000 Hz shall be used. The sink of an RTP PDU may ignore the timestamp or it may use it to obtain statistics about the link quality and / or to correct jitter.
+
+###### 5.1.3.3.1.9 Synchronisation Source (SSRC)
+
+The source of an RTP PDU shall supply a SSRC. The sink of an RTP PDU may ignore the SSRC if it does not use RTCP.
+
+###### 5.1.3.3.1.10 CSRC list
+
+This list is empty.
+
+##### 5.1.3.3.2 RTP Payload
+
+A single Iu UP PDU, as described in TS 25.415 [24], shall be transported as RTP payload.
+
+#### 5.1.3.4 RTCP
+
+RTCP (IETF RFC 1889 [22]) may be applied. RTCP over UDP (IETF RFC 768 [12]) over IPv6 (IETF RFC 2460 [16]) shall be used (IPv4 (IETF RFC 791 [13]) may be used optionally). The use of the RTCP protocol is optional. The receiving entity may ignore incoming RTCP PDUs.
+
+Figure 1a shows the protocol stack for the transport of RTCP. The above Sections about IP and UDP shall also apply for the transport of RTCP.
+
+
+
+| |
+|-------------------------------------------|
+| RTCP( RFC 1889 ) |
+| UDP ( RFC 768 ) |
+| IPv6 (RFC2460)
IPv4 optional (RFC 791) |
+
+**Figure 1a. RTCP Protocol stack for data stream transport on Iu-CS.**
+
+#### 5.1.3.5 Diffserv code point marking
+
+IP Differentiated Services code point marking (IETF RFC 2474 [19]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+## 5.2 Transport network control plane
+
+### 5.2.1 General
+
+The following figure shows the protocol stack for transport signalling over Iu-CS in ATM based transport (ATM transport option). An ALCAP protocol is not required when both UTRAN and CN nodes are using the IP based transport (IP transport option).
+
+The protocol stack for IP-ALCAP in IP to ATM interworking case is defined in chapter 5.3.3 of this Technical Specification.
+
+
+
+| |
+|----------------------------------------------------------------|
+| AAL2 connection signalling
(Q.2630.2) |
+| AAL2 Signalling Transport
Converter for MTP3b
(Q.2150.1) |
+| MTP3b |
+| SSCF-NNI |
+| SSCOP |
+| ATM |
+| Physical Layer |
+
+**Figure 2. Signalling bearer for ALCAP on Iu-CS interface.**
+
+### 5.2.2 Transport Signalling for the ATM Transport Option
+
+#### 5.2.2.1 Signalling protocol (ALCAP)
+
+##### 5.2.2.1.1 AAL2 Signalling Protocol (Q.2630.2)
+
+In the ATM transport option ITU-T Recommendation Q.2630.2 [21] shall be used for establishing AAL2 connections towards the circuit switched domain. ITU-T Recommendation Q.2630.2 [21] adds new optional capabilities to ITU-T Recommendation Q.2630.1 [10].
+
+The AAL2 transport layer uses the embedded E.164 or other AESA variants of the NSAP addressing formats ITU-T Rec. X.213 [11], and ITU-T Recommendation E.191 [35]. Native E.164 addressing (ITU-T Recommendation E.164 [5]) shall not be used.
+
+Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH request primitive of ITU-T Recommendation Q.2630.2 [21].
+
+The Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol.
+
+#### 5.2.2.2 Signalling transport converter
+
+##### 5.2.2.2.1 AAL2 MTP3B Signalling Transport Converter (Q.2150.1)
+
+The AAL2 MTP3b Signalling Transport Converter shall be used according to ITU-T Recommendation Q.2150.1 [8].
+
+#### 5.2.2.3 MTP3b (Q.2210)
+
+MTP3b shall be used according to ITU-T Recommendation Q.2210 [9] and ITU-T Implementor's guide (12/99) for recommendation Q.2210 [20].
+
+#### 5.2.2.4 SSCF-NNI (Q.2140)
+
+SSCF-NNI shall be used according to ITU-T Recommendation Q.2140 [7].
+
+#### 5.2.2.5 SSCOP (Q.2110)
+
+SSCOP shall be used according to ITU-T Recommendation Q.2110 [6].
+
+#### 5.2.2.6 ATM Adaptation Layer Type 5 (I.363.5)
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
+
+## 5.3 Interworking between ATM and IP Transport Options
+
+### 5.3.1 Introduction
+
+This clause specifies the interworking between IP and ATM transport options. An RNC/CN-node supporting IP transport option shall provide interworking to a CN-node/RNC supporting only ATM transport option.
+
+### 5.3.2 Interworking Alternatives
+
+For interworking with a CN-node/RNC supporting only ATM transport option, the RNC/CN-node supporting IP transport option shall additionally support at least one of the following interworking mechanisms:
+
+- 1) ATM&IP dual stack. An IP-ALCAP protocol is not required in this interworking solution.
+
+Annex A of this technical specification shows an example of protocols for the case the ATM&IP RNC/CN-node has no ATM connectivity.
+
+- 2) An Interworking Function (IWF), either internal or external to the RNC/CN node.
+
+Annex A of this technical specification shows an example of a protocol stack for the case when the IWF is an external unit to the RNC/CN node. Other protocol stacks for this case are not precluded.
+
+# 6 Packet switched domain
+
+## 6.1 Transport network user plane
+
+### 6.1.1 General
+
+There are two options for the transport layer for data streams over Iu-PS:
+
+- 1) ATM based Transport (ATM transport option)
+- 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+
+
+| |
+|----------------|
+| GTP-U |
+| UDP |
+| IP |
+| AAL5 |
+| ATM |
+| Physical Layer |
+
+Protocol Stack
+for the ATM transport option
+
+| |
+|--------------------------------------------|
+| GTP-U |
+| UDP |
+| IPv6 (RFC 2460)
IPv4 optional (RFC 791) |
+| Data Link Layer |
+| Physical Layer |
+
+Protocol Stack
+for the IP transport option
+
+Figure 3: Transport network layer for data streams over Iu-PS. Diagram showing two protocol stacks: ATM based (GTP-U/UDP/IP/AAL5/ATM/Physical) and IP based (GTP-U/UDP/IPv6 or IPv4/Data Link/Physical).
+
+**Figure 3. Transport network layer for data streams over Iu-PS.**
+
+### 6.1.2 ATM Transport Option
+
+#### 6.1.2.1 General
+
+In the ATM transport option, the protocol architecture for the User Plane of the Iu interface towards the packet switched domain shall be GTP-U (TS 29.060 [17]) over UDP over IP over AAL5 over ATM. One or several AAL5/ATM permanent VC's may be used as the common layer 2 resources between the UTRAN and the packet switched domain of the CN.
+
+One switched VC may be used per user flow. The standardisation of the procedures and protocols for use of Switched VC is outside the scope of 3GPP.
+
+Congestion control shall be performed over the Iu user plane toward the packet switched domain using buffer management and no flow control.
+
+#### 6.1.2.2 GTP-U
+
+The GTP-U (TS 29.060 [17]) protocol shall be used over the Iu interface toward the packet switched domain.
+
+#### 6.1.2.3 UDP /IP
+
+The path protocol used shall be UDP (IETF RFC 768 [12]), which is specified in RFC 768.
+
+The UDP port number for GTP-U shall be as defined in TS 29.060 [17].
+
+IPv4 (IETF RFC 791 [13]) shall be supported; IPv6 (IETF RFC 2460 [16]) support is optional.
+
+There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall send downstream packets of a given RAB to the RNC IP address (received in RANAP) associated to that particular
+
+RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address (received in RANAP) associated to that particular RAB.
+
+There is one RNC IP address per RNC in the CN associated with one MBMS RAB. This address is received in RANAP at the establishment of the MBMS RAB. The packet processing function in the CN shall send the downstream packets of the MBMS RAB to this associated RNC IP address.
+
+#### 6.1.2.4 ATM Adaptation Layer Type 5 (I.363.5)
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
+
+AAL5 virtual circuits shall be used to transport the IP packets across the Iu interface toward the packet switched domain. Multiple VCs may be used over the interface. An association shall be made between a VC and the IP addresses that are related to this VC in the peer node side. This association shall be made using O&M or using "ATM Inverse ARP" when PVCs are used.
+
+When PVCs are used, quality of service differentiation shall only be performed at the IP layer using differentiated services (IETF RFC 2474 [19]).
+
+#### 6.1.2.5 IP/ATM
+
+When the association mentioned in 6.1.2.4 is made using O&M, the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used.
+
+When the association mentioned in 6.1.2.4 is made using "ATM Inverse ARP", "Classical IP and ARP" over ATM protocols and the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used. "Classical IP and ARP over ATM" is specified in IETF RFC 2225 [15]. "Multiprotocol Encapsulation over AAL5" is specified in IETF RFC 2684 [14].
+
+"Classical IP and ARP over ATM" allows routers to be members of one or more LISs. The CN side of the Iu interface shall provide IP routing functionalities. The RNC side of the Iu interface may provide routing functionalities. If the RNC side of the Iu interface does not provide routing functionalities, the RNC routing tables shall include default route entries.
+
+### 6.1.3 IP Transport Option
+
+#### 6.1.3.1 General
+
+In the IP transport option GTP-U (TS 29.060 [17]) over UDP over IP shall be supported as the transport for data streams on the Iu-PS interface. The data link layer is as specified in subclause 4.2.
+
+The transport bearer is identified by the GTP-U TEID (TS 29.060 [17]) and the IP address (source TEID, destination TEID, source IP address, destination IP address).
+
+#### 6.1.3.2 GTP-U
+
+The GTP-U (TS 29.060 [17]) protocol shall be used over the Iu interface toward the packet switched domain.
+
+#### 6.1.3.3 UDP /IP
+
+The path protocol used shall be UDP (IETF RFC 768 [12]).
+
+The UDP port number for GTP-U shall be as defined in TS 29.060 [17].
+
+An IP RNC/CN-node shall support IPv6. The support of IPv4 is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+RNC shall support fragmentation and assembly of GTP packets at the IP layer.
+
+There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall send downstream packets of a given RAB to the RNC IP address (received in RANAP) associated to that particular
+
+RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address (received in RANAP) associated to that particular RAB.
+
+There is one RNC IP address per RNC in the CN associated with one MBMS RAB. This address is received in RANAP at the establishment of the MBMS RAB. The packet processing function in the CN shall send the downstream packets of the MBMS RAB to this associated RNC IP address.
+
+#### **6.1.3.4 Diffserv code point marking**
+
+IP Differentiated Services code point marking (IETF RFC 2474 [19]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+## 6.2 Transport network control plane
+
+ALCAP is not required over the Iu interface towards the packet switched domain.
+
+# 7 Broadcast Domain
+
+## 7.1 Transport network user plane
+
+### 7.1.1 General
+
+There are two options for the transport layer for data streams over Iu-BC:
+
+- 1) ATM based Transport (ATM transport option)
+- 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+
+
+| |
+|----------------|
+| TCP |
+| IP |
+| AAL5 |
+| ATM |
+| Physical Layer |
+
+Protocol Stack
+for the ATM transport option
+
+| |
+|-----------------------------------------------------------|
+| TCP |
+| IPv6 (RFC 2460)
IPv4 optional (RFC 791) |
+| Data Link Layer |
+| Physical Layer |
+
+Protocol Stack
+for the IP transport option
+
+Figure 4: Transport network layer for data streams over Iu-BC. Diagram showing two protocol stacks: ATM transport option (TCP, IP, AAL5, ATM, Physical Layer) and IP transport option (TCP, IPv6/IPv4, Data Link Layer, Physical Layer).
+
+**Figure 4. Transport network layer for data streams over Iu-BC.**
+
+### 7.1.2 ATM Transport Option
+
+#### 7.1.2.1 General
+
+In the ATM transport option, the protocol architecture for the Service Area Broadcast Plane of the Iu interface shall be TCP over IP over AAL5 over ATM.
+
+#### 7.1.2.2 TCP/IP
+
+The path protocol used shall be TCP, which is specified in IETF RFC793 [18]. IPv4 (IETF RFC 791 [13]) shall be supported, IPv6 (IETF RFC 2460 [16]) support is optional.
+
+The TCP Destination Port number for SABP messages is 3452. It is the registered port number for SABP.
+
+The 3452 destination port number shall be used by both entities (RNC or CN) whenever it sets up a new TCP connection. When it sends SABP messages on an existing TCP connection, the sending entity (RNC or CN) shall use as TCP destination port number either 3452 if it was the initiator of this TCP connection, or the TCP source port number that was received from the peer entity that had initiated this existing TCP connection.
+
+#### 7.1.2.3 ATM Adaptation Layer Type 5 (I.363.5)
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5.
+
+AAL5 virtual circuits shall be used to transport the IP packets across the Iu interface toward the broadcast domain. Multiple VC's may be used over the interface. An association shall be made between a VC and the IP addresses that are related to this VC in the peer node side. This association shall be made using O&M or using ATM Inverse ARP according to Classical IP over ATM when PVCs are used.
+
+#### 7.1.2.4 IP/ATM
+
+When the association mentioned in 7.1.2.3 is made using O&M, the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used.
+
+When the association mentioned in 7.1.2.3 is made using "ATM Inverse ARP", "Classical IP and ARP over ATM" protocols and the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used. "Classical IP and ARP over ATM" is specified in IETF RFC 2225 [15]. "Multiprotocol Encapsulation over AAL5" is specified in IETF RFC 2684 [14].
+
+### 7.1.3 IP Transport Option
+
+#### 7.1.3.1 General
+
+In the IP transport option TCP over IP shall be supported as the transport for data streams on the Iu-BC interface. The data link layer is as specified in subclause 4.2.
+
+The transport bearer is identified by the TCP port number and the IP address (source TCP port number, destination TCP port number, source IP address, destination IP address).
+
+#### 7.1.3.3 TCP /IP
+
+The path protocol used shall be TCP, which is specified in IETF RFC 793 [18].
+
+The TCP Destination Port number for SABP messages is 3452. It is the registered port number for SABP.
+
+The 3452 destination port number shall be used by both entities (RNC or CN) whenever it sets up a new TCP connection. When it sends SABP messages on an existing TCP connection, the sending entity (RNC or CN) shall use as TCP destination port number either 3452 if it was the initiator of this TCP connection, or the TCP source port number that was received from the peer entity that had initiated this existing TCP connection.
+
+An IP RNC/CN-node shall support IPv6. The support of IPv4 is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+#### 7.1.3.4 Diffserv code point marking
+
+IP Differentiated Services code point marking (IETF RFC 2474 [19]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+## 7.2 Transport network control plane
+
+ALCAP is not required over the Iu interface towards the broadcast domain.
+
+# --- Annex A (informative): IP-ATM Interworking
+
+## A.1 Application of IP tunnelling in IP-ATM interworking alternative 1 in case of no direct ATM connectivity at the IP&ATM dual stack RNC/CN-node
+
+One possibility of enabling ATM connectivity to the IP&ATM dual stack RNC/CN-node in the IP-ATM interworking alternative 1 scenario specified in chapter 5.3.2 is to use any ATM emulation over IP protocol from the IETF standards e.g. via tunnelling techniques.
+
+## --- A.2 Application of IP-ALCAP in IP-ATM interworking alternative 2
+
+One example scenario of IP-ATM interworking alternative 2 of section 5.3.2 is to use IP-ALCAP as specified in ITU-T Recommendation Q.2631.1 (10/2003) as the bearer control protocol between the RNC/CN Node and its external IWF. The following figure shows the corresponding protocol stack.
+
+
+
+The diagram shows a vertical stack of five protocol layers. From top to bottom, they are: IP-ALCAP (Q.2631.1), Q.2150.3, SCTP (RFC2960), IPv6 (RFC2640) with IPv4 optional (RFC791) as a sub-layer, and Datalink Layer.
+
+| |
+|------------------------------------------|
+| IP-ALCAP
(Q.2631.1) |
+| Q.2150.3 |
+| SCTP
(RFC2960) |
+| IPv6 (RFC2640)
IPv4 optional (RFC791) |
+| Datalink Layer |
+
+Protocol stack diagram for IP-ALCAP in IP-ATM interworking alternative 2
+
+Figure A.1. Protocol stack for IP-ALCAP in IP-ATM interworking alternative 2
+
+# --- Annex B (informative): Change history
+
+| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New |
+|------------|-----------|------|-----|------------------------------------------------------------|--------|
+| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 |
+| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 |
+| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 |
+| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 |
+| 06/2011 | RP-110685 | 0090 | - | Reference review outcome in TS 25.414 | 10.1.0 |
+| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25415/1bf34e86af3591c80bfbc1c318f811c0_img.jpg b/marked/Rel-11/25_series/25415/1bf34e86af3591c80bfbc1c318f811c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4ff93a9fa8dcb15f9fd5e19566ecc698ca5ca80
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/1bf34e86af3591c80bfbc1c318f811c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ea8bbb6fa2e7356cee07fd57ece4e2cefc89315a8b5a6cdf7654400e936b0d6
+size 27987
diff --git a/marked/Rel-11/25_series/25415/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Rel-11/25_series/25415/1dbb1d90b2022a3a765c85929a515cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5112182e27c8a2a816dd840f0e3f5abe54e3a40c
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/1dbb1d90b2022a3a765c85929a515cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f12ed3020ae82af1621a19bb64cf9a484291389deb31d5aae339f26268dfb19b
+size 43490
diff --git a/marked/Rel-11/25_series/25415/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/25_series/25415/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e64c5cbf72dfc2943622f3009ef9d0e3d9d6707c
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0a9c7005c139b9f4b495148011b7efa5aecedf21f028f49b087dad3d291cf81
+size 23930
diff --git a/marked/Rel-11/25_series/25415/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/25_series/25415/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6cd88777b9212766a9d544a380c3b23fe415411d
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0567b415b3166eb4941b781141317560911cd40e88916bf703c64cd77e91a4b3
+size 35342
diff --git a/marked/Rel-11/25_series/25415/2834bdd6eb8540277e609decbb924003_img.jpg b/marked/Rel-11/25_series/25415/2834bdd6eb8540277e609decbb924003_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69fcc82d6edd7cb8fced8b800c876dedb1716a63
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/2834bdd6eb8540277e609decbb924003_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:074c29698ad65dad03151adf790a6b525883dc57e047c3e5b0a9a042aca6b38d
+size 20488
diff --git a/marked/Rel-11/25_series/25415/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/25_series/25415/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..120c90139f7bd8b9623245acb9d5e56a4d570836
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26ca713bcfd0d9b4d69cf751ea37b29ed7ef3c6f0ca9fdee400b093ebd2e80d5
+size 18742
diff --git a/marked/Rel-11/25_series/25415/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/25_series/25415/2cf3896394a2342a2b46c504ab9a8830_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..945716d6c8e76420af57af6fd09f2ef4021dbe5c
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/2cf3896394a2342a2b46c504ab9a8830_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f05cf966c58faa611ab91bb2b2ad493c6eb1fc47b111a75551c786d4e551471
+size 75137
diff --git a/marked/Rel-11/25_series/25415/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/Rel-11/25_series/25415/2de714cedbbdd36f901f71bafa78f75a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70586f8838e3852f613d182f35d251ded6951d9c
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/2de714cedbbdd36f901f71bafa78f75a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0b261730454696d760f56d1bd2c0c07596f1eb1daa433ceb6458159b437b749
+size 55892
diff --git a/marked/Rel-11/25_series/25415/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/Rel-11/25_series/25415/4842f073775fb1e84d101c02fd74e59e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6fe1a61adcd20b8b8e4362126931f53d05c67f7
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/4842f073775fb1e84d101c02fd74e59e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:618aa163a8bcdf2b31946ed851cb56e3100d8dc2368be0dc6441f0675807d5e6
+size 28567
diff --git a/marked/Rel-11/25_series/25415/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/marked/Rel-11/25_series/25415/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..caf8d6f939d35ec59e97c147c6969de70163b885
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cef15438f28b44918c1693d70882b5cf5e0cacb2dd33c0e2280a5fe8b58dbd66
+size 66603
diff --git a/marked/Rel-11/25_series/25415/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-11/25_series/25415/4b87467ad9642943235f48f7d4b59449_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3b880a5e8d2b5e7eaeb1621c0ee047ef85fd353
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/4b87467ad9642943235f48f7d4b59449_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54d7723d91e890173aca160f4df7b0619875833af0f9df20dc8c4f48d13f5eb6
+size 22334
diff --git a/marked/Rel-11/25_series/25415/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/25_series/25415/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bddd37530de02b14c5f3304c49dcb4d900394e3a
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e7236167b656e96eac8bce74727aa1484b265b98aa993b880d42d1d71505d74
+size 11597
diff --git a/marked/Rel-11/25_series/25415/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-11/25_series/25415/51db757d054ce1ce83c436a3578b56ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec25de24d59c4ab3ced6bafd834f9350aed44b0c
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/51db757d054ce1ce83c436a3578b56ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb34649856764ca71554be533d936505f960a2768d6090c8aba6735fa298d230
+size 19040
diff --git a/marked/Rel-11/25_series/25415/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-11/25_series/25415/5793a44ffdadd039928e2f9fe6daae06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ab9bb3f8dad0c78eba72f24790c11776aae2892
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/5793a44ffdadd039928e2f9fe6daae06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3d4c85e99db94af82ae7312b48f97cd64a0cb9816526f31f7cf015b92fe991f
+size 19643
diff --git a/marked/Rel-11/25_series/25415/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/25_series/25415/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f80ffb9e351ecbec58e191e398f9308063a6d3ff
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2301d9482a3b76a7f8c26971efc6ac7e941797f5e66b0cd139349f9a9d3d93a0
+size 51417
diff --git a/marked/Rel-11/25_series/25415/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-11/25_series/25415/63e0c22852c26699d0bd095a2d796bab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf70928fa337a36ddda2cd94d1e083ba0fb19f35
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/63e0c22852c26699d0bd095a2d796bab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e914debf294c0812600ad169e187707d89347a4b17386fcdb973d0dcb16963f5
+size 40096
diff --git a/marked/Rel-11/25_series/25415/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-11/25_series/25415/73dff6b45b2b9ffd384bab3235f869af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..98e985a7f9a639077d9cfe67c90f0e09911a3626
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/73dff6b45b2b9ffd384bab3235f869af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75b4e4aecc2cafc08bc6572100fa66947f6c3d026cfdc5db24a46c0020de2b88
+size 20574
diff --git a/marked/Rel-11/25_series/25415/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-11/25_series/25415/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dda6ce52411b300fcd3fa125df94329a353045b7
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:369fee04551cbcbfa698048ff82fa8e1ca52f453a741a43928932901a2c18549
+size 34695
diff --git a/marked/Rel-11/25_series/25415/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-11/25_series/25415/86b4670fc1a5a694821ee92b99c1209a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d58e38de252178a3601428bf6185a2ee4c17465
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/86b4670fc1a5a694821ee92b99c1209a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70f910d1bcaee6ae5c2738fe7c53cfacfcfc74b7db44f359fd762dea50805297
+size 22029
diff --git a/marked/Rel-11/25_series/25415/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/25_series/25415/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41b7afc865095dbeddd00e0681651ca9d2d82de8
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99d010e3db2a74e8ddf5021d2c5754b7f838f26d6b479a1285fbd456fba87b0f
+size 19792
diff --git a/marked/Rel-11/25_series/25415/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/25_series/25415/90ddb84c323b956e2d50a54d3f870566_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88c2f15063419b75b3b12fd6e1a469d9fd02827b
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/90ddb84c323b956e2d50a54d3f870566_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8f6c01fb2c14c33af1404b0c80938d12be458034d21782e0bf45e1aa092a258
+size 13550
diff --git a/marked/Rel-11/25_series/25415/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-11/25_series/25415/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6cfe63f325b8e10caab65568519d0e4561ab147f
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9160f77e4efb0196e12bfbb99525c36d857f0b2251c3c2f954bbf9651d44dc50
+size 49865
diff --git a/marked/Rel-11/25_series/25415/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/25_series/25415/a0e8fe7862a6d7341faf5dac275277cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54db72dab6fd9311314b0bdda71b1c8856ae3bc8
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/a0e8fe7862a6d7341faf5dac275277cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b81181d5f9d9608c056b2f7e131be3d7fc576d0b29590afd2e3f3a80006f408
+size 104046
diff --git a/marked/Rel-11/25_series/25415/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/25_series/25415/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..787e027e6f4300ad1e26e687c4afdc6c30877b88
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1d4ee7472f0421bab4ff5a693507e7ff9ff5c2e3726a66a43911bb1976ea7e2
+size 9309
diff --git a/marked/Rel-11/25_series/25415/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-11/25_series/25415/b06a4c871dfd0ce034cf801519d0039a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3a1bf079e5340a9bda46e40b93d4fc25119909bb
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/b06a4c871dfd0ce034cf801519d0039a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4559a0a1e74a440186a2050e0152af2b19191bd3de3bf6e79adcb1ed35c4364
+size 34624
diff --git a/marked/Rel-11/25_series/25415/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/25_series/25415/d9c0a780cd22626253dab4aa41699e2f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7efd2f205f3bd213f61fce908b9508255048203
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/d9c0a780cd22626253dab4aa41699e2f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25249008988723465a744632d1900090321680debed9729a4b3c4a4fc7712ec5
+size 27859
diff --git a/marked/Rel-11/25_series/25415/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-11/25_series/25415/dd380ccd5aca1151074fede04826f1a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40ee3f0e621001095d53354a9139484d16975bb4
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/dd380ccd5aca1151074fede04826f1a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63c0f20689a3d98f268dfd9087bd1e5b50f9d46b01c7fc4f94b7f4b9d9098520
+size 17958
diff --git a/marked/Rel-11/25_series/25415/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-11/25_series/25415/ddee3e67e0dfc22e25188fa635a19558_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b08b00caa0fc52105b5b047546042de9f36b89f6
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/ddee3e67e0dfc22e25188fa635a19558_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d27c71c36d2e8a5c7b92eea74a0efcb039018c80341f70ccf05a630dd75bbcea
+size 42833
diff --git a/marked/Rel-11/25_series/25415/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-11/25_series/25415/e05c1a13b44ab41505609d82b00cf4df_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1205fc94d124e6f2694f1287cca54de7fc04cb73
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/e05c1a13b44ab41505609d82b00cf4df_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd016d8b6d4192ea703f198a675f3969f0494f4d12fbb2fa91a89c9d863a58c8
+size 14630
diff --git a/marked/Rel-11/25_series/25415/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-11/25_series/25415/e29665b8abcea967ef289c6aff07ae4c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0b62747bbcff59698d003904c1ccc19b86c943a
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/e29665b8abcea967ef289c6aff07ae4c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ca50bfe45d302b91bdfb7243e5274d493d7e1348c37d2488c5eb3f48e674672
+size 22307
diff --git a/marked/Rel-11/25_series/25415/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/25_series/25415/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c9682f77fb8cec94cbb488df4d666f73e1e0ae4
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be4b315856ac2aef2382634c56dff1075fb8911de8672d805fad145dea02447a
+size 29895
diff --git a/marked/Rel-11/25_series/25415/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/25_series/25415/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd9309ccdd58166f4a4d52bfc7c605e8bca5f501
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c91f96709ca7a6cf47a2af4c10b435fd08b6844d8dd5fc1a21cada4ac3b30e1
+size 64923
diff --git a/marked/Rel-11/25_series/25415/raw.md b/marked/Rel-11/25_series/25415/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c0b64f36b36710dc765734ed12399f195c7d321
--- /dev/null
+++ b/marked/Rel-11/25_series/25415/raw.md
@@ -0,0 +1,2140 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 9 |
+| 3.3 Concepts..... | 9 |
+| 3.4 Specification Notations ..... | 10 |
+| 4 General..... | 10 |
+| 4.1 General aspects..... | 10 |
+| 4.2 Operational and Functional Aspects ..... | 11 |
+| 4.2.1 Iu UP protocol modes of operation ..... | 11 |
+| 4.2.2 Transparent mode (TrM)..... | 11 |
+| 4.2.3 Support mode..... | 12 |
+| 5 Transparent mode, version 1 ..... | 13 |
+| 5.1 General ..... | 13 |
+| 5.1.1 Operation of the Iu UP in Transparent mode ..... | 13 |
+| 5.1.2 Interfaces of the Iu UP protocol layer in Transparent mode ..... | 13 |
+| 5.2 Iu UP Protocol layer Services in Transparent mode ..... | 14 |
+| 5.3 Services Expected from the UP Data Transport layer..... | 14 |
+| 5.4 Elements for Iu UP communication in Transparent mode..... | 14 |
+| 5.4.1 Frame Format for transparent mode ..... | 14 |
+| 6 Support mode for predefined SDU sizes, version 2 ..... | 14 |
+| 6.1 General ..... | 14 |
+| 6.1.1 Operation of the Iu UP in Support mode ..... | 14 |
+| 6.1.2 Interfaces of the Iu UP protocol layer in Support mode..... | 15 |
+| 6.2 Iu UP Protocol layer Services in Support mode..... | 15 |
+| 6.3 Services Expected from the UP Data Transport layer..... | 15 |
+| 6.4 Functions of the Iu UP Protocol Layer in Support mode ..... | 16 |
+| 6.4.1 Functional model of the Iu UP Protocol Layer in Support mode ..... | 16 |
+| 6.4.2 Frame Handler function..... | 16 |
+| 6.4.3 Procedure Control functions..... | 16 |
+| 6.4.4 Non Access Stratum Data Streams specific function(s)..... | 17 |
+| 6.4.4.1 Frame Quality Classification function..... | 17 |
+| 6.4.4.1.1 General ..... | 17 |
+| 6.4.4.1.2 Handling of FQC information in uplink path..... | 17 |
+| 6.4.4.1.3 Handling of FQC information in downlink path..... | 18 |
+| 6.5 Elementary procedures ..... | 18 |
+| 6.5.1 Transfer of User Data procedure ..... | 18 |
+| 6.5.1.1 Successful operation ..... | 18 |
+| 6.5.1.2 Unsuccessful operation ..... | 19 |
+| 6.5.2 Initialisation procedure ..... | 20 |
+| 6.5.2.1 Successful operation ..... | 20 |
+| 6.5.2.2 Unsuccessful operation ..... | 22 |
+| 6.5.3 Iu Rate Control procedure ..... | 22 |
+| 6.5.3.1 Successful operation ..... | 22 |
+| 6.5.3.2 Unsuccessful operation..... | 23 |
+| 6.5.3.2A Frequent Rate Control Procedures ..... | 24 |
+| 6.5.4 Time Alignment procedure..... | 25 |
+| 6.5.4.1 Successful operation ..... | 25 |
+| 6.5.4.2 Unsuccessful operation ..... | 26 |
+| 6.5.5 Handling of Error Event procedure ..... | 27 |
+| 6.5.5.1 Successful operation ..... | 27 |
+| 6.5.5.2 Unsuccessful operation ..... | 27 |
+| 6.5.6 Frame Quality Classification procedure..... | 28 |
+
+| | | |
+|-----------|------------------------------------------------------------------------|----|
+| 6.6 | Elements for Iu UP communication in Support mode ..... | 28 |
+| 6.6.1 | General ..... | 28 |
+| 6.6.2 | Frame Format for predefined size SDUs..... | 29 |
+| 6.6.2.1 | PDU Type 0 ..... | 29 |
+| 6.6.2.2 | PDU Type 1 ..... | 30 |
+| 6.6.2.3 | PDU Type 14 ..... | 31 |
+| 6.6.2.3.1 | General ..... | 31 |
+| 6.6.2.3.2 | Positive Acknowledgement..... | 32 |
+| 6.6.2.3.3 | Negative Acknowledgement ..... | 33 |
+| 6.6.2.3.4 | Procedures Coding ..... | 34 |
+| 6.6.3 | Coding of information elements in frames ..... | 37 |
+| 6.6.3.1 | PDU Type ..... | 37 |
+| 6.6.3.2 | Ack/Nack ..... | 37 |
+| 6.6.3.3 | Frame Number ..... | 38 |
+| 6.6.3.4 | PDU Type 14 Frame Number..... | 38 |
+| 6.6.3.5 | Frame Quality Classification (FQC)..... | 38 |
+| 6.6.3.6 | RAB sub-Flow Combination Indicator (RFCI) ..... | 39 |
+| 6.6.3.7 | Procedure Indicator..... | 39 |
+| 6.6.3.8 | Header CRC..... | 39 |
+| 6.6.3.9 | Payload CRC..... | 39 |
+| 6.6.3.10 | Chain Indicator ..... | 39 |
+| 6.6.3.11 | Number of Subflows per RFCI..... | 39 |
+| 6.6.3.12 | Length Indicator (LI) ..... | 39 |
+| 6.6.3.13 | Number of RFCI Indicators ..... | 40 |
+| 6.6.3.14 | RFCI n Indicator ..... | 40 |
+| 6.6.3.15 | Error distance..... | 40 |
+| 6.6.3.16 | Error Cause value..... | 40 |
+| 6.6.3.17 | Padding ..... | 41 |
+| 6.6.3.18 | Time alignment..... | 41 |
+| 6.6.3.19 | Spare ..... | 41 |
+| 6.6.3.20 | Spare extension ..... | 41 |
+| 6.6.3.21 | LRI, Last RFCI Indicator..... | 41 |
+| 6.6.3.22 | Length of subflow ..... | 42 |
+| 6.6.3.23 | TI..... | 42 |
+| 6.6.3.24 | IPTI of n th RFCI..... | 42 |
+| 6.6.3.25 | Iu UP Mode versions supported..... | 42 |
+| 6.6.3.26 | Iu UP Mode Version..... | 42 |
+| 6.6.3.27 | Payload fields..... | 42 |
+| 6.6.3.28 | Data PDU type ..... | 43 |
+| 6.6.4 | Timers ..... | 43 |
+| 6.6.5 | Maximum values of repetition counters ..... | 43 |
+| 6.7 | Handling of unknown, unforeseen and erroneous protocol data..... | 43 |
+| 6.7.1 | General ..... | 43 |
+| 6.7.2 | Error detected by Iu UP functions ..... | 44 |
+| 6.7.3 | Request by upper layers..... | 44 |
+| 6.7.4 | Error event frame over the Iu UP protocol ..... | 44 |
+| 6.7.5 | Handling of error reports ..... | 44 |
+| 6.7.5.1 | General..... | 44 |
+| 6.7.5.2 | Error distance..... | 45 |
+| 6.7.6 | List of errors in Iu UP ..... | 46 |
+| 6.7.7 | Error detection ..... | 47 |
+| 6.7.7.1 | General..... | 47 |
+| 6.7.7.2 | CRC Calculation..... | 47 |
+| 6.7.7.3 | Relation between input and output of the Cyclic Redundancy Check ..... | 47 |
+| 7 | Communication Primitives for the Iu UP protocol layer ..... | 48 |
+| 7.1 | Modelling Principle..... | 48 |
+| 7.2 | Primitives towards the upper layers at the RNL SAP ..... | 48 |
+| 7.2.1 | General ..... | 48 |
+| 7.2.2 | Iu-UP-DATA-REQUEST..... | 49 |
+| 7.2.3 | Iu-UP-DATA-INDICATION ..... | 50 |
+| 7.2.4 | Iu-UP-STATUS-REQUEST..... | 50 |
+
+| | | |
+|-------------------------------|----------------------------------------------------------------------|-----------|
+| 7.2.5 | Iu-UP-STATUS-INDICATION ..... | 50 |
+| 7.2.6 | Iu-UP-UNIT-DATA-REQUEST ..... | 50 |
+| 7.2.7 | Iu-UP-UNIT-DATA-INDICATION ..... | 50 |
+| 7.3 | Primitives towards the transport layers at TNL SAP ..... | 50 |
+| 7.3.1 | General ..... | 50 |
+| 7.3.2 | ATM/AAL2 based Transport layer ..... | 50 |
+| 7.3.2.1 | General ..... | 50 |
+| 7.3.2.2 | AAL2 Service Primitives used by the Iu UP protocol ..... | 51 |
+| 7.3.3 | GTP-U based Transport Layer ..... | 51 |
+| 7.3.3.1 | General ..... | 51 |
+| 7.3.3.2 | Generic Service Primitives used by the Iu UP protocol ..... | 51 |
+| 7.3.4 | RTP based Transport Layer ..... | 51 |
+| 7.3.4.1 | General ..... | 51 |
+| 7.3.4.2 | Generic Service Primitives used by the Iu UP protocol ..... | 51 |
+| 8 | Evolution of Iu UP Protocol ..... | 52 |
+| 8.1 | Principles for Protocol Evolution ..... | 52 |
+| 8.1.1 | Unknown field value ..... | 52 |
+| 8.1.2 | Adding a new field to an existing frame ..... | 53 |
+| 8.1.3 | Adding a new PDU type ..... | 53 |
+| 8.1.4 | Protocol version handling ..... | 53 |
+| Annex A (informative): | Illustration of usage of RFCI for AMR speech RAB ..... | 55 |
+| Annex B (informative): | Illustration of protocol states in the Iu UP ..... | 58 |
+| B.1 | Protocol state model for transparent mode ..... | 58 |
+| B.1.1 | Null State ..... | 58 |
+| B.1.2 | Transparent Mode Data Transfer Ready State ..... | 58 |
+| B.2 | Protocol state model for support mode for predefined SDU sizes ..... | 59 |
+| B.2.1 | Null State ..... | 59 |
+| B.2.2 | Initialisation State ..... | 59 |
+| B.2.3 | Support Mode Data Transfer Ready State ..... | 60 |
+| Annex C (informative): | Open Issues of the Iu UP ..... | 61 |
+| Annex D (informative): | Distributed rate decision within RNC ..... | 62 |
+| Annex E (informative): | Change History ..... | 63 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document defines the Radio Network Layer user plane protocol being used over the Iu 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.401: "UTRAN Overall Description".
+- [2] 3GPP TS 25.410: "UTRAN Iu interface: General Aspects and Principles".
+- [3] 3GPP TS 25.413: "UTRAN Iu interface RANAP Signalling".
+- [4] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling".
+- [5] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions".
+- [6] Void
+- [7] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation Layer specification: Type 2 AAL".
+- [8] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and reassembly service specific convergence sublayer for the AAL type 2".
+- [9] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [10] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification".
+- [11] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification".
+- [12] 3GPP TS 26.102: "Mandatory speech codec; AMR speech codec; Interface to Iu and Uu".
+- [13] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2".
+- [14] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications".
+- [15] IETF RFC 1890 (1996-01): "RTP Profile for Audio and Video Conferences with Minimal Control".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Iu Timing Interval (ITI):** Iu Timing Interval is the minimum time interval between sent Iu UP PDUs for a specific RAB. The ITI can be calculated for conversational and streaming traffic classes by the following formula:
+
+$$ITI = \frac{MaxSDUsize}{MaxBitrate}$$
+
+**Inter PDU Transmission Interval (IPTI):** inter PDU Transmission Interval is the actual interval at which Iu UP PDUs can be sent at a certain time for a specific RAB subflow combination. The IPTI of a RAB subflow combination is calculated based on the RAB subflow combination size and the RAB subflow combination bitrate by dividing the RAB subflow combination size with the RAB subflow combination bitrate.
+
+$$IPTI_g = \frac{RFC\_size_g}{RFC\_Bitrate_g}, \quad g = 1, \dots, n, \quad n = \text{number of subflow combinations}$$
+
+NOTE: If *RFC\_Bitrate* is not defined then *IPTI=ITI*. If *RFC\_size* is not defined then *RFC\_size=MaxSDUsize*.
+
+**Non Access Stratum (NAS) Data Streams:** non Access Stratum Data Streams is a generic term to identify these data streams exchanged at the Dedicated Service Access Points between the Non Access Stratum and the Access Stratum.
+
+**RAB sub-flows:** RAB as defined in TR 21.905 [9] is realised by UTRAN through one to several sub-flows. These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes.
+
+### **RAB sub-flows characteristics:**
+
+- 1) the sub-flows of a RAB are established and released together at the RAB establishment and release, respectively;
+- 2) the sub-flows of a RAB are submitted and delivered together at the RAB SAP;
+- 3) the sub-flows of a RAB are carried over the same Iu transmission connection;
+- 4) the sub-flows of a RAB are organised in a predefined manner at the RAB SAP and over the Iu interface. The organisation is imposed by the NAS as part of its co-ordination responsibility.
+
+### **RAB sub-flows numbering (applies to support mode for predefined SDU size only):**
+
+- 1) RAB sub-flows are numbered from 1 to N (N is the number of sub-flows);
+- 2) RAB sub-flow number 1 corresponds to the highest reliability class and the RAB sub-flow number N corresponds to the lowest reliability class;
+- 3) RAB sub-flows order inside the Iu frame is predefined so that RAB sub-flow number one comes first and the RAB sub-flow number N comes last.
+
+**RAB sub-Flow Combination (RFC):** RAB sub-flow combination is defined as an authorised combination of the RAB sub-flows variable attributes (e.g. SDU sizes) of currently valid RAB sub-flows that can be submitted simultaneously to the Iu UP for transmission over Iu interface. Each combination is given by the CN and cannot be altered by the SRNC.
+
+**RAB sub-Flow Combination Indicator (RFCI):** this indicator uniquely identifies a RAB sub-flow combination for the duration of the Iu UP peer protocol instances i.e. it is valid until the termination of the call or until a new initialisation is performed. Usage of RFCI applies only to Iu UP protocol operated in support mode for predefined SDU size.
+
+### **Principles related to RFCI allocation and Initialisation procedure:**
+
+- 1) RFCI value is present in every Iu user frame;
+- 2) in the Initialisation procedure in Iu UP, the size of every RAB sub-flow SDU for each RFCI is signalled.
+
+**Syntactical error:** field is defined to be syntactically incorrect in a frame if it contains at least one value defined as "reserved", or if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical error that a value specified as "spare" is being used.
+
+**Semantical error:** A frame is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|--------|----------------------------------------------|
+| AMR | Adaptive Multi-Rate codec |
+| AS | Access Stratum |
+| BER | Bit Error Rate |
+| CN | Core Network |
+| DTX | Discontinuous Transmission |
+| DU | Data Unit |
+| GF | Galois Field |
+| IPTI | Inter PDU Transmission Interval |
+| ITI | Iu Timing Interval |
+| NAS | Non Access Stratum |
+| PDU | Protocol Data Unit |
+| QoS | Quality of Service |
+| RAB | Radio Access Bearer |
+| RANAP | Radio Access Network Application Part |
+| RFC | RAB sub Flow Combination |
+| RFCI | RFC Indicator |
+| RNL | Radio Network Layer |
+| RTP | Real-time Transport Protocol |
+| SAP | Service Access Point |
+| SDU | Service Data Unit |
+| SID | Silence Insertion Descriptor |
+| SMpSDU | Support Mode for predefined SDU size |
+| SRNC | Serving RNC |
+| SRNS | Serving RNS |
+| SSSAR | Service Specific Segmentation and Reassembly |
+| TFCI | Transport Format Combination Indicator |
+| TFI | Transport Format Identification |
+| TFO | Tandem Free Operation |
+| TNL | Transport Network Layer |
+| TrFO | Transcoder Free Operation |
+| TrM | Transparent Mode |
+| UP | User Plane |
+| UUI | User to User Information |
+
+## 3.3 Concepts
+
+### **Iu UP mode of operation:**
+
+One objective of the Iu User Plane (UP) protocol is to remain independent of the CN domain (Circuit Switched or Packet Switched) and to have limited or no dependency with the Transport Network Layer. Meeting this objective provides the flexibility to evolve services regardless of the CN domain and to migrate services across CN domains.
+
+The Iu UP protocol is therefore defined with modes of operation that can be activated on a RAB basis rather than on a CN domain basis or (tele) service basis. The Iu UP mode of operation determines if and which set of features shall be provided to meet e.g. the RAB QoS requirements.
+
+### **Iu UP protocol PDU Type:**
+
+The Iu UP protocol PDU Types are defined for a given Iu UP mode of operation. An Iu UP PDU Type represents a defined structure of an Iu UP protocol frame. For instance, a frame made of a certain Frame Header mask part and a Frame Payload part would be specified as a certain PDU type valid for a given Iu UP mode of operation.
+
+### **Tandem Free Operation (TFO):**
+
+Configuration of a Speech or Multimedia call for which Transcoders are physically present in the communication path but transcoding functions are disabled or partially disabled. The Transcoders may perform control and/or protocol conversion functions.
+
+### **Transcoder (TC):**
+
+Physical device present in the network responsible for the transcoding of the speech data between two speech codecs or coding schemes (The Transcoder may also include other functions, i.e. Rate Adaptation in GSM).
+
+### **Transcoder Free Operation (TrFO):**
+
+Configuration of a Speech or Multimedia call for which Transcoders are not present in the communication path.
+
+## 3.4 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. Iu Rate Control procedure. |
+| 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. TIME ALIGNMENT control frame. |
+| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Frame Number IE. |
+| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 6.6.3 enclosed by quotation marks, e.g. "0" or "255". |
+
+# --- 4 General
+
+## 4.1 General aspects
+
+The Iu UP protocol is located in the User plane of the Radio Network layer over the Iu interface: the Iu UP protocol layer.
+
+The Iu UP protocol is used to convey user data associated to Radio Access Bearers.
+
+One Iu UP protocol instance is associated to one RAB and one RAB only. If several RABs are established towards one given UE, then these RABs make use of several Iu UP protocol instances.
+
+In general, Iu UP protocol instances exist at Iu access point as defined in TS 25.410 [2] i.e. at CN and UTRAN. However, as described in TS 23.153 [13], if TrFO is possible and the Iu UP protocol instances operate in support mode the Iu UP protocol instance in CN may resume performing Iu UP specific functions or vanish completely during stable call states. In this case the partner peer entity actually interacting with the UTRAN Iu UP protocol instance (i.e. performing all Iu UP specific functions except UP initialisation) may either be located within another UTRAN or within a CN node that is not the serving CN node of the UTRAN.
+
+Whenever a RAB requires transfer of user data in the Iu UP, an Iu UP protocol instance exists at each Iu interface access points. These Iu UP protocol instances are established, relocated and release together with the associated RAB.
+
+Whether these peer protocol instances perform some RAB related function depends on the mode of operation of the Iu UP as defined below.
+
+The following figure illustrates the logical placement of the Iu UP protocol layer and the placement of the Data Streams sources outside of the Access Stratum.
+
+
+
+Figure 1: Iu UP protocol layer occurrence in UTRAN overall architecture (User Plane View). The diagram shows the protocol stack for the User Plane across three entities: UE, UTRAN, and CN. The UE contains NAS Data Streams, Radio protocols, and a Radio (Uu) interface. The UTRAN contains Radio protocols, Iu UP, User plane Data Bearers protocols, and a Transport Layer. The CN contains NAS Data Streams, Iu UP, User plane Data Bearers protocols, and a Transport Layer. The Iu UP layer is highlighted in the UTRAN and CN. The diagram is divided into Non-Access Stratum (NAS) and Access Stratum (AS).
+
+Figure 1: Iu UP protocol layer occurrence in UTRAN overall architecture (User Plane View)
+
+## 4.2 Operational and Functional Aspects
+
+### 4.2.1 Iu UP protocol modes of operation
+
+The Iu UP protocol operates in mode according to the concept described in earlier subclause.
+
+Modes of operation of the protocol are defined:
+
+- 1) Transparent mode (TrM);
+- 2) Support mode for predefined SDU size (SMpSDU).
+
+Determination of the Iu UP protocol instance mode of operation is a CN decision taken at RAB establishment based on e.g. the RAB characteristics. It is signalled in the Radio Network layer control plane at RAB assignment and relocation for each RAB. It is internally indicated to the Iu UP protocol layer at user plane establishment.
+
+The choice of a mode is bound to the nature of the associated RAB and cannot be changed unless the RAB is changed.
+
+### 4.2.2 Transparent mode (TrM)
+
+The transparent mode is intended for those RABs that do not require any particular feature from the Iu UP protocol other than transfer of user data.
+
+The following figure illustrates the transparent mode of operation of the Iu UP protocol layer.
+
+
+
+Figure 2: Iu UP protocol layer in transparent occurrence over Iu interface. The diagram shows the UTRAN and CN connected via the Iu Interface. In the UTRAN, data flows from the Radio Interface Protocols through the 'Iu UP layer in transparent mode' to the TNL-SAP. In the CN, data flows from the Non Access Stratum (NAS) through the RNL-SAP, then through the 'Iu UP layer in transparent mode' to the TNL-SAP. A thick grey arrow indicates the end-to-end data transfer across the Iu Interface, bypassing the Iu UP layer's protocol functions.
+
+**Figure 2: Iu UP protocol layer in transparent occurrence over Iu interface**
+
+In this mode, the Iu UP protocol instance does not perform any Iu UP protocol information exchange with its peer over the Iu interface: no Iu frame is sent. The Iu UP protocol layer is crossed through by PDUs being exchanged between upper layers and transport network layer.
+
+For instance, the transfer of GTP-U PDUs could utilise the transparent mode of the Iu UP protocol.
+
+This release of the specification defines transparent mode version 1, the same as in the release 99 specification.
+
+### 4.2.3 Support mode
+
+The support modes are intended for those RABs that do require particular features from the Iu UP protocol in addition to transfer of user data. When operating in a support mode, the peer Iu UP protocol instances exchange Iu UP frames whereas in transparent mode, no Iu UP frames are generated.
+
+The following figure illustrates the functional model of the Iu UP protocol layer in support mode of operation.
+
+
+
+Figure 3: Iu UP protocol layer in support mode occurrence over Iu interface. The diagram shows the UTRAN and CN connected via the Iu Interface. In the UTRAN, data flows from the Radio Interface Protocols through the 'Iu UP layer in support mode' (containing 'Support Mode Functions') to the TNL-SAP. In the CN, data flows from the Non Access Stratum (NAS) through the RNL-SAP, then through the 'Iu UP layer in support mode' (containing 'Support Mode Functions') to the TNL-SAP. A thick grey arrow shows data transfer across the Iu Interface. A horizontal double-headed arrow between the 'Support Mode Functions' in the UTRAN and CN is labeled 'Transfer of Iu UP protocol frames', indicating bidirectional protocol exchange.
+
+**Figure 3: Iu UP protocol layer in support mode occurrence over Iu interface**
+
+Some RABs requesting Iu UP protocol support, constrain the Iu UP protocol and possibly the radio interface protocols in specific ways. For instance, certain RABs can have variable predefined rates.
+
+The Iu UP support mode is prepared to support variations.
+
+The only support mode defined here is the:
+
+- Support mode for predefined SDU size (SMpSDU).
+
+For instance, the transfer of AMR speech PDUs would utilise the support mode for predefined SDU size of the Iu UP protocol because it requires some Procedure Control functions and some NAS Data Streams specific functions while the sizes of the user data being transferred can vary in a predefined manner.
+
+This release of the specification defines the Support mode for predefined SDU sizes version 2. The Support mode for predefined SDU sizes version 1 (see release 99 of this specification) shall also be supported by a 3GPP implementation compliant to this release of the specification in order to be backward compatible with release 99.
+
+# --- 5 Transparent mode, version 1
+
+## 5.1 General
+
+### 5.1.1 Operation of the Iu UP in Transparent mode
+
+The Iu UP layer in transparent mode is present in the Iu User plane for transferring data transparently over the Iu interface.
+
+The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Streams transfer.
+
+### 5.1.2 Interfaces of the Iu UP protocol layer in Transparent mode
+
+Interfaces of the Iu UP protocol layer in transparent mode are the transport network layer and the upper layers. The Iu UP protocol layer in transparent mode is an empty layer through which NAS Data Streams PDUs are crossing between the Transport Network Layer and upper layers.
+
+The Iu UP protocol layer in transparent mode is using services of the Transport layers in order to transfer the Iu UP PDUs over the Iu interface.
+
+## 5.2 Iu UP Protocol layer Services in Transparent mode
+
+The following functions are needed to support this mode:
+
+- Transfer of user data.
+
+## 5.3 Services Expected from the UP Data Transport layer
+
+The Iu UP protocol layer in transparent mode expects the following services from the Transport Network Layer:
+
+- Transfer of user data.
+- Delivery of SDUs in sequence when requested by the RAB parameter *Delivery Order* IE (TS 25.413 [3]).
+
+## 5.4 Elements for Iu UP communication in Transparent mode
+
+### 5.4.1 Frame Format for transparent mode
+
+The following shows the format of the PDU crossing the Iu UP protocol layer in transparent mode. This frame is transferred transparently between the Iu UP protocol upper layers and transport network layer (TNL-SAP).
+
+
+
+Figure 4: Frame format for transparent mode. A rectangular box labeled 'Payload' is shown. To the right of the box, there is a vertical ellipsis of five dots. Above the ellipsis is the text 'Oct 1' and below it is 'Oct n', indicating the variable length of the payload in octets.
+
+**Figure 4: Frame format for transparent mode**
+
+This PDU has a variable length of n octets, whose maximum range depends on the type of user data (e.g. IP packet). No explicit length indication is visible at the Iu UP protocol layer.
+
+# 6 Support mode for predefined SDU sizes, version 2
+
+## 6.1 General
+
+### 6.1.1 Operation of the Iu UP in Support mode
+
+The Iu UP protocol layer in Support mode is present for data streams that need frame handling in the UP.
+
+The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Streams transfer.
+
+### 6.1.2 Interfaces of the Iu UP protocol layer in Support mode
+
+As part of the Access Stratum responsibility, the Iu UP protocol layer in support mode provides the services and functions that are necessary to handle non access stratum data streams. The Iu UP protocol layer in support mode is providing these services to the UP upper layers through a Dedicated Service Access Point used for Information Transfer as specified in TS 23.110 [5].
+
+The Iu UP protocol layer in support mode is using services of the Transport layers in order to transfer the Iu UP PDUs over the Iu interface.
+
+## 6.2 Iu UP Protocol layer Services in Support mode
+
+### Support mode for predefined SDU size Service
+
+The following functions are needed to support this mode:
+
+- Transfer of user data;
+- Initialisation;
+- Rate control;
+- Time alignment;
+- Handling of error event;
+- Frame quality classification.
+
+## 6.3 Services Expected from the UP Data Transport layer
+
+The Iu UP protocol layer in Support Mode expects the following services from the Transport Network Layer:
+
+- Transfer of user data.
+- Delivery of SDUs in sequence when requested by the RAB parameter *Delivery Order* IE (TS 25.413 [3]).
+
+## 6.4 Functions of the Iu UP Protocol Layer in Support mode
+
+### 6.4.1 Functional model of the Iu UP Protocol Layer in Support mode
+
+
+
+Figure 5: Functional model of the Iu UP protocol layer in Support mode. The diagram shows the functional architecture of the Iu UP layer between UTRAN and CN. On the UTRAN side, the Iu UP layer in support mode consists of three main functional blocks: NAS Data Streams specific functions, Procedure Control functions, and a Frame Handler function. These are connected to Radio Interface Protocols and a TNL-SAP. On the CN side, the Iu UP layer in support mode has similar functional blocks (NAS Data Streams specific functions, Procedure Control functions, and a Frame Handler function) connected to an RNL-SAP and a TNL-SAP. The RNL-SAP is further divided into Non Access Stratum and Access Stratum. Arrows indicate the flow of data and control signals between these components and the Iu Interface.
+
+**Figure 5: Functional model of the Iu UP protocol layer in Support mode**
+
+The Iu UP protocol layer in Support mode is made of three sets of functions:
+
+- 1) Frame Handler function;
+- 2) Procedure Control functions;
+- 3) Non Access Stratum Data Streams specific functions.
+
+### 6.4.2 Frame Handler function
+
+This function is responsible for framing and de-framing the different parts of an Iu UP protocol frame. This function takes the different parts of the Iu UP protocol frame and set the control part field to the correct values, including the handling of the frame number. It also ensures that the frame control part is semantically correct. This function is responsible for interacting with the Transport layers. This function is also responsible for the CRC check of the Iu UP frame header. The Iu UP frame with header CRC check error is discarded.
+
+### 6.4.3 Procedure Control functions
+
+This set of functions offers the control of a number of procedures handled at the Iu UP protocol level. These functions are responsible for the procedure control part of the Iu UP frames.
+
+Namely, these procedures are:
+
+- **Rate Control:** is the procedure which controls over the Iu UP the maximum rate that is allowed to be sent downlink among the rates that can be controlled. The set of rates is represented by RFCI indicators. The function controlling this procedure interacts with functions outside of the Iu UP protocol layer.
+- **Initialisation:** is the procedure which controls the exchange of initialisation information that is required for operation in support mode for predefined SDU size. Such information can contain the RFCI Set to be used until termination of the connection or until the next Initialisation procedure. This procedure is also used for negotiating the version of the Iu UP Mode among the versions the CN requested for the related RAB.
+- **Time Alignment:** is the procedure that controls the timing of the downlink data to the RNC over Iu. The function controlling this procedure interacts with functions outside of the Iu UP protocol layer.
+
+- **Handling of Error Event:** is the procedure that controls the information exchanged over the Iu related to detection of a fault situation. The function controlling this procedure interacts with functions outside of the Iu UP protocol layer.
+
+### 6.4.4 Non Access Stratum Data Streams specific function(s)
+
+These functions are responsible for a "limited manipulation" of the payload. These functions are responsible for the CRC check and calculation of the Iu UP frame payload part. These functions are also responsible for the Frame Quality Classification handling as described below.
+
+These functions interact with the upper layers by exchanging Iu data stream blocks of Iu UP frame payload. These functions also handle the padding and depadding of the Iu UP frame payloads when needed.
+
+These functions interact with the Procedure Control functions.
+
+These functions provide service access to the upper layers for the Procedure Control functions.
+
+#### 6.4.4.1 Frame Quality Classification function
+
+##### 6.4.4.1.1 General
+
+On the Iu UP in Support Mode the frames are classified with the Frame Quality Classifier (FQC). This classifying is based on the radio frame classification and the setting of the RAB attribute *Delivery of erroneous SDU* IE. The RAB attribute *Delivery of erroneous SDU* IE tells if erroneous frames shall be delivered or not.
+
+Figure 6 shows the main input and output information for frame quality classification function on the Iu UP.
+
+
+
+Figure 6: Frame quality classification in Iu UP. This diagram illustrates the data flow and processing within the Iu Interface between the UTRAN and the CN. On the UTRAN side, data from Radio Interface Protocols is processed through 'Radio frame classification' and 'Support Mode Functions'. The 'Support Mode Functions' output 'PDU or no PDU As a result of FQC AND CRC' to the RNL-SAP. The RNL-SAP is located at the boundary between the 'Access Stratum' and 'Non Access Stratum'. Data from the 'Non Access Stratum' is sent to the CN's 'Support Mode Functions' via the RNL-SAP. The CN's 'Support Mode Functions' output 'Frame Quality Classification Result of FQC AND CRC results' to its RNL-SAP. Both UTRAN and CN have a 'Transfer of Iu UP protocol frames' block. At the bottom, the TNL-SAP is shown on both sides, with a large grey arrow indicating data transfer between them. The Iu Interface is shown at the top, connecting the UTRAN and CN.
+
+**Figure 6: Frame quality classification in Iu UP**
+
+##### 6.4.4.1.2 Handling of FQC information in uplink path
+
+###### 6.4.4.1.2.1 Handling of FQC information at RNC
+
+In SRNC on the sending side, the Support Mode Functions takes as input the radio frame quality information together with the frame. Based on this, the *Frame Quality Classification (FQC)* IE is set for the frame, a CRC is or is not added (depending on PDU type) and the frame is sent to CN. The following steps shall be sequentially applied to derive the SRNC behaviour and the *Frame Quality Classification (FQC)* IE setting:
+
+- If there is at least one subflow with the *Delivery of erroneous SDU* IE set to "No" and for at least one of those subflows the radio frame classification is "Bad" then the Iu UP frame shall not be sent;
+
+- b) Otherwise, if there is at least one subflow with the *Delivery of erroneous SDU* IE set to "Yes" and for at least one of those subflows the radio frame classification is "Bad" then the Iu UP frame shall be sent with *Frame Quality Classification (FQC)* IE set to "frame bad due to radio";
+- c) Otherwise the Iu UP frame shall be sent with *Frame Quality Classification (FQC)* IE set to "frame good".
+
+###### 6.4.4.1.2.2 Handling of FQC information at CN
+
+The Support Mode Functions in CN on the receiving side makes a CRC check of the frame payload, if CRC is present and passes the appropriate frame and the appropriate frame quality classification information through the RNL-SAP. The following steps shall be sequentially applied to derive the CN behaviour and the FQC field setting:
+
+- a) If a CRC is available and the CRC check indicates that the Iu UP frame payload part is corrupted and at least one subflow has the *Delivery of erroneous SDU* IE set to "No", then the Iu UP frame shall be dropped;
+- b) Otherwise, if a CRC is available and the CRC check indicates that the Iu UP frame payload part is corrupted and at least one subflow has the *Delivery of erroneous SDU* IE set to "Yes", then the Iu UP frame shall be forwarded with the FQC set to "frame bad";
+- c) Otherwise the Iu UP frame shall be forwarded with the FQC as set by UTRAN.
+
+##### 6.4.4.1.3 Handling of FQC information in downlink path
+
+The Support Mode Functions in CN on the sending side adds a CRC, if necessary to the frame payload and passes it together with the FQC. If the payload stems from a transcoding unit of the NAS within the CN the FQC is always set to "frame good". Otherwise it may be set by a partner peer entity residing in another RNC.
+
+The Support Mode Functions in SRNC then makes a CRC-check, if the CRC is present. Based on the CRC check, a decision is made whether to deliver the frame or not based on the following sequential steps:
+
+- a) If a CRC is available and the CRC check indicates that the Iu UP frame payload part is corrupted then the frame shall be dropped;
+- b) Otherwise, if the FQC value of the Iu UP frame is set to "frame bad" or "frame bad due to radio" then the frame shall be dropped, regardless of the CRC check indication;
+- c) Otherwise, the frame shall be passed to radio interface protocols.
+
+NOTE: The case where SRNC receives a frame with the FQC set to "frame bad due to radio" (respectively: "frame bad"), corresponds to a TrFO (respectively: TFO) case. The frame is then trashed by the receiving RNC since there is currently no means to pass the frame quality indicator down to the UE.
+
+## 6.5 Elementary procedures
+
+### 6.5.1 Transfer of User Data procedure
+
+#### 6.5.1.1 Successful operation
+
+The purpose of the Transfer of User Data procedure is to transfer Iu UP frames between the two Iu UP protocol layers at both ends of the Iu interface. Since an Iu UP instance is associated to a RAB and a RAB only, the user data being transferred only relate to the associated RAB.
+
+The procedure is controlled at both ends of the Iu UP instance i.e. SRNC and the CN. Exceptions in case of TrFO, where the partner peer entity does not reside within the serving CN node are described in subclause 4.1 and TS 23.153 [13].
+
+The Transfer of User Data procedure is invoked whenever user data for that particular RAB needs to be sent across the Iu interface.
+
+The procedure is invoked by the Iu UP upper layers upon reception of the upper layer PDU and associated control information: RFCI.
+
+The upper layers may deliver a frame quality classification information together with the RFCI.
+
+The NAS Data Streams specific functions makes the padding of the payload (if needed) so that the Iu UP frame payload
+
+will be an integer number of octets. Then the NAS Data Streams specific functions perform, if needed, CRC calculation of the Iu frame payload and passes the Iu UP frame payload down to the Frame Handler function together with the RFCI.
+
+The Frame Handler function retrieves the frame number from its internal memory, formats the frame header and frame payload into the appropriate PDU Type and sends the Iu UP frame PDU to the lower layers for transfer across the Iu interface. If the UTRAN initialises the RAB it shall base the selection of the PDU type (in both directions) on the reliability attributes (see TS 25.413 [3]) for the RAB. If the reliability attribute *Delivery of Erroneous SDU* IE equals "no-error-detection-consideration" for all subflows then PDU Type 1 shall be used, otherwise PDU Type 0 shall be used.
+
+For RABs with the traffic class conversational or streaming the frame number shall be based on time (stepped at each ITI). For RABs with another type of traffic class the frame numbering shall be based on sent Iu UP PDU (stepped at each sent Iu UP PDU). See description of *Frame Number* IE.
+
+Upon reception of a user data frame, the Iu UP protocol layer checks the consistency of the Iu UP frame as follows:
+
+- The Frame Handler function checks the consistency of the frame header and the consistency of the frame number. If a frame loss is detected due a gap in the sequence of the received frame numbers (for a RAB where frame numbers does not relate to time), this shall be reported to the Procedure Control function. If correct, the Frame Handler function stores the frame number and passes the Iu UP frame payload and associated CRC, if any to the NAS Data Streams specific functions. The received RFCI is passed to the Procedure Control function;
+- The NAS Data Streams specific functions check the payload CRC, if any. If the RFCI is correct (i.e. RFCI is used at Initialisation) and matches the Iu UP frame payload (i.e. frame payload is not too short for the RFCI) as indicated by the Procedure Control functions, the NAS Data Streams specific functions removes the padding bits and the spare extension field when present from the Iu UP frame payload based on the RFCI information. Then the NAS Data Streams specific functions forwards to the upper layers the RFCI and the payload.
+
+
+
+Diagram illustrating successful transfers of user data between RNC/CN and CN/RNC. The diagram shows two vertical lines representing the RNC/CN (left) and CN/RNC (right) entities. Horizontal arrows represent the transfer of user data (RFCI, payload) from left to right. There are four such arrows, with the top one labeled 'TRANSFER OF USER DATA (RFCI, payload)'. Below the arrows, there are two horizontal bars representing the ground or base of the entities.
+
+**Figure 7: Successful Transfers of User Data**
+
+#### 6.5.1.2 Unsuccessful operation
+
+If the Iu UP frame carrying the user data is incorrectly formatted or cannot be correctly treated by the receiving Iu UP protocol layer, the Iu UP protocol layer shall either discard the frame or pass it to the upper layers with a frame classification indicating a corrupted frame. This decision is based on configuration data of the Iu UP instance for that particular RAB (i.e. if the RAB requests delivery of corrupted frame).
+
+If the Iu UP protocol layer detects a frame loss because of a gap in the received frame number sequence while the frame number does not relate to time (see description of *Frame Number* IE), the receiving Iu UP protocol layer shall report this to the Procedure Control function.
+
+
+
+Figure 8: Unsuccessful Transfers of User Data. The diagram shows two vertical lifelines: RNC/CN on the left and CN/RNC on the right. A horizontal arrow labeled 'TRANSFER OF USER DATA (RFCI, payload)' points from RNC/CN to CN/RNC. Below this, a wavy line with a red lightning bolt symbol represents a corrupted frame, labeled '1)'. A second horizontal arrow points from RNC/CN to CN/RNC, but it is terminated with a large 'X' symbol, labeled '2)', representing a detected frame loss.
+
+**Figure 8: Unsuccessful Transfers of User Data: 1) Corrupted Frame, 2) Detection of Frame loss**
+
+### 6.5.2 Initialisation procedure
+
+#### 6.5.2.1 Successful operation
+
+This procedure is mandatory for RABs using the support mode for predefined SDU size. The purpose of the Initialisation procedure is to configure both termination points of the Iu UP with RAB Subflows Combinations, RFCIs, and associated RAB Sub Flows SDU sizes necessary to be supported during the transfer of user data phase.
+
+Additional parameters may also be passed, such as the Inter PDU Timing Interval (IPTI) information.
+
+The Initialisation procedure may be controlled at both end of the Iu access point, i.e. the CN and UTRAN.
+
+The Initialisation procedure is invoked whenever indicated by the Iu UP Procedure Control function e.g. as a result of a relocation of SRNS or at RAB establishment over Iu or if the CN decides to resolve RFCI mismatch in case of TrFO (see TS 23.153 [13]). The Initialisation procedure shall not be re-invoked by the SRNC for the RAB without a RAB modification requested via RANAP (TS 25.413 [3]).
+
+When this procedure is invoked all other Iu UP procedures are suspended until termination of the Initialisation procedure.
+
+The Iu UP protocol entity invoking this procedure shall indicate the Iu UP Mode version of the INITIALISATION control frame it uses in the Iu UP Mode Version field. It shall also indicate the Iu UP Mode versions it proposes among the versions the CN requested for the related RAB and which it supports in the Iu UP Mode Versions Supported field. The sender should use the lowest Iu UP Mode version for the initialisation that has enough information to initialise the highest proposed protocol version.
+
+The invoking entity allocates a RAB sub-Flow Combination indicator (RFCI) to each RAB sub-Flow Combination it initialises. One requirement on which RAB sub-Flow Combinations to initialise, is that all requested compound RAB sub-Flow Combination SDU sizes shall be configured, except in the case when also version 1 of the user plane mode was included as an alternative in the request over RANAP. In that case, it is allowed to initialise just a subset of the requested RAB sub-Flow Combinations, however at least one of the requested RAB sub-Flow Combinations equal or above the guaranteed bitrate shall be initialised. The association of indicators to RAB Flow Combinations is valid for both the uplink and downlink direction in the Iu UP until a new Initialisation procedure is performed or the connection is terminated.
+
+The Procedure Control function may also generate additional Iu UP protocol parameters necessary for the RAB service to operate properly over Iu.
+
+To each RAB sub-Flow combination indicator is associated the size of each RAB sub-Flow SDU of that combination. The list of RAB sub-Flow Combination Indicators and their respective SDU sizes constitutes the RAB sub-Flow Combination set passed over the Iu UP in the INITIALISATION control frame i.e. into an appropriate Iu UP PDU Type.
+
+The first RAB Sub-flow Combination proposed in the list of RAB Sub-Flow Combinations corresponds to the maximum bit rate allowed to be used when starting the communication phase i.e. until the first RATE CONTROL control frame occurs. The RAB Sub-flow Combinations for rates below the guaranteed bit rate as specified in the RAB parameters (indicated to the Iu-UP at the RNC) shall not be used as the first RAB Sub-flow Combination in the proposed list of RAB Sub-Flow Combinations.
+
+Any RAB Sub-Flow Combination of the set that is initialised shall be supported by the two Iu UP termination points and may optionally be used by the sender (except for the first in the list that shall be used when starting). In particular,
+
+the use by the sender of the RFC "NO\_DATA" is optional even when it is included in the Initialisation procedure.
+
+Conversely, any RAB Sub-Flow Combination that is not part of the initialised set shall not be used even if supported. In particular, the two Iu UP termination points shall be capable of operating without the use of the RFC "NO\_DATA".
+
+The complete set of information is framed by the Iu UP Frame Handler function and transferred in an Iu UP INITIALISATION control frame. If needed, the INITIALISATION control frame CRC is calculated and set accordingly in the respective frame field.
+
+A supervision timer $T_{INIT}$ is started after sending the Iu UP INITIALISATION control frame. This timer supervises the reception of the initialisation acknowledgement frame.
+
+Upon reception of a frame indicating that an Initialisation procedure is active in the peer Iu UP entity, the Iu UP protocol layer forwards the whole protocol information contained in the INITIALISATION control frame to the upper layers. It also stores the RAB sub-Flow Combination set (and thus replaces a possible previous set) in order to control during the transfer of user data, that the Iu UP payload is correctly formatted (e.g. RFCI matches the expected Iu UP frame payload total length). The peer Iu UP entity receiving the INITIALISATION control frame shall choose a version that it supports among the proposed versions indicated by the sender for which it has enough initialisation information.
+
+If the INITIALISATION control frame is correctly formatted and treated by the receiving Iu UP protocol layer, and at least one of the proposed versions is supported, this latter sends an INITIALISATION POSITIVE ACKNOWLEDGEMENT frame using the version of the Iu UP Mode that is chosen.
+
+Upon reception of an initialisation acknowledgement frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{INIT}$ .
+
+If the Initialisation procedure requires that several frames are to be sent, each frame shall be acknowledged individually (i.e. any frame to be sent shall wait for the acknowledgement of the previous sent frame to be received before being sent. The supervision timer shall be used individually for each frame being sent.
+
+The successful operation of the Initialisation procedure may require that one or several chained frames are positively acknowledged. The number of INITIALISATION control frames in such a chain shall not exceed 4. Each chained frame shall be positively acknowledged before the one with the next frame number can be sent.
+
+The *PDU Type 14 Frame Number* IE of an INITIALISATION control frame shall always be set to "0" when the chain has only one frame. When several INITIALISATION control frames are used in a chain the *PDU Type 14 Frame Number* IE shall be set to "0" for the first one and incremented by one in the sending direction for each new frame in the chain. The positive acknowledgement or negative acknowledgement shall carry the frame number of the frame being acknowledged.
+
+Upon reception of an INITIALISATION NEGATIVE ACKNOWLEDGEMENT control frame, an erroneous acknowledgement or at timer $T_{INIT}$ expiry, the Iu UP protocol entity controlling the Initialisation procedure shall reset and restart the $T_{INIT}$ supervision timer and repeat one INITIALISATION control frame with the same frame number. The repetition shall be performed up to $N_{INIT}$ times, $N_{INIT}$ being chosen by the operator (default $N_{INIT} = 3$ ). The $N_{INIT}$ (maximum number of allowed repetition) is the aggregate count for each frame in the chain and is restart each time a frame is positively acknowledged.
+
+![Sequence diagram showing the successful initialisation of Iu UP for m RFCIs. The diagram shows two entities, RNC/CN on the left and CN/RNC on the right. The process starts with an INITIALISATION message from RNC/CN to CN/RNC. This message is a sequence of m elements, each containing (RFCI, SDU sizes[, IPTIs]). An asterisk (*) indicates this sequence can be repeated N_INIT times. A yellow triangle on the RNC/CN side indicates a timer start. The CN/RNC responds with an INITIALISATION ACK. A dashed box labeled 'Transfer Of User Data' follows. A note at the bottom left indicates that the INITIALISATION message can be repeated N_INIT times and that IPTIs is optional.](1bf34e86af3591c80bfbc1c318f811c0_img.jpg)
+
+INITIALISATION
+
+\* $((\text{RFCI}, \text{SDU sizes}[, \text{IPTIs}^{2)})]_m)$
+
+INITIALISATION ACK
+
+Transfer Of User Data
+
+\* can be repeated $N_{INIT}$ times
+2) optional
+
+Sequence diagram showing the successful initialisation of Iu UP for m RFCIs. The diagram shows two entities, RNC/CN on the left and CN/RNC on the right. The process starts with an INITIALISATION message from RNC/CN to CN/RNC. This message is a sequence of m elements, each containing (RFCI, SDU sizes[, IPTIs]). An asterisk (\*) indicates this sequence can be repeated N\_INIT times. A yellow triangle on the RNC/CN side indicates a timer start. The CN/RNC responds with an INITIALISATION ACK. A dashed box labeled 'Transfer Of User Data' follows. A note at the bottom left indicates that the INITIALISATION message can be repeated N\_INIT times and that IPTIs is optional.
+
+Figure 9: Successful Initialisation of Iu UP for m RFCIs
+
+#### 6.5.2.2 Unsuccessful operation
+
+If the INITIALISATION control frame is incorrectly formatted and cannot be correctly treated by the receiving Iu UP protocol layer, this latter sends an INITIALISATION NEGATIVE ACKNOWLEDGEMENT control frame.
+
+If the receiver does not support the Iu UP Mode version used for the Initialisation procedure, it shall send a negative acknowledgement using the highest version it supports among the versions proposed by the sender. If none of the proposed versions are supported, the receiver shall respond with a negative acknowledgement using the highest version it supports.
+
+After $N_{INIT}$ successive negative acknowledgment, erroneous acknowledgment or $T_{INIT}$ expiry for INITIALISATION control frames having the same frame number, the Initialisation procedure is unsuccessfully terminated and the Iu UP protocol layers in RNC take appropriate local actions.
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note over RNC,CN: INITIALISATION ((RFCI, SDU sizes[, IPTIs²])m)
+ RNC->>CN:
+ Note over RNC,CN: INITIALISATION NACK
+ CN-->>RNC: 1)
+ Note left of RNC: * after NINIT repetitions
+ Note left of RNC: 2) optional
+
+```
+
+The diagram shows the RNC sending an INITIALISATION frame with payload $((\text{RFCI, SDU sizes[, IPTIs}^2\text{])}_m)$ to the CN. The CN responds with an INITIALISATION NACK (labeled '1)'). A bracket on the left indicates this process repeats, with a note '\*' indicating 'after $N_{INIT}$ repetitions' and '2)' indicating 'optional'.
+
+Sequence diagram of unsuccessful initialisation between RNC and CN.
+
+**Figure 10: Unsuccessful initialisation of Iu UP: 1) $N_{INIT}$ negative acknowledgement or 2) $N_{INIT}$ expiries of timer $T_{INIT}$**
+
+### 6.5.3 Iu Rate Control procedure
+
+#### 6.5.3.1 Successful operation
+
+The purpose of the Iu Rate Control procedure is to signal to the peer Iu UP protocol layer the maximum rate over Iu in the reverse direction of the sent RATE CONTROL control frame.
+
+The Rate Control procedure over Iu UP is normally controlled by the entity controlling the rate control over UTRAN i.e. the SRNC. The Iu Rate Control procedure is invoked whenever the SRNC decides that the maximum rate permitted downlink over Iu shall be modified, or when a RATE CONTROL control frame is received from the CN. Within the context of TrFO the SRNC may also receive RATE CONTROL control frames from the TrFO partner.
+
+The rates that can be controlled by the SRNC are all the rates that are defined by the Iu-Initialisation procedure and which are above the guaranteed bitrate specified in the RAB parameters (indicated to the Iu UP at the RNC). Rates below or equal to the guaranteed bitrate, e.g. the lowest speech rate or the SID frames, cannot be controlled (i.e. cannot be forbidden) by the SRNC (exceptionally, in case of version 1 any of the initialised rates equal to or above the guaranteed bitrate can be controlled).
+
+The procedure can be signalled at any time when Transfer of User Data procedure is not suspended by another Procedure Control function. When the user plane was initiated due to SRNS relocation reasons no rate control shall be signalled before the reception of the relocation execution trigger (see TS 25.413 [3]). At the reception of the relocation execution trigger the RNC shall start the Iu Rate Control procedure. This enables both TrFO partners to exchange current maximum rates and proceed user data transport based on latest rate decisions.
+
+The Procedure Control function upon request of upper layer prepares the RATE CONTROL control frame payload containing the maximum rate of the reverse direction of the RATE CONTROL control frame. To align the Iu Rate Control procedure with version 1 of the Iu UP protocol the permitted maximum rate is given as a set of RFCI indicators, that shall contain the maximum rate and all rates below the maximum rate, i.e. all rate controllable and non rate controllable rates. In the context of TrFO and TFO the Iu Rate Control procedure may also be controlled by a remote peer.
+
+The Frame Handler function calculates the frame CRC, formats the frame header into the appropriate PDU Type and sends the Iu UP frame PDU to the lower layers for transfer across the Iu interface.
+
+A supervision timer $T_{RC}$ is started after sending the Iu UP RATE CONTROL control frame. This timer supervises the reception of the rate control acknowledgement frame. Upon reception of a rate control acknowledgement frame, the Iu
+
+UP protocol layer in the SRNC stops the supervision timer $T_{RC}$ .
+
+Upon reception of a RATE CONTROL control frame, the Iu UP protocol layer checks the consistency of the Iu UP frame as follows:
+
+- The Frame Handler function checks the consistency of the frame header and associated CRC. If correct, the Frame Handler function passes Procedure Control part to the procedure control functions;
+- The Procedure Control functions check that all RFCIs in the initial RFCI set are indicated as either allowed or barred. If the whole rate control information is correct, the Procedure Control functions passes the rate control information to the NAS Data Streams specific functions;
+- The NAS Data Streams specific functions forward to the upper layers the complete protocol data in a Iu-UP-Status indication primitive;
+- Upon reception of the Iu-UP-Status request primitive, the Procedure Control functions shall acknowledge the RATE CONTROL control frame by including its own maximum rate control information i.e. the permitted rates in the reverse direction of the RATE CONTROL ACK message.
+
+
+
+Sequence diagram for Figure 11: Successful Rate Control. Two vertical lifelines are labeled 'RNC/CN' on the left and 'CN/RNC' on the right. A horizontal arrow labeled 'RATE CONTROL (RFCI indicators)' goes from left to right. A return horizontal arrow labeled 'RATE CONTROL ACK (RFCI indicators)' goes from right to left. Both lifelines terminate at the bottom with a thick horizontal bar.
+
+Figure 11: Successful Rate Control
+
+Figure 12: Void
+
+#### 6.5.3.2 Unsuccessful operation
+
+If the Iu UP protocol layer receives a RATE CONTROL control frame that is badly formatted or corrupted, it shall ignore the RATE CONTROL control frame, but send a RATE CONTROL NEGATIVE ACKNOWLEDGEMENT control frame back (figure 13a).
+
+
+
+Sequence diagram for Figure 13a: Negative Acknowledgement received from the peer. Two vertical lifelines are labeled 'RNC/CN' on the left and 'CN/RNC' on the right. The sequence is: 1. 'RATE CONTROL' arrow from left to right. 2. 'RATE CONTROL NACK' arrow from right to left, with a red lightning bolt symbol indicating an error/negative response. 3. A second 'RATE CONTROL' arrow from left to right. 4. A 'RATE CONTROL ACK' arrow from right to left. Both lifelines terminate at the bottom with a thick horizontal bar.
+
+**Figure 13a: Negative Acknowledgement received from the peer**
+
+If the Iu UP in the SRNC detects that the RATE CONTROL control frame has not been correctly interpreted or received (e.g. the observed rate is outside the set of permitted rates in the reverse direction of the RATE CONTROL control frame (figure 13b), or a RATE CONTROL NEGATIVE ACKNOWLEDGEMENT control frame has been received, or no RATE CONTROL POSITIVE ACKNOWLEDGEMENT control frame was received before the supervision timer $T_{RC}$ expires (Figure 13c)), the Iu UP shall retrigger a Iu Rate Control procedure. If after $N_{RC}$ repetitions, the error situation persists, the Iu UP protocol layers (sending and receiving) take the appropriate local actions.
+
+
+
+```
+
+sequenceDiagram
+ participant RNC
+ participant CN
+ Note over RNC,CN: RATE CONTROL (RFCI indicators)
+ RNC-xCN: TRANSFER OF USER DATA (not permitted rate, payload)
+ Note right of RNC: 1)
+ Note over RNC,CN: RATE CONTROL (RFCI indicators)
+ RNC-xCN: TRANSFER OF USER DATA (not permitted rate, payload)
+ Note right of RNC: 2)
+
+```
+
+\* after NRC repetitions
+
+Sequence diagram showing unsuccessful transfer of rate control from RNC due to frame loss and corrupted frame.
+
+**Figure 13: Unsuccessful Transfer of rate control from RNC: 1) Frame loss 2) Corrupted Frame**
+
+
+
+```
+
+sequenceDiagram
+ participant RNC or CN
+ participant CN or RNC
+ RNC or CN->>CN or RNC: RATE CONTROL: undetected error
+ CN or RNC->>RNC or CN: RATE CONTROL ACK
+ RNC or CN->>CN or RNC: User Data with not permitted rates
+ CN or RNC->>RNC or CN: RATE CONTROL
+ RNC or CN->>CN or RNC: RATE CONTROL ACK
+
+```
+
+Sequence diagram for unsuccessful transfer of rate control due to undetected error.
+
+**Figure 13b: Unsuccessful Transfer of rate control: undetected error**
+
+
+
+```
+
+sequenceDiagram
+ participant RNC or CN
+ participant CN or RNC
+ RNC or CN-xCN or RNC: RATE CONTROL: lost frame
+ Note left of RNC or CN: T_RC timer expires
+ RNC or CN->>CN or RNC: RATE CONTROL
+ CN or RNC->>RNC or CN: RATE CONTROL ACK
+
+```
+
+Sequence diagram for unsuccessful transfer of rate control due to lost rate control frame.
+
+**Figure 13c: Unsuccessful Transfer of rate control: lost rate control**
+
+#### 6.5.3.2A Frequent Rate Control Procedures
+
+Typically a new RATE CONTROL control frame should not be sent in the same direction before the previous Iu Rate Control procedure was terminated successfully.
+
+If for some reasons (e.g. frequently received RATE CONTROL control frames from the CN in a TFO connection to GSM) a RATE CONTROL control frame has to be sent before the previous Iu Rate Control procedure was terminated successfully, then the previous Iu Rate Control procedure is defined as terminated successfully: the supervision timer
+
+$T_{RC}$ shall be stopped and acknowledgement frames (positive or negative) for the previous RATE CONTROL control frame shall be ignored, i.e. only the most recent Iu Rate Control procedure shall be active in the same direction.
+
+
+
+```
+
+sequenceDiagram
+ participant RNC/CN
+ participant CN/RNC
+ Note left of RNC/CN: * ignored by the peer
+ RNC/CN->>CN/RNC: RATE CONTROL 1
+ RNC/CN->>CN/RNC: RATE CONTROL 2
+ CN/RNC-->>RNC/CN: RATE CONTROL ACK 1
+ CN/RNC-->>RNC/CN: RATE CONTROL ACK 2
+
+```
+
+Sequence diagram illustrating Frequent Rate Control. Two entities, RNC/CN and CN/RNC, are shown. The RNC/CN sends 'RATE CONTROL 1' and 'RATE CONTROL 2' to the CN/RNC. The CN/RNC sends 'RATE CONTROL ACK 1' and 'RATE CONTROL ACK 2' back to the RNC/CN. A note indicates that 'RATE CONTROL ACK 1' is ignored by the peer because 'RATE CONTROL 2' is the most recent control frame.
+
+**Figure 14: Frequent Rate Control: only most recent one is important**
+
+**Figure 15: Void**
+
+### 6.5.4 Time Alignment procedure
+
+#### 6.5.4.1 Successful operation
+
+The purpose of the Time Alignment procedure is to minimise the buffer delay in RNC by controlling the downlink transmission timing in the peer Iu UP protocol layer entity.
+
+The Time Alignment procedure is controlled by SRNC.
+
+The Time Alignment procedure is invoked whenever the SRNC detects the reception of Iu UP PDU at an inappropriate timing that leads to an unnecessary buffer delay. The actual detection of the trigger in SRNC is an internal SRNC matter and is out of the scope of the present document.
+
+The Iu UP protocol layer entity in SRNC indicates the peer entity the necessary amount of the delay or advance adjustment in the number of 500 $\mu\text{s}$ steps.
+
+A supervision timer $T_{TA}$ is started after sending the Iu UP TIME ALIGNMENT control frame. This timer supervises the reception of the time alignment acknowledgement frame.
+
+The requested Iu UP protocol layer entity in the peer node adjusts the transmission timing by the amount as indicated by SRNC.
+
+If the TIME ALIGNMENT control frame is correctly formatted and treated by the receiving Iu UP protocol layer and the time alignment is treated correctly by the upper layers, this latter sends a time alignment acknowledgement frame.
+
+Upon reception of a time alignment acknowledgement frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{TA}$ .
+
+The procedure can be signalled at any time when transfer of user data is not suspended by another control procedure.
+
+
+
+Figure 15a: Successful Time Alignment. A sequence diagram showing the interaction between an RNC and a CN. The CN sends 'User data with bad timing' to the RNC. The RNC sends a 'TIME ALIGNMENT' control frame to the CN. The CN responds with an 'ACK'. Finally, the CN sends 'User data with adjusted timing' to the RNC. A yellow wedge on the RNC side indicates a timer.
+
+Figure 15a: Successful Time Alignment
+
+Figure 16: Void
+
+#### 6.5.4.2 Unsuccessful operation
+
+If the TIME ALIGNMENT control frame could not be handled by the peer side, the peer side should send a NACK with a corresponding cause. When the Iu UP protocol layer in the SRNC receives a NACK with cause "Time Alignment not supported", then the SRNC shall not send additional TIME ALIGNMENT control frames for that RAB (unless the Iu UP conditions change for that RAB). The cause value "Requested Time Alignment not possible" is used to indicate that the requested time alignment was not possible at that moment. At a later moment the SRNC may initiate a new TIME ALIGNMENT control frame when needed. If the TIME ALIGNMENT control frame is received by the RNC, it shall respond with a NACK with the cause "Time Alignment not supported".
+
+If the Iu UP protocol layer in the SRNC detects that the TIME ALIGNMENT control frame has not been correctly interpreted or received, i.e. NACK received or timer expires, and the time alignment need still persists, the Iu UP should retrigger a Time Alignment procedure. If after $N_{TA}$ repetitions, the error situation persists, the Iu UP protocol layers take appropriate local actions.
+
+Upon reception of a TIME ALIGNMENT NEGATIVE ACKNOWLEDGEMENT control frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{TA}$ .
+
+
+
+Figure 16a: Unsuccessful Time Alignment. A sequence diagram showing the interaction between an RNC and a CN. The RNC sends a 'TIME ALIGNMENT' control frame to the CN. The CN responds with a 'TIME ALIGNMENT NACK'. A red wedge on the RNC side indicates a timer. A bracket on the left side of the RNC is labeled '1)' for the NACK reception and '2)' for the timer expiry. A note next to the bracket indicates '\* after N\_TA repetitions'.
+
+Figure 16a: Unsuccessful Time Alignment: 1) $N_{TA}$ negative acknowledgements or 2) $N_{TA}$ expiries of timer $T_{TA}$
+
+
+
+Sequence diagram for Time Alignment received by the RNC. It shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow labeled 'TIME ALIGNMENT' points from the CN lifeline to the RNC lifeline. A return horizontal arrow labeled 'TIME ALIGNMENT NACK' points from the RNC lifeline back to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.
+
+Figure 16b: Time Alignment received by the RNC
+
+### 6.5.5 Handling of Error Event procedure
+
+#### 6.5.5.1 Successful operation
+
+The purpose of the Handling of Error Event procedure is to handle the error reporting. Over the Iu UP protocol the error reports are made with ERROR EVENT control frames. The Handling of Error Event procedure in the Iu UP can be triggered by:
+
+- An error detected by the Iu UP functions (by receiving an erroneous frame or by receiving a frame with unknown or unexpected data). In this case an Iu UP- Status Indication may be used to inform the upper layers;
+- A request by the upper layers.
+
+When an Error event is reported by an ERROR EVENT control frame the following information shall be included:
+
+- A cause value;
+- Error distance (=0 if Iu UP function detected, =1 if requested by upper layers).
+
+Upon reception of an ERROR EVENT control frame the Iu UP functions should take appropriate local actions based on the cause value. This may include reporting the error to the upper layers with an Iu UP status indication.
+
+
+
+Sequence diagram for Successful Error event. It shows two vertical lifelines: RNC/CN on the left and CN/RNC on the right. A horizontal arrow labeled 'ERROR EVENT (Cause value, Error distance)' points from the RNC/CN lifeline to the CN/RNC lifeline. Both lifelines end with a thick horizontal bar at the bottom.
+
+Figure 15b: Successful Error event
+
+#### 6.5.5.2 Unsuccessful operation
+
+If the ERROR EVENT control frame is incorrectly formatted and cannot be correctly treated by the receiving Iu UP protocol layer appropriate local actions are taken (e.g. upper layers are informed). An error in an ERROR EVENT control frame should not generate the sending of a new ERROR EVENT control frame.
+
+
+
+Sequence diagram showing unsuccessful transfer of ERROR EVENT control frame. Two entities, RNC/CN and CN/RNC, are shown. The RNC/CN sends an ERROR EVENT (Cause, Error distance) message. The first attempt (1) results in frame loss at the CN/RNC. The second attempt (2) results in a corrupted frame at the CN/RNC, indicated by a jagged line and a red lightning bolt.
+
+**Figure 16c: Unsuccessful Transfer of ERROR EVENT control frame: 1) Frame loss 2) Corrupted Frame**
+
+### 6.5.6 Frame Quality Classification procedure
+
+The Frame Quality Classification procedure uses the services of the Transfer of User Data procedure to exchange across the Iu UP interface the Frame Quality Classification information.
+
+
+
+Sequence diagram showing successful transfers of User Data with FQC information. Two entities, RNC/CN and CN/RNC, are shown. The RNC/CN sends a TRANSFER OF USER DATA (FQC, RFCI, payload) message to the CN/RNC. The CN/RNC responds with a TRANSFER OF USER DATA (FQC, RFCI, payload) message back to the RNC/CN.
+
+**Figure 17: Successful Transfers of User Data with FQC information**
+
+## 6.6 Elements for Iu UP communication in Support mode
+
+### 6.6.1 General
+
+In the present document the structure of frames will be specified by using figures similar to figure 18.
+
+| Bits | | | | | | | | Number of Octets | | | | |
+|------------------|---|---|---|---------|---|---------|---|------------------|---------|--------------|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | |
+| Field 1 | | | | Field 2 | | | | 1 | Octet 1 | Header part | | |
+| Field 3 | | | | | | Field 4 | | 2 | Octet 2 | | | |
+| Field 4 continue | | | | Spare | | | | 2 | Octet 3 | Payload part | | |
+| Field 6 | | | | | | | | | Octet 4 | | | |
+| Field 6 continue | | | | Padding | | | | 0-m | Octet 5 | | | |
+| Spare extension | | | | | | | | | | | | |
+
+**Figure 18: Example frame format**
+
+Unless otherwise indicated, fields which consist of multiple bits within an octet will have the more significant bit located at the higher bit position (indicated above frame in figure 18). In addition, if a field spans several octets, more significant bits will be located in lower numbered octets (right of frame in figure 18).
+
+On the Iu interface, the frame will be transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according decreasing bit position (bit position 7 first).
+
+Spare bits should be set to "0" by the sender and should not be checked by the receiver.
+
+The header part of the frame is always an integer number of octets. The payload part is octet rounded (by adding 'Padding' when needed).
+
+The receiver should be able to remove an additional spare extension field that may be present at the end of a frame. See description of Spare extension field.
+
+### 6.6.2 Frame Format for predefined size SDUs
+
+#### 6.6.2.1 PDU Type 0
+
+PDU Type 0 is defined to transfer user data over the Iu UP in support mode for pre-defined SDU sizes. Error detection scheme is provided over the Iu UP for the payload part.
+
+The following shows the Iu frame structure for PDU TYPE 0 data frame of the Iu UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+
+
+| Bits | | | | | | | | Number of Octets | |
+|-----------------|---|------|---|--------------|---|-------------|---|------------------|----------------------|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | |
+| PDU Type (=0) | | | | Frame Number | | | | 1 | Frame Control Part |
+| FQC | | RFCI | | | | | | 1 | |
+| Header CRC | | | | | | Payload CRC | | 2 | Frame Check Sum Part |
+| Payload CRC | | | | | | | | | |
+| Payload Fields | | | | | | | | 0-n | Frame Payload part |
+| Payload Fields | | | | Padding | | | | | |
+| Spare extension | | | | | | | | 0-4 | |
+
+**Figure 19: Iu UP PDU Type 0 Format**
+
+The Iu UP PDU TYPE 0 data frame is made of three parts:
+
+- 1) Iu UP Frame Control part (fixed size);
+- 2) Iu UP Frame Check Sum part (fixed size);
+- 3) Iu UP Frame Payload part (pre-defined SDU sizes rounded up to octets [Note: this does not consider the usage of spare extension field]).
+
+The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 0 Frame Header.
+
+#### 6.6.2.2 PDU Type 1
+
+PDU Type 1 is defined to transfer user data over the Iu UP in support mode for pre-defined SDU sizes when no payload error detection scheme is necessary over Iu UP (i.e. no payload CRC).
+
+The following shows the Iu frame structure for PDU TYPE 1 data frame of the Iu UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+
+
+| Bits | | | | | | | | Number of Octets | |
+|-----------------|---|------|---|--------------|---|-------|---|------------------|----------------------|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | |
+| PDU Type (=1) | | | | Frame Number | | | | 1 | Frame Control Part |
+| FQC | | RFCI | | | | | | 1 | |
+| Header CRC | | | | | | Spare | | 1 | Frame Check Sum Part |
+| Payload Fields | | | | | | | | 0-n | Frame Payload part |
+| Payload Fields | | | | Padding | | | | | |
+| Spare extension | | | | | | | | 0-4 | |
+
+**Figure 20: Iu UP PDU Type 1 Format**
+
+The Iu UP PDU TYPE 1 data frame is made of three parts:
+
+- 1) Iu UP Frame Control part (fixed size);
+- 2) Iu UP Frame Check Sum part (fixed size);
+- 3) Iu UP Frame Payload part (pre-defined SDU sizes, rounded up to octets [Note: this does not consider the usage of spare extension field]).
+
+The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 1 Frame Header.
+
+#### 6.6.2.3 PDU Type 14
+
+##### 6.6.2.3.1 General
+
+PDU Type 14 is defined to perform control procedures over the Iu UP in support mode for pre-defined SDU sizes. The control procedure is identified by the procedure indicator. The Frame Payload contains the data information related to the control procedure.
+
+Figure 21 shows the Iu frame structure for PDU Type 14 of the Iu UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+| Bits | | | | | | | | Number of Octets | | | |
+|-----------------------------|---|---|---|-------------------------------|---|--------------------------|---|------------------|---------------------|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | |
+| PDU Type (=14) | | | | Ack/Nack (=0, i.e. procedure) | | PDU Type 14 Frame Number | | 1 | Frame Control Part | | |
+| Iu UP Mode version | | | | Procedure Indicator | | | | 1 | | | |
+| Header CRC | | | | | | Payload CRC | | 1 | Frame Checksum Part | | |
+| Payload CRC | | | | | | | | 1 | | | |
+| Reserved for procedure data | | | | | | | | 0-n | Frame payload part | | |
+| Spare extension | | | | | | | | 0-32 | | | |
+
+**Figure 21: Iu UP PDU Type 14 Format for procedure sending**
+
+The Iu UP PDU Type 14 is made of three parts:
+
+- 1) Iu UP Frame Control part (fixed size);
+- 2) Iu UP Frame Check Sum part (fixed size);
+- 3) Iu UP Frame Payload part (variable length, rounded up to octet).
+
+The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 14 Frame Header.
+
+##### 6.6.2.3.2 Positive Acknowledgement
+
+When the PDU Type 14 is used to positively acknowledge a control procedure, the PDU Type 14 frame takes the following structure at the TNL-SAP.
+
+| Bits | | | | | | | | Number of Octets | | | |
+|--------------------|---|---|---|---------------------------------------------------------------------------------|---|--------------------------|---|------------------|---------------------|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | |
+| PDU Type (=14) | | | | Ack/Nack (=1, i.e. Ack) | | PDU Type 14 Frame Number | | 1 | Frame Control Part | | |
+| Iu UP Mode version | | | | Procedure Indicator
(indicating the procedure being positively acknowledged) | | | | 1 | | | |
+| Header CRC | | | | | | Spare | | 1 | Frame Checksum Part | | |
+| Spare | | | | | | | | 1 | | | |
+| Spare extension | | | | | | | | 0-32 | Frame Payload part | | |
+| | | | | | | | | | | | |
+
+**Figure 22: Iu UP PDU Type 14 Format for positive acknowledgement**
+
+The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 14 Frame Header for positive acknowledgement.
+
+##### 6.6.2.3.3 Negative Acknowledgement
+
+When the PDU Type 14 is used to negatively acknowledge a control procedure, the PDU Type 14 frame takes the following structure at the TNL-SAP.
+
+| Bits | | | | | | | | Number of Octets | |
+|--------------------|---|---|---------------------------------------------------------------------------------|---|--------------------------|---|---|------------------|---------------------|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | |
+| PDU Type (=14) | | | Ack/Nack (=2, i.e. Nack) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part |
+| Iu UP Mode version | | | Procedure Indicator
(indicating the procedure being negatively acknowledged) | | | | | 1 | |
+| Header CRC | | | | | Spare | | | 1 | Frame Checksum Part |
+| Spare | | | | | | | | 1 | |
+| Error Cause value | | | | | Spare | | | 1 | Frame payload part |
+| Spare extension | | | | | | | | 0-32 | |
+
+**Figure 23: Iu UP PDU Type 14 Format for negative acknowledgement**
+
+The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 14 Frame Header for negative acknowledgement.
+
+##### 6.6.2.3.4 Procedures Coding
+
+###### 6.6.2.3.4.1 Initialisation
+
+Figure 24 specifies how the INITIALISATION control frame is coded.
+
+| Bits | | | | | | | | Number of Octets | | | | | | | | | | |
+|----------------------------------------|----|----------------------|----|-----------------------------------------|---|-----------------------------|-----------|---------------------------------------------------------------------------------------------------------|---------------------|--|--|--|--|--|--|--|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | | |
+| PDU Type (=14) | | | | Ack/Nack (=0.
l.e. Procedure) | | PDU Type 14
Frame Number | | 1 | Frame Control Part | | | | | | | | | |
+| lu UP Mode version | | | | Procedure Indicator (=0) | | | | 1 | | | | | | | | | | |
+| Header CRC | | | | | | Payload CRC | | 2 | Frame Checksum part | | | | | | | | | |
+| Payload CRC | | | | | | | | | | | | | | | | | | |
+| Spare | | | TI | Number of subflows per
RFCI (N) | | | Chain Ind | 1 | Frame payload part | | | | | | | | | |
+| LRI | LI | 1 st RFCI | | | | | | 1 | | | | | | | | | | |
+| Length of subflow 1 | | | | | | | | 1 or 2
(dep. LI) | | | | | | | | | | |
+| Length of subflow 2 to N | | | | | | | | (N-1)x(1
or 2) | | | | | | | | | | |
+| LRI | LI | 2 nd RFCI | | | | | | 1 | | | | | | | | | | |
+| Length of subflow 1 | | | | | | | | 1 or 2
(dep. LI) | | | | | | | | | | |
+| Length of subflow 2 to N | | | | | | | | (N-1)x(1
or 2) | | | | | | | | | | |
+| ... | | | | | | | | | | | | | | | | | | |
+| IPTI of 1 st RFCI | | | | ... | | | | 0 or M/2
(M:
Number
of RFCIs
in frame).
Ended by
4
padding
bits if M
is odd. | | | | | | | | | | |
+| ... | | | | IPTI of M th RFCI or Padding | | | | | | | | | | | | | | |
+| lu UP Mode Versions supported (bitmap) | | | | | | | | 2 | | | | | | | | | | |
+| Data PDU type | | | | Spare | | | | 1 | | | | | | | | | | |
+| Spare extension | | | | | | | | 0-32 | | | | | | | | | | |
+
+Figure 24: lu UP PDU Type 14 used for Initialisation
+
+6.6.2.3.4.2 Rate Control
+
+6.6.2.3.4.2.1 Rate Control procedure
+
+Figure 25 specifies how the RATE CONTROL control frame is coded.
+
+| Bits | | | | | | | | Number of Octets | | | | |
+|--------------------|-------------|-------------------------------|-------------------------------|---------|--------------------------|---|---|------------------|---------------------|--|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | |
+| PDU Type (=14) | | | Ack/Nack (=0, i.e. Procedure) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part | | | |
+| Iu UP Mode version | | | Procedure Indicator (=1) | | | | | 1 | | | | |
+| Header CRC | | | | | Payload CRC | | | 1 | Frame Checksum Part | | | |
+| Payload CRC | | | | | | | | 1 | | | | |
+| Spare | | Number of RFCI Indicators (P) | | | | | | 1 | Frame payload part | | | |
+| RFCI 0 Ind. | RFCI 1 Ind. | ... | RFCI P-1 Ind. | Padding | | | | 0-n | | | | |
+| Spare extension | | | | | | | | 0-32 | | | | |
+
+**Figure 25: Iu UP PDU Type 14 Format used for Rate Control**
+
+###### 6.6.2.3.4.2.2
+
+###### Rate Control positive acknowledgement
+
+Figure 25a specifies how the RATE CONTROL POSITIVE ACKNOWLEDGEMENT control frame is coded.
+
+| Bits | | | | | | | | Number of Octets | | | |
+|--------------------|-------------|-------------------------------|---------------|------------------------------------------------------------------------------|---|--------------------------|---|------------------|---------------------|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | |
+| PDU Type (=14) | | | | Ack/Nack (=1, i.e. Ack) | | PDU Type 14 Frame Number | | 1 | Frame Control Part | | |
+| Iu UP Mode version | | | | Procedure Indicator (indicating the procedure being positively acknowledged) | | | | 1 | | | |
+| Header CRC | | | | | | Spare | | 1 | Frame Checksum Part | | |
+| Spare | | | | | | | | 1 | | | |
+| Spare | | Number of RFCI Indicators (P) | | | | | | 1 | Frame Payload part | | |
+| RFCI 0 Ind. | RFCI 1 Ind. | ... | RFCI P-1 Ind. | Padding | | | | 0-n | | | |
+| Spare extension | | | | | | | | 0 - (31-n) | | | |
+
+Figure 25a: Iu UP PDU Type 14 Format for positive acknowledgement
+
+###### 6.6.2.3.4.3
+
+###### Time Alignment
+
+Figure 26 specifies how the TIME ALIGNMENT control frame is coded.
+
+| Bits | | | | | | | | Number of Octets | | | |
+|--------------------|---|---|---|--------------------------|---|--------------------------|---|------------------|---------------------|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | |
+| PDU Type (=14) | | | | Ack/Nack(=0) | | PDU Type 14 Frame Number | | 1 | Frame Control Part | | |
+| Iu UP Mode version | | | | Procedure Indicator (=2) | | | | 1 | | | |
+| Header CRC | | | | | | Payload CRC | | 1 | Frame Checksum Part | | |
+| Payload CRC | | | | | | | | 1 | | | |
+| Time alignment | | | | | | | | 1 | Frame payload part | | |
+| Spare extension | | | | | | | | 0-32 | | | |
+
+Figure 26: Iu UP PDU Type 14 Format used for Time Alignment
+
+###### 6.6.2.3.4.4 Error Event
+
+Figure 27 specifies how the ERROR EVENT control frame is coded.
+
+| Bits | | | | | | | | Number of Octets | | | |
+|--------------------|---|-------------------|---|--------------------------|---|-----------------------------|---|------------------|---------------------|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | |
+| PDU Type (=14) | | | | Ack/Nack(=0) | | PDU Type 14
Frame Number | | 1 | Frame Control Part | | |
+| Iu UP Mode version | | | | Procedure Indicator (=3) | | | | 1 | | | |
+| Header CRC | | | | | | Payload CRC | | 1 | Frame Checksum Part | | |
+| Payload CRC | | | | | | | | 1 | | | |
+| Error distance | | Error Cause value | | | | | | 1 | Frame payload part | | |
+| Spare extension | | | | | | | | 0-32 | | | |
+
+Figure 27: Iu UP PDU Type 14 Format used for Error Event
+
+### 6.6.3 Coding of information elements in frames
+
+#### 6.6.3.1 PDU Type
+
+**Description:** The PDU type indicates the structure of the Iu UP frame. The field takes the value of the PDU Type it identifies: i.e. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame. PDU type is used in all frames in support mode for predefined SDU sizes.
+
+**Value range:** {0-1 and 14 in use, 2-13: reserved for future PDU types, 15=reserved for future PDU type extensions}
+
+**Field length:** 4 bits
+
+#### 6.6.3.2 Ack/Nack
+
+**Description:** The Ack/Nack field tells if the frame is:
+
+- A control procedure frame;
+- A positive acknowledgement (ACK) of a control procedure frame;
+- A negative acknowledgement (NACK) of a control procedure frame.
+
+**Value range:** {0=control procedure frame, 1=ACK, 2=NACK, 3=reserved}
+
+**Field length:** 2 bits
+
+#### 6.6.3.3 Frame Number
+
+**Description:** The Iu UP frame numbering is handled by a Frame Number. The frame numbering can be based on either time or sent Iu UP PDU. In case the frame numbering is based on time the purpose of the frame number is to be of help in handling the Time Alignment functionality. When the frame number is based on time, the Frame number set in the PDU header is incremented by one (modulo 16) at each new ITI. The Frame number set in the PDU header shall be based on the timing of the source. The source is where the original payload was created. Two packets that were consecutive at the source shall not have the same frame number assigned. In case the Frame number relates to sent Iu UP PDU the purpose of the Frame Number is to provide the receiving entity with a mechanism to keep track of lost Iu UP frames. When the frame number is based on sent Iu UP PDU, the Frame number is incremented by one (modulo 16) for each sent Iu UP PDU. For a given user data connection, there is no relations between the frame numbers of frames sent in the downlink direction and the frame numbers of frames sent in the uplink direction.
+
+In the case the Frame Number relates to sent Iu UP PDU, the following applies:
+
+- Frame loss is when an incoming PDU frame has a frame number that is equal to (previous PDU frame number + 2) modulo [max. PDU frame number + 1]. This indicates that one and only one PDU frame has been lost.
+- Unexpected frame number is when an incoming PDU does not have the expected frame number and is not considered as a Frame Loss.
+
+**Value range:** {0-15}.
+
+**Field length:** 4 bits.
+
+#### 6.6.3.4 PDU Type 14 Frame Number
+
+**Description:** The Iu UP frame numbering is handled by a Frame Number. The purpose of the PDU Type 14 Frame Number is to provide the receiving entity with a mechanism to keep track of lost Iu UP frames. The PDU Type 14 Frame Number shall be managed as one single counter for all control procedure functions of a RAB. The sender shall increment this number by one (modulo 4) for each sent Iu UP Type 14 PDU starting with value 0 for the first PDU Type 14 INITIALISATION control frame sent out of the initialisation procedure. The counter shall be reset to 0 in case a new initialisation takes place. It is also used to relate the acknowledgment frame to the frame being acknowledged i.e. the same PDU Type 14 Frame Number is used in the positive or negative acknowledgement frame as the one used in the frame being acknowledged.
+
+The PDU Type 14 Frame Number shall be handled independently per direction, i.e. control frames other than acknowledgment frames shall be numbered independently per direction.
+
+The following applies for PDU Type 14 Frame Number:
+
+- Frame loss is when an incoming PDU frame has a frame number that is equal to (previous PDU frame number + 2) modulo [max. PDU frame number + 1]. This indicates that one and only one PDU frame has been lost.
+- Unexpected frame number is when an incoming PDU does not have the expected frame number and is not considered as a Frame Loss.
+
+Upon detection of frame loss or unexpected PDU Type 14 Frame Number in a procedure other than initialisation, the receiving entity shall still consider the frame as valid and handle it normally e.g. treat it and send an acknowledgement frame when appropriate.
+
+**Value range:** {0-3}.
+
+**Field length:** 2 bits.
+
+#### 6.6.3.5 Frame Quality Classification (FQC)
+
+**Description:** Frame Quality Classification is used to classify the Iu UP frames depending on whether errors have occurred in the frame or not. Frame Quality Classification is dependent on the RAB attribute *Delivery of erroneous SDU* IE.
+
+**Value range:** {0=frame good, 1=frame bad, 2=frame bad due to radio, 3= spare}.
+
+**Field length:** 2 bits.
+
+#### 6.6.3.6 RAB sub-Flow Combination Indicator (RFCI)
+
+**Description:** The RFCI identifies the structure of the payload. This can be used to specify the sizes of the subflows.
+
+**Value range:** {0-62, 63=RFCI not applicable}.
+
+**Field length:** 6 bits.
+
+#### 6.6.3.7 Procedure Indicator
+
+**Description:** The Procedure Indicator identifies the control procedure in the current frame.
+
+**Value range:** {0=initialisation, 1=rate control, 2=time alignment, 3=error event, 4-15=reserved}.
+
+**Field length:** 4 bits.
+
+#### 6.6.3.8 Header CRC
+
+**Description:** This field contains the CRC of all fields in Frame Control Part. The CRC is a 6-bit checksum based on the generator polynom $G(D) = D^6+D^5+D^3+D^2+D^1+1$ , see subclause 6.7.7. With this CRC all error bursts shorter than 7 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 24 bits, (max 3 octets).
+
+**Field length:** 6 bits.
+
+#### 6.6.3.9 Payload CRC
+
+**Description:** This field contains the CRC of all the fields (including Padding and possible Spare extension) of the Frame Payload Part. The CRC is a 10 bit checksum based on the generator polynom $G(D) = D^{10}+D^9+D^5+D^4+D^1+1$ , see subclause 6.7.7. With this CRC all error bursts shorter than 11 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 500 bits (max 62 octets).
+
+**Field length:** 10 bits.
+
+#### 6.6.3.10 Chain Indicator
+
+**Description:** Chain indicator is used to indicate whether the control procedure frame is the last frame related to the control procedure.
+
+**Value range:** {0=this frame is the last frame for the procedure, 1=additional frames will be sent for the procedure}.
+
+**Field length:** 1 bit.
+
+#### 6.6.3.11 Number of Subflows per RFCI
+
+**Description:** Number of Subflows per RFCI field indicates the number of subflows the RAB is made of. It is used to decode the SDU size information data lengths. All RFCs consist of the same number of subflows within a specific RAB.
+
+**Value range:** {0=reserved, 1-7}.
+
+**Field length:** 3 bits.
+
+#### 6.6.3.12 Length Indicator (LI)
+
+**Description:** Length Indicator, indicates if 1 or 2 octets is used for the RAB subflow size information.
+
+**Value range:** {0=one octet used, 1=two octets used}.
+
+**Field length:** 1 bit.
+
+#### 6.6.3.13 Number of RFCI Indicators
+
+**Description:** Number of RFCI indicators indicates the number of RFCI indicators present in the control procedure frame.
+
+**Value range:** {0-63}.
+
+**Field length:** 6 bits.
+
+#### 6.6.3.14 RFCI n Indicator
+
+**Description:** RFCI n Indicator indicates if the RFCI with value n is allowed or barred (n is a value between 0-62). E.g. RFCI 4 Indicator set to "0" indicates that RFCI =4 is allowed, RFCI 5 Indicator set to "1" indicates that RFCI =5 is barred, etc...
+
+**Value range:** {0=RFCI allowed, 1=RFCI barred}.
+
+**Field length:** 1 bit.
+
+#### 6.6.3.15 Error distance
+
+**Description:** Indicates if the error occurred at the error reporting entity (=0) or in a more distant entity. The error distance is incremented by one (or kept at its maximum value) when an error report is forwarded.
+
+- 0: Reporting local error.
+- 1: First forwarding of error event report.
+- 2: Second forwarding of error event report.
+- 3: Reserved for future use.
+
+**Value range:** {0: Reporting local error, 1: First forwarding of error event report. 2: Second forwarding of error event, 3: Reserved for future use}.
+
+**Field length:** 2 bit.
+
+#### 6.6.3.16 Error Cause value
+
+**Description:** Cause value is used to indicate what kind of error caused the error. Error cause value is used in NEGATIVE ACKNOWLEDGEMENT and ERROR EVENT control frames.
+
+- 0: CRC error of frame header.
+- 1: CRC error of frame payload.
+- 2: Unexpected frame number.
+- 3: Frame loss.
+- 4: PDU type unknown.
+- 5: Unknown procedure.
+- 6: Unknown reserved value.
+- 7: Unknown field.
+- 8: Frame too short.
+- 9: Missing fields.
+- 10–15: spare.
+- 16: Unexpected PDU type.
+- 17: spare.
+- 18: Unexpected procedure.
+- 19: Unexpected RFCI.
+- 20: Unexpected value.
+- 21–41: spare.
+- 42: Initialisation failure.
+- 43: Initialisation failure (network error, timer expiry).
+- 44: Initialisation failure (Iu UP function error, repeated NACK).
+- 45: Rate control failure.
+- 46: Error event failure.
+- 47: Time Alignment not supported.
+- 48: Requested Time Alignment not possible.
+- 49: Iu UP Mode version not supported.
+- 50–63: spare.
+
+**Value range:** {0–15 Used for syntactical protocol errors, 16–41 Used for semantical protocol errors, 42–63 Used for other errors}.
+
+**Field length:** 6 bit.
+
+#### 6.6.3.17 Padding
+
+**Description:** This field is an additional field used to make the frame payload part an integer number of octets when needed. Padding is set to "0" by the sender and is not interpreted by the receiver.
+
+**Value range:** {0–127}.
+
+**Field length:** 0–7 bits.
+
+#### 6.6.3.18 Time alignment
+
+**Description:** Time alignment indicates the amount the sending time should be advanced or delayed.
+
+0: Reserved.
+ 1: Delay 1\*500µs.
+ ...
+ 80: Delay 80\*500µs.
+ 81–127 Reserved.
+ 128: Reserved.
+ 129: Advance 1\*500µs.
+ ...
+ 208: Advance 80\*500µs.
+ 209–255 Reserved.
+
+**Value range:** {0: Reserved, 1–80: used for delay, 81–128: Reserved, 129–208 used for advance, 209–255: Reserved}.
+
+**Field length:** 8 bit.
+
+#### 6.6.3.19 Spare
+
+**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver.
+
+**Value range:** (0–2n-1).
+
+**Field Length:** n bits.
+
+#### 6.6.3.20 Spare extension
+
+**Description:** The spare extension field shall not be sent. The receiver should be capable of receiving a spare extension. The spare extension should not be interpreted by the receiver. This since in later versions of the present document additional new fields might be added in place of the spare extension. The spare extension can be an integer number of octets carrying new fields or additional information; the maximum length of the spare extension field (m) depends on the PDU type.
+
+**Value range:** 0–2m\*8-1.
+
+**Field Length:** 0–m octets. For PDU Types in the set {0,1}, m=4. For PDU Types in the set {14}, m=32.
+
+#### 6.6.3.21 LRI, Last RFCI Indicator
+
+**Description:** The Last RFCI Indicator is used to indicate which is the last RFCI in the current INITIALISATION control frame. This makes it possible for a receiver to detect a spare extension field.
+
+**Value range:** (0: Not last RFCI, 1: Last RFCI in current frame).
+
+**Field Length:** 1 bit.
+
+#### 6.6.3.22 Length of subflow
+
+**Description:** This field indicates the length of the corresponding subflow as number of bits per SDU.
+
+**Value range:** (0–255 if LI=0, 0–65535 if LI=1).
+
+**Field Length:** 8 or 16 bits (depending on LI).
+
+#### 6.6.3.23 TI
+
+**Description:** This field indicates if Timing Information is included in the INITIALISATION control frame.
+
+**Value range:** {0: IPTIs not present, 1: IPTIs present in frame}.
+
+**Field length:** 1 bit.
+
+#### 6.6.3.24 IPTI of nth RFCI
+
+**Description:** This field indicates the IPTI value in number of ITIs for the corresponding RFCI (in the same order as the RFCIs occur in the INITIALISATION control frame).
+
+**Value range:** {0–15}.
+
+**Field length:** 4 bits.
+
+#### 6.6.3.25 Iu UP Mode versions supported
+
+**Description:** This field indicates the Iu UP Mode Versions proposed by the sender for the related RAB for the initialisation procedure. Up to 16 Iu UP Mode versions can be simultaneously indicated.
+
+**Value range:**
+
+Each bit, in the two octet field, indicates a Iu UP Protocol version: (First octet, bit 7) indicates version 16, (Second octet, bit 0) indicates version 1.
+
+Bit = 0 means "Version not supported, not allowed or not proposed"
+
+Bit = 1 means "Version supported among the required versions and proposed"
+
+**Field length:** 2 octets
+
+#### 6.6.3.26 Iu UP Mode Version
+
+**Description:** This field indicates the Iu UP Mode version used for type 14 frames. Up to 16 Iu UP Mode Versions can be available.
+
+**Value range:** {1-16} The binary coded value is the version number minus 1 (e.g. version 1 is coded "0000", ..., version 16 is coded "1111").
+
+**Field length:** 4 bits
+
+#### 6.6.3.27 Payload fields
+
+**Description:** This field contains the Subflow SDUs, starting with the Subflow 1 SDU. The MSB of the Subflow 1 SDU is placed in bit 7 of the first octet (see example in figure 27a).
+
+**Value range:** {any value}.
+
+**Field length:** Sum of the lengths of the included Subflow SDUs.
+
+| Bits | | | | | | | | Number
of Octets |
+|---------------------|---|---|---|---------------|----------------------------------------------|---|---|---------------------|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
+| Subflow 1 SDU | | | | | | | | 1 |
+| Subflow 1 SDU cont. | | | | Subflow 2 SDU | | | | 1 |
+| Subflow 2 SDU cont. | | | | | Padding
(Not part of
'Payload fields') | | | 1 |
+
+Figure 27a: Example of 'Payload fields' with two Subflow SDUs
+
+#### 6.6.3.28 Data PDU type
+
+**Description:** This field indicates the PDU type that shall be used (in both directions) for transferring user data.
+
+**Value range:** {0: PDU type 0, 1: PDU type 1, 2–15: Reserved for future use}.
+
+**Field length:** 4 bits.
+
+### 6.6.4 Timers
+
+#### TINIT
+
+This Timer is used to supervise the reception of the initialisation acknowledgement frame from the peer Iu UP instance. This Timer is set by O&M.
+
+#### TTA
+
+This Timer is used to supervise the reception of the time alignment acknowledgement frame from the peer Iu UP instance. This Timer is set by O&M.
+
+#### TRC
+
+This Timer is used to supervise the reception of the rate control frame from the peer Iu UP instance. This Timer is set by O&M.
+
+### 6.6.5 Maximum values of repetition counters
+
+#### NINIT
+
+Maximum number of repetitions of an INITIALISATION control frame due to failure at the Initialisation procedure.
+
+#### NRC
+
+Maximum number of repetitions of a RATE CONTROL control frame due to failure at the Rate Control procedure.
+
+#### NTA
+
+Maximum number of repetitions of a TIME ALIGNMENT control frame due to failure at the Time Alignment procedure.
+
+## 6.7 Handling of unknown, unforeseen and erroneous protocol data
+
+### 6.7.1 General
+
+Error handling in Iu UP protocol is applicable only for Iu UP in Support mode.
+
+The Handling of Error Event procedure is the procedure handling error reporting. The Handling of Error Event procedure in the Iu UP can be triggered by:
+
+- An error detected by the Iu UP functions (by receiving an erroneous frame or by receiving a frame with unknown or unexpected data);
+- A request by the upper layers;
+- An ERROR EVENT control frame over the Iu UP protocol.
+
+The error can be reported either by:
+
+- An ERROR EVENT control frame over the Iu UP protocol;
+- An Iu UP Status Indication to upper layers (e.g. to be used by O&M).
+
+When an Error event is reported, either by an Iu-UP-Status-Indication, or by an ERROR EVENT control frame the following information shall be included:
+
+- Type of the error (syntactical error, semantical error or other error);
+- Error distance, i.e. information where the error occurred.
+
+### 6.7.2 Error detected by Iu UP functions
+
+When an error is detected within the Iu UP functions (by receiving a frame containing erroneous, unknown or unexpected data) one of the following actions is taken depending on the type of the error:
+
+1. Error indicated to upper layers by sending a Iu-UP-Status-Indication primitive;
+2. ERROR EVENT control frame sent;
+3. ERROR EVENT control frame sent and error indicated to upper layers by sending a Iu-UP-Status-Indication primitive;
+4. No action.
+
+### 6.7.3 Request by upper layers
+
+When the Iu UP receives an Iu-UP-Status-Request indicating Error event then an ERROR EVENT control frame should be sent over the Iu UP protocol indicating the appropriate error type.
+
+### 6.7.4 Error event frame over the Iu UP protocol
+
+When an ERROR EVENT control frame is received over the Iu UP protocol an Iu-UP-Status-Indication with 'Error event' information indicating the error type should be made to the upper layers. The Error event report contains a 'Cause value' that tells the type of the error. The Error event report also contains a field 'Error distance' that tells the distance to the entity reporting the error event. The 'Error distance' is "0" when the error is originally sent. When an Error event report is forwarded the 'Error distance' is incremented by one.
+
+### 6.7.5 Handling of error reports
+
+#### 6.7.5.1 General
+
+Figure 28 shows the external error case when the Handling of Error Event procedure is originally triggered by an Iu-UP-Status-Request. As an action on this the Handling of Error Event procedure sends an ERROR EVENT control frame over the Iu UP. On the other side the reception of ERROR EVENT control frame triggers the Handling of Error Event procedure, and an Iu-UP-Status-Indication is sent to upper layers. The handling is symmetrical over the Iu UP protocol.
+
+
+
+```
+
+graph TD
+ subgraph Left [ ]
+ SMF1[Support Mode Functions]
+ end
+ subgraph Right [ ]
+ SMF2[Support Mode Functions]
+ end
+ SMF2 -- "ERROR EVENT control frame (Cause, Error distance = 1)" --> SMF1
+ SMF1 -- "Status-Indication Error event (Cause, Error distance = 2)" --> TopLeft[ ]
+ SMF2 -- "Status-Request Error event (Cause)" --> TopRight[ ]
+ SMF1 <--> |"Transfer of Iu UP protocol frames"| SMF2
+ IuInterface[Iu Interface] -.-> SMF1
+ IuInterface -.-> SMF2
+ style Left fill:none,stroke:none
+ style Right fill:none,stroke:none
+ style TopLeft fill:none,stroke:none
+ style TopRight fill:none,stroke:none
+ style IuInterface fill:none,stroke:none
+
+```
+
+Diagram illustrating the external error handling process over the Iu UP protocol. Two 'Support Mode Functions' blocks are shown, connected by a double-headed arrow labeled 'Transfer of Iu UP protocol frames'. Above the left block, an arrow points up to 'Status-Indication Error event (Cause, Error distance = 2)'. Above the right block, an arrow points down from 'Status-Request Error event (Cause)'. A vertical dashed line labeled 'Iu Interface' runs between the two blocks. A horizontal arrow points from the right block to the left block, labeled 'ERROR EVENT control frame (Cause, Error distance = 1)'.
+
+Figure 28: External error
+
+Figure 29 shows the internal error case when the Handling of Error Event procedure is originally triggered by the Iu UP
+
+functions. As an action on this the Handling of Error Event procedure sends an ERROR EVENT control frame over the Iu UP. On the other side the reception of ERROR EVENT control frame triggers the Handling of Error Event procedure, and an Iu-UP-Status-Indication is sent to the upper layers. The handling is symmetrical over the Iu UP protocol.
+
+
+
+Diagram illustrating internal error handling between two Support Mode Functions over an Iu Interface. The left side shows a 'Status-Indication Error event (Cause, Error distance=1)' being sent upwards. The right side shows an 'ERROR EVENT control frame (Cause, Error distance=0)' being sent from the left side to the right side, and a 'Status-Indication Error event (Cause, Error distance=0)' being sent upwards from the right side. A red double-headed arrow labeled 'Transfer of Iu UP protocol frames' is shown between the two sides.
+
+Figure 29: Internal error
+
+#### 6.7.5.2 Error distance
+
+In an ERROR EVENT control frame the error distance has the following meaning:
+
+- 0: Error report relates to an Iu UP function error at the other side.
+- 1: Error report relates to an error at the other side reported by the upper layers.
+
+In an Iu UP-Status indication the error distance has the following meaning:
+
+- 0: Error report relates to a local Iu UP function error.
+- 1: Error report relates to an Iu UP function error at the other side.
+- 2: Error report relates to an error at the other side reported by the upper layers.
+
+### 6.7.6 List of errors in Iu UP
+
+Table 0: List of errors in Iu UP
+
+| Error Type | Error Cause | Recommended action by Handling of Error Event procedure | Possibly detected by function | Comment |
+|-------------|----------------------------------------|--------------------------------------------------------------------|-------------------------------------|-------------------------------------------------------|
+| Syntactical | CRC error of Frame payload (CRC check) | No action | NAS Data Streams specific functions | Handled by Frame Quality Classification, when applied |
+| | CRC error of Frame Header (CRC check) | Iu-UP-Status-Indication(Error event) | Frame Handler functions | Frame discarded |
+| | Unexpected Frame Number | Iu-UP-Status-Indication(Error event) | Frame Handler functions | See 6.6.3.3 |
+| | Frame loss | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | See 6.6.3.3 |
+| | PDU type Unknown | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | Used when PDU type is not 0, 1, or 14 |
+
+| Error Type | Error Cause | Recommended action by Handling of Error Event procedure | Possibly detected by function | Comment |
+|-------------------|--------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | Unknown procedure | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | Used when procedure value is neither 0, 1, 2, or 3 |
+| | Unknown reserved value | See 8.1.1 | | |
+| | Unknown field | | | This error cause shall not be sent. |
+| | Frame too short | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | Used when:
- the length of the entire received PDU is less than the expected (calculated) PDU header length, or
- the length of the payload (entire received PDU minus PDU header length) is less than the expected (calculated) payload length |
+| | Missing fields | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | This error cause shall not be sent. |
+| Semantical | Unexpected PDU type | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | |
+| | Unexpected procedure | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | |
+| | Unexpected RFCI | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | NAS Data Streams specific functions | |
+| | Unexpected value | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Procedure Control functions | |
+| Other error | Initialisation failure (outside Iu UP) | ERROR EVENT control frame | Function outside Iu UP | |
+| | Initialisation failure (network error, timer expiry) | Iu-UP-Status-Indication(Error event) | Procedure Control functions | |
+| | Initialisation failure (Iu UP function error, repeated NACK) | Iu-UP-Status-Indication(Error event) | Procedure Control functions | |
+| | Rate control failure | Iu-UP-Status-Indication(Error event) | Procedure Control functions | |
+| | Error event failure | Iu-UP-Status-Indication(Error event) | Procedure Control functions | |
+| | Time Alignment not supported | Iu-UP-Status-Indication(Error event) | Procedure Control functions | |
+| | Requested Time Alignment not possible | Iu-UP-Status-Indication(Error event) | Function outside Iu UP | |
+
+| Error Type | Error Cause | Recommended action by Handling of Error Event procedure | Possibly detected by function | Comment |
+|------------|-----------------------------|---------------------------------------------------------|-------------------------------|---------|
+| | Iu UP version not supported | Iu-UP-Status-Indication(Error event) | Procedure Control functions | |
+
+### 6.7.7 Error detection
+
+#### 6.7.7.1 General
+
+Error detection is provided on frames through a Cyclic Redundancy Check. The CRC for the payload is 10 bits and for the header it is 6 bits.
+
+#### 6.7.7.2 CRC Calculation
+
+The parity bits are generated by one of the following cyclic generator polynomials:
+
+$$g_{CRC6}(D) = D^6 + D^5 + D^3 + D^2 + D^1 + 1;$$
+
+$$g_{CRC10}(D) = D^{10} + D^9 + D^5 + D^4 + D^1 + 1.$$
+
+Denote the bits to be protected of a frame by $a_1, a_2, a_3, \dots, a_{A_i}$ ( $a_1$ being the bit with the highest bit position in the first octet), and the parity bits by $p_1, p_2, p_3, \dots, p_{L_i}$ . $A_i$ is the length of the protected data and $L_i$ is 6 or 10 depending on the CRC length.
+
+The encoding is performed in a systematic form, which means that in GF(2), the polynomial
+
+$$a_1 D^{A_i+5} + a_2 D^{A_i+4} + \dots + a_{A_i} D^6 + p_1 D^5 + p_2 D^4 + \dots + p_5 D^1 + p_6$$
+
+yields a remainder equal to 0 when divided by $g_{CRC6}(D)$ and the polynomial
+
+$$a_1 D^{A_i+9} + a_2 D^{A_i+8} + \dots + a_{A_i} D^{10} + p_1 D^9 + p_2 D^8 + \dots + p_9 D^1 + p_{10}$$
+
+yields a remainder equal to 0 when divided by $g_{CRC10}(D)$ . If $A_i = 0$ , $p_1 = p_2 = p_3 = \dots = p_{L_i} = 0$ .
+
+#### 6.7.7.3 Relation between input and output of the Cyclic Redundancy Check
+
+The protected bits are left unchanged in the frame. The parity bits for the Header CRC are put in the Header CRC field with $p_1$ being the highest bit position of the first octet of the Header CRC field. The parity bits for the Payload CRC are put in the Payload CRC field with $p_1$ being the highest bit position of the first octet of the Payload CRC field.
+
+# 7 Communication Primitives for the Iu UP protocol layer
+
+## 7.1 Modelling Principle
+
+The principle illustrated by figure 30 is used for modelling the primitives towards the protocol layer.
+
+
+
+Figure 30: Modelling principle. A diagram showing a 'Protocol Layer' box. Above the box, a 'REQUEST' primitive is shown with a downward arrow pointing to the box, and an 'INDICATION' primitive is shown with an upward arrow pointing from the box.
+
+Figure 30: Modelling principle
+
+## 7.2 Primitives towards the upper layers at the RNL SAP
+
+### 7.2.1 General
+
+The Iu UP protocol layer interacts with upper layers as illustrated in the figure above. The interactions with the upper layers are shown in terms of primitives where the primitives represent the logical exchange of information and control between the upper layer and the Iu UP protocol layer. They do not specify or constrain implementations.
+
+The following primitives are defined:
+
+- Iu-UP-DATA;
+- Iu-UP-STATUS;
+- Iu-UP-UNIT-DATA.
+
+Table 1: Iu UP protocol layer service primitives towards the upper layer at the RNL SAP
+
+| Primitive | Type | Parameters | Comments |
+|-----------------|------------|-------------------------|-----------------------------------------------------------------------------------------|
+| Iu-UP-DATA | Request | Iu-UP-payload | Subflow 1 SDU, ..., Subflow n SDU |
+| | | Iu-UP-control | RFCI |
+| | | | FQC |
+| | | | Frame Number |
+| | Indication | Iu-UP-payload | Subflow 1 SDU, ..., Subflow n SDU |
+| | | Iu-UP-control | RFCI |
+| | | | FQC |
+| | | | Frame Number |
+| Iu-UP-Status | Indication | Iu-UP-Procedure-Control | Error Cause, Error Distance |
+| | | | Complete protocol data for Initialisation, Rate Control, Time Alignment and Error Event |
+| | | | |
+| | | | |
+| | Request | Iu-UP-Procedure-Control | Error Cause |
+| | | | Complete protocol data for Initialisation, Rate Control, Time Alignment and Error Event |
+| | | | |
+| | | | |
+| Iu-UP-UNIT-DATA | Request | Iu-UP-payload | |
+| | Indication | Iu-UP-payload | |
+
+Primitive usage is a function of the mode of operation of the Iu UP protocol. Table 2 provides the association between
+
+Iu UP primitives towards the upper layers and the Iu UP modes of operation.
+
+**Table 2: Iu UP protocol layer service primitives related to the Iu UP mode of operation and function within the mode of operation**
+
+| Primitive | Type | Mode of Operation |
+|-----------------|------------|-------------------|
+| Iu-UP-DATA | Request | SMpSDU |
+| | Indication | SMpSDU |
+| Iu-UP-Status | Request | SMpSDU |
+| | Indication | SMpSDU |
+| Iu-UP-UNIT-DATA | Request | TrM |
+| | Indication | TrM |
+
+### 7.2.2 Iu-UP-DATA-REQUEST
+
+This primitive is used as a request from the upper layer Iu NAS Data Stream entity to send the RAB subflow SDU(s) on the established transport connection. This primitive includes the RFCI, the Frame Number and FQC information of the payload.
+
+The Iu UP protocol layer forms the Iu UP data frame, the Iu Data Stream DU being the payload of the Iu UP frame, and transfers the frame by means of the lower layer services.
+
+### 7.2.3 Iu-UP-DATA-INDICATION
+
+This primitive is used as an indication to the upper layer entity to pass the Iu NAS Data Stream User Plane information of a received Iu UP frame.
+
+This primitive includes the RFCI, the Frame Number and FQC information of the payload.
+
+This primitive may also include information aiming at informing the upper layers of a faulty situation that relates to the payload included in the primitive.
+
+### 7.2.4 Iu-UP-STATUS-REQUEST
+
+This primitive is used to pass control procedure information from the upper layer.
+
+This primitive shall contain the complete protocol data for the respective procedure.
+
+### 7.2.5 Iu-UP-STATUS-INDICATION
+
+This primitive is used to pass control procedure information to the upper layer.
+
+This primitive shall contain the complete protocol data for the respective procedure.
+
+### 7.2.6 Iu-UP-UNIT-DATA-REQUEST
+
+This primitive is used as a request from the upper layer to send an Iu UP payload on the established transport connection.
+
+The Iu UP protocol layer transfers the Iu Data Stream DU by means of the lower layer services without adding any protocol header overhead.
+
+### 7.2.7 Iu-UP-UNIT-DATA-INDICATION
+
+This primitive is used as an indication to the upper layer entity to pass the Iu UP payload.
+
+## 7.3 Primitives towards the transport layers at TNL SAP
+
+### 7.3.1 General
+
+Access to the Transport network Layer is performed through a generic SAP: TNL-SAP.
+
+When the Transport Network upper layer consists of AAL2, the TNL SAP maps onto the AAL-SAP through which communication is performed using specific AAL primitives.
+
+When the Transport Network upper layer consists of GTP-U, the TNL SAP maps onto the GTP-U SAP through which communication is performed using generic primitives.
+
+The choice of communication, specific or generic, through the TNL SAP is fixed by the Radio Network Layer control plane logic. This choice is based on the requirements placed by e.g. the RAB characteristics, the CN domain requesting the RAB establishment or other operator's choice.
+
+### 7.3.2 ATM/AAL2 based Transport layer
+
+#### 7.3.2.1 General
+
+When the Iu UP protocol layer uses the services of an ATM/AAL2 transport (ITU-T Recommendation I.363.2 [7]), it uses an established AAL2 connection for transferring frames between the peer TNL-SAPs at both ends of the Iu User plane access points. The Transport Network Control Plane over Iu handles the signalling to establish and release the AAL2 call connections.
+
+#### 7.3.2.2 AAL2 Service Primitives used by the Iu UP protocol
+
+AAL2 services and primitives used at the Service Access Point from the AAL2 layer are shown in table 3.
+
+**Table 3: AAL2 primitives and parameters**
+
+| Primitive | Type | Parameters | Comments |
+|---------------------------------------------------------------------------------------------------------------|------------|------------|-----------------|
+| SSSAR-UNITDATA | Request | SSSAR-INFO | |
+| | | SSSAR-UUI | Not used (note) |
+| SSSAR-UNITDATA | Indication | SSSAR-INFO | |
+| | | SSSAR-UUI | Not used (note) |
+| NOTE: The setting of this field is set to not used i.e. decimal value 26 according to ITU-T Rec. I.366.1 [8]. | | | |
+
+The primitives of table 3 are the standard primitives of ITU-T Rec. I.366.1 [8]. These primitives are intended to be used in the Iu UP.
+
+### 7.3.3 GTP-U based Transport Layer
+
+#### 7.3.3.1 General
+
+When the Iu UP protocol layer uses the services of a GTP-U transport, it uses an established GTP-U tunnel for transferring frames between the GTP-U tunnel endpoints at both ends of the Iu User plane access points. The RANAP Control Plane signalling over Iu handles the signalling to establish and release the GTP-U tunnels.
+
+#### 7.3.3.2 Generic Service Primitives used by the Iu UP protocol
+
+Generic primitives are used at the GTP-U SAP. They are shown in table 4.
+
+**Table 4: Generic primitives and parameters to and from GTP-U layer**
+
+| Primitive | Type | Parameters | Comments |
+|----------------|------------|---------------|----------|
+| Iu-UP-UNITDATA | Request | Iu-UP-payload | |
+| Iu-UP-UNITDATA | Indication | Iu-UP-payload | |
+
+### 7.3.4 RTP based Transport Layer
+
+#### 7.3.4.1 General
+
+When the Iu UP protocol layer uses the services of a RTP/UDP/IP transport, it uses an established RTP session for transferring frames between the two RTP endpoints at both ends of the Iu User plane access points as defined in IETF RFC 1889 [14]. A single Iu-UP PDU shall be transported as RTP payload. A dynamic Payload Type (IETF RFC 1890 [15]) shall be used (see TS 25.414 [4]).
+
+#### 7.3.4.2 Generic Service Primitives used by the Iu UP protocol
+
+Generic primitives are used at the RTP SAP. They are shown in table 5.
+
+**Table 5: Generic primitives and parameters to and from RTP layer**
+
+| Primitive | Type | Parameters | Comments |
+|----------------|------------|---------------|----------|
+| Iu-UP-UNITDATA | Request | Iu-UP-payload | |
+| Iu-UP-UNITDATA | Indication | Iu-UP-payload | |
+
+# 8 Evolution of Iu UP Protocol
+
+## 8.1 Principles for Protocol Evolution
+
+### 8.1.1 Unknown field value
+
+The Iu UP protocol may be evolved by taking into use field values that have been specified to be reserved for future use or have been specified as spare values. When a UP protocol entity receives an unknown field value, it can react differently depending whether the unknown value is reserved for future use or if it is a spare value. The following principles are recommended for receiver reactions:
+
+- If a spare value is used by the sender, but not understood by the receiver, there should be a default action for the receiver. This default action should be defined on a field basis;
+- If a value that is reserved for future use is used by the sender, but not understood by the receiver, the value should be rejected by the receiver. This should be done by sending a Negative Acknowledgement to the peer entity, if possible. Otherwise an Error Event should be generated in order to inform the upper layers and the peer entity;
+- A received ERROR EVENT control frame shall not trigger another ERROR EVENT control frame back to the sender, even though e.g. the Cause value in the received ERROR EVENT control frame would not be understood.
+
+In the following the recommended actions of the receiver are handled field by field when an unknown field value is received.
+
+#### PDU Type
+
+Recommended action if reserved values used: Generate Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "PDU type unknown".
+
+#### FQC
+
+Recommended action if spare values used: Ignore the field and pass it onwards.
+
+#### ACK/NACK
+
+Proposed action if reserved values used: Generate an Error Event, i.e. the upper layers and the peer entity are informed
+
+about the error event with Cause: "Unknown reserved value".
+
+#### **Procedure Indicator**
+
+Recommended action if reserved values used: Generate an Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "Unknown procedure".
+
+#### **Error Cause value**
+
+Value "49" is reserved for "Iu UP Mode version not supported" whatever the Iu UP Mode version.
+
+Recommended action if reserved values used: Generate Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "Unknown reserved value".
+
+Recommended action if spare values used: Ignore the field and pass it onwards.
+
+### 8.1.2 Adding a new field to an existing frame
+
+If there is a need to add a new field to an existing procedure, the following principles shall be applied:
+
+- The PDU type defines the header mask. Therefore, a new field shall not be added to the header part of an existing frame and possible spare bits in the header shall not be taken into use since these would be violations of the header mask;
+- The Procedure Indicator shall define the fields that should be in a control frame;
+- There shall be only one Procedure Indicator for each procedure;
+- If a new field needs to be introduced to an existing procedure (i.e. existing procedure that is defined in an existing UP version), the new field shall not be *added* to the payload part. Instead, the new field may be introduced by placing it to a spare field in the payload part of the frame, if possible;
+- However, if a new field needs to be introduced to an existing procedure, but spare field(s) in the payload part cannot be used to introduce the new field, then a new procedure shall be created and hence a new Procedure Indicator value shall be allocated for the new procedure;
+- To enable simple protocol evolution, when a new Procedure Indicator will be introduced, the new frame shall include both the new fields and the fields of the old frame;
+- When an implementation receives an unknown Procedure Indicator it may use the ERROR EVENT control frame with Cause: "Unknown procedure" to report this. This indicates to the sender that the procedure was not understood and it may try with an older procedure.
+
+### 8.1.3 Adding a new PDU type
+
+In the future, the Iu UP protocol may evolve so that there is a need to add a new PDU type. The criteria for introducing a new PDU type could be e.g.:
+
+- The Procedure Indicators may run out and there is a need to have more;
+- There is a need to change the header mask, e.g. the Frame Number field may need to be increased or the CRC field needs to be modified.
+
+While the PDU Type 15 is reserved for future PDU type extensions, there may be 'subtypes' under PDU Type 15 in the future and there also may be new procedures in these 'subtypes'.
+
+Thus it has to be ensured that if the same Procedure Indicator value is used under several PDU types, it should be made clear e.g. in the Error Event cause element, which PDU type it concerns.
+
+The maximum length of the Spare Extension field is defined per PDU type. Thus when a new PDU type is added, an appropriate length for the Spare Extension field (if any) has to be defined. For Release '99, a length of 4 octets has been used for data PDUs, and 32 octets for control PDUs.
+
+### 8.1.4 Protocol version handling
+
+In the future, new versions of the Iu UP protocol may be introduced. A reason for a new version of the protocol could
+
+be, e.g.:
+
+- The earlier introduced new features or functions are required to be mandatory in the new version;
+- Due to technical development, the new version of the protocol could be totally different (and incompatible) from the earlier version.
+
+The following principles shall be applied to version handling of Iu UP protocol:
+
+- It shall be possible to introduce additional modes of operation;
+- It shall be possible to evolve the operation modes independently of each other;
+- There shall be independent version numbers for each mode of operation;
+- The mode of operation of an Iu UP protocol instance is decided by the CN. Further, the CN shall indicate those versions that are required to support certain features, e.g. TrFO. The version of the mode among the required ones shall be negotiated between the CN and UTRAN during Initialisation procedure;
+- The version number of a UP operation mode may change or be unchanged between different releases;
+- When the protocol is evolved it shall be made clear in the specification, which features belong to which versions;
+- A new version may be an evolution (i.e. compatible) of the old version or the new version may be totally different from the old version.
+- The structure of the PDU Type 14 header, up to and including header CRC, shall remain unchanged whatever the Iu UP version.
+
+# --- Annex A (informative): Illustration of usage of RFCI for AMR speech RAB
+
+This annex contains information related to usage of RFCIs in the context of AMR speech RAB.
+
+The following figure illustrates the RFCI allocation and flow throughout the UTRAN.
+
+
+
+Diagram illustrating the RAB establishment and reconfiguration process between UE, RNC, and CN. The diagram is divided into Control Plane (CP) and User Plane (UP). In the CP, the CN sends RAB attributes to the RNC, which then allocates RFCIs, configures L2/L3, and initializes the Iu UP. The RNC then configures the UE's L2/L3. In the UP, the UE sends NAS data streams to its L2/L3, which are then passed to the RNC's L2/L3. The RNC's L2/L3 sends an Iu Frame to the RNC's Iu UP, which then sends it to the CN's Iu UP. The CN's Iu UP sends the data to its L2/L3, which then sends it to the UE's L2/L3. The UE's L2/L3 then sends the data to the NAS data streams. The diagram also shows the flow of RFCIs and TFCIs between the UE, RNC, and CN.
+
+1. **RAB Attributes:** at RAB establishment or reconfiguration, the SDU format information parameter is passed to UTRAN. The SDU information is organised per BER i.e. RAB sub Flow. For instance, 12,2 kbits/s AMR codec is passed as RAB sub flow 1 SDU size: 81 bits –class A bits-, as RAB sub flow 2 SDU size: 103 bits –class B bits-, as RAB sub flow 3 SDU size: 60 bits –class C-, which makes one RAB sub Flow Combination. This is done for all source rates (i.e. all codec modes, DTX also if included). So using the RAB subflows combination set from Table A.1, the SDU Formation Information Parameters for RAB subflow 1 is [81,42,39,0], for RAB subflow 2 is [103,53,0,0], and for RAB subflow 3 is [60,0,0,0]. The Iu UP is used in support mode for predefined SDU size.
+2. **Allocation of RFCIs:** the RNC dynamically allocates an identification (RFCI) to each permitted/possible combinations it can offer. E.g. for 0 kbits/s, the RNC allocates RFCI 0, for the SID, the RNC allocates RFCI 3, for 4,75 kbits/s, the RNC allocates RFCI 2, and for 12,2. kbits/s, the RNC allocates RFCI 1 (according to the example table A.1).
+3. **Configuration of L2/L3 based on RFCIs:** RFCIs are used to configure the L2/L3. RLC (TS 25.322 [11]) is used in transparent mode. MAC (TS 25.321 [10]) configures its co-ordinated DCHs with the RFCIs and associates one RFCI to one TFI.
+4. **Initialisation of Iu UP:** the RNC reports the permitted combinations it can offer to the transcoder using an inband Iu INITIALISATION control frame containing the RFCIs and associated RAB sub Flow sizes.
+5. **Configuration of L2/L3 based on e.g. TFIs:** idem as 3. L2/L3 may use e.g. TFI to communicate with the Codec about the RAB sub-Flow structure of the SDU received or to be sent.
+6. **RFCIs+ SDU size information:** the RFCIs and associated RAB sub Flow sizes received within the Iu INITIALISATION control frame are passed to the Codec for configuration.
+7. **Example of DL frame transfer:**
+ - 7.1. The Codec encodes a 12,2 kbits/s frame. It sends down to the Iu UP an SDU with an associated RFCI equals to 1 (in this example).
+ - 7.2. The Iu UP packs a frame with a header containing an RFCI set to value "1", and the payload made of the SDU received from the Codec.
+ - 7.3. The Iu UP passes to L2/L3, the Iu frame payload (the Codec SDU) and the RFCI. The L2/L3 uses this RFCI to break the Iu frame onto the co-ordinated DCHs corresponding to the different bits protection classes. The corresponding TFI is selected.
+ - 7.4. The radio frame is sent with the TFI chosen by MAC (TS 25.321 [10]).
+ - 7.5. The L2/L3 receives the SDUs on the co-ordinated DCHs, combines them back and uses e.g. the TFI to indicate to the codec the structure of the received frame.
+
+**Figure A.1**
+
+For information on RAB subflow combinations used for AMR speech see TS 26.102 [12].
+
+SRNC allocates one or more possible/available RAB sub-flow combination(s) and generates RAB sub-flow combination set. RAB sub-flow combination number is dynamically generated by SRNC. This RAB sub-flow combination set is signalled towards CN with user plane signalling as described in TS 25.401 [1]. The signalling towards UE is to be defined by TSG-RAN WG2.
+
+### **RAB sub-flow combination set:**
+
+A RAB sub-flow combination indicator, RFCI, indicates which RAB sub flow combination will be used for the Iu user frames. In the communication phase the RFCI is included in the user frame, and the RFCI state the structure of the user frame.
+
+Table A.1 exemplifies the allocation of 4 different RAB sub-flows combinations for 3 sub-flows and generating of RAB sub-flows combination set.
+
+**Table A.1: Example of Allocation of RAB sub-flows combination indicator**
+
+| | RFCI
(RAB sub-
Flow
Combination
Indicator) | RAB sub-
Flow 1 | RAB sub-
flow 2 | RAB sub-
flow 3 | Total | Source rate |
+|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------------------|----------------------------|--------------|--------------------|
+| RAB
sub-
flows
combina
tion set | 1 | 81 | 103 | 60 | 244 | Source rate 1 |
+| | 2 | 42 | 53 | 0 | 95 | Source rate 2 |
+| | 3 | 39 | 0 | 0 | 39 | Source rate 3 |
+| | 0 | 0 | 0 | 0 | 0 | Source rate 4 |
+| NOTE: | In the table above the greyed area shows the part that is sent in the Initialisation procedure in Iu UP. This is what constitutes the RAB subflow combination set. | | | | | |
+
+# Annex B (informative): Illustration of protocol states in the Iu UP
+
+This annex contains information related to possible protocol states for operation of the Iu UP. This annex does not constraint implementation and is for illustration purposes only.
+
+The state model is common for both ends of the Iu UP so that the protocol machines are operating symmetrically. This approach is taken to facilitate state description for all cases including possible future scenarios where the Iu UP could be terminated elsewhere.
+
+NOTE: Primitive Iu-UP-CONFIG-Req is used by upper layers to configure the Iu UP protocol layer. It is used in this annex for illustrative purposes and therefore it is not defined in clause 7.
+
+## B.1 Protocol state model for transparent mode
+
+Figure B.1 illustrates the state model for transparent mode Iu UP instances. A transparent mode instance can be in one of following states.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> 1 : Iu-UP-CONFIG-Req
+ 1 --> 2 : Iu-UP-CONFIG-Req
+ 2 --> 2 : Iu-UP-UNIT-DATA-Req or Iu-UP-UNIT-DATA-Ind or SSSAR-UNITDATA-Req or SSSAR-UNITDATA-Ind or Iu-UP-UNITDATA-Ind or Iu-UP-UNITDATA-Req
+ state "1. Null" as 1
+ state "2. TrM Data Transfer Ready" as 2
+
+```
+
+Figure B.1: Protocol state model for transparent mode. The diagram shows two states: 1. Null and 2. TrM Data Transfer Ready. State 1 is a circle labeled '1.' and 'Null'. State 2 is a circle labeled '2.' and 'TrM Data Transfer Ready'. A transition arrow from State 1 to State 2 is labeled 'Iu-UP-CONFIG-Req'. A transition arrow from State 2 to State 1 is labeled 'Iu-UP-CONFIG-Req'. State 2 has a self-loop arrow labeled with a list of primitives: Iu-UP-UNIT-DATA-Req or Iu-UP-UNIT-DATA-Ind or SSSAR-UNITDATA-Req or SSSAR-UNITDATA-Ind or Iu-UP-UNITDATA-Ind or Iu-UP-UNITDATA-Req.
+
+Figure B.1: Protocol state model for transparent mode
+
+### B.1.1 Null State
+
+In the null state the Iu UP instance does not exist and therefore it is not possible to transfer any data through it.
+
+Upon reception of a Iu-UP-CONFIG-Req from higher layer the Iu UP instance is created and transparent mode data transfer ready state is entered. The mode information is received either through RANAP signalling or directly in the CN node. In the Iu-UP-CONFIG-Req e.g. the following information will be indicated:
+
+- Transparent mode.
+
+### B.1.2 Transparent Mode Data Transfer Ready State
+
+In the transparent mode data transfer ready state, transparent mode data can be exchanged between the entities.
+
+Upon reception of Iu-UP-CONFIG-Req indicating release from higher layer, the Iu UP instance is terminated and the null state is entered.
+
+## B.2 Protocol state model for support mode for predefined SDU sizes
+
+Figure B.2 illustrates the state model for support mode Iu UP instances. A support mode instance can be in one of the following states.
+
+
+
+Iu PDU
+ Primitive between layers
+
+```
+
+stateDiagram-v2
+ [*] --> 1: Null
+ 1 --> 2: Initialisation (Iu-UP-CONFIGReq)
+ 2 --> 1: Iu-UP-CONFIGReq
+ 2 --> 2: Initialisation (Repeat)
+ 2 --> 3: Last Initialisation ACK sent or Last Initialisation Ack received
+ 3 --> 2: Negative Initialisation Ack
+ 3 --> 1: Iu-UP-CONFIGReq
+ 3 --> 3: Rate control PDU
+ 3 --> 4: Iu-UP-STATUSInd (Rate control)
+ 4 --> 3: Iu-UP-STATUSInd (Rate control)
+ 4 --> 4: Iu-UP-DATAReq or Iu-UP-DATAInd or SSSAR-UNITDATAReq or SSSAR-UNITDATAInd or Iu-UP-UNITDATAInd or Iu-UP-UNITDATAReq
+
+```
+
+Figure B.2: Protocol state model for support mode. The diagram shows four states: 1. Null, 2. Initialisation, 3. SMpSDU Data Transfer Ready, and 4. SMpSDU Data Transfer Ready. Transitions are labeled with Iu-UP primitives. State 1 to 2 is Iu-UP-CONFIGReq. State 2 to 1 is Iu-UP-CONFIGReq. State 2 to 2 is Initialisation (Repeat). State 2 to 3 is Last Initialisation ACK sent or Last Initialisation Ack received. State 3 to 2 is Negative Initialisation Ack. State 3 to 1 is Iu-UP-CONFIGReq. State 3 to 3 is Rate control PDU. State 3 to 4 is Iu-UP-STATUSInd (Rate control). State 4 to 3 is Iu-UP-STATUSInd (Rate control). State 4 to 4 is Iu-UP-DATAReq or Iu-UP-DATAInd or SSSAR-UNITDATAReq or SSSAR-UNITDATAInd or Iu-UP-UNITDATAInd or Iu-UP-UNITDATAReq.
+
+Figure B.2: Protocol state model for support mode
+
+### B.2.1 Null State
+
+In the null state the Iu UP instance does not exist and therefore it is not possible to transfer any data through it.
+
+Upon reception of a Iu-UP-CONFIG-Req from higher layer the Iu UP instance is created and initialisation state is entered. In the Iu-UP-CONFIG-Req e.g. the following information could be indicated:
+
+- Support mode for predefined SDU sizes;
+- Time alignment (FFS);
+- Indication of delivery of erroneous SDUs;
+- Periodicity;
+- required UP versions.
+
+### B.2.2 Initialisation State
+
+In the initialisation state the instance exchanges initialisation information with its peer Iu UP instance.
+
+Upon reception of Iu-UP-CONFIG-Req indicating release from higher layer, the Iu UP instance is terminated and the null state is entered.
+
+Upon sending or receiving of an INITIALISATION control frame the Iu UP instance remains in the Initialisation state. The sending side starts a supervision timer $T_{INIT}$ . The receiving side acknowledges the INITIALISATION control frame with a positive acknowledgement or a negative acknowledgement.
+
+Upon reception of the last initialisation acknowledgement frame, the supervision timer $T_{INIT}$ is stopped and the Iu UP instance enters SMpSDU data transfer ready state.
+
+After sending a positive acknowledgement of the last INITIALISATION control frame, the Iu UP instance enters SMpSDU data transfer ready state. Note that CN does not know if the initialisation ACK was correctly received by the RNC (and Initialisation procedure successfully completed) until it receives RAB assignment response, or use data from
+
+the RNC. The CN must therefore be able to continue receiving INITIALISATION control frames by re-entering the Initialisation state (from Support Mode Data Transfer Ready State), if the CN has started to send user data before receiving the indication that Initialisation was successfully completed.
+
+Upon reception of an INITIALISATION NEGATIVE ACKNOWLEDGEMENT control frame (INIT NACK) initialisation frame can be repeated n times.
+
+If after n repetitions, the Initialisation procedure is unsuccessfully terminated (due to n negative acknowledgements or timer expires) the Handling of Error Event procedure is used to report the Initialisation failure and the Iu UP instance remains in the initialisation state. Upon reception of an INITIALISATION control frame the Initialisation state is entered.
+
+### B.2.3 Support Mode Data Transfer Ready State
+
+In the support mode data transfer ready state, support mode data can be exchanged between the peer Iu UP instances.
+
+Upon reception of Iu-UP-DATA-Request from the upper layer or SSSAR-UNITDATA-Indication or Iu-UP-UNITDATA-Indication from TNL layer, appropriate user data transfer procedures are performed. Iu UP instance remains in the SMpSDU data transfer ready state.
+
+Upon sending of Iu-UP-DATA-Indication or SSSAR-UNITDATA-Request or Iu-UP-UNITDATA-Request the Iu UP instance remains in the SMpSDU data transfer ready state.
+
+Upon sending or receiving of a rate control PDU the Iu UP instance remains in the SMpSDU data transfer ready state.
+
+Upon sending of a Iu-UP-STATUS-Indication (rate control) the Iu UP instance remains in the SMpSDU data transfer ready state.
+
+Upon reception of Iu-UP-CONFIG-Req from higher layer the Iu UP instance is terminated and the null state is entered.
+
+Upon detection of a protocol fault, Iu-UP-STATUS-Indication is sent to upper layer an ERROR EVENT control frame may be sent over Iu UP.
+
+In case of handover or relocation, Initialisation procedures may have to be performed and Iu UP instance may have to enter the initialisation state.
+
+# --- Annex C (informative): Open Issues of the Iu UP
+
+This annex contains information related to open issues left in the Iu UP protocol.
+
+# Annex D (informative): Distributed rate decision within RNC
+
+This annex contains information related to the distributed rate decision within an RNC (see also within TS 23.153 [13])
+
+The Iu Rate Control procedure over Iu UP is normally controlled by the entity controlling the rate control over UTRAN i.e. the SRNC. The SRNC may send RATE CONTROL control frames in uplink (to the CN) to control the rates in downlink. The SRNC may also send RATE CONTROL control frames in downlink (to the UE) to control the rates in uplink. The Iu Rate Control procedures for both directions are independent of each other, i.e. different rates may be permitted in uplink and downlink, see figure D.1.
+
+
+
+Figure D.1: Rate Control for uplink and downlink. This sequence diagram shows the interaction between a User Equipment (UE), a Serving Radio Network Controller (SRNC), and a Core Network (CN). For uplink data flow: UE sends 'User Data with uplink Rates' to SRNC, which then forwards 'User Data' to CN. SRNC sends a 'Rate Control for uplink' message back to UE. For downlink data flow: CN sends 'User Data with downlink Rates' to SRNC, which then forwards 'User Data' to UE. SRNC sends a 'Rate Control for downlink' message to CN.
+
+Figure D.1: Rate Control for uplink and downlink
+
+The rates associated with the service could be rank ordered from "lower" to "higher" according to their SDU bit rates and RFCI values, with RFCI=0 having the lowest rate. A rate lower than the currently allowed maximum rate shall not be forbidden while a higher rate is forbidden. In order to stabilise the Iu Rate Control procedure and its influences on the radio link and the network, typically only one additional rate shall be forbidden or permitted in subsequent RATE CONTROL control frames.
+
+In some cases, as TrFO and TFO, the rate is also controlled by the remote partner at the other end of the Iu UP. The SRNC may then also receive RATE CONTROL control frames in downlink (from the CN) controlling the rates in uplink. Only rates that are permitted by both sides for one direction shall be used in that direction. The SRNC shall therefore combine these RATE CONTROL control frames from the CN with its own control frames for the uplink direction by taking the RATE CONTROL control frame with the lowest maximum rate and shall send this RATE CONTROL control frame downlink to the UE. This combination is denoted in figure D.2 with "Rate Control (CN $\oplus$ RNC)".
+
+
+
+Figure D.2: Distributed Rate Control for uplink and downlink. This sequence diagram shows a more complex interaction between UE, SRNC, and CN. For uplink: CN sends 'Rate Control (CN) for uplink' to SRNC, which combines it and sends 'Rate Control (CN ⊕ RNC) for uplink' to UE. UE sends 'User Data with (CN ⊕ RNC) Rates' to SRNC, which forwards 'User Data' to CN. For downlink: SRNC sends 'Rate Control (RNC) for downlink' to CN. CN sends 'User Data with (RNC ⊕ CN) Rates' to SRNC, which forwards 'User Data' to UE.
+
+Figure D.2: Distributed Rate Control for uplink and downlink
+
+# --- Annex E (informative): Change History
+
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New |
+|---------|-------|-----------|------|-----|------------------------------------------------------------|--------|
+| 12/2008 | - | - | - | - | Creation of Rel-8 version based on v7.3.0 | 8.0.0 |
+| 12/2009 | - | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 |
+| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 |
+| 03/2011 | | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 |
+| 06/2011 | RP-52 | SP-110685 | 0134 | - | Reference review outcome in TS 25.415 | 10.1.0 |
+| 09/2012 | | | | | Update to Rel-11 version (MCC) | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25422/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-11/25_series/25422/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca6737b54463a8ca359b8e49ef1a6f2b35b38bc4
--- /dev/null
+++ b/marked/Rel-11/25_series/25422/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf15f34be3cfc496553a9a67c9aa04ade9ad91d8e7c95a301641b31c0ca92493
+size 48581
diff --git a/marked/Rel-11/25_series/25422/raw.md b/marked/Rel-11/25_series/25422/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8dac63b0ecdaab73aeba709d757b81758be9af8b
--- /dev/null
+++ b/marked/Rel-11/25_series/25422/raw.md
@@ -0,0 +1,208 @@
+
+
+
+
+# Keywords ---
+
+UMTS, radio
+
+# --- Contents
+
+| | | |
+|------------------------|--------------------------------------------------|----|
+| 1 | Scope..... | 5 |
+| 2 | References..... | 5 |
+| 3 | Abbreviations..... | 6 |
+| 4 | Data Link Layer ..... | 7 |
+| 4.1 | ATM Transport Option ..... | 7 |
+| 4.2 | IP Transport Option..... | 7 |
+| 5 | RNSAP Signalling Bearer..... | 7 |
+| 5.1 | Introduction ..... | 7 |
+| 5.2 | Signalling Bearer..... | 8 |
+| 5.2.1 | ATM Option 1 ..... | 8 |
+| 5.2.2 | ATM Option 2 ..... | 8 |
+| 5.2.3 | IP Transport Option..... | 9 |
+| 5.3 | Services Provided by the Signalling Bearer ..... | 9 |
+| Annex A (informative): | Change history..... | 10 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the standards for Signalling Transport to be used across Iur Interface. Iur Interface is a logical interface between the two RNC of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. The present document describes how the RNSAP signalling messages are transported between the two RNCs.
+
+# --- 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] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN Signalling ATM Adaptation Layer (SAAL) - Overview description".
+- [2] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".
+- [3] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer - Service Specific Co-ordination Function for signalling at the Network Node Interface (SSCF AT NNI)".
+- [4] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
+- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [6] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer specification: Type 5 AAL".
+- [7] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [8] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages".
+- [9] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [10] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [11] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide".
+- [12] ITU-T Recommendation Q.716 (1993-03): "Signalling System No. 7 - Signalling Connection Control Part (SCCP) performance".
+- [13] IETF RFC 791 (September 1981): "Internet Protocol".
+- [14] IETF RFC 1483 (July 1993): "Multi protocol Encapsulation over ATM Adaptation Layer 5".
+- [15] IETF RFC 2225 (April 1998): "Classical IP and ARP over ATM".
+- [16] IETF RFC 2960 (October 2000): "Stream Control Transmission Protocol".
+- [17] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)".
+- [18] IETF STD 51, RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)".
+
+- [19] IETF STD 51, RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [20] IETF RFC 2507 (1999-02): "IP header compression".
+- [21] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [22] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [23] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [24] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (Ipv6) Specification".
+- [25] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [26] Void [27] IETF RFC 3153 (2001-08): "PPP Multiplexing".
+- [28] IETF RFC 2364 (1998-07): "PPP over AAL5".
+- [29] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture".
+- [30] IETF RFC 3309 (2002-09): "SCTP Checksum Change".
+- [31] ANSI T1.111-2001: "Signalling System Number 7 (SS7) - Message Transfer Part (MTP)".
+- [32] ANSI T1.112-2001: "Signaling System Number 7 (SS7) -- Signaling Connection Control Part (SCCP)".
+- [33] ANSI T1.645-1995 (R2003): "B-ISDN Signaling ATM Adaptation Layer - Service Specific Coordination Function for Support of Signaling at the Network Node Interface (SSCF at the NNI)".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-----------|----------------------------------------------------------|
+| AAL | ATM Adaptation Layer |
+| AAL2 | ATM Adaptation Layer 2 |
+| AAL5 | ATM Adaptation Layer 5 |
+| ATM | Asynchronous Transfer Mode |
+| DiffServ | Differentiated Services |
+| HDLC | High level Data Link Control |
+| IP | Internet Protocol |
+| IPv4 | Internet Protocol, version 4 |
+| IPv6 | Internet Protocol, version 6 |
+| M3UA | SS7 MTP3 User Adaptation layer |
+| ML/MC-PPP | Muti-Link/Multi-Class PPP |
+| MPLS | Multiprotocol Label Switching |
+| MTP3-B | Message Transfer Part level 3 for Q.2140 |
+| PLMN | Public Land Mobile Network |
+| PPP | Point-to-Point protocol |
+| PPPMux | PPP Multiplexing |
+| QoS | Quality of Service |
+| RNC | Radio Network Controller |
+| RNSAP | Radio Network Subsystem Application Part |
+| SAAL-NNI | Signalling ATM Adaptation Layer - Network Node Interface |
+| SCCP | Signalling Connection Control Part |
+| SCTP | Stream Control Transmission Protocol |
+| SSCF | Service Specific Co-ordination Function |
+| SSCOP | Service Specific Connection Oriented Protocol |
+| UE | User Equipment |
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the radio network control plane according to ITU-T Rec. I.361 [5]. The structure of the cell header used in the UTRAN Iur interface is the cell header format and encoding at NNI (see figure 3 of ITU-T Rec. I.361 [5]).
+
+## 4.2 IP Transport Option
+
+A UTRAN Node supporting IP transport option shall support PPP protocol with HDLC framing IETF RFC 1661 [18], IETF RFC 1662 [19].
+
+Note: This does not preclude the single implementation and use of any other data link layer protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [27], IETF RFC 2364 [28]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [29]), etc.) fulfilling the UTRAN requirements toward the upper layers.
+
+An RNC using IP transport option having interfaces connected via slow bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression IETF RFC 2507 [20] and the PPP extensions ML/MC-PPP IETF RFC 1990 [21], IETF RFC 2686 [22]. In this case, negotiation of header compression IETF RFC 2507 [20] over PPP shall be performed via IETF RFC 2509 [23].
+
+# --- 5 RNSAP Signalling Bearer
+
+## 5.1 Introduction
+
+This subclause specifies the Signalling Bearer protocol stack that supports the RNSAP signalling protocol.
+
+The following requirements on the RNSAP signalling bearer can be stated:
+
+- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode;
+- provide separate independent connections for distinguishing transactions with individual UEs;
+- supervise the "UE connections" and provide connection status information to the Upper Layers for individual UEs;
+- provide networking and routing functions;
+- provide redundancy in the signalling network;
+- provide load sharing.
+
+## 5.2 Signalling Bearer
+
+This subclause refers to specifications of the Signalling Bearer for the Radio Network Layer protocols. As shown in figure 1, the standard allows operators to choose one out of three protocol suites for transport of SCCP messages.
+
+
+
+The diagram illustrates three protocol stacks for RNSAP transport, all sharing a common RNSAP layer at the top and an SCCP-SAP interface. The first stack (ATM Transport Option 1) includes SCCP, MTP3-B, SSCF-NNI, SSCOP, AAL5, and ATM. The second stack (ATM Transport Option 2) includes SCCP, M3UA, SCTP, IP, Data Link, and PHY. The third stack (IP Transport Option) includes SCCP, M3UA, SCTP, IP, Data Link, and PHY.
+
+Figure 1: Signalling bearer for RNSAP. The diagram shows three protocol stacks for RNSAP transport. All three start with RNSAP at the top, connected via an SCCP-SAP. The first stack (ATM Transport Option 1) consists of SCCP, MTP3-B, SSCF-NNI, SSCOP, AAL5, and ATM. The second stack (ATM Transport Option 2) consists of SCCP, M3UA, SCTP, IP, Data Link, and PHY. The third stack (IP Transport Option) consists of SCCP, M3UA, SCTP, IP, Data Link, and PHY.
+
+Figure 1: Signalling bearer for RNSAP
+
+### 5.2.1 ATM Option 1
+
+1. **SCCP** ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8]/ ITU-T Rec. Q.713 [9]/ ITU-T Rec. Q.714 [10]/ ITU-T Rec. Q.715 [11]/ ITU-T Rec. Q.716[12] or ANSI T1.112-2001 [32] provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis.
+2. **MTP3-B** ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31] provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded.
+3. **SAAL-NNI** ITU-T Rec. Q.2100 [1] consists of the following sub-layers: - **SSCF** ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 [33], - **SSCOP** ITU-T Rec. Q.2110 [2] and - **AAL5** ITU-T Rec. I.363.5 [6]. The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells.
+4. **ATM** ITU-T Rec. I.361 [5].
+
+### 5.2.2 ATM Option 2
+
+1. **SCCP**. See subclause 5.2.1
+2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 - User Adaptation Layer" IETF RFC 3332 [17] also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall support both the client and the server functionality towards another RNC. This enables the RNC to report to another RNC when it is a newly introduced entity in the network.
+
+3. **SCTP** refers to the Stream Control Transmission Protocol IETF RFC 2960 [16] developed by the Sigtran working group of the IETF for the purposes of transporting various signalling protocols over IP networks. The checksum method specified in RFC 3309 IETF RFC 3309 [30] shall be used instead of the method specified in IETF RFC 2960 [16].
+4. **IP** IETF RFC 791 [13] over ATM is defined in IETF RFC 1483 [14] and IETF RFC 2225 [15].
+5. **ATM** ITU-T Rec. I.361 [5].
+
+### 5.2.3 IP Transport Option
+
+1. **SCCP**. See subclause 5.2.1.
+2. **M3UA**: See subclause 5.2.2.
+3. **SCTP**. See subclause 5.2.2. In addition, Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint.
+4. **IP**. An IP UTRAN Node shall support IPv6 IETF RFC 2460 [24]. The support of IPv4 IETF RFC 791 [13] is optional.
+
+NOTE: This does not preclude single implementation of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network
+
+IP Differentiated Services code point marking IETF RFC 2474 [25] shall be supported. The Diffserv code point may be determined from the application parameters.
+
+5. Data link layer is as specified in chapter 4.2.
+
+## 5.3 Services Provided by the Signalling Bearer
+
+When considering the requirements that the upper layers, i.e. RNSAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in the references ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8]/ ITU-T Rec. Q.713 [9]/ ITU-T Rec. Q.714 [10]/ ITU-T Rec. Q.715 [11]/ ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32].
+
+# --- Annex A (informative): Change history
+
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New |
+|---------|-------|-----------|------|-----|------------------------------------------------------------|--------|
+| 12/2008 | - | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 |
+| 12/2009 | - | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 |
+| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 |
+| 03/2011 | | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 |
+| 06/2011 | 52 | RP-110684 | 0024 | - | Correction of references. | 10.1.0 |
+| 09/2012 | | | | | Update to Rel-11 version (MCC) | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/25_series/25423/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-11/25_series/25423/04dc3838022e96d8d5548bb1b777b38c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49b1a48a5c8ffaaa60049e6cccd001be7b391f1f
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/04dc3838022e96d8d5548bb1b777b38c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f432ee387a3801b5365063a90704cc337443f26ce67d03f5d0cedbc5ab3a4af
+size 10576
diff --git a/marked/Rel-11/25_series/25423/0915f7aa46dc1d36868fb9fba8db3dac_img.jpg b/marked/Rel-11/25_series/25423/0915f7aa46dc1d36868fb9fba8db3dac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b3a5219713b7bdcc2657b74ec6ba848a89a368e
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/0915f7aa46dc1d36868fb9fba8db3dac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dfb988ecf481c744b409cc80466437e9123b752b0835007130c6d4dfad00460
+size 17159
diff --git a/marked/Rel-11/25_series/25423/0a6bfc1efcbd3366f91d098cfc02046e_img.jpg b/marked/Rel-11/25_series/25423/0a6bfc1efcbd3366f91d098cfc02046e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2fc31a4dfcd1cb5a2f15f9f2891961e486d73240
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/0a6bfc1efcbd3366f91d098cfc02046e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0351eb165a66159164ddce4ff59679e864e99f0af28e320db1fa3412d0a34cf9
+size 12921
diff --git a/marked/Rel-11/25_series/25423/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-11/25_series/25423/0f1767577a073167eb9628d72034e083_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b01d2cad7fba5f9ce40847d8fecbbbb4d40c5408
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/0f1767577a073167eb9628d72034e083_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:478cca96887a9c4f65ce5628c67f485e005578219ea5bb4d3753c90d67e8e0a7
+size 3986
diff --git a/marked/Rel-11/25_series/25423/11878e99fcab03106ffd86c24fbd11c9_img.jpg b/marked/Rel-11/25_series/25423/11878e99fcab03106ffd86c24fbd11c9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61251482a995315796482fdac28b0a7e0cb0755b
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/11878e99fcab03106ffd86c24fbd11c9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1aa1b2736f425c77c9f6511e2ee4fc0616e8e9f36cb9dbc74efcdc7a3420c28
+size 10510
diff --git a/marked/Rel-11/25_series/25423/164fae2c6490ee9f4cbf3c05758ecc57_img.jpg b/marked/Rel-11/25_series/25423/164fae2c6490ee9f4cbf3c05758ecc57_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f110ba5fdb9da61ee60440d48c6ff6853026c01
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/164fae2c6490ee9f4cbf3c05758ecc57_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05c5b20891389af2ffecf69150cb03ad7361c2db1c58208bb770e9d37e47003e
+size 8318
diff --git a/marked/Rel-11/25_series/25423/1662582b76eec39c269b6ae14fe5d5f1_img.jpg b/marked/Rel-11/25_series/25423/1662582b76eec39c269b6ae14fe5d5f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7be179e432fb3c0e3a5c852110b69cedbbfa0d66
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/1662582b76eec39c269b6ae14fe5d5f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86999ede30de5d0268327f7e0759cb3cf3f0b6eb4713f91a80d555ba7603be84
+size 11353
diff --git a/marked/Rel-11/25_series/25423/1b3c088f23921d4eeb45ffc05586e59b_img.jpg b/marked/Rel-11/25_series/25423/1b3c088f23921d4eeb45ffc05586e59b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..016d1ecc1f6132aeca3c4325b80092900b004c53
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/1b3c088f23921d4eeb45ffc05586e59b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf4a4923a57615426bd8418eddbb95d78ad951678f057f13f2f474806b91600d
+size 7025
diff --git a/marked/Rel-11/25_series/25423/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-11/25_series/25423/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..720979ca24d48a6057557caac28c65bef937b7a4
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:178aa8871e731fa1ac1857e2807f109d58f517b574e6ebd09432c22af0d79386
+size 8706
diff --git a/marked/Rel-11/25_series/25423/1c79f31a718d63814feb28ab46f64f19_img.jpg b/marked/Rel-11/25_series/25423/1c79f31a718d63814feb28ab46f64f19_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d16d1963b42a7cfb6276201f9aad5b31d2eec98
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/1c79f31a718d63814feb28ab46f64f19_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aea8000be540c927be5afa89db9d54a8a8141c68446e40ef4721b8b158a8a174
+size 13322
diff --git a/marked/Rel-11/25_series/25423/2119293733c74fc64de88aefd597f4bb_img.jpg b/marked/Rel-11/25_series/25423/2119293733c74fc64de88aefd597f4bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa57ecbfa0d51b500320feb00b874d53524dfc29
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/2119293733c74fc64de88aefd597f4bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0d1c822cbb20bbc52709b53a8defe5f2858dcb2309989b29659e2b5ea8f2ea4
+size 13036
diff --git a/marked/Rel-11/25_series/25423/22481ca9b0500af295e4999a041c1cf4_img.jpg b/marked/Rel-11/25_series/25423/22481ca9b0500af295e4999a041c1cf4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93b8b5afcdfa70a383ac491a15eec43f878afb27
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/22481ca9b0500af295e4999a041c1cf4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f06afe7c76a6de43f6c4603d9ef5ada9cf9b73335a7411860ef7635f057266b
+size 10886
diff --git a/marked/Rel-11/25_series/25423/22fe85c0c46c139769f6d847570e1863_img.jpg b/marked/Rel-11/25_series/25423/22fe85c0c46c139769f6d847570e1863_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89b732bda174d920b6be6258d1c0e32526298a83
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/22fe85c0c46c139769f6d847570e1863_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9667b2c8f349762162ad861a03d9d0c1f68073ba6fbf76d93220f0e031a6729
+size 14656
diff --git a/marked/Rel-11/25_series/25423/29696d66e33e11fa83d6385ca8712f41_img.jpg b/marked/Rel-11/25_series/25423/29696d66e33e11fa83d6385ca8712f41_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2051ca95b4f44ee484ee2bd5a2535bb861a83af7
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/29696d66e33e11fa83d6385ca8712f41_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a1ac4602401794cc28b443bb4a421b045649d47a819f838665c5f00a47b7f3a
+size 10037
diff --git a/marked/Rel-11/25_series/25423/2a7bc05444905929ebc1e54d2210c2ab_img.jpg b/marked/Rel-11/25_series/25423/2a7bc05444905929ebc1e54d2210c2ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3321fd47e7860ff3bff64c1c53e22295533bbf08
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/2a7bc05444905929ebc1e54d2210c2ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58d34e8d94e98c2eb3757b7283742c38e2b7c72fbb6d2c04b7e3686b7339ed84
+size 12045
diff --git a/marked/Rel-11/25_series/25423/2df09d249c38abee55dbf0526dd6da0a_img.jpg b/marked/Rel-11/25_series/25423/2df09d249c38abee55dbf0526dd6da0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4bdc2c86f91935cd03e0a3a97f0694d77cff7f50
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/2df09d249c38abee55dbf0526dd6da0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d771aecf25b90bc6853f40d1bf390acefc14e4cc15b0811a5113a01c1525b41
+size 16411
diff --git a/marked/Rel-11/25_series/25423/30caf467423c4eb6326bddd4e8931a7c_img.jpg b/marked/Rel-11/25_series/25423/30caf467423c4eb6326bddd4e8931a7c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a93694354f4002c91fe96ed71ff11e6da1a86ab7
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/30caf467423c4eb6326bddd4e8931a7c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e66a13c5f9284a3f50eac3d055520b9c5d449bb89802efb6fe6b849808cf76e1
+size 9403
diff --git a/marked/Rel-11/25_series/25423/32f3dbb543933c01efffae559bfd1f13_img.jpg b/marked/Rel-11/25_series/25423/32f3dbb543933c01efffae559bfd1f13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e53d526ca61c107845a2f769a1b831188afb7db
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/32f3dbb543933c01efffae559bfd1f13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4982489ae8abc8974a86c7963aaab9b5d10e7f6b3fd79b176e11db0420dd9284
+size 12695
diff --git a/marked/Rel-11/25_series/25423/35a7554182eb055209552843f341a1ae_img.jpg b/marked/Rel-11/25_series/25423/35a7554182eb055209552843f341a1ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c90a8e44835669a2bc56eeb355b09b21ecd027e
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/35a7554182eb055209552843f341a1ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ab83640b600c797675ca6bc7008eed1e2a0ad8ee1e249e420727160d7987864
+size 20980
diff --git a/marked/Rel-11/25_series/25423/3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg b/marked/Rel-11/25_series/25423/3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45aa14447d10e3654385e7fd285ce67235f45464
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8227747bd57912ea671d5f168be2ef9b7c9d36805f817a0f7bca1260b582b9b
+size 37005
diff --git a/marked/Rel-11/25_series/25423/40b1d147c829cd50e0b9f2bb4782de9e_img.jpg b/marked/Rel-11/25_series/25423/40b1d147c829cd50e0b9f2bb4782de9e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce9299f2f359ca053b05a5879cdb490be8f793d7
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/40b1d147c829cd50e0b9f2bb4782de9e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef3fc88ba10ef193b1cddcc35f4eeaeaac224b14580b7fc488339602e17289ab
+size 11172
diff --git a/marked/Rel-11/25_series/25423/43d1301c386b8a428ec992d9876aa5f5_img.jpg b/marked/Rel-11/25_series/25423/43d1301c386b8a428ec992d9876aa5f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..deeecdc47a1090d9d79d1408d11bc6d49de78dee
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/43d1301c386b8a428ec992d9876aa5f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:971a66d855257e177e005f2c62e36de60b19db00423a7502e71f8e9c1ecd2c2d
+size 8366
diff --git a/marked/Rel-11/25_series/25423/4a02f1724b34505019a7a53f3333f33c_img.jpg b/marked/Rel-11/25_series/25423/4a02f1724b34505019a7a53f3333f33c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9854e501424ea3222a7c9574329b4d1a9bce609
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/4a02f1724b34505019a7a53f3333f33c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f484c3ed352e34b387f464f50a18a09d1d0073b84f50c087b5499a6f8e1164b
+size 12112
diff --git a/marked/Rel-11/25_series/25423/4a94ebc4d41217ce3083a255bfb9c538_img.jpg b/marked/Rel-11/25_series/25423/4a94ebc4d41217ce3083a255bfb9c538_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65294bcc4660e8e8a62d32b9a898dc63138cf506
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/4a94ebc4d41217ce3083a255bfb9c538_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e75b343d23d8d57b3fb8643a7633e890cf386f6a65a89fd2b109141a0797136b
+size 12825
diff --git a/marked/Rel-11/25_series/25423/4c4198618f328b0d0e20dbbc61586b6a_img.jpg b/marked/Rel-11/25_series/25423/4c4198618f328b0d0e20dbbc61586b6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9bb9cccf50442989494e44d01f48b08f3915623c
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/4c4198618f328b0d0e20dbbc61586b6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c6cbdea1e2e086f722f7b6d068d0c8c14c56edbe6910e3821d351b32efc4557
+size 34800
diff --git a/marked/Rel-11/25_series/25423/4d7f667796a8cdcdd745e953ac11e289_img.jpg b/marked/Rel-11/25_series/25423/4d7f667796a8cdcdd745e953ac11e289_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4abfdb426c93b4f74ce8279deecdb7e3a7df9a89
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/4d7f667796a8cdcdd745e953ac11e289_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6b4ac5f1a48ccd5005eb0ffbfd9c3c70757016edcf947e3dbee766fb2819323
+size 8929
diff --git a/marked/Rel-11/25_series/25423/51cdb2d7f658d676182c2605268f1056_img.jpg b/marked/Rel-11/25_series/25423/51cdb2d7f658d676182c2605268f1056_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2be8ee8b4fb16a8a3bc7b47be888fc9072a6547b
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/51cdb2d7f658d676182c2605268f1056_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b64cf78108e3f9ca15fd78f1a1f04d30d3ced5c77f6ad94b63973fdf6134de7
+size 101311
diff --git a/marked/Rel-11/25_series/25423/529a7bdc5cbe385e05575e2e77ffc7fa_img.jpg b/marked/Rel-11/25_series/25423/529a7bdc5cbe385e05575e2e77ffc7fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16b29ab0ee6261de6ba9e9e6564bf19243bad740
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/529a7bdc5cbe385e05575e2e77ffc7fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00697a34128554c46539a802073d9aa38fd715880a7a57790e1a695500c18115
+size 74569
diff --git a/marked/Rel-11/25_series/25423/54d24edc8f9ee7fc1d7850c1270a1fda_img.jpg b/marked/Rel-11/25_series/25423/54d24edc8f9ee7fc1d7850c1270a1fda_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..180414380e84eb62a666d0b7374c48869a77c16f
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/54d24edc8f9ee7fc1d7850c1270a1fda_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba336238fafbdf9b1e932f999ddf48242b59b7678d89802a1fa480785cb53e10
+size 8733
diff --git a/marked/Rel-11/25_series/25423/5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg b/marked/Rel-11/25_series/25423/5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..906e7f85835d4522d28c85c4c73adf61536ab6e7
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99c5ab8409489c5a451ddb0a2cb06a2132c4ed245f2cf16216ac3ab2b7b1ff15
+size 16109
diff --git a/marked/Rel-11/25_series/25423/5879500ca01e1a2521654beff6c289a4_img.jpg b/marked/Rel-11/25_series/25423/5879500ca01e1a2521654beff6c289a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3428d780daab91a6eabd954fbbf28fa6a8a5a54a
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/5879500ca01e1a2521654beff6c289a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f05c1451354433734643e5e2b280bacb95d4568078bec987a091d234c6551b53
+size 29043
diff --git a/marked/Rel-11/25_series/25423/5aa18c874a16d82357f315358d51b5e1_img.jpg b/marked/Rel-11/25_series/25423/5aa18c874a16d82357f315358d51b5e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ef539a9574f47f0d244214b1c11d049ea4b14c7
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/5aa18c874a16d82357f315358d51b5e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07b51998756131d39836216f362a96fa1050a406475186eed4537649363e36e3
+size 9658
diff --git a/marked/Rel-11/25_series/25423/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-11/25_series/25423/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..904aee6b60d8ed3dc3045149df758675611651b2
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9600b2bff448c493c61b2ebeb9ae4108f8813b334c1f5e473cb53305187a57f
+size 9485
diff --git a/marked/Rel-11/25_series/25423/5cb74e3ca5034698d7eab12de06f8763_img.jpg b/marked/Rel-11/25_series/25423/5cb74e3ca5034698d7eab12de06f8763_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b31b8874b947fa0bf375d3380058960bbd79de2
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/5cb74e3ca5034698d7eab12de06f8763_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:408e0fb5c417fa162741c6618ce5db781335f19a13632920210ed7f95307f231
+size 10988
diff --git a/marked/Rel-11/25_series/25423/6c16bb5c29edb38bf5375e6dfd69832e_img.jpg b/marked/Rel-11/25_series/25423/6c16bb5c29edb38bf5375e6dfd69832e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b03802f23df05800fc6e07ac5e661d98c67953f
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/6c16bb5c29edb38bf5375e6dfd69832e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8376c5a3b89ba635cf4594f1d5e3941b43e9c776c2ba831db3a41d9bb342a6a5
+size 74631
diff --git a/marked/Rel-11/25_series/25423/6c6c57fd6906a27054b02c6be574f417_img.jpg b/marked/Rel-11/25_series/25423/6c6c57fd6906a27054b02c6be574f417_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddf53c6f3528d1aa544a6662e34d895f83700bb5
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/6c6c57fd6906a27054b02c6be574f417_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09ddd794c9b141c5189ea87d673eba285571051136a22f854ac611cd052140d9
+size 9908
diff --git a/marked/Rel-11/25_series/25423/739d9761cdbb47394f979141864a8de6_img.jpg b/marked/Rel-11/25_series/25423/739d9761cdbb47394f979141864a8de6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76998eb53c921c73bf8cc3235bb76bd67c3793f0
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/739d9761cdbb47394f979141864a8de6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:851785990f24083d97ef50e6d18e9165675dc28cd847e301256a317a0a80fc37
+size 13276
diff --git a/marked/Rel-11/25_series/25423/7591d62243861662f4e2e10f0746e903_img.jpg b/marked/Rel-11/25_series/25423/7591d62243861662f4e2e10f0746e903_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdf61869d0cfd55b291c552363f6df52c9610b13
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/7591d62243861662f4e2e10f0746e903_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:085cd034842244cde7e8f15da91f5673f86b2ae913bbac9044a69eea43554cf1
+size 61504
diff --git a/marked/Rel-11/25_series/25423/76fcd3a0d306d750251ab1a9df544fe1_img.jpg b/marked/Rel-11/25_series/25423/76fcd3a0d306d750251ab1a9df544fe1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90aeed602ac68934812cfb6b6add147bec5220b1
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/76fcd3a0d306d750251ab1a9df544fe1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c63ce3d2672cc20d1f6609c23cb6328a9359a0bc02e0d53a5ba16b2396450813
+size 35314
diff --git a/marked/Rel-11/25_series/25423/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-11/25_series/25423/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8b2c4cccaf03cf6bf28bbac8a11b8cf91ac12b5
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d77b9c1c753685701dbca0bb981fed8927e1d494cd13dc61898c89af7e6516f
+size 16512
diff --git a/marked/Rel-11/25_series/25423/7b8b192e2853ef28d28eff0241ebe86b_img.jpg b/marked/Rel-11/25_series/25423/7b8b192e2853ef28d28eff0241ebe86b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cca93b7b9e7fe0ef237f6b3c66c646380d772bd4
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/7b8b192e2853ef28d28eff0241ebe86b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64648149e3ac652e570bd8e4250845b12f46a3ae81644943ba4f8e6f2228dd1b
+size 13528
diff --git a/marked/Rel-11/25_series/25423/7cea8cfa9ce0cdc9fe5f3f27384ed943_img.jpg b/marked/Rel-11/25_series/25423/7cea8cfa9ce0cdc9fe5f3f27384ed943_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22687dae9621cfc7c1d607e0e124b52842db0a3f
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/7cea8cfa9ce0cdc9fe5f3f27384ed943_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85ed0291292c05f1702f9975c3f9459999a9e48e35a23cba5971c11ee628561d
+size 7931
diff --git a/marked/Rel-11/25_series/25423/7eca4b22c05b3134e3c099899a0a1989_img.jpg b/marked/Rel-11/25_series/25423/7eca4b22c05b3134e3c099899a0a1989_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bece02ed3a575c03b143bf2f2acbc652998a4bc2
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/7eca4b22c05b3134e3c099899a0a1989_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:286cb607e82cc533224a95edfb3ae20ebe7ad639907876dd08ece34ed812da69
+size 10916
diff --git a/marked/Rel-11/25_series/25423/873275851761a3173ee66f649493aea3_img.jpg b/marked/Rel-11/25_series/25423/873275851761a3173ee66f649493aea3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64d1eada93180c7696eb7def5c974e2051c5dd02
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/873275851761a3173ee66f649493aea3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8219fbc8c6844ae3ab16d6abf4e693d69630611c56bbbabbaeb70d52920d802c
+size 19420
diff --git a/marked/Rel-11/25_series/25423/8b663a8371fe20ff0f4dff9da6bf7f45_img.jpg b/marked/Rel-11/25_series/25423/8b663a8371fe20ff0f4dff9da6bf7f45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9fa445105212659b0ebfd2a92221d4605103ad1f
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/8b663a8371fe20ff0f4dff9da6bf7f45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c07847bb4b70977cd3826b9d6683873710c2f3915d3cd100fdee03776d7c2694
+size 10750
diff --git a/marked/Rel-11/25_series/25423/8bc810ce7e97c39e9d29aceff0ec222e_img.jpg b/marked/Rel-11/25_series/25423/8bc810ce7e97c39e9d29aceff0ec222e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f9499ca15c83a5045251a8f40a29f3d72e5f4fc
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/8bc810ce7e97c39e9d29aceff0ec222e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c961045d81a1706e10ec3cc3146601df23616f2b48927badbc34b7d6c02a1f49
+size 16774
diff --git a/marked/Rel-11/25_series/25423/8ce9decfe331b11186a76f813e5dd62c_img.jpg b/marked/Rel-11/25_series/25423/8ce9decfe331b11186a76f813e5dd62c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..facd916dc2f7bcea3bf30c27bb70bfc89c30b3fb
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/8ce9decfe331b11186a76f813e5dd62c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f3ca763d1a6e360828c583d69ec11e8c3578cd7d0349de1402a9af93f96f14f
+size 35494
diff --git a/marked/Rel-11/25_series/25423/8e2b6b0d92809964fe902cdb1272fb39_img.jpg b/marked/Rel-11/25_series/25423/8e2b6b0d92809964fe902cdb1272fb39_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86c55515bc0ec46483e7f3feed9a94e47f10a25b
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/8e2b6b0d92809964fe902cdb1272fb39_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50fc0348928e0f9b594995e13a46b2297256a129c6843217e7170ff31a795f27
+size 10281
diff --git a/marked/Rel-11/25_series/25423/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg b/marked/Rel-11/25_series/25423/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..780c862f93243a6d6307124352b1040358f7a7fc
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b73e05b88daa2d33284134d742d7c2b6a610ff9e7f1d46851f9e6fcda8149765
+size 11075
diff --git a/marked/Rel-11/25_series/25423/98846e09f417ec7e22831cb4e9367492_img.jpg b/marked/Rel-11/25_series/25423/98846e09f417ec7e22831cb4e9367492_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b51b65c3b553fb9e4e0adc2368e9c20ff70fdfd
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/98846e09f417ec7e22831cb4e9367492_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:47959003f1808fb167b1f4cb6b86f0a454abb7af8ea2a1aa9f854624974876c1
+size 9968
diff --git a/marked/Rel-11/25_series/25423/99bf828c64968a93d77f4b8e0ac5d732_img.jpg b/marked/Rel-11/25_series/25423/99bf828c64968a93d77f4b8e0ac5d732_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..600b8ffa08c58279f3f90e7e896aaeff8e72df29
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/99bf828c64968a93d77f4b8e0ac5d732_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2543ccd5233fe60d7754649f9d6e816f24c8903182f458b380f2d4c6776069a5
+size 25080
diff --git a/marked/Rel-11/25_series/25423/9b8575279d417902c70db5535adc80e3_img.jpg b/marked/Rel-11/25_series/25423/9b8575279d417902c70db5535adc80e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..548afc0d3863ba3cbc25681d93a3da19e5fe747e
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/9b8575279d417902c70db5535adc80e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d3cd8c0a9b37d8b29858770ba8e214f03e708aa0b46191e398c52c88537146a
+size 10082
diff --git a/marked/Rel-11/25_series/25423/a02f5bd95c2fe443da73c13ae88d9d69_img.jpg b/marked/Rel-11/25_series/25423/a02f5bd95c2fe443da73c13ae88d9d69_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61f97d7e1df65475da926ac587f026bca5481589
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/a02f5bd95c2fe443da73c13ae88d9d69_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a712ca94c2b8ac6eb74e4a0e98167d2dc03be02ae0feb6dc90d1ba92078bfbd3
+size 62277
diff --git a/marked/Rel-11/25_series/25423/a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg b/marked/Rel-11/25_series/25423/a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff5f025f49835e1148d11a582efe886da13f4cba
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13893ac452508a6571c26256fa0fe37c8b6084ea14a96a317e7fe32f94eb427d
+size 15715
diff --git a/marked/Rel-11/25_series/25423/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-11/25_series/25423/a3472689858b068ef469213682965325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c60af554eb881c2d6e1e1365bdd777ae0f94eae
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/a3472689858b068ef469213682965325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f21384b4ce18a33ed5e680256b133e5803cdb6856ee5a81d8d0f2aed4d017d1
+size 7397
diff --git a/marked/Rel-11/25_series/25423/a76686b464c2226186201244b757849c_img.jpg b/marked/Rel-11/25_series/25423/a76686b464c2226186201244b757849c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89df851254a2acaf9333133ce73e61291203548d
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/a76686b464c2226186201244b757849c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d67756ef5b629f3288db161ca5c8bfcba8182265d6368ace7339f48cc7e764fb
+size 13904
diff --git a/marked/Rel-11/25_series/25423/adf8611a07655d290aeeb6f197afeb77_img.jpg b/marked/Rel-11/25_series/25423/adf8611a07655d290aeeb6f197afeb77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e69ce6f4db7672b53558dbe17d34a75140f912b
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/adf8611a07655d290aeeb6f197afeb77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a138449f376d77faa0bf5766e185f7d6eaec61eca5293ead4ea4b0746d3b5ff2
+size 75150
diff --git a/marked/Rel-11/25_series/25423/ae6a6693b862ab33ece3b16176efc61c_img.jpg b/marked/Rel-11/25_series/25423/ae6a6693b862ab33ece3b16176efc61c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b32ce36a8e123c593bfd9465b593a0a3477b8070
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/ae6a6693b862ab33ece3b16176efc61c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03de8761427453060a2bef2838cf3e5f3e615833eeb87d735713fdbbcd016791
+size 19558
diff --git a/marked/Rel-11/25_series/25423/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg b/marked/Rel-11/25_series/25423/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..87ffc9d4406a6f73f1ea7db5ad07063feab20ad4
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8ba6d4fce1d073a6babdcf429ad9d8817815864b84f5ee034cab0795c11ea79
+size 10201
diff --git a/marked/Rel-11/25_series/25423/b46063d0aa9f16339e823bd0179e22e3_img.jpg b/marked/Rel-11/25_series/25423/b46063d0aa9f16339e823bd0179e22e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddee1ca27954d7a0f96ad3207bd63b6ae2618b9d
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/b46063d0aa9f16339e823bd0179e22e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21a74c1189dc6f015200d1d9db103d0a21e09e62ec43117187eb57ac473f32bf
+size 16885
diff --git a/marked/Rel-11/25_series/25423/b5f2a0aca0501abc9bc6d78b7c0f4ae3_img.jpg b/marked/Rel-11/25_series/25423/b5f2a0aca0501abc9bc6d78b7c0f4ae3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f2bb15261b4d139bf26b9a9eafc9fb91ae41418d
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/b5f2a0aca0501abc9bc6d78b7c0f4ae3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb018d42fa8e028f6f52ad20c16fa98a11f346277189cacc65d492e1a268b7b5
+size 10385
diff --git a/marked/Rel-11/25_series/25423/b85f3ca0cec9353ebfbbb0be21b544cf_img.jpg b/marked/Rel-11/25_series/25423/b85f3ca0cec9353ebfbbb0be21b544cf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..177ae5ff765191a74ca2b9cf242303934adb7593
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/b85f3ca0cec9353ebfbbb0be21b544cf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb5555dd31fe61488957e7518925b1f898342f327f14eb53f8cf4781f69dd251
+size 73515
diff --git a/marked/Rel-11/25_series/25423/bc323b6edcaf7b81d9c75666062bbd55_img.jpg b/marked/Rel-11/25_series/25423/bc323b6edcaf7b81d9c75666062bbd55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b89a04dab04aee2a68fde7f6a3041bb3a18062f0
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/bc323b6edcaf7b81d9c75666062bbd55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1b042b3576844adeece6620c6dac385ab398abc39186cb9a82533b799cc3343
+size 7223
diff --git a/marked/Rel-11/25_series/25423/bdeb55b93c90523cd4861f25f2be5dd8_img.jpg b/marked/Rel-11/25_series/25423/bdeb55b93c90523cd4861f25f2be5dd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa5580f581549ae9224e4dc4b8367ad4d21ed50d
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/bdeb55b93c90523cd4861f25f2be5dd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd4f4cb6df3229d57f64be65833576df3828a65c797e36c743feda2c933d6760
+size 75486
diff --git a/marked/Rel-11/25_series/25423/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg b/marked/Rel-11/25_series/25423/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3410d9956d9d3414f98b54ebf33f6393190d4d12
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1dc649073345e7ff475e98fe8234725c7c052a45a29ff8ebabb4a418d68aec1
+size 14297
diff --git a/marked/Rel-11/25_series/25423/c614b03eba4d8f7e0f6ffec64ecb68b0_img.jpg b/marked/Rel-11/25_series/25423/c614b03eba4d8f7e0f6ffec64ecb68b0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1def5bd047793c32f435b7d95eb63af96ba49752
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/c614b03eba4d8f7e0f6ffec64ecb68b0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b9002df680144f806f6925cf2fdfa94b98d135974b2a7f1208a1c4a500a61b5
+size 13050
diff --git a/marked/Rel-11/25_series/25423/c64555b7f91435b01997807dbb4bcc4c_img.jpg b/marked/Rel-11/25_series/25423/c64555b7f91435b01997807dbb4bcc4c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da27bd3301984fe321918a16ee0d0ffa28bee6f6
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/c64555b7f91435b01997807dbb4bcc4c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3fbbe79cf7bc860554ee4cde2d337d25c1aa38b5b48ce7114d037113775f63ac
+size 14046
diff --git a/marked/Rel-11/25_series/25423/ca322f838ed1785bc0de168636f7b426_img.jpg b/marked/Rel-11/25_series/25423/ca322f838ed1785bc0de168636f7b426_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b272949690072123e95ed2244b9e4f5d936f2c1b
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/ca322f838ed1785bc0de168636f7b426_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82d6f6319441f514e12db768231e08e72af9079e05993fec6ae09ce5787503dd
+size 15332
diff --git a/marked/Rel-11/25_series/25423/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Rel-11/25_series/25423/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..550a5ce92e369e61ab5148420266c72f3685a433
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93805711a312a60d0b1c4bd5f1dfb6616b9aed3db19635b52f4e8b85d068b775
+size 11086
diff --git a/marked/Rel-11/25_series/25423/cb711b5d3b333c97df3dd7f7205c5b40_img.jpg b/marked/Rel-11/25_series/25423/cb711b5d3b333c97df3dd7f7205c5b40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44fb60bda8815ba8342bf6fc1ded7e70fb4b53d2
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/cb711b5d3b333c97df3dd7f7205c5b40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e064c88472c346148abdc1f2406d48737fc745e403c5347edeeae852bbc4d9c6
+size 14018
diff --git a/marked/Rel-11/25_series/25423/cbaea7d0d0ec69ce33d0a17ea878c634_img.jpg b/marked/Rel-11/25_series/25423/cbaea7d0d0ec69ce33d0a17ea878c634_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2b805ff47654f0eae915e024bed9fbb42e804ea
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/cbaea7d0d0ec69ce33d0a17ea878c634_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79da26879ab7e97b4a7303f57d0f6ccfbdff1183910dec96db22c800fa79dd1f
+size 23396
diff --git a/marked/Rel-11/25_series/25423/d9cf65b94921cc4457be18d794ac0624_img.jpg b/marked/Rel-11/25_series/25423/d9cf65b94921cc4457be18d794ac0624_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..72e73eb2096b8b9813bc6aa701b9e39db863c709
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/d9cf65b94921cc4457be18d794ac0624_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09352ab78a0cdc964c181911d71b322644727e9b0fdb4551d8d68321629d61a5
+size 10520
diff --git a/marked/Rel-11/25_series/25423/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-11/25_series/25423/db5ab5d386827a5d5f5fad0f45612b90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdedb429e1a9fe54fb0f3af8105162ac86634cc5
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/db5ab5d386827a5d5f5fad0f45612b90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b3eeef0adfd1e0913d6d9d42886932b21bc85b4a25f7805325122592d01d735
+size 13533
diff --git a/marked/Rel-11/25_series/25423/e23c9577e177bf077bac8951a775dd90_img.jpg b/marked/Rel-11/25_series/25423/e23c9577e177bf077bac8951a775dd90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02a6be5995cd257bfe8dbc041bc911c5fe1ae27e
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/e23c9577e177bf077bac8951a775dd90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ab64e6efc712ee6927f563b1722dce794a601af88da49a039834466077b3d6a
+size 21945
diff --git a/marked/Rel-11/25_series/25423/e7b22e97c8d8064fe5f7cdfc4f2a5371_img.jpg b/marked/Rel-11/25_series/25423/e7b22e97c8d8064fe5f7cdfc4f2a5371_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..83a4b3c7565c8d161b17dc5ef8a5e80fc5fade4d
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/e7b22e97c8d8064fe5f7cdfc4f2a5371_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd95e81f5cc50df5c11dd2f0c674c66a2e8ad4cc77f43e992e6fa4fb372b2b19
+size 9409
diff --git a/marked/Rel-11/25_series/25423/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-11/25_series/25423/e94cbc0895c6914a2bb53f150ab7495e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7923c27a0a86c3c449bca2b081e5aeef9ab9e68
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/e94cbc0895c6914a2bb53f150ab7495e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29604ebe84adc300c0f28bc8551c8f3767245184a5b05e1c86eab0e377d37517
+size 25736
diff --git a/marked/Rel-11/25_series/25423/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/Rel-11/25_series/25423/e9b43ac020435f8121e8592f31afdc52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0493b2b5ba166ec3d0e00dca7449932e8044aa11
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/e9b43ac020435f8121e8592f31afdc52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:969402973f1ed606d9fe8ad80d3264013851add475fa58af7c927fcff40589e5
+size 6248
diff --git a/marked/Rel-11/25_series/25423/ebf3358c49f6a9f72d5a39731d7e22ca_img.jpg b/marked/Rel-11/25_series/25423/ebf3358c49f6a9f72d5a39731d7e22ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cef19d3dfc16797079d133f1e17374d34a0c0356
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/ebf3358c49f6a9f72d5a39731d7e22ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1610dc4d2fe332334ef24f33f97d9df7bf7bab6a82e2851462c15eb8bd20488
+size 16375
diff --git a/marked/Rel-11/25_series/25423/efed3385cdd07695b11167783a8bdbb1_img.jpg b/marked/Rel-11/25_series/25423/efed3385cdd07695b11167783a8bdbb1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4870acf6e81d8c6cd821b64443c25dc4cb84440c
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/efed3385cdd07695b11167783a8bdbb1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2449eabe25ffe86782a71b56d5c1f837daed80629456599d40d31b88b57c0105
+size 10176
diff --git a/marked/Rel-11/25_series/25423/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-11/25_series/25423/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b090e1fbcedc6c1cc0c3cf5a8e2ce3c6a37ac872
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d4cc79aa02a35333f51be19824b7aa0de6808f7bdcef25128c504a2407cad7d
+size 7064
diff --git a/marked/Rel-11/25_series/25423/f5e131a3fffe09aa98db055df84e4378_img.jpg b/marked/Rel-11/25_series/25423/f5e131a3fffe09aa98db055df84e4378_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d4906d40ba576c5c4d7c73cc754ce379c559778c
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/f5e131a3fffe09aa98db055df84e4378_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef4031a89932a8ee566fb8217b7701c4c3e5ab54ef903a1b134e84abc8a6096f
+size 14157
diff --git a/marked/Rel-11/25_series/25423/f943b07ab747bfd85e302e5a31c20ba8_img.jpg b/marked/Rel-11/25_series/25423/f943b07ab747bfd85e302e5a31c20ba8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5c562d620c080fb0b2bd63845f811120e0313fd
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/f943b07ab747bfd85e302e5a31c20ba8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66bbb61aa463541526da36acff3e64d2345ce147ca670142022873cbdcfc7520
+size 4175
diff --git a/marked/Rel-11/25_series/25423/fbce213427570f177cd310adf8b7a604_img.jpg b/marked/Rel-11/25_series/25423/fbce213427570f177cd310adf8b7a604_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f2df5054ec15d7106caf6ecb07060e66b0b2da43
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/fbce213427570f177cd310adf8b7a604_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50aeb63adf62b19da831d13d5f584ac4b0ff740fe8426e87c114e813e5f273cb
+size 7998
diff --git a/marked/Rel-11/25_series/25423/raw.md b/marked/Rel-11/25_series/25423/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4f014a00983646878fdfb9dd89fcb434cf0f1c44
--- /dev/null
+++ b/marked/Rel-11/25_series/25423/raw.md
@@ -0,0 +1,48763 @@
+Error:
+
+2
+
+Error: Reference source not found
+
+# Contents
+
+| | |
+|------------------------------------------------------------------|----|
+| Foreword..... | 24 |
+| 1 Scope..... | 25 |
+| 2 References..... | 25 |
+| 3 Definitions, Symbols and Abbreviations..... | 27 |
+| 3.1 Definitions..... | 27 |
+| 3.2 Symbols..... | 28 |
+| 3.3 Abbreviations..... | 28 |
+| 4 General..... | 31 |
+| 4.1 Procedure Specification Principles..... | 31 |
+| 4.2 Forwards and Backwards Compatibility..... | 32 |
+| 4.3 Source Signalling Address Handling..... | 32 |
+| 4.4 Specification Notations..... | 32 |
+| 5 RNSAP Services..... | 33 |
+| 5.1 RNSAP Procedure Modules..... | 33 |
+| 5.2 Parallel Transactions..... | 34 |
+| 6 Services Expected from Signalling Transport..... | 34 |
+| 7 Functions of RNSAP..... | 34 |
+| 7.1 RNSAP functions and elementary procedures for Iur-g..... | 37 |
+| 8 RNSAP Procedures..... | 38 |
+| 8.1 Elementary Procedures..... | 38 |
+| 8.2 Basic Mobility Procedures..... | 40 |
+| 8.2.1 Uplink Signalling Transfer..... | 40 |
+| 8.2.1.1 General..... | 40 |
+| 8.2.1.2 Successful Operation..... | 40 |
+| 8.2.1.3 Abnormal Conditions..... | 42 |
+| 8.2.1A GERAN Uplink Signalling Transfer..... | 42 |
+| 8.2.1A.1 General..... | 42 |
+| 8.2.1A.2 Successful Operation..... | 42 |
+| 8.2.1A.3 Abnormal Conditions..... | 42 |
+| 8.2.2 Downlink Signalling Transfer..... | 43 |
+| 8.2.2.1 General..... | 43 |
+| 8.2.2.1.1 Downlink Signalling Transfer for Iur-g..... | 43 |
+| 8.2.2.2 Successful Operation..... | 43 |
+| 8.2.2.2.1 Successful Operation for Iur-g..... | 44 |
+| 8.2.2.3 Abnormal Conditions..... | 44 |
+| 8.2.2.3.1 Abnormal Conditions for Iur-g..... | 44 |
+| 8.2.3 Relocation Commit..... | 44 |
+| 8.2.3.1 General..... | 44 |
+| 8.2.3.2 Successful Operation..... | 44 |
+| 8.2.3.2.1 Successful Operation for Iur-g..... | 45 |
+| 8.2.3.3 Abnormal Conditions..... | 45 |
+| 8.2.4 Paging..... | 45 |
+| 8.2.4.1 General..... | 45 |
+| 8.2.4.2 Successful Operation..... | 45 |
+| 8.2.4.2.1 Successful Operation for Iur-g..... | 45 |
+| 8.2.4.3 Abnormal Conditions..... | 46 |
+| 8.2.4.3.1 Abnormal Conditions for Iur-g..... | 46 |
+| 8.2.5 MBSFN MCCH Information..... | 46 |
+| 8.2.5.1 General..... | 46 |
+| 8.2.5.2 Successful Operation..... | 46 |
+| 8.2.5.3 Abnormal Conditions..... | 46 |
+| 8.2.6 Enhanced Relocation Resource Allocation[1.28Mcps TDD]..... | 46 |
+| 8.2.6.1 General..... | 46 |
+
+| | | |
+|----------|-----------------------------------------------------------|-----|
+| 8.2.6.2 | Successful Operation..... | 47 |
+| 8.2.6.3 | Unsuccessful Operation..... | 47 |
+| 8.2.6.4 | Abnormal Conditions..... | 47 |
+| 8.2.7 | Enhanced Relocation Resource Release[1.28Mcps TDD]..... | 47 |
+| 8.2.7.1 | General..... | 47 |
+| 8.2.7.2 | Successful Operation..... | 48 |
+| 8.2.7.3 | Abnormal Conditions..... | 48 |
+| 8.3 | Dedicated Procedures..... | 48 |
+| 8.3.1 | Radio Link Setup..... | 48 |
+| 8.3.1.1 | General..... | 48 |
+| 8.3.1.2 | Successful Operation..... | 48 |
+| 8.3.1.3 | Unsuccessful Operation..... | 78 |
+| 8.3.1.4 | Abnormal Conditions..... | 80 |
+| 8.3.2 | Radio Link Addition..... | 84 |
+| 8.3.2.1 | General..... | 84 |
+| 8.3.2.2 | Successful Operation..... | 84 |
+| 8.3.2.3 | Unsuccessful Operation..... | 115 |
+| 8.3.2.4 | Abnormal Conditions..... | 117 |
+| 8.3.3 | Radio Link Deletion..... | 121 |
+| 8.3.3.1 | General..... | 121 |
+| 8.3.3.2 | Successful Operation..... | 121 |
+| 8.3.3.3 | Unsuccessful Operation..... | 122 |
+| 8.3.3.4 | Abnormal Conditions..... | 122 |
+| 8.3.4 | Synchronised Radio Link Reconfiguration Preparation..... | 122 |
+| 8.3.4.1 | General..... | 122 |
+| 8.3.4.2 | Successful Operation..... | 122 |
+| 8.3.4.3 | Unsuccessful Operation..... | 169 |
+| 8.3.4.4 | Abnormal Conditions..... | 171 |
+| 8.3.5 | Synchronised Radio Link Reconfiguration Commit..... | 176 |
+| 8.3.5.1 | General..... | 176 |
+| 8.3.5.2 | Successful Operation..... | 176 |
+| 8.3.5.3 | Abnormal Conditions..... | 177 |
+| 8.3.6 | Synchronised Radio Link Reconfiguration Cancellation..... | 178 |
+| 8.3.6.1 | General..... | 178 |
+| 8.3.6.2 | Successful Operation..... | 178 |
+| 8.3.6.3 | Abnormal Conditions..... | 178 |
+| 8.3.7 | Unsynchronised Radio Link Reconfiguration..... | 178 |
+| 8.3.7.1 | General..... | 178 |
+| 8.3.7.2 | Successful Operation..... | 178 |
+| 8.3.7.3 | Unsuccessful Operation..... | 219 |
+| 8.3.7.4 | Abnormal Conditions..... | 220 |
+| 8.3.8 | Physical Channel Reconfiguration..... | 225 |
+| 8.3.8.1 | General..... | 225 |
+| 8.3.8.2 | Successful Operation..... | 225 |
+| 8.3.8.3 | Unsuccessful Operation..... | 226 |
+| 8.3.8.4 | Abnormal Conditions..... | 226 |
+| 8.3.9 | Radio Link Failure..... | 227 |
+| 8.3.9.1 | General..... | 227 |
+| 8.3.9.2 | Successful Operation..... | 227 |
+| 8.3.9.3 | Abnormal Conditions..... | 228 |
+| 8.3.10 | Radio Link Restoration..... | 228 |
+| 8.3.10.1 | General..... | 228 |
+| 8.3.10.2 | Successful Operation..... | 228 |
+| 8.3.10.3 | Abnormal Conditions..... | 228 |
+| 8.3.11 | Dedicated Measurement Initiation..... | 228 |
+| 8.3.11.1 | General..... | 228 |
+| 8.3.11.2 | Successful Operation..... | 229 |
+| 8.3.11.3 | Unsuccessful Operation..... | 232 |
+| 8.3.11.4 | Abnormal Conditions..... | 232 |
+| 8.3.12 | Dedicated Measurement Reporting..... | 233 |
+| 8.3.12.1 | General..... | 233 |
+
+| | | |
+|----------|--------------------------------------------|-----|
+| 8.3.12.2 | Successful Operation..... | 233 |
+| 8.3.12.3 | Abnormal Conditions..... | 234 |
+| 8.3.13 | Dedicated Measurement Termination..... | 234 |
+| 8.3.13.1 | General..... | 234 |
+| 8.3.13.2 | Successful Operation..... | 234 |
+| 8.3.13.3 | Abnormal Conditions..... | 234 |
+| 8.3.14 | Dedicated Measurement Failure..... | 235 |
+| 8.3.14.1 | General..... | 235 |
+| 8.3.14.2 | Successful Operation..... | 235 |
+| 8.3.14.3 | Abnormal Conditions..... | 235 |
+| 8.3.15 | Downlink Power Control [FDD]..... | 235 |
+| 8.3.15.1 | General..... | 235 |
+| 8.3.15.2 | Successful Operation..... | 236 |
+| 8.3.15.3 | Abnormal Conditions..... | 236 |
+| 8.3.16 | Compressed Mode Command [FDD]..... | 237 |
+| 8.3.16.1 | General..... | 237 |
+| 8.3.16.2 | Successful Operation..... | 237 |
+| 8.3.16.3 | Abnormal Conditions..... | 237 |
+| 8.3.17 | Downlink Power Timeslot Control [TDD]..... | 237 |
+| 8.3.17.1 | General..... | 237 |
+| 8.3.17.2 | Successful Operation..... | 238 |
+| 8.3.17.3 | Abnormal Conditions..... | 238 |
+| 8.3.18 | Radio Link Pre-emption..... | 238 |
+| 8.3.18.1 | General..... | 238 |
+| 8.3.18.2 | Successful Operation..... | 238 |
+| 8.3.18.3 | Abnormal Conditions..... | 239 |
+| 8.3.19 | Radio Link Congestion..... | 239 |
+| 8.3.19.1 | General..... | 239 |
+| 8.3.19.2 | Successful Operation..... | 239 |
+| 8.3.19.3 | Abnormal Conditions..... | 240 |
+| 8.3.20 | Radio Link Activation..... | 240 |
+| 8.3.20.1 | General..... | 240 |
+| 8.3.20.2 | Successful Operation..... | 240 |
+| 8.3.20.3 | Abnormal Conditions..... | 241 |
+| 8.3.21 | Radio Link Parameter Update..... | 241 |
+| 8.3.21.1 | General..... | 241 |
+| 8.3.21.2 | Successful Operation..... | 241 |
+| 8.3.21.3 | Abnormal Conditions..... | 243 |
+| 8.3.22 | UE Measurement Initiation [TDD]..... | 243 |
+| 8.3.22.1 | General..... | 243 |
+| 8.3.22.2 | Successful Operation..... | 243 |
+| 8.3.22.3 | Unsuccessful Operation..... | 244 |
+| 8.3.22.4 | Abnormal Conditions..... | 245 |
+| 8.3.23 | UE Measurement Reporting [TDD]..... | 245 |
+| 8.3.23.1 | General..... | 245 |
+| 8.3.23.2 | Successful Operation..... | 245 |
+| 8.3.23.3 | Abnormal Conditions..... | 245 |
+| 8.3.24 | UE Measurement Termination [TDD]..... | 245 |
+| 8.3.24.1 | General..... | 245 |
+| 8.3.24.2 | Successful Operation..... | 246 |
+| 8.3.24.3 | Abnormal Conditions..... | 246 |
+| 8.3.25 | UE Measurement Failure [TDD]..... | 246 |
+| 8.3.25.1 | General..... | 246 |
+| 8.3.25.2 | Successful Operation..... | 246 |
+| 8.3.25.3 | Abnormal Conditions..... | 246 |
+| 8.3.26 | Iur Invoke Trace..... | 247 |
+| 8.3.26.1 | General..... | 247 |
+| 8.3.26.2 | Successful Operation..... | 247 |
+| 8.3.26.3 | Abnormal Conditions..... | 247 |
+| 8.3.27 | Iur Deactivate Trace..... | 248 |
+| 8.3.27.1 | General..... | 248 |
+
+| | | |
+|-----------|--------------------------------------------------------|-----|
+| 8.3.27.2 | Successful Operation..... | 248 |
+| 8.3.27.3 | Abnormal Conditions..... | 248 |
+| 8.3.28 | Enhanced Relocation..... | 248 |
+| 8.3.28.1 | General..... | 248 |
+| 8.3.28.2 | Successful Operation..... | 248 |
+| 8.3.28.3 | Unsuccessful Operation..... | 249 |
+| 8.3.28.4 | Abnormal Conditions..... | 249 |
+| 8.3.29 | Enhanced Relocation Cancel..... | 249 |
+| 8.3.29.1 | General..... | 249 |
+| 8.3.29.2 | Successful Operation..... | 249 |
+| 8.3.29.3 | Unsuccessful Operation..... | 249 |
+| 8.3.29.4 | Abnormal Conditions..... | 250 |
+| 8.3.30 | Enhanced Relocation Signalling Transfer..... | 250 |
+| 8.3.30.1 | General..... | 250 |
+| 8.3.30.2 | Successful Operation..... | 250 |
+| 8.3.30.3 | Abnormal Conditions..... | 250 |
+| 8.3.31 | Enhanced Relocation Release..... | 250 |
+| 8.3.31.1 | General..... | 250 |
+| 8.3.31.2 | Successful Operation..... | 250 |
+| 8.3.31.3 | Abnormal Conditions..... | 251 |
+| 8.3.32 | Secondary UL Frequency Reporting [FDD]..... | 251 |
+| 8.3.32.1 | General..... | 251 |
+| 8.3.32.2 | Successful Operation..... | 251 |
+| 8.3.32.3 | Abnormal Conditions..... | 251 |
+| 8.3.33 | Secondary UL Frequency Update [FDD]..... | 251 |
+| 8.3.33.1 | General..... | 251 |
+| 8.3.33.2 | Successful Operation..... | 251 |
+| 8.3.33.3 | Abnormal Conditions..... | 252 |
+| 8.4 | Common Transport Channel Procedures..... | 252 |
+| 8.4.1 | Common Transport Channel Resources Initialisation..... | 252 |
+| 8.4.1.1 | General..... | 252 |
+| 8.4.1.2 | Successful Operation..... | 252 |
+| 8.4.1.3 | Unsuccessful Operation..... | 254 |
+| 8.4.1.4 | Abnormal Conditions..... | 254 |
+| 8.4.2 | Common Transport Channel Resources Release..... | 254 |
+| 8.4.2.1 | General..... | 254 |
+| 8.4.2.2 | Successful Operation..... | 255 |
+| 8.4.2.3 | Abnormal Conditions..... | 255 |
+| 8.5 | Global Procedures..... | 255 |
+| 8.5.1 | Error Indication..... | 255 |
+| 8.5.1.1 | General..... | 255 |
+| 8.5.1.2 | Successful Operation..... | 255 |
+| 8.5.1.2.1 | Successful Operation for Iur-g..... | 256 |
+| 8.5.1.3 | Abnormal Conditions..... | 256 |
+| 8.5.2 | Common Measurement Initiation..... | 256 |
+| 8.5.2.1 | General..... | 256 |
+| 8.5.2.2 | Successful Operation..... | 256 |
+| 8.5.2.2.1 | Successful Operation for Iur-g..... | 263 |
+| 8.5.2.3 | Unsuccessful Operation..... | 264 |
+| 8.5.2.4 | Abnormal Conditions..... | 264 |
+| 8.5.2.4.1 | Abnormal Conditions for Iur-g..... | 265 |
+| 8.5.3 | Common Measurement Reporting..... | 266 |
+| 8.5.3.1 | General..... | 266 |
+| 8.5.3.2 | Successful Operation..... | 266 |
+| 8.5.3.2.1 | Successful Operation for Iur-g..... | 267 |
+| 8.5.3.3 | Abnormal Conditions..... | 267 |
+| 8.5.4 | Common Measurement Termination..... | 267 |
+| 8.5.4.1 | General..... | 267 |
+| 8.5.4.2 | Successful Operation..... | 267 |
+| 8.5.4.2.1 | Successful Operation for Iur-g..... | 268 |
+| 8.5.4.3 | Abnormal Conditions..... | 268 |
+
+| | | |
+|-----------|-----------------------------------------------|-----|
+| 8.5.5 | Common Measurement Failure..... | 268 |
+| 8.5.5.1 | General..... | 268 |
+| 8.5.5.2 | Successful Operation..... | 268 |
+| 8.5.5.2.1 | Successful Operation for Iur-g..... | 268 |
+| 8.5.5.3 | Abnormal Conditions..... | 268 |
+| 8.5.6 | Information Exchange Initiation..... | 268 |
+| 8.5.6.1 | General..... | 268 |
+| 8.5.6.2 | Successful Operation..... | 269 |
+| 8.5.6.2.1 | Successful Operation for Iur-g..... | 272 |
+| 8.5.6.3 | Unsuccessful Operation..... | 273 |
+| 8.5.6.4 | Abnormal Conditions..... | 273 |
+| 8.5.6.4.1 | Abnormal Conditions for Iur-g..... | 274 |
+| 8.5.7 | Information Reporting..... | 275 |
+| 8.5.7.1 | General..... | 275 |
+| 8.5.7.2 | Successful Operation..... | 275 |
+| 8.5.7.2.1 | Successful Operation for Iur-g..... | 275 |
+| 8.5.7.3 | Abnormal Conditions..... | 275 |
+| 8.5.8 | Information Exchange Termination..... | 275 |
+| 8.5.8.1 | General..... | 275 |
+| 8.5.8.2 | Successful Operation..... | 275 |
+| 8.5.8.2.1 | Successful Operation for Iur-g..... | 276 |
+| 8.5.8.3 | Abnormal Conditions..... | 276 |
+| 8.5.9 | Information Exchange Failure..... | 276 |
+| 8.5.9.1 | General..... | 276 |
+| 8.5.9.2 | Successful Operation..... | 276 |
+| 8.5.9.2.1 | Successful Operation for Iur-g..... | 276 |
+| 8.5.10 | Reset..... | 276 |
+| 8.5.10.1 | General..... | 276 |
+| 8.5.10.2 | Successful Operation..... | 276 |
+| 8.5.10.3 | Abnormal Conditions..... | 277 |
+| 8.5.11 | Direct Information Transfer..... | 277 |
+| 8.5.11.1 | General..... | 277 |
+| 8.5.11.2 | Successful Operation..... | 277 |
+| 8.5.12 | Information Transfer Control..... | 278 |
+| 8.5.12.1 | General..... | 278 |
+| 8.5.12.2 | Successful Operation..... | 278 |
+| 8.5.12.3 | Abnormal Conditions..... | 279 |
+| 8.6 | MBMS Procedures..... | 279 |
+| 8.6.1 | MBMS Attach..... | 279 |
+| 8.6.1.1 | General..... | 279 |
+| 8.6.1.2 | Successful Operation..... | 279 |
+| 8.6.1.3 | Abnormal Conditions..... | 279 |
+| 8.6.2 | MBMS Detach..... | 279 |
+| 8.6.2.1 | General..... | 279 |
+| 8.6.2.2 | Successful Operation..... | 280 |
+| 8.6.2.3 | Abnormal Conditions..... | 280 |
+| 9 | Elements for RNSAP Communication..... | 280 |
+| 9.1 | Message Functional Definiton and Content..... | 280 |
+| 9.1.1 | General..... | 280 |
+| 9.1.2 | Message Contents..... | 280 |
+| 9.1.2.1 | Presence..... | 280 |
+| 9.1.2.2 | Criticality..... | 281 |
+| 9.1.2.3 | Range..... | 281 |
+| 9.1.2.4 | Assigned Criticality..... | 281 |
+| 9.1.3 | RADIO LINK SETUP REQUEST..... | 282 |
+| 9.1.3.1 | FDD Message..... | 282 |
+| 9.1.3.2 | TDD Message..... | 286 |
+| 9.1.4 | RADIO LINK SETUP RESPONSE..... | 290 |
+| 9.1.4.1 | FDD Message..... | 290 |
+| 9.1.4.2 | TDD Message..... | 293 |
+| 9.1.5 | RADIO LINK SETUP FAILURE..... | 300 |
+
+| | | |
+|----------|---------------------------------------------------------|-----|
+| 9.1.5.1 | FDD Message..... | 300 |
+| 9.1.5.2 | TDD Message..... | 303 |
+| 9.1.6 | RADIO LINK ADDITION REQUEST..... | 304 |
+| 9.1.6.1 | FDD Message..... | 304 |
+| 9.1.6.2 | TDD Message..... | 307 |
+| 9.1.7 | RADIO LINK ADDITION RESPONSE..... | 309 |
+| 9.1.7.1 | FDD Message..... | 309 |
+| 9.1.7.2 | TDD Message..... | 312 |
+| 9.1.8 | RADIO LINK ADDITION FAILURE..... | 319 |
+| 9.1.8.1 | FDD Message..... | 319 |
+| 9.1.8.2 | TDD Message..... | 321 |
+| 9.1.9 | RADIO LINK DELETION REQUEST..... | 321 |
+| 9.1.10 | RADIO LINK DELETION RESPONSE..... | 322 |
+| 9.1.11 | RADIO LINK RECONFIGURATION PREPARE..... | 323 |
+| 9.1.11.1 | FDD Message..... | 323 |
+| 9.1.11.2 | TDD Message..... | 328 |
+| 9.1.12 | RADIO LINK RECONFIGURATION READY..... | 334 |
+| 9.1.12.1 | FDD Message..... | 334 |
+| 9.1.12.2 | TDD Message..... | 336 |
+| 9.1.13 | RADIO LINK RECONFIGURATION COMMIT..... | 341 |
+| 9.1.14 | RADIO LINK RECONFIGURATION FAILURE..... | 341 |
+| 9.1.15 | RADIO LINK RECONFIGURATION CANCEL..... | 342 |
+| 9.1.16 | RADIO LINK RECONFIGURATION REQUEST..... | 343 |
+| 9.1.16.1 | FDD Message..... | 343 |
+| 9.1.16.2 | TDD Message..... | 347 |
+| 9.1.17 | RADIO LINK RECONFIGURATION RESPONSE..... | 350 |
+| 9.1.17.1 | FDD Message..... | 350 |
+| 9.1.17.2 | TDD Message..... | 352 |
+| 9.1.18 | RADIO LINK FAILURE INDICATION..... | 354 |
+| 9.1.19 | RADIO LINK RESTORE INDICATION..... | 354 |
+| 9.1.20 | DL POWER CONTROL REQUEST [FDD]..... | 355 |
+| 9.1.21 | PHYSICAL CHANNEL RECONFIGURATION REQUEST..... | 355 |
+| 9.1.21.1 | FDD Message..... | 355 |
+| 9.1.21.2 | TDD Message..... | 356 |
+| 9.1.22 | PHYSICAL CHANNEL RECONFIGURATION COMMAND..... | 358 |
+| 9.1.23 | PHYSICAL CHANNEL RECONFIGURATION FAILURE..... | 358 |
+| 9.1.24 | UPLINK SIGNALLING TRANSFER INDICATION..... | 358 |
+| 9.1.24.1 | FDD Message..... | 358 |
+| 9.1.24.2 | TDD Message..... | 360 |
+| 9.1.24A | GERAN UPLINK SIGNALLING TRANSFER INDICATION..... | 361 |
+| 9.1.25 | DOWNLINK SIGNALLING TRANSFER REQUEST..... | 362 |
+| 9.1.26 | RELOCATION COMMIT..... | 362 |
+| 9.1.27 | PAGING REQUEST..... | 363 |
+| 9.1.28 | DEDICATED MEASUREMENT INITIATION REQUEST..... | 364 |
+| 9.1.29 | DEDICATED MEASUREMENT INITIATION RESPONSE..... | 365 |
+| 9.1.30 | DEDICATED MEASUREMENT INITIATION FAILURE..... | 367 |
+| 9.1.31 | DEDICATED MEASUREMENT REPORT..... | 368 |
+| 9.1.32 | DEDICATED MEASUREMENT TERMINATION REQUEST..... | 368 |
+| 9.1.33 | DEDICATED MEASUREMENT FAILURE INDICATION..... | 369 |
+| 9.1.34 | COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST..... | 369 |
+| 9.1.35 | COMMON TRANSPORT CHANNEL RESOURCES REQUEST..... | 370 |
+| 9.1.36 | COMMON TRANSPORT CHANNEL RESOURCES RESPONSE..... | 372 |
+| 9.1.36.1 | FDD Message..... | 372 |
+| 9.1.36.2 | TDD Message..... | 374 |
+| 9.1.37 | COMMON TRANSPORT CHANNEL RESOURCES FAILURE..... | 375 |
+| 9.1.38 | COMPRESSED MODE COMMAND [FDD]..... | 375 |
+| 9.1.39 | ERROR INDICATION..... | 376 |
+| 9.1.40 | DL POWER TIMESLOT CONTROL REQUEST [TDD]..... | 376 |
+| 9.1.41 | RADIO LINK PREEMPTION REQUIRED INDICATION..... | 377 |
+| 9.1.42 | RADIO LINK CONGESTION INDICATION..... | 377 |
+| 9.1.43 | COMMON MEASUREMENT INITIATION REQUEST..... | 378 |
+
+| | | |
+|----------|-------------------------------------------------------------|-----|
+| 9.1.44 | COMMON MEASUREMENT INITIATION RESPONSE..... | 380 |
+| 9.1.45 | COMMON MEASUREMENT INITIATION FAILURE..... | 381 |
+| 9.1.46 | COMMON MEASUREMENT REPORT..... | 381 |
+| 9.1.47 | COMMON MEASUREMENT TERMINATION REQUEST..... | 382 |
+| 9.1.48 | COMMON MEASUREMENT FAILURE INDICATION..... | 382 |
+| 9.1.49 | INFORMATION EXCHANGE INITIATION REQUEST..... | 383 |
+| 9.1.50 | INFORMATION EXCHANGE INITIATION RESPONSE..... | 384 |
+| 9.1.51 | INFORMATION EXCHANGE INITIATION FAILURE..... | 385 |
+| 9.1.52 | INFORMATION REPORT..... | 386 |
+| 9.1.53 | INFORMATION EXCHANGE TERMINATION REQUEST..... | 387 |
+| 9.1.54 | INFORMATION EXCHANGE FAILURE INDICATION..... | 387 |
+| 9.1.55 | RESET REQUEST..... | 387 |
+| 9.1.56 | RESET RESPONSE..... | 390 |
+| 9.1.57 | RADIO LINK ACTIVATION COMMAND..... | 390 |
+| 9.1.57.1 | FDD Message..... | 390 |
+| 9.1.57.2 | TDD Message..... | 391 |
+| 9.1.58 | RADIO LINK PARAMETER UPDATE INDICATION..... | 392 |
+| 9.1.58.1 | FDD Message..... | 392 |
+| 9.1.58.2 | TDD Message..... | 393 |
+| 9.1.59 | UE MEASUREMENT INITIATION REQUEST [TDD]..... | 393 |
+| 9.1.60 | UE MEASUREMENT INITIATION RESPONSE [TDD]..... | 393 |
+| 9.1.61 | UE MEASUREMENT INITIATION FAILURE [TDD]..... | 393 |
+| 9.1.62 | UE MEASUREMENT REPORT [TDD]..... | 394 |
+| 9.1.63 | UE MEASUREMENT TERMINATION REQUEST [TDD]..... | 394 |
+| 9.1.64 | UE MEASUREMENT FAILURE INDICATION [TDD]..... | 394 |
+| 9.1.65 | IUR INVOKE TRACE..... | 394 |
+| 9.1.66 | IUR DEACTIVATE TRACE..... | 395 |
+| 9.1.67 | MBMS ATTACH COMMAND..... | 395 |
+| 9.1.68 | MBMS DETACH COMMAND..... | 396 |
+| 9.1.69 | DIRECT INFORMATION TRANSFER..... | 397 |
+| 9.1.70 | ENHANCED RELOCATION REQUEST..... | 398 |
+| 9.1.71 | ENHANCED RELOCATION RESPONSE..... | 398 |
+| 9.1.72 | ENHANCED RELOCATION FAILURE..... | 399 |
+| 9.1.73 | ENHANCED RELOCATION CANCEL..... | 399 |
+| 9.1.74 | ENHANCED RELOCATION SIGNALLING TRANSFER..... | 399 |
+| 9.1.75 | ENHANCED RELOCATION RELEASE..... | 399 |
+| 9.1.76 | MBSFN MCCH INFORMATION (FDD)..... | 400 |
+| 9.1.77 | SECONDARY UL FREQUENCY REPORT..... | 400 |
+| 9.1.77.1 | FDD Message..... | 400 |
+| 9.1.78 | SECONDARY UL FREQUENCY UPDATE INDICATION..... | 400 |
+| 9.1.78.1 | FDD Message..... | 400 |
+| 9.1.79 | ENHANCED RELOCATION RESOURCE REQUEST [TDD]..... | 401 |
+| 9.1.80 | ENHANCED RELOCATION RESOURCE RESPONSE [TDD]..... | 401 |
+| 9.1.81 | ENHANCED RELOCATION RESOURCE FAILURE [TDD]..... | 401 |
+| 9.1.82 | ENHANCED RELOCATION RESOURCE RELEASE COMMAND [TDD]..... | 401 |
+| 9.1.83 | ENHANCED RELOCATION RESOURCE RELEASE COMPLETE [TDD]..... | 402 |
+| 9.1.84 | INFORMATION TRANSFER CONTROL REQUEST..... | 402 |
+| 9.2 | Information Element Functional Definition and Contents..... | 402 |
+| 9.2.0 | General..... | 402 |
+| 9.2.1 | Common Parameters..... | 402 |
+| 9.2.1.1 | Allocation/Retention Priority..... | 402 |
+| 9.2.1.2 | Allowed Queuing Time..... | 403 |
+| 9.2.1.2A | Allowed Rate Information..... | 403 |
+| 9.2.1.2B | Altitude and Direction..... | 403 |
+| 9.2.1.2C | Antenna Co-location Indicator..... | 404 |
+| 9.2.1.2D | Alternative Format Reporting Indicator..... | 404 |
+| 9.2.1.3 | Binding ID..... | 404 |
+| 9.2.1.4 | BLER..... | 404 |
+| 9.2.1.4A | Block STTD Indicator..... | 405 |
+| 9.2.1.4B | Burst Mode Parameters..... | 405 |
+| 9.2.1.5 | Cause..... | 405 |
+
+| | | |
+|------------|----------------------------------------------------------------------------|-----|
+| 9.2.1.5A | Cell Geographical Area Identity (Cell GAI)..... | 412 |
+| 9.2.1.5B | Cell Geographical Area Additional Shapes (Cell GAI Additional Shapes)..... | 412 |
+| 9.2.1.5C | Cell Capacity Class Value..... | 413 |
+| 9.2.1.5D | Cell Global Identifier (CGI)..... | 413 |
+| 9.2.1.6 | Cell Identifier (C-ID)..... | 414 |
+| 9.2.1.7 | Cell Individual Offset..... | 414 |
+| 9.2.1.8 | Cell Parameter ID..... | 414 |
+| 9.2.1.9 | CFN..... | 414 |
+| 9.2.1.10 | CFN Offset..... | 415 |
+| 9.2.1.11 | CN CS Domain Identifier..... | 415 |
+| 9.2.1.11A | CN Domain Type..... | 415 |
+| 9.2.1.12 | CN PS Domain Identifier..... | 415 |
+| 9.2.1.12A | Common Measurement Accuracy..... | 416 |
+| 9.2.1.12B | Common Measurement Object Type..... | 416 |
+| 9.2.1.12C | Common Measurement Type..... | 416 |
+| 9.2.1.12D | Common Measurement Value..... | 417 |
+| 9.2.1.12E | Common Measurement Value Information..... | 418 |
+| 9.2.1.12F | Common Transport Channel Resources Initialisation Not Required..... | 419 |
+| 9.2.1.12G | Coverage Indicator..... | 419 |
+| 9.2.1.13 | Criticality Diagnostics..... | 419 |
+| 9.2.1.14 | C-RNTI..... | 421 |
+| 9.2.1.14A | CTFC..... | 421 |
+| 9.2.1.15 | DCH Combination Indicator..... | 422 |
+| 9.2.1.16 | DCH ID..... | 422 |
+| 9.2.1.16A | DCH Information Response..... | 422 |
+| 9.2.1.17 | Dedicated Measurement Object Type..... | 422 |
+| 9.2.1.18 | Dedicated Measurement Type..... | 422 |
+| 9.2.1.19 | Dedicated Measurement Value..... | 423 |
+| 9.2.1.19A | Dedicated Measurement Value Information..... | 425 |
+| 9.2.1.19Aa | Delayed Activation..... | 425 |
+| 9.2.1.19Ab | Delayed Activation Update..... | 426 |
+| 9.2.1.19B | DGPS Corrections..... | 426 |
+| 9.2.1.19C | Discard Timer..... | 427 |
+| 9.2.1.20 | Diversity Control Field..... | 428 |
+| 9.2.1.21 | Diversity Indication..... | 428 |
+| 9.2.1.21A | DL Power..... | 428 |
+| 9.2.1.22 | Downlink SIR Target..... | 428 |
+| 9.2.1.23 | DPCH Constant Value..... | 428 |
+| 9.2.1.24 | D-RNTI..... | 429 |
+| 9.2.1.25 | D-RNTI Release Indication..... | 429 |
+| 9.2.1.26 | DRX Cycle Length Coefficient..... | 429 |
+| 9.2.1.26A | DSCH ID..... | 429 |
+| 9.2.1.26Aa | DSCH Initial Window Size..... | 429 |
+| 9.2.1.26B | DSCH Flow Control Information..... | 429 |
+| 9.2.1.26Ba | DSCH-RNTI..... | 429 |
+| 9.2.1.26Bb | Extended GSM Cell Individual Offset..... | 429 |
+| 9.2.1.26C | FACH Flow Control Information..... | 430 |
+| 9.2.1.27 | FACH Initial Window Size..... | 430 |
+| 9.2.1.28 | FACH Priority Indicator..... | 430 |
+| 9.2.1.28A | FN Reporting Indicator..... | 430 |
+| 9.2.1.29 | Frame Handling Priority..... | 431 |
+| 9.2.1.30 | Frame Offset..... | 431 |
+| 9.2.1.30A | GA Point with Uncertainty..... | 431 |
+| 9.2.1.30B | GA Ellipsoid Point with Uncertainty Ellipse..... | 431 |
+| 9.2.1.30C | GA Ellipsoid Point with Altitude..... | 431 |
+| 9.2.1.30D | GA Ellipsoid Point with Altitude and Uncertainty Ellipsoid..... | 431 |
+| 9.2.1.30E | GA Ellipsoid Arc..... | 432 |
+| 9.2.1.30F | Geographical Coordinates..... | 432 |
+| 9.2.1.30Fa | GERAN Cell Capability..... | 432 |
+| 9.2.1.30Fb | GERAN Classmark..... | 433 |
+| 9.2.1.30Fc | GERAN System Information..... | 433 |
+
+| | | |
+|------------|------------------------------------------------------|-----|
+| 9.2.1.30G | GPS Almanac..... | 433 |
+| 9.2.1.30H | GPS Ionospheric Model..... | 434 |
+| 9.2.1.30I | GPS Navigation Model and Time Recovery..... | 435 |
+| 9.2.1.30J | GPS Real-Time Integrity..... | 436 |
+| 9.2.1.30K | GPS Receiver Geographical Position (GPS RX Pos)..... | 437 |
+| 9.2.1.30L | GPS UTC Model..... | 437 |
+| 9.2.1.30M | Guaranteed Rate Information..... | 437 |
+| 9.2.1.30N | HCS Prio..... | 437 |
+| 9.2.1.30NA | HS-DSCH Information To Modify Unsynchronised..... | 438 |
+| 9.2.1.30Na | HS-DSCH Initial Capacity Allocation..... | 440 |
+| 9.2.1.30Nb | HS-DSCH Initial Window Size..... | 441 |
+| 9.2.1.30O | HS-DSCH MAC-d Flow ID..... | 441 |
+| 9.2.1.30OA | HS-DSCH MAC-d Flows Information..... | 441 |
+| 9.2.1.30OB | HS-DSCH MAC-d Flows To Delete..... | 443 |
+| 9.2.1.30OC | HS-DSCH MAC-d PDU Size Format..... | 443 |
+| 9.2.1.30Oa | HS-DSCH Physical Layer Category..... | 443 |
+| 9.2.1.30P | HS-DSCH-RNTI..... | 443 |
+| 9.2.1.30Q | HS-DSCH Information To Modify..... | 445 |
+| 9.2.1.30R | HS-SCCH Code Change Indicator..... | 449 |
+| 9.2.1.30S | HS-SCCH Code Change Grant..... | 449 |
+| 9.2.1.30T | IMEI..... | 450 |
+| 9.2.1.30U | IMEISV..... | 450 |
+| 9.2.1.30V | HS-PDSCH Code Change Indicator [FDD]..... | 450 |
+| 9.2.1.30W | HS-PDSCH Code Change Grant [FDD]..... | 450 |
+| 9.2.1.31 | IMSI..... | 451 |
+| 9.2.1.31A | Information Exchange ID..... | 451 |
+| 9.2.1.31B | Information Exchange Object Type..... | 451 |
+| 9.2.1.31C | Information Report Characteristics..... | 451 |
+| 9.2.1.31D | Information Threshold..... | 451 |
+| 9.2.1.31E | Information Type..... | 452 |
+| 9.2.1.31F | IPDL Parameters..... | 456 |
+| 9.2.1.31G | Inter-frequency Cell Information..... | 456 |
+| 9.2.1.32 | L3 Information..... | 457 |
+| 9.2.1.33 | Limited Power Increase..... | 457 |
+| 9.2.1.33A | Load Value..... | 457 |
+| 9.2.1.34 | MAC-c/sh SDU Length..... | 457 |
+| 9.2.1.34A | MAC-d PDU Size..... | 457 |
+| 9.2.1.34Aa | MAC-hs Guaranteed Bit Rate..... | 457 |
+| 9.2.1.34Ab | MAC-hs Reordering Buffer Size for RLC-UM..... | 458 |
+| 9.2.1.34B | MAC-hs Reset Indicator..... | 458 |
+| 9.2.1.34C | MAC-hs Window Size..... | 458 |
+| 9.2.1.34D | MAC PDU Size Extended..... | 458 |
+| 9.2.1.35 | Maximum Allowed UL Tx Power..... | 458 |
+| 9.2.1.35A | Measurement Availability Indicator..... | 459 |
+| 9.2.1.35B | Measurement Change Time..... | 459 |
+| 9.2.1.36 | Measurement Filter Coefficient..... | 459 |
+| 9.2.1.36A | Measurement Hysteresis Time..... | 459 |
+| 9.2.1.37 | Measurement ID..... | 459 |
+| 9.2.1.38 | Measurement Increase/Decrease Threshold..... | 459 |
+| 9.2.1.38A | Measurement Recovery Behavior..... | 461 |
+| 9.2.1.38B | Measurement Recovery Reporting Indicator..... | 461 |
+| 9.2.1.38C | Measurement Recovery Support Indicator..... | 461 |
+| 9.2.1.39 | Measurement Threshold..... | 461 |
+| 9.2.1.39A | Message Structure..... | 463 |
+| 9.2.1.40 | Message Type..... | 464 |
+| 9.2.1.41 | Multiple URAs Indicator..... | 466 |
+| 9.2.1.41a | NACC Related Data..... | 466 |
+| 9.2.1.41A | Neighbouring UMTS Cell Information..... | 466 |
+| 9.2.1.41B | Neighbouring FDD Cell Information..... | 467 |
+| 9.2.1.41C | Neighbouring GSM Cell Information..... | 469 |
+| 9.2.1.41D | Neighbouring TDD Cell Information..... | 471 |
+
+| | | |
+|------------|---------------------------------------------------------------|-----|
+| 9.2.1.41Dd | Neighbouring TDD Cell Measurement Information LCR..... | 472 |
+| 9.2.1.41De | Neighbouring E-UTRA Cell Information..... | 472 |
+| 9.2.1.41Df | EARFCN..... | 474 |
+| 9.2.1.41Dg | EARFCN-Extended..... | 474 |
+| 9.2.1.41E | Paging Cause..... | 474 |
+| 9.2.1.41F | Paging Record Type..... | 475 |
+| 9.2.1.41Fa | Partial Reporting Indicator..... | 475 |
+| 9.2.1.41G | Neighbouring FDD Cell Measurement Information..... | 475 |
+| 9.2.1.41H | Neighbouring TDD Cell Measurement Information..... | 476 |
+| 9.2.1.41I | NRT Load Information Value..... | 476 |
+| 9.2.1.42 | Payload CRC Present Indicator..... | 476 |
+| 9.2.1.43 | PCCPCH Power..... | 477 |
+| 9.2.1.44 | Primary CPICH Power..... | 477 |
+| 9.2.1.45 | Primary Scrambling Code..... | 477 |
+| 9.2.1.45A | Priority Queue ID..... | 477 |
+| 9.2.1.45B | Process Memory Size..... | 477 |
+| 9.2.1.46 | Puncture Limit..... | 478 |
+| 9.2.1.46A | QE-Selector..... | 478 |
+| 9.2.1.47 | RANAP Relocation Information..... | 478 |
+| 9.2.1.48 | Report Characteristics..... | 478 |
+| 9.2.1.48a | Report Periodicity..... | 480 |
+| 9.2.1.48A | Requested Data Value..... | 480 |
+| 9.2.1.48B | Requested Data Value Information..... | 482 |
+| 9.2.1.48C | Restriction State Indicator..... | 482 |
+| 9.2.1.48D | RLC Mode..... | 482 |
+| 9.2.1.49 | RL ID..... | 482 |
+| 9.2.1.49A | RL Specific DCH Information..... | 483 |
+| 9.2.1.50 | RNC-ID..... | 483 |
+| 9.2.1.50a | Extended RNC-ID..... | 483 |
+| 9.2.1.50A | SAT ID..... | 483 |
+| 9.2.1.50B | RT Load Value..... | 484 |
+| 9.2.1.51 | SCH Time Slot..... | 484 |
+| 9.2.1.51A | Scheduling Priority Indicator..... | 484 |
+| 9.2.1.52 | Service Area Identifier (SAI)..... | 484 |
+| 9.2.1.52A | SFN..... | 485 |
+| 9.2.1.52B | SFN-SFN Measurement Threshold Information..... | 485 |
+| 9.2.1.52C | SFN-SFN Measurement Value Information..... | 485 |
+| 9.2.1.52Ca | Shared Network Area (SNA) Information..... | 486 |
+| 9.2.1.52D | SID..... | 487 |
+| 9.2.1.53 | S-RNTI..... | 487 |
+| 9.2.1.53a | S-RNTI Group..... | 487 |
+| 9.2.1.54 | Sync Case..... | 488 |
+| 9.2.1.54A | TI..... | 488 |
+| 9.2.1.55 | TFCI Presence..... | 488 |
+| 9.2.1.56 | Time Slot..... | 488 |
+| 9.2.1.56A | TNL QoS..... | 488 |
+| 9.2.1.57 | ToAWE..... | 489 |
+| 9.2.1.58 | ToAWS..... | 489 |
+| 9.2.1.58a | Trace Depth..... | 489 |
+| 9.2.1.58b | Trace Recording Session Reference..... | 489 |
+| 9.2.1.58c | Trace Reference..... | 490 |
+| 9.2.1.58A | Traffic Class..... | 490 |
+| 9.2.1.59 | Transaction ID..... | 490 |
+| 9.2.1.59A | Transmitted Carrier Power..... | 490 |
+| 9.2.1.59B | T UTRAN-GPS Accuracy Class..... | 491 |
+| 9.2.1.59C | T UTRAN-GPS Measurement Threshold Information..... | 491 |
+| 9.2.1.59D | T UTRAN-GPS Measurement Value Information..... | 491 |
+| 9.2.1.60 | Transport Bearer ID..... | 492 |
+| 9.2.1.61 | Transport Bearer Request Indicator..... | 492 |
+| 9.2.1.62 | Transport Layer Address..... | 493 |
+| 9.2.1.63 | Transport Format Combination Set (TFCS)..... | 493 |
+
+| | | |
+|------------|----------------------------------------------------------|-----|
+| 9.2.1.64 | Transport Format Set..... | 494 |
+| 9.2.1.65 | TrCH Source Statistics Descriptor..... | 496 |
+| 9.2.1.66 | UARFCN..... | 496 |
+| 9.2.1.66A | UE Identity..... | 496 |
+| 9.2.1.67 | UL FP Mode..... | 496 |
+| 9.2.1.68 | UL Interference Level..... | 496 |
+| 9.2.1.68A | Uncertainty Ellipse..... | 497 |
+| 9.2.1.68B | Unidirectional DCH Indicator..... | 497 |
+| 9.2.1.69 | Uplink SIR..... | 497 |
+| 9.2.1.70 | URA ID..... | 497 |
+| 9.2.1.70A | UTRAN Access Point Position..... | 497 |
+| 9.2.1.70B | URA Information..... | 498 |
+| 9.2.1.70C | User Plane Congestion Fields Inclusion..... | 498 |
+| 9.2.1.71 | UTRAN Cell Identifier (UC-ID)..... | 498 |
+| 9.2.1.72 | Neighbouring TDD Cell Information LCR..... | 499 |
+| 9.2.1.73 | Permanent NAS UE Identity..... | 499 |
+| 9.2.1.74 | SFN-SFN Measurement Reference Point Position..... | 500 |
+| 9.2.1.75 | UTRAN Access Point Position with Altitude..... | 500 |
+| 9.2.1.76 | SFN-SFN Measurement Time Stamp..... | 500 |
+| 9.2.1.77 | SFN-SFN Value..... | 500 |
+| 9.2.1.78 | SCTD Indicator..... | 500 |
+| 9.2.1.79 | Congestion Cause..... | 501 |
+| 9.2.1.80 | TMGI..... | 501 |
+| 9.2.1.81 | Transmission Mode..... | 501 |
+| 9.2.1.82 | Access Point Name..... | 502 |
+| 9.2.1.83 | IP Multicast Address..... | 502 |
+| 9.2.1.84 | MBMS Bearer Service Full Address..... | 502 |
+| 9.2.1.85 | Provided Information..... | 502 |
+| 9.2.1.86 | MBMS Channel Type Information..... | 503 |
+| 9.2.1.87 | MBMS Preferred Frequency Layer Information..... | 505 |
+| 9.2.1.88 | E-DCH DDI Value..... | 505 |
+| 9.2.1.89 | E-DCH MAC-d Flow Multiplexing List..... | 506 |
+| 9.2.1.90 | E-DCH MAC-d Flows To Delete..... | 506 |
+| 9.2.1.91 | E-DCH MAC-d Flow ID..... | 506 |
+| 9.2.1.91A | E-DCH MAC-d PDU Size Format..... | 507 |
+| 9.2.1.92 | E-DCH Logical Channel Information..... | 507 |
+| 9.2.1.93 | E-DCH Logical Channel To Modify..... | 508 |
+| 9.2.1.94 | E-RNTI..... | 509 |
+| 9.2.1.95 | E-DCH Processing Overload Level..... | 509 |
+| 9.2.1.96 | E-DCH Power Offset for Scheduling Info..... | 510 |
+| 9.2.1.97 | Logical channel ID..... | 510 |
+| 9.2.1.98 | MAC-es Guaranteed Bit Rate..... | 510 |
+| 9.2.1.99 | MAC-e Reset Indicator..... | 510 |
+| 9.2.1.100 | Maximum Number of Retransmissions for E-DCH..... | 510 |
+| 9.2.1.101 | Scheduling Information..... | 511 |
+| 9.2.1.102 | DGANSS Corrections..... | 511 |
+| 9.2.1.103 | GANSS Almanac..... | 513 |
+| 9.2.1.104 | GANSS Clock Model..... | 517 |
+| 9.2.1.104a | GANSS Additional Clock Models..... | 517 |
+| 9.2.1.105 | GANSS Ionospheric Model..... | 519 |
+| 9.2.1.105a | GANSS Additional Ionospheric Model..... | 520 |
+| 9.2.1.106 | GANSS Navigation Model..... | 520 |
+| 9.2.1.107 | GANSS Orbit Model..... | 520 |
+| 9.2.1.107a | GANSS Additional Orbit Models..... | 521 |
+| 9.2.1.108 | GANSS Real Time Integrity..... | 525 |
+| 9.2.1.109 | GANSS Receiver Geographical Position (GANSS RX Pos)..... | 526 |
+| 9.2.1.110 | GANSS Time Model..... | 526 |
+| 9.2.1.110a | GANSS Additional Time Models..... | 527 |
+| 9.2.1.111 | GANSS UTC Model..... | 527 |
+| 9.2.1.111a | GANSS Additional UTC Models..... | 527 |
+| 9.2.1.112 | TUTRAN-GANSS Accuracy Class..... | 529 |
+
+| | | |
+|------------|-------------------------------------------------------------------|-----|
+| 9.2.1.113 | T UTRAN-GANSS Measurement Threshold Information..... | 529 |
+| 9.2.1.114 | T UTRAN-GANSS Measurement Value Information..... | 530 |
+| 9.2.1.115 | GANSS Reference Time..... | 532 |
+| 9.2.1.116 | HARQ Memory Partitioning..... | 533 |
+| 9.2.1.117 | Multiple PLMN List..... | 534 |
+| 9.2.1.118 | GANSS Data Bit Assistance..... | 534 |
+| 9.2.1.119 | GANSS ID..... | 535 |
+| 9.2.1.119a | GANSS Time ID..... | 535 |
+| 9.2.1.120 | GANSS Navigation Model And Time Recovery..... | 535 |
+| 9.2.1.120a | GANSS Additional Navigation Models And Time Recovery..... | 536 |
+| 9.2.1.121 | GANSS Signal ID..... | 537 |
+| 9.2.1.122 | GANSS Transmission Time..... | 537 |
+| 9.2.1.122a | GANSS Earth Orientation Parameters..... | 537 |
+| 9.2.1.122b | SBAS ID..... | 538 |
+| 9.2.1.122c | GANSS Auxiliary Information..... | 538 |
+| 9.2.1.122d | Additional Ionospheric Model Request..... | 538 |
+| 9.2.1.122e | Earth Orientation Parameters Request..... | 538 |
+| 9.2.1.122f | GANSS Additional Navigation Models And Time Recovery Request..... | 539 |
+| 9.2.1.122g | GANSS Additional UTC Models Request..... | 539 |
+| 9.2.1.122h | GANSS Auxiliary Information Request..... | 539 |
+| 9.2.1.123 | SixtyfourQAM DL Support Indicator..... | 539 |
+| 9.2.1.124 | RANAP Enhanced Relocation Information Request..... | 539 |
+| 9.2.1.125 | RANAP Enhanced Relocation Information Response..... | 539 |
+| 9.2.1.126 | Released CN Domain..... | 540 |
+| 9.2.1.127 | Secondary CCPCH system information MBMS..... | 540 |
+| 9.2.1.128 | MBSFN Cluster Identity..... | 540 |
+| 9.2.1.129 | MBSFN Scheduling Transmission Time Interval..... | 540 |
+| 9.2.1.130 | MAC-ehs Reset Timer..... | 540 |
+| 9.2.1.131 | Enhanced FACH Support Indicator..... | 540 |
+| 9.2.1.132 | Enhanced PCH Capability ..... | 541 |
+| 9.2.1.133 | Priority Queue Information for Enhanced FACH/PCH..... | 541 |
+| 9.2.1.134 | MIMO Activation Indicator..... | 541 |
+| 9.2.1.135 | MIMO Mode Indicator..... | 541 |
+| 9.2.1.136 | DL RLC PDU Size Format..... | 542 |
+| 9.2.1.137 | UE Aggregate Maximum Bit Rate..... | 542 |
+| 9.2.1.138 | DGNSS Validity Period..... | 542 |
+| 9.2.1.139 | MDT Configuration..... | 543 |
+| 9.2.1.140 | MDT Report parameters..... | 545 |
+| 9.2.1.141 | Neighbouring UMTS Cell Information Extension..... | 545 |
+| 9.2.1.142 | Source ID..... | 546 |
+| 9.2.1.143 | Target ID..... | 546 |
+| 9.2.1.144 | MS Classmark 2..... | 546 |
+| 9.2.1.145 | MS Classmark 3..... | 546 |
+| 9.2.1.146 | Speech Version..... | 547 |
+| 9.2.1.147 | Controlled Object Scope..... | 547 |
+| 9.2.1.148 | ANR Report Indication..... | 547 |
+| 9.2.1.149 | ANR Cell Information..... | 548 |
+| 9.2.1.150 | ANR FDD Cell Information..... | 548 |
+| 9.2.1.151 | ANR TDD Cell Information..... | 549 |
+| 9.2.1.152 | ANR TDD Cell Information LCR..... | 549 |
+| 9.2.1.153 | ANR Multiple PLMN List..... | 550 |
+| 9.2.1.154 | Extended RNTI..... | 550 |
+| 9.2.1.155 | Extended S-RNTI Group..... | 550 |
+| 9.2.1.156 | Common E-RGCH Cell Information..... | 551 |
+| 9.2.2 | FDD Specific Parameters..... | 551 |
+| 9.2.2.a | ACK-NACK Repetition Factor..... | 551 |
+| 9.2.2.b | ACK Power Offset..... | 551 |
+| 9.2.2.A | Active Pattern Sequence Information..... | 551 |
+| 9.2.2.B | Adjustment Period..... | 552 |
+| 9.2.2.C | Adjustment Ratio..... | 552 |
+| 9.2.2.Ca | Bundling Mode Indicator..... | 553 |
+
+| | | |
+|------------|-----------------------------------------------------------------------------------|-----|
+| 9.2.2.D | Cell Capability Container FDD..... | 553 |
+| 9.2.2.E | Cell Portion ID..... | 555 |
+| 9.2.2.1 | Chip Offset..... | 555 |
+| 9.2.2.2 | Closed Loop Mode1 Support Indicator..... | 556 |
+| 9.2.2.3 | Closed Loop Mode2 Support Indicator..... | 556 |
+| 9.2.2.3A | Closed Loop Timing Adjustment Mode..... | 556 |
+| 9.2.2.4 | Compressed Mode Method..... | 556 |
+| 9.2.2.4A | DCH FDD Information..... | 556 |
+| 9.2.2.4B | E-DCH FDD Information..... | 557 |
+| 9.2.2.4C | E-DCH FDD Information Response..... | 558 |
+| 9.2.2.4D | E-DCH FDD DL Control Channel Information..... | 559 |
+| 9.2.2.4E | E-DCH RL Indication..... | 561 |
+| 9.2.2.4F | E-DCH FDD Information To Modify..... | 561 |
+| 9.2.2.4G | E-DCH Transport Format Combination Set Information (E-TFCS Information)..... | 565 |
+| 9.2.2.4J | E-TTI..... | 567 |
+| 9.2.2.4K | E-DPCCH Power Offset..... | 567 |
+| 9.2.2.4KA | Void..... | 567 |
+| 9.2.2.4L | E-DCH HARQ Power Offset FDD..... | 567 |
+| 9.2.2.4M | Void..... | 567 |
+| 9.2.2.4MA | Void..... | 567 |
+| 9.2.2.4MB | Void..... | 567 |
+| 9.2.2.4MC | E-DCH MAC-d Flows Information..... | 567 |
+| 9.2.2.4MD | Void..... | 569 |
+| 9.2.2.4ME | Void..... | 569 |
+| 9.2.2.4MF | Void..... | 569 |
+| 9.2.2.4MG | E-DCH Maximum Bitrate..... | 569 |
+| 9.2.2.4MH | Void..... | 569 |
+| 9.2.2.4MI | E-DCH Reference Power Offset..... | 569 |
+| 9.2.2.4MJ | Void..... | 569 |
+| 9.2.2.4N | Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission..... | 569 |
+| 9.2.2.4O | HARQ Process Allocation For 2ms TTI..... | 570 |
+| 9.2.2.4P | Reference E-TFCI Power Offset..... | 570 |
+| 9.2.2.4Q | Extended Reference E-TFCI Power Offset..... | 570 |
+| 9.2.2.4R | Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission..... | 570 |
+| 9.2.2.4S | Transport Bearer Not Requested Indicator..... | 571 |
+| 9.2.2.4T | Transport Bearer Not Setup Indicator..... | 571 |
+| 9.2.2.5 | D-Field Length..... | 571 |
+| 9.2.2.6 | Diversity Control Field..... | 571 |
+| 9.2.2.7 | Diversity Indication..... | 571 |
+| 9.2.2.8 | Diversity Mode..... | 571 |
+| 9.2.2.9 | DL DPCH Slot Format..... | 571 |
+| 9.2.2.9A | DL DPCH Timing Adjustment..... | 572 |
+| 9.2.2.10 | DL Power..... | 572 |
+| 9.2.2.10A | DL Power Balancing Information..... | 572 |
+| 9.2.2.10B | DL Power Balancing Activation Indicator..... | 572 |
+| 9.2.2.10C | DL Reference Power Information..... | 573 |
+| 9.2.2.10D | DL Power Balancing Updated Indicator..... | 573 |
+| 9.2.2.11 | DL Scrambling Code..... | 573 |
+| 9.2.2.12 | Downlink Frame Type..... | 573 |
+| 9.2.2.12A | DPC Mode..... | 573 |
+| 9.2.2.13 | DRAC Control..... | 574 |
+| 9.2.2.13A | DSCH FDD Information..... | 574 |
+| 9.2.2.13B | DSCH FDD Information Response..... | 574 |
+| 9.2.2.13Bb | DSCH-RNTI..... | 574 |
+| 9.2.2.13C | FDD DCHs To Modify..... | 574 |
+| 9.2.2.13D | Enhanced DSCH PC..... | 575 |
+| 9.2.2.13E | Enhanced DSCH PC Counter..... | 575 |
+| 9.2.2.13F | Enhanced DSCH PC Indicator..... | 575 |
+| 9.2.2.13G | Enhanced DSCH PC Wnd..... | 575 |
+| 9.2.2.13H | Enhanced DSCH Power Offset..... | 575 |
+| 9.2.2.13I | Enhanced Primary CPICH Ec/No..... | 575 |
+
+| | | |
+|------------|-------------------------------------------------------------------------|-----|
+| 9.2.2.14 | FDD DL Channelisation Code Number..... | 576 |
+| 9.2.2.14A | FDD DL Code Information..... | 576 |
+| 9.2.2.15 | FDD S-CCPCH Offset..... | 576 |
+| 9.2.2.16 | FDD TPC Downlink Step Size..... | 576 |
+| 9.2.2.16A | First RLS Indicator..... | 576 |
+| 9.2.2.17 | Gap Position Mode..... | 577 |
+| 9.2.2.18 | Gap Period (TGP)..... | 577 |
+| 9.2.2.19 | Gap Starting Slot Number (SN)..... | 577 |
+| 9.2.2.19a | HS-DSCH FDD Information..... | 577 |
+| 9.2.2.19aa | HS-DSCH FDD Secondary Serving Information..... | 579 |
+| 9.2.2.19b | HS-DSCH FDD Information Response..... | 581 |
+| 9.2.2.19ba | HS-DSCH FDD Secondary Serving Information Response..... | 582 |
+| 9.2.2.19bb | HS-DSCH FDD Secondary Serving Information To Modify..... | 582 |
+| 9.2.2.19bc | HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised..... | 584 |
+| 9.2.2.19c | HS-DSCH FDD Update Information..... | 586 |
+| 9.2.2.19ca | HS-DSCH FDD Secondary Serving Update Information..... | 586 |
+| 9.2.2.19C | HS-DSCH configured indicator..... | 586 |
+| 9.2.2.19d | HS-SCCH Power Offset..... | 586 |
+| 9.2.2.19e | E-DCH FDD Update Information..... | 587 |
+| 9.2.2.19f | HS-DSCH Serving Cell Change Information..... | 587 |
+| 9.2.2.19g | HS-DSCH Serving Cell Change Information Response..... | 587 |
+| 9.2.2.19ga | HS-DSCH Secondary Serving Cell Change Information Response..... | 588 |
+| 9.2.2.19G | HS-DSCH TB Size Table Indicator..... | 588 |
+| 9.2.2.19h | E-DCH Serving Cell Change Information Response..... | 588 |
+| 9.2.2.20 | IB_SG_POS..... | 589 |
+| 9.2.2.21 | IB_SG_REP..... | 589 |
+| 9.2.2.21a | Inner Loop DL PC Status..... | 589 |
+| 9.2.2.21b | Initial DL DPCH Timing Adjustment Allowed..... | 589 |
+| 9.2.2.21A | Limited Power Increase..... | 589 |
+| 9.2.2.21B | IPDL FDD Parameters..... | 589 |
+| 9.2.2.21C | Length of TFCI2..... | 590 |
+| 9.2.2.21D | Void..... | 590 |
+| 9.2.2.21E | Void..... | 590 |
+| 9.2.2.21F | Void..... | 590 |
+| 9.2.2.22 | Max Adjustment Period..... | 590 |
+| 9.2.2.23 | Max Adjustment Step..... | 590 |
+| 9.2.2.24 | Max Number of UL DPDCHs..... | 590 |
+| 9.2.2.24a | CQI Feedback Cycle k..... | 590 |
+| 9.2.2.24b | CQI Power Offset..... | 590 |
+| 9.2.2.24c | CQI Repetition Factor..... | 590 |
+| 9.2.2.24d | Measurement Power Offset..... | 591 |
+| 9.2.2.24e | Maximum Set of E-DPDCHs..... | 591 |
+| 9.2.2.24f | Void..... | 591 |
+| 9.2.2.24A | Min DL Channelisation Code Length..... | 591 |
+| 9.2.2.25 | Min UL Channelisation Code Length..... | 591 |
+| 9.2.2.26 | Multiplexing Position..... | 591 |
+| 9.2.2.26a | NACK Power Offset..... | 592 |
+| 9.2.2.26A | Number of DL Channelisation Codes..... | 592 |
+| 9.2.2.27 | Pattern Duration (PD)..... | 592 |
+| 9.2.2.27a | PC Preamble..... | 592 |
+| 9.2.2.27A | PDSCH Code Mapping..... | 592 |
+| 9.2.2.27B | Phase Reference Update Indicator..... | 592 |
+| 9.2.2.28 | Power Adjustment Type..... | 592 |
+| 9.2.2.29 | Power Control Mode (PCM)..... | 593 |
+| 9.2.2.30 | Power Offset..... | 593 |
+| 9.2.2.31 | Power Resume Mode (PRM)..... | 593 |
+| 9.2.2.31A | Preamble Signatures..... | 593 |
+| 9.2.2.32 | Primary CPICH Ec/No..... | 593 |
+| 9.2.2.32A | Primary CPICH Usage For Channel Estimation..... | 593 |
+| 9.2.2.33 | Propagation Delay (PD)..... | 593 |
+| 9.2.2.33a | Extended Propagation Delay..... | 594 |
+
+| | | |
+|-----------|-----------------------------------------------------------------------|-----|
+| 9.2.2.33A | PRACH Minimum Spreading Factor..... | 594 |
+| 9.2.2.34 | QE-Selector..... | 594 |
+| 9.2.2.34a | Qth Parameter..... | 594 |
+| 9.2.2.34A | RACH Sub Channel Numbers..... | 594 |
+| 9.2.2.35 | RL Set ID..... | 594 |
+| 9.2.2.35a | RL Specific E-DCH Information..... | 594 |
+| 9.2.2.35A | Received Total Wide Band Power..... | 595 |
+| 9.2.2.36 | S-Field Length..... | 595 |
+| 9.2.2.36A | Void..... | 595 |
+| 9.2.2.37 | Scrambling Code Change..... | 595 |
+| 9.2.2.37A | Scrambling Code Number..... | 595 |
+| 9.2.2.37B | Secondary CCPCH Info..... | 595 |
+| 9.2.2.38 | Secondary CCPCH Slot Format..... | 595 |
+| 9.2.2.38A | Secondary CPICH Information..... | 595 |
+| 9.2.2.38B | Secondary CPICH Information Change..... | 595 |
+| 9.2.2.38C | Serving E-DCH RL..... | 596 |
+| 9.2.2.39 | Slot Number (SN)..... | 596 |
+| 9.2.2.39a | Split Type..... | 596 |
+| 9.2.2.39A | SRB Delay..... | 596 |
+| 9.2.2.40 | SSDT Cell Identity..... | 596 |
+| 9.2.2.40A | SSDT Cell Identity for EDSCHPC..... | 596 |
+| 9.2.2.41 | SSDT Cell Identity Length..... | 596 |
+| 9.2.2.42 | SSDT Indication..... | 596 |
+| 9.2.2.43 | SSDT Support Indicator..... | 596 |
+| 9.2.2.44 | STTD Indicator..... | 596 |
+| 9.2.2.45 | STTD Support Indicator..... | 597 |
+| 9.2.2.45A | Synchronisation Indicator..... | 597 |
+| 9.2.2.46 | TFCI Signalling Mode..... | 597 |
+| 9.2.2.46A | TFCI PC Support Indicator..... | 597 |
+| 9.2.2.47 | Transmission Gap Distance (TGD)..... | 597 |
+| 9.2.2.47A | Transmission Gap Pattern Sequence Information..... | 597 |
+| 9.2.2.47B | Transmission Gap Pattern Sequence Scrambling Code Information..... | 599 |
+| 9.2.2.48 | Transmit Diversity Indicator..... | 599 |
+| 9.2.2.49 | Transmit Gap Length (TGL)..... | 599 |
+| 9.2.2.50 | Tx Diversity Indicator..... | 599 |
+| 9.2.2.50A | UE Support Of Dedicated Pilots For Channel Estimation..... | 600 |
+| 9.2.2.50B | UE Support Of Dedicated Pilots For Channel Estimation Of HS-DSCH..... | 600 |
+| 9.2.2.51 | UL/DL Compressed Mode Selection..... | 600 |
+| 9.2.2.52 | UL DPCCH Slot Format..... | 600 |
+| 9.2.2.52A | UL DPDCH Indicator for E-DCH operation..... | 600 |
+| 9.2.2.53 | UL Scrambling Code..... | 600 |
+| 9.2.2.54 | Uplink Delta SIR..... | 600 |
+| 9.2.2.55 | Uplink Delta SIR After..... | 601 |
+| 9.2.2.56 | DPC Mode Change Support Indicator..... | 601 |
+| 9.2.2.57 | HARQ Preamble Mode..... | 601 |
+| 9.2.2.58 | HARQ Preamble Mode Activation Indicator..... | 601 |
+| 9.2.2.59 | Frequency Band Indicator..... | 601 |
+| 9.2.2.60 | E-RGCH Release Indicator..... | 602 |
+| 9.2.2.61 | E-AGCH Power Offset..... | 602 |
+| 9.2.2.61A | E-AGCH Table Choice..... | 602 |
+| 9.2.2.62 | E-RGCH Power Offset..... | 603 |
+| 9.2.2.63 | E-HICH Power Offset..... | 603 |
+| 9.2.2.64 | E-RGCH 2-Index-Step Threshold..... | 603 |
+| 9.2.2.65 | E-RGCH 3-Index-Step Threshold..... | 603 |
+| 9.2.2.66 | HARQ Info for E-DCH..... | 603 |
+| 9.2.2.67 | DCH Indicator For E-DCH-HSDPA Operation..... | 604 |
+| 9.2.2.68 | E-RGCH and E-HICH Channelisation Code Validity Indicator..... | 604 |
+| 9.2.2.69 | E-DCH Minimum Set E-TFCI Validity Indicator..... | 604 |
+| 9.2.2.70 | Fast Reconfiguration Mode..... | 604 |
+| 9.2.2.71 | Fast Reconfiguration Permission..... | 605 |
+| 9.2.2.72 | Continuous Packet Connectivity DTX-DRX Information..... | 605 |
+
+| | | |
+|-----------|-----------------------------------------------------------------------|-----|
+| 9.2.2.73 | Continuous Packet Connectivity DTX-DRX Information To Modify..... | 606 |
+| 9.2.2.74 | Continuous Packet Connectivity HS-SCCH less Information..... | 607 |
+| 9.2.2.75 | Continuous Packet Connectivity HS-SCCH less Information Response..... | 607 |
+| 9.2.2.75A | Continuous Packet Connectivity HS-SCCH Less Deactivate Indicator..... | 608 |
+| 9.2.2.76 | MIMO Activation Indicator..... | 608 |
+| 9.2.2.77 | MIMO Mode Indicator..... | 608 |
+| 9.2.2.78 | MIMO Information Response..... | 608 |
+| 9.2.2.79 | SixtyfourQAM DL Support Indicator..... | 608 |
+| 9.2.2.79A | Sixtyfour QAM Usage Allowed Indicator..... | 608 |
+| 9.2.2.79B | SixtyfourQAM DL Usage Indicator..... | 609 |
+| 9.2.2.80 | Enhanced FACH Support Indicator ..... | 609 |
+| 9.2.2.81 | Enhanced PCH Support Indicator ..... | 609 |
+| 9.2.2.82 | Priority Queue Information for Enhanced FACH/PCH..... | 609 |
+| 9.2.2.83 | SixteenQAM UL Information..... | 609 |
+| 9.2.2.84 | SixteenQAM UL Information To Modify..... | 609 |
+| 9.2.2.85 | F-DPCH Slot Format..... | 609 |
+| 9.2.2.86 | F-DPCH Slot Format Support Request..... | 609 |
+| 9.2.2.87 | Max UE DTX Cycle..... | 609 |
+| 9.2.2.88 | Enhanced PCH Capability ..... | 609 |
+| 9.2.2.89 | MAC-ehs Reset Timer..... | 610 |
+| 9.2.2.90 | SixteenQAM UL Operation Indicator..... | 610 |
+| 9.2.2.90a | SixtyfourQAM UL Operation Indicator..... | 610 |
+| 9.2.2.91 | E-TFCI Boost Information..... | 610 |
+| 9.2.2.92 | Common E-DCH Support Indicator..... | 610 |
+| 9.2.2.93 | Common E-DCH MAC-d Flow Specific Information..... | 610 |
+| 9.2.2.94 | Counting Information..... | 611 |
+| 9.2.2.95 | Transmission Mode Information..... | 611 |
+| 9.2.2.96 | MBMS Neighbouring Cell Information..... | 612 |
+| 9.2.2.97 | RLC Sequence Number..... | 612 |
+| 9.2.2.98 | Time Stamp..... | 612 |
+| 9.2.2.99 | HS-DSCH Preconfiguration Info..... | 612 |
+| 9.2.2.100 | HS-DSCH Preconfiguration Setup..... | 614 |
+| 9.2.2.101 | Secondary Serving Cell List..... | 617 |
+| 9.2.2.102 | Minimum Reduced E-DPDCH Gain Factor..... | 617 |
+| 9.2.2.103 | UE Support Indicator Extension..... | 617 |
+| 9.2.2.104 | Power Offset For S-CPICH for MIMO..... | 618 |
+| 9.2.2.105 | Power Offset For S-CPICH for MIMO Request Indicator..... | 618 |
+| 9.2.2.106 | Single Stream MIMO Activation Indicator..... | 619 |
+| 9.2.2.107 | Single Stream MIMO Mode Indicator..... | 619 |
+| 9.2.2.108 | HS-DSCH MAC-ehs Format..... | 619 |
+| 9.2.2.109 | Activation Information..... | 619 |
+| 9.2.2.110 | Additional E-DCH FDD Setup Information..... | 619 |
+| 9.2.2.111 | Additional E-DCH Configuration Change Information..... | 620 |
+| 9.2.2.112 | Additional E-DCH FDD Information..... | 620 |
+| 9.2.2.113 | Multicell E-DCH Transport Bearer Mode..... | 621 |
+| 9.2.2.114 | Multicell E-DCH Information..... | 621 |
+| 9.2.2.115 | Additional E-DCH RL Specific Information To Setup..... | 621 |
+| 9.2.2.116 | Additional E-DCH RL Specific Information To Add..... | 622 |
+| 9.2.2.117 | Additional E-DCH RL Specific Information To Modify..... | 622 |
+| 9.2.2.118 | Additional E-DCH MAC-d Flow Specific Information..... | 623 |
+| 9.2.2.119 | Multicell E-DCH RL Specific Information..... | 623 |
+| 9.2.2.120 | Additional E-DCH FDD Information Response..... | 623 |
+| 9.2.2.121 | Additional Modified E-DCH FDD Information Response..... | 625 |
+| 9.2.2.122 | Additional E-DCH FDD Update Information..... | 625 |
+| 9.2.2.123 | Cell Capability Container Extension FDD..... | 626 |
+| 9.2.2.124 | Non-Serving RL Preconfiguration Setup..... | 629 |
+| 9.2.2.125 | Non-Serving RL Preconfiguration Info..... | 630 |
+| 9.2.2.126 | Void..... | 632 |
+| 9.2.2.127 | Usefulness of Battery Optimization..... | 632 |
+| 9.2.2.128 | M1 Report..... | 632 |
+| 9.2.2.129 | Support of Dynamic DTXDRX Related HS-SCCH Order..... | 632 |
+
+| | | |
+|-----------|--------------------------------------------------------------------------------------|-----|
+| 9.2.2.130 | UL CLTD Information Reconf..... | 632 |
+| 9.2.2.131 | UL CLTD Information..... | 633 |
+| 9.2.2.132 | UL CLTD Information To Modify..... | 633 |
+| 9.2.2.133 | UL CLTD Information Removal..... | 633 |
+| 9.2.2.134 | UL CLTD State Update Information..... | 634 |
+| 9.2.2.135 | F-TPICH Slot Format..... | 634 |
+| 9.2.2.136 | F-TPICH Offset..... | 634 |
+| 9.2.2.137 | S-DPCCH Power Offset Information..... | 634 |
+| 9.2.2.138 | UL CLTD Activation Information..... | 634 |
+| 9.2.2.139 | F-TPICH Information..... | 634 |
+| 9.2.2.140 | F-TPICH Information To Modify..... | 635 |
+| 9.2.2.141 | F-TPICH Information Removal..... | 635 |
+| 9.2.2.142 | F-TPICH Information Reconf..... | 635 |
+| 9.2.2.143 | F-TPICH Information Response..... | 635 |
+| 9.2.2.144 | F-TPICH Reconfiguration Information..... | 635 |
+| 9.2.2.145 | MIMO with four transmit antennas Activation Indicator..... | 636 |
+| 9.2.2.146 | MIMO with four transmit antennas Mode Indicator..... | 636 |
+| 9.2.2.147 | Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator..... | 636 |
+| 9.2.2.148 | Power Offset For S-CPICH for MIMO with four transmit antennas..... | 636 |
+| 9.2.2.149 | Dual Stream MIMO with four transmit antennas Activation Indicator..... | 637 |
+| 9.2.2.150 | Dual Stream MIMO with four transmit antennas Mode Indicator..... | 637 |
+| 9.2.2.151 | Multiflow Reconfiguration..... | 637 |
+| 9.2.2.152 | Multiflow Information..... | 637 |
+| 9.2.2.153 | Multiflow Information To Modify..... | 638 |
+| 9.2.2.154 | Multiflow Stop..... | 638 |
+| 9.2.2.155 | Multiflow Role..... | 639 |
+| 9.2.2.156 | Multiflow MIMO..... | 639 |
+| 9.2.2.157 | Multiflow Timing..... | 639 |
+| 9.2.2.158 | UL MIMO Reconfiguration..... | 639 |
+| 9.2.2.159 | UL MIMO Information..... | 640 |
+| 9.2.2.160 | UL MIMO Information To Modify..... | 640 |
+| 9.2.2.161 | UL MIMO Information Removal..... | 640 |
+| 9.2.2.162 | UL MIMO DL Control Channel Information..... | 641 |
+| 9.2.2.163 | E-ROCH Power Offset..... | 641 |
+| 9.2.2.164 | S-E-DPCCH Power Offset..... | 641 |
+| 9.2.2.165 | Inter-stream Interference Compensation Index..... | 641 |
+| 9.2.2.166 | Secondary Transport Block E-HICH Release Indicator..... | 642 |
+| 9.2.2.167 | Precoder weight set restriction..... | 642 |
+| 9.2.2.168 | Multiflow Repetition Factors..... | 642 |
+| 9.2.3 | TDD Specific Parameters..... | 642 |
+| 9.2.3.a | Alpha Value..... | 642 |
+| 9.2.3.A | Block STTD Indicator..... | 643 |
+| 9.2.3.1 | Burst Type..... | 643 |
+| 9.2.3.1a | Cell Capability Container TDD..... | 643 |
+| 9.2.3.1b | Cell Capability Container TDD LCR..... | 643 |
+| 9.2.3.2 | CCTrCH ID..... | 644 |
+| 9.2.3.2A | DCH TDD Information..... | 644 |
+| 9.2.3.2B | DCH TDD Information Response..... | 645 |
+| 9.2.3.2C | DL Timeslot Information..... | 645 |
+| 9.2.3.2D | DL Time Slot ISCP Info..... | 646 |
+| 9.2.3.2E | DL Timeslot Information LCR..... | 646 |
+| 9.2.3.2F | DL Time Slot ISCP Info LCR..... | 647 |
+| 9.2.3.3 | DPCH ID..... | 647 |
+| 9.2.3.3a | DSCH TDD Information..... | 647 |
+| 9.2.3.3aa | HS-DSCH TDD Information..... | 648 |
+| 9.2.3.3ab | HS-DSCH TDD Information Response..... | 650 |
+| 9.2.3.3ac | HS-DSCH TDD Update Information..... | 654 |
+| 9.2.3.3ad | HS-SICH ID..... | 654 |
+| 9.2.3.3ae | DSCH ID..... | 654 |
+| 9.2.3.3af | DSCH Initial Window Size..... | 654 |
+| 9.2.3.3ag | DSCH Flow Control Information..... | 655 |
+
+| | | |
+|------------|----------------------------------------------------------|-----|
+| 9.2.3.3ah | DSCH-RNTI..... | 655 |
+| 9.2.3.3ai | TSN-Length..... | 655 |
+| 9.2.3.3A | Maximum Number of Timeslots..... | 655 |
+| 9.2.3.3B | Maximum Number of UL Physical Channels per Timeslot..... | 656 |
+| 9.2.3.3C | Maximum Number of DL Physical Channels..... | 656 |
+| 9.2.3.3D | Maximum Number of DL Physical Channels per Timeslot..... | 656 |
+| 9.2.3.4 | Midamble Shift And Burst Type..... | 656 |
+| 9.2.3.4A | Minimum Spreading Factor..... | 657 |
+| 9.2.3.4B | IPDL TDD parameters..... | 657 |
+| 9.2.3.4Bb | IPDL TDD parameters LCR..... | 658 |
+| 9.2.3.4C | Midamble shift LCR..... | 658 |
+| 9.2.3.4D | Neighbouring TDD Cell Information LCR..... | 659 |
+| 9.2.3.5 | Primary CCPCH RSCP..... | 659 |
+| 9.2.3.5a | Primary CCPCH RSCP Delta..... | 659 |
+| 9.2.3.5A | PRACH Midamble..... | 659 |
+| 9.2.3.5B | RB Identity..... | 659 |
+| 9.2.3.6 | Repetition Length..... | 659 |
+| 9.2.3.7 | Repetition Period..... | 660 |
+| 9.2.3.7A | Rx Timing Deviation..... | 660 |
+| 9.2.3.7B | Secondary CCPCH Info TDD..... | 660 |
+| 9.2.3.7C | Secondary CCPCH TDD Code Information..... | 661 |
+| 9.2.3.7D | Special Burst Scheduling..... | 661 |
+| 9.2.3.7E | Synchronisation Configuration..... | 661 |
+| 9.2.3.7F | Secondary CCPCH Info TDD LCR..... | 661 |
+| 9.2.3.7G | Secondary CCPCH TDD Code Information LCR..... | 662 |
+| 9.2.3.7H | Support of 8PSK..... | 662 |
+| 9.2.3.7I | TDD ACK NACK Power Offset..... | 663 |
+| 9.2.3.8 | TDD Channelisation Code..... | 663 |
+| 9.2.3.8a | TDD Channelisation Code LCR..... | 663 |
+| 9.2.3.8A | TDD DPCH Offset..... | 663 |
+| 9.2.3.8B | TDD DCHs To Modify..... | 664 |
+| 9.2.3.8C | TDD DL Code Information..... | 664 |
+| 9.2.3.8D | TDD DL Code Information LCR..... | 665 |
+| 9.2.3.8E | TDD DL DPCH Time Slot Format LCR..... | 665 |
+| 9.2.3.9 | TDD Physical Channel Offset..... | 665 |
+| 9.2.3.10 | TDD TPC Downlink Step Size..... | 665 |
+| 9.2.3.10a | TDD TPC Uplink Step Size..... | 666 |
+| 9.2.3.10A | TDD UL Code Information..... | 666 |
+| 9.2.3.10B | TDD UL Code Information LCR..... | 666 |
+| 9.2.3.10C | TDD UL DPCH Time Slot Format LCR..... | 666 |
+| 9.2.3.10D | 1.28 Mcps TDD uplink physical channel capability..... | 667 |
+| 9.2.3.11 | TFCI Coding..... | 667 |
+| 9.2.3.12 | DL Timeslot ISCP..... | 667 |
+| 9.2.3.12a | Time Slot LCR..... | 667 |
+| 9.2.3.12A | Timing Advance Applied..... | 667 |
+| 9.2.3.13 | Transport Format Management..... | 668 |
+| 9.2.3.13A | UL Timeslot ISCP..... | 668 |
+| 9.2.3.13B | UL PhysCH SF Variation..... | 668 |
+| 9.2.3.13C | UL Timeslot Information..... | 668 |
+| 9.2.3.13D | UL Time Slot ISCP Info..... | 668 |
+| 9.2.3.13E | TSTD Indicator..... | 669 |
+| 9.2.3.13F | TSTD Support Indicator..... | 669 |
+| 9.2.3.13Fa | UE Measurement Hysteresis Time..... | 669 |
+| 9.2.3.13Fb | UE Measurement Parameter Modification Allowed..... | 669 |
+| 9.2.3.13Fc | UE Measurement Report Characteristics..... | 670 |
+| 9.2.3.13Fd | UE Measurement Threshold..... | 670 |
+| 9.2.3.13Fe | UE Measurement Timeslot Information HCR..... | 671 |
+| 9.2.3.13Ff | UE Measurement Timeslot Information LCR..... | 671 |
+| 9.2.3.13Fg | UE Measurement Time to Trigger..... | 671 |
+| 9.2.3.13Fh | UE Measurement Type..... | 672 |
+| 9.2.3.13Fi | UE Measurement Value..... | 672 |
+
+| | | |
+|------------|-------------------------------------------------------------------|-----|
+| 9.2.3.13Fj | UE Measurement Value Information..... | 673 |
+| 9.2.3.13G | UL Timeslot Information LCR..... | 673 |
+| 9.2.3.13H | UL Time Slot ISCP Info LCR..... | 673 |
+| 9.2.3.13I | Uplink Synchronisation Frequency..... | 674 |
+| 9.2.3.13J | Uplink Synchronisation Step Size..... | 674 |
+| 9.2.3.13K | Uplink Timing Advance Control LCR..... | 674 |
+| 9.2.3.13L | USCH ID..... | 675 |
+| 9.2.3.14 | USCH Information..... | 675 |
+| 9.2.3.16 | Support of PLCCH..... | 676 |
+| 9.2.3.17 | PLCCH Information..... | 676 |
+| 9.2.3.18 | PLCCH Sequence Number..... | 677 |
+| 9.2.3.19 | Minimum Spreading Factor 7.68Mcps..... | 677 |
+| 9.2.3.20 | Maximum Number of DL Physical Channels 7.68Mcps..... | 677 |
+| 9.2.3.21 | Maximum Number of DL Physical Channels per Timeslot 7.68Mcps..... | 677 |
+| 9.2.3.22 | Secondary CCPCH Info 7.68Mcps TDD..... | 677 |
+| 9.2.3.23 | Midamble Shift And Burst Type 7.68Mcps..... | 678 |
+| 9.2.3.24 | Secondary CCPCH TDD Code Information 7.68Mcps..... | 679 |
+| 9.2.3.25 | TDD Channelisation Code 7.68Mcps..... | 679 |
+| 9.2.3.26 | UL Timeslot Information 7.68Mcps..... | 680 |
+| 9.2.3.27 | TDD UL Code Information 7.68Mcps..... | 680 |
+| 9.2.3.28 | DL Timeslot Information 7.68Mcps..... | 680 |
+| 9.2.3.29 | TDD DL Code Information 7.68Mcps..... | 681 |
+| 9.2.3.30 | Rx Timing Deviation 7.68Mcps..... | 681 |
+| 9.2.3.31 | Cell Capability Container 7.68 Mcps TDD..... | 681 |
+| 9.2.3.32 | Neighbouring TDD Cell Measurement Information 7.68Mcps..... | 682 |
+| 9.2.3.33 | UE Measurement Timeslot Information 7.68Mcps..... | 682 |
+| 9.2.3.34 | DPCH ID 7.68Mcps..... | 683 |
+| 9.2.3.35 | Rx Timing Deviation 3.84Mcps Extended..... | 683 |
+| 9.2.3.36 | E-PUCH Information..... | 683 |
+| 9.2.3.36a | E-PUCH Information LCR..... | 683 |
+| 9.2.3.37 | E-TFCS Information TDD..... | 685 |
+| 9.2.3.38 | E-DCH MAC-d Flows Information TDD..... | 685 |
+| 9.2.3.39 | E-DCH Non-scheduled Grant Information TDD..... | 686 |
+| 9.2.3.39a | E-DCH Non-scheduled Grant Information LCR TDD..... | 687 |
+| 9.2.3.40 | E-DCH TDD Information..... | 687 |
+| 9.2.3.40a | E-DCH TDD Information LCR..... | 687 |
+| 9.2.3.41 | E-DCH TDD Information Response..... | 689 |
+| 9.2.3.41a | E-DCH TDD Information Response 1.28Mcps..... | 689 |
+| 9.2.3.42 | E-DCH TDD Information to Modify..... | 690 |
+| 9.2.3.43 | E-DCH Grant Type..... | 691 |
+| 9.2.3.44 | Timeslot Resource Related Information..... | 692 |
+| 9.2.3.44a | Timeslot Resource Related Information LCR..... | 692 |
+| 9.2.3.45 | Power Resource Related Information..... | 692 |
+| 9.2.3.46 | E-PUCH Offset..... | 692 |
+| 9.2.3.47 | E-DCH TDD Maximum Bitrate..... | 692 |
+| 9.2.3.48 | E-HICH Time Offset..... | 692 |
+| 9.2.3.48a | E-HICH Time Offset LCR..... | 693 |
+| 9.2.3.49 | E-DCH HARQ Power Offset TDD..... | 693 |
+| 9.2.3.49a | E-DCH MAC-d Flow Retransmission Timer..... | 693 |
+| 9.2.3.50 | E-DCH Non-scheduled Grant Information 7.68Mcps TDD..... | 693 |
+| 9.2.3.51 | E-DCH TDD Information 7.68Mcps..... | 693 |
+| 9.2.3.52 | E-DCH TDD Information Response 7.68Mcps..... | 694 |
+| 9.2.3.53 | E-DCH TDD Maximum Bitrate 7.68Mcps..... | 694 |
+| 9.2.3.54 | E-DCH Physical Layer Category LCR..... | 695 |
+| 9.2.3.54A | Extended E-DCH Physical layer Category LCR..... | 695 |
+| 9.2.3.54B | Multi-Carrier E-DCH Physical Layer Category LCR..... | 695 |
+| 9.2.3.55 | UpPCH Information LCR..... | 695 |
+| 9.2.3.56 | UpPCH Position LCR..... | 695 |
+| 9.2.3.57 | Common E-DCH MAC-d Flow ID..... | 695 |
+| 9.2.3.58 | Common E-DCH MAC-d Flow Specific Information LCR..... | 696 |
+| 9.2.3.59 | MAC-es Maximum Bit Rate LCR..... | 696 |
+
+| | | |
+|-----------------------------|-------------------------------------------------------------------------------------------------|-------------|
+| 9.2.3.60 | Idle Interval Information..... | 696 |
+| 9.2.3.61 | Continuous Packet Connectivity DRX Information LCR..... | 697 |
+| 9.2.3.62 | Continuous Packet Connectivity DRX Information To Modify LCR..... | 697 |
+| 9.2.3.63 | Continuous Packet Connectivity DRX Information Response LCR..... | 698 |
+| 9.2.3.64 | HS-DSCH Semi-Persistent scheduling Information LCR..... | 699 |
+| 9.2.3.65 | HS-DSCH Semi-Persistent scheduling Information to modify LCR..... | 700 |
+| 9.2.3.66 | E-DCH Semi-Persistent scheduling Information LCR..... | 701 |
+| 9.2.3.67 | E-DCH Semi-Persistent scheduling Information to modify LCR..... | 702 |
+| 9.2.3.68 | HS-DSCH Semi-Persistent scheduling Information Response LCR..... | 703 |
+| 9.2.3.69 | E-DCH Semi-Persistent scheduling Information Response LCR..... | 704 |
+| 9.2.3.70 | HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR..... | 705 |
+| 9.2.3.71 | E-DCH Semi-Persistent scheduling Deactivate Indicator LCR..... | 705 |
+| 9.2.3.72 | HS-SICH Reference Signal Information..... | 705 |
+| 9.2.3.73 | Cell Portion LCR ID..... | 705 |
+| 9.2.3.74 | TS0 HS-PDSCH Indication LCR..... | 706 |
+| 9.2.3.75 | DCH Measurement Occasion Information..... | 706 |
+| 9.2.3.76 | DCH Measurement Type Indicator..... | 707 |
+| 9.2.3.77 | Multi-Carrier E-DCH Information LCR..... | 708 |
+| 9.2.3.78 | Multi-Carrier E-DCH Information Response LCR..... | 709 |
+| 9.2.3.79 | Multi-Carrier E-DCH Transport Bearer Mode LCR..... | 709 |
+| 9.2.3.80 | Cell Capability Container Extension TDD LCR..... | 709 |
+| 9.2.3.81 | MU-MIMO Information..... | 710 |
+| 9.2.3.82 | MU-MIMO Indicator..... | 711 |
+| 9.2.3.83 | M2 Report..... | 711 |
+| 9.2.3.84 | UE RF Band Capability LCR..... | 711 |
+| 9.3 | Message and Information Element Abstract Syntax (with ASN.1)..... | 712 |
+| 9.3.0 | General..... | 712 |
+| 9.3.1 | Usage of Private Message Mechanism for Non-standard Use..... | 712 |
+| 9.3.2 | Elementary Procedure Definitions..... | 712 |
+| 9.3.3 | PDU Definitions..... | 729 |
+| 9.3.4 | Information Element Definitions..... | 911 |
+| 9.3.5 | Common Definitions..... | 1137 |
+| 9.3.6 | Constant Definitions..... | 1138 |
+| 9.3.7 | Container Definitions..... | 1159 |
+| 9.4 | Message Transfer Syntax..... | 1164 |
+| 9.5 | Timers..... | 1164 |
+| 10 | Handling of Unknown, Unforeseen and Erroneous Protocol Data..... | 1164 |
+| 10.1 | General..... | 1164 |
+| 10.2 | Transfer Syntax Error..... | 1164 |
+| 10.3 | Abstract Syntax Error..... | 1165 |
+| 10.3.1 | General..... | 1165 |
+| 10.3.2 | Criticality Information..... | 1165 |
+| 10.3.3 | Presence Information..... | 1166 |
+| 10.3.4 | Not Comprehended IE/IE Group..... | 1166 |
+| 10.3.4.1 | Procedure ID..... | 1166 |
+| 10.3.4.1A | Type of Message..... | 1166 |
+| 10.3.4.2 | IEs Other Than the Procedure ID and Type of Message..... | 1166 |
+| 10.3.5 | Missing IE or IE Group..... | 1168 |
+| 10.3.6 | IEs or IE Groups Received in Wrong Order or With Too Many Occurrences or Erroneously Present. . | 1169 |
+| 10.4 | Logical Error..... | 1169 |
+| 10.5 | Exceptions..... | 1170 |
+| Annex A (normative): | Allocation and Pre-emption of Radio Links in the DRNS..... | 1171 |
+| A.1 | Deriving Allocation Information for a Radio Link..... | 1171 |
+| A.1.1 | Establishment of a New Radio Link..... | 1171 |
+| A.1.2 | Modification of an Existing Radio Link..... | 1171 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------------------------|-------------|
+| A.2 | Deriving Retention Information for a Radio Link..... | 1172 |
+| A.3 | The Allocation/Retention Process..... | 1172 |
+| A.4 | The Pre-emption Process..... | 1173 |
+| Annex B (informative): | Measurement Reporting..... | 1173 |
+| Annex C (informative): | Guidelines for Usage of the Criticality Diagnostics IE..... | 1180 |
+| C.1 | EXAMPLE MESSAGE Layout..... | 1180 |
+| C.2 | Example on a Received EXAMPLE MESSAGE..... | 1182 |
+| C.3 | Content of Criticality Diagnostics..... | 1183 |
+| C.3.1 | Example 1..... | 1183 |
+| C.3.2 | Example 2..... | 1184 |
+| C.3.3 | Example 3..... | 1185 |
+| C.3.4 | Example 4..... | 1186 |
+| C.3.5 | Example 5..... | 1187 |
+| C.4 | ASN.1 of EXAMPLE MESSAGE..... | 1187 |
+| Annex D (normative): | DRNS Behaviour at SRNC or RNSAP Signalling Bearer Failure..... | 1190 |
+| D.1 | Detection of SRNC or RNSAP Signalling Bearer/Connection Failure..... | 1190 |
+| D.1.1 | Termination of all UE Contexts Related to a Specific SRNC..... | 1190 |
+| D.1.2 | Termination of Specific UE Context..... | 1190 |
+| D.2 | DRNC Actions at UE Context Termination..... | 1190 |
+| Annex E (informative): | Change History..... | 1191 |
+
+---
+
+## Foreword
+
+This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+---
+
+# 1 Scope
+
+The present document specifies the radio network layer signalling procedures of the control plane between RNCs in UTRAN, between RNC in UTRAN and BSS in GERAN Iu mode and between BSSs in GERAN Iu mode.
+
+---
+
+# 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 23.003: "Numbering, addressing and identification".
+- [2] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+- [3] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport & Transport Layer Signalling for DCH Data Streams".
+- [4] 3GPP TS 25.427: "UTRAN Iur and Iub Interface User Plane Protocols for DCH Data Streams".
+- [5] 3GPP TS 25.435: "UTRAN Iub interface User Plane Protocols for Common Transport Channel Data Streams".
+- [6] 3GPP TS 25.104: "UTRA (BS) FDD; Radio transmission and Reception".
+- [7] 3GPP TS 25.105: "UTRA (BS) TDD; Radio Transmission and Reception".
+- [8] 3GPP TS 25.211: "Physical Channels and Mapping of Transport Channels onto Physical Channels (FDD)".
+- [9] 3GPP TS 25.212: "Multiplexing and Channel Coding (FDD)".
+- [10] 3GPP TS 25.214: "Physical Layer Procedures (FDD)".
+- [11] 3GPP TS 25.215: "Physical Layer – Measurements (FDD)".
+- [12] 3GPP TS 25.221: "Physical Channels and Mapping of Transport Channels onto Physical Channels (TDD)".
+- [13] 3GPP TS 25.223: "Spreading and Modulation (TDD)".
+- [14] 3GPP TS 25.225: "Physical Layer – Measurements (TDD)".
+- [15] 3GPP TS 25.304: "UE Procedures in Idle Mode"
+- [16] 3GPP TS 25.331: "RRC Protocol Specification".
+- [17] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2".
+- [18] ITU-T Recommendation X.680 (2002-07): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+- [19] ITU-T Recommendation X.681 (2002-07): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification".
+
+- [20] ITU-T Recommendation X.691 (2002-07): “Information technology – ASN.1 encoding rules – Specification of Packed Encoding Rules (PER)”.
+- [21] 3GPP TS 25.213: “Spreading and modulation (FDD)”.
+- [22] 3GPP TS 25.224: “Physical Layer Procedures (TDD)”.
+- [23] 3GPP TS 25.133: “Requirements for support of Radio Resource management (FDD)”.
+- [24] 3GPP TS 25.123: “Requirements for support of Radio Resource management (TDD)”.
+- [25] 3GPP TS 23.032: “Universal Graphical Area Description (GAD)”.
+- [26] 3GPP TS 25.302: “Services Provided by the Physical Layer”.
+- [27] 3GPP TS 25.213: “Spreading and modulation (FDD)”.
+- [28] 3GPP TR 25.921 (version.7.0.0): “Guidelines and Principles for Protocol Description and Error Handling”.
+- [29] Void
+- [30] ICD-GPS-200: “Navstar GPS Space Segment/Navigation User Interface”.
+- [31] RTCM-SC104: “RTCM Recommended Standards for Differential GNSS Service (v.2.2)”.
+- [32] 3GPP TS 25.425: “UTRAN Iur and Iub Interface User Plane Protocols for Common Transport Channel data streams “.
+- [33] IETF RFC 2460 (1998-12): “Internet Protocol, Version 6 (Ipv6) Specification”.
+- [34] IETF RFC 768 (1980-08): “User Datagram Protocol”.
+- [35] 3GPP TS 25.424: “ UTRAN Iur Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams “.
+- [36] 3GPP TS 44.118: “Mobile radio interface layer 3 specification; Radio Resource Control (RRC) Protocol Iu mode”.
+- [37] Void
+- [38] 3GPP TS 48.008: “Mobile-services Switching Centre – Base Station System (MSC – BSS) interface; Layer 3 specification”.
+- [39] 3GPP TS 43.051: “GSM/EGDE Radio Access Network; Overall description – Stage 2”.
+- [40] 3GPP TS 25.401: “UTRAN Overall Description”.
+- [41] 3GPP TS 25.321: “MAC protocol specification”.
+- [42] 3GPP TS 25.306: “UE Radio Access capabilities”.
+- [43] 3GPP TS 25.101: “ User Equipment (UE) radio transmission and reception (FDD)”.
+- [44] IETF RFC 2474 (1998-12): “Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers”.
+- [45] IETF RFC 2475 (1998-12): “An Architecture for Differentiated Services”.
+- [46] 3GPP TS 25.222: “Multiplexing and Channel Coding (TDD)”.
+- [47] 3GPP TS 44.060: “General Packet Radio Service (GPRS); Mobile Station (MS) – Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol”.
+- [48] 3GPP TS 32.421: “Subscriber and equipment trace: Trace concepts and requirements”.
+- [49] 3GPP TS 32.422: “Subscriber and equipment trace: Trace control and Configuration Management”.
+
+- [50] 3GPP TS 25.346: “Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (Stage-2) “.
+- [51] 3GPP TS 23.246: “Multimedia Broadcast Multicast Service; Architecture and Functional Description”.
+- [52] 3GPP TS 25.319: “ Enhanced Uplink; Overall description; Stage 2”.
+- [53] Galileo OS Signal in Space ICD (OS SIS ICD), Draft 0, Galileo Joint Undertaking, May 23rd, 2006.
+In this version of the specification, Galileo Information Elements are not used.
+- [54] 3GPP TS 23.251: “Network Sharing: Architecture and functional description”.
+- [55] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006.
+- [56] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005.
+- [57] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, March 31, 2008.
+- [58] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.
+- [59] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008.
+- [60] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.
+- [61] 3GPP TS 36.401: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture Description”.
+- [62] 3GPP TS 36.104: “Base Station (BS) radio transmission and reception “.
+- [63] 3GPP TS 25.308: “High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2”.
+- [64] 3GPP TS 36.133: “Requirements for support of radio resource management”.
+- [65] 3GPP TS 23.195: “Provision of UE Specific Behaviour Information to Network Entities”.
+- [66] 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3”.
+- [67] 3GPP TS 44.108: “Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol”.
+- [68] 3GPP TS 25.422: “UTRAN Iur interface signalling transport”.
+- [69] 3GPP TS 45.005: “Technical Specification Group GSM/EDGE Radio Access Network; Radio transmission and reception”
+
+---
+
+## 3 Definitions, Symbols and Abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Elementary Procedure:** RNSAP protocol consists of Elementary Procedures (Eps). An Elementary Procedure is a unit of interaction between two RNCs. An EP consists of an initiating message and possibly a response message. Two kinds of Eps are used:
+
+- **Class 1:** Elementary Procedures with response (success or failure);
+- **Class 2:** Elementary Procedures without response.
+
+For Class 1 Eps, the types of responses can be as follows:
+
+#### Successful
+
+- - A signalling message explicitly indicates that the elementary procedure has been successfully completed with the receipt of the response.
+
+#### Unsuccessful
+
+- - A signalling message explicitly indicates that the EP failed.
+
+Class 2 Eps are considered always successful.
+
+**Prepared Reconfiguration:** A Prepared Reconfiguration exists when the Synchronised Radio Link Reconfiguration Preparation procedure has been completed successfully. The Prepared Reconfiguration does not exist anymore only after either of the procedures Synchronised Radio Link Reconfiguration Commit or Synchronised Radio Link Reconfiguration Cancellation has been completed. In particular, the Prepared Reconfiguration still exists if the object (e.g. Radio Link) concerned by the Synchronised Radio Link Reconfiguration (e.g. in the case of an HS-DSCH Setup) is removed, but the UE Context still exists.
+
+**UE Context:** The UE Context contains the necessary information for the DRNC/DBSS to communicate with a specific UE. The UE Context is created by the Radio Link Setup procedure or by the Uplink Signalling Transfer procedure when the UE makes its first access in a cell controlled by the DRNS/DBSS or by Enhanced Relocation procedure when the procedure is the first dedicated RNSAP procedure for the UE. The UE Context is deleted by the Radio Link Deletion procedure, by the Common Transport Channel Resources Release procedure, or by the Downlink Signalling Transfer procedure when neither any Radio Links nor any common transport channels are established towards the concerned UE. The UE Context is identified by the SCCP Connection for messages using connection oriented mode of the signalling bearer and the D-RNTI for messages using connectionless mode of the signalling bearer, unless specified otherwise in the procedure text.
+
+**Distant RNC Context:** The Distant RNC context is created by the first Common Measurement Initiation Procedure or Information Exchange Initiation Procedure initiated by one RNC/BSS and requested from another RNC/BSS. The Distant RNC Context is deleted after the Common Measurement Termination, the Common Measurement Failure, the Information Exchange Termination or the Information Exchange Failure procedure when there is no more Common Measurement and no more Information to be provided by the requested RNC/BSS to the requesting RNC/BSS. The Distant RNC Context is identified by a connection oriented signalling bearer (See TS 25.422 [68]) as, for common measurements and information exchange, only the connection oriented mode of the signalling bearer is used.
+
+**Signalling radio bearer 2:** The signalling radio bearer 2 is used by the UE to access a GERAN cell in order to perform RRC procedures (TS 44.118 [36]).
+
+**UE Link:** see definition in TS 25.346 [50].
+
+**URA Link:** see definition in TS 25.346 [50].
+
+**MBMS Bearer Service:** see definition in TS 23.246 [51].
+
+**MBMS session:** see definition in TS 25.346 [50].
+
+**MBMS session start:** see definition in TS 25.346 [50].
+
+**MBMS session stop:** see definition in TS 25.346 [50].
+
+**MBMS Selected Services:** see definition in TS 25.346 [50].
+
+**PUESBINE feature:** as defined in TS 23.195 [65].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|--------------------------------------|
+| A-GPS | Assisted-GPS |
+| ALCAP | Access Link Control Application Part |
+
+| | |
+|----------------|----------------------------------------------------------------------------------------------|
+| APN | Access Point Name |
+| ASN.1 | Abstract Syntax Notation One |
+| BER | Bit Error Rate |
+| BLER | Block Error Rate |
+| BSS | Base Station Subsystem |
+| CBSS | Controlling BSS |
+| CCCH | Common Control Channel |
+| CCPCH | Common Control Physical Channel |
+| CCTrCH | Coded Composite Transport Channel |
+| CFN | Connection Frame Number |
+| C-ID | Cell Identifier |
+| CM | Compressed Mode |
+| CN | Core Network |
+| CPICH | Common Pilot Channel |
+| CRNC | Controlling RNC |
+| CLTD | Closed Loop Transmit Diversity |
+| DBSS | Drift BSS |
+| C-RNTI | Cell Radio Network Temporary Identifier |
+| CS | Circuit Switched |
+| CTFC | Calculated Transport Format Combination |
+| DGANSS | Differential GANSS |
+| DGPS | Differential GPS |
+| DL | Downlink |
+| DPC | Downlink Power Control |
+| DPCCH | Dedicated Physical Control Channel |
+| DPCH | Dedicated Physical Channel |
+| DPDCH | Dedicated Physical Data Channel |
+| DRNC | Drift RNC |
+| DRNS | Drift RNS |
+| D-RNTI | Drift Radio Network Temporary Identifier |
+| DRX | Discontinuous Reception |
+| DSCH | Downlink Shared Channel |
+| E c | Energy in single Code |
+| E-AGCH | E-DCH Absolute Grant Channel |
+| E-DCH | Enhanced UL DCH |
+| E-HICH | E-DCH HARQ Acknowledgement Indicator Channel |
+| E-PUCH | Enhanced Uplink Physical Channel (TDD only) |
+| E-RNTI | E-DCH RNTI |
+| E-RUCCH | E-DCH Random Access Uplink Control Channel (TDD only) |
+| E-TFCI | E-DCH Transport Format Combination Indicator |
+| E-UCCH | E-DCH Uplink Control Channel (TDD only) |
+| E-UTRA | Evolved UTRA |
+| EDSCHPC | Enhanced Downlink Shared Channel Power Control |
+| EGNOS | European Geostationary Navigation Overlay Service |
+| EP | Elementary Procedure |
+| FACH | Forward Access Channel |
+| FDD | Frequency Division Duplex |
+| F-DPCH | Fractional DPCH |
+| FN | Frame Number |
+| FP | Frame Protocol |
+| F-TPICH | Fractional Transmitted Precoding Indicator Channel |
+| GANSS | Galileo and Additional Navigation Satellite Systems |
+| GERAN | GSM EDGE Radio Access Network |
+| GA | Geographical Area |
+| GAGAN | GPS Aided Geo Augmented Navigation |
+| GAI | Geographical Area Identifier |
+| GLONASS | GLObal'naya Navigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) |
+| GNSS | Global Navigation Satellite System |
+| GPS | Global Positioning System |
+| GRA | GERAN Registration Area |
+| GSM | Global System Mobile |
+
+| | |
+|-----------|--------------------------------------------------------------------|
+| GWCN | Gateway Core Network |
+| HSDPA | High Speed Downlink Packet Access |
+| HW | Hardware |
+| IB | Information Block |
+| ICD | Interface Control Document |
+| ID | Identity or Identifier |
+| IE | Information Element |
+| IMSI | International Mobile Subscriber Identity |
+| IP | Internet Protocol |
+| IPDL | Idle Period DownLink |
+| ISCP | Interference Signal Code Power |
+| LAC | Location Area Code |
+| LCR | Low Chip Rate (1.28 Mcps) |
+| LCS | Location Services |
+| MAC | Medium Access Control |
+| MBMS | Multimedia Broadcast Multicast Service |
+| MDT | Minimization of Drive Tests |
+| MOCN | Multi-Operator Core Network |
+| MRNC | MBMS Master RNC |
+| MS | Mobile Station |
+| MSAS | Multi-functional Satellite Augmentation System |
+| NACC | Network Assisted Cell Change |
+| NAS | Non Access Stratum |
+| No | Reference Noise |
+| NRT | Non Real Time |
+| O&M | Operation and Maintenance |
+| P(-)CCPCH | Primary CCPCH |
+| PCH | Paging Channel |
+| OTD | Observed Time Difference |
+| P(-)CPICH | Primary CPICH |
+| PCS | Personal Communication Services |
+| PDSCH | Physical Downlink Shared Channel |
+| PDU | Protocol Data Unit |
+| PhCH | Physical Channel |
+| PICH | Paging Indication Channel |
+| PLCCH | Physical Layer Common Control Channel |
+| Pos | Position or Positioning |
+| PRACH | Physical Random Access Channel |
+| PTP | Point To Point |
+| PTM | Point To Multipoint |
+| PS | Packet Switched |
+| PUESBINE | Provision of UE Specific Behaviour Information to Network Entities |
+| QE | Quality Estimate |
+| QZSS | Quasi-Zenith Satellite System |
+| RAC | Routing Area Code |
+| RACH | Random Access Channel |
+| RAN | Radio Access Network |
+| RANAP | Radio Access Network Application Part |
+| RB | Radio Bearer |
+| RL | Radio Link |
+| RLC | Radio Link Control |
+| RLS | Radio Link Set |
+| RM | Rate Matching |
+| RNC | Radio Network Controller |
+| RNS | Radio Network Subsystem |
+| RNSAP | Radio Network Subsystem Application Part |
+| RNTI | Radio Network Temporary Identifier |
+| RRC | Radio Resource Control |
+| RT | Real Time |
+| RSCP | Received Signal Code Power |
+| SBAS | Satellite Based Augmentation System |
+
+| | |
+|-----------|----------------------------------------------|
+| SBSS | Serving BSS |
+| Rx | Receive or Reception |
+| Sat | Satellite |
+| SCCP | Signalling Connection Control Part |
+| S(-)CCPCH | Secondary CCPCH |
+| SCH | Synchronisation Channel |
+| SCTD | Space Code Transmit Diversity |
+| S-DPCCH | Secondary Dedicated Physical Control Channel |
+| SDU | Service Data Unit |
+| SF | System Frame |
+| SFN | System Frame Number |
+| SHCCH | Shared Control Channel |
+| SIR | Signal-to-Interference Ratio |
+| SNA | Shared Network Area |
+| SRB2 | Signalling radio bearer 2 |
+| SRNC | Serving RNC |
+| SRNS | Serving RNS |
+| S-RNTI | Serving Radio Network Temporary Identifier |
+| STTD | Space Time Transmit Diversity |
+| TDD | Time Division Duplex |
+| TF | Transport Format |
+| TFCI | Transport Format Combination Indicator |
+| TFCS | Transport Format Combination Set |
+| TFS | Transport Format Set |
+| TGCFN | Transmission Gap Connection Frame Number |
+| TMGI | Temporary Mobile Group Identity |
+| ToAWE | Time of Arrival Window Endpoint |
+| ToAWS | Time of Arrival Window Startpoint |
+| TPC | Transmit Power Control |
+| TrCH | Transport Channel |
+| TS | Time Slot |
+| TSG | Technical Specification Group |
+| TSTD | Time Switched Transmit Diversity |
+| TTI | Transmission Time Interval |
+| TX | Transmit or Transmission |
+| UARFCN | UTRA Absolute Radio Frequency Channel Number |
+| UDP | User Datagram Protocol |
+| UC-ID | UTRAN Cell Identifier |
+| UE | User Equipment |
+| UL | Uplink |
+| UMTS | Universal Mobile Telecommunications System |
+| URA | UTRAN Registration Area |
+| U-RNTI | UTRAN Radio Network Temporary Identifier |
+| USCH | Uplink Shared Channel |
+| UTC | Universal Coordinated Time |
+| UTRA | Universal Terrestrial Radio Access |
+| UTRAN | Universal Terrestrial Radio Access Network |
+| WAAS | Wide Area Augmentation System |
+
+---
+
+## 4 General
+
+### 4.1 Procedure Specification Principles
+
+The principle for specifying the procedure logic is to specify the functional behaviour of the DRNC/CRNC exactly and completely. The SRNC functional behaviour is left unspecified. The Physical Channel Reconfiguration procedure, [TDD – the UE Measurement Initiation, the UE Measurement Reporting, UE Measurement Termination, UE Measurement Failure,] and the Reset procedure are an exception from this principle.
+
+The following specification principles have been applied for the procedure text in subclause 8:
+
+- The procedure text discriminates between:
+ - 1) Functionality which “shall” be executed
+ - The procedure text indicates that the receiving node “shall” perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
+- 04.%2% Functionality which “shall, if supported” be executed
+ - The procedure text indicates that the receiving node “shall, if supported,” perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
+
+Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements for including *Criticality Diagnostics* IE, see section 10. For examples on how to use the *Criticality Diagnostics* IE, see Annex C.
+
+## 4.2 Forwards and Backwards Compatibility
+
+The forwards and backwards compatibility of the protocol is assured by a mechanism in which all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.
+
+## 4.3 Source Signalling Address Handling
+
+The sender of an RNSAP messages shall include the Source Signalling Address, i.e. the Signalling Address of the sending node.
+
+## 4.4 Specification Notations
+
+For the purposes of the present document, the following notations apply:
+
+- | | |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [FDD] | This tagging of a word indicates that the word preceding the tag “[FDD]” applies only to FDD. This tagging of a heading indicates that the heading preceding the tag “[FDD]” and the section following the heading applies only to FDD. |
+| [TDD] | This tagging of a word indicates that the word preceding the tag “[TDD]” applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “[TDD]” and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. |
+| [3.84Mcps TDD] | This tagging of a word indicates that the word preceding the tag “[3.84Mcps TDD]” applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “[3.84Mcps TDD]” and the section following the heading applies only to 3.84Mcps TDD. |
+| [1.28Mcps TDD] | This tagging of a word indicates that the word preceding the tag “[1.28Mcps TDD]” applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “[1.28Mcps TDD]” and the section following the heading applies only to 1.28Mcps TDD. |
+| [7.68Mcps TDD] | This tagging of a word indicates that the word preceding the tag “[7.68Mcps TDD]” applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “[7.68Mcps TDD]” and the section following the heading applies only to 7.68Mcps TDD. |
+| [FDD - ...] | This tagging indicates that the enclosed text following the “[FDD – “ applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. |
+
+| | |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [TDD - ...] | This tagging indicates that the enclosed text following the “[TDD – “ applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. |
+| [3.84Mcps TDD - ...] | This tagging indicates that the enclosed text following the “[3.84Mcps TDD – “ applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. |
+| [1.28Mcps TDD - ...] | This tagging indicates that the enclosed text following the “[1.28Mcps TDD – “ applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. |
+| [7.68Mcps TDD - ...] | This tagging indicates that the enclosed text following the “[7.68Mcps TDD – “ applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. |
+| Procedure | When referring to an elementary 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 Link Setup procedure. |
+| 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. |
+| IE | When referring to an information element (IE) in the specification, the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation “IE”, e.g. Transport Format Set IE . |
+| Value of an IE | When referring to the value of an information element (IE) in the specification, the “Value” is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. “Abstract Syntax Error (Reject)”. |
+
+---
+
+## 5 RNSAP Services
+
+### 5.1 RNSAP Procedure Modules
+
+The Iur interface RNSAP procedures are divided into five modules as follows:
+
+1. RNSAP Basic Mobility Procedures;
+2. RNSAP Dedicated Procedures;
+3. RNSAP Common Transport Channel Procedures;
+4. RNSAP Global Procedures;
+5. RNSAP MBMS Procedures.
+
+The Basic Mobility Procedures module contains procedures used to handle the mobility within UTRAN, within GERAN and between UTRAN and GERAN.
+
+The Dedicated Procedures module contains procedures that are used to handle DCHs, [FDD – F-DPCH,] [TDD – DSCHs, USCHs], HS-DSCH and E-DCH between two RNSs. If procedures from this module are not used in a specific Iur, then the usage of DCH, [FDD – F-DPCH,] [TDD – DSCH, USCH,] HS-DSCH and E-DCH traffic between corresponding RNSs is not possible.
+
+The Common Transport Channel Procedures module contains procedures that are used to control common transport channel data streams (excluding the DSCH, HS-DSCH and USCH) over Iur interface.
+
+The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module are in contrast to the above modules involving two peer CRNCs/CBSSs.
+
+The MBMS Procedures module contains procedures that are specific to MBMS and used for cases that cannot be handled by other modules.
+
+## 5.2 Parallel Transactions
+
+Unless explicitly indicated in the procedure specification, at any instance in time one protocol peer shall have a maximum of one ongoing RNSAP Dedicated procedure related to a certain UE.
+
+---
+
+## 6 Services Expected from Signalling Transport
+
+The signalling transport shall provide two different service modes for the RNSAP.
+
+1. Connection oriented data transfer service. This service is supported by a signalling connection between two RNCs. It shall be possible to dynamically establish and release signalling connections based on the need. Each active UE shall have its own signalling connection. The signalling connection shall provide in sequence delivery of RNSAP messages. RNSAP shall be notified if the signalling connection breaks.
+2. Connectionless data transfer service. RNSAP shall be notified in case a RNSAP message did not reach the intended peer RNSAP entity.
+
+---
+
+## 7 Functions of RNSAP
+
+The RNSAP protocol provides the following functions:
+
+- Radio Link Management. This function allows the SRNC to manage radio links using dedicated resources in a DRNS;
+- Physical Channel Reconfiguration. This function allows the DRNC to reallocate the physical channel resources for a Radio Link;
+- Radio Link Supervision. This function allows the DRNC to report failures and restorations of a Radio Link;
+- Compressed Mode Control [FDD]. This function allows the SRNC to control the usage of compressed mode within a DRNS;
+- Measurements on Dedicated Resources. This function allows the SRNC to initiate measurements on dedicated resources in the DRNS. The function also allows the DRNC to report the result of the measurements;
+- DL Power Drifting Correction [FDD]. This function allows the SRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links;
+- DCH Rate Control. This function allows the DRNC to limit the rate of each DCH configured for the Radio Link(s) of a UE in order to avoid congestion situations in a cell;
+- CCCH Signalling Transfer. This function allows the SRNC and DRNC to pass information between the UE and the SRNC on a CCCH controlled by the DRNS;
+- GERAN Signalling Transfer. This function allows the SBSS and DBSS, the SRNC and DBSS or the SBSS and DRNC to pass information between the UE/MS and the SRNC/SBSS on an SRB2/CCCH controlled by the DBSS/DRNC;
+- Paging. This function allows the SRNC/SBSS to page a UE in a URA/GRA or a cell in the DRNS;
+- Common Transport Channel Resources Management. This function allows the SRNC to utilise Common Transport Channel Resources within the DRNS;
+- Relocation Execution. This function allows the SRNC/SBSS to finalise a Relocation previously prepared via other interfaces;
+
+- Reporting of General Error Situations. This function allows reporting of general error situations, for which function specific error messages have not been defined;
+- DL Power Timeslot Correction [TDD]. This function enables the DRNS to apply an individual offset to the transmission power in each timeslot according to the downlink interference level at the UE;
+- Measurements on Common Resources. This function allows an RNC/BSS to request from another RNC/BSS to initiate measurements on Common Resources. The function also allows the requested RNC/BSS to report the result of the measurements;
+- Information Exchange. This function allows an RNC to request from another RNC the transfer of information. The function also allows the requested RNC to report the requested information;
+- Resetting the Iur. This function is used to completely or partly reset the Iur interface;
+- UE Measurement Forwarding[TDD]. This function allows the DRNC to request and receive UE measurements from the SRNC;
+- Tracing. This function allows the SRNC to activate or deactivate trace in a DRNC;.
+- MBMS UE Linking/De-linking. This function allows the SRNC to provide/update/remove the UE Link to/in/from the DRNC;
+- MBMS URA Linking/De-linking. This function allows the SRNC to provide/update/remove the URA Link to/in/from the DRNC;
+- MBMS Channel Type Indication. This function allows the DRNC to indicate to the SRNC the selected channel type for an MBMS bearer service within certain cells in the DRNS;
+- MBMS Preferred Frequency Layer Indication. This function allows the DRNC to indicate to the SRNC the preferred frequency layer for an MBMS bearer service within certain cells in the DRNS;
+- MBMS MCCH Information Control. This function allows an MRNC to distribute the MCCH Information to CRNC within the MBSFN cluster;
+- Direct Information Transfer. This function allows an RNC to transfer information to another RNC;
+- Relocating serving RNC. This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another;
+- Exchanging information about the secondary UL frequency. This function allows the SRNC to transfer information about the secondary UL frequency to the DRNS and the DRNS to transfer information about the secondary UL frequency to SRNC in Dual-Cell E-DCH operation;
+- Radio Resource Reserve Handover [1.28Mcps TDD]. This function allows the SRNC to request allocation of radio resources in the target BSS prior to the HANDOVER REQUEST message is received from the Core Network;
+- Automatic Neighbour Relation Management: This function enables RNC to distribute ANR reports, configure ANR neighbour relations, and control the ANR report distribution.
+
+The mapping between the above functions and RNSAP elementary procedures is shown in the Table 1.
+
+**Table 1: Mapping between functions and RNSAP elementary procedures**
+
+| Function | Elementary Procedure(s) |
+|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Radio Link Management | a) Radio Link Setup
b) Radio Link Addition
c) Radio Link Deletion
d) Unsynchronised Radio Link Reconfiguration
e) Synchronised Radio Link Reconfiguration Preparation
f) Synchronised Radio Link Reconfiguration Commit
g) Synchronised Radio Link Reconfiguration Cancellation
h) Radio Link Pre-emption
i) Radio Link Activation
j) Radio Link Parameter Update |
+| Physical Channel Reconfiguration | Physical Channel Reconfiguration |
+| Radio Link Supervision | a) Radio Link Failure
b) Radio Link Restoration |
+| Compressed Mode Control [FDD] | a) Radio Link Setup
b) Radio Link Addition
c) Compressed Mode Command
d) Unsynchronised Radio Link Reconfiguration
e) Synchronised Radio Link Reconfiguration Preparation
f) Synchronised Radio Link Reconfiguration Commit
g) Synchronised Radio Link Reconfiguration Cancellation |
+| Measurements on Dedicated Resources | a) Dedicated Measurement Initiation
b) Dedicated Measurement Reporting
c) Dedicated Measurement Termination
d) Dedicated Measurement Failure |
+| DL Power Drifting Correction [FDD] | Downlink Power Control |
+| DCH Rate Control | a) Radio Link Setup
b) Radio Link Addition
c) Unsynchronised Radio Link Reconfiguration
d) Synchronised Radio Link Reconfiguration Preparation
e) Radio Link Congestion |
+| CCCH Signalling Transfer | a) Uplink Signalling Transfer
b) Downlink Signalling Transfer |
+| GERAN Signalling Transfer | a) GERAN Uplink Signalling Transfer
b) Downlink Signalling Transfer |
+| Paging | Paging |
+| Common Transport Channel Resources Management | a) Common Transport Channel Resources Initiation
b) Common Transport Channel Resources Release |
+| Relocation Execution | Relocation Commit |
+| Reporting of General Error Situations | Error Indication |
+| Measurements on Common Resources | a) Common Measurement Initiation
b) Common Measurement Reporting
c) Common Measurement Termination
d) Common Measurement Failure |
+| Information Exchange | a) Information Exchange Initiation
b) Information Reporting
c) Information Exchange Termination
d) Information Exchange Failure |
+| DL Power Timeslot Correction [TDD] | Downlink Power Timeslot Control |
+| Reset | Reset |
+| UE Measurement Forwarding[TDD] | a) UE Measurement Initiation
b) UE Measurement Reporting
c) UE Measurement Termination
d) UE Measurement Failure |
+| Trace | a) Iur Invoke Trace
b) Iur Deactivate Trace |
+| MBMS UE Linking/De-linking | a) Common Transport Channel Resources Initiation |
+
+| Function | Elementary Procedure(s) |
+|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | b) Radio Link Setup
c) Downlink Signalling Transfer
d) MBMS Attach
e) MBMS Detach |
+| MBMS Channel Type Indication | a) Direct Information Transfer
b) Uplink Signalling Transfer
c) Radio Link Setup
d) Radio Link Addition
e) Common Transport Channel Resources Initiation |
+| MBMS Preferred Frequency Layer Indication | a) Direct Information Transfer
b) Radio Link Setup
d) Radio Link Addition |
+| MBMS URA Linking/De-linking | a) Downlink Signalling Transfer
b) MBMS Attach
c) MBMS Detach |
+| MBMS MCCH Information Control | a) MBSFN MCCH Information |
+| Direct Information Transfer | a) Direct Information Transfer |
+| Relocating serving RNC | a) Enhanced Relocation
b) Enhanced Relocation Cancel
c) Enhanced Relocation Signalling Transfer
d) Enhanced Relocation Release |
+| Exchanging information about the secondary UL frequency [FDD] | a) Secondary UL Frequency Reporting
b) Secondary UL Frequency Update |
+| Radio Resource Reserve Handover [1.28Mcps TDD] | a) Enhanced Relocation Resource Allocation
b) Enhanced Relocation Resource Release |
+| Automatic Neighbour Relation Management | a) Direct Information Transfer
b) Information Exchange Initiation
c) Information Reporting
d) Information Exchange Termination
e) Information Exchange Failure
f) Information Transfer Control |
+
+## 7.1 RNSAP functions and elementary procedures for Iur-g.
+
+The functions and RNSAP elementary procedures, which are applicable on the Iur-g interface are shown in the Table 1A.
+
+**Table 1A: RNSAP elementary procedures applicable on the Iur-g interface**
+
+| Function | Elementary Procedure(s) |
+|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| GERAN Signalling Transfer | a) GERAN Uplink Signalling Transfer
b) Downlink Signalling Transfer |
+| Paging | Paging |
+| Relocation Execution | Relocation Commit |
+| Reporting of General Error Situations | Error Indication |
+| Measurements on Common Resources | a) Common Measurement Initiation
b) Common Measurement Reporting
c) Common Measurement Termination
d) Common Measurement Failure |
+| Information Exchange | a) Information Exchange Initiation
b) Information Reporting
c) Information Exchange Termination
d) Information Exchange Failure |
+| Radio Resource Reserve Handover [1.28Mcps TDD] | a) Enhanced Relocation Resource Allocation
b) Enhanced Relocation Resource Release |
+
+NOTE: In the connection with the functions related to the GERAN and UTRAN, the term RNC shall refer to RNC/BSS.
+
+## 8 RNSAP Procedures
+
+### 8.1 Elementary Procedures
+
+In the following tables, all Eps are divided into Class 1 and Class 2 Eps.
+
+**Table 2: Class 1 Elementary Procedures**
+
+| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome |
+|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|--------------------------------------------|
+| | | Response message | Response message |
+| Radio Link Setup | RADIO LINK SETUP REQUEST | RADIO LINK SETUP RESPONSE | RADIO LINK SETUP FAILURE |
+| Radio Link Addition | RADIO LINK ADDITION REQUEST | RADIO LINK ADDITION RESPONSE | RADIO LINK ADDITION FAILURE |
+| Radio Link Deletion | RADIO LINK DELETION REQUEST | RADIO LINK DELETION RESPONSE | |
+| Synchronised Radio Link Reconfiguration Preparation | RADIO LINK RECONFIGURATION PREPARE | RADIO LINK RECONFIGURATION READY | RADIO LINK RECONFIGURATION FAILURE |
+| Unsynchronised Radio Link Reconfiguration | RADIO LINK RECONFIGURATION REQUEST | RADIO LINK RECONFIGURATION RESPONSE | RADIO LINK RECONFIGURATION FAILURE |
+| Physical Channel Reconfiguration | PHYSICAL CHANNEL RECONFIGURATION REQUEST | PHYSICAL CHANNEL RECONFIGURATION COMMAND | PHYSICAL CHANNEL RECONFIGURATION FAILURE |
+| Dedicated Measurement Initiation | DEDICATED MEASUREMENT INITIATION REQUEST | DEDICATED MEASUREMENT INITIATION RESPONSE | DEDICATED MEASUREMENT INITIATION FAILURE |
+| Common Transport Channel Resources Initialisation | COMMON TRANSPORT CHANNEL RESOURCES REQUEST | COMMON TRANSPORT CHANNEL RESOURCES RESPONSE | COMMON TRANSPORT CHANNEL RESOURCES FAILURE |
+| Common Measurement Initiation | COMMON MEASUREMENT INITIATION REQUEST | COMMON MEASUREMENT INITIATION RESPONSE | COMMON MEASUREMENT INITIATION FAILURE |
+| Information Exchange Initiation | INFORMATION EXCHANGE INITIATION REQUEST | INFORMATION EXCHANGE INITIATION RESPONSE | INFORMATION EXCHANGE INITIATION FAILURE |
+| Reset | RESET REQUEST | RESET RESPONSE | |
+| UE Measurement Initiation[TDD] | UE MEASUREMENT INITIATION REQUEST | UE MEASUREMENT INITIATION RESPONSE | UE MEASUREMENT INITIATION FAILURE |
+| Enhanced Relocation | ENHANCED RELOCATION REQUEST | ENHANCED RELOCATION RESPONSE | ENHANCED RELOCATION FAILURE |
+| Enhanced Relocation Resource Allocation[1.28Mcps TDD] | ENHANCED RELOCATION RESOURCE REQUEST | ENHANCED RELOCATION RESOURCE RESPONSE | ENHANCED RELOCATION RESOURCE FAILURE |
+| Enhanced Relocation Resource Release[1.28Mcps TDD] | ENHANCED RELOCATION RESOURCE RELEASE COMMAND | ENHANCED RELOCATION RESOURCE RELEASE COMPLETE | |
+
+**Table 3: Class 2 Elementary Procedures**
+
+| Elementary Procedure | Initiating Message |
+|------------------------------------------------------|----------------------------------------------------|
+| Uplink Signalling Transfer | UPLINK SIGNALLING TRANSFER INDICATION |
+| GERAN Uplink Signalling Transfer | GERAN UPLINK SIGNALLING TRANSFER INDICATION |
+| Downlink Signalling Transfer | DOWNLINK SIGNALLING TRANSFER REQUEST |
+| Relocation Commit | RELOCATION COMMIT |
+| Paging | PAGING REQUEST |
+| Synchronised Radio Link Reconfiguration Commit | RADIO LINK RECONFIGURATION COMMIT |
+| Synchronised Radio Link Reconfiguration Cancellation | RADIO LINK RECONFIGURATION CANCEL |
+| Radio Link Failure | RADIO LINK FAILURE INDICATION |
+| Radio Link Restoration | RADIO LINK RESTORE INDICATION |
+| Dedicated Measurement Reporting | DEDICATED MEASUREMENT REPORT |
+| Dedicated Measurement Termination | DEDICATED MEASUREMENT TERMINATION REQUEST |
+| Dedicated Measurement Failure | DEDICATED MEASUREMENT FAILURE INDICATION |
+| Downlink Power Control [FDD] | DL POWER CONTROL REQUEST |
+| Compressed Mode Command [FDD] | COMPRESSED MODE COMMAND |
+| Common Transport Channel Resources Release | COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST |
+| Error Indication | ERROR INDICATION |
+| Downlink Power Timeslot Control [TDD] | DL POWER TIMESLOT CONTROL REQUEST |
+| Radio Link Pre-emption | RADIO LINK PREEMPTION REQUIRED INDICATION |
+| Radio Link Congestion | RADIO LINK CONGESTION INDICATION |
+| Common Measurement Reporting | COMMON MEASUREMENT REPORT |
+| Common Measurement Termination | COMMON MEASUREMENT TERMINATION REQUEST |
+| Common Measurement Failure | COMMON MEASUREMENT FAILURE INDICATION |
+| Information Reporting | INFORMATION REPORT |
+| Information Exchange Termination | INFORMATION EXCHANGE TERMINATION REQUEST |
+| Information Exchange Failure | INFORMATION EXCHANGE FAILURE INDICATION |
+| MBMS Attach | MBMS ATTACH COMMAND |
+| MBMS Detach | MBMS DETACH COMMAND |
+| Radio Link Parameter Update | RADIO LINK PARAMETER UPDATE INDICATION |
+| UE Measurement Reporting [TDD] | UE MEASUREMENT REPORT |
+| UE Measurement Termination [TDD] | UE MEASUREMENT TERMINATION REQUEST |
+| UE Measurement Failure [TDD] | UE MEASUREMENT FAILURE INDICATION |
+| Iur Invoke Trace | IUR INVOKE TRACE |
+| Iur Deactivate Trace | IUR DEACTIVATE TRACE |
+| Direct Information Transfer | DIRECT INFORMATION TRANSFER |
+| Enhanced Relocation Cancel | ENHANCED RELOCATION CANCEL |
+| Enhanced Relocation Signalling Transfer | ENHANCD RELOCATION SIGNALLING TRANSFER |
+| Enhanced Relocation Release | ENHANCD RELOCATION RELEASE |
+| MBSFN MCCH Information | MBSFN MCCH INFORMATION |
+| Secondary UL Frequency Reporting [FDD] | SECONDARY UL FREQUENCY REPORT |
+| Secondary UL Frequency Update[FDD] | SECONDARY UL FREQUENCY UPDATE INDICATION |
+| Information Transfer Control | INFORMATION TRANSFER CONTROL REQUEST |
+
+## 8.2 Basic Mobility Procedures
+
+### 8.2.1 Uplink Signalling Transfer
+
+#### 8.2.1.1 General
+
+The procedure is used by the DRNC to forward a Uu message received on the CCCH to the SRNC.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+#### 8.2.1.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant UE
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: Uu message received from UE containing S-RNTI and SRNC ID as addressing information
+ DRNC->>SRNC: UPLINK SIGNALLING TRANSFER INDICATION
+
+```
+
+Sequence diagram illustrating the Uplink Signalling Transfer procedure, Successful Operation. The diagram shows two entities: DRNC and SRNC. The DRNC receives a Uu message from the UE containing S-RNTI and SRNC ID as addressing information. The DRNC then sends an UPLINK SIGNALLING TRANSFER INDICATION message to the SRNC.
+
+**Figure 1: Uplink Signalling Transfer procedure, Successful Operation**
+
+When the DRNC receives an Uu message on the CCCH in which the UE addressing information is U-RNTI, i.e. S-RNTI and SRNC-ID, DRNC shall send the UPLINK SIGNALLING TRANSFER INDICATION message to the SRNC identified by the SRNC-ID received from the UE.
+
+If at least one URA Identity is being broadcast in the cell where the Uu message was received (the accessed cell), the DRNC shall include a URA Identity for this cell in the *URA ID* IE, the *Multiple URAs Indicator* IE indicating whether or not multiple URA Identities are being broadcast in the accessed cell, and the RNC Identity of all other RNCs that are having at least one cell within the URA where the Uu message was received in the *URA Information* IE in the UPLINK SIGNALLING TRANSFER INDICATION message.
+
+The DRNC shall include in the message the C-RNTI that it allocates to identify the UE in the radio interface in the accessed cell. If there is no valid C-RNTI for the UE in the accessed cell, the DRNS shall allocate a new C-RNTI for the UE [FDD – and in case Enhanced FACH operation is activated in the accessed cell the DRNC shall allocate the HS-DSCH-RNTI to the UE and shall include the *HS-DSCH-RNTI* IE in the message. And in case Common E-DCH operation is activated in the accessed cell the DRNC shall include the E-RNTI received from Node B and shall include the *E-RNTI* IE in the message]. [1.28Mcps TDD – and in case Enhanced FACH operation is activated in the accessed cell the DRNC shall allocate the HS-DSCH-RNTI to the UE and shall include the *HS-DSCH-RNTI* IE in the message and the DRNC shall include the E-RNTI received from Node B and shall include the *E-RNTI* IE in the message]. If the DRNS allocates a new C-RNTI it shall also release any C-RNTI previously allocated for the UE.
+
+If the DRNS has any RACH and/or FACH resources allocated for the UE identified by the U-RNTI in another cell than the accessed cell in which the Mac SDU sizes, flow control settings (including credits) and/or transport bearer are different from those in the old cell, then the DRNS shall not include the *Common Transport Channel Resources Initialisation Not Required* IE in the UPLINK SIGNALLING TRANSFER INDICATION message. In addition the DRNS shall release these RACH and/or FACH resources in old cell.
+
+If the DRNS has any RACH and/or FACH resources allocated for the UE identified by the U-RNTI in another cell than the accessed cell in which the Mac SDU sizes, flow control settings (including credits) and transport bearer are the same as in the old cell, there is no need for Common Transport Channel Resources Initialisation to be initiated. In that case, DRNC may include the *Common Transport Channel Resources Initialisation Not Required* IE in the UPLINK SIGNALLING TRANSFER INDICATION message. In addition, the DRNS shall move these RACH and/or FACH resources to the new cell. If no Common Transfer Channel Resources Initialisation procedure is executed, the currently applicable Mac SDU sizes, flow control settings (including credits) and transport bearer shall continue to be used while the UE is in the new cell.
+
+If no context exists for this UE in the DRNC, the DRNC shall create a UE Context for this UE, allocate a D-RNTI for the UE Context, and include the *D-RNTI* IE and the identifiers for the CN CS Domain and CN PS Domain that the DRNC is connected to in the UPLINK SIGNALLING TRANSFER INDICATION message. These CN Domain Identifiers shall be based on the LAC and RAC respectively of the cell where the message was received from the UE.
+
+Depending on local configuration in the DRNS, it may include the geographical co-ordinates of the cell, represented either by the *Cell GAI* IE or by the *Cell GA Additional Shapes* IE, in which the Uu message was received in the UPLINK SIGNALLING TRANSFER INDICATION message. If the DRNC includes the *Cell GA Additional Shapes* IE in the UPLINK SIGNALLING TRANSFER INDICATION message, it shall also include the *Cell GAI* IE.
+
+[FDD – The DRNC shall include the *DPC Mode Change Support Indicator* IE in the UPLINK SIGNALLING TRANSFER INDICATION message if the accessed cell supports DPC mode change.]
+
+The DRNC shall include [FDD – the *Cell Capability Container FDD* IE] [3.84Mcps TDD – the *Cell Capability Container TDD* IE] [1.28Mcps TDD – the *Cell Capability Container TDD LCR* IE] [7.68Mcps TDD – the *Cell Capability Container 7.68Mcps TDD* IE] [FDD – and/or the *Cell Capability Container Extension FDD* IE] in the UPLINK SIGNALLING TRANSFER INDICATION message if the accessed cell supports any functionalities listed in [FDD – 9.2.2.D] [3.84Mcps TDD – 9.2.3.1a] [1.28Mcps TDD – 9.2.3.1b] [7.68Mcps TDD – 9.2.3.31] [FDD – 9.2.2.123].
+
+[FDD – If the cell is multicell adjacent and/or non-adjacent carrier operation capable and if the cell can be the serving HS-DSCH then the possible cells to serve multicell adjacent and/or non-adjacent carrier operation (same or adjacent sector in the same Node B) that can act as secondary serving HS-DSCH shall be listed in the *Secondary Serving Cell List* IE. For each cell in the *Secondary Serving Cell List* IE that is Multi Cell E-DCH capable, indicated in the *Cell Capability Container Extension FDD* IE by the Multi Cell E-DCH Support Indicator bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the accessed cell as the corresponding cell of the primary uplink frequency, the DRNS shall, if supported, include the *Multicell E-DCH Restriction* IE set to "TRUE". If the *Secondary Serving Cell List* IE is not present, the multicell (adjacent or non-adjacent carrier operation) capable cell can only serve as a secondary serving HS-DSCH cell in single band operation.]
+
+[FDD – If the cell is dual band capable and if the cell can be the serving HS-DSCH then the possible cells to serve dual band carrier operation (same sector) that can act as secondary serving HS-DSCH shall be listed in the *Dual Band Secondary Serving Cell List* IE. If the *Dual Band Secondary Serving Cell List* IE is not present, the dual band capable cell can only serve as a secondary serving HS-DSCH cell in dual band operation.]
+
+If MOCN or GWCN network sharing configuration is used then the DRNC shall include the broadcasted PLMN identities of the concerned cell in the *Multiple PLMN List* IE in the UPLINK SIGNALLING TRANSFER INDICATION message.
+
+If available, the DRNC shall include the *SNA Information* IE for the concerned cell.
+
+When receiving the *SNA Information* IE, the SRNC should use it to restrict cell access based on SNA information. See also TS 25.401 [40] for a broader description of the SNA access control.
+
+[FDD – The DRNC shall include the *Cell Portion ID* IE in the UPLINK SIGNALLING TRANSFER INDICATION message if available.]
+
+[1.28 Mcps TDD – The DRNC shall include the *Cell Portion LCR ID* IE in the UPLINK SIGNALLING TRANSFER INDICATION message if available.]
+
+[FDD – If the propagation delay value exceeds the range of the *Propagation Delay* IE then the DRNC shall if supported include the *Extended Propagation Delay* IE and set the *Propagation Delay* IE to its maximum value.]
+
+If the *D-RNTI* IE is not to be included in the UPLINK SIGNALLING TRANSFER INDICATION message and the UE Link is currently stored in the UE Context in the DRNC, the DRNC shall assume that the UE changes the cell under which it camps in the DRNS (see TS 25.346 [50], section 5.1.6 on intra-DRNC cell change). In this case, if an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in the cell identified by the *UC-ID* IE, the DRNC shall include in the *Active MBMS Bearer Service List* IE the *Transmission Mode* IE for each of these active MBMS bearer services. Or else, if the DRNC receives a Uu message on the CCCH in which the short identities for MBMS Selected Services are included, and the Uu message requests for MBMS PtP radio bearer establishment, the DRNC shall determine which TMGIs correspond with the short identities and shall include in the *Active MBMS Bearer Service List* IE the *TMGI* IE together with the *Transmission Mode* IE for each of these MBMS Selected Services.
+
+If the CCCH message contains *Measurement results for monitored cells on non-used frequencies* IE in *Measured Result on RACH* IE, the DRNC may include in the UPLINK SIGNALLING TRANSFER INDICATION message the *Inter-frequency Cell List* IE for each of the measured inter-frequency cells. The order of cells in *Measurement results for monitored cells on non-used frequencies* IE in the CCCH message shall be preserved in *Inter-frequency Cell List* IE. If the *UL UARFCN* IE in the *Inter-frequency Cell List* IE is not present, the default duplex distance defined for the operating frequency band shall be used in the SRNC (see TS 25.101 [43]).
+
+[3.84 Mcps TDD – the DRNC shall include the *Rx Timing Deviation* IE unless the cell to which the CCCH message was sent is configured to use the extended timing advance in which case *Rx Timing Deviation 3.84Mcps Extended* IE shall be included.]
+
+[7.68 Mcps TDD – the DRNC shall include the *Rx Timing Deviation 7.68Mcps* IE.]
+
+### 8.2.1.3 Abnormal Conditions
+
+-
+
+## 8.2.1A GERAN Uplink Signalling Transfer
+
+### 8.2.1A.1 General
+
+The procedure is used by the DBSS to forward an Um message received on the SRB2 to the SBSS/SRNC. The procedure is also used by the DRNC to forward a Uu message received on the CCCH to the SBSS.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+### 8.2.1A.2 Successful Operation
+
+
+
+Sequence diagram illustrating the GERAN Uplink Signalling Transfer procedure for successful operation. The diagram shows two vertical lifelines: DBSS/DRNC on the left and SBSS/SRNC on the right. A dashed line from the DBSS/DRNC lifeline points to a box containing the text 'Um/Uu message received from UE/MS containing S-RNTI and RNC/BSC ID as addressing information'. From the bottom of this box, a solid horizontal arrow labeled 'GERAN UPLINK SIGNALLING TRANSFER' points to the SBSS/SRNC lifeline.
+
+**Figure 1A: GERAN Uplink Signalling Transfer procedure, Successful Operation**
+
+When the DBSS receives an Um message on the SRB2 in which the MS addressing information is G-RNTI, i.e. S-RNTI and BSC-ID, DBSS shall send the GERAN UPLINK SIGNALLING TRANSFER INDICATION message to the SBSS/SRNC identified by the BSC-ID received from the MS.
+
+Alternatively, when the DRNC receives an Uu message on the CCCH in which the UE addressing information is U-RNTI, i.e. S-RNTI and SRNC-ID, and in which the SRNC-ID points to a GERAN BSS, the DRNC shall send the GERAN UPLINK SIGNALLING TRANSFER INDICATION message to the SBSS identified by SRNC-ID received from the UE.
+
+If at least one GRA/URA Identity is being broadcast in the cell where the Um/Uu message was received (the accessed cell), the DBSS/DRNC shall include a GRA/URA Identity for this cell in the *URA ID* IE, the *Multiple URAs Indicator* IE indicating whether or not multiple GRA/URA Identities are being broadcast in the accessed cell, and the RNC/BSS Identity of all other RNC/BSSs that are having at least one cell within the GRA/URA where the Um/Uu message was received in the *URA Information* IE in the GERAN UPLINK SIGNALLING TRANSFER INDICATION message.
+
+If no context exists for this UE/MS in the DBSS/DRNC, the DBSS/DRNC shall create a UE Context for this UE/MS, allocate a D-RNTI for the UE Context, and include the *D-RNTI* IE and the identifiers for the CN CS Domain and CN PS Domain that the DBSS/DRNC is connected to in the GERAN UPLINK SIGNALLING TRANSFER INDICATION message. These CN Domain Identifiers shall be based on the LAC and RAC respectively of the cell where the message was received from the UE/MS.
+
+### 8.2.1A.3 Abnormal Conditions
+
+-
+
+## 8.2.2 Downlink Signalling Transfer
+
+### 8.2.2.1 General
+
+The procedure is used by the SRNC to request to the DRNC the transfer of a Uu message on the CCCH in a cell. When used, the procedure is in response to a received Uplink Signalling Transfer procedure.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+#### 8.2.2.1.1 Downlink Signalling Transfer for Iur-g
+
+The procedure is used by the SRNC/SBSS to request to the DBSS the transfer of an Um message on the SRB2 in a cell.
+
+The procedure is used by the SBSS to request to the DRNC the transfer of a Uu message on the CCCH in a cell.
+
+### 8.2.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of SRNC: DOWNLINK SIGNALLING TRANSFER REQUEST
+ SRNC->>DRNC: DOWNLINK SIGNALLING TRANSFER REQUEST
+
+```
+
+Sequence diagram showing the Downlink Signalling Transfer procedure. A message labeled 'DOWNLINK SIGNALLING TRANSFER REQUEST' is sent from the SRNC to the DRNC.
+
+**Figure 2: Downlink Signalling Transfer procedure, Successful Operation**
+
+The procedure consists of the DOWNLINK SIGNALLING TRANSFER REQUEST message sent by the SRNC to the DRNC.
+
+The message contains the Cell Identifier (C-ID) contained in the received UPLINK SIGNALLING TRANSFER INDICATION message and the D-RNTI.
+
+Upon receipt of the message, the DRNC shall send the L3 Information on the CCCH in the cell indicated by the *C-ID* IE to the UE identified by the *D-RNTI* IE.
+
+If the *D-RNTI Release Indication* IE is set to “Release D-RNTT” and the DRNS has no dedicated resources (DCH, [TDD – USCH and/or DSCH]) allocated for the UE, the DRNS shall release the D-RNTI, the UE Context and any RACH and FACH resources and any C-RNTI allocated to the UE Context upon receipt of the DOWNLINK SIGNALLING TRANSFER REQUEST message. If a UE Link is currently stored in the UE Context, the DRNC shall perform UE De-linking as specified in TS 25.346 [50], section 5.1.6.
+
+If the *D-RNTI Release Indication* IE is set to “Release D-RNTT” and the DRNS has dedicated resources allocated for the UE, the DRNS shall only release any RACH and FACH resources and any C-RNTI allocated to the UE Context upon receipt of the DOWNLINK SIGNALLING TRANSFER REQUEST message.
+
+If the *MBMS Bearer Service List* IE is included and *URA-ID* IE is not included in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the DRNC shall perform the UE Linking as specified in TS 25.346 [50], section 5.1.6.
+
+If the *MBMS Bearer Service List* IE is included and the *URA-ID* IE is included in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the DRNC shall perform the URA Linking as specified in TS 25.346 [50], section 5.1.10.
+
+If the *MBMS Bearer Service List* IE is included and the *Old URA-ID* IE is included in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the DRNC shall perform URA De-linking for the URA identified by the *Old URA-ID* IE as specified in TS 25.346 [50], section 5.1.10.
+
+[FDD – If the *Enhanced PCH Capability* IE is included in the message, the DRNC should store the information. If the *Enhanced PCH Capability* IE is not included in the message, the DRNC shall use the information to release an RRC Connection for the UE in cells supporting Enhanced PCH.]
+
+[1.28Mcps TDD – If the *Enhanced PCH Capability* IE is included in the message, the DRNC should store the information. If the *Enhanced PCH Capability* IE is not included in the message, the DRNC shall use the information to release an RRC Connection for the UE in cells supporting Enhanced PCH.]
+
+#### 8.2.2.2.1 Successful Operation for Iur-g
+
+The procedure consists of the DOWNLINK SIGNALLING TRANSFER REQUEST message sent by the SRNC/SBSS to the DBSS or by the SBSS to the DRNC.
+
+The message contains the Cell Identifier (*C-ID*) contained in the received UPLINK SIGNALLING TRANSFER INDICATION message and the *D-RNTI*.
+
+Upon receipt of the message, the DBSS shall send the L3 Information on the SRB2 in the cell indicated by the *C-ID* IE to the UE/MS identified by the *D-RNTI* IE.
+
+Upon receipt of the message, the DRNC shall send the L3 Information on the CCCH in the cell indicated by the *C-ID* IE to the UE/MS identified by the *D-RNTI* IE.
+
+#### 8.2.2.3 Abnormal Conditions
+
+If the user identified by the *D-RNTI* IE has already accessed another cell controlled by the DRNC than the cell identified by the *C-ID* IE in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the message shall be ignored.
+
+##### 8.2.2.3.1 Abnormal Conditions for Iur-g
+
+If the user identified by the *D-RNTI* IE has already accessed another cell controlled by the DRNC/DBSS than the cell identified by the *C-ID* IE in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the message shall be ignored.
+
+If the DRNC receives from the SBSS the DOWNLINK SIGNALLING TRANSFER REQUEST message, in which the *D-RNTI Release Indication* IE is set to “not Release D-RNTI”, the DRNC shall ignore this IE and release the *D-RNTI*.
+
+If the DBSS receives from the SBSS/SRNC the DOWNLINK SIGNALLING TRANSFER REQUEST message, in which the *D-RNTI Release Indication* IE is set to “not Release D-RNTI”, the DBSS shall ignore this IE and release the *D-RNTI*.
+
+### 8.2.3 Relocation Commit
+
+#### 8.2.3.1 General
+
+The Relocation Commit procedure is used by source RNC to execute the Relocation. This procedure supports the Relocation procedures described in TS 25.413 [2].
+
+This procedure shall use the signalling bearer mode specified below.
+
+#### 8.2.3.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant Source RNC
+ participant Target RNC
+ Note right of Source RNC: RELOCATION COMMIT
+ Source RNC->>Target RNC: RELOCATION COMMIT
+```
+
+Sequence diagram showing the Relocation Commit procedure. A Source RNC sends a RELOCATION COMMIT message to a Target RNC.
+
+**Figure 3: Relocation Commit procedure, Successful Operation**
+
+The source RNC sends the RELOCATION COMMIT message to the target RNC to request the target RNC to proceed with the Relocation. When the UE is utilising one or more radio links in the DRNC the message shall be sent using the
+
+connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the *D-RNTI* IE shall be included in the message to identify the UE Context in the DRNC.
+
+Upon receipt of the RELOCATION COMMIT message from the source RNC the target RNC finalises the Relocation. If the message contains the transparent *RANAP Relocation Information* IE the target RNC shall use this information when finalising the Relocation.
+
+#### 8.2.3.2.1 Successful Operation for Iur-g
+
+The source RNC/BSS sends the RELOCATION COMMIT message to the target RNC/BSS to request the target RNC/BSS to proceed with the Relocation.
+
+The message shall be sent using the connectionless service of the signalling bearer and the *D-RNTI* IE shall be included in the message to identify the UE/MS context in the DBSS.
+
+Upon receipt of the RELOCATION COMMIT message from the source RNC/BSS, the target RNC/BSS finalises the Relocation. If the message contains the transparent *RANAP Relocation Information* IE the target RNC/BSS shall use this information when finalising the Relocation.
+
+#### 8.2.3.3 Abnormal Conditions
+
+-
+
+### 8.2.4 Paging
+
+#### 8.2.4.1 General
+
+This procedure is used by the SRNC to indicate to a CRNC that a UE shall be paged in a cell or URA that is under the control of the CRNC.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+#### 8.2.4.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant CRNC
+ Note left of SRNC: SRNC
+ Note right of CRNC: CRNC
+ SRNC->>CRNC: PAGING REQUEST
+```
+
+Sequence diagram showing the successful operation of the paging procedure. The SRNC sends a PAGING REQUEST message to the CRNC.
+
+**Figure 4: Paging procedure, Successful Operation**
+
+The procedure is initiated with a PAGING REQUEST message sent from the SRNC to the CRNC.
+
+If the message contains the *C-ID* IE, the CRNC shall page in the indicated cell. Alternatively, if the message contains the *URA-ID* IE, the CRNC shall page in all cells that it controls in the indicated URA.
+
+If the PAGING REQUEST message includes the *CN Originated Page to Connected Mode UE* IE, the CRNC shall include the information contained in the *CN Originated Page to Connected Mode UE* IE when paging the UE.
+
+The CRNC shall calculate the Paging Occasions from the *IMSI* IE and the *DRX Cycle Length Coefficient* IE according to specification in TS 25.304 [15] and apply transmission on PICH and PCH [FDD – or HS-DSCH] [1.28Mcps TDD – or HS-DSCH] accordingly.
+
+[FDD – If the PAGING REQUEST message includes the *Enhanced PCH Capability* IE, the CRNC shall use the information to page the UE in cells supporting Enhanced PCH.]
+
+[1.28Mcps TDD – If the PAGING REQUEST message includes the *Enhanced PCH Capability* IE, the CRNC shall use the information to page the UE in cells supporting Enhanced PCH.]
+
+#### 8.2.4.2.1 Successful Operation for Iur-g
+
+The procedure is initiated with a PAGING REQUEST message sent from the SBSS to the CRNC/CBSS or from the SRNC to the CBSS.
+
+If the message contains the *URA-ID* IE, the CRNC/CBSS shall page in all cells that it controls in the indicated URA/GRA.
+
+If the PAGING REQUEST message includes the *CN Originated Page to Connected Mode UE* IE, the CRNC/CBSS shall include the information contained in the *CN Originated Page to Connected Mode UE* IE when paging the UE.
+
+The CBSS shall calculate the Paging Occasions from the *IMSI* IE and the *GERAN DRX Cycle Length Coefficient* IE according to specification in TS 44.118 [36] and apply transmission on PCCCH or PACCH accordingly.
+
+#### 8.2.4.3 Abnormal Conditions
+
+##### 8.2.4.3.1 Abnormal Conditions for Iur-g
+
+If the DRNC receives a PAGING REQUEST message from the SBSS, which contains the *C-ID* IE, the message shall be ignored.
+
+If the DBSS receives a PAGING REQUEST message from the SBSS/SRNC, which contains the *C-ID* IE, the message shall be ignored.
+
+### 8.2.5 MBSFN MCCH Information
+
+#### 8.2.5.1 General
+
+The procedure is used by the MRNC to inform the CRNC of the MCCH configuration and scheduling information used in MRNC.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+#### 8.2.5.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant MRNC
+ participant CRNC
+ Note right of MRNC: MBSFN MCCH INFORMATION
+ MRNC->>CRNC: MBSFN MCCH INFORMATION
+
+```
+
+Sequence diagram showing the MBSFN MCCH Information procedure. A horizontal line represents the timeline, with vertical bars at the ends labeled CRNC and MRNC. A long arrow points from the MRNC side to the CRNC side, labeled 'MBSFN MCCH INFORMATION'.
+
+**Figure 4A: MBSFN MCCH Information procedure, Successful Operation**
+
+The procedure is used for MBSFN operation when a MRNC is used.
+
+The message contains the MCCH message list sent on the MRNC and the MCCH configuration information of the MRNC.
+
+Upon receipt of the message, if the *MCCH Configuration* IE exists, the CRNC shall setup or reconfigure the MCCH of all cells in the MBSFN cluster with the configuration contained in this IE, and update the System Information of these cells.
+
+The CRNC shall decode the *L3 Information* IE contained in the *MCCH Message List* IE and apply the RLC/MAC/PHY configuration specified by relative MCCH Message to setup the RB information of MTCH, and then send the *L3 Information* IE on the MCCH in the receiving sequence at the beginning of the first MCCH modification period following the CFN indicated by the *CFN* IE.
+
+In case MRNC is used and TDM multiplexing is used over air interface, the *MBSFN Scheduling Transmission Time Interval info List* IE shall be contained to show the scheduling transmission time interval for MBMS service which is configured with MBSFN TDM multiplexing. The CRNC shall schedule received data packets in the scheduling transmission time interval following the time point indicated by the timestamp.
+
+### 8.2.5.3 Abnormal Conditions
+
+-
+
+## 8.2.6 Enhanced Relocation Resource Allocation[1.28Mcps TDD]
+
+### 8.2.6.1 General
+
+The purpose of this procedure is to inform the BSS to pre-allocate resource for UE relocation from UTRAN to GERAN.
+
+This procedure shall use the signalling bearer connection for the relevant UE context.
+
+### 8.2.6.2 Successful Operation
+
+
+
+Sequence diagram for Figure 4B: Enhanced Relocation Resource Allocation Procedure, Successful Operation. It shows two vertical lifelines. A horizontal arrow points from the left lifeline to the right lifeline. A return horizontal arrow points from the right lifeline back to the left lifeline.
+
+**Figure 4B: Enhanced Relocation Resource Allocation Procedure, Successful Operation**
+
+The RNC initiates the Enhanced Relocation Resource Allocation procedure by sending the ENHANCED RELOCATION RESOURCE REQUEST message to the BSS to request the BSS to prepare resource for the relocation.
+
+Upon receipt of the ENHANCED RELOCATION RESOURCE REQUEST message from the RNC, the BSS finalises the relocation resource preparation and sends ENHANCED RELOCATION RESOURCE RESPONSE message to the RNC.
+
+### 8.2.6.3 Unsuccessful Operation
+
+
+
+Sequence diagram for Figure 4C: Enhanced Relocation Resource Allocation Procedure, Unsuccessful Operation. It shows two vertical lifelines. A horizontal arrow points from the left lifeline to the right lifeline. A return horizontal arrow points from the right lifeline back to the left lifeline. A large black rectangular box obscures the top portion of the diagram, covering the initial message exchange.
+
+**Figure 4C: Enhanced Relocation Resource Allocation Procedure, Unsuccessful Operation**
+
+If the BSS is not able to finalise the relocation resource preparation or can not accept the relocation resource request during the handover procedure, the BSS shall send the ENHANCED RELOCATION RESOURCE FAILURE message to the RNC.
+
+### 8.2.6.4 Abnormal Conditions
+
+-
+
+## 8.2.7 Enhanced Relocation Resource Release[1.28Mcps TDD]
+
+### 8.2.7.1 General
+
+This procedure is used by the RNC to inform BSS that related resource pre-allocated for UE shall be released due to failure of the enhanced relocation from UTRAN TDD to GERAN.
+
+This procedure shall use the signalling bearer connection for the relevant UE context.
+
+### 8.2.7.2 Successful Operation
+
+
+
+Sequence diagram for Enhanced Relocation Resource Release Procedure, Successful Operation. It shows two vertical lifelines. A horizontal arrow points from the left lifeline to the right lifeline. A second horizontal arrow points from the right lifeline back to the left lifeline.
+
+**Figure 4D: Enhanced Relocation Resource Release Procedure, Successful Operation**
+
+The Enhanced Relocation Resource Release procedure is initiated by sending the ENHANCED RELOCATION RESOURCE RELEASE COMMAND message from the RNC to the BSS.
+
+Upon reception of the ENHANCED RELOCATION RESOURCE RELEASE COMMAND message, the BSS shall release related resource pre-allocated for UE, and then responded with the ENHANCED RELOCATION RESOURCE RELEASE COMPLETE message.
+
+### 8.2.7.3 Abnormal Conditions
+
+-
+
+## 8.3 Dedicated Procedures
+
+### 8.3.1 Radio Link Setup
+
+#### 8.3.1.1 General
+
+This procedure is used for establishing the necessary resources in the DRNS for one or more radio links.
+
+The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure.
+
+#### 8.3.1.2 Successful Operation
+
+
+
+Sequence diagram for Radio Link Setup procedure: Successful Operation. It shows two vertical lifelines labeled SRNC and DRNC. A horizontal arrow labeled 'RADIO LINK SETUP REQUEST' points from SRNC to DRNC. A horizontal arrow labeled 'RADIO LINK SETUP RESPONSE' points from DRNC back to SRNC.
+
+**Figure 5: Radio Link Setup procedure: Successful Operation**
+
+When the SRNC makes an algorithmic decision to add the first cell or set of cells from a DRNS to the active set of a specific UE-UTRAN connection, the RADIO LINK SETUP REQUEST message is sent to the corresponding DRNC to request establishment of the radio link(s). The Radio Link Setup procedure is initiated with this RADIO LINK SETUP REQUEST message sent from the SRNC to the DRNC.
+
+Upon receipt of the RADIO LINK SETUP REQUEST message, the DRNS shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
+
+The DRNS shall prioritise resource allocation for the RL(s) to be established according to Annex A.
+
+If the RADIO LINK SETUP REQUEST message includes the *Allowed Queuing Time* IE the DRNS may queue the request for a time period not to exceed the value of the *Allowed Queuing Time* IE before starting to execute the request.
+
+If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK SETUP REQUEST message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
+
+If the *Usefulness of Battery Optimization* IE is contained in the RADIO LINK SETUP REQUEST message, the DRNC may store the received value and use it to determine whether this UE can benefit from battery optimization techniques.
+
+### Transport Channels Handling:
+
+#### DCH(s):
+
+[TDD – If the *DCH Information* IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the new DCHs according to the parameters given in the message.]
+
+If the RADIO LINK SETUP REQUEST message includes a *DCH Information* IE with multiple *DCH Specific Info* IEs, then the DRNS shall treat the DCHs in the *DCH Information* IE as a set of co-ordinated DCHs.
+
+If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to “Uplink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.
+
+If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to “Downlink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.
+
+[FDD – For each DCH which do not belong to a set of co-ordinated DCHs, and which includes a *QE-Selector* IE set to “selected”, the DRNS shall use the Transport channel BER from that DCH for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If the *QE-Selector* IE is set to “non-selected”, the DRNS shall use the Physical channel BER for the QE in the UL data frames, TS 25.427 [4].]
+
+For a set of co-ordinated DCHs, the DRNS shall use the Transport channel BER from the DCH with the *QE-Selector* IE set to “selected” for the QE in the UL data frames, TS 25.427 [4]. [FDD – If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If all DCHs have *QE-Selector* IE set to “non-selected”, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4].] [TDD – If no Transport channel BER is available for the selected DCH, the DRNS shall use 0 for the QE, TS 25.427 [4].]
+
+The DRNS shall use the included *UL DCH FP Mode* IE for a DCH or a set of co-ordinated DCHs as the DCH FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs.
+
+The DRNS shall use the included *ToAWS* IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs.
+
+The DRNS shall use the included *ToAWE* IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs.
+
+The *Frame Handling Priority* IE defines the priority level that should be used by the DRNS to prioritise between different frames of the data frames of the DCHs in the downlink on the radio interface in congestion situations once the new RL(s) have been activated.
+
+The *Traffic Class* IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE indicates the value “RRC”.
+
+If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related DCH or set of co-ordinated DCHs.
+
+If the *DCH Information* IE contains a *DCH Specific Info* IE which includes the *Guaranteed Rate Information* IE, the DRNS shall treat the included IEs according to the following:
+
+- If the *Guaranteed Rate Information* IE includes the *Guaranteed UL Rate* IE, the DRNS shall apply the Guaranteed Rate in the uplink of this DCH. The DRNS may decide to request the SRNC
+
+to limit the user rate of the uplink of the DCH at any point in time. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to only reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the *DCH Specific Info* IE in the *DCH Information* IE does not include the *Guaranteed UL Rate* IE, the DRNS shall not limit the user rate of the uplink of the DCH.
+
+- If the *Guaranteed Rate Information* IE includes the *Guaranteed DL Rate* IE, the DRNS shall apply the Guaranteed Rate in the downlink of this DCH. The DRNS may decide to request the SRNC to limit the user rate of the downlink of the DCH at any point in time. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to only reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the *DCH Specific Info* IE in the *DCH Information* IE does not include the *Guaranteed DL Rate* IE, the DRNS shall not limit the user rate of the downlink of the DCH.
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer shall not be Established” for a DCH, then the DRNC shall not establish a transport bearer for the concerned DCH and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer may not be Established” for a DCH and:]
+
+- [FDD – if the DRNC establishes a transport bearer for the concerned DCH, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH being established.]
+- [FDD – if the DRNC does not establish a transport bearer for the concerned DCH, the DRNC shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[TDD – DSCH(s):]**
+
+[TDD – If the *DSCH Information* IE is included in the RADIO LINK SETUP REQUEST message, the DRNC shall establish the requested DSCHs. If the *Transport Layer Address* IE and *Binding ID* IE are included in the *DSCH Information* IE the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the DSCH. In addition, the DRNC shall send a valid set of *DSCH Scheduling Priority* IE and *MAC-c/sh SDU Length* IE parameters to the SRNC in the RADIO LINK SETUP RESPONSE message. If the *PDSCH RL ID* IE indicates a radio link in the DRNS, then the DRNC shall allocate a DSCH-RNTI to the UE Context and include the *DSCH-RNTI* IE in the RADIO LINK SETUP RESPONSE message.]
+
+[TDD – If the *DSCH Information* IE is included in the RADIO LINK SETUP REQUEST message, the DRNS may use the *Traffic Class* IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related DSCHs.]
+
+[TDD – The DRNC shall include the *DSCH Initial Window Size* IE in the RADIO LINK SETUP RESPONSE message for each DSCH, if the DRNS allows the SRNC to start transmission of MAC-c/sh SDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32].]
+
+[TDD – If the RADIO LINK SETUP REQUEST message includes the *TNL QoS* IE in the *DSCH TDD Information* IE and if ALCAP is not used, the DRNS may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.]
+
+#### **[TDD – USCH(s):]**
+
+[TDD – The DRNS shall use the list of RB Identities in the *RB Info* IE in the *USCH information* IE to map each *RB Identity* IE to the corresponding USCH. If the *Transport Layer Address* IE and *Binding ID* IE are included in the *USCH Information* IE the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the USCH.]
+
+[TDD – If the *USCH Information* IE is included in the RADIO LINK SETUP REQUEST message, the DRNS may use the *Traffic Class* IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related USCHs.]
+
+[TDD – If the *USCH Information* IE is included in the RADIO LINK SETUP REQUEST message and contains the *TNL QoS* IE, and if ALCAP is not used, the DRNS may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related USCH.]
+
+[TDD – If the *USCH Information* IE is included in the RADIO LINK SETUP REQUEST message, the DRNS shall establish the requested USCHs, and the DRNC shall provide the [3.84 Mcps TDD – *USCH Information Response* IE] [1.28 Mcps TDD – *USCH Information Response LCR* IE] [7.68 Mcps TDD – *USCH Information Response 7.68 Mcps* IE] in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[TDD – CCTrCH Handling:]**
+
+[TDD – If the *UL CCTrCH Information* IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the new UL CCTrCH(s) according to the parameters given in the message.]
+
+[1.28Mcps TDD – If the *UL CCTrCH Information LCR* IE includes the *TDD TPC Uplink Step Size* IE, the DRNS shall configure the uplink TPC step size according to the parameters given in the message.]
+
+[TDD – If the *DL CCTrCH Information* IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the new DL CCTrCH(s) according to the parameters given in the message.]
+
+[TDD – If the *TPC CCTrCH List* IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the identified UL CCTrCHs with TPC according to the parameters given in the message.]
+
+#### **HS-DSCH:**
+
+If the *HS-DSCH Information* IE is present in the RADIO LINK SETUP REQUEST message, then:
+
+- - The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.
+- - The DRNC shall include the *HARQ Memory Partitioning* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK SETUP RESPONSE message. [FDD – The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.] [1.28Mcps TDD– The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE is included in the *HS-DSCH Information* IE.]
+- - The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the RADIO LINK SETUP RESPONSE message.
+- - The DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.
+- - If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *HS-DSCH Information* IE for an HS-DSCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow.
+- - The DRNS may use the *Traffic Class* IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *HS-DSCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.
+- - If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the *User Plane Congestion Fields Inclusion* IE in the *HS-DSCH Information Response* IE.
+
+- If the RADIO LINK SETUP REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK SETUP REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+- If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.
+- The DRNC shall include the *HS-DSCH Initial Capacity Allocation* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK SETUP RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK SETUP REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to the value “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer I in RADIO LINK SETUP REQUEST in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE.
+- [FDD – If the RADIO LINK SETUP REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR* IE] [7.68 Mcps TDD – *HS-SCCH Specific Information Response 7.68 Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [TDD – The DRNC shall include the [3.84 Mcps TDD – *HS-PDSCH Timeslot Specific Information Response* IE] [1.28 Mcps TDD – *HS-PDSCH Timeslot Specific Information Response LCR* IE] [7.68 Mcps TDD – *HS-PDSCH Timeslot Specific Information Response* IE] in the *HS-DSCH Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – If the RADIO LINK SETUP REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK SETUP RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the DRNC shall not include the *HARQ Preamble Mode Activation Indicator* IE in the RADIO LINK SETUP RESPONSE message.]
+
+- - If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]).
+ - - [FDD – If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.]
+ - - [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC.]
+ - - [FDD – If the *MIMO Activation Indicator* IE, or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then]
+- a) - [FDD – The DRNS shall activate the MIMO mode, or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link.]
+- b) - [FDD – The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- c) - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- d) - [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration are set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+ - - [1.28 Mcps TDD – If the *MIMO Activation Indicator* IE is included in the *HS-DSCH TDD Information* IE, then]
+- e) - [1.28 Mcps TDD – The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.]
+- f) - [1.28 Mcps TDD – The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+ - - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+ - - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE set to “Flexible MAC-d PDU Size” and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+ - - [FDD – If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may use:]
+- g) - [FDD – a different HS-SCCH in consecutive TTIs for this UE;]
+
+h) - [FDD – HS-SCCH orders for the case of HS-SCCH-less operation to this UE.]
+
+- - [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the DRNS may use the supported HSDPA functions for this UE.]
+- - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – The DRNS shall include the *SixtyfourQAM DL Support Indicator* IE in the RADIO LINK SETUP RESPONSE message. This *SixtyfourQAM DL Support Indicator* IE is related to the HS-DSCH Radio Link.]
+- - [1.28 Mcps TDD – The DRNS shall include the *SixtyfourQAM DL Support Indicator* IE in the RADIO LINK SETUP RESPONSE message.]
+- - If the RADIO LINK SETUP REQUEST message includes the *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].
+- - [FDD – If the RADIO LINK SETUP REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
+- - [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.]
+- - [1.28 Mcps TDD – If the *UE TS0 Capability LCR* IE is included in the *HS-DSCH TDD Information* IE, then the DRNC may include the *TS0 HS-PDSCH Indication LCR* IE in the RADIO LINK SETUP RESPONSE message if HS-PDSCH resources could be allocated on TS0 for the UE.]
+- - [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### [FDD – Secondary Serving HS-DSCH:]
+
+[FDD – If the *Additional HS Cell Information RL Setup* IE is present in the RADIO LINK SETUP REQUEST message, then:]
+
+- - [FDD – The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- - [FDD – The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – If the RADIO LINK SETUP REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Secondary Serving Information* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+- - [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC.]
+- [FDD – If the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the MIMO mode, or MIMO with four transmit antennas Mode, or Dual Stream MIMO with four transmit antennas Mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO for the secondary serving HS-DSCH Radio Link and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
+- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and more than one secondary serving HS-DSCH Radio Link is setup, then the DRNS shall use this value in the physical layer.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+- [FDD – If Sixtyfour QAM will not be used for the secondary serving HS-DCSH, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for the secondary serving HS-DSCH Transport Block Size signalling.]
+
+- [FDD – The DRNS shall include the *SixtyfourQAM DL Support Indicator* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### [FDD - Multiflow Setup]:
+
+[FDD - If the *Multiflow Information* IE is present in the RADIO LINK SETUP REQUEST message, then the DRNS shall setup the requested Multiflow operation.]
+
+#### [FDD – E-DCH]:
+
+[FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DCH Minimum Set E-TFCI Validity Indicator* IE the DRNS shall ignore the value in *E-DCH Minimum Set E-TFCI* IE. If the *E-DCH Minimum Set E-TFCI validity indicator* IE is absent DRNS shall use the value for the related resource allocation operation.]
+
+[FDD – If the *E-TFCS Information IE in the E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].]
+
+[FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the DRNS shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the DRNS shall use the value “127” in the algorithm defined in TS 25.214 [10].]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DPCH Information* IE, which contains the *Minimum Reduced E-DPDCH Gain Factor* IE, then the DRNS shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ]
+
+[FDD – If the *E-DCH FDD Information* IE is present in the RADIO LINK SETUP REQUEST message then:]
+
+- [FDD – The DRNS shall setup the requested E-DCH resources on the Radio Links indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+- [FDD – If the RADIO LINK SETUP REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *RL specific E-DCH Information* IE for an E-DCH MAC-d flow, then if the *Transport Bearer Not Requested Indicator* IE is not included for this E-DCH MAC-d flow, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. The DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for every E-DCH MAC-d flow being established for which the *Transport Bearer Not Requested Indicator* IE was not included.]
+- [FDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer shall not be Established” for an E-DCH MAC-d flow, then the DRNC shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.]
+- [FDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer may not be Established” for an E-DCH MAC-d flow and:]
+
+- i) - [FDD – if the DRNC establishes a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.]
+- j) - [FDD – if the DRNC does not establish a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *E-DCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+ - - [FDD – If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being “E-DCH Non-Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.]
+ - - [FDD – If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being “E-DCH Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
+ - - [FDD – If the *TNL QoS* IE is included for a E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+ - - [FDD – The DRNC may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNC may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK SETUP RESPONSE message, for every RL indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+ - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH ReferencePower Offset* IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+
+- - [FDD – If the RADIO LINK SETUP REQUEST message contains the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this DRNS:]
+- k) - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both and include these E-RNTI identifiers and the Channelisation Code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *RL Information Response* IE for the indicated RL in the RADIO LINK SETUP RESPONSE message.]
+- l) - [FDD – The DRNS may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK SETUP RESPONSE message for the initial grant for the serving E-DCH RL.]
+- m) - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- n) - [FDD – If a serving cell change is performed the RADIO LINK SETUP RESPONSE message may contain invalid data (see 9.2.2.4C).]
+ - - [FDD – If the DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK SETUP RESPONSE message, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE, to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+ - - [FDD – The DRNS may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK SETUP RESPONSE message for the serving E-DCH RL.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *Bundling Mode Indicator* IE for a E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to “Bundling” and the *E-TTI* IE is set to “2ms”, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+ - - [FDD – If the RADIO LINK SETUP REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+ - - [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC.]
+
+- - [FDD – If the RADIO LINK SETUP REQUEST message includes the *SixteenQAM UL Operation Indicator* IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.]
+- o) - [FDD – If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]
+
+#### [FDD – Additional E-DCH Setup:]
+
+[FDD – If the *Additional E-DCH Cell Information RL Setup Req* IE is present in the RADIO LINK SETUP REQUEST message, then the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:]
+
+- - [FDD – The DRNS shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – If the *UL SIR Target* IE in the *UL DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE and/or the *DL Power Balancing Information* IE and/or the *Minimum Reduced E-DPDCH Gain Factor* IE in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE are present, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Secondary UL Frequency Activation State* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
+- [FDD – If the *Propagation Delay* IE, the *Initial DL Tx Power* IE, *Primary CPICH Ec/No* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Extended Propagation Delay* IE and/or *Enhanced Primary CPICH Ec/No* IE is included in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH Secondary RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *F-DPCH Slot Format Support Request* IE in the *F-DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message. If the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE includes the *F-DPCH Slot Format* IE, the DRNS may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+- [FDD – If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Processing Overload Level* IE are present in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in same way as for the information used on Primary uplink frequency.]
+- - [FDD – If the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “Separate Iur Transport Bearer Mode” the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+
+- - [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “UL Flow Multiplexing Mode” the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
+ - - [FDD – if Separate Iur Transport Bearer Mode is used in the new configuration, then:]
+- p) - [FDD – The DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the *Transport Bearer Not Requested Indicator* IE in the *RL Specific E-DCH Information* IE in the *RL Information* IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.]
+- q) - [FDD – If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MAC-d flow the DRNS shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+- - [FDD – If activation of power balancing for the Additional E-DCH RL by the RADIO LINK SETUP REQUEST message is supported by the DRNS, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+ - - [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+ - - [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+ - - [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message]
+ - - [FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message and if DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+ - - [FDD – If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:]
+
+- r) - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- s) - [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.]
+- t) - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- u) - [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC. If the *Serving Cell Change CFN* IE is not included then the DRNS shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.]
+ - - [FDD – If the *D-RNTI* IE was included in the RADIO LINK SETUP REQUEST message the DRNS shall include in the RADIO LINK SETUP RESPONSE message the *Primary Scrambling Code* IE, the *UL UARFCN* IE and the *DL UARFCN* IE for the secondary UL frequency in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+ - - [FDD – If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used” in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE RADIO LINK SETUP RESPONSE message.]
+ - - [FDD – If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Secondary CPICH Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message. If the DRNS doesn’t include the *Secondary CPICH Information* IE, it shall not include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used”.]
+
+#### **[FDD – E-DCH –HS-DSCH:]**
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *DCH Indicator For E-DCH-HSDPA Operation* IE, then the DRNS shall ignore the *DCH Information* IE in the RADIO LINK SETUP REQUEST message.]
+
+#### **[1.28 Mcps TDD - Multi-Carrier E-DCH Setup:]**
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information* IE is present in the RADIO LINK SETUP REQUEST message, then the *Multi-Carrier E-DCH Information* IE defines the new configuration and then:]
+
+- - [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+- - [1.28Mcps TDD - The DRNS shall use the corresponding *PRXdes\_base* IE for power control on each uplink frequency according to TS 25.331 [16].]
+- - [1.28Mcps TDD - If the *SNPL Carrier Group Indicator* IE is present in the *Multi-Carrier E-DCH Information LCR* IE, the DRNS shall use the information to determine which SNPL Carrier Group each frequency indicated by the *UARFCN* IE belongs to.]
+
+- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iur transport bearer mode", the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "E-DCH UL flow multiplexing mode", the DRNS shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iur transport bearer.]
+- [1.28Mcps TDD - If the Separate Iur transport bearer mode is used in the new configuration, then the DRNS shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the DRNS shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response 1.28Mcps* IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+
+### Physical Channels Handling:
+
+#### [FDD – Compressed Mode:]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE, the DRNS shall store the information about the Transmission Gap Pattern Sequences to be used in the Compressed Mode Configuration. This Compressed Mode Configuration shall be valid in the DRNS until the next Compressed Mode Configuration is configured in the DRNS or the last Radio Link is deleted.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE and the *Active Pattern Sequence Information* IE, the DRNS shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received *CM Configuration Change CFN* IE refers to latest passed CFN with that value. The DRNS shall treat the received *TGCFN* IEs as follows:]
+
+- [FDD – If any received *TGCFN* IE has the same value as the received *CM Configuration Change CFN* IE, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
+- [FDD – If any received *TGCFN* IE does not have the same value as the received *CM Configuration Change CFN* IE but the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE has already passed, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
+- [FDD – For all other Transmission Gap Pattern Sequences included in the *Active Pattern Sequence Information* IE, the DRNS shall activate each Transmission Gap Pattern Sequence at the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE for the Transmission Gap Pattern Sequence.]
+
+[FDD – If the *Downlink Compressed Mode Method* IE in one or more Transmission Gap Pattern Sequence is set to “SF/2” in the RADIO LINK SETUP REQUEST message and the UE Context is configured to use DPCH in the downlink, the DRNS shall include the *Transmission Gap Pattern Sequence Scrambling Code Information* IE in the RADIO LINK SETUP RESPONSE message indicating for each DL Channelisation Code whether the alternative scrambling code shall be used or not.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE and the *Active Pattern Sequence Information* IE and the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the information provided by the *Downlink Compressed Mode Method* IE if included for the concerned Transmission Gap Pattern Sequence(s).]
+
+[FDD - If the RADIO LINK SETUP REQUEST message includes the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List*
+
+IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]
+
+**[FDD – DL Code Information:]**
+
+[FDD – When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.211 [8]. When *p* number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to “*PhCH number 1*”, the second to “*PhCH number 2*”, and so on until the *p*th to “*PhCH number p*”.]
+
+**[FDD – Phase Reference Handling:]**
+
+[FDD – If Primary CPICH is not to be used as a Phase Reference for this Radio Link, the DRNC shall include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used” in the RADIO LINK SETUP RESPONSE message.]
+
+[FDD – If Secondary CPICH may be used as a Phase Reference for this Radio Link, the DRNC shall include the *Secondary CPICH Information* IE in the RADIO LINK SETUP RESPONSE message.]
+
+[FDD – If the DRNC doesn’t include the *Secondary CPICH Information* IE in the RADIO LINK SETUP RESPONSE message, it shall not include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used” in the RADIO LINK SETUP RESPONSE message.]
+
+**[FDD - UL CLTD Handling:]**
+
+[FDD - If the *UL CLTD Information* IE is present in the RADIO LINK SETUP REQUEST message, then the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights and then :]
+
+- - [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.]
+- - [FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]
+
+**[FDD – UL MIMO Setup:]**
+
+[FDD - If the *UL MIMO Information* IE is present in the RADIO LINK SETUP REQUEST message, then the DRNS shall setup the requested UL MIMO operation.]
+
+**General:**
+
+[FDD – If the *Propagation Delay* IE and optionally the *Extended Propagation Delay* IE are included, the DRNS may use this information to speed up the detection of UL synchronisation on the Uu interface.]
+
+[FDD – If the received *Limited Power Increase* IE is set to “Used”, the DRNS shall, if supported, use Limited Power Increase according to TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control.]
+
+[TDD – If the RADIO LINK SETUP REQUEST message includes the [1.28 Mcps TDD and 3.84 Mcps TDD – *Maximum Number of DL Physical Channels per Timeslot* IE] [7.68 Mcps TDD – *Maximum Number of DL Physical Channels per Timeslot 7.68 Mcps* IE] the DRNC shall take this value into account when allocating physical resources, otherwise the DRNC can assume that this UE capability is consistent with the other signalled UE capabilities.]
+
+[1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Support for 8PSK* IE within the *DL Physical Channel Information* IE or *UL Physical Channel Information* IE, the DRNC shall take this into account in the specified direction when allocating physical resources, otherwise the DRNC can assume that this UE does not support 8PSK resource allocation.]
+
+[1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Support for PLCCH* IE within the *DL Physical Channel Information* IE , the DRNC shall take this into account when allocating PLCCH sequence numbers, otherwise the DRNC can assume that this UE does not support PLCCH.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *DL DPCH Information* IE, then the DRNS shall configure the concerned UE Context to use DPCH in the downlink, i.e. with a DL DPCCH and a DL DPDCH.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *F-DPCH Information* IE, then:]
+
+- - [FDD – The DRNS shall configure the concerned UE Context to use F-DPCH in the downlink, i.e. with transmission of only the TPC field.]
+- - [FDD – If the *F-DPCH Information* IE includes the *F-DPCH Slot Format Support Request* IE, then the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the RADIO LINK SETUP RESPONSE message. If the *F-DPCH Information* IE includes the *F-DPCH Slot Format* IE, the DRNC may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+
+#### **[FDD – E-DPCH Handling:]**
+
+[FDD – If the *UL DPDCH Indicator for E-DCH operation* IE is included in the *UL DPCH Information* IE and set to “UL-DPDCH not present” the *Min UL Channelisation Code Length* IE, the *Puncture Limit* IE and the *TFCS* IE, within the *UL DPCH Information* IE shall be ignored and no UL DPDCH resources shall be allocated.]
+
+#### **[FDD – Continuous Packet Connectivity Handling:]**
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:]
+
+- - [FDD – The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]
+- - [FDD – If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:]
+
+- - [FDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]
+- - [FDD – The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – If at least one of *HS-PDSCH Second Code Support* IE is set to “True”, then the DRNC shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[1.28 Mcps TDD – Continuous Packet Connectivity Handling:]**
+
+[1.28 Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Continuous Packet Connectivity DRX Information LCR* IE, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message.]
+
+[1.28 Mcps TDD – If the *Inactivity Threshold for UE DRX Cycle Ext* IE is included in the *Continuous Packet Connectivity DRX Information LCR* IE, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].]
+
+[1.28 Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall include *Allcoated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – The DRNS shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – The DRNS shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent scheduling operation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]
+
+[1.28 Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall include *Allcoated E-DCH Semi-persistent resource* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – If the *E-DCH Semi-Persistent scheduling Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.]
+
+#### **[1.28 Mcps TDD - MU-MIMO Handling:]**
+
+[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *MU-MIMO Indicator* IE, then:]
+
+- [1.28 Mcps TDD - The DRNS may use the MU-MIMO for the radio link according to the *MU-MIMO Usage Indicator* IE and shall include the *MU-MIMO Information* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – If the *Standalone Midamble Channel Indicator* IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK SETUP RESPONSE message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK SETUP RESPONSE message.]
+
+#### **Radio Link Handling:**
+
+##### **Diversity Combination Control:**
+
+[FDD – The *Diversity Control Field* IE indicates for each RL except for the first RL whether the DRNS shall combine the RL with any of the other RLs or not.]
+
+- [FDD – If the *Diversity Control Field* IE is set to “May” (be combined with another RL), the DRNS shall decide for any of the alternatives.]
+- [FDD – If the *Diversity Control Field* IE is set to “Must”, the DRNS shall combine the RL with one of the other RL.]
+
+- [FDD – If the *Diversity Control Field* IE is set to “Must not”, the DRNS shall not combine the RL with any other existing RL.]
+
+[FDD – When an RL is to be combined, the DRNS shall choose which RL(s) to combine it with.]
+
+[FDD – The *Diversity Control Field* IE is only applicable for DCHs, in case of E-DCH it shall always be assumed to be set to “May”.]
+
+[FDD – In the RADIO LINK SETUP RESPONSE message, the DRNC shall indicate for each RL with the Diversity Indication in the *RL Information Response* IE whether the RL is combined or not.]
+
+- [FDD – In case of not combining with a RL previously listed in the RADIO LINK SETUP RESPONSE message or for the first RL in the RADIO LINK SETUP RESPONSE message, the DRNC shall]
+- [FDD – in case of requested DCHs, include in the *DCH Information Response* IE in the RADIO LINK SETUP RESPONSE message for which the *Transport Bearer Not Requested Indicator* IE was not included the *Binding ID* IE and *Transport Layer Address* IE for the transport bearer to be established for each DCH of this RL.]
+- [FDD – in case of requested DCHs, include in the RADIO LINK SETUP RESPONSE message the *Transport Bearer Not Setup Indicator* IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK SETUP REQUEST message.]
+- [FDD – in case of a requested E-DCH, include in the *E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE for which the *Transport Bearer Not Requested Indicator* IE was not included message the *Binding ID* IE and the *Transport Layer Address* IE for the establishment of transport bearers for every E-DCH MAC-d flow being established.]
+- [FDD – in case of a requested E-DCH, include in the RADIO LINK SETUP RESPONSE message the *Transport Bearer Not Setup Indicator* IE for every E-DCH MAC-d flow for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK SETUP REQUEST message.]
+- [FDD – Otherwise in case of combining, the *RL ID* IE indicates (one of) the RL(s) previously listed in this RADIO LINK SETUP RESPONSE message with which the concerned RL is combined and if the ALCAP is not used and the transport bearer for the DCH is already established, the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE included in the *RL Information* IE for a specific RL in the RADIO LINK SETUP REQUEST message, shall not be used. In case of combining an E-DCH RL, one of the RLs previously listed in this RADIO LINK SETUP RESPONSE message including the *E-DCH FDD Information Response* IE and part of the same Radio Link Set shall be regarded as the RL with which the concerned E-DCH RL is combined and if the ALCAP is not used, the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific E- DCH Information* IE included in the *RL Information* IE for a specific RL in the RADIO LINK SETUP REQUEST message, shall not be used.]
+
+[TDD – The DRNC shall always include in the RADIO LINK SETUP RESPONSE message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each DCH, DSCH and USCH of the RL.]
+
+In the case of a set of co-ordinated DCHs requiring a new transport bearer the *Binding ID* IE and the *Transport Layer Address* IE shall be included in the RADIO LINK SETUP RESPONSE message for only one of the DCHs in the set of co-ordinated DCHs [FDD – where the *Transport Bearer Not Requested Indicator* IE was not included].
+
+#### **[FDD – Transmit Diversity:]**
+
+[FDD – If the cell in which the RL is being set up is capable to provide Close loop Tx diversity, the DRNC shall include the *Closed Loop Timing Adjustment Mode* IE in the RADIO LINK SETUP RESPONSE message indicating the configured Closed loop timing adjustment mode of the cell.]
+
+[FDD – When the *Diversity Mode* IE is set to “STTD”, or “Closed loop mode1”, the DRNC shall activate/deactivate the Transmit Diversity for each Radio Link in accordance with the *Transmit Diversity Indicator* IE.]
+
+[FDD – If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Setup* IE in the RADIO LINK SETUP REQUEST message, the DRNS shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to “None” the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.]
+
+#### DL Power Control:
+
+[FDD – If both the *Initial DL TX Power* IE and *Uplink SIR Target* IE are included in the message, the DRNS shall use the indicated DL TX Power and Uplink SIR Target as initial value. If the value of the *Initial DL TX Power* IE is outside the configured DL TX power range, the DRNS shall apply these constraints when setting the initial DL TX power. The DRNS shall also include the configured DL TX power range defined by *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the RADIO LINK SETUP RESPONSE message. The DRNS shall not transmit with a power higher than indicated by the *Maximum DL TX Power* IE or lower than indicated by the *Minimum DL TX Power* IE on any DL DPCH or on the F-DPCH of the RL except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the $\delta P_{curr}$ , as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
+
+[FDD – If both the *Initial DL TX Power* and the *Uplink SIR Target* IEs are not included in the RADIO LINK SETUP REQUEST message, then DRNC shall determine the initial Uplink SIR Target and include it in the *Uplink SIR Target* IE in the RADIO LINK SETUP RESPONSE message.]
+
+[TDD – The DRNC shall use the *Uplink SIR Target CCTrCH* IEs in the RADIO LINK SETUP RESPONSE message to indicate for any UL CCTrCH an Uplink SIR Target value in case this is deviating from the value included in the *Uplink SIR Target* IE specified for the Radio Link. If in any [3.84Mcps TDD – *UL CCTrCH Information* IE] [1.28Mcps TDD – *UL CCTrCH Information LCR* IE] [7.68Mcps TDD – *UL CCTrCH Information 7.68 Mcps* IE] the *Uplink SIR Target CCTrCH* IE is not included, the value of the *Uplink SIR Target* IE shall apply to the respective UL CCTrCH.]
+
+[FDD – If the *Primary CPICH Ec/No* IE is present, the DRNC should use the indicated value when deciding the Initial DL TX Power. If the *Enhanced Primary CPICH Ec/No* IE is present, the DRNC should use the indicated value when deciding the Initial DL Tx Power.]
+
+[TDD – If [3.84Mcps TDD and 7.68 Mcps TDD – the *DL Time Slot ISCP Info* IE] [1.28Mcps TDD – the *DL Time Slot ISCP Info LCR* IE] is present, the DRNS should use the indicated value when deciding the Initial DL TX Power for the Radio Link. The DRNS shall use the indicated DL Timeslot ISCP when determining the initial DL power per timeslot as specified in TS 25.224 [22], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.]
+
+[TDD – If the *Primary CCPCH RSCP Delta* IE is included, the DRNS should assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP Delta* IE. If the *Primary CCPCH RSCP Delta* IE is not included and the *Primary CCPCH RSCP* IE is included, the DRNS should assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP* IE. The DRNS should use the indicated value when deciding the Initial DL TX Power for the Radio Link.]
+
+[3.84 Mcps TDD and 7.68 Mcps TDD – The DL TX power upper and lower limit is configured in the following way:
+
+- The DRNC shall include the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the RADIO LINK SETUP RESPONSE message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the value(s) for that CCTrCH in the *CCTrCH Maximum DL TX Power* IE and *CCTrCH Minimum DL TX Power* IE. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power* IE/*CCTrCH Maximum DL TX Power* IE or lower than indicated by the appropriate *Minimum DL TX Power* IE/*CCTrCH Minimum DL TX Power* IE on any DL DPCH within each CCTrCH of the RL.]
+
+[1.28 Mcps TDD – The DL TX power upper and lower limit is configured in the following way:
+
+- The DRNC shall include the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* in the RADIO LINK SETUP RESPONSE message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the value(s) for that timeslot in the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* within the *DL Timeslot Information LCR IE*. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power IE* or lower than indicated by the appropriate *Minimum DL TX Power IE* on any DL DPCH within each timeslot of the RL.]
+
+[1.28 Mcps TDD – If the *TSTD Support Indicator IE* is present, the DRNS shall apply this information when configuring the transmit diversity for the new radio link.]
+
+[FDD – The DRNS shall start any DL transmission using the indicated DL TX power level (if received) or the decided DL TX power level on each DL channelisation code or on the F-DPCH of a RL until UL synchronisation is achieved on the Uu interface for the concerned RLS or Power Balancing is activated. No inner loop power control or power balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.214 [10] subclause 5.2.1.2) and the power control procedure (see 8.3.15).]
+
+[TDD – The DRNS shall start any DL transmission using the decided DL TX power level on each DL channelisation code and on each Time Slot of a RL until UL synchronisation is achieved on the Uu interface for the concerned RL. No inner loop power control shall be performed during this period. Then after UL synchronisation, the DL power shall vary according to the inner loop power control (see TS 25.224 [22] subclause 4.2.3.3).]
+
+[FDD – If the received *Inner Loop DL PC Status IE* is set to “Active”, the DRNS shall activate the inner loop DL power control for all RLs. If *Inner Loop DL PC Status IE* is set to “Inactive”, the DRNS shall deactivate the inner loop DL power control for all RLs according to TS 25.214 [10].]
+
+[FDD – If the *DPC Mode IE* is present in the RADIO LINK SETUP REQUEST message, the DRNC shall apply the DPC mode indicated in the message, and be prepared that the DPC mode may be changed during the lifetime of the RL. If the *DPC Mode IE* is not present in the RADIO LINK SETUP REQUEST message, DPC mode 0 shall be applied (see TS 25.214 [10]).]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *DL Power Balancing Information IE* and the *Power Adjustment Type IE* is set to “Common” or “Individual”, the DRNS shall activate the power balancing, if activation of power balancing by the RADIO LINK SETUP REQUEST message is supported, according to subclause 8.3.15, using the *DL Power Balancing Information IE*. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing i.e. $P_{ini}$ shall be set to the power level indicated by the *Initial DL TX Power IE* (if received) or the decided DL TX power level on each DL channelisation code of a RL based on the *Primary CPICH Ec/No IE* or the *Enhanced Primary CPICH Ec/No IE*.]
+
+[FDD – If activation of power balancing by the RADIO LINK SETUP REQUEST message is supported by the DRNS, the DRNC shall include the *DL Power Balancing Activation Indicator IE* in the *RL Information Response IE* in the RADIO LINK SETUP RESPONSE message.]
+
+#### Neighbouring Cell Handling:
+
+If there are UMTS neighbouring cell(s) to the cell in which a Radio Link was established then:
+
+- The DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Neighbouring FDD Cell Information IE* and/or *Neighbouring TDD Cell Information IE* in the *Neighbouring UMTS Cell Information IE* for each neighbouring FDD cell and/or TDD cell respectively. In addition, if the information is available, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Frame Offset IE*, *Primary CPICH Power IE*, *Cell Individual Offset IE*, *STTD Support Indicator IE*, *Closed Loop Model Support Indicator IE*, *Coverage Indicator IE*, *Antenna Co-location Indicator IE* and *HCS Prio IE* in the *Neighbouring FDD Cell Information IE*, and the *Frame Offset IE*, *Cell Individual Offset IE*, *DPCH Constant Value IE*, the *PCCPCH Power IE*, *Coverage Indicator IE*, *Antenna Co-location Indicator IE* and *HCS Prio IE* in the *Neighbouring TDD Cell Information IE* or the *Neighbouring TDD Cell Information LCR IE*. If the *Neighbouring TDD Cell Information IE* includes the *Sync Case IE* for the set to “Case1”, the DRNC shall include the *Time Slot For SCH IE* in the *Neighbouring TDD Cell Information IE*. If the *Neighbouring TDD Cell*
+
+*Information* IE includes *Sync Case* IE set to "Case2", the DRNC shall include the *SCH Time Slot* IE in the *Neighbouring TDD Cell Information* IE.
+
+- - If a UMTS neighbouring cell is not controlled by the same DRNC, the DRNC shall also include in the RADIO LINK SETUP RESPONSE message the *CN PS Domain Identifier* IE and/or *CN CS Domain Identifier* IE which are the identifiers of the CN nodes connected to the RNC controlling the UMTS neighbouring cell.
+- - If the information is available, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *DPC Mode Change Support Indicator* IE for each neighbour cell in the *Neighbouring FDD Cell Information* IE.
+- - The DRNC shall include the *Cell Capability Container FDD* IE, the *Cell Capability Container TDD* IE, the *Cell Capability Container TDD LCR* IE and/or the *Cell Capability Container Extension FDD* IE if the DRNC is aware that the neighbouring cell supports any functionality listed in 9.2.2.D, 9.2.3.1a, 9.2.3.1b and/or the *Cell Capability Container Extension FDD* IE.
+- - [FDD – The DRNC shall, if supported, include the *Cell List Validity Indicator* IE if the neighbouring cell is multi cell capable and/or dual band capable but the cell can not be the serving HS-DSCH in a multicell and/or dual band configuration. Hence the cell can only serve as the secondary serving HS-DSCH cell. When *Cell List Validity Indicator* IE is included the SRNC should ignore the indicated cell list(s).]
+- - [FDD – For each cell in the *Secondary Serving Cell List* IE that is Multi Cell E-DCH capable, indicated in the *Cell Capability Container Extension FDD* IE by the "Multi Cell E-DCH Support Indicator" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the cell identified by the *C-ID* IE as the corresponding cell of the primary uplink frequency, the DRNS shall, if supported, include the *Multicell E-DCH Restriction* IE set to "TRUE".]
+- - For the UMTS neighbouring cells which are controlled by the DRNC, the DRNC shall report in the RADIO LINK SETUP RESPONSE message the restriction state of those cells, otherwise the *Restriction State Indicator* IE may be absent. The DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Restriction State Indicator* IE for the neighbouring cells which are controlled by the DRNC in the *Neighbouring FDD Cell Information* IE, the *Neighbouring TDD Cell Information* IE and the *Neighbouring TDD Cell Information LCR* IE.
+- - If MOCN or GWCN network sharing configuration is used then the DRNC shall include the broadcasted PLMN identities of the concerned neighbouring cells in the *Multiple PLMN List* IE in the *Neighbouring FDD Cell Information* IE, the *Neighbouring TDD Cell Information* IE and the *Neighbouring TDD Cell Information LCR* IE.
+- - If available, the DRNC shall include the *SNA Information* IE for the concerned neighbouring cells in the *Neighbouring FDD Cell Information* IE, the *Neighbouring TDD Cell Information* IE and the *Neighbouring TDD Cell Information LCR* IE.
+- - If available, the DRNC shall include the *Frequency Band Indicator* IE for the concerned neighbouring cells in the *Neighbouring FDD Cell Information* IE.
+- - If the number of neighbouring UMTS RNCs is beyond the predefined maximum number, the DRNC shall, if supported, include the remaining neighbouring information in the *Neighbouring UMTS Cell Information Extension* IE. The IE filling rules in the Neighbouring UMTS Cell Information shall also apply to the *Neighbouring UMTS Cell Information Extension* IE.
+
+If there are GSM neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Neighbouring GSM Cell Information* IE for each of the GSM neighbouring cells. If available the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Cell Individual Offset* IE, and if the *Cell Individual Offset* IE alone cannot represent the value of the offset, the DRNC shall also include the *Extended GSM Cell Individual Offset* IE in the *Neighbouring GSM Cell Information* IE. If available the DRNC shall also include in the RADIO LINK SETUP RESPONSE message the *Coverage Indicator* IE, *Antenna Co-location Indicator* IE and *HCS Prio* IE in the *Neighbouring GSM Cell Information* IE. If available, the DRNC shall also include the *SNA Information* IE for the concerned neighbouring cells in the *Neighbouring GSM Cell Information* IE. If network sharing configuration is used then the DRNC may include the broadcasted PLMN identities of the concerned neighbouring cells in the *PLMN List* IE in the *Neighbouring GSM Cell Information* IE.
+
+When receiving the *SNA Information* IE in the RADIO LINK SETUP RESPONSE message, the SRNC should use it to restrict cell access based on SNA information. See also TS 25.401 [40] for a broader description of the SNA access control.
+
+If there are GERAN neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include the *GERAN Cell Capability* IE in the *Neighbouring GSM Cell Information* IE that is included in the RADIO LINK SETUP RESPONSE message for each of the GERAN cells.
+
+If there are GERAN Iu-mode neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include, if available, the *GERAN Classmark* IE in the *Neighbouring GSM Cell Information* IE that is included in the RADIO LINK SETUP RESPONSE message for each of the GERAN Iu-mode neighbouring cells. TS 43.051 [39] defines when the transmission of the *GERAN Classmark* IE will be required at the initiation of the Relocation Preparation procedure.
+
+If there are E-UTRA neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Neighbouring E-UTRA Cell Information* IE for each of the E-UTRA neighbouring cells, and may also include the *PCI* IE, *TAC* IE and *PLMN List* IE in the *Neighbouring E-UTRA Cell Information* IE in the RADIO LINK SETUP RESPONSE message.
+
+#### **[1.28Mcps TDD – Uplink Synchronisation Parameters LCR:]**
+
+[1.28Mcps TDD – If the *Uplink Synchronisation Parameters LCR* IE is present, the DRNC shall use the indicated values of *Uplink synchronisation stepsize* IE and *Uplink synchronisation frequency* IE when evaluating the timing of the UL synchronisation.]
+
+#### **[1.28Mcps TDD – Shared physical channels Synchronisation Detection:]**
+
+[1.28Mcps TDD – If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall also include the *Out-of-sync Detection Window* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[1.28Mcps TDD – Uplink Timing Advance Control LCR:]**
+
+[1.28Mcps TDD – The DRNC shall include the *Uplink Timing Advance Control LCR* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[1.28Mcps TDD – PowerControl GAP:]**
+
+[1.28Mcps TDD – If applied in the DRNS, the DRNC may include the *PowerControl GAP* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[1.28Mcps TDD – E-UTRAN Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Idle Interval Configuration Indicator* IE, if supported, the DRNC shall include the *Idle Interval Information* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[1.28Mcps TDD – RNTI Allocation Indicator:]**
+
+[1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *RNTI Allocation Indicator* IE, if supported, the DRNS may allocate an E-RNTI and/or an H-RNTI for UE to use in CELL\_FACH state.]
+
+#### **[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *DCH Measurement Type indicator* IE, if supported, the DRNS shall include the *Measurement purpose* IE and the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE in the RADIO LINK SETUP RESPONSE message to configure the measurement occasion pattern(s) indicated by the *DCH Measurement Type indicator* IE.]
+
+#### **MBMS Handling:**
+
+If the *MBMS Bearer Service List* IE is included in the RADIO LINK SETUP REQUEST message, the DRNC shall, if supported, perform the UE Linking as specified in TS 25.346 [50], section 5.1.6. If the UE Link is currently stored in the UE Context or the *MBMS Bearer Service List* IE is included in the RADIO LINK SETUP REQUEST message and if an MBMS session for some MBMS bearer services contained in the UE
+
+Link is ongoing in some of the cells identified by the *C-ID* IEs in the RADIO LINK SETUP REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the *Active MBMS Bearer Service List* IE the *Transmission Mode* IE in the concerned *RL Information Response* IEs in the RADIO LINK SETUP RESPONSE message.
+
+If the UE Link is currently stored in the UE Context or the *MBMS Bearer Service List* IE is included in the RADIO LINK SETUP REQUEST message and if an MBMS preferred frequency layer for some active MBMS bearer services contained in the UE Link is set in some of the cells identified by the *C-ID* IEs in the RADIO LINK SETUP REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the *Active MBMS Bearer Service List* IE the *Preferred Frequency Layer* IE in the concerned *RL Information Response* IEs in the RADIO LINK SETUP RESPONSE message.
+
+#### [FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE for a Radio Link not indicated by the *HS-PDSCH RL ID* IE the DRNS shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [63]: ]
+
+- - [FDD – The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK SETUP REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of *Secondary C-ID* IEs in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK SETUP REQUEST message. ]
+- - [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ]
+ - - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell.]
+ - - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells.]
+- - [FDD –If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ]
+- - [FDD – The DRNS shall return these codes in the *Sets of HS-SCCH Codes* IE along with the corresponding per-cell *HS-DSCH-RNTI* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message. ]
+- - [FDD – The DRNS shall use the first in the numbered list of the primary serving HS-DSCH cell's HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the SRNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [16].]
+- - [FDD – The DRNS shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message, IEs according to the rules defined for HS-DSCH setup and: ]
+ - - [FDD – if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *HARQ Preamble Mode Activation Indicator* IE.]
+ - - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE.]
+ - - [FDD – if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the Pilot Configuration and MIMO N/M Ratio in *MIMO Information Response* IE.]
+
+- - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *Pilot Configuration* and *MIMO N/M Ratio* in *MIMO Information Response* IE]
+- - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *Pilot Configuration* and *MIMO N/M Ratio* in *MIMO Information Response* IE]
+- - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE.]
+- - [FDD – if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to “Flexible MAC-d PDU Size” and if Sixtyfour QAM will not be used in the preconfiguration, the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell.]
+- - [FDD – if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell.]
+- - [FDD – if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE.]
+- - [FDD – if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS shall store this information in the preconfigured configuration.]
+- - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH Preconfiguration Info* IE in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – the *SixtyfourQAM DL Support Indicator* IE shall be included.]
+- - [FDD – if the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS may store this information in the preconfigured configuration.]
+- - [FDD – the DRNS shall, if supported, include in the *Sets of HS-SCCH Codes* IE the *Measurement Power Offset* IE for each preconfigured cell.]
+- - [FDD – The DRNS shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows: ]
+ - - [FDD – The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.]
+ - - [FDD – The DRNS may preconfigure the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.]
+- - [FDD –If the *HS-DSCH Preconfiguration Setup* IE includes the *E-DCH Indicator* IE for a secondary cell, the DRNS shall include in the *Additional E-DCH Preconfiguration Information* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message the *E-DCH FDD DL Control Channel Information* containing the
+
+preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the *E-DCH Indicator* IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]
+
+- - [FDD – The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE. ]
+- - [FDD – The DRNS may preconfigure the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving Additional E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.]
+- - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where HS-DSCH / secondary HS-DSCH is preconfigured, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH Preconfiguration Info* IE or in the *Sets of HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Info* IE for each preconfigured cell in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the DRNC shall allocate resources for the preconfigured Multiflow.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the DRNC shall allocate resources for the preconfigured F-TPICH channel and include *F-TPICH Information Response* IE in the *HS-DSCH Preconfiguration Info* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the DRNC shall allocate resources for the preconfigured UL CLTD.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the DRNC shall allocate resources for the preconfigured UL MIMO.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixteen QAM.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixtyfour QAM.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Non-Serving RL Preconfiguration Setup* IE in the *RL Information* IE and:]
+
+- - [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK SETUP RESPONSE message.]
+- - [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of *new Serving RL* in
+
+*Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE* for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info IE* in the RADIO LINK SETUP RESPONSE message.]
+
+- [FDD –If the *F-TPICH Information IE* is included, the DRNC shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [8], and include *F-TPICH Information Response IE* in the *Non-Serving RL Preconfiguration Info IE*.]
+
+#### General:
+
+If the RADIO LINK SETUP REQUEST message includes the *RL Specific DCH Information IE*, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD – for every DCH being established for which the *Transport Bearer Not Requested Indicator IE* was not included].
+
+If no *D-RNTI IE* was included in the RADIO LINK SETUP REQUEST message, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *D-RNTI IE*, the *CN PS Domain Identifier IE* and/or the *CN CS Domain Identifier IE* for the CN domains (using LAC and RAC of the current cell) to which the DRNC is connected.
+
+[1.28 Mcps TDD – If no *D-RNTI IE* was included in the RADIO LINK SETUP REQUEST message, the DRNC could include in the RADIO LINK SETUP RESPONSE message the *UARFCN IE*.]
+
+[FDD – If the *D-RNTI IE* was included in the RADIO LINK SETUP REQUEST message the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Primary Scrambling Code IE*, the *UL UARFCN IE* and the *DL UARFCN IE*.]
+
+[TDD – If the *D-RNTI IE* was included in the RADIO LINK SETUP REQUEST message the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *UARFCN IE*, the *Cell Parameter ID IE* and the *SCTD Indicator IE*.]
+
+[3.84Mcps TDD and 7.68 Mcps TDD – If the *D-RNTI IE* was included in the RADIO LINK SETUP REQUEST message the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Sync Case IE* and if the *Sync Case IE* is set to “Case 2”, the DRNC shall also include the *SCH Time Slot IE* in the RADIO LINK SETUP RESPONSE message. If the included *Sync Case IE* is set to “Case1”, the DRNC shall also include the *Time Slot For SCH IE*.]
+
+[3.84Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD IE* in the RADIO LINK SETUP RESPONSE message if at least one *DSCH Information Response IE* or *USCH Information Response IE* is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the *Secondary CCPCH Info TDD IE* in the RADIO LINK SETUP RESPONSE message if at least one *DSCH Information Response IE* or *USCH Information Response IE* is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[1.28 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD LCR IE* in the RADIO LINK SETUP RESPONSE message if at least one *DSCH Information Response LCR IE* or *USCH Information Response LCR IE* is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the *Secondary CCPCH Info TDD LCR IE* in the RADIO LINK SETUP RESPONSE message if at least one *DSCH Information Response LCR IE* or *USCH Information Response LCR IE* is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[7.68 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info 7.68Mcps TDD IE* in the RADIO LINK SETUP RESPONSE message if at least one *DSCH Information Response 7.68 Mcps IE* or *USCH Information Response 7.68 Mcps IE* is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the *Secondary CCPCH Info 7.68Mcps TDD IE* in the RADIO LINK SETUP RESPONSE message if at least one *DSCH Information Response 7.68 Mcps IE* or *USCH Information Response 7.68 Mcps IE* is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+For each Radio Link established in a cell in which at least one URA Identity is being broadcast, the DRNC shall include in the *URA Information IE* within the RADIO LINK SETUP RESPONSE message *URA*
+
+Information for this cell including the *URA ID* IE, the *Multiple URAs Indicator* IE indicating whether or not multiple URA Identities are being broadcast in the cell, and the *RNC-ID* IE of all other RNCs that have at least one cell within the URA identified by the *URA ID* IE.
+
+Depending on local configuration in the DRNS, the DRNC may include in the RADIO LINK SETUP RESPONSE message the *UTRAN Access Point Position* IE and the geographical co-ordinates of the cell, represented either by the *Cell GAI* IE or by the *Cell GA Additional Shapes* IE. If the DRNC includes the *Cell GA Additional Shapes* IE in the RADIO LINK SETUP RESPONSE message, it shall also include the *Cell GAI* IE.
+
+If the DRNS need to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Allowed UL Rate* IE in the *DCH Information Response* IE for this Radio Link.
+
+If the DRNS need to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the *Allowed DL Rate* IE in the *DCH Information Response* IE for this Radio Link.
+
+If the *Permanent NAS UE Identity* IE is included in the RADIO LINK SETUP REQUEST message, the DRNS shall store the information for the considered UE Context for the life-time of the UE Context.
+
+If the RADIO LINK SETUP REQUEST message includes the *Permanent NAS UE Identity* IE and a *C-ID* IE corresponding to a cell reserved for operator use, the DRNS shall use this information to determine whether it can set up a Radio Link on this cell or not for the considered UE Context.
+
+If the HCS priority information is available in the DRNS, it shall include the *HCS Prio* IE for each of the established RLs in the RADIO LINK SETUP RESPONSE message.
+
+The DRNS shall start receiving on the new RL(s) after the RLs are successfully established.
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Cell Portion ID* IE, the DRNS shall use this information when it decides to use beamforming for the new RL.]
+
+[1.28 Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Cell Portion LCR ID* IE, the DRNS shall use this information when it decides to allocate physical resource for the new RL.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Initial DL DPCH Timing Adjustment Allowed* IE, then the DRNS may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the DRNS shall include, for the concerned Radio Link(s), the *Initial DL DPCH Timing Adjustment* IE in the *Radio Link Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *D-RNTI* IE which already has a RL and *Synchronisation Indicator* IE, the DRNC shall ignore the value in the *Frame Offset* IE and *Chip Offset* IE in the RADIO LINK SETUP REQUEST message and shall include in the *Frame Offset* IE and *Chip Offset* IE the values used for already established RL in the RADIO LINK SETUP RESPONSE message.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message includes the *F-TPICH Information* IE in the *RL Information* IE, the DRNS shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10], and shall include the *F-TPICH Information Response* IE in the RADIO LINK SETUP RESPONSE message.]
+
+#### **[FDD – Radio Link Set Handling:]**
+
+[FDD – The *First RLS Indicator* IE indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The DRNS shall use the *First RLS Indicator* IE to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.]
+
+[FDD – For each RL not having a common generation of the TPC commands in the DL with another RL, the DRNS shall assign to the RL a unique value for the *RL Set ID* IE which uniquely identifies the RL as an RL Set within the UE Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Set(s) shall not be common.]
+
+[FDD – For all RLs having a common generation of the TPC commands in the DL with another RL, the DRNS shall assign to each RL the same value for the *RL Set ID* IE which uniquely identifies these RLs as members of the same RL Set within the UE Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.]
+
+[FDD –The UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N\_INSYNC\_IND that are configured in the cells supporting the radio links of the RL Set.]
+
+[FDD – For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the *E-DCH RL Set ID* IE in the RADIO LINK SETUP RESPONSE message. The value of the *E-DCH RL Set ID* IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
+
+#### [TDD- E-DCH:]
+
+[TDD – If the [3.84Mcps – *E-DCH Information* IE][1.28Mcps – *E-DCH Information 1.28Mcps* IE][7.68Mcps TDD – *E-DCH Information 7.68Mcps* IE] is present in the RADIO LINK SETUP REQUEST message:]
+
+- [TDD – The DRNS shall setup the requested E-DCH resources on the Radio Link indicated by the *E-DCH Serving RL* IE.]
+- [TDD – If the *TNL QoS* IE is included in the *E-DCH MAC-d Flows Information TDD* IE for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [TDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *E-DCH MAC-d Flows Information TDD* IE for an E-DCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.]
+- [TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flows Information TDD* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [TDD – If in the RADIO LINK SETUP REQUEST message the *E-DCH Grant Type* IE in the *E-DCH MAC-d Flows Information TDD* IE is set to “Non-scheduled” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants are configured for that E-DCH MAC-d flow.]
+- [TDD – If in the RADIO LINK SETUP REQUEST message the *E-DCH Grant Type* IE in the *E-DCH MAC-d Flows Information TDD* IE is set to “Scheduled” the DRNS shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.]
+- [TDD – If the RADIO LINK SETUP REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows Information TDD* IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions for the related queue.]
+- [1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *MAC-es Maximum Bit Rate LCR* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows Information TDD* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [TDD – If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+- [3.84Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH TDD Maximum Bitrate* IE in the *E-DCH TDD Information* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+
+- [1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Physical Layer Category LCR IE* or *Extended E-DCH Physical Layer Category LCR IE* in the *E-DCH TDD Information LCR IE* for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [7.68Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH TDD Maximum Bitrate 7.68Mcps IE* in the *E-DCH TDD Information 7.68Mcps IE* for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [3.84Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Processing Overload Level IE* in the *E-DCH TDD Information IE*, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level IE*, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [7.68Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Processing Overload Level IE* in the *E-DCH TDD Information 7.68Mcps IE*, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level IE*, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Processing Overload Level IE* in the *E-DCH TDD Information LCR IE*, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level IE*, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [TDD – The DRNS may use the *Traffic Class IE* for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B.]
+- [TDD – If the RADIO LINK SETUP REQUEST message includes the [3.84Mcps TDD – *E-DCH TDD Information IE*][1.28Mcps TDD – *E-DCH TDD Information LCR IE*] in the *E-DCH MAC-d Flows Information TDD IE*, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Maximum Number of Retransmission for Scheduling Info LCR IE* and the *E-DCH Retransmission timer for Scheduling Info LCR IE* in the *E-DCH TDD Information LCR IE*, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
+- [3.84Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information TDD IE* in the *E-DCH Information Response IE* in the RADIO LINK SETUP RESPONSE message.]
+- [3.84Mcps TDD – The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the *E-DCH Information Response IE* in the RADIO LINK SETUP RESPONSE message.]
+- [1.28Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information LCR TDD IE* in the *E-DCH Information Response 1.28Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [1.28Mcps TDD – The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier, the E-AGCH(s) and E-HICH(s) assigned in the *E-DCH Information Response 1.28Mcps IE* in the RADIO LINK SETUP RESPONSE message.]
+- [7.68Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE* in the *E-DCH Information Response 7.68Mcps IE* in the RADIO LINK SETUP RESPONSE message.]
+- [7.68Mcps TDD – The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the *E-DCH Information Response 7.68Mcps IE* in the RADIO LINK SETUP RESPONSE message.]
+- [1.28Mcps TDD – If the RADIO LINK SETUP REQUEST message includes the *Multi-Carrier E-DCH Physical Layer Category LCR IE* in the *E-DCH TDD Information LCR IE*, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
+
+- [1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present and if the RADIO LINK SETUP REQUEST message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]
+
+#### Response Message:
+
+Upon receipt of the RADIO LINK SETUP REQUEST message, the DRNS allocates the requested type of channelisation codes and other physical channel resources for each RL and assigns a binding identifier and a transport layer address for each DCH, for each set of co-ordinated DCHs [TDD – and for each DSCH and USCH]. This information shall be sent to the SRNC in the RADIO LINK SETUP RESPONSE message when all the RLs have been successfully established.
+
+[1.28 Mcps TDD – if the DRNS assigns one or more PLCCH sequence numbers to the radio link, then the PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK SETUP RESPONSE message.]
+
+After sending the RADIO LINK SETUP RESPONSE message the DRNS shall continuously attempt to obtain UL synchronisation on the Uu interface and start reception on the new RL.
+
+For each RL for which the *Delayed Activation* IE is not included in the RADIO LINK SETUP REQUEST message the DRNS shall:
+
+- [FDD – start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4].]
+- [TDD – start transmission on the new RL immediately as specified in TS 25.427 [4].]
+
+For each RL for which the *Delayed Activation* IE is included in the RADIO LINK SETUP REQUEST message, the DRNS shall:
+
+- if the *Delayed Activation* IE indicates “Separate Indication”:
+ - - not start any DL transmission for the concerned RL on the Uu interface.
+- if the *Delayed Activation* IE indicates “CFN”:
+ - - [FDD – start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4], however never before the CFN indicated in the *Activation CFN* IE.]
+ - - [TDD – start transmission on the new RL at the CFN indicated in the *Activation CFN* IE as specified in TS 25.427 [4].]
+
+### 8.3.1.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: Unsuccessful Operation
+ SRNC->>DRNC: RADIO LINK SETUP REQUEST
+ DRNC-->>SRNC: RADIO LINK SETUP FAILURE
+
+```
+
+Sequence diagram showing the Radio Link Setup procedure for an Unsuccessful Operation. The diagram shows two vertical lines representing the SRNC (left) and DRNC (right). A horizontal arrow labeled 'RADIO LINK SETUP REQUEST' points from the SRNC to the DRNC. A horizontal arrow labeled 'RADIO LINK SETUP FAILURE' points from the DRNC back to the SRNC.
+
+**Figure 6: Radio Link Setup procedure: Unsuccessful Operation**
+
+If the establishment of at least one radio link is unsuccessful, the DRNC shall respond with a RADIO LINK SETUP FAILURE message. The DRNC shall include in the RADIO LINK SETUP FAILURE message a general *Cause* IE or a *Cause* IE for each failed radio link. The *Cause* IE indicates the reason for failure.
+
+[FDD – If some radio links were established successfully, the DRNC shall indicate this in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message.]
+
+If the RADIO LINK SETUP REQUEST message includes a *C-ID* IE corresponding to a cell reserved for operator use and the *Permanent NAS UE Identity* IE is not present, the DRNC shall reject the procedure and send the RADIO LINK SETUP FAILURE message.
+
+[FDD – If the RL identified by the *HS-PDSCH RL ID* IE is a radio link in the DRNS and this RL is successfully established, then the DRNC shall allocate a HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE, the *HS-DSCH FDD Information Response* IE and the *SixtyfourQAM DL Support Indicator* IE in the RADIO LINK SETUP FAILURE message. This *SixtyfourQAM DL Support Indicator* IE is related to the HS-DSCH Radio Link.]
+
+[FDD – If the RL identified by the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Setup* IE is a radio link in the DRNS and this RL is successfully established, then the DRNC shall allocate a HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE, the *HS-DSCH FDD Secondary Serving Information Response* IE and the *SixtyfourQAM DL Support Indicator* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP FAILURE message. If the establishment of the RL identified by the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Setup* IE, i.e secondary serving HS-DSCH Radio Link is unsuccessful but the establishment of the RL identified by the *HS-PDSCH RL ID* IE for the serving HS-DSCH Radio Link is successful, then the DRNC shall indicate the unsuccessful secondary serving HS-DSCH Radio Link in the *Unsuccessful RL Information Response* IE in the RADIO LINK SETUP FAILURE message by setting the *RL ID* IE to the same value as the unsuccessful *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Setup* IE.]
+
+[1.28 Mcps TDD – If the RL identified by the *HS-PDSCH RL ID* IE is a radio link in the DRNS and this RL is successfully established, then the DRNC shall allocate a HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE, the *HS-DSCH TDD Information Response* IE and the *SixtyfourQAM DL Support Indicator* IE in the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the *MIMO Activation Indicator* IE is included and the *Power Offset For S-CPICH for MIMO Request Indicator* IE is not included in the *HS-DSCH FDD Information* IE in the RADIO LINK SETUP REQUEST message but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link shall be reported as failed and the DRNC shall include in the RADIO LINK SETUP FAILURE message the *Cause* IE.]
+
+[FDD – If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included and the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is not included in the *HS-DSCH FDD Information* IE in the RADIO LINK SETUP REQUEST message but MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link shall be reported as failed and the DRNC shall include in the RADIO LINK SETUP FAILURE message the *Cause* IE.]
+
+[FDD – If the RL identified by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE is a radio link in the DRNS and this RL is successfully established, then the DRNS shall include the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message. If the establishment of the RL identified by the *E-DCH Additional RL ID* IE is unsuccessful, then the DRNS shall indicate the unsuccessful setup of the Additional E-DCH Radio Link in the *Unsuccessful RL Information Response* IE in the RADIO LINK SETUP FAILURE message by setting the *RL ID* IE to the same value as the unsuccessful *E-DCH Additional RL ID* IE in the *Additional E-DCH Cell Information Setup* IE.]
+
+Typical cause values are:
+
+#### Radio Network Layer Causes:
+
+[FDD – UL Scrambling Code Already in Use;]
+ DL Radio Resources not Available;
+ UL Radio Resources not Available;
+ [FDD – Combining Resources not available;]
+ Combining not Supported
+ Requested Configuration not Supported;
+ Cell not Available;
+ [FDD – Requested Tx Diversity Mode not Supported;]
+ Power Level not Supported;
+ Number of DL codes not supported;
+ Number of UL codes not supported;
+ Dedicated Transport Channel Type not Supported;
+ DL Shared Channel Type not Supported;
+ [TDD – UL Shared Channel Type not Supported;]
+ [FDD – UL Spreading Factor not Supported;]
+ [FDD – DL Spreading Factor not Supported;]
+
+CM not Supported;
+[FDD – DPC mode change not Supported;]
+Cell reserved for operator use;
+Delayed Activation not supported;
+E-DCH not supported;
+[FDD – F-DPCH not supported;]
+[FDD – Continuous Packet Connectivity DTX-DRX operation not Supported;]
+[FDD – Continuous Packet Connectivity HS-SCCH less operation not Supported;]
+[FDD – MIMO not supported;]
+[FDD – E-DCH TTI2ms not supported;]
+[FDD – Continuous Packet Connectivity DTX-DRX operation not available;]
+[FDD – Continuous Packet Connectivity UE DTX Cycle not available;]
+[FDD – MIMO not available;]
+[FDD – SixteenQAM UL not Supported;]
+HS-DSCH MAC-d PDU Size Format not supported;
+[FDD – F-DPCH Slot Format operation not supported;]
+E-DCH MAC-d PDU Size Format not available;
+[FDD – E-DPCCH Power Boosting not supported;]
+[FDD – SixtyfourQAM DL and MIMO Combined not available;]
+[FDD – Multi Cell operation not available;]
+[FDD – Multi Cell operation not supported;]
+[FDD – Multi Cell operation with MIMO not available;]
+[FDD – Multi Cell operation with MIMO not supported;]
+[FDD – Single Stream MIMO not supported;]
+[FDD – Single Stream MIMO not available;]
+[FDD – TX diversity for MIMO UE on DL Control Channels not available;]
+[FDD – Multi Cell E-DCH Operation not supported;]
+[FDD – Multi Cell E-DCH Operation not available;]
+[FDD – Multi Cell operation with Single Stream MIMO not available;]
+[FDD – Multi Cell operation with Single Stream MIMO not supported;]
+[FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available;]
+[FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported;]
+[FDD – Frequency Specific Compressed Mode Not Available;]
+[FDD – Uplink Closed Loop Transmit Diversity Operation Not Available;]
+[FDD – Uplink Closed Loop Transmit Diversity Operation Not Supported;]
+[FDD – MIMO with four transmit antennas not supported;]
+[FDD – MIMO with four transmit antennas not available;]
+[FDD – Dual Stream MIMO with four transmit antennas not supported;]
+[FDD – Dual Stream MIMO with four transmit antennas not available;]
+[FDD – Multiflow Operation Not Available;]
+[FDD – Multiflow Operation Not Supported;]
+[FDD – SixtyfourQAM UL not Available;]
+[FDD – SixtyfourQAM UL not Supported;]
+[FDD – UL MIMO Operation Not Available;]
+[FDD – UL MIMO Operation Not Supported;]
+[FDD – UL MIMO and SixteenQAM Operation Not Available;]
+[FDD – UL MIMO and SixteenQAM Operation Not Supported;]
+[FDD – UL MIMO and SixtyfourQAM Operation Not Available;]
+[FDD – UL MIMO and SixtyfourQAM Operation Not Supported.]
+
+#### **Transport Layer Causes:**
+
+Transport Resource Unavailable.
+
+#### **Miscellaneous Causes:**
+
+Control Processing Overload;
+HW Failure;
+Not enough User Plane Processing Resources.
+
+### 8.3.1.4 Abnormal Conditions
+
+If the DRNC receives either an S-RNTI or a D-RNTI which already has RL(s) established [FDD – and the *Synchronisation Indicator* IE is not included in the RADIO LINK SETUP message,] the DRNC shall send the RADIO LINK SETUP FAILURE message to the SRNC, indicating the reason for failure.
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Active Pattern Sequence Information* IE, but the *Transmission Gap Pattern Sequence Information* IE is not present, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes both the *Initial DL TX Power* IE and the *Primary CPICH Ec/No* IE or does not include either of these IEs, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+If more than one DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to “selected” [TDD – or no DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to “selected”] the DRNC shall reject the Radio Link Setup procedure and shall respond with a RADIO LINK SETUP FAILURE message.
+
+[FDD – If only the *Initial DL TX Power* IE or the *Uplink SIR Target* IE is included in the RADIO LINK SETUP REQUEST message, then DRNC shall reject the Radio Link Setup procedure and shall respond with the RADIO LINK SETUP FAILURE message.]
+
+If the RADIO LINK SETUP REQUEST message includes a *DCH Information* IE with multiple *DCH Specific Info* IEs, and if the DCHs in the *DCH Information* IE do not have the same *Transmission Time Interval* IE in the *Semi-static Transport Format Information* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Enhanced Primary CPICH Ec/No* IE, but not the *Primary CPICH Ec/No* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE [FDD – or in the *RL Specific E-DCH Information* IE] included in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to “Must” [FDD- or the RL is combined with an E-DCH RL previously listed in the RADIO LINK SETUP RESPONSE message in the DRNC], the DRNC shall reject the Radio Link Setup procedure and the DRNC shall respond with the RADIO LINK SETUP FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE nor *RL Specific E-DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to “May”, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to “Must Not”, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for the first RL and/or [FDD – in the *RL Specific E-DCH Information* IE in the *RL Information* IE for the first E-DCH RL][TDD – in the *E-DCH MAC-d Flows Information TDD* IE], the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for an HS-DSCH MAC-d Flow in the *HS-DSCH MAC-d Flows Information* IE, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
+
+[TDD – If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for a DSCH in the *DSCH TDD Information* IE and/or for an USCH in the *USCH Information* IE, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.]
+
+If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE or the *Binding ID* IE, and not both are present for a transport bearer intended to be established, the DRNC shall reject the Radio Link Setup procedure and the DRNC shall respond with the RADIO LINK SETUP FAILURE message.
+
+If the RADIO LINK SETUP REQUEST message includes an *HS-PDSCH RL-ID* IE not referring to one of the radio links to be established, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+If the RADIO LINK SETUP REQUEST message contains the *HS-DSCH Information* IE and if the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE has the value “Indexed MAC-d PDU Size”, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+If the RADIO LINK SETUP REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE has the value “Flexible MAC-d PDU Size”, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[TDD – If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE is not present, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *F-DPCH Information* IE and the *DL DPCH Information* IE, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *E-DCH RL Indication* IE set to “E-DCH”, but does not contain the *E-DCH FDD Information* IE, or if the message contains the *E-DCH FDD Information* IE, but does not contain the *E-DCH RL Indication* IE set to “E-DCH”, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+If the RADIO LINK SETUP REQUEST message contains the *HS-PDSCH RL ID* IE and the *Serving E-DCH RL* IE but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not configured to be in the same cell then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *HS-PDSCH RL ID* IE and the *E-DPCH Information* IE which includes the *HS-DSCH Configured Indicator* IE set as “HS-DSCH not configured” then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *E-DPCH Information* IE but does not contain the *UL DPDCH Indicator for E-DCH operation* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Serving Cell Change CFN* IE, but neither the *Serving E-DCH RL* IE nor *HS-DSCH Information* IE is included, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Transport Bearer Not Requested Indicator* IE for a DCH, but does not contain the *Unidirectional DCH indicator* IE set to “Uplink DCH only” in the *DCH Specific Info* IE for the DCH, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Synchronisation Indicator* IE for a RL, but does not contain the *D-RNTI* IE which already has the RL, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the *UL DPCH Information* IE in the RADIO LINK SETUP REQUEST message contains the *UL DPCH Slot Format* set to “4” but does not contain the *F-DPCH Information* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the *UL DPCH Information* IE in the RADIO LINK SETUP REQUEST message contains the *UL DPCH Slot Format* set to “0” or “2” and the *Continuous Packet Connectivity DTX-DRX Information* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the *UL DPCH Information* IE in the RADIO LINK SETUP REQUEST message contains *Diversity Mode* IE set to “Closed loop mode 1” and *UL DPCH Slot Format* not set to “2” or “3”, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *MIMO Activation Indicator* IE, *Sixtyfour QAM Usage Allowed Indicator* IE set to “Allowed”, the *Additional HS Cell Information RL Setup* IE, the *MIMO with four transmit antennas Activation Indicator* IE, the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE and/or the *Single Stream MIMO Activation Indicator* IE, but does not contain the *HS-DSCH MAC-d PDU Size Format* IE set to “Flexible MAC-d PDU Size”, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Continuous Packet Connectivity DTX-DRX Information* IE but does not contain the *F-DPCH Information* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Serving E-DCH RL ID* IE but contains the *Transport Bearer Not Requested Indicator* IE in the RL Specific E-DCH Information for the new Serving E-DCH RL, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with RL which the transport bearer is configured to be established for the DCH or the E-DCH MAC-d Flow, previously listed in the RADIO LINK SETUP RESPONSE message in the DRNS, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE indicating a secondary serving cell that is not in the same Node B as the new serving HS-DSCH cell, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE and if the *HS-DSCH Information* IE is not present, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+If the RADIO LINK SETUP REQUEST message includes the *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE set to “Flexible RLC PDU Size”, and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE has the value “Indexed MAC-d PDU Size”, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+If the RADIO LINK SETUP REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, and the *DL RLC PDU Size Format* IE in the *HS-DSCH Information* IE has the value “Flexible RLC PDU Size”, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Setup* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and if the *E-DPCH Information* IE is not present, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d*
+
+*Flows Information* IE in the *E-DCH FDD Information* IE is not present, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD – If the RADIO LINK SETUP REQUEST message contains in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Setup* IE the *Diversity Mode* IE not set to “None” but not the *Transmit Diversity Indicator* or contains the *Transmit Diversity Indicator* but not the *Diversity Mode* IE not set to “None”, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE containing more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are received in the *Ordinal Number Of Frequency* IE in the in the *HS-DSCH FDD Secondary Serving Information* IE, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE containing more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value “1”, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message contains the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message with the cause value “Invalid CM settings”.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message contains the *UL CLTD Information* IE but does not contain the *F-TPICH Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL CLTD Information* IE but without *F-TPICH Information* IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message contains the *UL MIMO Information* IE in *E-DCH FDD Information* IE but does not contain the *UL CLTD Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL MIMO Information* IE but without *UL CLTD Information* IE, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD - If the RADIO LINK SETUP REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+## 8.3.2 Radio Link Addition
+
+### 8.3.2.1 General
+
+This procedure is used for establishing the necessary resources in the DRNS for one [FDD – or more] additional RLs towards a UE when there is already at least one RL established to the concerned UE via this DRNS.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Radio Link Addition procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+[TDD – The Radio Link Addition procedure serves to establish a new Radio Link with the DSCH and USCH included, if they existed before.]
+
+### 8.3.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: Initiate Radio Link Addition
+ SRNC->>DRNC: RADIO LINK ADDITION REQUEST
+ Note right of DRNC: Process Request
+ DRNC-->>SRNC: RADIO LINK ADDITION RESPONSE
+ Note left of SRNC: Success
+
+```
+
+Sequence diagram showing the Radio Link Addition procedure: Successful Operation. The diagram shows two vertical lifelines, SRNC on the left and DRNC on the right. A horizontal arrow labeled 'RADIO LINK ADDITION REQUEST' points from SRNC to DRNC. A return horizontal arrow labeled 'RADIO LINK ADDITION RESPONSE' points from DRNC back to SRNC.
+
+**Figure 7: Radio Link Addition procedure: Successful Operation**
+
+The procedure is initiated with a RADIO LINK ADDITION REQUEST message sent from the SRNC to the DRNC.
+
+Upon receipt, the DRNS shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
+
+The DRNS shall prioritise resource allocation for the RL(s) to be established according to Annex A.
+
+If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK ADDITION REQUEST message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
+
+#### Transport Channel Handling:
+
+[3.84 Mcps TDD – The DRNC shall include the *UL/DL DPCH Information* IE within the *UL/DL CCTrCH Information* IE for each CCTrCH that requires DPCHs.]
+
+[1.28 Mcps TDD – The DRNC shall include the *UL/DL DPCH Information LCR* IE within the *UL/DL CCTrCH Information LCR* IE for each CCTrCH that requires DPCHs.]
+
+[7.68 Mcps TDD – The DRNC shall include the *UL/DL DPCH Information 7.68 Mcps* IE within the *UL/DL CCTrCH Information 7.68 Mcps* IE for each CCTrCH that requires DPCHs.]
+
+#### [TDD – DSCH:]
+
+[3.84 Mcps TDD – If the radio link to be added includes a DSCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a *DSCH Information Response* IE for each DSCH.]
+
+[1.28 Mcps TDD – If the radio link to be added includes a DSCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a *DSCH Information Response LCR* IE for each DSCH.]
+
+[7.68 Mcps TDD – If the radio link to be added includes a DSCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a *DSCH Information Response 7.68 Mcps* IE for each DSCH.]
+
+#### [TDD – USCH:]
+
+[3.84 Mcps TDD – If the radio link to be added includes any USCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a *USCH Information Response* IE for each USCH.]
+
+[1.28 Mcps TDD – If the radio link to be added includes any USCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a *USCH Information Response LCR* IE for each USCH.]
+
+[7.68 Mcps TDD – If the radio link to be added includes any USCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a *USCH Information Response 7.68 Mcps* IE for each USCH.]
+
+#### Physical Channels Handling:
+
+##### [FDD –Compressed Mode:]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Active Pattern Sequence Information* IE, the DRNS shall use the information to activate the indicated (all ongoing) Transmission Gap Pattern Sequence(s) in the new RL. The received *CM Configuration Change CFN* IE refers to the latest passed CFN with that value. The DRNS shall treat the received *TGCFN* IEs as follows:]
+
+- [FDD – If any received *TGCFN* IE has the same value as the received *CM Configuration Change CFN* IE, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
+- [FDD – If any received *TGCFN* IE does not have the same value as the received *CM Configuration Change CFN* IE but the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE has already passed, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
+- [FDD – For all other Transmission Gap Pattern Sequences included in the *Active Pattern Sequence Information* IE, the DRNS shall activate each Transmission Gap Pattern Sequence at the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE for the Transmission Gap Pattern Sequence.]
+
+[FDD – If the *RADIO LINK ADDITION REQUEST* message includes the *Active Pattern Sequence Information* IE and the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the downlink compressed mode method information, if existing, for the concerned Transmission Gap Pattern Sequence(s) in the Compressed Mode Configuration.]
+
+[FDD – If the *Active Pattern Sequence Information* IE is not included, the DRNS shall not activate the ongoing compressed mode pattern in the new RLs, but the ongoing pattern in the existing RL shall be maintained.]
+
+[FDD – If some Transmission Gap Pattern sequences using SF/2 method are initialised in the DRNS and the UE Context is configured to use DPCH in the downlink, the DRNC shall include the *Transmission Gap Pattern Sequence Scrambling Code Information* IE in the *DL Code Information* IE in the *RADIO LINK ADDITION RESPONSE* message to indicate the Scrambling code change method that it selects for each channelisation code.]
+
+[FDD - If the *RADIO LINK ADDITION REQUEST* message includes the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]
+
+#### **[FDD – DL Code Information:]**
+
+[FDD – When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.211 [8]. When *p* number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to “*PhCH number 1*”, the second to “*PhCH number 2*”, and so on until the *p*th to “*PhCH number p*”.]
+
+#### **[TDD – CCTrCH Handling:]**
+
+[TDD – If the *UL CCTrCH Information* IE is present, the DRNS shall configure the new UL CCTrCH(s) according to the parameters given in the message.]
+
+[1.28Mcps TDD – If the *UL CCTrCH Information* IE includes the *TDD TPC Uplink Step Size* IE, the DRNS shall configure the uplink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.]
+
+[TDD – If the *DL CCTrCH Information* IE is present, the DRNS shall configure the new DL CCTrCH(s) according to the parameters given in the message.]
+
+[TDD – If the *DL CCTrCH Information* IE includes the *TDD TPC Downlink Step Size* IE, the DRNS shall configure the downlink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.]
+
+#### **[FDD - UL CLTD Handling:]**
+
+[FDD - If the *UL CLTD Information* IE is present in the *RADIO LINK ADDITION REQUEST* message, then the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights and then :]
+
+- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.]
+- [FDD - If there is a HS-DSCH RL configuration in the concerned UE Context, the *UL CLTD Activation Information* IE shall be included in the *UL CLTD Information* IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]
+
+#### [FDD – UL MIMO Setup]:
+
+[FDD - If the *UL MIMO Information* IE is present in the RADIO LINK ADDITION REQUEST message, then the DRNS shall setup the requested UL MIMO operation.]
+
+#### General:
+
+[FDD – The DRNS shall use the provided Uplink SIR Target value as the current target for the inner-loop power control.]
+
+### Radio Link Handling:
+
+#### Diversity Combination Control:
+
+The *Diversity Control Field* IE indicates for each RL whether the DRNS shall combine the new RL with existing RL(s) or not on the Iur.
+
+- If the *Diversity Control Field* IE is set to “May” (be combined with another RL), the DRNS shall decide for any of the alternatives.
+- If the *Diversity Control Field* IE is set to “Must”, the DRNS shall combine the RL with one of the other RL. When a new RL is to be combined the DRNS shall choose which RL(s) to combine it with.
+- If the *Diversity Control Field* IE is set to “Must not”, the DRNS shall not combine the RL with any other existing RL.
+
+[FDD – The *Diversity Control Field* IE is only applicable for DCHs, in case of E-DCH it shall always be assumed to be set to “May”.]
+
+In the case of not combining a RL with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or a RL previously listed in the RADIO LINK ADDITION RESPONSE message, the DRNC shall indicate with the Diversity Indication in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message that no combining is done. In this case the DRNC shall:
+
+- include in the *DCH Information Response* IE both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each DCH of the RL in the RADIO LINK ADDITION RESPONSE message [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included].
+- [FDD – include in the RADIO LINK ADDITION RESPONSE the *Transport Bearer Not Setup Indicator* IE for every DCH or set of co-ordinated DCHs for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK ADDITION REQUEST message.]
+
+[FDD – In case of not combining E-DCH, the *E-DCH FDD Information Response* IE shall be included in the RADIO LINK ADDITION RESPONSE message containing the *Binding ID* IE and the *Transport Layer Address* IE for the establishment of transport bearers for every E-DCH MAC-d flow being established for which the *Transport Bearer Not Requested Indicator* IE was not included.]
+
+[FDD – In case of not combining E-DCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE the *Transport Bearer Not Setup Indicator* IE for every E-DCH MAC-d flow for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK ADDITION REQUEST message.]
+
+In the case of combining with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, the DRNC
+
+shall indicate with the Diversity Indication in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message that the RL is combined. In this case, the *RL ID* IE indicates (one of) the previously established RL(s) or a RL previously listed in this RADIO LINK ADDITION RESPONSE message with which the new RL is combined and if the ALCAP is not used [FDD – and the transport bearer for this DCH is already established], the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE included in the *RL Information* IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used.
+
+[FDD – In the case of combining with an E-DCH RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, one of the previously established RLs or a RL previously listed in this RADIO LINK ADDITION RESPONSE message including the *E-DCH FDD Information Response* IE and part of the same Radio Link Set shall be regarded as the RL with which the concerned E-DCH RL is combined and if the ALCAP is not used, the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific E-DCH Information* IE included in the *RL Information* IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used. In case E-DCH RL is established for the first time, the DRNC shall include *E-DCH FDD Information Response* IE instead of using the Diversity Indication of DCH RL in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message. It shall include in the *E-DCH FDD Information Response* IE the *Binding ID* IE and *Transport Layer Address* IE for the transport bearers to be established for each E-DCH MAC-d flow of this E-DCH RL for which the *Transport Bearer Not Requested Indicator* IE was not included.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Additional E-DCH Cell Information RL Add Req* IE, then:]
+
+- - [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “Separate Iur Transport Bearer Mode” the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+- - [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “UL Flow Multiplexing Mode” the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
+- - [FDD – if Separate Iur Transport Bearer Mode is used in the new configuration, then:]
+ - - [FDD – the DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the *Transport Bearer Not Requested Indicator* IE in the *RL Specific E-DCH Information* IE in the *RL Information* IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.]
+ - - [FDD – If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE or in the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH Cell Information Addition* IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MAC-d flow the DRNS shall, for establishment of the transport bearer, include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE for establishment of the transport bearer.]
+
+[TDD – The DRNC shall always include in the RADIO LINK ADDITION RESPONSE message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each DSCH and USCH of the RL.]
+
+In the case of a set of co-ordinated DCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and the *Transport Layer Address* IE for only one of the DCHs in the set of co-ordinated DCHs [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included].
+
+If the DRNS needs to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Allowed UL Rate* IE in the *DCH Information Response* IE for this Radio Link.
+
+If the DRNS needs to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Allowed DL Rate* IE in the *DCH Information Response* IE for this Radio Link.
+
+#### **[FDD – Transmit Diversity:]**
+
+[FDD – The DRNS shall activate any feedback mode diversity according to the received settings.]
+
+[FDD – If the cell in which the RL is being added is capable to provide Close loop Tx diversity, the DRNC shall indicate the Closed loop timing adjustment mode of the cell by including the *Closed Loop Timing Adjustment Mode* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+[FDD – When the *Transmit Diversity Indicator* IE and/or *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE is present the DRNS shall activate/deactivate the Transmit Diversity for each new Radio Link and/or secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE and/or *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE using the diversity mode of the existing Radio Link(s) and/or existing secondary serving HS-DSCH Radio Link.]
+
+#### **DL Power Control:**
+
+[FDD – If the *Primary CPICH Ec/No* IE or the *Primary CPICH Ec/No* IE and the *Enhanced Primary CPICH Ec/No* IE measured by the UE are included for an RL in the RADIO LINK ADDITION REQUEST message, the DRNS shall use this in the calculation of the Initial DL TX Power for this RL. If the *Primary CPICH Ec/No* IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]
+
+[TDD – If [3.84Mcps TDD and 7.68 Mcps TDD – the *DL Time Slot ISCP Info* IE] [1.28Mcps TDD – the *DL Time Slot ISCP Info LCR* IE] is included in the RADIO LINK ADDITION REQUEST message, the DRNS shall use it in the calculation of the Initial DL TX Power.]
+
+[TDD – If the *Primary CCPCH RSCP Delta* IE is included, the DRNS shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP Delta* IE. If the *Primary CCPCH RSCP Delta* IE is not included and the *Primary CCPCH RSCP* IE is included, the DRNS shall assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP* IE. The DRNS shall use it in the calculation of the Initial DL TX Power.]
+
+[TDD – If the *Primary CCPCH RSCP* IE, *Primary CCPCH RSCP Delta* IE, [3.84Mcps TDD and 7.68 Mcps TDD – and the *DL Time Slot ISCP Info* IE] [1.28Mcps TDD – and the *DL Time Slot ISCP Info LCR* IE] are not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CCPCH power used by the existing RL.]
+
+[FDD – The Initial DL TX Power shall be applied until UL synchronisation is achieved on the Uu interface for that RLS or Power Balancing is activated. No inner loop power control or power balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.214 [10] subclause 5.2.1.2) and the power control procedure (see 8.3.7).]
+
+[TDD – The Initial DL TX Power shall be applied until UL synchronisation is achieved on the Uu interface for that RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.224 [22] subclause 4.2.3.3).]
+
+[3.84 Mcps TDD and 7.68 Mcps TDD – The DL TX power upper and lower limit is configured in the following way: The DRNC shall include the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the RADIO LINK ADDITION RESPONSE message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the value(s) for that CCTrCH in the *CCTrCH Maximum DL TX Power* IE and *CCTrCH Minimum DL TX Power*. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power* IE/*CCTrCH Maximum DL TX*
+
+*Power IE* or lower than indicated by the appropriate *Minimum DL TX Power IE/CCTrCH Minimum DL TX Power IE* on any DL DPCH within each CCTrCH of the RL.]
+
+[1.28 Mcps TDD – The DL TX power upper and lower limit is configured in the following way: The DRNC shall include the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* in the RADIO LINK ADDITION RESPONSE message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the value(s) for that timeslot in the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* within the *DL Timeslot Information LCR IE*. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power IE* or lower than indicated by the appropriate *Minimum DL TX Power IE* on any DL DPCH within each timeslot of the RL.]
+
+[FDD – If the *DPC Mode IE* is present in the RADIO LINK ADDITION REQUEST message, the DRNC shall apply the DPC mode indicated in the message, and be prepared that the DPC mode may be changed during the lifetime of the RL. If the *DPC Mode IE* is not present in the RADIO LINK ADDITION REQUEST message, DPC mode 0 shall be applied (see TS 25.214 [10]).]
+
+The DRNC shall provide the configured *Maximum DL TX Power IE* and *Minimum DL TX Power IE* for every new RL to the SRNC in the RADIO LINK ADDITION RESPONSE message. The DRNS shall not transmit with a power higher than indicated by the *Maximum DL TX Power IE* or lower than indicated by the *Minimum DL TX Power IE* on any DL DPCH [FDD – or on the F-DPCH] of the RL [FDD – except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the $\delta P_{curr}$ , as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
+
+[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Individual” in the existing RL(s) and the RADIO LINK ADDITION REQUEST message includes the *DL Reference Power IE*, the DRNS shall activate the power balancing and use the *DL Reference Power IE* for the power balancing procedure in the new RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported by the DRNS, according to subclause 8.3.15. In this case, the DRNC shall include the *DL Power Balancing Activation Indicator IE* in the *RL Information Response IE* in the RADIO LINK ADDITION RESPONSE message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{init}$ shall be set to the power level which is calculated based on the *Primary CPICH Ec/No IE* or the *Enhanced Primary CPICH Ec/No IE* (if received), or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing RLs.]
+
+#### UL Power Control:
+
+The DRNC shall also provide the configured UL Maximum SIR and UL Minimum SIR for every new RL to the SRNC in the RADIO LINK ADDITION RESPONSE message. These values are taken into consideration by DRNS admission control and shall be used by the SRNC as limits for the UL inner-loop power control target.
+
+#### Neighbouring Cell Handling:
+
+If there are UMTS neighbouring cell(s) to the cell in which a Radio Link was established then:
+
+- The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Neighbouring FDD Cell Information IE* and/or *Neighbouring TDD Cell Information IE* in the *Neighbouring UMTS Cell Information IE* for each neighbouring FDD cell and/or TDD cell respectively. In addition, if the information is available, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Frame Offset IE*, *Primary CPICH Power IE*, *Cell Individual Offset IE*, *STTD Support Indicator IE*, *Closed Loop Model Support Indicator IE*, *Coverage Indicator IE*, *Antenna Co-location Indicator IE* and *HCS Prio IE* in the *Neighbouring FDD Cell Information IE*, and the *Frame Offset IE*, *Cell Individual Offset IE*, *DPCH Constant Value IE* and the *PCCPCH Power IE*, *Coverage Indicator IE*, *Antenna Co-location Indicator IE* and *HCS Prio IE* in the *Neighbouring TDD Cell Information IE* or the *Neighbouring TDD Cell Information LCR IE*. If the *Neighbouring TDD Cell Information IE* includes the *Sync Case IE* set to “Case1”, the DRNC shall include the *Time SlotFor SCH IE* in the *Neighbouring TDD Cell Information IE*. If the *Neighbouring TDD Cell Information IE* includes the *Sync Case IE* set to “Case2”, the DRNC shall include the *SCH Time Slot IE* in the *Neighbouring TDD Cell Information IE*.
+- If a UMTS neighbouring cell is not controlled by the same DRNC, the DRNC shall also include in the RADIO LINK ADDITION RESPONSE message the *CN PS Domain Identifier IE*
+
+and/or *CN CS Domain Identifier* IE which are the identifiers of the CN nodes connected to the RNC controlling the UMTS neighbouring cell.
+
+- - [FDD – The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *DPC Mode Change Support Indicator* IE for each neighbour cell in the *Neighbouring FDD Cell Information* IE if this information is available.]
+- - The DRNC shall include the *Cell Capability Container FDD* IE, the *Cell Capability Container TDD* IE, *Cell Capability Container 7.68Mcps TDD* IE, the *Cell Capability Container TDD LCR* IE and/or the *Cell Capability Container Extension FDD* IE if the DRNC is aware that the neighbouring cell supports any functionality listed in 9.2.2.D, 9.2.3.1a, 9.2.3.1b and 9.2.2.123.
+- - [FDD – The DRNC shall, if supported, include the *Cell List Validity Indicator* IE if the neighbouring cell is multi cell capable and/or dual band capable but the cell can not be the serving HS-DSCH in a multicell and/or dual band configuration. Hence the cell can only serve as the secondary serving HS-DSCH cell. When *Cell List Validity Indicator* IE is included the SRNC should ignore the indicated cell list(s).]
+- - [FDD – For each cell in the *Secondary Serving Cell List* IE that is Multi Cell E-DCH capable, indicated in the *Cell Capability Container Extension FDD* IE by the "Multi Cell E-DCH Support Indicator" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the cell identified by the *C-ID* IE as the corresponding cell of the Primary uplink frequency, the DRNS shall, if supported, include the *Multicell E-DCH Restriction* IE set to "TRUE".]
+- - For the UMTS neighbouring cells which are controlled by the DRNC, the DRNC shall report in the RADIO LINK ADDITION RESPONSE message the restriction state of those cells, otherwise *Restriction State Indicator* IE may be absent. The DRNC shall include the *Restriction State Indicator* IE for the neighbouring cells which are controlled by the DRNC in the *Neighbouring FDD Cell Information* IE, the *Neighbouring TDD Cell Information* IE and the *Neighbouring TDD Cell Information LCR* IE.
+- - If available, the DRNC shall include the *SNA Information* IE for the concerned neighbouring cells in the *Neighbouring FDD Cell Information* IE, the *Neighbouring TDD Cell Information* IE and the *Neighbouring TDD Cell Information LCR* IE.
+- - If MOCN or GWCN network sharing configuration is used then the DRNC shall include the broadcasted PLMN identities of concerned neighbouring cells in the *Multiple PLMN List* IE in the *Neighbouring FDD Cell Information* IE, the *Neighbouring TDD Cell Information* IE and the *Neighbouring TDD Cell Information LCR* IE.
+- - If available, the DRNC shall include the *Frequency Band Indicator* IE for the concerned neighbouring cells in the *Neighbouring FDD Cell Information* IE.
+- - If the number of neighbouring UMTS RNCs is beyond the predefined maximum number, the DRNC shall, if supported, include the remaining neighbouring information in the *Neighbouring UMTS Cell Information Extension* IE. The IE filling rules in the *Neighbouring UMTS Cell Information* shall also apply to the *Neighbouring UMTS Cell Information Extension* IE.
+
+If there are GSM neighbouring cells to the cell(s) in which a radio link is established, the DRNC shall include the *Neighbouring GSM Cell Information* IE in the RADIO LINK ADDITION RESPONSE message for each of the GSM neighbouring cells. If available the DRNC shall include the *Cell Individual Offset* IE, and if the *Cell Individual Offset* IE alone cannot represent the value of the offset, the DRNC shall also include the *Extended GSM Cell Individual Offset* IE in the *Neighbouring GSM Cell Information* IE. If available the DRNC shall also include the *Coverage Indicator* IE, *Antenna Co-location Indicator* IE and *HCS Prio* IE in the *Neighbouring GSM Cell Information* IE. If available, the DRNC shall also include the *SNA Information* IE for the concerned neighbouring cells in the *Neighbouring GSM Cell Information* IE. If network sharing configuration is used then the DRNC may include the broadcasted PLMN identities of the concerned neighbouring cells in the *PLMN List* IE in the *Neighbouring GSM Cell Information* IE.
+
+When receiving the *SNA Information* IE in the RADIO LINK ADDITION RESPONSE message, the SRNC should use it to restrict cell access based on SNA information. See also TS 25.401 [40] for a broader description of the SNA access control.
+
+If there are GERAN neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include the *GERAN Cell Capability* IE in the *Neighbouring GSM Cell Information* IE that is included in the RADIO LINK ADDITION RESPONSE message for each of the GERAN cells.
+
+If there are GERAN Iu-mode neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include, if available, the *GERAN Classmark* IE in the *Neighbouring GSM Cell Information* IE that is included in the RADIO LINK ADDITION RESPONSE message for each of the GERAN Iu-mode neighbouring cells. TS 43.051 [39] defines when the transmission of the *GERAN Classmark* IE will be required at the initiation of the Relocation Preparation procedure.
+
+If there are E-UTRA neighbouring cells to the cell(s) in which a radio link is established, the DRNC shall include the *Neighbouring E-UTRA Cell Information* IE in the RADIO LINK ADDITION RESPONSE message for each of the E-UTRA neighbouring cells, and may also include the *PCI* IE, *TAC* IE and *PLMN List* IE in the *Neighbouring E-UTRA Cell Information* IE in the RADIO LINK ADDITION RESPONSE message.
+
+#### **[1.28Mcps TDD – Uplink Synchronisation Parameters LCR:]**
+
+[1.28Mcps TDD – If the *Uplink Synchronisation Parameters LCR* IE is present, the DRNC shall use the indicated values of *Uplink synchronisation stepsize* IE and *Uplink synchronisation frequency* IE when evaluating the timing of the UL synchronisation.]
+
+#### **[1.28Mcps TDD – Shared physical channels Synchronisation Detection:]**
+
+[1.28Mcps TDD – If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall include the *Out-of-sync Detection Window* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### **[1.28Mcps TDD – Uplink Timing Advance Control LCR:]**
+
+[1.28Mcps TDD – The DRNC shall include the *Uplink Timing Advance Control LCR* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### **[1.28Mcps TDD – PowerControl GAP:]**
+
+[1.28Mcps TDD – If applied in the DRNS, the DRNC may include the *PowerControl GAP* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### **[1.28Mcps TDD – E-UTRAN Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *Idle Interval Configuration Indicator* IE, if supported, the DRNC shall include the *Idle Interval Information* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### **[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *DCH Measurement Type indicator* IE, if supported, the DRNS shall include the *Measurement purpose* IE and the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE in the RADIO LINK ADDITION RESPONSE message to configure the measurement occasion pattern(s) indicated by the *DCH Measurement Type indicator* IE.]
+
+#### **MBMS Handling:**
+
+If the UE Link is currently stored in the UE Context and an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in some of the cells identified by the *C-ID* IEs in the RADIO LINK ADDITION REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the *Active MBMS Bearer Service List* IE the *Transmission Mode* IE in the concerned *RL Information Response* IEs in the RADIO LINK ADDITION RESPONSE message.
+
+If the UE Link is currently stored in the UE Context and an MBMS preferred frequency layer for some active MBMS bearer services contained in the UE Link is set in some of the cells identified by the *C-ID* IEs in the RADIO LINK ADDITION REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the *Active MBMS Bearer Service List* IE the *Preferred Frequency Layer* IE in the concerned *RL Information Response* IEs in the RADIO LINK ADDITION RESPONSE message.
+
+### [FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE for a Radio Link not indicated by the *HS-PDSCH RL ID* IE in the *HS-DSCH Serving Cell Change Information* IE the DRNS shall, if supported, preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [63]:]
+
+- - [FDD – The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK ADDITION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of *Secondary C-ID* IEs in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK ADDITION REQUEST message. ]
+- - [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ]
+ - - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell.]
+ - - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells.]
+- - [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ]
+- - [FDD – The DRNS shall return these codes in the *Sets of HS-SCCH Codes* IE along with the corresponding per-cell *HS-DSCH-RNTI* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message. ]
+- - [FDD – The DRNS shall use the first in the numbered list the primary serving HS-DSCH cell's of HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the SRNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [16]].
+- - [FDD – The DRNS shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:]
+ - - [FDD – if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *HARQ Preamble Mode Activation Indicator* IE.]
+ - - [FDD – if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the Pilot Configuration and MIMO N/M Ratio in *MIMO Information Response* IE.]
+ - - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE]
+ - - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the Pilot Configuration and MIMO N/M Ratio in *MIMO Information Response* IE]
+ - - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the Pilot Configuration and MIMO N/M Ratio in *MIMO Information Response* IE]
+ - - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE]
+ - - [FDD – if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to “Flexible MAC-d PDU Size” and if Sixtyfour QAM will not
+
+be used for the cell in the preconfiguration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell.]
+
+- - [FDD – if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell.]
+- - [FDD – if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE.]
+- - [FDD – if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS shall store this information in the preconfigured configuration.]
+- - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH Preconfiguration Info* IE in the RADIO LINK ADDITION RESPONSE message.]
+- - [FDD – the *SixtyfourQAM DL Support Indicator* IE may be included.]
+- - [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS may store this information in the preconfigured configuration.]
+- - [FDD – the DRNS shall, if supported, include in the *Sets of HS-SCCH Codes* IE the *Measurement Power Offset* IE for each preconfigured cell.]
+- - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where HS-DSCH / secondary HS-DSCH is preconfigured, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH Preconfiguration Info* IE or in the *Sets of HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Info* IE for each preconfigured cell in the RADIO LINK ADDITION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the DRNC shall allocate resources for the preconfigured Multiflow.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the DRNC shall allocate resources for the preconfigured F-TPICH channel and include *F-TPICH Information Response* IE in the *HS-DSCH Preconfiguration Info* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the DRNC shall allocate resources for the preconfigured UL CLTD.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the DRNC shall allocate resources for the preconfigured UL MIMO.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixteen QAM.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixtyfour QAM.]
+
+[FDD – The DRNS shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
+
+- [FDD – The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information IE*.]
+- [FDD – The DRNS may preconfigure the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information IE*.]
+
+[FDD – If the *HS-DSCH Preconfiguration Setup IE* includes the *E-DCH Indicator IE* for a secondary cell, the DRNS shall include in the *Additional E-DCH Preconfiguration Information IE* in the *HS-DSCH Preconfiguration Info IE* in the *RL Information Response IE* in the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response IE* of the RADIO LINK ADDITION FAILURE message the *E-DCH FDD DL Control Channel Information IE* containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the *E-DCH Indicator IE*, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]
+
+- [FDD – The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding *E-AGCH in the E-DCH FDD DL Control Channel Information IE*. ]
+- [FDD – The DRNS may preconfigure the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* for the initial grant for the serving Additional E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information IE*.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Non-Serving RL Preconfiguration Setup IE* in the *RL Information IE* and:]
+
+- [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A IE* and/or *New non-serving RL E-DCH FDD DL Control Channel Information B IE* in the *Non-Serving RL Preconfiguration Info IE* for the RL in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information C IE* in the *Non-Serving RL Preconfiguration Info IE* for the RL in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A IE*, the *New non-serving E-DCH FDD DL Control Channel Information B IE* and/or the *New non-serving E-DCH FDD DL Control Channel Information C IE* for the RL in the *Non-Serving RL Preconfiguration Info IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup IE* is included, the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A IE*, the *New non-serving RL E-DCH FDD DL Control Channel Information B IE* and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C IE* according to the choice of new Serving RL in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE* for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If the *F-TPICH Information IE* is included, the DRNC shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [8], and include *F-TPICH Information Response IE* in the *Non-Serving RL Preconfiguration Info IE*.]
+
+#### General:
+
+If the RADIO LINK ADDITION REQUEST message includes the *RL Specific DCH Information IE*, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD – for which the *Transport Bearer Not Requested Indicator IE* was not included].
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer shall not be Established” for a DCH, then the DRNC shall not establish a transport bearer for the concerned DCH and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer may not be Established” for a DCH and:]
+
+- - [FDD – if the DRNC establishes a transport bearer for the concerned DCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH being established.]
+- - [FDD – if the DRNC does not establish a transport bearer for the concerned DCH, the DRNC shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]
+
+Depending on local configuration in the DRNS, the DRNC may include in the RADIO LINK ADDITION RESPONSE message the *UTRAN Access Point Position* IE and the geographical co-ordinates of the cell, represented either by the *Cell GAI* IE or by the *Cell GA Additional Shapes* IE. If the DRNC includes the *Cell GA Additional Shapes* IE in the RADIO LINK ADDITION RESPONSE message, it shall also include the *Cell GAI* IE.
+
+For each Radio Link established in a cell in which at least one URA Identity is being broadcast, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a URA Information for this cell including the *URA ID* IE, the *Multiple URAs Indicator* IE indicating whether or not multiple URA Identities are being broadcast in the cell, and the *RNC-ID* IEs of all other RNCs that have at least one cell within the URA identified by the *URA ID* IE.
+
+[3.84Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD* IE in the RADIO LINK ADDITION RESPONSE message if at least one *DSCH Information Response* IE or *USCH Information Response* IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the *Secondary CCPCH Info TDD* IE in the RADIO LINK ADDITION RESPONSE message if at least one *DSCH Information Response* IE or *USCH Information Response* IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[1.28 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK ADDITION RESPONSE message if at least one *DSCH Information Response LCR* IE or *USCH Information Response LCR* IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK ADDITION RESPONSE message if at least one *DSCH Information Response LCR* IE or *USCH Information Response LCR* IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[7.68 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info 7.68 Mcps TDD* IE in the RADIO LINK ADDITION RESPONSE message if at least one *DSCH Information Response 7.68 Mcps* IE or *USCH Information Response 7.68 Mcps* IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the *Secondary CCPCH Info 7.68 Mcps TDD* IE in the RADIO LINK ADDITION RESPONSE message if at least one *DSCH Information Response 7.68 Mcps* IE or *USCH Information Response 7.68 Mcps* IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+If the *Permanent NAS UE Identity* IE is present in the RADIO LINK ADDITION REQUEST message, the DRNS shall store the information for the considered UE Context for the lifetime of the UE Context.
+
+If the RADIO LINK ADDITION REQUEST message includes a *C-ID* IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is available in the DRNC for the considered UE Context, the DRNC shall use this information to determine whether it can add the Radio Link on this cell or not.
+
+If the HCS priority information is available in the DRNS, it shall include the *HCS Prio* IE for each of the established RLs in the RADIO LINK ADDITION RESPONSE message.
+
+The DRNS shall start receiving on the new RL(s) after the RLs are successfully established.
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Initial DL DPCH Timing Adjustment Allowed* IE, then the DRNS may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the DRNS shall include, for the concerned Radio Link(s), the *Initial DL DPCH Timing Adjustment* IE in the *Radio Link Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Synchronisation Indicator* IE, set to “Timing Maintained Synchronisation”, the DRNS shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10]. The DRNS shall select the TPC pattern as if “first RLS indicator” is set to “first RLS” according to subclause 5.1.2.2.1.2 in TS 25.214 [10].]
+
+[FDD – If the UE Context is configured for F-DPCH Slot Format operation, then the DRNS shall include the *F-DPCH Slot Format* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message includes the *F-TPICH Information* IE in the *RL Information* IE, the DRNS shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10], and shall include the *F-TPICH Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+**[FDD – Radio Link Set Handling:]**
+
+[FDD – For each RL not having a common generation of the TPC commands in the DL with another RL, the DRNS shall assign to the RL a unique value for the *RL Set ID* IE which uniquely identifies the RL as an RL Set within the UE Context. In case of E-DCH, the generation of E-HICH information for RLs in different RL Sets shall not be common.]
+
+[FDD – For all RLs having a common generation of the TPC commands in the DL with another new or existing RL, the DRNS shall assign to each RL the same value for the *RL Set ID* IE which uniquely identifies these RLs as members of the same RL Set within the UE Context. In case of E-DCH, the generation of E-HICH related information for all RLs in a RL Set shall be common.]
+
+[FDD – After addition of the new RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the previously existing and newly established RL Set(s), use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N\_INSYNC\_IND that are configured in the cells supporting the radio links of the RL Set.]
+
+[FDD – For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the *E-DCH RL Set ID* IE in the RADIO LINK ADDITION RESPONSE message. The value of the *E-DCH RL Set ID* IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
+
+**[FDD – Serving HS-DSCH Radio Link Change:]**
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Serving Cell Change Information* IE, then the *HS-PDSCH RL ID* IE indicates the new Serving HS-DSCH Radio Link:]
+
+- [FDD – In the new configuration the DRNS shall allocate the HS-PDSCH resources for the new Serving HS-PDSCH Radio Link.]
+- [FDD – The DRNS may include the *HARQ Memory Partitioning* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message. The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.]
+- [FDD – If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the *User Plane Congestion Fields Inclusion* IE in the *HS-DSCH Information Response* IE.]
+- [FDD – The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If a reset of the MAC-hs is not required the DRNS shall include the *MAC-hs Reset Indicator* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- [FDD – If the *HS-DSCH Serving Cell Change Information* IE includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:]
+ - - [FDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]
+ - - [FDD – The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+ - - [FDD – If at least one of *HS-PDSCH Second Code Support* IE is set to “True”, then the DRNC shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If the *HS-DSCH Serving Cell Change Information* IE includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:]
+ - - [FDD – The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]
+ - - [FDD – If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
+- [FDD - If the UE Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new configuration, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Information Response* IE in the *HS-DSCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+
+**[FDD – HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change:]**
+
+[FDD – If the *HS-DSCH Information* IE is present in the *HS-DSCH Serving Cell Change Information* IE, then:]
+
+- - [FDD – The DRNS shall setup the requested HS-PDSCH resources on the *Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID* IE.]
+- - [FDD – the *HS-DSCH Information* IE defines the new HS-DSCH configuration in the DRNS to be used on the new HS-DSCH Radio Link.]
+- - [FDD – The DRNC shall include the *HARQ Memory Partitioning* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message. The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.]
+
+- - [FDD – The DRNS may use the *Traffic Class* IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *HS-DSCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE. If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.]
+- - [FDD – The DRNC shall include the *HS-DSCH Initial Capacity Allocation* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK ADDITION REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer I in RADIO LINK ADDITION REQUEST in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the DRNC shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]).]
+- - [FDD – If the *MIMO Activation Indicator* IE, or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then ]
+ - - [FDD – The DRNS shall activate the MIMO mode, or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link.]
+ - - [FDD – The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO Information Response*
+
+IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+- - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE set to “Flexible MAC-d PDU Size” and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Information Response* IE in the *HS-DSCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- - [FDD – If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may use:]
+ - - [FDD – a different HS-SCCH in consecutive TTIs for this UE.]
+ - - [FDD – HS-SCCH orders for the case of HS-SCCH-less operation to this UE.]
+- - [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the DRNS may use the supported HSDPA functions for this UE.]
+ - - [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the D shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall, if supported, consider the data of the HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
+- - [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE in the *HS-DSCH Serving Cell Change Information* IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.]
+
+- [FDD – The DRNC may include the *Transport Layer Address* IE and the *Binding ID* IE for HS-DSCH MAC-d flow in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC. ]
+- [FDD – If the *Serving Cell Change CFN* IE is not included then the DRNS shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.]
+- [FDD – If the requested Serving HS-DSCH Radio Link Change was successful or unsuccessful, the DRNS shall indicate this in the *HS-DSCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNS may include the *Preoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the *HS-DSCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### **[FDD – Secondary Serving HS-DSCH Radio Link Change:]**
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Additional HS Cell Information RL Addition* IE, then the *HS-PDSCH RL ID* IE indicates the new Serving HS-DSCH Radio Link:]
+
+- [FDD – In the new configuration the DRNS shall allocate the HS-PDSCH resources for the new secondary serving HS-PDSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+- [FDD – The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD - If the UE Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new secondary serving HS-DSCH Radio Link, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Change Information Response* IE in the
+
+RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for the secondary serving HS-DSCH Transport Block Size signalling.]
+
+**[FDD – Secondary Serving HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change:]**
+
+- - [FDD – The DRNS shall setup the requested HS-PDSCH resources on the Secondary Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.]
+- - [FDD – The *HS-DSCH FDD Secondary Serving Information* IE defines the new secondary serving HS-DSCH configuration in the DRNS to be used on the new secondary serving HS-DSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- - [FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+- - [FDD – If the *MIMO Activation Indicator* IE, or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the MIMO mode, or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
+- - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+- - [FDD – If Sixtyfour QAM will not be used for the secondary serving cell, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION
+
+RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+
+- - [FDD – If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE in the RADIO LINK ADDITION REQUEST message the DRNS shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to “None” the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.]
+- [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the HS-PDSCH resources of the old secondary serving HS-PDSCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.]
+- [FDD – If the *Serving Cell Change CFN* IE is not included then the DRNS shall activate immediately the resources that are allocated for the new secondary serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous secondary serving HS-PDSCH Radio Link.]
+- [FDD – If the requested secondary serving HS-DSCH Radio Link Change was successful or unsuccessful, the DRNS shall indicate this in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### **[FDD - Multiflow Setup]:**
+
+[FDD - If the *Multiflow Information* IE is present in the RADIO LINK ADDITION REQUEST message, then the DRNS shall setup the requested Multiflow operation.]
+
+#### **[FDD – Additional Serving E-DCH Radio Link Change]:**
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Additional E-DCH Cell Information Addition* IE in the *Additional E-DCH Cell Information RL Add Req* IE and the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Addition* IE, the *HS-PDSCH RL ID* IE indicates the new Additional Serving E-DCH Radio Link:]
+
+- [FDD – In the new configuration the DRNS shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
+- [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.]
+- [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+- [FDD – The DRNS may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the DRNS Communication Context that have not been included in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE.]
+- [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.]
+- [FDD- If the *Serving Cell Change CFN* IE is not included then the DRNS shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link, and shall keep active the resources that are allocated for the previous additional serving E-DCH Radio Link.]
+- [FDD – If the addition of the requested Additional Serving E-DCH Radio Link was successful but the Additional Serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the *Additional E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+#### [FDD – E-DCH:]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE, then for every such RL.]
+
+- [FDD – The DRNS shall setup the E-DCH resources as configured in the UE context.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *RL specific E-DCH Information* IE for an E-DCH MAC-d flow, then if the *Transport Bearer Not Requested Indicator* IE is not included for this E-DCH MAC-d flow, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.]
+- [FDD – The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for every E-DCH MAC-d flow being established for which the *Transport Bearer Not Requested Indicator* IE was not included.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer Shall not be Established” for an E-DCH MAC-d flow, then the DRNC shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer may not be Established” for an E-DCH MAC-d flow and:
+ - - [FDD – if the DRNC establishes a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.]
+ - - [FDD – if the DRNC does not establish a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – The DRNC may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNC may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK ADDITION RESPONSE message, for every RL indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+- [FDD – If the DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK ADDITION RESPONSE message, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE, to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+
+**[FDD – Serving E-DCH Radio Link Change:]**
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Serving E-DCH RL* IE, this indicates the new Serving E-DCH Radio Link:]
+
+- [FDD – If the new Serving E-DCH RL is in this DRNS:]
+ - - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both and include these E-RNTI identifiers and the Channelisation Code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *E-DCH Serving Cell Change Information Response* IE for the indicated RL in the RADIO LINK ADDITION RESPONSE message.]
+ - - [FDD – The DRNS may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the new serving E-DCH RL.]
+ - - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+ - - [FDD – If a serving cell change is performed the RADIO LINK ADDITION RESPONSE message may contain invalid data (see 9.2.2.4C).]
+ - - [FDD – The DRNS may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK ADDITION RESPONSE message for the new serving E-DCH RL.]
+- [FDD – The DRNS may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Link in the DRNS Communication Context that have not been included in the *E-DCH FDD DL Control Channel Information* IE in *RL Information Response* IE.]
+- [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.]
+- [FDD- If the *Serving Cell Change CFN* IE is not included then the DRNS shall activate immediately the resources that are allocated for the new serving E-DCH Radio Link, and shall keep active the resources that are allocated for the previous serving E-DCH Radio Link.]
+- [FDD – If the addition of the requested Serving E-DCH Radio Link was successful but the Serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+**[FDD – E-DPCH Handling:]**
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes an *E-DPCH Information* IE it defines the new E-DPCH configuration in the DRNS to be used on the new E-DCH Radio Link and the DRNS shall use the new parameters for the related resource allocation operations.]
+
+[FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the DRNS shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the DRNS shall use the value “127” in the algorithm defined in TS 25.214 [10].]
+
+[FDD – If the *E-DPCH Information* IE includes the *E-TFCS Information* IE, the DRNS shall use the *E-TFCS Information* IE for the E-DCH when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration. If the *E-TFCS Information* IE contains the *E-DCH Minimum Set E-TFCI Validity Indicator* IE the DRNS shall ignore the value in *E-DCH Minimum Set E-TFCI* IE. If the *E-DCH Minimum Set E-TFCI validity indicator* IE is absent DRNS shall use the value for the related resource allocation operation.]
+
+[FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes an *E-DPCH Information* IE, which contains the *Minimum Reduced E-DPDCH Gain Factor* IE, then the DRNS shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ]
+
+#### **[FDD – E-DCH Setup on a new Radio Link:]**
+
+[FDD – If the *E-DCH FDD Information* IE is present in the RADIO LINK ADDITION REQUEST message then:]
+
+- [FDD – the *E-DCH FDD Information* IE defines the new E-DCH FDD configuration in the DRNS to be used on the new E-DCH Radio Link.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being “E-DCH Non-Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.]
+
+- [FDD – If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being “E-DCH Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
+- [FDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *E-DCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+- [FDD – If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Bundling Mode Indicator* IE for a E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to “Bundling” and the *E-TTI* IE is set to “2ms”, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Reference Power Offset* IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *SixteenQAM UL Operation Indicator* IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.]
+ - - [FDD – If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]
+
+#### [FDD – Additional E-DCH Setup:]
+
+[FDD – If the *Additional E-DCH Cell Information RL Add Req* IE is present in the RADIO LINK ADDITION REQUEST message and the choice of *Setup Or Addition Of E-DCH On Secondary UL Frequency* is “Setup”, then the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:]
+
+- [FDD – If the *C-ID* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *C-ID* IE indicates the cell in which the additional E-DCH shall be setup.]
+ - - [FDD – The DRNS shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.]
+- [FDD – If the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *E-DCH Additional RL ID* IE indicates the existing RL on which the Additional E-DCH shall be setup.]
+ - - [FDD – The DRNS shall setup the Additional E-DCH on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.]
+- [FDD – The DRNS shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – If the *UL SIR Target* IE in the *UL DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE and/or the *DL Power Balancing Information* IE and/or the *Minimum Reduced E-DPDCH Gain Factor* IE in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE are present, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Secondary UL Frequency Activation State* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
+- [FDD – If the *Initial DL Tx Power* IE, the *Primary CPICH Ec/No* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE, is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Enhanced Primary CPICH Ec/No* IE is included in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH Secondary RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- If the *F-DPCH Slot Format Support Request* IE in the *F-DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message. If the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE includes the *F-DPCH Slot Format* IE, the DRNS may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+- [FDD – If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Processing Overload Level* IE are present in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If activation of power balancing for the Additional E-DCH RL by the RADIO LINK ADDITION REQUEST message is supported by the DRNS, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message to a value that uniquely
+
+identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+
+- [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message and if DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+- [FDD – If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:]
+ - v) - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.]
+ - w) - [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.]
+ - x) - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant E-DCH FDD Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+ - y) - [FDD – If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC. If the *Serving Cell Change CFN* IE is not included then the DRNS shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link]
+- [FDD – If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used” in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE RADIO LINK ADDITION RESPONSE message.]
+- [FDD – If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Secondary CPICH Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message. If the DRNS doesn’t include the *Secondary CPICH Information* IE, it shall not include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used”.]
+
+### [FDD – Additional E-DCH RL Addition:]
+
+[FDD – If the *Additional E-DCH Cell Information RL Add Req* IE is present in the RADIO LINK ADDITION REQUEST message and the choice of *Setup Or Addition Of E-DCH On Secondary UL Frequency* is “Addition”, then the *Additional E-DCH Cell Information Addition* IE defines the new configuration and then:]
+
+- [FDD – The DRNS shall setup the requested E-DCH resources as requested, or as configured in the UE context, on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Add* IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – if the *Multicell E-DCH Information* IE is included and contains the *Minimum Reduced E-DPDCH Gain Factor* IE, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.]
+- [FDD – if the *Additional E-DCH FDD Information* IE is included and contains the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Processing Overload Level* IE, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.]
+- [FDD – If the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE is included in the *Additional E-DCH RL Specific Information To Add* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Individual” in the existing Additional E-DCH RL(s) and the RADIO LINK ADDITION REQUEST message includes the *DL Reference Power* IE in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Add* IE, the DRNS shall activate the power balancing and use the *DL Reference Power* IE for the power balancing procedure in the new Additional RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.15. In this case, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{init}$ shall be set to the power level which is calculated based on the following IEs in the *Additional E-DCH RL Specific Information To Add* IE (if received): *Primary CPICH Ec/No* IE or the *Enhanced Primary CPICH Ec/No* IE in the *Multicell E-DCH RL Specific Information* IE or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing Additional RLs.]
+- [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+- [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set the same value for the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+[FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Add* IE the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell*
+
+*Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message and if DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+
+- [FDD – If in the *Additional E-DCH RL Specific Information To Add* IE the *Primary CPICH Ec/No* IE or the *Primary CPICH Ec/No* IE and the *Enhanced Primary CPICH Ec/No* IE in the *Multicell E-DCH RL Specific Information* IE measured by the UE are included for an RL in the RADIO LINK ADDITION REQUEST message, the DRNS shall use this in the calculation of the Initial DL TX Power for this additional RL. If the *Primary CPICH Ec/No* IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]
+
+#### [TDD – HS-DSCH Setup:]
+
+[TDD – If the *HS-DSCH Information* IE is present in the RADIO LINK ADDITION REQUEST message, then:]
+
+- [TDD – The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.]
+- [TDD – The DRNC shall include the *HARQ Memory Partitioning* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]). ]
+- [TDD – The DRNS may use the *Traffic Class* IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *HS-DSCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+- [TDD – The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [TDD – The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *HS-DSCH Information* IE for an HS-DSCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNC shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].]
+- [TDD – The DRNC shall include the *HS-DSCH Initial Capacity Allocation* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d
+
+flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK ADDITION REQUEST message includes *HS-DSCH MAC-d PDU Size Format IE* in the *HS-DSCH Information IE* set to “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation IE* the values for the peer of *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE* to the values of the corresponding peer I in RADIO LINK ADDITION REQUEST in the *HS-DSCH MAC-d Flows Information IE* in the *HS-DSCH Information IE* for a Priority Queue including *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE*.]
+
+- [TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response IE*] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR IE*] in the *HS-DSCH TDD Information Response IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+[1.28 Mcps TDD – If the *MIMO Activation Indicator IE* is included in the *HS-DSCH TDD Information IE*, then, The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link. The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream IE* in the *HS-DSCH TDD Information Response IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+- [1.28 Mcps TDD – If the *UE TS0 Capability LCR IE* is included in the *HS-DSCH TDD Information IE*, then the DRNC may include the *TS0 HS-PDSCH Indication LCR IE* in the RADIO LINK ADDITION RESPONSE message if HS-PDSCH resources could be allocated on TS0 for the UE.]
+
+#### [TDD – Intra-Node B Serving HS-DSCH Radio Link Change:]
+
+[TDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-PDSCH RL ID IE*, this indicates the new Serving HS-DSCH Radio Link:]
+
+- [TDD – The DRNC shall include the *HARQ Memory Partitioning IE* in the *HS-DSCH TDD Information Response IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response IE*] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR IE*] [7.68Mcps TDD – *HS-SCCH Specific Information Response 7.68Mcps IE*] in the *HS-DSCH TDD Information Response IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+#### [TDD – E-DCH:]
+
+[3.84Mcps TDD, 1.28Mcps TDD and 7.68Mcps TDD – If the [3.84Mcps TDD – *E-DCH Information IE*][1.28Mcps TDD – *E-DCH Information 1.28Mcps IE*] [7.68Mcps TDD – *E-DCH Information 7.68Mcps IE*] is present in the RADIO LINK ADDITION REQUEST message:]
+
+- [TDD – The DRNS shall setup the requested E-DCH resources on the Radio Link indicated by the *E-DCH Serving RL IE*.]
+- [TDD – If the *TNL QoS IE* is included in the *E-DCH MAC-d Flows Information TDD IE* for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS IE* may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address IE* and *Binding ID IE* in the *E-DCH MAC-d Flows Information TDD IE* for an E-DCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List IE* for an E-DCH MAC-d flow in the *E-DCH MAC-d Flows Information TDD IE*, the DRNS shall use this information for the related resource allocation operation.]
+- [TDD – If in the RADIO LINK ADDITION REQUEST message the *E-DCH Grant Type IE* in the *E-DCH MAC-d Flows Information TDD IE* is set to “Non-scheduled” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants are configured for that E-DCH MAC-d flow.]
+- [TDD – If in the RADIO LINK ADDITION REQUEST message the *E-DCH Grant Type IE* in the *E-DCH MAC-d Flows Information TDD IE* is set to “Scheduled” the DRNS shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.]
+
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows Information TDD* IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions for the related queue.]
+- - [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *MAC-es Maximum Bit Rate LCR* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows Information TDD* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+- [3.84Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH TDD Maximum Bitrate* IE in the *E-DCH TDD Information* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE in the *E-DCH TDD Information LCR* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE in the *E-DCH TDD Information 7.68Mcps* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [3.84Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Processing Overload Level* IE in the *E-DCH TDD Information* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Processing Overload Level* IE in the *E-DCH TDD Information 7.68Mcps* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Processing Overload Level* IE in the *E-DCH TDD Information LCR* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [TDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B.]
+- [TDD – If the RADIO LINK ADDITION REQUEST message includes the [3.84Mcps TDD – *E-DCH TDD Information* IE][1.28Mcps TDD – *E-DCH TDD Information LCR* IE] in the *E-DCH MAC-d Flows Information TDD* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *Maximum Number of Retransmission for Scheduling Info LCR* IE and the *E-DCH Retransmission timer for Scheduling Info LCR* IE in the *E-DCH TDD Information LCR* IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
+- [3.84Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information TDD* IE in the *E-DCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [3.84Mcps TDD – The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the *E-DCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message.]
+
+- [1.28Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information LCR TDD IE* in the *E-DCH Information Response 1.28Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [1.28Mcps TDD – The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier, the E-AGCH(s) and E-HICH(s) assigned in the *E-DCH Information Response 1.28Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [7.68Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE* in the *E-DCH Information Response 7.68Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [7.68Mcps TDD – The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the *E-DCH Information Response 7.68Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+- [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *Multi-Carrier E-DCH Physical Layer Category LCR IE* in the *E-DCH TDD Information LCR IE*, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
+- [1.28Mcps TDD - If the *UE TS0 Capability LCR IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE* is not present and if the RADIO LINK ADDITION REQUEST message includes the *UE TS0 Capability LCR IE* in the *E-DCH TDD Information LCR IE*, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]
+
+### **[3.84Mcps TDD – Intra-Node B Serving E-DCH Radio Link Change:]**
+
+[3.84Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Serving RL IE*, this indicates the new Serving E-DCH Radio Link:]
+
+- [3.84Mcps TDD – The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response IE* in the *E-DCH Information Response IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+### **[1.28Mcps TDD – Intra-Node B Serving E-DCH Radio Link Change:]**
+
+[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Serving RL IE*, this indicates the new Serving E-DCH Radio Link:]
+
+- [1.28Mcps TDD – The DRNS shall allocate E-AGCH parameters and E-HICH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response IE* and the *E-HICH Specific Information Response IE* in the *E-DCH Information Response 1.28Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+### **[7.68Mcps TDD – Intra-Node B Serving E-DCH Radio Link Change:]**
+
+[7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Serving RL IE*, this indicates the new Serving E-DCH Radio Link:]
+
+- [7.68Mcps TDD – The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response 7.68Mcps TDD IE* in the *E-DCH Information Response 7.68Mcps IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+### **[1.28 Mcps TDD – Continuous Packet Connectivity Handling:]**
+
+[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Continuous Packet *Connectivity DRX Information LCR IE*, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR IE* in the RADIO LINK ADDITION RESPONSE message.]
+
+[1.28 Mcps TDD - If the *Inactivity Threshold for UE DRX Cycle Ext IE* is included in the *Continuous Packet Connectivity DRX Information LCR IE*, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].]
+
+[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall include *Allcoated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK ADDITON RESPONSE message.]
+- [1.28 Mcps TDD – The DRNS shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [1.28 Mcps TDD – The DRNS shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK ADDITION RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent scheduling operation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]
+
+[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall include *Allcoated E-DCH Semi-persistent resource* IE in the RADIO LINK ADDITON RESPONSE message.]
+- [1.28 Mcps TDD – If the *E-DCH Semi-Persistent scheduling Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.]
+
+#### **[1.28 Mcps TDD –Multi-Carrier E-DCH:]**
+
+[1.28 Mcps TDD - If the *Multi-Carrier E-DCH Information* IE is present in the RADIO LINK ADDITION REQUEST message, then the *Multi-Carrier E-DCH Information* IE defines the new configuration and then:]
+
+- [1.28 Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequencies indicated by the the *Multi-Carrier E-DCH Information LCR* IE.]
+- [1.28 Mcps TDD - The DRNS shall use the corresponding *PRXdcs\_base* IE for power control on each uplink frequency according to TS 25.331 [16].]
+- [1.28 Mcps TDD - If the *SNPL Carrier Group Indicator* IE is present in the *Multi-Carrier E-DCH Information LCR* IE, the DRNS shall use the information to determine which SNPL Carrier Group each frequency indicated by the *UARFCN* IE belongs to.]
+- [1.28 Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iur transport bearer mode", the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+- [1.28 Mcps TDD – If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "E-DCH UL flow multiplexing mode", the DRNS shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iur transport bearer.]
+- [1.28 Mcps TDD - If the Separate Iur transport bearer mode is used in the new configuration, then the DRNS shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+
+- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the DRNS shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response 1.28Mcps* IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+
+#### [1.28 Mcps TDD - MU-MIMO Handling:]
+
+[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *MU-MIMO Indicator* IE, then:]
+
+- [1.28 Mcps TDD –the DRNS may use the MU-MIMO for the radio link according to the *MU-MIMO Usage Indicator* IE and shall include the *MU-MIMO Information* IE in the RADIO LINK SETUP RESPONSE message.]
+- [1.28 Mcps TDD – If the *Standalone Midamble Channel Indicator* IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK ADDITION RESPONSE message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK ADDITION RESPONSE message.
+
+#### Response message:
+
+If all requested RLs are successfully added, the DRNC shall respond with a RADIO LINK ADDITION RESPONSE message.
+
+After sending the RADIO LINK ADDITION RESPONSE message the DRNS shall continuously attempt to obtain UL synchronisation on the Uu interface.
+
+For each RL for which the *Delayed Activation* IE is not included in the RADIO LINK ADDITION REQUEST message the DRNS shall:
+
+- [FDD –start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4].]
+- [TDD – start transmission on the new RL immediately as specified in TS 25.427 [4].]
+
+For each RL for which the *Delayed Activation* IE is included in the RADIO LINK ADDITION REQUEST message, the DRNS shall:
+
+- if the *Delayed Activation* IE indicates “Separate Indication”:
+ - - not start any DL transmission for the concerning RL on the Uu interface.
+- if the *Delayed Activation* IE indicates “CFN”:
+ - - [FDD – start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4], however never before the CFN indicated in the *Activation CFN* IE.]
+- [TDD – start transmission on the new RL at the CFN indicated in the *Activation CFN* IE as specified in TS 25.427 [4].]
+
+[1.28 Mcps TDD – if the DRNS assigns one or more PLCCH sequence numbers to the radio link, then the PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK ADDITION RESPONSE message.]
+
+#### 8.3.2.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: Unsuccessful Operation
+ SRNC->>DRNC: RADIO LINK ADDITION REQUEST
+ DRNC-->>SRNC: RADIO LINK ADDITION FAILURE
+
+```
+
+Sequence diagram showing the Unsuccessful Operation of the Radio Link Addition procedure. The diagram shows two vertical lifelines for SRNC and DRNC. A horizontal arrow labeled 'RADIO LINK ADDITION REQUEST' points from SRNC to DRNC. A horizontal arrow labeled 'RADIO LINK ADDITION FAILURE' points from DRNC back to SRNC.
+
+**Figure 8: Radio Link Addition procedure: Unsuccessful Operation**
+
+If the establishment of at least one RL is unsuccessful, the DRNC shall respond with a RADIO LINK ADDITION FAILURE message. DRNC shall include in the RADIO LINK ADDITION FAILURE message a general *Cause* IE or a *Cause* IE for each failed radio link. The *Cause* IE indicates the reason for failure.
+
+[FDD – If some RL(s) were established successfully, the DRNC shall indicate this in the RADIO LINK ADDITION FAILURE message in the same way as in the RADIO LINK ADDITION RESPONSE message.]
+
+[FDD – If the requested Serving HS-DSCH Radio Link Change was successful, or if the addition of the requested serving HS-DSCH Radio Link was successful or existed already but the Serving HS-DSCH Radio Link change was unsuccessful, the DRNS shall indicate this in the *HS-DSCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the requested secondary serving HS-DSCH Radio Link Change was successful, or if the addition of the requested secondary serving HS-DSCH Radio Link was successful or existed already but the secondary serving HS-DSCH Radio Link change was unsuccessful, the DRNS shall indicate this in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the requested Serving E-DCH Radio Link Change was successful, or if the addition of the requested serving E-DCH Radio Link was successful or existed already but the Serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the *MIMO Activation Indicator* IE is included and the *Power Offset For S-CPICH for MIMO Request Indicator* IE is not included in the *HS-DSCH FDD Information* IE in the *HS-DSCH Serving Cell Change Information* IE in the RADIO LINK ADDITION REQUEST message or the power offset for S-CPICH for MIMO Request indicator has not been configured in the UE Context but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link shall be reported as failed and the DRNC shall include in the RADIO LINK ADDITION FAILURE message the *Cause* IE.]
+
+[FDD – If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included and the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is not included in the *HS-DSCH FDD Information* IE in the *HS-DSCH Serving Cell Change Information* IE in the RADIO LINK ADDITION REQUEST message or the power offset for S-CPICH for MIMO with four transmit antennas Request indicator has not been configured in the UE Context but MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link shall be reported as failed and the DRNC shall include in the RADIO LINK ADDITION FAILURE message the *Cause* IE.]
+
+[FDD – If the requested additional serving E-DCH Radio Link Change was successful, or if the addition of the requested additional serving E-DCH Radio Link was successful or existed already but the additional serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the *Additional E-DCH Secondary Serving Cell Change Information Response* IE in the *Additional E-DCH Cell Change Information Response* IE in the RADIO LINK ADDITION FAILURE message.]
+
+Typical cause values are:
+
+#### Radio Network Layer Causes:
+
+- DL Radio Resources not Available;
+- UL Radio Resources not Available;
+- Combining Resources not Available;
+- Combining not Supported
+- Cell not Available;
+- [FDD – Requested Tx Diversity Mode not Supported;]
+- Power Level not Supported;
+- CM not Supported;
+- Reconfiguration CFN not Elapsed;
+- Number of DL Codes not Supported;
+- Number of UL codes not Supported;
+- [FDD – DPC mode change not Supported;]
+- Cell reserved for operator use;
+- Delayed Activation not supported;
+
+[FDD – F-DPCH not supported;]
+ E-DCH not supported;
+ [FDD – MIMO not supported;]
+ [FDD – E-DCH TTI2ms not supported;]
+ [FDD – Continuous Packet Connectivity DTX-DRX operation not available;]
+ [FDD – Continuous Packet Connectivity UE DTX Cycle not available;]
+ [FDD – MIMO not available;]
+ [FDD – F-DPCH Slot Format operation not supported;]
+ [FDD – E-DPCCH Power Boosting not supported;]
+ [FDD – SixtyfourQAM DL and MIMO Combined not available;]
+ [FDD – Multi Cell operation not available;]
+ [FDD – Multi Cell operation not supported;]
+ [1.28Mcps TDD – MIMO not supported;]
+ [1.28Mcps TDD – MIMO not available;]
+ [1.28Mcps TDD – SixtyfourQAM DL and MIMO Combined not available;]
+ [FDD – TX diversity for MIMO UE on DL Control Channels not available;]
+ [FDD – Single Stream MIMO not available;]
+ [FDD – Multi Cell operation with MIMO not available;]
+ [FDD – Multi Cell operation with MIMO not supported;]
+ [FDD – Multi Cell E-DCH Operation not supported;]
+ [FDD – Multi Cell E-DCH Operation not available;]
+ [FDD – Multi Cell operation with Single Stream MIMO not available;]
+ [FDD – Multi Cell operation with Single Stream MIMO not supported;]
+ [FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available;]
+ [FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported;]
+ [FDD – Frequency Specific Compressed Mode Not Available;]
+ [FDD – Uplink Closed Loop Transmit Diversity Operation Not Available;]
+ [FDD – Uplink Closed Loop Transmit Diversity Operation Not Supported;]
+ [FDD – MIMO with four transmit antennas not supported;]
+ [FDD – MIMO with four transmit antennas not available;]
+ [FDD – Dual Stream MIMO with four transmit antennas not supported;]
+ [FDD – Dual Stream MIMO with four transmit antennas not available;]
+ [FDD – Multiflow Operation Not Available;]
+ [FDD – Multiflow Operation Not Supported;]
+ [FDD – SixtyfourQAM UL not Available;]
+ [FDD – SixtyfourQAM UL not Supported;]
+ [FDD – UL MIMO Operation Not Available;]
+ [FDD – UL MIMO Operation Not Supported;]
+ [FDD – UL MIMO and SixteenQAM Operation Not Available;]
+ [FDD – UL MIMO and SixteenQAM Operation Not Supported;]
+ [FDD – UL MIMO and SixtyfourQAM Operation Not Available;]
+ [FDD – UL MIMO and SixtyfourQAM Operation Not Supported.]
+
+#### Transport Layer Causes:
+
+Transport Resource Unavailable.
+
+#### Miscellaneous Causes:
+
+Control Processing Overload;
+ HW Failure;
+ Not enough User Plane Processing Resources.
+
+### 8.3.2.4 Abnormal Conditions
+
+If the RADIO LINK ADDITION REQUEST message includes a *C-ID* IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is not available in the DRNC for the considered UE Context, the DRNC shall reject the procedure for this particular Radio Link and send the RADIO LINK ADDITION FAILURE message.
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transmission Gap Pattern Sequence Status* IEs in the *Active Pattern Sequence Information* IE and it does not address exactly all ongoing compressed mode patterns and frequency specific compressed mode is not supported, the DRNS shall reject the Radio Link Addition
+
+procedure and shall respond with a RADIO LINK ADDITION FAILURE message with the *Cause* IE value “Invalid CM settings”.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message is used to establish a new RL without compressed mode when compressed mode is active for the existing RL(s) (as specified in subclause 8.3.2.2), and if at least one of the new RLs is to be established in a cell that has the same UARFCN (both UL and DL) as at least one cell with an already existing RL and frequency specific compressed mode is not supported,, the DRNS shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value “Invalid CM settings”.]
+
+[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Individual” in the existing RL(s) and if the *DL Reference Power* IEs are included in the *RL Information* IE but the *DL Reference Power* IE is not present for each RL in the *RL Information* IE, the DRNC shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *DL Reference Power* IEs in the *RL Information* IE but the power balancing is not active in the existing RL(s) or the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Common” in the existing RL(s), the DRNC shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value “Power Balancing status not compatible”.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Enhanced Primary CPICH Ec/No* IE, but not the *Primary CPICH Ec/No* IE, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE [FDD – or for an E-DCH MAC-d flow in *RL Specific E-DCH Information* IE] included in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to “Must” [FDD – or the RL is combined with existing E-DCH RL which transport bearer is not established in the DRNS], the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE nor *RL Specific E-DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to “May”, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to “Must Not”, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in [FDD – the *RL Specific E-DCH Information* IE in the *RL Information* IE for the first E-DCH RL][TDD – the *E-DCH MAC-d Flows Information TDD* IE], the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
+
+If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for an HS-DSCH MAC-d Flow in the *HS-DSCH MAC-d Flows Information* IE, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
+
+If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE or the *Binding ID* IE, and not both are present for a transport bearer intended to be established, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Serving Cell Change Information* IE but not the *HS-DSCH FDD Information* IE and the UE Context is not configured for HS-DSCH, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Serving Cell Change CFN* IE but neither the *Serving E-DCH RL* IE nor the *HS-DSCH Serving Cell Change Information* IE, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Serving E-DCH RL* IE but the UE Context is not configured for E-DCH, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the *E-DCH FDD Information* IE is present in the RADIO LINK ADDITION REQUEST message, but the *E-DPCH Information* IE is not present, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH RL Indication* IE set to “E-DCH”, but no *E-DCH FDD Information* IE, and the UE Context is not configured for E-DCH, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH FDD Information* IE but no *E-DCH RL Indication* IE set to “E-DCH”, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[TDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-PDSCH RL-ID* IE not equal to the *RL ID* IE, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[TDD – If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Serving RL* IE not equal to the *RL ID* IE, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+If the RADIO LINK ADDITION REQUEST message contains the *HS-PDSCH RL ID* IE [FDD – in the *HS-DSCH Serving Cell Change Information* IE] and/or *Serving E-DCH RL* IE and if both HS-DSCH and E-DCH are configured in the DRNS but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *HS-DSCH Serving Cell Change Information* IE and the *E-DPCH Information* IE which includes the *HS-DSCH Configured Indicator* IE set as “HS-DSCH not configured” then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information*] and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information*] has the value “Indexed MAC-d PDU Size”, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
+
+If the RADIO LINK ADDITION REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information*] and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information*] has the value “Flexible MAC-d PDU Size”, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[TDD – If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE is not present, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Transport Bearer Not Requested Indicator* IE for a DCH but the DCH is configured to be included as a part of the downlink CCTrCH, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *MIMO Activation Indicator* IE, *Sixtyfour QAM Usage Allowed Indicator* IE set to “Allowed”, the *Additional HS Cell Information RL Addition* IE, the *MIMO with four transmit antennas Activation Indicator* IE, the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE and/or the *Single Stream MIMO Activation Indicator* IE, but does not contain the *HS-DSCH MAC-d PDU*
+
+*Size Format* IE set to “Flexible MAC-d PDU Size”, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Serving E-DCH RL ID* IE but contains the *Transport Bearer Not Requested Indicator* IE in the RL Specific E-DCH Information for the new Serving E-DCH RL or there is at least one E-DCH MAC-d flow which transport bearer was not configured in the existing E-DCH RL to be combined with the Serving E-DCH RL, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with the existing RL which the transport bearer is established for the DCH or the E-DCH MAC-d Flow in DRNS, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition* IE indicating a secondary serving cell that is not in the same Node B as the new serving HS-DSCH cell, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition* IE and if the HS-DSCH is not configured in the DRNS Communication Context and the *HS-DSCH Information* IE is not present, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+If the RADIO LINK ADDITION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information* IE] set to “Flexible RLC PDU Size”, *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information* IE] has the value “Indexed MAC-d PDU Size”, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
+
+If the RADIO LINK ADDITION REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information* IE] and the *DL RLC PDU Size Format* IE in the *HS-DSCH Information* IE [FDD – in the *HS-DSCH Serving Cell Change Information* IE] has the value “Flexible RLC PDU Size”, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE in the *HS-DSCH Serving Cell Change Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and if the *E-DPCH Information* IE is not present or the E-DPCH Information was not configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Additional E-DCH Cell Information RL Add Req* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Additional E-DCH Cell Information RL Add Req* IE and the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, but the Radio Link indicated by the *E-DCH Additional RL ID* IE is not configured in the current UE context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Diversity Mode* IE in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE and the secondary serving HS-DSCH is already configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD – If the secondary serving HS-DSCH is not configured in the UE Context and if the RADIO LINK ADDITION REQUEST message contains in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell*
+
+*Information RL Addition* IE the *Diversity Mode* IE not set to "None" but not the *Transmit Diversity Indicator* or contains the *Transmit Diversity Indicator* but not the *Diversity Mode* IE not set to "None", then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition* IE and the new configuration contains more than one secondary serving HS-DSCH RL and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the *Ordinal Number Of Frequency* IE in the *HS-DSCH FDD Secondary Serving Information* IE, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition* IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have *Ordinal Number Of Frequency* value "1", the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM settings".]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message contains the *UL CLTD Information* IE but does not contain the *F-TPICH Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL CLTD Information* IE but without *F-TPICH Information* IE, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message contains the *UL MIMO Information* IE in *E-DCH FDD Information* IE but does not contain the *UL CLTD Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL MIMO Information* IE but without *UL CLTD Information* IE, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+[FDD - If the RADIO LINK ADDITION REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
+
+## 8.3.3 Radio Link Deletion
+
+### 8.3.3.1 General
+
+The Radio Link Deletion procedure is used to release the resources in a DRNS for one or more established radio links towards a UE.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Radio Link Deletion procedure may be initiated by the SRNC at any time after establishing a Radio Link.
+
+### 8.3.3.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: Initiate Radio Link Deletion
+ SRNC->>DRNC: RADIO LINK DELETION REQUEST
+ DRNC-->>SRNC: RADIO LINK DELETION RESPONSE
+
+```
+
+Sequence diagram showing the successful operation of the Radio Link Deletion procedure. The SRNC sends a RADIO LINK DELETION REQUEST message to the DRNC, and the DRNC responds with a RADIO LINK DELETION RESPONSE message.
+
+**Figure 9: Radio Link Deletion procedure, Successful Operation**
+
+The procedure is initiated with a RADIO LINK DELETION REQUEST message sent from the SRNC to the DRNC.
+
+Upon receipt of this message, the DRNS shall delete the radio link(s) identified by the *RL ID* IE(s) in the message, shall release all associated resources and shall respond to the SRNC with a RADIO LINK DELETION RESPONSE message.
+
+If the radio link(s) to be deleted represent the last radio link(s) for the UE in the DRNS and if the UE is not using any common resources in the DRNS, then the DRNC shall release the UE Context.
+
+[FDD – After deletion of the RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall for each of the remaining RL Set(s) use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall for each of the remaining RL Set(s) use the minimum value of the parameters N\_INSYNC\_IND that are configured in the cells supporting the radio links of the RL Set.]
+
+[FDD – If the RL indicated by the *RL ID* IE in the RADIO LINK DELETION REQUEST message is the serving HS-DSCH Radio link and a related secondary serving HS-DSCH Radio Link exists in the DRNS, the DRNC shall delete the secondary serving HS-DSCH Radio Link.]
+
+[FDD – If the RL indicated by the *RL ID* IE in the RADIO LINK DELETION REQUEST message is the secondary serving HS-DSCH Radio link, the DRNC shall delete the secondary serving HS-DSCH Radio Link.]
+
+### 8.3.3.3 Unsuccessful Operation
+
+-
+
+### 8.3.3.4 Abnormal Conditions
+
+If the RL indicated by the *RL ID* IE does not exist, the DRNC shall respond with the RADIO LINK DELETION RESPONSE message.
+
+## 8.3.4 Synchronised Radio Link Reconfiguration Preparation
+
+### 8.3.4.1 General
+
+The Synchronised Radio Link Reconfiguration Preparation procedure is used to prepare a new configuration of Radio Link(s) related to one UE-UTRAN connection within a DRNS.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Synchronised Radio Link Reconfiguration Preparation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.4.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: Initiate procedure
+ SRNC->>DRNC: RADIO LINK RECONFIGURATION PREPARE
+ Note right of DRNC: Process request
+ DRNC-->>SRNC: RADIO LINK RECONFIGURATION READY
+```
+
+The diagram illustrates the interaction between the SRNC and the DRNC for the Synchronised Radio Link Reconfiguration Preparation procedure. It starts with the SRNC sending a 'RADIO LINK RECONFIGURATION PREPARE' message to the DRNC. The DRNC then responds with a 'RADIO LINK RECONFIGURATION READY' message back to the SRNC.
+
+Sequence diagram showing the Synchronised Radio Link Reconfiguration Preparation procedure between SRNC and DRNC.
+
+**Figure 10: Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation**
+
+The Synchronised Radio Link Reconfiguration Preparation procedure is initiated by the SRNC by sending the RADIO LINK RECONFIGURATION PREPARE message to the DRNC.
+
+Upon receipt, the DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *Allowed Queuing Time* IE the DRNS may queue the request the time corresponding to the value of the *Allowed Queuing Time* IE before starting to execute the request.
+
+The DRNS shall prioritise resource allocation for the RL(s) to be modified according to Annex A.
+
+If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK RECONFIGURATION PREPARE message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
+
+#### **DCH Modification:**
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCHs To Modify* IEs, the DRNS shall treat them each as follows:
+
+- If the *DCHs To Modify* IE includes multiple *DCH Specific Info* IEs then the DRNS shall treat the DCHs in the *DCHs To Modify* IE as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
+- If the *DCHs To Modify* IE includes the *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCHs To Modify* IE includes the *ToAWS* IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCHs To Modify* IE includes the *ToAWE* IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Frame Handling Priority* IE for a DCH to be modified, the DRNS should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the DRNS once the new configuration has been activated.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Traffic Class* IE for a DCH to be modified, the DRNS should store this information for this DCH in the new configuration. The *Traffic Class* IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE for this DCH indicates the value “RRC”.
+- [FDD – If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to “Uplink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.]
+- [FDD – If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to “ Downlink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.]
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Transport Format Set* IE for the UL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration.
+- If the *DCHs to Modify* IE includes the *TNL QoS* IE for a DCH or a set of co-ordinated DCHs to be modified and if ALCAP is not used, the DRNS may store this information for this DCH in the new configuration. The *TNL QoS* IE may be used to determine the transport bearer characteristics to apply in the uplink for the related DCH or set of co-ordinated DCHs.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Transport Format Set* IE for the DL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Allocation/Retention Priority* IE, the DRNS shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A.
+- [TDD – If the *DCHs To Modify* IE includes the *CCTrCH ID* IE for the UL, the DRNS shall map the DCH onto the referenced UL CCTrCH in the new configuration.]
+
+- [TDD – If the *DCHs To Modify* IE includes the *CCTrCH ID* IE for the DL, the DRNS shall map the DCH onto the referenced DL CCTrCH in the new configuration.]
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Guaranteed Rate Information* IE, the DRNS shall treat the included IEs according to the following:
+ - - If the *Guaranteed Rate Information* IE includes the *Guaranteed UL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate in the uplink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate.
+ - - If the *Guaranteed Rate Information* IE includes the *Guaranteed DL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate in the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate.
+
+#### DCH Addition:
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCHs To Add* IEs, the DRNS shall treat them each as follows:
+
+- The DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message and include these DCH in the new configuration.
+- If the *DCH Information* IE includes a *DCHs To Add* IE with multiple *DCH Specific Info* IEs, the DRNS shall treat the DCHs in the *DCHs To Add* IE as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
+- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to “Uplink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.
+- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to “Downlink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.
+- [FDD – For each DCH which do not belong to a set of co-ordinated DCHs and which includes a *QE-Selector* IE set to “selected”, the DRNS shall use the Transport channel BER from that DCH for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If the *QE-Selector* IE is set to “non-selected”, the DRNS shall use the Physical channel BER for the QE in the UL data frames, TS 25.427 [4].]
+- For a set of co-ordinated DCHs, the DRNS shall use the Transport channel BER from the DCH with the *QE-Selector* IE set to “selected” for the QE in the UL data frames, TS 25.427 [4]. [FDD – If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If all DCHs have the *QE-Selector* IE set to “non-selected”, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4].] [TDD – If no Transport channel BER is available for the selected DCH, the DRNS shall use 0 for the QE, TS 25.427 [4].]
+- The DRNS should store the *Frame Handling Priority* IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the DRNS once the new configuration has been activated.
+- If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the DRNS may use this information to determine the transport bearer characteristics to apply for the uplink for the related DCH or set of co-ordinated DCHs.
+- The DRNS should store the *Traffic Class* IE received for a DCH to be added in the new configuration. The *Traffic Class* IE may be used to determine the transport bearer characteristics to apply between DRNC and Node
+
+B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE indicates the value “RRC”.
+
+- The DRNS shall use the included *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- The DRNS shall use the included *ToAWS* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- The DRNS shall use the included *ToAWE* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- [3.84Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD* IE in the RADIO LINK RECONFIGURATION READY message if at least one DSCH or USCH exists in the new configuration.]
+- [1.28Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK RECONFIGURATION READY message if at least one DSCH or USCH exists in the new configuration.]
+- [7.68Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD 7.68Mcps* IE in the RADIO LINK RECONFIGURATION READY message if at least one DSCH or USCH exists in the new configuration.]
+- If the *DCHs To Add* IE contains a *DCH Specific Info* IE which includes the *Guaranteed Rate Information* IE, the DRNS shall treat the included IEs according to the following:
+ - - If the *Guaranteed Rate Information* IE includes the *Guaranteed UL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the uplink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the *DCH Specific Info* IE in the *DCHs To Add* IE does not include the *Guaranteed UL Rate* IE, the DRNS shall not limit the user rate of the uplink of the DCH.
+- If the *Guaranteed Rate Information* IE includes the *Guaranteed DL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the *DCH Specific Info* IE in the *DCHs To Add* IE does not include the *Guaranteed DL Rate* IE, the DRNS shall not limit the user rate of the downlink of the DCH.
+- [TDD – The DRNS shall apply the *CCTrCH ID* IE (for the DL) in the Downlink of this DCH in the new configuration.]
+- [TDD – The DRNS shall apply the *CCTrCH ID* IE (for the UL) in the Uplink of this DCH in the new configuration.]
+
+#### DCH Deletion:
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCH To Delete*, the DRNS shall not include the referenced DCHs in the new configuration.
+
+If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the DRNS shall not include this set of co-ordinated DCHs in the new configuration.
+
+#### Physical Channel Modification:
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *UL DPCH Information* IE, the DRNS shall apply the parameters to the new configuration as follows:]
+
+- [FDD – If the *UL DPCH Information* IE includes the *Uplink Scrambling Code* IE, the DRNS shall apply this Uplink Scrambling Code to the new configuration.]
+- [FDD – If the *UL DPCH Information* IE includes the *Min UL Channelisation Code Length* IE, the DRNS shall apply the new Min UL Channelisation Code Length in the new configuration. The DRNS shall apply the contents of the *Max Number of UL DPDCHs* IE (if it is included) in the new configuration.]
+- [FDD – If the *UL DPCH Information* IE includes the *TFCS* IE, the DRNS shall use the *TFCS* IE for the UL when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration.]
+- [FDD – If the *UL DPCH Information* IE includes the *UL DPCCH Slot Format* IE, the DRNS shall apply the new Uplink DPCCH Slot Format to the new configuration.]
+- [FDD – If the *UL DPCH Information* IE includes the *UL SIR Target* IE, the DRNS shall use the value for the UL inner loop power control when the new configuration is being used.]
+- [FDD – If the *UL DPCH Information* IE includes the *Puncture Limit* IE, the DRNS shall apply the value in the uplink of the new configuration.]
+- [FDD – If the *UL DPCH Information* IE includes the *Diversity Mode* IE, the DRNS shall apply diversity according to the given value.]
+- [FDD – If the *UL DPCH Information* IE includes the *UL DPDCH Indicator For E-DCH Operation* IE and it is set to “UL DPDCH not present”, the UL DPDCH resources shall be removed from the configuration.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes a *DL DPCH Information* IE and the concerned UE Context is configured to use F-DPCH in the downlink in the old configuration, the DRNS shall configure the concerned UE Context to use DPCH in the downlink in the new configuration. In this case, if at least one Transmission Gap Pattern Sequence is configured with an SF/2 downlink compressed mode method in the new configuration, the DRNC shall include the *Transmission Gap Pattern Sequence Scrambling Code Information* IE in the RADIO LINK RECONFIGURATION READY message indicating for each Channelisation Code whether the alternative scrambling code shall be used or not.]
+
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *DL DPCH Power Information* IE, the DRNS shall use the information contained in it for the power settings of the DL DPCH. In particular, if the received *Inner Loop DL PC Status* IE is set to “Active”, the DRNS shall activate the inner loop DL power control for all RLs. If *Inner Loop DL PC Status* IE is set to “Inactive”, the DRNS shall deactivate the inner loop DL power control for all RLs according to TS 25.214 [10]. Furthermore, the DRNC shall include the *DL Code Information* IE in the RADIO LINK RECONFIGURATION READY.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes a *DL DPCH Information* IE, the DRNS shall apply the parameters to the new configuration as follows:]
+
+- [FDD – If the *DL DPCH Information* IE includes the *Number of DL Channelisation Codes* IE, the DRNS shall allocate given number of Downlink Channelisation Codes per Radio Link and apply the new Downlink Channelisation Code(s) to the new configuration. Each Downlink Channelisation Code allocated for the new configuration shall be included in the RADIO LINK RECONFIGURATION READY message within the *DL Code Information* IE as a *FDD DL Channelisation Code Number* IE when sent to the SRNC. If some Transmission Gap Pattern sequences using “SF/2” method are already initialised in the DRNS, DRNC shall include the *Transmission Gap Pattern Sequence Scrambling Code Information* IE in the RADIO LINK RECONFIGURATION READY message in case the DRNS selects to change the Scrambling code change method for one or more DL Channelisation Code.]
+- [FDD – When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.211 [8]. When *p* number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to “*PhCH number 1*”, the second to “*PhCH number 2*”, and so on until the *p*th to “*PhCH number p*”.]
+- [FDD – If the *DL DPCH Information* IE includes the *TFCS* IE, the DRNS shall use the *TFCS* IE for the DL when reserving resources for the downlink of the new configuration. The DRNS shall apply the new TFCS in the Downlink of the new configuration.]
+
+- [FDD – If the *DL DPCH Information* IE includes the *DL DPCH Slot Format* IE, the DRNS shall apply the new slot format used in DPCH in DL.]
+- [FDD – If the *DL DPCH Information* IE includes the *TFCI Signalling Mode* IE, the DRNS shall apply the new signalling mode of the TFCI.]
+- [FDD – If the *DL DPCH Information* IE includes the *Multiplexing Position* IE, the DRNS shall apply the new parameter to define whether fixed or flexible positions of transport channels shall be used in the physical channel.]
+- [FDD – If the *DL DPCH Information* IE includes the *Limited Power Increase* IE set to “Used”, the DRNS shall, if supported, use Limited Power Increase according to TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.]
+- [FDD – If the *DL DPCH Information* IE includes the *Limited Power Increase* IE set to “Not Used”, the DRNS shall not use Limited Power Increase for the inner loop DL power control in the new configuration.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *F-DPCH Information* IE, then:]
+
+- [FDD – The DRNS shall configure the concerned UE Context to use F-DPCH in the downlink in the new configuration.]
+- [FDD – If the *F-DPCH Information* IE includes the *F-DPCH Slot Format Support Request* IE, then the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the RADIO LINK RECONFIGURATION READY message. If the *F-DPCH Information* IE includes the *F-DPCH Slot Format* IE, the DRNC may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transmission Gap Pattern Sequence Information* IE, the DRNS shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode Configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode Configuration has been activated or once the previous Compressed Mode Configuration has been deactivated. This new Compressed Mode Configuration shall be valid in the DRNS until the next Compressed Mode Configuration is configured in the DRNS or until the last Radio Link is deleted.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transmission Gap Pattern Sequence Information* IE and the *Downlink Compressed Mode Method* IE in one or more Transmission Gap Pattern Sequence within the *Transmission Gap Pattern Sequence Information* IE is set to “SF/2” and the UE Context is configured to use DPCH in the downlink in the new configuration, the DRNC shall include the *Transmission Gap Pattern Sequence Scrambling Code Information* IE in the RADIO LINK RECONFIGURATION READY message indicating for each Channelisation Code whether the alternative scrambling code shall be used or not.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DPCH Information* IE, the DRNS shall apply the parameters to the new configuration as follows:]
+
+- [FDD – If the *E-DPCH Information* IE includes the *Maximum Set of E-DPDCHs* IE, the DRNS shall apply the contents of the Maximum Set in the new configuration.]
+- [FDD – If the *E-DPCH Information* IE includes the *Puncture Limit* IE, the DRNS shall apply the value in the uplink of the new configuration.]
+- [FDD – If the *E-DPCH Information* IE includes the *E-TFCS Information* IE, the DRNS shall use the *E-TFCS Information* IE for the E-DCH when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration. If the *E-TFCS Information* IE contains the *E-DCH Minimum Set E-TFCI Validity Indicator* IE the DRNS shall ignore the value in *E-DCH Minimum Set E-TFCI* IE. If the *E-DCH Minimum Set E-TFCI validity indicator* IE is absent DRNS shall use the value for the related resource allocation operation.]
+- [FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION PREPARE message.]
+
+- [FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the DRNS shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the DRNS shall use the value “127” in the algorithm defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION PREPARE message.]
+- [FDD – If the *E-DPCH Information* IE includes the *E-TTI* IE, the DRNS shall use the value when the new configuration is being used.]
+- [FDD – If the *E-DPCH Information* IE includes the *E-DPCCH Power Offset* IE, the DRNS shall use the value when the new configuration is being used.]
+- [FDD – If the *E-DPCH Information* IE includes the *E-RGCH 2-Index-Step* IE, the DRNS shall use the value when the new configuration is being used.]
+- [FDD – If the *E-DPCH Information* IE includes the *E-RGCH 3-Index-Step* IE, the DRNS shall use the value when the new configuration is being used.]
+- [FDD – If the *E-DPCH Information* IE includes the *E-DCH HARQ Info* IE, the DRNS shall use the value when the new configuration is being used.]
+- [FDD – If the *E-DPCH Information* IE includes the *HS-DSCH Configured Indicator* IE, the DRNS shall use the value when the new configuration is being used.]
+- [FDD – If the *E-DPCH Information* IE includes the *Minimum Reduced E-DPDCH Gain Factor* IE , then the DRNS shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPAR message includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:]
+
+- [FDD – The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]
+- [FDD – If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then:]
+
+- [FDD – If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.]
+- [FDD – If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10].]
+- [FDD – If the *DTX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of *DTX Information To Modify* IE is “Deactivate”, then DRX should be deactivated together with DTX.]
+- [FDD – If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:]
+
+- [FDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]
+
+- [FDD – The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If at least one of *HS-PDSCH Second Code Support* IE is set to “True”, then the DRNC shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE, then the DRNS shall deactivate the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.]
+
+#### **[FDD - UL CLTD Setup:]**
+
+[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Setup", then: the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights according the new configuration defined in the *UL CLTD Information* IE and then:]
+
+- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.]
+
+[FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]
+
+#### **[FDD - UL CLTD Modification:]**
+
+[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Configuration Change", then: the *UL CLTD Information To Modify* IE defines the new configuration and then:]
+
+- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *C-ID* IE in the *UL CLTD Information To Modify* IE, then the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context. Otherwise the DRNS shall configure the serving E-DCH cell or the HS\_DSCH serving cell to determine the precoding weights as specified in TS 25.319[38]. The UL CLTD configuration is only valid for the cell to determine the precoding weights.]
+- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *S-DPCCH Power Offset information* IE in the *UL CLTD Information To Modify* IE, then the DRNS shall use this value to determine the S-DPCCH power.]
+- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UL CLTD State Activation Information* IE in the *UL CLTD Information To Modify* IE, then the DRNS shall use this value to update the local state of UL CLTD for the concerned UE Context. If the *UL CLTD Activation Information* IE is set to "De-activated", the DRNS should release the F-TPICH resource configured for the concerned UE Context.]
+
+#### **[FDD - UL CLTD Removal:]**
+
+[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Removal", then the configured UL CLTD for the concerned UE Context shall be removed.]
+
+#### **[FDD – UL MIMO Setup:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UL MIMO Information* IE in *E-DCH FDD Information*, or *UL MIMO Reconfiguration* IE and the choice of *Setup or Change or Stop* is “Setup”, then the DRNS shall setup the requested UL MIMO operation.]
+
+#### **[FDD – UL MIMO Modification:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *UL MIMO Reconfiguration* IE and the choice of *Setup or Change or Stop* is “Change”, then the DRNS shall apply the new configuration.]
+
+#### **[FDD – UL MIMO Removal:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UL MIMO Reconfiguration IE* and the choice of *Setup* or *Change* or *Stop* is "Stop", then the DRNS shall terminate the UL MIMO operation.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DRX Information LCR IE*, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[1.28 Mcps TDD – If the *Inactivity Threshold for UE DRX Cycle Ext IE* is included in the *Continuous Packet Connectivity DRX Information LCR IE*, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DRX Information To Modify LCR IE*, then:]
+
+- [1.28 Mcps TDD – If the *UE DTX DRX Offset IE* is included in the *Continuous Packet Connectivity DRX Information To Modify LCR IE*, then the DRNS shall apply the indicated Offset in *UE DTX DRX Cycle IE* in the new configuration.]
+- [1.28 Mcps TDD – If the *Enabling Delay IE* is included in the *Continuous Packet Connectivity DRX Information To Modify LCR IE*, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [22].]
+- [1.28 Mcps TDD – If the *DRX Information To Modify IE* is included in the *Continuous Packet Connectivity DRX Information To Modify LCR IE*, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Information LCR IE*, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID IE* for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent Resource Reservation Indicator IE* is included in the *HS-DSCH Semi-Persistent scheduling Information LCR IE*, then the DRNS shall include *Allocated HS-PDSCH Semi-persistent resource IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Information LCR IE*, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL IE* for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator IE* is included in the *E-DCH Semi-Persistent scheduling Information LCR IE*, then the DRNS shall include *Allocated E-DCH Semi-persistent resource IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Information to modify LCR IE*, then:]
+
+- [1.28 Mcps TDD – If the *Transport Block Size List IE* or/and *Repetition Period list IE* is/are included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR IE*, the DRNS shall modify the configuration of Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID IE* for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall include *Allcoated HS-DSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent scheduling operation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]
+- [1.28 Mcps TDD – If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [1.28 Mcps TDD – If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then:]
+
+- [1.28 Mcps TDD – If the *Repetition Period list* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, the DRNS shall modify the configuration of Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].
+- [1.28 Mcps TDD – If the *E-DCH Semi-Persistent scheduling Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.]
+- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall include *Allocated E-DCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the DRNS shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the DRNS shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.]
+
+[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MU-MIMO Indicator* IE, then:]
+
+- [1.28 Mcps TDD - The DRNS may use the MU-MIMO for the radio link according to the *MU-MIMO Usage Indicator* IE and shall include the *MU-MIMO Information* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [1.28 Mcps TDD - If the *Standalone Midamble Channel Indicator* IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION READY message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION READY message.]
+
+#### [TDD – UL/DL CCTrCH Modification]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *UL CCTrCH To Modify* IEs or *DL CCTrCH To Modify* IEs, then the DRNS shall treat them each as follows:]
+
+- [TDD – If any of the *UL CCTrCH To Modify* IEs or *DL CCTrCH To Modify* IEs includes any of the *TFCS* IE, *TFCI coding* IE, *Puncture limit* IE, or *TPC CCTrCH ID* IEs the DRNS shall apply these as the new values, otherwise the previous values specified for this CCTrCH are still applicable.]
+- [TDD – If any of the following listed DPCH information IEs are modified in the new prepared configuration, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the IEs indicating the new values: *Repetition Period* IE, *Repetition Length* IE, *TDD DPCH Offset* IE, [3.84 Mcps TDD – *UL Timeslot Information* IE,] [1.28 Mcps TDD – *UL Timeslot Information LCR* IE,] [7.68 Mcps TDD – *UL Timeslot*
+
+*Information 7.68 Mcps IE,] [3.84Mcps TDD – DL Timeslot Information IE,] [1.28Mcps TDD – DL Timeslot Information LCR IE,] [7.68 Mcps TDD – DL Timeslot Information 7.68 Mcps IE,] [3.84Mcps TDD – Midamble Shift And Burst Type IE,] [1.28Mcps TDD – Midamble Shift LCR IE,] [7.68 Mcps TDD – Midamble Shift And Burst Type 7.68 Mcps IE,] [TFCI Presence IE,] [3.84Mcps TDD – TDD Channelisation Code IE,] [1.28Mcps TDD – and/or TDD Channelisation Code LCR IE,] [7.68 Mcps TDD – TDD Channelisation Code 7.68 Mcps IE,] [1.28Mcps TDD – TDD UL DPCH Time Slot Format LCR IE or TDD DL DPCH Time Slot Format LCR IE,]*]
+
+- [1.28Mcps TDD – If the *UL CCTrCH To Modify* IE includes the *UL SIR Target* IE, the DRNS shall use the value for the UL inner loop power control according to TS 25.221 [12] and TS 25.224 [22] in the new configuration.]
+- [TDD – If any of the *DL CCTrCH To Modify* IEs includes any *TPC CCTrCH ID* IEs, the DRNS shall apply these as the new values, otherwise the previous values specified for this CCTrCH are still applicable.]
+- [1.28Mcps TDD – If the *UL CCTrCH to Modify* IE includes the *TDD TPC Uplink Step Size* IE, the DRNS shall apply this value to the uplink TPC step size in the new configuration.]
+- [TDD – If the *DL CCTrCH to Modify* IE includes the *TDD TPC Downlink Step Size* IE, the DRNS shall apply this value to the downlink TPC step size in the new configuration.]
+- [1.28 Mcps TDD – if the DRNS modifies, deletes or grants a new PLCCH assignment(s) to the UL CCTrCH, then the resulting PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[TDD – UL/DL CCTrCH Addition]**
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *UL CCTrCH To Add* IEs or *DL CCTrCH To Add* IEs, the DRNS shall include this CCTrCH in the new configuration.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCHs to Add* IEs, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the DPCH information in [3.84Mcps TDD – *UL DPCH to be Added IE/DL DPCH to be Added* IEs] [1.28Mcps TDD – *UL DPCH to be Added LCR IE/DL DPCH to be Added LCR* IEs] [7.68 Mcps TDD – *UL DPCH to be Added 7.68 Mcps IE/DL DPCH to be Added 7.68 Mcps* IEs]. [3.84Mcps TDD – If no UL DPCH is active before a reconfiguration which adds an UL DPCH, and if a valid Rx Timing Deviation measurement is known in DRNC, then the DRNC shall include the *Rx Timing Deviation* IE (or the *Rx Timing Deviation 3.84 Mcps Extended* IE if the cell containing the radio link is configured for extended timing advance) in the RADIO LINK RECONFIGURATION READY message]. [7.68 Mcps TDD – If no UL DPCH is active before a reconfiguration which adds an UL DPCH, and if a valid Rx Timing Deviation measurement is known in DRNC, then the DRNC shall include the *Rx Timing Deviation 7.68 Mcps* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *TDD TPC Downlink Step Size* IE within a *DL CCTrCH To Add* IE, the DRNS shall set the TPC step size of that CCTrCH to that value, otherwise the DRNS shall use the same value as the lowest numbered DL CCTrCH in the current configuration.]
+
+[1.28Mcps TDD – The DRNS shall use the *UL SIR Target* IE in the *UL CCTrCH To Add* IE as the UL SIR value for the inner loop power control for this CCTrCH according to TS 25.221 [12] and TS 25.224 [22] in the new configuration.]
+
+[TDD – If any of the *DL CCTrCH To Add* IEs includes any *TPC CCTrCH ID* IEs, the DRNS shall configure the identified UL CCTrCHs with TPC according to the parameters given in the message.]
+
+[1.28Mcps TDD – If the *UL CCTrCH To Add* IE includes *TDD TPC Uplink Step Size* IE, the DRNS shall apply the uplink TPC step size in the new configuration.]
+
+[1.28 Mcps TDD – if the DRNS grants a PLCCH assignment(s) to the UL CCTrCH, then the resulting PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[TDD – UL/DL CCTrCH Deletion]**
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *UL CCTrCH To Delete* IEs or *DL CCTrCH To Delete* IEs, the DRNS shall remove this CCTrCH in the new configuration, and the DRNC shall include in the RADIO LINK RECONFIGURATION READY message corresponding *UL DPCH to be Deleted* IEs and *DL DPCH to be Deleted* IEs.]
+
+**DL Power Control:**
+
+[FDD – If the *RL Information* IE includes the *DL Reference Power* IEs and power balancing is active, DRNS shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported, when the new configuration has been activated, according to subclause 8.3.15, using the *DL Reference Power* IE. If the CFN modulo the value of the *Adjustment Period* IE is not equal to 0, the power balancing continues with the old reference power until the end of the current adjustment period, and the updated reference power shall be used from the next adjustment period.]
+
+[FDD – If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the DRNS, the DRNC shall include the *DL Power Balancing Updated Indicator* IE in the *RL Information Response* IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.]
+
+**[TDD – DSCH Addition/Modification/Deletion:]**
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *DSCH To Add*, *DSCH To Modify* or *DSCH To Delete* IEs, then the DRNS shall use this information to add/modify/delete the indicated DSCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *DSCH To Add* IE, then the DRNS shall use the *Allocation/Retention Priority* IE, *Scheduling Priority Indicator* IE and *TrCH Source Statistics Descriptor* IE to define a set of DSCH Priority classes each of which is associated with a set of supported MAC-c/sh SDU lengths.]
+
+[TDD – The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each added DSCH.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *DSCH To Add* IE, then the DRNS may use the *Traffic Class* IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related DSCHs.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *TNL QoS* IE in the *DSCH TDD Information* IE and if ALCAP is not used, the DRNS may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *DSCH To Modify* IE, then the DRNS shall treat them each as follows:]
+
+- [TDD – The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the *Transport Layer Address* IE and the *Binding ID* IE for any new transport bearer to be established for each modified DSCH.]
+- [TDD – If the *DSCHs To Modify* IE includes the *CCTrCH ID* IE, then the DRNS shall map the DSCH onto the referenced DL CCTrCH.]
+- [TDD – If the *DSCHs To Modify* IE includes any of the *Allocation/Retention Priority* IE, *Scheduling Priority Indicator* IE or *TrCH Source Statistics Descriptor* IE, the DRNS shall use them to update the set of DSCH Priority classes each of which is associated with a set of supported MAC-c/sh SDU lengths.]
+- [TDD – If the *DSCHs To Modify* IE includes any of the *Transport Format Set* IE or *BLER* IE, the DRNS shall apply the parameters to the new configuration.]
+- [TDD – If the *DSCHs To Modify* IE includes the *Traffic Class* IE, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B for the related DSCHs.]
+- [TDD – If the *DSCHs To Modify* IE includes the *TNL QoS* IE and if ALCAP is not used, the DRNS may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.]
+
+[3.84 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD* IE in the RADIO LINK RECONFIGURATION READY message if a DSCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the *Secondary CCPCH Info TDD* IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[1.28 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK RECONFIGURATION READY message if a DSCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[7.68 Mcps TDD – The DRNC shall include the *Secondary CCPCH Info 7.68 Mcps TDD* IE in the RADIO LINK RECONFIGURATION READY message if a DSCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the *Secondary CCPCH Info 7.68 Mcps TDD* IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+[TDD – The DRNC shall include the *DSCH Initial Window Size* IE in the RADIO LINK RECONFIGURATION READY message for each DSCH, if the DRNS allows the SRNC to start transmission of MAC-c/sh SDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32].]
+
+#### [TDD USCH Addition/Modification/Deletion]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *USCH To Modify*, *USCH To Add* or *USCH To Delete* IEs, then the DRNS shall use this information to add/modify/delete the indicated USCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *USCH To Add* IE, then, the DRNS shall use the *Allocation/Retention Priority* IE, *Scheduling Priority Indicator* IE and *TrCH Source Statistics Descriptor* IE to define a set of USCH Priority classes each of which is associated with a set of supported MAC-c/sh SDU lengths.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *USCH To Add* IE, then the DRNS may use the *Traffic Class* IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related USCHs.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *USCH To Add* IE, if the *TNL QoS* IE is included and if ALCAP is not used, the DRNS may use the *TNL QoS* IE to determine the transport bearer characteristics to apply for the related USCHs.]
+
+[TDD – The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each added USCH.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes any *USCH To Modify* IE, then the DRNS shall treat them each as follows:]
+
+- [TDD – If the *USCH To Modify* IE includes any of the *Allocation/Retention Priority* IE, *Scheduling Priority Indicator* IE or *TrCH Source Statistics Descriptor* IE, the DRNS shall use them to update the set of USCH Priority classes.]
+- [TDD – If the *USCH To Modify* IE includes any of the *CCTrCH ID* IE, *Transport Format Set* IE, *BLER* IE or *RB Info* IE, the DRNS shall apply the parameters to the new configuration.]
+- [TDD – If the *USCHs To Modify* IE includes the *Traffic Class* IE, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B for the related USCHs.]
+- [3.84Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD* IE in the RADIO LINK RECONFIGURATION READY message if a USCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the *Secondary CCPCH Info TDD* IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+- [1.28Mcps TDD – The DRNC shall include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK RECONFIGURATION READY message if a USCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the *Secondary CCPCH Info TDD LCR* IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+- [7.68Mcps TDD – The DRNC shall include the *Secondary CCPCH Info 7.68Mcps TDD* IE in the RADIO LINK RECONFIGURATION READY message if a USCH is added and at least one DCH exists in the new
+
+configuration. The DRNC shall also include the *Secondary CCPCH Info 7.68Mcps TDD* IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.]
+
+- [TDD – if the *TNL QoS* IE is included and if ALCAP is not used, the DRNS may use the *TNL QoS* IE to determine the transport bearer characteristics to apply for the related USCHs.]
+- [TDD – The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the *Transport Layer Address* IE and the *Binding ID* IE for any new transport bearer to be established for each modified USCH.]
+
+#### RL Information:
+
+[FDD – If the *RL Information* IE includes the *DL DPCH Timing Adjustment* IE, the DRNS shall adjust the timing of the radio link accordingly in the new configuration. If the UE Context is configured to use F-DPCH in the downlink in the new configuration, the DRNC may include the *DL Code Information* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Setup", then the DRNS shall use the information in *F-TPICH Information* IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10], and shall include *F-TPICH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Configuration Change", then: the *F-TPICH Information To Modify* IE defines the new configuration and then:]
+
+- [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Offset* IE, the DRNS shall use this information to configure the time offset of F-TPICH, and may include the *F-TPICH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Removal", then the DRNS shall remove the configured F-TPICH for the RL.]
+
+#### HS-DSCH Setup:
+
+If the *HS-DSCH Information* IE is present in the RADIO LINK RECONFIGURATION PREPARE message, then:
+
+- The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.
+- The DRNC shall include the *HARQ Memory Partitioning* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION READY message. [FDD – The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE, or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.] [1.28Mcps TDD– The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE is included in the *HS-DSCH Information* IE.]
+- The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the RADIO LINK RECONFIGURATION READY message.
+- The DRNS may use the *Traffic Class* IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *HS-DSCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.
+- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+
+- If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the *User Plane Congestion Fields Inclusion IE* in the *HS-DSCH Information Response IE*.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Guaranteed Bit Rate IE* for a Priority Queue in the *HS-DSCH MAC-d Flows Information IE* in the *HS-DSCH Information IE*, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Discard Timer IE* for a Priority Queue in the *HS-DSCH MAC-d Flows Information IE* in the *HS-DSCH Information IE*, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended IE* for a Priority Queue in the *HS-DSCH MAC-d Flows Information IE* in the *HS-DSCH Information IE*, then the DRNS shall ignore the *SID IE* and *MAC-d PDU Size IE* in the *MAC-d PDU Size Index IE* and use *Maximum MAC-d PDU Size Extended IE* to optimise capacity allocation for the related HSDPA Priority Queue.
+- The DRNC shall include the *HS-DSCH Initial Capacity Allocation IE* in the [FDD – *HS-DSCH FDD Information Response IE*] [TDD – *HS-DSCH TDD Information Response IE*] in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32] If RADIO LINK RECONFIGURATION PREPARE message includes *HS-DSCH MAC-d PDU Size Format IE* in the *HS-DSCH Information IE* set to “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation IE* the values for the peer of *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE* to the values of the corresponding peer I in RADIO LINK RECONFIGURATION PREPARE in the *HS-DSCH MAC-d Flows Information IE* in the *HS-DSCH Information IE* for a Priority Queue including *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE*.
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SCCH Power Offset IE* in the *HS-DSCH Information IE*, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
+- [FDD – The DRNC shall include the *Measurement Power Offset IE* in the *HS-DSCH Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the *HS-SCCH Specific Information Response IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response IE*] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR IE*] [7.68 Mcps TDD – *HS-SCCH Specific Information Response 7.68 Mcps IE*] in the *HS-DSCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Preamble Mode IE* in the *HS-DSCH Information IE*, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the *HARQ Preamble Mode Activation Indicator IE* in the *HS-DSCH Information Response IE* in the RADIO LINK RECONFIGURATION READY message. If the *HARQ Preamble Mode IE* is not included or if the mode 0 is applied, then the DRNC shall not include the *HARQ Preamble Mode Activation Indicator IE* in the *HS-DSCH Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d PDU Size Format IE* in the *HS-DSCH Information IE*, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]).
+
+- [FDD – If the *MIMO Activation Indicator* IE, or the *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then:]
+ - - [FDD – The DRNS shall activate the MIMO mode, or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link.]
+ - - [FDD – The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+ - - [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up on the cell with a non-zero power offset where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [1.28 Mcps TDD – If the *MIMO Activation Indicator* IE is included in the *HS-DSCH TDD Information* IE, then:]
+ - - [1.28 Mcps TDD – The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.]
+ - - [1.28 Mcps TDD – The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d PDU Size Format* IE set to “Flexible MAC-d PDU Size” and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- [FDD – If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may use:]
+ - - [FDD – a different HS-SCCH in consecutive TTIs for this UE]
+ - - [FDD – HS-SCCH orders for the case of HS-SCCH-less operation to this UE]
+- [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the DRNS may use the supported HSDPA functions for this UE.]
+- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+- [FDD – If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
+- If the RADIO LINK RECONFIGURATION PREPARE message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
+- [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.]
+- [1.28 Mcps TDD – If the *UE TS0 Capability LCR* IE is included in the *HS-DSCH TDD Information* IE, then the DRNC may include the *TS0 HS-PDSCH Indication LCR* IE in the RADIO LINK RECONFIGURATION READY message if HS-PDSCH resources could be allocated on TS0 for the UE.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### [FDD – Secondary Serving HS-DSCH Setup:]
+
+[FDD – If the *C-ID* IE is present in the *Additional HS Cell Information RL Reconf Prep* IE in the RADIO LINK RECONFIGURATION PREPARE message, and no secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency* IEs, in the *HS-DSCH FDD Secondary Serving Information* IE or in the *HS-DSCH FDD Secondary Serving Information To Modify* IE for each instance of the *Additional HS Cell Information RL Reconf Prep* IE, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:]
+
+- [FDD – The DRNS shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- [FDD – The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *MIMO Activation Indicator* IE, or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the MIMO mode, or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+- [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up on the cell with a non-zero power offset where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+- - [FDD – If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, then the DRNC shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+- [FDD – If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, the DRNS shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to “None” the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.]
+- - [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+- - [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### Intra-DRNS Serving HS-DSCH Radio Link Change:
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-PDSCH RL ID* IE, this indicates the new Serving HS-DSCH Radio Link:
+
+The DRNS shall release the HS-PDSCH resources on the old Serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new Serving HS-DSCH Radio Link.
+
+The DRNC may include the *HARQ Memory Partitioning* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION READY message. [FDD – The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] [1.28Mcps TDD – The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.]
+
+- If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the *User Plane Congestion Fields Inclusion IE* in the *HS-DSCH Information Response IE*.
+
+The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI IE* in the RADIO LINK RECONFIGURATION READY message.
+
+If a reset of the MAC-hs is not required the DRNS shall include the *MAC-hs Reset Indicator IE* in the RADIO LINK RECONFIGURATION READY message.
+
+[FDD – The DRNC shall include the *Measurement Power Offset IE* in the *HS-DSCH Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the *HS-SCCH Specific Information Response IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response IE*] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR IE*] [7.68 Mcps TDD – *HS-SCCH Specific Information Response 7.68 Mcps IE*] in the *HS-DSCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[TDD – The DRNC shall include the [3.84 Mcps TDD – *HS-PDSCH Timeslot Specific Information IE*] [1.28 Mcps TDD – *HS-PDSCH Timeslot Specific Information LCR IE*] [7.68 Mcps TDD – *HS-PDSCH Timeslot Specific Information 7.68 Mcps IE*] in the *HS-DSCH Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+- The DRNC may include the *Transport Layer Address IE* and the *Binding ID IE* for HS-DSCH MAC-d flow in the [FDD – *HS-DSCH FDD Information Response IE*] [TDD – *HS-DSCH TDD Information Response IE*] in the RADIO LINK RECONFIGURATION READY message.
+- If the *TNL QoS IE* is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS IE* may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH Information To Modify IE* and the value is set to "allowed" or if *HS-DSCH Information To Modify IE* is not included and the UE Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new configuration, then it shall include the *SixtyfourQAM DL Usage Indicator IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- [FDD – If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO IE*.]
+- [FDD – If the power offset for S-CPICH for MIMO with four transmit antennas Request indicator and MIMO with four transmit antennas activation indicator or Dual Stream MIMO with four transmit antennas activation indicator have been configured in the new configuration and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO IE* in the *HS-DSCH FDD*
+
+*Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### [FDD – Intra-DRNS Secondary Serving HS-DSCH Radio Link Change:]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *C-ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency* IEs, in the *HS-DSCH FDD Secondary Serving Information* IE for each instance of the *Additional HS Cell Information RL Reconf Prep* IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-DRNS secondary serving HS-DSCH Radio Link change, then the *HS-PDSCH RL ID* IE indicates the new Serving HS-DSCH Radio Link:]
+
+- [FDD – The DRNS shall release the HS-PDSCH resources on the old secondary serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new secondary serving HS-DSCH Radio Link. The DRNS shall remove the old secondary serving HS-PDSCH Radio Link if no E-DCH resources are allocated to the RL. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- [FDD – The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE and the value is set to "allowed" or if *HS-DSCH FDD Secondary Serving Information To Modify* IE is not included and the UE Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+- [FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the *HS-DSCH FDD Secondary Serving Information* IE defines the new secondary serving HS-DSCH configuration in the DRNS to be used on the new secondary serving HS-DSCH Radio Link, and then:]
+ - - [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may use this
+
+value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+
+- - [FDD – If the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the MIMO mode or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas, or Dual Stream MIMO with four transmit antennas mode and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
+ - - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+ - - [FDD – If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, the DRNS shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to “None” the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.]
+- [FDD - If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured for the secondary serving HS-DSCH radio link in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- [FDD - If the Power Offset For S-CPICH for MIMO with four transmit antennas Request indicator and MIMO with four transmit antennas activation indicator or Dual Stream MIMO with four transmit antennas activation indicator have been configured for the secondary serving HS-DSCH radio link in the new configuration and MIMO with four transmit antennas Pilot Configuration is set up with a non zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [FDD – The DRNC may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+**[FDD – Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *C-ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE and an additional non serving E-DCH RL exists in the cell indicated by the *C-ID* IE, the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE indicates the new Additional Serving E-DCH Radio Link.]
+
+- [FDD – If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Serving Additional E-DCH Radio Link at the activation of the new configuration.]
+- [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS may include the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2 IE*.]
+- [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS may include the *E-RGCH/E-HICH Channelisation Code IE* and/or the *E-HICH Signature Sequence IE* and/or the *E-RGCH Signature Sequence IE* or may alternatively include the *E-RGCH Release Indicator IE* in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Link on secondary UL frequency in the DRNS. If the DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code IE* in the *E-DCH FDD DL Control Channel Information IE* then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator IE* in the *E-DCH FDD DL Control Channel Information IE*, to indicate that the *E-RGCH/E-HICH Channelisation Code IE* contains invalid data.]
+
+#### **[FDD – Additional Serving E-DCH Radio Link Change to a new RL:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Additional E-DCH RL Specific Information To Add IE* in the *Additional E-DCH Configuration Change Information IE* in the *Additional E-DCH Cell Information RL Reconf Prep IE* and the *C-ID IE* in the *Additional HS Cell Information RL Reconf Prep IE* and there is no radio links in the cell indicated by the *C-ID IE* for the UE context, the *HS-PDSCH RL ID IE* indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.]
+
+- [FDD – If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
+- [FDD – In the new configuration the DRNS shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* for the initial grant for the additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2 IE*.]
+
+- [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+### HS-DSCH Modification:
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Information To Modify IE*, then:
+
+- The DRNC shall include the *HS-DSCH Initial Capacity Allocation IE* for each HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the DRNS allows the SRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK RECONFIGURATION PREPARE message includes *HS-DSCH MAC-d PDU Size Format IE* in the *HS-DSCH Information To Modify IE* set to “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation IE* the values for the peer of *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE* to the values of the corresponding peer I in RADIO LINK RECONFIGURATION PREPARE in the *HS-DSCH Information To Modify IE* for a Priority Queue including *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE*.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Traffic Class IE* in the *HS-DSCH Information To Modify IE* for a specific HS-DSCH MAC-d flow, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the *Traffic Class IE* if the *TrCH Source Statistics Descriptor IE* for this specific HS-DSCH MAC-d flow indicates the value “RRC”.
+- If the *TNL QoS IE* is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS IE* may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Guaranteed Bit Rate IE* in the *HS-DSCH Information To Modify IE*, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Discard Timer IE* for a Priority Queue in the *HS-DSCH Information To Modify IE*, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended IE* in the *HS-DSCH Information To Modify IE*, then the DRNS shall ignore the *SID IE* and *MAC-d PDU Size IE* in the *MAC-d PDU Size Index IE* and use *Maximum MAC-d PDU Size Extended IE* to optimise capacity allocation for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Window Size IE* or *TI IE* in the *HS-DSCH Information To Modify IE*, then the DRNS shall use the indicated values in the new configuration for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-d PDU Size Index IE* in the *Modify Priority Queue* choice, the DRNS shall delete the previous list of MAC-d PDU Size Index values for the related HSDPA Priority Queue and use the MAC-d PDU Size Index values indicated in the *MAC-d PDU Size Index IE* in the new configuration.
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *CQI Feedback Cycle k IE*, the *CQI Repetition Factor IE*, the *ACK-NACK Repetition Factor IE*, the *ACK Power Offset IE*, the *NACK Power Offset IE* or the *CQI Power Offset IE* in the *HS-DSCH Information To Modify IE*, then the DRNS shall use the indicated CQI Feedback Cycle k value, the CQI Repetition Factor or the ACK-NACK Repetition Factor, ACK Power Offset, the NACK Power Offset or the CQI Power Offset in the new configuration.]
+- [FDD – If the *HS-SCCH Power Offset IE* is included in the *HS-DSCH Information To Modify IE*, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
+
+- [TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *TDD ACK NACK Power Offset* IE in the *HS-DSCH Information To Modify* IE, the DRNS shall use the indicated power offset in the new configuration.]
+- [FDD – If the *HS-DSCH Information To Modify* IE includes the *HS-SCCH Code Change Grant* IE, then the DRNS may modify the HS-SCCH codes corresponding to the HS-DSCH. The DRNC shall then report the codes which are used in the new configuration specified in the *HS-SCCH Specific Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *HS-DSCH Information To Modify* IE includes the *HS-PDSCH Code Change Grant* IE, then the DRNS may modify the HS-PDSCH codes corresponding to the HS-DSCH. The DRNC shall then report the codes which are used in the new configuration specified in the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If the concerned DRNS is not in Continuous Packet Connectivity HS-SCCH less mode, the SRNC shall not include the *HS-PDSCH Code Change Grant* IE in the *HS-DSCH Information To Modify* IE.]
+- [TDD – If the *HS-DSCH Information To Modify* IE includes the *HS-SCCH Code Change Grant* IE, then the DRNS may modify the HS-SCCH parameters corresponding to the HS-DSCH. The DRNC shall then report the values for the parameters which are used in the new configuration specified in the [3.84Mcps TDD – *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR* IE] [7.68 Mcps TDD – *HS-SCCH Specific Information Response 7.68 Mcps* IE] in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information To Modify* IE, then the DRNS shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the DRNC shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information To Modify* IE, then the DRNS shall use, in the new configuration, the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]).
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Physical Layer Category* IE in the *HS-DSCH Information To Modify* IE, the DRNS shall use this information in the new configuration.]
+- [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information To Modify* IE, then:]
+ - - [FDD – The DRNS shall activate/deactivate the MIMO mode or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link in the new configuration in accordance with the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE.]
+ - - [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is set to “Activate”, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – If the *MIMO Mode Indicator* IE is set to “Activate” and *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for*
+
+*MIMO IE in the HS-DSCH FDD Information Response IE. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]*
+
+- - [FDD – If the *MIMO with four transmit antennas Mode Indicator IE* is set to “Activate” or the *Dual Stream MIMO with four transmit antennas Mode Indicator IE* is set to “Activate” and *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator IE* is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas IE* in the *HS-DSCH FDD Information Response IE*. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas IE*.]
+- [FDD – The DRNC may include the *HARQ Memory Partitioning IE* in the RADIO LINK RECONFIGURATION READY message. The *HARQ Memory Partitioning IE* may contain the *HARQ Memory Partitioning Information Extension For MIMO IE*.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH Information To Modify IE*, then the DRNS may if the value is set to “allowed” use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH Information To Modify IE* with value set to “not allowed”, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]
+- [FDD – If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- [1.28Mcps TDD – If the *MIMO Mode Indicator IE* is included in the *HS-DSCH Information To Modify IE*, then:]
+ - - [1.28Mcps TDD – The DRNS shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in the new configuration in accordance with the *MIMO Mode Indicator IE*.]
+ - - [1.28 Mcps TDD – If the *MIMO Mode Indicator IE* is set to “Activate”, then the DRNS shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream IE* in the *HS-DSCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+- [1.28Mcps TDD – The DRNC may include the *HARQ Memory Partitioning IE* in the RADIO LINK RECONFIGURATION READY message. The *HARQ Memory Partitioning IE* may contain the *HARQ Memory Partitioning Information Extension For MIMO IE*.]
+- - [FDD – Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.]
+- - [FDD – If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
+- - If the RADIO LINK RECONFIGURATION PREPARE message includes *DL RLC PDU Size Format IE* for a Priority Queue in the *HS-DSCH Information To Modify IE*, the *DL RLC PDU Size Format IE* may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].
+- - [FDD – If the *UE Support Indicator Extension IE* is included in the *HS-DSCH Information To Modify IE* the DRNS may use the supported HSDPA functions for this UE.]
+- - [FDD - If the *UE Support Indicator Extension IE* is included in the *HS-DSCH Information To Modify IE* with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+- [FDD – If the *Single Stream MIMO Mode Indicator* IE is included in the *HS-DSCH Information To Modify* IE, then the DRNS shall activate/deactivate the Single Stream MIMO for the HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator* IE.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[FDD – Secondary Serving HS-DSCH Modification:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then:]
+
+- [FDD – If the *HS-SCCH Power Offset* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+- [FDD – If the *HS-DSCH FDD Secondary Serving Information To Modify* IE includes the *HS-SCCH Code Change Grant* IE, then the DRNS may modify the HS-SCCH codes corresponding to the secondary serving HS-DSCH. The DRNC shall then report the codes which are used in the new configuration specified in the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the DRNS shall activate/deactivate the MIMO mode or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE.]
+- [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE, is set to “Activate”, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *MIMO Mode Indicator* IE is set to “Activate” and *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- [FDD – If the *MIMO with four transmit antennas Mode Indicator* IE is set to “Activate” or the *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is set to “Activate” and *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [FDD – If the *Single Stream MIMO Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the DRNS shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator* IE.]
+- [FDD – If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary
+
+serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+- [FDD – If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, then the DRNC shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+- [FDD – If the *Diversity Mode* IE is included, then:]
+ - - [FDD – the DRNS shall apply cell specific transmit diversity configuration for the secondary serving HS-DSCH radio link according to *Diversity Mode* IE and *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information To Modify* IE,]
+ - - [FDD – If the *Diversity Mode* IE is not set to “None”, the DRNS shall apply diversity for the secondary serving HS-DSCH radio link according to the value given in the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information To Modify* IE.]
+- [FDD – If the *Non Cell Specific Tx Diversity* IE equals “Tx Diversity” is included, the DRNS shall apply non cell specific transmit diversity configuration and reconfigure the transmit diversity setting for the secondary serving HS-DSCH radio link to the same value as defined for the serving HS-DSCH radio link in the new configuration.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### [FDD – Secondary Serving HS-DSCH Removal:]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Secondary Serving Remove* IE in the *Additional HS Cell Information RL Reconf Prep* IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.]
+
+#### HS-DSCH MAC-d Flow Addition/Deletion:
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes any *HS-DSCH MAC-d Flows To Add* or *HS-DSCH MAC-d Flows To Delete* IEs, then the DRNS shall use this information to add/delete the indicated HS-DSCH MAC-d flows on the Serving HS-DSCH Radio Link. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes an *HS-DSCH MAC-d Flows To Delete* IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the UE Context, then the DRNC shall delete the HS-DSCH configuration from the UE Context and release the HS-PDSCH resources.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d Flows To Add* IE, then:
+
+- The DRNS may use the *Traffic Class* IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *HS-DSCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.
+- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- The DRNC shall include the *HS-DSCH Initial Capacity Allocation* IE in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being added, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If the UE context is configured to use the “Flexible MAC-d PDU Size” format for
+
+the HS-DSCH, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer in RADIO LINK RECONFIGURATION PREPARE message in the *HS-DSCH MAC-d Flows To Add* IE for a *Priority Queue including Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE.
+
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Guaranteed Bit Rate* IE in the *HS-DSCH MAC-d Flows To Add* IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the DRNC shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.
+- The DRNC may include the *HARQ Memory Partitioning* IE in the RADIO LINK RECONFIGURATION READY message. [FDD – The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.]
+- If the RADIO LINK RECONFIGURATION PREPARE message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, the *DL RLC PDU Size Format* IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
+
+#### [FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE the DRNS shall, if supported, preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [63]:]
+
+- - [FDD – The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION PREPARE message. The list of secondary serving HS-DSCH cells is designated by the list of *Secondary C-ID* IEs in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION PREPARE message.]
+- - [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ]
+ - - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell.]
+ - - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells.]
+- - [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ]
+- - [FDD – The DRNS shall return these codes in the *Sets of HS-SCCH Codes* IE along with the corresponding per-cell *HS-DSCH-RNTI* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK RECONFIGURATION READY.]
+- - [FDD – The DRNS shall use the first in the numbered list the primary serving HS-DSCH cell's of HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the SRNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [16].]
+
+- - [FDD – The DRNS shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION READY message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:]
+ - - [FDD – if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the HARQ Preamble Mode Activation Indicator IE.]
+ - - [FDD – if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.]
+ - - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE]
+ - - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.]
+ - - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.]
+ - - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE]
+ - - [FDD – if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfiguration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell.]
+ - - [FDD – if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell.]
+ - - [FDD – if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE.]
+ - - [FDD – if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS shall store this information in the preconfigured configuration.]
+ - - [FDD – the *SixtyfourQAM DL Support Indicator* IE may be included.]
+ - - [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS may store this information in the preconfigured configuration.]
+ - - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – the DRNS shall, if supported, include in the *Sets of HS-SCCH Codes* IE the *Measurement Power Offset* IE for each preconfigured cell.]
+- - [FDD – The DRNS shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION READY message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
+ - - [FDD – The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.]
+ - - [FDD – The DRNS may preconfigure the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.]
+
+- - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells IE* in the *HS-DSCH Preconfiguration Setup* IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where HS-DSCH / secondary HS-DSCH is preconfigured, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH Preconfiguration Info* IE or in the *Sets of HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Info* IE for each preconfigured cell in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the DRNC shall allocate resources for the preconfigured Multiflow.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the DRNC shall allocate resources for the preconfigured F-TPICH channel and include *F-TPICH Information Response* IE in the *HS-DSCH Preconfiguration Info* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the DRNC shall allocate resources for the preconfigured UL CLTD.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the DRNC shall allocate resources for the preconfigured UL MIMO.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixteen QAM.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixtyfour QAM.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Non-Serving RL Preconfiguration Setup* IE in the *RL Information* IE and:]
+
+- - [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION READY message.]
+- - [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION READY message.]
+- - [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION READY message.]
+- - [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of *new Serving RL* in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information* IE for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION READY message.]
+- - [FDD –If the *F-TPICH Information* IE is included, the DRNC shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [8], and include *F-TPICH Information Response* IE in the *Non-Serving RL Preconfiguration Info* IE.]
+
+#### [FDD – Enhanced HS Serving Cell Change:]
+
+[FDD –Upon receipt of the RADIO LINK RECONFIGURATION PREPARE message, if the Enhanced HS Serving Cell Change is preconfigured in the DRNS for the UE context, the DRNS may execute the Enhanced HS Serving Cell Change procedure according to [63].]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Enhanced HS Serving CC Abort* IE in the *HS-DSCH Information To Modify* IE or the *HS-DSCH FDD Information* IE then the DRNS shall not execute
+
+the synchronized Enhanced HS Serving Cell Change procedure when performing the Serving HS-DSCH Radio Link Change or the HS-DSCH Setup.]
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Non-Serving RL Preconfiguration Removal* IE, the DRNS shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.]
+
+#### **[FDD - Multiflow Setup:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Multiflow Information* IE in *HS-DSCH Information* IE, or *Multiflow Reconfiguration* IE in *HS-DSCH Information To Modify* IE and the choice of Setup or Change or Stop is “Setup”, then the DRNS shall setup the requested Multiflow operation.]
+
+#### **[FDD - Multiflow Modification:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *Multiflow Reconfiguration* IE in *HS-DSCH Information To Modify* IE and the choice of Setup or Change or Stop is “Change”, then the DRNS shall apply the new configuration.]
+
+#### **[FDD - Multiflow Removal:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Multiflow Reconfiguration* IE in *HS-DSCH Information To Modify* IE, and the choice of Setup or Change or Stop is “Stop”, then the DRNS shall terminate the Multiflow operation.]
+
+#### **[FDD – E-DCH Setup:]**
+
+[FDD – If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION PREPARE message then:]
+
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being “E-DCH Non-Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.]
+- [FDD – If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being “E-DCH Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
+
+- [FDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *E-DCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+- [FDD – If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Bundling Mode Indicator* IE for a E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to “Bundling” and the *E-TTI* IE is set to “2ms”, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH ReferencePower Offset* IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *SixteenQAM UL Operation Indicator* IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.]
+ - - [FDD – If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]
+
+#### **[FDD – E-DCH Radio Link Handling:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH RL Indication* IE in the *RL Information* IE:]
+
+- [FDD – The DRNC shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+- [FDD – The DRNC may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNC may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control*
+
+*Channel Information* IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+
+- [FDD – The DRNC shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the *E-DCH RL Indication* IE set to “Non E-DCH”, in the *RL Information* IE.]
+- [FDD – For each RL for which the *E-DCH RL Indication* IE is set to “E-DCH”, and which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the *E-DCH RL Set ID* IE in the RADIO LINK RECONFIGURATION READY message. The value of the *E-DCH RL Set ID* IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
+
+#### [FDD – Serving E-DCH Radio Link Change:]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Serving E-DCH RL ID* IE, this indicates the new Serving E-DCH Radio Link:]
+
+- [FDD – If the old Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link at the activation of the new configuration.]
+- [FDD – If the new Serving E-DCH RL is within this DRNS:]
+ - - [FDD – the DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *RL Information Response* IE for the indicated RL in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – The DRNS may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the new serving E-DCH RL.]
+ - - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – If a serving cell change is performed the RADIO LINK RECONFIGURATION READY message may contain invalid data (see 9.2.2.4C).]
+ - - [FDD – The DRNS may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK RECONFIGURATION READY message for the new serving E-DCH RL.]
+- [FDD – The DRNS may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Links in the DRNS.]
+- [FDD – If the DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE, to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+
+#### [FDD – E-DCH Modification:]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH FDD Information To Modify* IE, then:]
+
+- [FDD – If the *E-DCH FDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the DRNS shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d PDU Size Format* IE in the *E-DCH FDD Information To Modify* IE, then the DRNS shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+
+- [FDD – If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [FDD –If the *Traffic Class* IE is included for an E-DCH MAC-d flow then the DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE for this specific E-DCH MAC-d flow indicates the value “RRc”.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Data Description Indicator* IE, the DRNC shall use the DDI values indicated in the *Data Description Indicator* IE in the new configuration.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH FDD Information To Modify* IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information To Modify* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow in the *E-DCH FDD Information To Modify* IE, then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH HARQ Power Offset FDD* IE in the *E-DCH FDD Information To Modify* IE for an E-DCH MAC-d flow the DRNS shall use this information for calculating the unquantised gain factor for an E-TFC ( $\beta_{ed,j,uq}$ ) as defined in TS 25.214 [10].]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Grant Type and it is indicated as being “E-DCH Non-Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Grant Type and it is indicated as being “E-DCH Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the DRNS shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Logical Channel To Modify* IE, the DRNS shall use this information to modify the indicated logical channels:
+ - - [FDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the DRNS shall apply the values in the new configuration.]
+ - - [FDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the DRNS shall apply the values in the new configuration.]
+ - - [FDD – If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the DRNS shall apply the value in the new configuration.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information To Modify* IE and the *Bundling Mode Indicator* IE is set to “Bundling” and the *E-TTI* IE is set to
+
+“2ms”, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
+
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH ReferencePower Offset* IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-e Reset Indicator* IE in the *E-DCH FDD Information To Modify* IE, then the DRNS shall use this value to determine whether MAC-e(or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *SixteenQAM UL Operation Indicator* IE in the *E-DCH FDD Information To Modify* IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE]
+ - - [FDD – If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH DL Control Channel Grant Information* IE in the *E-DCH FDD Information To Modify* IE, the DRNS may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the *E-DCH RL ID* IE. The DRNC shall then report the modified configuration which is used in the new configuration specified in the *E-DCH FDD DL Control Channel Information* IE for each E-DCH RL in the RADIO LINK RECONFIGURATION READY message.]
+
+**[FDD – E-DCH MAC-d Flow Addition:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Add* IE, then the DRNS shall use this information to add the indicated E-DCH MAC-d flows.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH MAC-d Flows To Add* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flows To Add* IE, then:]
+
+- [FDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *E-DCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
+
+#### **[FDD – E-DCH MAC-d Flow Deletion:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Delete* IEs, then the DRNS shall use this information to delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration shall also be removed.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNC shall delete the E-DCH configuration from the UE Context and release the E-DCH resources.]
+
+#### **[FDD – Additional E-DCH Setup:]**
+
+[FDD – If the *Additional E-DCH Cell Information RL Reconf Prep* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is “Setup”, then the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:]
+
+- [FDD – If the *C-ID* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *C-ID* IE indicates the cell in which the additional E-DCH shall be setup.
+ - - [FDD – The DRNS shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.]
+- [FDD – If the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *E-DCH Additional RL ID* IE indicates the existing RL on which the Additional E-DCH shall be setup.
+ - - [FDD – The DRNS shall setup the additional E-DCH on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.]
+- [FDD – The DRNS shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – If the *UL SIR Target* IE in the *UL DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE and/or the *DL Power Balancing Information*
+
+IE and/or the *Minimum Reduced E-DPDCH Gain Factor* IE in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE are present, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+
+- [FDD – If the *Secondary UL Frequency Activation State* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
+- [FDD – If the *Initial DL Tx Power* IE, the *Primary CPICH Ec/No* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Enhanced Primary CPICH Ec/No* IE is included in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH Secondary RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *F-DPCH Slot Format Support Request* IE in the *F-DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO RECONFIGURATION READY message. If the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE includes the *F-DPCH Slot Format* IE, the DRNS may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+- [FDD – If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Processing Overload Level* IE are present in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION PREPARE message is supported by the DRNS, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+- [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message and if DRNS has no valid data for
+
+the *E-RGCH/E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+
+- [FDD – If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:]
+ - - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message.]
+ - - [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.]
+ - - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used” in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Secondary CPICH Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message. If the DRNS doesn’t include the *Secondary CPICH Information* IE, it shall not include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used”.]
+
+#### [FDD – Additional E-DCH Configuration Change]
+
+[FDD – If the *Additional E-DCH Cell Information RL Reconf Prep* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is “Configuration Change”, then the *Additional E-DCH Cell Information Configuration Change* IE defines the new configuration and then:]
+
+- [FDD – If the *UL Scrambling Code* IE and/or the *UL SIR Target* IE are present in the *UL DPCH Information* IE in the *Additional E-DCH Configuration Change Information* IE and/or if the *Minimum Reduced E-DPDCH Gain Factor* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH Configuration Change Information* IE, the DRNS shall use the information in the same way as for the information that is used on the Primary uplink frequency.]
+- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *F-DPCH Information* IE in the *Additional E-DCH Configuration Change Information* IE, then:]
+ - - [FDD – The DRNS shall configure the concerned UE Context to use F-DPCH in the downlink in the new configuration.]
+ - - [FDD – If the *F-DPCH Information* IE includes the *F-DPCH Slot Format Support Request* IE, then the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the *Additional E-DCH FDD Information Response* IE for new RLs on the secondary UL frequency or in the *Additional Modified E-DCH FDD Information Response* IE for modified RLs in the RADIO LINK RECONFIGURATION READY message. If the *Multicell E-DCH Information* IE in the *Additional E-DCH Configuration Change Information* IE includes the *F-DPCH Slot Format* IE, the DRNS may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+
+#### [FDD – Additional E-DCH RL Addition:]
+
+[FDD – If the *Additional E-DCH RL Specific Information To Add* IE is present in the *Additional E-DCH Configuration Change Information* IE, then:]
+
+- - [FDD – The DRNS shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the *E-DCH Additional RL ID* IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- - [FDD – If the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE, the *E-HICH Power Offset* IE is included, the DRNS shall use the information in the same way as for information is used on the Primary uplink frequency.]
+- - [FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Individual” in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION PREPARE message includes the *DL Reference Power* IE in the *Multicell E-DCH RL Specific Information* IE, the DRNS shall activate the power balancing and use the *DL Reference Power* IE for the power balancing procedure in the new Additional RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION PREPARE message at RL addition on secondary UL frequency is supported, according to subclause 8.3.15. In this case, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{init}$ shall be set to the power level which is calculated based on the following IEs (if received): *Primary CPICH Ec/No* IE or the *Enhanced Primary CPICH Ec/No* IE in the *Multicell E-DCH RL Specific Information* IE or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing Additional RLs.]
+- - [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+- - [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+- - [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message]
+- - [FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Add* IE, the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message and if DRNS has no valid data for the *E-RGCH/ E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH/ E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/ E-HICH Channelisation Code* IE contains invalid data.]
+
+- [FDD – If the *Primary CPICH Ec/No* IE or the *Primary CPICH Ec/No* IE and the *Enhanced Primary CPICH Ec/No* IE in the *Multicell E-DCH RL Specific Information* IE measured by the UE are included for a RL in the RADIO LINK RECONFIGURATION PREPARE message, the DRNS shall use this in the calculation of the Initial DL TX Power for this additional RL. If the *Primary CPICH Ec/No* IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]
+
+**[FDD – Additional E-DCH RL Modification:]**
+
+[FDD – If the *Additional E-DCH RL Specific Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then the RL indicated by the *E-DCH Additional RL ID* IE indicates the RL on which E-DCH resources shall be modified:]
+
+- [FDD – If the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE, the *E-HICH Power Offset* IE, and/or the *E-DCH DL Control Channel Grant* IE in the *Multicell E-DCH RL Specific Information* IE is included, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.]
+- [FDD – If the *DL Reference Power* IEs is included in the *Multicell E-DCH RL Specific Information* IE and power balancing is active, DRNS shall apply DL power Control in the same way as defined for the Primary uplink frequency.]
+- [FDD – If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the DRNS, the DRNS shall include the *DL Power Balancing Updated Indicator* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – If the *Phase Reference Update Indicator* IE is included in the *Multicell E-DCH RL Specific Information* IE, DRNS shall modify the channel estimation information according to TS 25.214 [10] subclause 4.3.2.1 and set the value(s) in *Primary CPICH Usage For Channel Estimation* IE and/or *Secondary CPICH Information Change* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message accordingly.]
+- [FDD – If the RADIO LINK RECONFIGURATION READY message includes the *Primary CPICH Usage For Channel Estimation* IE and/or the *Secondary CPICH Information Change* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE, the DRNS shall avoid the new configuration in which neither the Primary CPICH nor the Secondary CPICH is used as a Phase Reference for this Radio Link.]
+
+**[FDD – Additional E-DCH Modification:]**
+
+[FDD – If the *Additional E-DCH FDD Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then:]
+
+- [FDD – If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Maximum Bitrate* IE is included, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the *E-DCH Processing Overload Level* IE is included, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the RNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the DL TX power upper or lower limit has been re-configured for the secondary UL frequency, the DRNS shall include the new value(s) in the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s), and the DRNS shall include in the RADIO LINK RECONFIGURATION READY message the *Maximum Uplink SIR* IE and *Minimum Uplink SIR* IE in the *Additional Modified E-DCH FDD*
+
+*Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE for each Radio Link when these values are changed.]
+
+- [FDD – If the Additional E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional Modified E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[FDD – Additional E-DCH Removal]**
+
+[FDD – If the *Additional E-DCH Cell Information RL Reconf Prep* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is “Removal”, then the additional E-DCH on the secondary uplink frequency shall be removed.]
+
+#### **[1.28Mcps TDD – Uplink Synchronisation Parameters LCR:]**
+
+[1.28Mcps TDD –If the *Uplink Synchronisation Parameters LCR* IE is present, the DRNC shall use the indicated values of *Uplink synchronisation stepsize* IE and *Uplink synchronisation frequency* IE when evaluating the timing of the UL synchronisation.]
+
+#### **[1.28Mcps TDD – Shared physical channels Synchronisation Detection:]**
+
+[1.28Mcps TDD – If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall include the *Out-of-sync Detection Window* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[1.28Mcps TDD – Uplink Timing Advance Control LCR:]**
+
+[1.28Mcps TDD – The DRNC shall include the *Uplink Timing Advance Control LCR* IE in the RADIO LINK RECONFIGURATION READY message, if the Uplink Timing Advance Control parameters have been changed.]
+
+#### **[1.28Mcps TDD – PowerControl GAP:]**
+
+[1.28Mcps TDD – If applied in the DRNS, the DRNC may include the *PowerControl GAP* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[1.28Mcps TDD – E-UTRAN Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Need for Idle Interval* IE set to “TRUE”, if supported, the DRNC shall include the *Idle Interval Information* IE in the RADIO LINK RECONFIGURATION READY message. If the *Need for Idle Interval* IE is set to “FALSE”, the DRNC shall delete the configuration related to E-UTRAN Inter-RAT measurement ]
+
+#### **[1.28Mcps TDD – RNTI Allocation Indicator:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *RNTI Allocation Indicator* IE, if supported, the DRNS may allocate an E-RNTI and/or an H-RNTI for UE to use in CELL\_FACH state.]
+
+#### **[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *DCH Measurement Type indicator* IE, if supported, the DRNS shall include the *Measurement purpose* IE and the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE in the RADIO LINK RECONFIGURATION READY message to configure the measurement occasion pattern(s) indicated by the *DCH Measurement Type indicator* IE.]
+
+#### **[TDD – DSCH RNTI Addition/Deletion:]**
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *PDSCH RL ID* IE, then the DRNS shall use it as the new RL identifier for PDSCH and PUSCH.]
+
+- [TDD – If the indicated PDSCH RL ID is in the DRNS and there was no DSCH-RNTI allocated to the UE Context, the DRNC shall allocate a DSCH-RNTI to the UE Context and include the *DSCH-RNTI* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [TDD – If the indicated PDSCH RL ID is in the DRNS and there was a DSCH-RNTI allocated to the UE Context, the DRNC shall allocate a new DSCH-RNTI to the UE Context, release the old DSCH-RNTI and include the *DSCH-RNTI* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [TDD – If the indicated PDSCH RL ID is not in the DRNS and there was a DSCH-RNTI allocated to the UE Context, the DRNC shall release this DSCH-RNTI.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes a *DSCHs To Delete* IE and/or a *USCHs To Delete* IE which results in the deletion of all DSCH and USCH resources for the UE Context, then the DRNC shall release the DSCH-RNTI allocated to the UE Context, if there was one.]
+
+#### **[FDD – Phase Reference Handling:]**
+
+[FDD – If Primary CPICH usage for channel estimation information has been reconfigured, the DRNC shall include the *Primary CPICH Usage For Channel Estimation* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD – If Secondary CPICH information for channel estimation has been reconfigured, the DRNC shall include the *Secondary CPICH Information Change* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes *Phase Reference Update Indicator* IE, DRNC shall modify the channel estimation information according to TS 25.214 [10] subclause 4.3.2.1 and set the value(s) in *Primary CPICH Usage For Channel Estimation* IE and/or *Secondary CPICH Information Change* IE in the RADIO LINK RECONFIGURATION READY message accordingly.]
+
+[FDD – If the RADIO LINK RECONFIGURATION READY message includes the *Primary CPICH Usage For Channel Estimation* IE and/or the *Secondary CPICH Information Change* IE, the DRNC shall avoid the new configuration in which neither the Primary CPICH nor the Secondary CPICH is used as a Phase Reference for this Radio Link.]
+
+#### **[FDD – Fast Reconfiguration:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Fast Reconfiguration Mode* IE, the DRNS shall, if supported, and if it is possible to base the synchronization of the reconfiguration on the detection of the change in the uplink scrambling code for this reconfiguration, include the *Fast ReconfigurationPermission* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### **[TDD – Intra- DRNS Serving E-DCH Radio Link Change:]**
+
+TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Serving RL* IE, this indicates the new Serving E-DCH Radio Link:]
+
+- [TDD – In the new configuration the DRNS shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.]
+- [3.84Mcps TDD – The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response* IE in the *E-DCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [1.28Mcps TDD – The DRNS shall allocate E-AGCH parameters and E-HICH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response* IE and the *E-HICH Specific Information Response* IE in the *E-DCH Information Response 1.28Mcps* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [7.68Mcps TDD – The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response 7.68Mcps* IE in the *E-DCH TDD Information Response 7.68Mcps* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [TDD – If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+
+#### **[TDD – E-PUCH Handling:]**
+
+[3.84Mcps TDD and 7.68Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-PUCH Information* IE, the DRNS shall apply the parameters to the new configuration.]
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-PUCH Information LCR* IE, the DRNS shall apply the parameters to the new configuration.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes an *E- TFCS Information* IE, the DRNS shall apply the beta parameters to the new configuration.]
+
+#### **[3.84Mcps TDD – E-DCH Setup:]**
+
+[3.84Mcps TDD – the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE and *E-DCH TDD Information* IE.]
+
+#### **[1.28Mcps TDD – E-DCH Setup:]**
+
+[1.28cps TDD – the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information LCR* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE and *E-DCH TDD Information LCR* IE.]
+
+[1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]
+
+#### **[7.68Mcps TDD – E-DCH Setup:]**
+
+[7.68Mcps TDD – the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE and *E-DCH TDD Information 7.68Mcps* IE.]
+
+#### **[TDD- E-DCH MAC-d Flow Addition/Deletion:]**
+
+[TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes any *E-DCH MAC-d Flows To Add* or *E-DCH MAC-d Flows To Delete* IEs, then the DRNS shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH MAC-d Flows To Add* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.]
+
+[TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNS shall delete the E-DCH configuration from the UE Context and release the E-DCH resources.]
+
+[TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flows To Add* IE, then:]
+
+- [TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [1.28Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Maximum Bit Rate LCR* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+
+#### **[3.84Mcps TDD – E-DCH Non-scheduled allocations:]**
+
+[3.84Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information TDD* IE in the *E-DCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+**[1.28Mcps TDD – E-DCH Non-scheduled allocations:]**
+
+[1.28Mcps – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information LCR TDD* IE in the *E-DCH Information Response 1.28Mcps* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+**[7.68Mcps TDD – E-DCH Non-scheduled allocations:]**
+
+[7.68Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information 7.68Mcps TDD* IE in the *E-DCH Information Response 7.68Mcps* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+**[TDD – E-DCH Modification:]**
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH TDD Information To Modify* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.]
+
+[TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d PDU Size Format* IE in the *E-DCH TDD Information To Modify* IE, then the DRNS shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+
+**[3.84Mcps TDD – E-DCH Modification:]**
+
+[3.84Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH TDD Information* IE, then:]
+
+- [3.84Mcps TDD – If the *E-DCH TDD Information* IE includes the *E-DCH TDD Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [3.84Mcps TDD – If the *E-DCH TDD Information* IE includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [3.84Mcps TDD – If the *E-DCH TDD Information* IE includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+
+**[1.28Mcps TDD – E-DCH Modification:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH TDD Information LCR* IE, then:]
+
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *E-DCH Processing Overload Level* IE for an E-DCH, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *Maximum Number of Retransmission for Scheduling Info LCR* IE and the *E-DCH Retransmission timer for Scheduling Info LCR* IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *Multi-Carrier E-DCH Physical Layer Category LCR* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
+- [1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]
+
+#### [7.68Mcps TDD – E-DCH Modification:]
+
+[7.68Mcps TDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH TDD Information 7.68Mcps* IE, then:]
+
+- [7.68Mcps TDD – If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [7.68Mcps TDD – If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [7.68Mcps TDD – If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+
+[TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH TDD Information To Modify* IE, then:]
+
+- [TDD- If the *E-DCH TDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the DRNS shall apply the new *Allocation/Retention Priority* to this E-DCH in the new configuration according to Annex A.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE contains a *TNL QoS* IE for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information To Modify* IE includes the *E-DCH MAC-d Flow Retransmission Timer* IE for an E-DCH MAC-d flow then the DRNS shall use this information to set the retransmission timer.]
+- - [TDD– If the *TNL QoS* IE is included in the *E-DCH TDD Information to Modify* IE for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH HARQ Power Offset TDD* IE for an E-DCH MAC-d flow the DRNS shall use this new power offset value.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE contains the *E-DCH Grant Type* IE, the DRNS shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.]
+
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the DRNS shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Logical Channel To Modify* IE, the DRNS shall use this information to modify the indicated logical channels:]
+ - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the DRNS shall apply the values in the new configuration.]
+ - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the DRNS shall apply the values in the new configuration.]
+ - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Guaranteed Bit Rate* IE, the DRNS shall apply the values in the new configuration.]
+ - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *E-DCH DDI Value* IE, the DRNS shall apply the values in the new configuration.]
+ - [1.28Mcps TDD – If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Maximum Bit Rate LCR* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+ - [TDD – If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the DRNS shall apply the value in the new configuration.]
+- [TDD– If the *E-DCH TDD Information To Modify* IE includes the *MAC-e Reset Indicator* IE, then the DRNS shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]
+
+#### [1.28Mcps TDD –Multi-Carrier E-DCH Continue:]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.]
+
+#### [1.28Mcps TDD – Multi-Carrier E-DCH Setup:]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Setup", then the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:]
+
+- [1.28Mcps TDD - The DRNS shall use the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE to decide the transport bearer mode in the new configuration.]
+- [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+
+#### [1.28Mcps TDD – Multi-Carrier E-DCH Change:]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Change", then: the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:]
+
+- [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is different from current configured frequencies, then the DRNS shall setup the E-DCH resources, as requested in the DRNS Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+- [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is the same as any current configured frequency, then the DRNS shall reconfigure the E-DCH resources, as requested or as configured in the DRNS Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Change" and the *Removal*
+
+*UL Multi-Carrier info* IE is included, then the DRNS shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the *UARFCN* IE in the *Removal UL Multi-Carrier info* IE.]
+
+## General
+
+If the requested modifications are allowed by the DRNC and the DRNC has successfully reserved the required resources for the new configuration of the Radio Link(s), it shall respond to the SRNC with the RADIO LINK RECONFIGURATION READY message. When this procedure has been completed successfully there exists a Prepared Reconfiguration, as defined in subclause 3.1.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Layer Address* IE and *Binding ID* IE in the [TDD – *DSCHs To Modify* IE, *DSCHs To Add* IE, *USCHs To Modify* IE, *USCHs To Add* IE], *HS-DSCH Information* IE, *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE, [FDD – *RL Specific E-DCH Information* IE,] [TDD – *E-DCH MAC-d Flows to Add* IE,] [TDD – *E-DCH TDD Information to Modify* IE,] or in the *RL Specific DCH Information* IEs, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included], *HS-DSCH MAC-d* flow being added or *E-DCH MAC-d* flow [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included] being added, or any Transport Channel, *HS-DSCH MAC-d* flow or *E-DCH MAC-d* flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE.
+
+The DRNC shall include in the RADIO LINK RECONFIGURATION READY message the *Transport Layer Address* IE and the *Binding ID* IE for any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included], *HS-DSCH MAC-d* flow being added or *E-DCH MAC-d* flow [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included] being added, or any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included], *HS-DSCH MAC-d* flow or *E-DCH MAC-d* flow [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included] being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iur interface, the *Transport Layer Address* IE and the *Binding ID* IE in the *DCH Information Response* IE shall be included [FDD – if the *Transport Bearer Not Requested Indicator* IE is not included for the corresponding DCH,] for only one of the DCHs in the set of co-ordinated DCHs.
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer Shall not be Established” for a DCH or an *E-DCH MAC-d* flow, then the DRNC shall not establish a transport bearer for the concerned DCH or *E-DCH MAC-d* flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or *E-DCH MAC-d* flow in the RADIO LINK RECONFIGURATION READY message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer may not be Established” for a DCH or an *E-DCH MAC-d* flow and:]
+
+- [FDD – if the DRNC establishes a transport bearer for the concerned DCH or *E-DCH MAC-d* flow, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH or *E-DCH MAC-d* flow being established.]
+- [FDD – if the DRNC does not establish a transport bearer for the concerned DCH or *E-DCH MAC-d* flow, the DRNC shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or *E-DCH MAC-d* flow in the RADIO LINK RECONFIGURATION READY message.]
+
+In the case of a Radio Link being combined with another Radio Link within the DRNS, the *Transport Layer Address* IE and the *Binding ID* IE in the *DCH Information Response* IE shall be included for only one of the combined Radio Links [FDD – if the *Transport Bearer Not Requested Indicator* IE is not included for this DCH of the Radio Link].
+
+[FDD – In the case of an *E-DCH RL* being combined with another *E-DCH RL* within the DRNS, the *E-DCH FDD Information Response* IE shall be included only for one of the combined *E-DCH RLs*.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Additional E-DCH Cell Information RL Reconf Prep* IE, then:]
+
+- [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “Separate Iur Transport Bearer Mode” the DRNS shall use this mode in the new configuration and apply separate transport bearers for the *MAC-d* flows.]
+
+- [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “UL Flow Multiplexing Mode” the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
+- [FDD – if Separate Iur Transport Bearer Mode is used in the new configuration, then:]
+ - - [FDD – the DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Not Requested Indicator* IE in the *RL Specific E-DCH Information* IE in the *RL Information* IE and/or the *Transport Bearer Request Indicator* IE in the *E-DCH FDD Information To Modify* IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.]
+ - - [FDD – If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE or in the *Additional E-DCH RL Specific Information To Add* IE and/or the *Additional E-DCH RL Specific Information To Modify* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information Configuration Change* IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MAC-d flow the DRNS shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION READY message in the *Additional E-DCH Cell Information Response RLReconf* IE the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE for new E-DCH radio links on the Secondary UL frequency and/or include the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional Modified E-DCH FDD Information Response* IE for radio links on the Secondary UL frequency that has been modified.]
+
+[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Multi-Carrier E-DCH Information Reconf* IE, then:]
+
+- [1.28Mcps TDD - If the *Multi-carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iur Transport Bearer Mode" the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "UL Flow Multiplexing Mode" the DRNS shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.]
+- [1.28Mcps TDD - If the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf* IE is "Setup" and the Separate Iur transport bearer mode is used in the new configuration, or if the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf* IE is "Change" and the Transport Bearer Mode is changed to "Separate Iur Transport Bearer Mode" indicated by *Multi-carrier E-DCH Transport Bearer Mode LCR* IE, then the DRNS shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+- [1.28Mcps TDD - The DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Request Indicator* IE in the *E-DCH TDD Information to Modify* IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.]
+- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the *Transport Bearer Request Indicator* IE is set to " Bearer Requested ", then the DRNS shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response 1.28Mcps* IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+
+Any allowed rate for the uplink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall
+
+include in the RADIO LINK RECONFIGURATION READY message the *Allowed UL Rate* IE in the *DCH Information Response* IE for this Radio Link.
+
+Any allowed rate for the downlink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the *Allowed DL Rate* IE in the *DCH Information Response* IE for this Radio Link.
+
+The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s) and the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the *Maximum Uplink SIR* IE and *Minimum Uplink SIR* IE for each Radio Link when these values are changed.
+
+[FDD – If the DL TX power upper or lower limit has been re-configured, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE respectively. The DRNS shall not transmit with a higher power than indicated by the *Maximum DL TX Power* IE or lower than indicated by the *Minimum DL TX Power* IE on any DL DPCH or on the F-DPCH of the RL –except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the $\delta P_{curr}$ , as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
+
+[3.84 Mcps TDD and 7.68 Mcps TDD – If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the RADIO LINK RECONFIGURATION READY message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the new value(s) for that CCTrCH in the *CCTrCH Maximum DL TX Power* IE and *CCTrCH Minimum DL TX Power*. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power* IE/*CCTrCH Maximum DL TX Power* IE or lower than indicated by the appropriate *Minimum DL TX Power* IE/*CCTrCH Minimum DL TX Power* IE on any DL DPCH within each CCTrCH of the RL.]
+
+[1.28 Mcps TDD – If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the RADIO LINK RECONFIGURATION READY message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the new value(s) for that timeslot in the *Maximum DL TX Power* IE and *Minimum DL TX Power* within the *DL Timeslot Information LCR* IE. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power* IE or lower than indicated by the appropriate *Minimum DL TX Power* IE on any DL DPCH within each timeslot of the RL.]
+
+[TDD – If the [3.84 Mcps TDD and 7.68 Mcps TDD – *DL Time Slot ISCP Info* IE][1.28 Mcps TDD – *DL Time Slot ISCP Info LCR* IE] is present, the DRNS should use the indicated values when deciding the Initial DL TX Power.]
+
+[TDD – If the *Primary CCPCH RSCP Delta* IE is included, the DRNS shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP Delta* IE. If the *Primary CCPCH RSCP Delta* IE is not included and the *Primary CCPCH RSCP* IE is included, the DRNS shall assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP* IE. The DRNS shall use the indicated values when deciding the Initial DL TX Power.]
+
+### 8.3.4.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: Unsuccessful Operation
+ SRNC->>DRNC: RADIO LINK RECONFIGURATION PREPARE
+ DRNC-->>SRNC: RADIO LINK RECONFIGURATION FAILURE
+
+```
+
+Sequence diagram showing the Unsuccessful Operation of the Synchronised Radio Link Reconfiguration Preparation procedure. The diagram shows two vertical lines representing the SRNC (left) and DRNC (right). A solid arrow labeled 'RADIO LINK RECONFIGURATION PREPARE' points from the SRNC to the DRNC. A dashed arrow labeled 'RADIO LINK RECONFIGURATION FAILURE' points from the DRNC back to the SRNC.
+
+**Figure 11: Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation**
+
+If the DRNS cannot reserve the necessary resources for all the new DCHs of a set of co-ordinated DCHs requested to be added, it shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed.
+
+If the requested Synchronised Radio Link Reconfiguration Preparation procedure fails for one or more RLs, the DRNC shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC, indicating the reason for failure for each failed radio link in a *Cause* IE.
+
+[FDD – If the *MIMO Activation Indicator* IE is included and the *Power Offset For S-CPICH for MIMO Request Indicator* IE is not included in the *HS-DSCH FDD Information* IE in the *HS-DSCH FDD Information* IE in the RADIO LINK RECONFIGURATION PREPARE message or MIMO is activated and the power offset for S-CPICH for MIMO Request indicator has not been configured in the new configuration but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link, and/or activation of MIMO, shall be reported as failed and the DRNC shall include in the RADIO LINK RECONFIGURATION FAILURE message the *Cause* IE.]
+
+[FDD – If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included and the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is not included in the *HS-DSCH FDD Information* IE in the *HS-DSCH FDD Information* IE in the RADIO LINK RECONFIGURATION PREPARE message or MIMO with four transmit antennas is activated and the power offset for S-CPICH for MIMO with four transmit antennas Request indicator has not been configured in the new configuration but MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link, and/or activation of MIMO, shall be reported as failed and the DRNC shall include in the RADIO LINK RECONFIGURATION FAILURE message the *Cause* IE.]
+
+Typical cause values are:
+
+#### Radio Network Layer Causes:
+
+UL Scrambling Code Already in Use;
+DL Radio Resources not Available;
+UL Radio Resources not Available;
+Requested Configuration not Supported;
+Number of DL Codes not Supported;
+Number of UL Codes not Supported;
+Dedicated Transport Channel Type not Supported;
+DL Shared Channel Type not Supported;
+[TDD – UL Shared Channel Type not Supported;]
+[FDD – UL Spreading Factor not Supported;]
+[FDD – DL Spreading Factor not Supported;]
+CM not Supported;
+RL Timing Adjustment not Supported;
+E-DCH not supported;
+[FDD – F-DPCH not supported;]
+[FDD – Continuous Packet Connectivity DTX-DRX operation not Supported;]
+[FDD – Continuous Packet Connectivity HS-SCCH less operation not Supported;]
+[FDD – MIMO not supported;]
+[FDD – E-DCH TTI2ms not supported;]
+[FDD – Continuous Packet Connectivity DTX-DRX operation not available;]
+[FDD – Continuous Packet Connectivity UE DTX Cycle not available;]
+[FDD – MIMO not available;]
+[FDD – SixteenQAM UL not Supported;]
+HS-DSCH MAC-d PDU Size Format not supported;
+[FDD – F-DPCH Slot Format operation not supported;]
+E-DCH MAC-d PDU Size Format not available;
+[FDD – E-DPCCH Power Boosting not supported;]
+[FDD – SixtyfourQAM DL and MIMO Combined not available;]
+[FDD – Multi Cell operation not available;]
+[FDD – Multi Cell operation not supported;]
+[FDD – SixtyfourQAM DL and MIMO Combined not supported;]
+[1.28Mcps TDD- MIMO not supported;]
+[1.28Mcps TDD – MIMO not available;]
+[1.28Mcps TDD – SixtyfourQAM DL and MIMO Combined not available;]
+[FDD – TX diversity for MIMO UE on DL Control Channels not available;]
+[FDD – Single Stream MIMO not supported;]
+[FDD – Single Stream MIMO not available;]
+[FDD – Multi Cell operation with MIMO not available;]
+[FDD – Multi Cell operation with MIMO not supported;]
+[FDD – Multi Cell E-DCH Operation not supported;]
+
+[FDD – Multi Cell E-DCH Operation not available;]
+ [FDD – Multi Cell operation with Single Stream MIMO not available;]
+ [FDD – Multi Cell operation with Single Stream MIMO not supported;]
+ [FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available;]
+ [FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported;]
+ [FDD – Uplink Closed Loop Transmit Diversity Operation Not Available;]
+ [FDD – Uplink Closed Loop Transmit Diversity Operation Not Supported;]
+ [FDD – MIMO with four transmit antennas not supported;]
+ [FDD – MIMO with four transmit antennas not available;]
+ [FDD – Dual Stream MIMO with four transmit antennas not supported;]
+ [FDD – Dual Stream MIMO with four transmit antennas not available;]
+ [FDD – SixtyfourQAM UL not Available;]
+ [FDD – SixtyfourQAM UL not Supported;]
+ [FDD – UL MIMO Operation Not Available;]
+ [FDD – UL MIMO Operation Not Supported;]
+ [FDD – UL MIMO and SixteenQAM Operation Not Available;]
+ [FDD – UL MIMO and SixteenQAM Operation Not Supported;]
+ [FDD – UL MIMO and SixtyfourQAM Operation Not Available;]
+ [FDD – UL MIMO and SixtyfourQAM Operation Not Supported;]
+ [FDD – Multiflow Operation Not Available;]
+ [FDD – Multiflow Operation Not Supported.]
+
+#### Miscellaneous Causes:
+
+Control Processing Overload;
+ Not enough User Plane Processing Resources.
+
+### 8.3.4.4 Abnormal Conditions
+
+If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC.
+
+If more than one DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to “selected” [TDD – or no DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to “selected”] the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes a *DCHs To Modify* IE or *DCHs To Add* IE with multiple *DCH Specific Info* IEs, and if the DCHs in the *DCHs To Modify* IE or *DCHs To Add* IE do not have the same *Transmission Time Interval* IE in the *Semi-static Transport Format Information* IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the *RL Information* IE includes the *DL Reference Power* IE, but the power balancing is not active in the indicated RL(s), the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value “Power Balancing status not compatible”.]
+
+[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Common” in the existing RL(s) but the RADIO LINK RECONFIGURATION PREPARE message includes more than one *DL Reference Power* IE, the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value “Power Balancing status not compatible”.]
+
+If the RADIO LINK RECONFIGURATION PREPARE message contains the *Transport Layer Address* IE or the *Binding ID* IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added, or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE., and not both are present for a transport bearer intended to be established, the DRNC shall reject the Synchronised Radio Link Reconfiguration Preparation procedure and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE or *HS-DSCH MAC-d Flows To Delete* IE in addition to the *HS-DSCH*
+
+*Information IE*, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *HS-DSCH Information To Modify IE*, *HS-DSCH MAC-d Flows To Add IE*, *HS-DSCH MAC-d Flows To Delete IE* or *HS-PDSCH RL ID IE* and the Serving HS-DSCH Radio Link is not in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Information IE* and does not include the *HS-PDSCH RL-ID IE*, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Information To Modify IE* deleting the last remaining Priority Queue of an HS-DSCH MAC-d Flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-PDSCH RL-ID IE* indicating a Radio Link not existing in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *HS-DSCH Information IE*, *HS-DSCH Information To Modify IE*, or *HS-DSCH MAC-d Flows To Add IE* and if in the new configuration the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID IE* have the same *Scheduling Priority Indicator IE* value, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Indexed MAC-d PDU Size” for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Flexible MAC-d PDU Size” for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Fixed MAC-d PDU Size” for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Flexible MAC-d PDU Size” for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use *MAC-d PDU Size List*, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *F-DPCH Information IE* and the *DL DPCH Information IE*, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If the RADIO LINK RECONFIGURATION PREPARE message includes *HS-DSCH Information IE* and the HS-DSCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the concerned UE Context is configured to use DPCH in the downlink in the old configuration and if the RADIO LINK RECONFIGURATION PREPARE message includes the *DL DPCH Power Information IE*, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to use F-DPCH in the downlink in the old configuration and the RADIO LINK RECONFIGURATION PREPARE message includes at least one but not all of the *TFCS IE*, *DL DPCH Slot Format IE*, *TFCS Signalling Mode IE*, *Multiplexing Position IE*, *Limited Power Increase IE* and *DL DPCH Power Information IE* in the *DL DPCH Information IE*, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the *E-DCH FDD Information IE* is present in the RADIO LINK RECONFIGURATION PREPARE message, but the *E-DPCH Information IE* is not present or if any of the *Maximum Set of E-DPDCHs IE*, *Puncture Limit IE*, *E-TFCS Information IE*, *E-TTI IE*, *E-DPCCH Power Offset IE*, *E-RGCH 2-Index-Step Threshold IE*, *E-RGCH 3-Index-*
+
+*Step Threshold IE*, *HARQ Info for E-DCH IE* or *HS-DSCH Configured Indicator IE* are not present in the *E-DPCH Information IE*, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH RL Indication IE* set to “E-DCH”, but no *E-DCH FDD Information IE*, and the UE Context is not configured for E-DCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH FDD Information IE* but no *E-DCH RL Indication IE* set to “E-DCH”, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If the RADIO LINK RECONFIGURATION PREPARE message contains the *HS-PDSCH RL ID IE* and/or the *Serving E-DCH RL IE* and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *HS-PDSCH RL ID IE* and the *E-DPCH Information IE* which includes the *HS-DSCH Configured Indicator IE* set as “HS-DSCH not configured” then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *E-DCH FDD Information To Modify IE*, *E-DCH MAC-d Flows To Add IE* or *E-DCH MAC-d Flows To Delete IE* in addition to the *E-DCH FDD Information IE*, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *E-DCH FDD Information To Modify IE*, *E-DCH MAC-d Flows To Add IE*, *E-DCH MAC-d Flows To Delete IE* and the UE Context is not configured for E-DCH, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH FDD Information To Modify IE* deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes *E-DCH FDD Information IE* and the E-DCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the *Fast Reconfiguration IE* is included in the RADIO LINK RECONFIGURATION PREPARE message and the *UL Scrambling Code IE* does not indicate an uplink scrambling code different from the currently used uplink scrambling code the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify IE* in addition to the *Continuous Packet Connectivity DTX-DRX Information IE*, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE* in addition to the *Continuous Packet Connectivity HS-SCCH less Information IE*, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. ]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE* while the Continuous Packet Connectivity HS-SCCH less configuration isn't configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify IE* while the Continuous Packet Connectivity DTX-DRX configuration isn't configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *DRX Information To Modify IE* in *Continuous Packet Connectivity DTX-DRX Information To Modify IE* while the Continuous Packet Connectivity
+
+DRX configuration is not configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH Indicator* IE set to “Uplink DCH only” but no *Transport Format Set* IE for the uplink for this DCH and the DRNC had ignored the configuration of Transport Format Set for uplink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH Indicator* IE set to “Downlink DCH only” but no *Transport Format Set* IE for the downlink for this DCH and the DRNC had ignored the configuration of Transport Format Set for downlink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Transport Bearer Not Requested Indicator* IE for a DCH or an E-DCH MAC-d flow but does not contain the corresponding *DCH ID* IE and the *Unidirectional DCH indicator* IE set to “Uplink DCH only” for the DCH in *DCH Information To Add* IE or does not contain the corresponding *E-DCH MAC-d Flow ID* IE in *E-DCH MAC-d Flows Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply UL DPCCH Slot Format 4 but is not configured to use F-DPCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply the “Closed loop mode 1” and if the concerned UE Context is not configured to apply UL DPCCH Slot Format 2 or 3, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply MIMO, allowed to apply 64QAM, establish the secondary serving HS-DSCH Radio Link, apply MIMO with four transmit antennas, or apply Dual Stream MIMO with four transmit antennas, or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE for a DCH in the *RL Specific DCH Information* IE but does not include the *DCH ID* IE for the DCH in the *DCHs to Add* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE for an E-DCH MAC-d flow in the *RL Specific E-DCH Information* IE but does not include the *E-DCH MAC-d flow ID* IE for the E-DCH MAC-d flow in the *E-DCH MAC-d flows Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Continuous Packet Connectivity DTX-DRX Information* IE but does not contain the *F-DPCH Information* IE and the concerned UE Context is not previously configured to use F-DPCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to have the Serving E-DCH Radio Link but there is at least one E-DCH MAC-d flow which the transport bearer is not configured for the Serving E-DCH Radio Link in DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH or the E-DCH MAC-d Flow in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional HS Cell Information RL Reconf Prep* IE indicating a new secondary serving cell that is not in the same Node B as the serving HS-DSCH cell (or new serving in case of simultaneous serving HS-DSCH cell change), then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If ALCAP is not used, if the concerned UE Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION PREPARE message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the DCH, the E-DCH MAC-d flow and/or the HS-DSCH MAC-d flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[TDD – If ALCAP is not used, if the concerned UE Context is configured to establish a DSCH and/or a USCH but the RADIO LINK RECONFIGURATION PREPARE message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the DSCH and/or the USCH, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use “Flexible RLC PDU Size” for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use “Flexible RLC PDU Size”, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply more than one of MIMO, MIMO with four transmit antennas, Dual Stream MIMO with four transmit antennas and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional E-DCH Cell Information RL Reconf Prep* IE and if the *E-DPCH Information* IE is not present or the E-DPCH Information was not configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional E-DCH Cell Information RL Reconf Prep* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE in the *Additional E-DCH Cell Information RL Reconf Prep* IE and the *C-ID* IE is not included but the RL indicated by the *E-DCH Additional RL ID* IE is not configured in the current UE context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Diversity Mode* IE in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE and the secondary serving HS-DSCH is already configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the secondary serving HS-DSCH is not configured in the UE Context and if the RADIO LINK RECONFIGURATION PREPARE message contains in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE the *Diversity Mode* IE not set to “None” but not the *Transmit Diversity Indicator* or contains the *Transmit Diversity Indicator* but not the *Diversity Mode* IE not set to “None”, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Diversity Mode* IE in the *Secondary Serving Information To Modify* IE in the *Additional HS Cell Information RL Reconf Prep* IE and the *Non Cell Specific Tx Diversity* IE, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional HS Cell Information RL Reconf Prep* IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the *Ordinal Number Of Frequency* IE in the *HS-DSCH FDD Secondary Serving Information* IE or the *HS-DSCH FDD Secondary Serving Information To Modify* IE, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional HS Cell Information RL Reconf Prep* IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *UL CLTD Information* IE but does not contain the *F-TPICH Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL CLTD Information* IE but without *F-TPICH Information* IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *UL MIMO Information* IE in *E-DCH FDD Information* IE but does not contain the *UL CLTD Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL MIMO Information* IE but without *UL CLTD Information* IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+## 8.3.5 Synchronised Radio Link Reconfiguration Commit
+
+### 8.3.5.1 General
+
+This procedure is used to order the DRNS to switch to the new configuration for the Radio Link(s) within the DRNS, previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+### 8.3.5.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ SRNC->>DRNC: RADIO LINK RECONFIGURATION COMMIT
+
+```
+
+Sequence diagram showing the Synchronised Radio Link Reconfiguration Commit procedure. A horizontal line represents the timeline, with 'SRNC' on the left and 'DRNC' on the right. A vertical line descends from 'SRNC' and another from 'DRNC'. A horizontal arrow points from the SRNC's vertical line to the DRNC's vertical line, labeled 'RADIO LINK RECONFIGURATION COMMIT'.
+
+**Figure 12: Synchronised Radio Link Reconfiguration Commit procedure, Successful Operation**
+
+The DRNS shall switch to the new configuration previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure at the “configuration switching point” occurring:
+
+- [TDD – at the next coming CFN with a value equal to the value requested by the SRNC in the *CFN* IE (see TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the SRNC.]
+- [FDD – if the *Fast Reconfiguration* IE is not included in the RADIO LINK RECONFIGURATION COMMIT message at the next coming CFN with a value equal to the value requested by the SRNC in the *CFN* IE (see TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the SRNC.]
+- [FDD – if the *Fast Reconfiguration* IE is included in the RADIO LINK RECONFIGURATION COMMIT message as soon as the DRNS detects that the UE uses the new configuration in the uplink (e.g. the NodeB indicates that the UE uses the new scrambling code used for the uplink by sending the RADIO LINK
+
+RESTORATION message). In order to limit the period for the detection in the DRNS the CFN in the RADIO LINK RECONFIGURATION COMMIT message indicates the earliest possible time instant at which the UE might use the new configuration.]
+
+[FDD – If the *Active Pattern Sequence Information* IE is included in the RADIO LINK RECONFIGURATION COMMIT message, the *CM Configuration Change CFN* IE in the *Active Pattern Sequence Information* IE shall be ignored by the DRNS.]
+
+[FDD – If the *Active Pattern Sequence Information* IE is not included in the RADIO LINK RECONFIGURATION COMMIT message and a new Compressed Mode Configuration exists in the prepared configuration, the DRNS shall behave as if an *Active Pattern Sequence Information* IE with an empty *Transmission Gap Pattern Sequence Status* IE was included.]
+
+When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1.
+
+In the case of a Transport Channel or MAC-d flow modification for which a new transport bearer was requested and established, the switch to the new transport bearer shall also take place at the configuration switching point (defined above) indicated CFN.
+
+The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [4], subclause 5.10.1, and in TS 25.425 [32], subclauses 5.3.1 and 5.3.2.
+
+[FDD – If the RADIO LINK RECONFIGURATION COMMIT includes the *Active Pattern Sequence Information* IE, the DRNS shall deactivate all the ongoing Transmission Gap Pattern Sequences at the configuration switching point (defined above). From that moment on all Transmission Gap Pattern Sequences included in *Transmission Gap Pattern Sequence Status* IE repetitions shall be started when the indicated *TGCFN* IE elapses. The *CFN* IE and *TGCFN* IE for each sequence refer to the next coming CFN with that value. If the values of the *CFN* IE and the *TGCFN* IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the *CFN* IE.]
+
+[FDD – If the RADIO LINK RECONFIGURATION COMMIT message includes the *Active Pattern Sequence Information* IE and the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the downlink compressed mode method information, if existing, for the concerned Transmission Gap Pattern Sequence(s) in the Compressed Mode Configuration.]
+
+[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]
+
+### 8.3.5.3 Abnormal Conditions
+
+If a new transport bearer is required for the new configuration and it is not available at the requested configuration switching point (defined in sub-clause 8.3.3.2), the DRNS shall initiate the Radio Link Failure procedure.
+
+[FDD – If the *Fast Reconfiguration* IE is included in the RADIO LINK RECONFIGURATION COMMIT message and the DRNC did not include the *Fast ReconfigurationPermission* IE in the RADIO LINK RECONFIGURATION READY message, the DRNC shall initiate the Radio Link Failure procedure.]
+
+[FDD - If the RADIO LINK RECONFIGURATION COMMIT message contains the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall initiate the Radio Link Failure procedure with the cause value “Invalid CM Settings”.]
+
+## 8.3.6 Synchronised Radio Link Reconfiguration Cancellation
+
+### 8.3.6.1 General
+
+This procedure is used to order the DRNS to release the new configuration for the Radio Link(s) within the DRNS, previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+### 8.3.6.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ SRNC->>DRNC: RADIO LINK RECONFIGURATION CANCEL
+```
+
+Sequence diagram for Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation. It shows a single message 'RADIO LINK RECONFIGURATION CANCEL' being sent from the SRNC to the DRNC.
+
+**Figure 13: Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation**
+
+Upon receipt of the RADIO LINK RECONFIGURATION CANCEL message from the SRNC, the DRNS shall release the new configuration ([FDD – including the new Transmission Gap Pattern Sequence parameters (if existing)]) previously prepared by the Synchronised RL Reconfiguration Preparation procedure and continue using the old configuration. When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1.
+
+### 8.3.6.3 Abnormal Conditions
+
+-
+
+## 8.3.7 Unsynchronised Radio Link Reconfiguration
+
+### 8.3.7.1 General
+
+The Unsynchronised Radio Link Reconfiguration procedure is used to reconfigure Radio Link(s) related to one UE-UTRAN connection within a DRNS.
+
+The procedure is used when there is no need to synchronise the time of the switching from the old to the new radio link configuration in the cells used by the UE-UTRAN connection within the DRNS.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Unsynchronised Radio Link Reconfiguration procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.7.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ SRNC->>DRNC: RADIO LINK RECONFIGURATION REQUEST
+ DRNC-->>SRNC: RADIO LINK RECONFIGURATION RESPONSE
+```
+
+Sequence diagram for Unsynchronised Radio Link Reconfiguration procedure, Successful Operation. It shows two messages: 'RADIO LINK RECONFIGURATION REQUEST' from SRNC to DRNC, and 'RADIO LINK RECONFIGURATION RESPONSE' from DRNC back to SRNC.
+
+**Figure 14: Unsynchronised Radio Link Reconfiguration procedure, Successful Operation**
+
+The Unsynchronised Radio Link Reconfiguration procedure is initiated by the SRNC by sending the RADIO LINK RECONFIGURATION REQUEST message to the DRNC.
+
+Upon receipt, the DRNS shall modify the configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *Allowed Queuing Time* IE the DRNS may queue the request the time corresponding to the value of the *Allowed Queuing Time* IE before starting to execute the request.
+
+The DRNS shall prioritise resource allocation for the RL to be modified according to Annex A.
+
+If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK RECONFIGURATION REQUEST message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
+
+#### **DCH Modification:**
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes any *DCHs To Modify* IEs, then the DRNS shall treat them as follows:
+
+- If the *DCHs To Modify* IE includes multiple *DCH Specific Info* IEs, then the DRNS shall treat the DCHs as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
+- If the *DCHs To Modify* IE includes the *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCHs To Modify* IE includes the *ToAWS* IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCHs To Modify* IE includes the *ToAWE* IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes a *Transport Format Set* IE for the UL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes a *Transport Format Set* IE for the DL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Frame Handling Priority* IE, the DRNS should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the DRNS once the new configuration has been activated.
+- If the *DCH Specific Info* IE includes the *Traffic Class* IE, the DRNC may use this information to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE for this DCH indicates the value “RRC”.
+- [FDD – If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to “Uplink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.]
+- [FDD – If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to “Downlink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.]
+- If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the DRNS may use this information to determine the transport bearer characteristics to apply for the uplink for the related DCH or set of co-ordinated DCHs.
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Allocation/Retention Priority* IE, the DRNS shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A.
+- [TDD – If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *CCTrCH ID* IE for the UL, the DRNS shall map the DCH onto the referenced UL CCTrCH in the new configuration.]
+- [TDD – If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *CCTrCH ID* IE for the DL, the DRNS shall map the DCH onto the referenced DL CCTrCH in the new configuration.]
+- If the *DCHs To Modify* IE contains a *DCH Specific Info* IE which includes the *Guaranteed Rate Information* IE, the DRNS shall treat the included IEs according to the following:
+ - - If the *Guaranteed Rate Information* IE includes the *Guaranteed UL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate in the uplink of the DCH at any point in time after activating the
+
+new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate.
+
+- If the *Guaranteed Rate Information* IE includes the *Guaranteed DL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user in the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate.
+
+#### DCH Addition:
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes any *DCHs To Add* IEs, then the DRNS shall treat them each as follows:
+
+- The DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message and include these DCH in the new configuration.
+- If the *DCHs To Add* IE includes multiple *DCH Specific Info* IEs then the DRNS shall treat the DCHs in the *DCHs To Add* IE as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if all of them can be in the new configuration.
+- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to “Uplink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.
+- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to “Downlink DCH only”, the DRNS shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.
+- [FDD – For each DCH which does not belong to a set of co-ordinated DCHs, and which includes a *QE-Selector* IE set to “selected”, the DRNS shall use the Transport channel BER from that DCH for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If the *QE-Selector* IE is set to “non-selected”, the DRNS shall use the Physical channel BER for the QE in the UL data frames, TS 25.427 [4].]
+- For a set of co-ordinated DCHs, the DRNS shall use the Transport channel BER from the DCH with the *QE-Selector* IE set to “selected” for the QE in the UL data frames, TS 25.427 [4]. [FDD – If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If all DCHs have the *QE-Selector* IE set to “non-selected”, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4].] [TDD – If no Transport channel BER is available for the selected DCH, the DRNS shall use 0 for the QE, TS 25.427 [4].]
+- The DRNS should store the *Frame Handling Priority* IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the DRNS once the new configuration has been activated.
+- The *Traffic Class* IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE indicates the value “RRC”.
+- If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the DRNS may use this information to determine the transport bearer characteristics to apply for the uplink for the related DCH or set of co-ordinated DCHs.
+- The DRNS shall use the included *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- The DRNS shall use the included *ToAWS* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+
+- The DRNS shall use the included *ToAWE* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
+- If the *DCH Specific Info* IE includes the *Guaranteed Rate Information* IE, the DRNS shall treat the included IEs according to the following:
+ - - If the *Guaranteed Rate Information* IE includes the *Guaranteed UL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the uplink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the *DCH Specific Info* IE in the *DCH Information* IE does not include the *Guaranteed UL Rate* IE, the DRNS shall not limit the user rate of the uplink of the DCH.
+- If the *Guaranteed Rate Information* IE includes the *Guaranteed DL Rate* IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the *DCH Specific Info* IE in the *DCH Information* IE does not include the *Guaranteed DL Rate* IE, the DRNS shall not limit the user rate of the uplink of the DCH.
+
+#### DCH Deletion:
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes any *DCHs To Delete* IEs, the DRNS shall not include the referenced DCHs in the new configuration.
+
+If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the DRNS shall not include this set of co-ordinated DCHs in the new configuration.
+
+#### [FDD – Physical Channel Modification:]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *UL DPCH Information* IE, then the DRNS shall apply the parameters to the new configuration as follows: ]
+
+- [FDD – If the *UL DPCH Information* IE includes the *TFCS* IE for the UL, the DRNS shall apply the new TFCS in the Uplink of the new configuration.]
+- [FDD – If the *UL DPCH Information* IE includes the *UL DPDCH Indicator For E-DCH Operation* IE set to “UL DPDCH not present”, the UL DPDCH resources shall be removed from the configuration.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes a *DL DPCH Information* IE, then the DRNS shall apply the parameters to the new configuration as follows:]
+
+- [FDD – If the *DL DPCH Information* IE includes the *TFCS* IE for the DL, the DRNS shall apply the new TFCS in the Downlink of the new configuration.]
+- [FDD – If the *DL DPCH Information* IE includes the *TFCI Signalling Mode* IE for the DL, the DRNS shall apply the new TFCI Signalling Mode in the Downlink of the new configuration.]
+- [FDD – If the *DL DPCH Information* IE includes the *Limited Power Increase* IE and the IE is set to “Used”, the DRNS shall, if supported, use Limited Power Increase according to TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.]
+- [FDD – If the *DL DPCH Information* IE includes the *Limited Power Increase* IE and the IE is set to “Not Used”, the DRNS shall not use Limited Power Increase for the inner loop DL power control in the new configuration.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE, the DRNS shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode
+
+Configuration has been activated. This new Compressed Mode Configuration shall be valid in the DRNS until the next Compressed Mode Configuration is configured in the DRNS or last Radio Link is deleted.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE, and if the *Downlink Compressed Mode Method* in one or more Transmission Gap Pattern Sequence within the *Transmission Gap Pattern Sequence Information* IE is set to “SF/2”, the DRNC shall include the *DL Code Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message, without changing any of the DL Channelisation Codes or DL Scrambling Codes, indicating for each DL Channelisation Code whether the alternative scrambling code shall be used or not.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DPCH Information* IE which contains the *E-TFCS Information* IE, the DRNS shall use the *E-TFCS Information* IE for the E-DCH when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration. If the *E-TFCS Information* IE contains the *E-DCH Minimum Set E-TFCI Validity Indicator* IE the DRNS shall ignore the value in *E-DCH Minimum Set E-TFCI* IE. If the *E-DCH Minimum Set E-TFCI validity indicator* IE is absent DRNS shall use the value for the related resource allocation operation.]
+
+[FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION REQUEST message.]
+
+[FDD – If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the DRNS shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the DRNS shall use the value “127” in the algorithm defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION REQUEST message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *E-DPCH Power Offset* IE, the DRNS shall use the value when the new configuration is being used.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *E-RGCH 2-Index-Step* IE, the DRNS shall use the value when the new configuration is being used.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *E-RGCH 3-Index-Step* IE, the DRNS shall use the value when the new configuration is being used.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *HARQ Info for E-DCH* IE, the DRNS shall use the value when the new configuration is being used.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *Minimum Reduced E-DPDCH Gain Factor* IE, then the DRNS shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:]
+
+- [FDD – The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]
+- [FDD – If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then:]
+
+- [FDD – If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.]
+- [FDD – If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10]. ]
+
+- [FDD – If the *DTX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of *DTX Information To Modify* IE is “Deactivate”, then DRX should be deactivated together with DTX.]
+- [FDD – If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:]
+
+- [FDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]
+- [FDD – The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If at least one of *HS-PDSCH Second Code Support* IE is set to “True”, then the DRNC shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[FDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE, then the DRNS shall deactivate the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.]
+
+#### **[FDD - UL CLTD Setup:]**
+
+[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Setup", then: the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights according the new configuration defined in the *UL CLTD Information* IE and then:]
+
+- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.]
+- [FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]
+
+#### **[FDD - UL CLTD Modification:]**
+
+[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Configuration Change", then: the *UL CLTD Information To Modify* IE defines the new configuration and then:]
+
+- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *C-ID* IE in the *UL CLTD Information To Modify* IE, then the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context. Otherwise the DRNS shall configure the serving E-DCH cell or the HS\_ DSCH serving cell to determine the precoding weights as specified in TS 25.319[38]. The UL CLTD configuration is only valid for the cell to determine the precoding weights.]
+- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *S-DPCCH Power Offset Information* IE in the *UL CLTD Information To Modify* IE, then the DRNS shall use this value to determine the S-DPCCH power.]
+- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UL CLTD State Activation Information* IE in the *UL CLTD Information To Modify* IE, then the DRNS shall use this value to update the local state of UL CLTD for the concerned UE Context. If the *UL CLTD Activation Information* IE is set to "De-activated", the DRNS should release the F-TPICH resource configured for the concerned UE Context.]
+
+#### **[FDD - UL CLTD Removal:]**
+
+[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Removal", then the configured UL CLTD for the concerned UE Context shall be removed.]
+
+**[FDD – UL MIMO Setup:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UL MIMO Information* IE in *E-DCH FDD Information*, or the *UL MIMO Reconfiguration* IE and the choice of *Setup or Change or Stop* is "Setup", then the DRNS shall setup the requested UL MIMO operation.]
+
+**[FDD – UL MIMO Modification:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes *UL MIMO Reconfiguration* IE and the choice of *Setup or Change or Stop* is "Change", then the DRNS shall apply the new configuration.]
+
+**[FDD – UL MIMO Removal:]**
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UL MIMO Reconfiguration* IE and the choice of *Setup or Change or Stop* is "Stop", then the DRNS shall terminate the UL MIMO operation.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DRX Information LCR* IE, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[1.28 Mcps TDD - If the *Inactivity Threshold for UE DRX Cycle Ext* IE is included in the *Continuous Packet Connectivity DRX Information LCR* IE, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then:]
+
+- [1.28 Mcps TDD – If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the DRNS shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.]
+- [1.28 Mcps TDD – If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [22].]
+- [1.28 Mcps TDD – If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall include *Allocated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:]
+
+- [1.28 Mcps TDD – The DRNS shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+
+- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the DRNS shall include *Allocated E-DCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then:]
+
+- [1.28 Mcps TDD – If the *Transport Block Size List* IE or/and *Repetition Period list* IE is/are included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the DRNS shall modify the configuration of Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].
+- [1.28 Mcps TDD – The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall include *Allcoated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [1.28 Mcps TDD – If the *HS-DSCH Semi-Persistent scheduling operation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]
+- [1.28 Mcps TDD – If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [1.28 Mcps TDD – If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then:]
+
+- [1.28 Mcps TDD – If the *Repetition Period list* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, the DRNS shall modify the configuration of Serving HS-DSCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].]
+- [1.28 Mcps TDD – If the *E-DCH Semi-Persistent scheduling Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.]
+- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the DRNS shall include *Allocated E-DCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the DRNS shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the DRNS shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.]
+
+[1.28 Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *MU-MIMO Indicator* IE, then:]
+
+- [1.28 Mcps TDD –the DRNS may use the MU-MIMO for the radio link according to the *MU-MIMO Usage Indicator* IE and shall include the *MU-MIMO Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [1.28 Mcps TDD – If the *Standalone Midamble Channel Indicator* IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION RESPONSE
+
+message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### **[TDD – UL/DL CCTrCH Modification]**
+
+[TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes any *UL CCTrCH To Modify* IE or *DL CCTrCH To Modify* IE, the DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message.]
+
+[TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes any *UL CCTrCH Information To Modify* IEs or *DL CCTrCH Information To Modify* IEs which contain a *TFCS* IE, the DRNS shall apply the included *TFCS* IE as the new value(s) to the referenced CCTrCH. Otherwise the DRNS shall continue to apply the previous value(s) specified for this CCTrCH.]
+
+[1.28Mcps TDD – If the *UL CCTrCH To Modify* IE includes *UL SIR Target* IE, the DRNS shall apply this value as the new configuration and use it for the UL inner loop power control according to TS 25.221 [12] and TS 25.224 [22].]
+
+#### **[TDD – UL/DL CCTrCH Deletion]**
+
+[TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes any *UL CCTrCH Information To Delete* IEs or *DL CCTrCH Information To Delete* IEs, the DRNS shall not include the referenced CCTrCH in the new configuration.]
+
+#### **DL Power Control:**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *DL Reference Power Information* IE and the power balancing is active, the DRNS shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported, using the *DL Reference Power Information* IE in the RADIO LINK RECONFIGURATION REQUEST message. The updated reference power shall be used from the next adjustment period.]
+
+[FDD – If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the DRNS, the DRNC shall include the *DL Power Balancing Updated Indicator* IE in the *RL Information Response* IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### **[1.28Mcps TDD – Uplink Synchronisation Parameters LCR:]**
+
+[1.28Mcps TDD – If the *Uplink Synchronisation Parameters LCR* IE is present, the DRNC shall use the indicated values of *Uplink synchronisation stepsize* IE and *Uplink synchronisation frequency* IE when evaluating the timing of the UL synchronisation.]
+
+#### **[1.28Mcps TDD – Shared physical channels Synchronisation Detection:]**
+
+[1.28Mcps TDD – If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall include the *Out-of-sync Detection Window* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### **[1.28Mcps TDD – Uplink Timing Advance Control LCR:]**
+
+[1.28Mcps TDD – The DRNC shall include the *Uplink Timing Advance Control LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message, if the Uplink Timing Advance Control parameters have been changed.]
+
+#### **[1.28Mcps TDD – PowerControl GAP:]**
+
+[1.28Mcps TDD – If applied in the DRNS, the DRNC may include the *PowerControl GAP* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### **[1.28Mcps TDD – E-UTRAN Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Need for Idle Interval* IE set to “TRUE”, if supported, the DRNC shall include the *Idle Interval Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the *Need for Idle Interval* IE is set to “FALSE”, the DRNC shall delete the configuration related to E-UTRAN Inter-RAT measurement. ]
+
+#### **[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *DCH Measurement Type indicator* IE, if supported, the DRNS shall include the *Measurement purpose* IE and the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message to configure the measurement occasion pattern(s) indicated by the *DCH Measurement Type indicator* IE.]
+
+**[1.28Mcps TDD – RNTI Allocation Indicator:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *RNTI Allocation Indicator* IE, if supported, the DRNS may allocate an E-RNTI and/or an H-RNTI for UE to use in CELL\_FACH state.]
+
+**RL Information:**
+
+[FDD – If the UE Context is configured for F-DPCH Slot Format operation, the DRNS shall include the *F-DPCH Slot Format* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[FDD – If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Setup", then the DRNS shall use the information in *F-TPICH Information* IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10] , and shall include the *F-TPICH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[FDD – If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Configuration Change", then: the *F-TPICH Information To Modify* IE defines the new configuration and then:]
+
+- [FDD – If the *F-TPICH Information To Modify* IE includes the *F-TPICH Offset* IE, the DRNS shall use this information to configure the time offset of F-TPICH, and may include the *F-TPICH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+[FDD – If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Removal", then the DRNS shall remove the configured F-TPICH for the RL.]
+
+**HS-DSCH Setup:**
+
+If the *HS-DSCH Information* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, then:
+
+- The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.
+- The DRNC shall include the *HARQ Memory Partitioning* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD – The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE is included in the *HS-DSCH Information* IE.] [1.28Mcps TDD– The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than “8”, if the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.]
+- The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the RADIO LINK RECONFIGURATION RESPONSE message.
+- The DRNS may use the *Traffic Class* IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *HS-DSCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.
+- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the *User Plane Congestion Fields Inclusion* IE in the *HS-DSCH Information Response* IE.
+
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the DRNS shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.
+- The DRNC shall include the *HS-DSCH Initial Capacity Allocation* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK RECONFIGURATION REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer I in RADIO LINK RECONFIGURATION REQUEST in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE.
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR* IE] [7.68Mcps TDD – *HS-SCCH Specific Information Response 7.68Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the DRNC shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]).
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then]
+
+- - [FDD – The DRNS shall activate the MIMO mode or MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link.]
+ - - [FDD – The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas, or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+ - - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+ - - [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [1.28 Mcps TDD – If the *MIMO Activation Indicator* IE is included in the *HS-DSCH TDD Information* IE, then:]
+- - [1.28 Mcps TDD – The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.]
+ - - [1.28 Mcps TDD – The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the *Sixtyfour QAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE set to “Flexible MAC-d PDU Size” and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- [FDD – If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS may use:]
+- - [FDD – a different HS-SCCH in consecutive TTIs for this UE.]
+ - - [FDD – HS-SCCH orders for the case of HS-SCCH-less operation to this UE.]
+- [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the DRNS may use the supported HSDPA functions for this UE.]
+- [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
+
+- If the RADIO LINK RECONFIGURATION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
+- [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.]
+- [1.28 Mcps TDD – If the *UE TS0 Capability LCR* IE is included in the *HS-DSCH TDD Information* IE, then the DRNC may include the *TS0 HS-PDSCH Indication LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message if HS-PDSCH resources could be allocated on TS0 for the UE.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### [FDD – Secondary Serving HS-DSCH Setup:]
+
+[FDD – If the *C-ID* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, no secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency* IEs, in the *HS-DSCH FDD Secondary Serving Information* IE or in the *HS-DSCH FDD Secondary Serving Information To ModifyUnsynchronised* IE for each instance of the *Additional HS Cell Information RL Reconf Req* IE, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:]
+
+- [FDD – The DRNS shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- [FDD – The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the MIMO mode or MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas, or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+- [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+ - [FDD – If the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+ - [FDD – If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
+ - [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+ - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+ - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+ - [FDD – If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+- [FDD – The DRNS may include the *PreCoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+#### Intra-DRNS Serving HS-DSCH Radio Link Change:
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-PDSCH RL ID* IE, this indicates the new Serving HS-DSCH Radio Link:
+
+- The DRNS shall release the HS-PDSCH resources on the old Serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new Serving HS-DSCH Radio Link.
+- If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the *User Plane Congestion Fields Inclusion* IE in the *HS-DSCH Information Response* IE.
+- The DRNC may include the *HARQ Memory Partitioning* IE in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD – The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] [1.28Meps TDD– The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.]
+- The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI* IE in the RADIO LINK RECONFIGURATION RESPONSE message.
+
+- If a reset of the MAC-hs is not required the DRNS shall include the *MAC-hs Reset Indicator* IE in the RADIO LINK RECONFIGURATION RESPONSE message.
+- [FDD – The DRNC shall include the *Measurement Power Offset* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [TDD – The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD – *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD – *HS-SCCH Specific Information Response LCR* IE] [7.68 Mcps TDD – *HS-SCCH Specific Information Response 7.68 Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [TDD – The DRNC shall include the [3.84 Mcps TDD – *HS-PDSCH Timeslot Specific Information* IE] [1.28 Mcps TDD – *HS-PDSCH Timeslot Specific Information LCR* IE] [7.68 Mcps TDD – *HS-PDSCH Timeslot Specific Information 7.68 Mcps* IE] in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- The DRNC may include the *Transport Layer Address* IE and the *Binding ID* IE for HS-DSCH MAC-d flow in the [FDD – *HS-DSCH FDD Information Response* IE] [TDD – *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message.
+- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE and the value is set to "allowed" or if *HS-DSCH Information To Modify Unsynchronized* IE is not included and the UE Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new configuration, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- [FDD – If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- [FDD – If the power offset for S-CPICH for MIMO with four transmit antennas Request indicator and MIMO with four transmit antennas activation indicator, or Dual Stream MIMO with four transmit antennas Activation Indicator have been configured in the new configuration and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+**[FDD – Intra-DRNS Secondary Serving HS-DSCH Radio Link Change:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *C-ID IE* in the *Additional HS Cell Information RL Reconf Req IE*, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency IEs*, in the *HS-DSCH FDD Secondary Serving Information IE* for each instance of the *Additional HS Cell Information RL Reconf Req IE*, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-DRNS secondary serving HS-DSCH Radio Link change, then the *HS-PDSCH RL ID IE* indicates the new Serving HS-DSCH Radio Link:]
+
+- [FDD – The DRNS shall release the HS-PDSCH resources on the old secondary serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new secondary serving HS-DSCH Radio Link. The DRNS shall remove the old secondary serving HS-PDSCH Radio Link if no E-DCH resources are allocated to the RL. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
+- [FDD – The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the *HS-DSCH-RNTI IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNC shall include the *Measurement Power Offset IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD - If the *Ordinal Number Of Frequency IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+- [FDD – The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the *HS-SCCH Specific Secondary Serving Information Response IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNC shall include the *HS-PDSCH And HS-SCCH Scrambling Code IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE* and the value is set to "allowed" or if *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE* is not included and the UE context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the *SixtyfourQAM DL Usage Indicator IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the *HS-DSCH TB Size Table Indicator IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+- [FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the *HS-DSCH FDD Secondary Serving Information IE* defines the new secondary serving HS-DSCH configuration in the DRNS to be used on the new secondary serving HS-DSCH Radio Link, and then:]
+ - - [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SCCH Power Offset IE* in the *HS-DSCH FDD Secondary Serving Information IE*, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+ - - [FDD – If the *MIMO Activation Indicator IE* or *MIMO with four transmit antennas Activation Indicator IE*, or *Dual Stream MIMO with four transmit antennas Activation Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, then the DRNS shall activate the MIMO mode or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four
+
+transmit antennas, or Dual Stream MIMO with four transmit antennas mode and include the *MIMO Information Response IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *HS-DSCH Secondary Serving Cell Change Information Response IE* in the *Additional HS Cell Change Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+- - [FDD – If the *Single Stream MIMO Activation Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
+ - - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+ - - [FDD – If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE* with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+- [FDD – If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO IE*.]
+- [FDD – If the power offset for S-CPICH for MIMO with four transmit antennas Request indicator and MIMO with four transmit antennas activation indicator, or Dual Stream MIMO with four transmit antennas activation indicator have been configured in the new configuration and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, the DRNC shall include the *Power Offset For S-CPICH for MIMO with four transmit antennas IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas IE*.]
+- [FDD – The DRNS may include the *Precoder weight set restriction IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+**[FDD – Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *C-ID IE* in the *Additional HS Cell Information RL Reconf Req IE* and an additional non serving E-DCH RL exists in the cell indicated by the *C-ID IE*, the *HS-PDSCH RL ID IE* in the *HS Cell Information RL Reconf Req IE* indicates the new Additional Serving E-DCH Radio Link.]
+
+- - [FDD – If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
+- - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- - [FDD – The DRNS may include the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* in the *E-DCH FDD DL Control Channel Information IE* in the *Additional Modified E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RLReconf IE* in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2 IE*.]
+
+- [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [FDD – The DRNS may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Link on secondary UL frequency in the DRNS. If the DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE in the *E-DCH FDD DL Control Channel Information* IE then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE, to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+
+**[FDD – Additional Serving E-DCH Radio Link Change to a new RL:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information RL Reconf Req* IE and the *C-ID* IE in the *Additional HS Cell Information RL Reconf Req* IE and there is no radio links in the cell indicated by the *C-ID* IE for the UE context, the *HS-PDSCH RL ID* IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.]
+
+- [FDD – If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
+- [FDD – In the new configuration the DRNS shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.]
+- [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message. ]
+
+**HS-DSCH Modification:**
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Information To Modify Unsynchronised* IE, then:
+
+- The DRNC shall include the *HS-DSCH Initial Capacity Allocation* IE for each HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the DRNS allows the SRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If UE context is configured to use “Flexible MAC-d PDU Size”, then DRNC shall only set in the *HS-DSCH Initial Capacity Allocation* IE the
+
+values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer for the Priority Queue of UE context.
+
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Traffic Class* IE in the *HS-DSCH Information To Modify Unsynchronised* IE for a specific HS-DSCH MAC-d flow, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE for this specific HS-DSCH MAC-d flow indicates the value “RRC”.
+- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH Information To Modify Unsynchronised* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *ACK Power Offset* IE, the *NACK Power Offset* IE or the *CQI Power Offset* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, then the DRNS shall use the indicated ACK Power Offset, the NACK Power Offset or the CQI Power Offset in the new configuration.]
+- [FDD – If the *HS-SCCH Power Offset* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
+- [TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *TDD ACK NACK Power Offset* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the DRNS shall use the indicated power offset in the new configuration.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, then the DRNS shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the DRNC shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE, then:]
+ - - [FDD – The DRNS shall activate/deactivate the MIMO mode or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link in the new configuration in accordance with the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE.]
+ - - [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is set to “Activate”, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+ - - [FDD – If the *MIMO Mode Indicator* IE is set to “Activate” and *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for*
+
+*MIMO IE in the HS-DSCH FDD Information Response IE. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]*
+
+- [FDD – If the *MIMO with four transmit antennas Mode Indicator IE* or *Dual Stream MIMO with four transmit antennas Mode Indicator IE* is set to “Activate” and *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator IE* is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas IE* in the *HS-DSCH FDD Information Response IE*. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas IE*.]
+- [FDD – The DRNC may include the *HARQ Memory Partitioning IE* in the RADIO LINK RECONFIGURATION RESPONSE message. The *HARQ Memory Partitioning IE* may contain the *HARQ Memory Partitioning Information Extension For MIMO IE*.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH Information To Modify Unsynchronised IE*, then the DRNS may if the value is set to “allowed” use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH Information To Modify Unsynchronised IE* with value set to “not allowed”, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]
+- [FDD – If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the *HS-DSCH TB Size Table Indicator IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.]
+- [1.28Mcps TDD- If the *MIMO Mode Indicator IE* is included in the *HS-DSCH Information To Modify Unsynchronised IE*, then:]
+ - [1.28Mcps TDD- The DRNS shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in the new configuration in accordance with the *MIMO Mode Indicator IE*.]
+ - [1.28 Mcps TDD – If the *MIMO Mode Indicator IE* is set to “Activate”, then the DRNS shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream IE* in the *HS-DSCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.]
+- [FDD – If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
+- [FDD – If the *UE Support Indicator Extension IE* is included in the *HS-DSCH Information To Modify Unsynchronised IE* the DRNS may use the supported HSDPA functions for this UE.]
+- [FDD - If the *UE Support Indicator Extension IE* is included in the *HS-DSCH Information To Modify IE* with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order IE* in the *HS-DSCH FDD Response IE* in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *Single Stream MIMO Mode Indicator IE* is included in the *HS-DSCH Information To Modify Unsynchronised IE*, then the DRNS shall activate/deactivate the Single Stream MIMO for the HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator IE*.]
+- [FDD – The DRNS may include the *Precoder weight set restriction IE* in the *HS-DSCH Information Response IE* in the RADIO LINK RECONFIGURATION READY message.]
+
+#### [FDD – Secondary Serving HS-DSCH Modification:]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE in the *Additional HS Cell Information RL Reconf Req* IE, then:]
+
+- [FDD – If the *HS-SCCH Power Offset* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
+- [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the DRNS shall activate/deactivate the MIMO mode or MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE.]
+- [FDD – If the *MIMO Mode Indicator* IE or *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is set to “Activate”, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO or MIMO with four transmit antennas, or Dual Stream MIMO with four transmit antennas and include the *MIMO Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *MIMO Mode Indicator* IE is set to “Activate” and *Power Offset For S-CPICH for MIMO Request Indicator* IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- [FDD – If the *MIMO with four transmit antennas Mode Indicator* IE is set to “Activate” or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is set to “Activate” and *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator* IE is included, the DRNC shall, if supported and MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO with four transmit antennas* IE.]
+- [FDD – If the *Single Stream MIMO Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator* IE.]
+- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the DRNS may if the value is set to “allowed” use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE with value set to “not allowed”, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
+- [FDD – If, in the new configuration, the UE context is configured to use the “Flexible MAC-d PDU Size” format and if Sixtyfour QAM will not be used for the secondary serving HS-DSCH, then the DRNS shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]
+
+- [FDD – The DRNS may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.]
+
+**[FDD – Secondary Serving HS-DSCH Removal:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Secondary Serving Remove* IE in the *Additional HS Cell Information RL Reconf Req* IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.]
+
+**HS-DSCH MAC-d Flow Addition/Deletion:**
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes any *HS-DSCH MAC-d Flows To Add* or *HS-DSCH MAC-d Flows To Delete* IEs, then the DRNS shall use this information to add/delete the indicated HS-DSCH MAC-d flows on the Serving HS-DSCH Radio Link. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes an *HS-DSCH MAC-d Flows To Delete* IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the UE Context, then the DRNC shall delete the HS-DSCH configuration from the UE Context and release the HS-PDSCH resources.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH MAC-d Flows To Add* IE, then:
+
+- The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value “RRC” in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.
+- If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.
+- The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being added, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If the UE context is configured to use the “Flexible MAC-d PDU Size” format for the HS-DSCH, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK RECONFIGURATION REQUEST message in the HS-DSCH MAC-d Flows To Add IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the DRNC shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
+- If the RADIO LINK RECONFIGURATION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].
+- [FDD – FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
+
+### [FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE the DRNS shall, if supported, preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [63]:]
+
+- - [FDD – The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of *Secondary C-ID* IEs in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION REQUEST message.]
+- - [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ]
+ - - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell.]
+ - - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells.]
+- - [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ]
+- - [FDD – The DRNS shall return these codes in the *Sets of HS-SCCH Codes* IE along with the corresponding per-cell *HS-DSCH-RNTI* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK RECONFIGURATION RESPONSE.]
+- - [FDD – The DRNS shall use the first in the numbered list the primary serving HS-DSCH cell's of HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the SRNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [16].]
+- - [FDD – The DRNS shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:]
+ - - [FDD – if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the HARQ Preamble Mode Activation Indicator IE.]
+ - - [FDD – if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.]
+ - - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE]
+ - - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.]
+ - - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.]
+ - - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE]
+ - - [FDD – if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfiguration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell.]
+ - - [FDD – if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell.]
+
+- - [FDD – if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE.]
+- - [FDD – if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS shall store this information in the preconfigured configuration.]
+- - [FDD – the *SixtyfourQAM DL Support Indicator* IE may be included.]
+- - [FDD – If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the DRNS may store this information in the preconfigured configuration.]
+- - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the DRNS shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- - [FDD – the DRNS shall, if supported, include in the *Sets of HS-SCCH Codes* IE the *Measurement Power Offset* IE for each preconfigured cell.]
+- - [FDD – The DRNS shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
+ - - [FDD – The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.]
+ - - [FDD – The DRNS may preconfigure the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.]
+- - [FDD – If the *Power Offset For S-CPICH for MIMO Request Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where HS-DSCH / secondary HS-DSCH is preconfigured, include the *Power Offset For S-CPICH for MIMO* IE in the *HS-DSCH Preconfiguration Info* IE or in the *Sets of HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Info* IE for each preconfigured cell in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the *Power Offset For S-CPICH for MIMO* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the DRNC shall allocate resources for the preconfigured Multiflow.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the DRNC shall allocate resources for the preconfigured F-TPICH channel and include *F-TPICH Information Response* IE in the *HS-DSCH Preconfiguration Info* IE.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the DRNC shall allocate resources for the preconfigured UL CLTD.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the DRNC shall allocate resources for the preconfigured UL MIMO.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixteen QAM.]
+- - [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the DRNC shall allocate resources for the preconfigured UL Sixtyfour QAM.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Non-Serving RL Preconfiguration Setup* IE in the *RL Information* IE and:]
+
+- [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – if the choice of *new Serving RL* is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the DRNC may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of new Serving RL in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information* IE for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the *F-TPICH Information* IE is included, the DRNC shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [8], and include *F-TPICH Information Response* IE in the *Non-Serving RL Preconfiguration Info* IE.]
+
+#### [FDD – Enhanced HS Serving Cell Change:]
+
+[FDD – Upon receipt of the RADIO LINK RECONFIGURATION REQUEST message, if the Enhanced HS Serving Cell Change is preconfigured in the DRNS for the UE context, the DRNS may execute the Enhanced HS Serving Cell Change procedure according to TS 25.308 [63].]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Enhanced HS Serving CC Abort* IE in the *HS-DSCH Information To Modify Unsynchronised* IE or the *HS-DSCH FDD Information* IE then the DRNS shall not execute the unsynchronized Enhanced HS Serving Cell Change procedure when performing the Serving HS-DSCH Radio Link Change or the HS-DSCH Setup.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *No of Target Cell HS-SCCH Order* IE then the DRNS shall repeat the Target Cell HS-SCCH Order on the HS-SCCH the number of times defined in the IE.]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Non-Serving RL Preconfiguration Removal* IE, the DRNC shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.]
+
+#### [FDD - Multiflow Setup:]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Multiflow Information* IE in *HS-DSCH Information* IE, or *Multiflow Reconfiguration* IE in *HS-DSCH Information To Modify* IE and the choice of *Setup or Change or Stop* is "Setup", then the DRNS shall setup the requested Multiflow operation.]
+
+#### [FDD - Multiflow Modification:]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes *Multiflow Reconfiguration* IE in *HS-DSCH Information To Modify* IE and the choice of *Setup or Change or Stop* is "Change", then the DRNS shall apply the new configuration.]
+
+#### [FDD - Multiflow Removal:]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Multiflow Reconfiguration* IE in *HS-DSCH Information To Modify* IE, and the choice of *Setup or Change or Stop* is "Stop", then the DRNS shall terminate the Multiflow operation.]
+
+#### [FDD – E-DCH Setup:]
+
+[FDD – If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION REQUEST message then:]
+
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel information* IE in the *E-DCH FDD Information* IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH Information* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being “E-DCH Non-Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.]
+- [FDD – If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being “E-DCH Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
+- [FDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *E-DCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+- [FDD – If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Bundling Mode Indicator* IE for a E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to “Bundling” and the *E-TTI* IE is set to “2ms”, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related Mac-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related Mac-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH ReferencePower Offset* IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
+
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DPCH Information* IE which contains the *HS-DSCH Configured Indicator* IE and/or the *Maximum Set of E-DPDCHs* IE, and/or the *Puncture Limit* IE and/or the *E-TTI* IE, the DRNS shall use and apply the value(s) in the new configuration.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *SixteenQAM UL Operation Indicator* IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.]
+ - - [FDD – If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]
+
+#### [FDD – E-DCH Radio Link Handling:]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH RL Indication* IE in the *RL Information* IE:]
+
+- [FDD – The DRNC shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+- [FDD – The DRNC may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNC may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the *E-DCH RL Indication* IE, set to “E-DCH”, in the *RL Information* IE.]
+- [FDD – The DRNC shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the *E-DCH RL Indication* set to “Non E-DCH”.]
+- [FDD – For each RL for which the *E-DCH RL Indication* IE is set to “E-DCH”, and which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the *E-DCH RL Set ID* IE in the RADIO LINK RECONFIGURATION RESPONSE message. The value of the *E-DCH RL Set ID* IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
+
+#### [FDD – Serving E-DCH Radio Link Change:]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Serving E-DCH RL* IE, this indicates the new Serving E-DCH Radio Link:]
+
+- [FDD – If the old Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link.]
+- [FDD – If the new Serving E-DCH RL is within this DRNS:]
+ - - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information*]
+
+IE in the *RL Information Response* IE for the indicated RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+- - [FDD – The DRNS may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the new serving E-DCH RL.]
+ - - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+ - - [FDD – If a serving cell change is performed the RADIO LINK RECONFIGURATION RESPONSE message may contain invalid data (see 9.2.2.4C).]
+ - - [FDD – The DRNS may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the new serving E-DCH RL.]
+- [FDD – The DRNS may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Links in the DRNS.]
+- [FDD – If the DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE, to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+
+#### [FDD – E-DCH Modification:]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH FDD Information To Modify* IE, then:]
+
+- [FDD – If the *E-DCH FDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the DRNS shall apply the new *Allocation/Retention Priority* to this E-DCH in the new configuration according to Annex A.]
+- [FDD – If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [FDD – If *Traffic Class* IE is included for an E-DCH MAC-d flow the DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the *Traffic Class* IE if the *TrCH Source Statistics Descriptor* IE for this specific E-DCH MAC-d flow indicates the value “RRC”.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Data Description Indicator* IE, the DRNC shall use the DDI values indicated in the *Data Description Indicator* IE in the new configuration.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH FDD Information To Modify* IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow in the *E-DCH FDD Information To Modify* IE, then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH HARQ Power Offset FDD* IE in the *E-DCH FDD Information To Modify* IE for an E-DCH MAC-d flow the DRNS shall use this information for calculating the unquantised gain factor for an E-TFC ( $\beta_{ed,j,uq}$ ) as defined in TS 25.214 [10].]
+
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Grant Type and it is indicated as being “E-DCH Non-Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Grant Type and it is indicated as being “E-DCH Scheduled Transmission Grant” for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the DRNS shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Logical Channel To Modify* IE, the DRNS shall use this information to modify the indicated logical channels.]
+ - - [FDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the DRNS shall apply the values in the new configuration.]
+ - - [FDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the DRNS shall apply the values in the new configuration.]
+ - - [FDD – If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the DRNC shall apply the value in the new configuration.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information To Modify* IE and the *Bundling Mode Indicator* IE is set to “Bundling” and the *E-TTI* IE is set to “2ms”, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the DRNS shall use this information for the related resource allocation operation.]
+- [FDD – If the E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH ReferencePower Offset* IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
+
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *SixteenQAM UL Operation Indicator* IE in the *E-DCH FDD Information To Modify* IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.]
+ - - [FDD – If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH DL Control Channel Grant Information* IE in the *E-DCH FDD Information To Modify* IE, the DRNS may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the *E-DCH RL ID* IE. The DRNC shall then report the modified configuration which is used in the new configuration specified in the *E-DCH FDD DL Control Channel Information* IE for each E-DCH RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### **[FDD – E-DCH MAC-d Flow Addition:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Add* IE, then the DRNS shall use this information to add the indicated E-DCH MAC-d flows.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH MAC-d Flows To Add* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flows To Add* IE, then:]
+
+- [FDD – The DRNS may use the *Traffic Class* IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If *TrCH Source Statistics Descriptor* IE is present with the value “RRC” in the *E-DCH MAC-d Flows Information* IE, then the DRNC should ignore the *Traffic Class* IE.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
+
+#### **[FDD – E-DCH MAC-d Flow Deletion:]**
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Delete* IEs, then the DRNS shall use this information to delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration shall also be removed.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNC shall delete the E-DCH configuration from the UE Context and release the E-DCH resources.]
+
+### [FDD – Additional E-DCH Setup:]
+
+[FDD – If the *Additional E-DCH Cell Information RL Reconf Req* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is “Setup”, then the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:]
+
+- [FDD – If the *C-ID* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *C-ID* IE indicates the cell in which the additional E-DCH shall be setup.]
+ - - [FDD – The DRNS shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.]
+- [FDD – If the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *E-DCH Additional RL ID* IE indicates the existing RL on which the additional E-DCH shall be setup.]
+ - - [FDD – The DRNS shall setup the additional E-DCH on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.]
+- [FDD – The DRNS shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.]
+- [FDD – If the *UL SIR Target* IE in the *UL DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE and/or the *DL Power Balancing Information* IE and/or the *Minimum Reduced E-DPDCH Gain Factor* IE in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE are present, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Secondary UL Frequency Activation State* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
+- [FDD – If the *Initial DL Tx Power* IE, the *Primary CPICH Ec/No* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *Enhanced Primary CPICH Ec/No* IE is included in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH Secondary RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+- [FDD – If the *F-DPCH Slot Format Support Request* IE in the *F-DPCH Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the *F-DPCH Slot Format* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE includes the *F-DPCH Slot Format* IE, the DRNS may use the *F-DPCH Slot Format* IE to determine the F-DPCH slot format.]
+- [FDD – If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Processing Overload Level* IE are present in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]
+
+- [FDD – If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION REQUEST message is supported by the DRNS, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+- [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message and if DRNS has no valid data for the *E-RGCH/E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH and E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/E-HICH Channelisation Code* IE contains invalid data.]
+- [FDD – If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:]
+ - - [FDD – The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+ - - [FDD – The DRNS may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.]
+ - - [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used” in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the *Secondary CPICH Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the DRNS doesn’t include the *Secondary CPICH Information*
+
+IE, it shall not include the *Primary CPICH Usage For Channel Estimation* IE set to the value “Primary CPICH shall not be used”.]
+
+#### [FDD – Additional E-DCH Configuration Change]
+
+[FDD – If the *Additional E-DCH Cell Information RL Reconf Req* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is “Configuration Change”, then the *Additional E-DCH Cell Information Configuration Change* IE defines the new configuration and then:]
+
+- [FDD – If the *Minimum Reduced E-DPDCH Gain Factor* IE and/or the *Common DL Reference Power* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH Configuration Change Information* IE the DRNS shall use the information in the same way as for the information that is used on the Primary uplink frequency.]
+- [FDD. If the UE Context is configured for F-DPCH Slot Format operation, the DRNS shall include the *F-DPCH Slot Format* IE in the *Additional E-DCH FDD Information Response* IE for new RLs on the secondary UL frequency or in the *Additional Modified E-DCH FDD Information Response* IE for modified RLs in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### [FDD – Additional E-DCH RL Addition:]
+
+[FDD – If the *Additional E-DCH RL Specific Information To Add* IE is present in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Configuration Change Information* IE, then:]
+
+- - [FDD – The DRNS shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the *E-DCH Additional RL ID* IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
+- - [FDD – If the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE, the *E-HICH Power Offset* IE is included, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.]
+- - [FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Individual” in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION REQUEST message includes the *DL Reference Power* IE in the *Multicell E-DCH RL Specific Information* IE, the DRNS shall activate the power balancing and use the *DL Reference Power* IE for the power balancing procedure in the new Additional RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION REQUEST message at RL addition on secondary UL frequency is supported, according to subclause 8.3.15. In this case, the DRNS shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{ini}$ shall be set to the power level which is calculated based on the following IEs (if received): *Primary CPICH Ec/No* IE or the *Enhanced Primary CPICH Ec/No* IE in the *Multicell E-DCH RL Specific Information* IE or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing Additional RLs.]
+- - [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
+- - [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE
+
+Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
+
+- - [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message]
+- - [FDD – For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Add* IE, the DRNS may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the DRNS may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message and if DRNS has no valid data for the *E-RGCH/ E-HICH Channelisation Code* IE, then it shall insert the *E-RGCH/ E-HICH Channelisation Code Validity Indicator* IE to indicate that the *E-RGCH/ E-HICH Channelisation Code* IE contains invalid data.]
+- - [FDD – If the *Primary CPICH Ec/No* IE or the *Primary CPICH Ec/No* IE and the *Enhanced Primary CPICH Ec/No* IE in the *Multicell E-DCH RL Specific Information* IE measured by the UE are included for a RL in the RADIO LINK RECONFIGURATION REQUEST message, the DRNS shall use this in the calculation of the Initial DL TX Power for this additional RL. If the *Primary CPICH Ec/No* IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]
+
+#### [FDD – Additional E-DCH RL Modification:]
+
+[FDD – If the *Additional E-DCH RL Specific Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then the additional E-DCH RL indicated by the *E-DCH Additional RL ID* IE indicates the RL on which E-DCH resources shall be modified:]
+
+- [FDD – If the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE, the *E-HICH Power Offset* IE, and/or the *E-DCH DL Control Channel Grant* IE in the *Multicell E-DCH RL Specific Information* IE is included, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.]
+- [FDD – If the *DL Reference Power* IEs is included in the *Multicell E-DCH RL Specific Information* IE and power balancing is active, DRNS shall apply DL power Control in the same way as defined for the Primary uplink frequency.]
+- [FDD – If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the DRNS, the DRNS shall include the *DL Power Balancing Updated Indicator* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- - [FDD – If the RADIO LINK RECONFIGURATION RESPONSE message includes the *Primary CPICH Usage For Channel Estimation* IE and/or the *Secondary CPICH Information Change* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE, the DRNS shall avoid the new configuration in which neither the Primary CPICH nor the Secondary CPICH is used as a Phase Reference for this Radio Link.]
+
+#### [FDD – Additional E-DCH Modification:]
+
+[FDD – If the *Additional E-DCH FDD Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then:]
+
+- [FDD – If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Minimum Set E-TFCI* IE and/or the *E-DCH Maximum Bitrate* IE is included, the DRNS shall use this information for the related resource allocation operation.]
+
+- [FDD – If the *E-DCH Processing Overload Level* IE is included, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the DRNS shall notify the RNC by initiating the Radio Link Failure procedure.]
+- [FDD – If the DL TX power upper or lower limit has been re-configured for the secondary UL frequency, the DRNS shall include the new value(s) in the *Maximum DL TX Power* IE and *Minimum DL TX Power* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.
+- [FDD – The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s), and the DRNS shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Maximum Uplink SIR* IE and *Minimum Uplink SIR* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RLReconf* IE for each Radio Link when these values are changed.]
+- [FDD – If the Additional E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional Modified E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+#### **[FDD – Additional E-DCH Removal]**
+
+[FDD – If the *Additional E-DCH Cell Information RL Reconf Req* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is “Removal”, then the additional E-DCH on the secondary uplink frequency shall be removed.]
+
+#### **[TDD – Intra- DRNS Serving E-DCH Radio Link Change:]**
+
+[TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Serving RL* IE, this indicates the new Serving E-DCH Radio Link:]
+
+- [TDD – In the new configuration the DRNS shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.]
+- [3.84Mcps TDD – The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response* IE in the *E-DCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [1.28Mcps TDD – The DRNS shall allocate E-AGCH parameters and E-HICH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response* IE and the *E-HICH Specific Information Response* IE in the *E-DCH Information Response 1.28Mcps* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [7.68Mcps TDD – The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the *E-AGCH Specific Information Response 7.68Mcps* IE in the *E-DCH TDD Information Response 7.68Mcps* IE in the RADIO LINK RECONFIGURATION READY message.]
+- [TDD – If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+
+#### **[TDD – E-PUCH Handling:]**
+
+[3.84Mcps TDD and 7.68Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-PUCH Information* IE, the DRNS shall apply the parameters to the new configuration.]
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-PUCH Information LCR* IE, the DRNS shall apply the parameters to the new configuration.]
+
+[TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-TFCS Information* IE, the DRNS shall apply the beta parameters to the new configuration.]
+
+### **[3.84Mcps TDD – E-DCH Setup:]**
+
+[3.84Mcps TDD – the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE and *E-DCH TDD Information* IE.]
+
+### **[1.28Mcps TDD – E-DCH Setup:]**
+
+[1.28Mcps TDD – the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information LCR* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE and *E-DCH TDD Information LCR* IE.]
+
+[1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]
+
+### **[7.68Mcps TDD – E-DCH Setup:]**
+
+[7.68Mcps TDD – the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE and *E-DCH TDD Information 7.68Mcps* IE.]
+
+### **[TDD- E-DCH MAC-d Flow Addition/Deletion:]**
+
+[TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes any *E-DCH MAC-d Flows To Add* or *E-DCH MAC-d Flows To Delete* IEs, then the DRNS shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]
+
+[TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH TDD Information To Add* IE, then the DRNS shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.]
+
+[TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNS shall delete the E-DCH configuration from the UE Context and release the E-DCH resources.]
+
+[TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flows To Add* IE, then:]
+
+- [TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.]
+- [1.28Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Maximum Bit Rate LCR* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+
+### **[3.84Mcps TDD – E-DCH Non-scheduled allocations:]**
+
+[3.84Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information TDD* IE in the *E-DCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+### **[1.28Mcps TDD – E-DCH Non-scheduled allocations:]**
+
+[1.28Mcps – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information LCR TDD* IE in the *E-DCH Information Response 1.28Mcps* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+**[7.68Mcps TDD – E-DCH Non-scheduled allocations:]**
+
+[7.68Mcps TDD – The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the *E-DCH Non-scheduled Grant Information 7.68Mcps TDD* IE in the *E-DCH Information Response 7.68Mcps* IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+**[3.84Mcps TDD – E-DCH Modification:]**
+
+[3.84Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH TDD Information* IE, then:]
+
+- [3.84Mcps TDD – If the *E-DCH TDD Information* IE includes the *E-DCH TDD Maximum Bitrate* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [3.84Mcps TDD – If the *E-DCH TDD Information* IE includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [3.84Mcps TDD – If the *E-DCH TDD Information* IE includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+
+**[1.28Mcps TDD – E-DCH Modification:]**
+
+[1.28Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH TDD Information LCR* IE, then:]
+
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *Maximum Number of Retransmission for Scheduling Info LCR* IE and the *E-DCH Retransmission timer for Scheduling Info LCR* IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information LCR* IE includes the *Multi-Carrier E-DCH Physical Layer Category LCR* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
+- [1.28Mcps TDD – If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]
+
+**[7.68Mcps TDD – E-DCH Modification:]**
+
+[7.68Mcps TDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH TDD Information 7.68Mcps* IE, then:]
+
+- [7.68Mcps TDD – If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+
+- [7.68Mcps TDD – If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH Processing Overload Level* IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]
+- [7.68Mcps TDD – If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH Power Offset for Scheduling Info* IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
+
+[TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH TDD Information To Modify* IE, then:]
+
+- [TDD- If the *E-DCH TDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the DRNS shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE contains a *TNL QoS* IE for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.]
+- [1.28Mcps TDD – If the *E-DCH TDD Information To Modify* IE includes the *E-DCH MAC-d Flow Retransmission Timer* IE for an E-DCH MAC-d flow then the DRNS shall use this information to set the retransmission timer.]
+- [TDD– If the *TNL QoS* IE is included in the *E-DCH TDD Information to Modify* IE for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH HARQ Power Offset TDD* IE for an E-DCH MAC-d flow the DRNS shall use this new power offset value.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE contains the *E-DCH Grant Type* IE, the DRNS shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the DRNS shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.]
+- [TDD- If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Logical Channel To Modify* IE, the DRNS shall use this information to modify the indicated logical channels:]
+ - - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the DRNS shall apply the values in the new configuration.]
+ - - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the DRNS shall apply the values in the new configuration.]
+ - - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Guaranteed Bit Rate* IE, the DRNS shall apply the values in the new configuration.]
+ - - [TDD – If the *E-DCH Logical Channel To Modify* IE includes *E-DCH DDI Value* IE, the DRNS shall apply the values in the new configuration.]
+ - - [1.28Mcps TDD – If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Maximum Bit Rate LCR* IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
+
+- - [TDD – If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the DRNC shall apply the value in the new configuration.]
+- [TDD– If the *E-DCH TDD Information To Modify* IE includes the *MAC-e Reset Indicator* IE, then the DRNS shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]
+
+#### [1.28Mcps TDD –Multi-Carrier E-DCH Continue:]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.]
+
+#### [1.28Mcps TDD – Multi-Carrier E-DCH Setup:]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Setup", then the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:]
+
+- [1.28Mcps TDD - The DRNS shall use the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE to decide the transport bearer mode in the new configuration.]
+- [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+
+#### [1.28Mcps TDD – Multi-Carrier E-DCH Change:]
+
+- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Change", then the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:]
+ - - [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is different from current configured frequencies, then the DRNS shall setup the E-DCH resources, as requested in the DRNS Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+ - - [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is the same as any current configured frequency, then the DRNS shall reconfigure the E-DCH resources, as requested or as configured in the DRNS Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.]
+
+[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Change" and the *Removal UL Multi-Carrier info* IE is included, then the DRNS shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the *UARFCN* IE in the *Removal UL Multi-Carrier info* IE.]
+
+#### General:
+
+If the requested modifications are allowed by the DRNS, and if the DRNS has successfully allocated the required resources and changed to the new configuration, the DRNC shall respond to the SRNC with the RADIO LINK RECONFIGURATION RESPONSE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *RL Specific DCH Information* IE, *HS-DSCH Information* IE, *HS-DSCH Information To Modify Unsynchronised* IE, *HS-DSCH MAC-d Flows To Add* IE, [FDD – *RL Specific E-DCH Information* IE] [TDD – *E-DCH MAC-d Flows to Add* IE], the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included], HS-DSCH MAC-d flow being added or E-DCH MAC-d flow [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included] being added, or any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included] or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE.
+
+The DRNC shall include the *Transport Layer Address* IE and the *Binding ID* IE in the RADIO LINK RECONFIGURATION RESPONSE message for any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included], HS-DSCH MAC-d flow being added or E-DCH MAC-d flow [FDD – for
+
+which the *Transport Bearer Not Requested Indicator* IE is not included] being added, or any Transport Channel [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included], HS-DSCH MAC-d flow or E-DCH MAC-d flow [FDD – for which the *Transport Bearer Not Requested Indicator* IE was not included] being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [4], subclause 5.10.1, and in TS 25.425 [32], subclause 5.3.2.
+
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer Shall not be Established” for a DCH or an E-DCH MAC-d flow being added, then the DRNC shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.]
+- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to “Transport Bearer may not be Established” for a DCH or an E-DCH MAC-d flow being added and:]
+ - - [FDD – if the DRNC establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.]
+ - - [FDD – if the DRNC does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the DRNC shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.]
+
+In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iur interface, the DRNC shall include the *Transport Layer Address* IE and the *Binding ID* IE in the *DCH Information Response* IE only for one of the DCHs [FDD – for which the *Transport Bearer Not Requested Indicator* IE is not included] in the set of co-ordinated DCHs.
+
+In the case of a Radio Link being combined with another Radio Link within the DRNS, the DRNC shall include the *Transport Layer Address* IE and the *Binding ID* IE [FDD for the concerned DCH for which the *Transport Bearer Not Requested Indicator* IE is not included] in the *DCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message for only one of the combined Radio Links.
+
+[FDD – In the case of an E-DCH RL being combined with another E-DCH RL within the DRNS, the *E-DCH FDD Information Response* IE shall be included only for one of the combined E-DCH RLs.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Additional E-DCH Cell Information RL Reconf Req* IE, then:]
+
+- [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “Separate Iur Transport Bearer Mode” the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+- [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to “UL Flow Multiplexing Mode” the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
+- [FDD – if Separate Iur Transport Bearer Mode is used in the new configuration, then:]
+ - - [FDD – the DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Not Requested Indicator* IE in the *RL Specific E-DCH Information* IE in the *RL Information* IE and/or the *Transport Bearer Request Indicator* IE in the *E-DCH FDD Information To Modify* IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.]
+ - - [FDD – If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE or in the *Additional E-DCH RL Specific Information To Add* IE and/or the *Additional E-DCH RL Specific Information To Modify* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information Configuration Change* IE, then the
+
+DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MAC-d flow the DRNS shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION RESPONSE message in the *Additional E-DCH Cell Information Response RLReconf IE* the *Binding ID IE* and *Transport Layer Address IE* in the *Additional E-DCH MAC-d Flow Specific Information Response IE* in the *Additional E-DCH FDD Information Response IE* for new E-DCH radio links on the Secondary UL frequency and/or include the *Binding ID IE* and *Transport Layer Address IE* in the *Additional E-DCH MAC-d Flow Specific Information Response IE* in the *Additional Modified E-DCH FDD Information Response IE* for radio links on the Secondary UL frequency that has been modified.]
+
+[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Multi-Carrier E-DCH Information Reconf IE*, then:]
+
+- [1.28Mcps TDD - If the *Multi-carrier E-DCH Transport Bearer Mode LCR IE* is set to "Separate Iur Transport Bearer Mode" the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
+- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR IE* is set to "UL Flow Multiplexing Mode" the DRNS shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.]
+- [1.28Mcps TDD - If the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf IE* is "Setup" and the Separate Iur transport bearer mode is used in the new configuration, or if the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf IE* is "Change" and the Transport Bearer Mode is changed to "Separate Iur Transport Bearer Mode" indicated by *Multi-carrier E-DCH Transport Bearer Mode LCR IE*, then the DRNS shall include the *Binding ID IE* and *Transport Layer Address IE* in the *Multi-Carrier E-DCH Information Response LCR IE* in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+- [1.28Mcps TDD - The DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Request Indicator IE* in the *E-DCH TDD Information to Modify IE* received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.]
+- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the *Transport Bearer Request Indicator IE* is set to " Bearer Requested ", then the DRNS shall include the *Binding ID IE* and *Transport Layer Address IE* in the *E-DCH TDD Information Response 1.28Mcps IE* in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
+
+Any allowed rate for the uplink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Allowed UL Rate IE* in the *DCH Information Response IE* for this Radio Link.
+
+Any allowed rate for the downlink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Allowed DL Rate IE* in the *DCH Information Response IE* for this Radio Link.
+
+The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s), and the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Maximum Uplink SIR IE* and *Minimum Uplink SIR IE* for each Radio Link when these values are changed.
+
+[FDD – If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* in the RADIO LINK RECONFIGURATION RESPONSE message. The DRNS shall not transmit with a higher power than indicated by the *Maximum DL TX Power IE* or lower than indicated by the *Minimum DL TX Power IE* on any DL DPCH or on the F-DPCH of the RL except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the $\delta P_{curr}$ , as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
+
+[3.84 Mcps TDD and 7.68 Mcps TDD – If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* in the RADIO LINK RECONFIGURATION RESPONSE message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the new value(s) for that CCTrCH in the *CCTrCH Maximum DL TX Power IE* and *CCTrCH Minimum DL TX Power IE*. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power IE/CCTrCH Maximum DL TX Power IE* or lower than indicated by the appropriate *Minimum DL TX Power IE/CCTrCH Minimum DL TX Power IE* on any DL DPCH within each CCTrCH of the RL.]
+
+[1.28 Mcps TDD – If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* in the RADIO LINK RECONFIGURATION RESPONSE message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the new value(s) for that timeslot in the *Maximum DL TX Power IE* and *Minimum DL TX Power IE* within the *DL Timeslot Information LCR IE*. The DRNS shall not transmit with a higher power than indicated by the appropriate *Maximum DL TX Power IE* or lower than indicated by the appropriate *Minimum DL TX Power IE* on any DL DPCH within each timeslot of the RL.]
+
+### 8.3.7.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ SRNC->>DRNC: RADIO LINK RECONFIGURATION REQUEST
+ DRNC-->>SRNC: RADIO LINK RECONFIGURATION FAILURE
+
+```
+
+Sequence diagram showing an unsuccessful radio link reconfiguration procedure between SRNC and DRNC. The SRNC sends a RADIO LINK RECONFIGURATION REQUEST to the DRNC, and the DRNC responds with a RADIO LINK RECONFIGURATION FAILURE.
+
+**Figure 15: Unsynchronised Radio Link Reconfiguration procedure, Unsuccessful Operation**
+
+If the DRNS cannot allocate the necessary resources for all the new DCHs in a set of co-ordinated DCHs requested to be added, it shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed.
+
+If the requested Unsynchronised Radio Link Reconfiguration procedure fails for one or more Radio Link(s), the DRNC shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC, indicating the reason for failure.
+
+[FDD – If the *MIMO Activation Indicator IE* is included and the *Power Offset For S-CPICH for MIMO Request Indicator IE* is not included in the *HS-DSCH FDD Information IE* in the *HS-DSCH Serving Cell Change Information IE* in the RADIO LINK RECONFIGURATION REQUEST message or MIMO is activated and the power offset for S-CPICH for MIMO Request indicator has not been configured in the UE Context but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link, and/or activation of MIMO, shall be reported as failed and the DRNC shall include in the RADIO LINK RECONFIGURATION FAILURE message the *Cause IE*.]
+
+[FDD – If the *MIMO with four transmit antennas Activation Indicator IE* or the *Dual Stream MIMO with four transmit antennas Activation Indicator IE* is included and the *Power Offset For S-CPICH for MIMO with four transmit antennas Request Indicator IE* is not included in the *HS-DSCH FDD Information IE* in the *HS-DSCH Serving Cell Change Information IE* in the RADIO LINK RECONFIGURATION REQUEST message or MIMO with four transmit antennas is activated and the power offset for S-CPICH for MIMO with four transmit antennas Request indicator has not been configured in the UE Context but MIMO with four transmit antennas Pilot Configuration is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link, and/or activation of MIMO with four transmit antennas, shall be reported as failed and the DRNC shall include in the RADIO LINK RECONFIGURATION FAILURE message the *Cause IE*.]
+
+Typical cause values are:
+
+#### Radio Network Layer Causes:
+
+UL Scrambling Code Already in Use;
+ DL Radio Resources not Available;
+ UL Radio Resources not Available;
+ Requested Configuration not Supported;
+ CM not Supported;
+ E-DCH not supported;
+ [FDD – Continuous Packet Connectivity DTX-DRX operation not Supported;]
+ [FDD – Continuous Packet Connectivity HS-SCCH less operation not Supported;]
+
+[FDD – MIMO not supported;]
+ [FDD – E-DCH TTI2ms not supported;]
+ [FDD – Continuous Packet Connectivity DTX-DRX operation not available;]
+ [FDD – Continuous Packet Connectivity UE DTX Cycle not available;]
+ [FDD – MIMO not available;]
+ [FDD – SixteenQAM UL not Supported;]
+ HS-DSCH MAC-d PDU Size Format not supported;
+ E-DCH MAC-d PDU Size Format not available;
+ [FDD – E-DPCCH Power Boosting not supported;]
+ [FDD – SixtyfourQAM DL and MIMO Combined not available;]
+ [FDD – Multi Cell operation not available;]
+ [FDD – Multi Cell operation not supported;]
+ [FDD – SixtyfourQAM DL and MIMO Combined not supported;]
+ [1.28Mcps TDD – MIMO not available;]
+ [1.28Mcps TDD- SixteenQAM UL not Supported;]
+ [1.28Mcps TDD – SixtyfourQAM DL and MIMO Combined not available;]
+ [FDD – Single Stream MIMO not supported;]
+ [FDD – Single Stream MIMO not available;]
+ [FDD – Multi Cell operation with MIMO not available;]
+ [FDD – Multi Cell operation with MIMO not supported;]
+ [FDD – Multi Cell E-DCH Operation not supported;]
+ [FDD – Multi Cell E-DCH Operation not available;]
+ [FDD – Multi Cell operation with Single Stream MIMO not available;]
+ [FDD – Multi Cell operation with Single Stream MIMO not supported;]
+ [FDD – Uplink Closed Loop Transmit Diversity Operation Not Available;]
+ [FDD – Uplink Closed Loop Transmit Diversity Operation Not Supported;]
+ [FDD – MIMO with four transmit antennas not supported;]
+ [FDD – MIMO with four transmit antennas not available;]
+ [FDD – Dual Stream MIMO with four transmit antennas not supported;]
+ [FDD – Dual Stream MIMO with four transmit antennas not available;]
+ [FDD – Multiflow Operation Not Available;]
+ [FDD – Multiflow Operation Not Supported;]
+ [FDD – SixtyfourQAM UL not Available;]
+ [FDD – SixtyfourQAM UL not Supported;]
+ [FDD – UL MIMO Operation Not Available;]
+ [FDD – UL MIMO Operation Not Supported;]
+ [FDD – UL MIMO and SixteenQAM Operation Not Available;]
+ [FDD – UL MIMO and SixteenQAM Operation Not Supported;]
+ [FDD – UL MIMO and SixtyfourQAM Operation Not Available;]
+ [FDD – UL MIMO and SixtyfourQAM Operation Not Supported.]
+
+#### Miscellaneous Causes:
+
+Control Processing Overload;
+ Not enough User Plane Processing Resources.
+
+### 8.3.7.4 Abnormal Conditions
+
+If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed, and the DRNC shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC.
+
+If more than one DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to “selected” [TDD – or no DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to “selected”], the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure, and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes a *DCHs To Modify* IE or *DCHs To Add* IE with multiple *DCH Specific Info* IEs, and if the DCHs in the *DCHs To Modify* IE or *DCHs To Add* IE do not have the same *Transmission Time Interval* IE in the *Semi-static Transport Format Information* IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *DL Reference Power Information* IE, but the power balancing is not active in the indicated RL(s), the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed and the DRNC shall respond the RADIO LINK RECONFIGURATION FAILURE message with the cause value “Power Balancing status not compatible”.]
+
+[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Common” in the existing RL(s) but the *DL Reference Power Information* IE includes the *Individual DL Reference Power Information* IE, the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value “Power Balancing status not compatible”.]
+
+[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to “Individual” in the existing RL(s) but the *DL Reference Power Information* IE includes the *Common DL Reference Power* IE, the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value “Power Balancing status not compatible”.]
+
+If the RADIO LINK RECONFIGURATION REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added, or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE., and not both are present for a transport bearer intended to be established, the DRNC shall reject the Unsynchronised Radio Link Reconfiguration procedure, and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE or *HS-DSCH MAC-d Flows To Delete* IE in addition to the *HS-DSCH Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE, *HS-DSCH MAC-d Flows To Delete* IE or *HS-PDSCH RL ID* IE and the Serving HS-DSCH Radio Link is not in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Information* IE and does not include the *HS-PDSCH RL-ID* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-PDSCH RL-ID* IE indicating a Radio Link not existing in the UE Context, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *HS-DSCH Information* IE, *HS-DSCH Information To Modify* IE, or *HS-DSCH MAC-d Flows To Add* IE and if in the new configuration the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Indexed MAC-d PDU Size” for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Flexible MAC-d PDU Size” for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the UE Context is configured to use “Fixed MAC-d PDU Size” for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use “Flexible MAC-d PDU Size” for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the RADIO LINK RECONFIGURATION REQUEST message includes *HS-DSCH Information* IE and the HS-DSCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, but the *E-DPCH Information* IE is not present or if any of the *Maximum Set of E-DPDCHs* IE, *Puncture Limit* IE, *E-TFCS Information* IE, *E-TTI* IE, *E-DPCCH Power Offset* IE, *E-RGCH 2-Index-Step Threshold* IE, *E-RGCH 3-Index-Step Threshold* IE, *HARQ Info for E-DCH* IE or *HS-DSCH Configured Indicator* IE are not present in the *E-DPCH Information* IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If any of the *HS-DSCH Configured Indicator* IE, *Maximum Set of E-DPDCHs* IE, *Puncture Limit* IE or *E-TTI* IE are present in the *E-DPCH Information* IE and the *E-DCH FDD Information* IE is not present in the RADIO LINK RECONFIGURATION REQUEST message, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH RL Indication* IE set to “E-DCH”, but no *E-DCH FDD Information* IE, and the UE Context is not configured for E-DCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH FDD Information* IE but no *E-DCH RL Indication* IE set to “E-DCH”, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If the RADIO LINK RECONFIGURATION REQUEST message contains the *HS-PDSCH RL ID* IE and/or the *Serving E-DCH RL* IE and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *HS-PDSCH RL ID* IE and the *E-DPCH Information* IE which includes the *HS-DSCH Configured Indicator* IE set as “HS-DSCH not configured” then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *E-DCH FDD Information To Modify* IE, *E-DCH MAC-d Flows To Add* IE or *E-DCH MAC-d Flows To Delete* IE in addition to the *E-DCH FDD Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *E-DCH FDD Information To Modify* IE, *E-DCH MAC-d Flows To Add* IE, *E-DCH MAC-d Flows To Delete* IE and the UE Context is not configured for E-DCH, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH FDD Information To Modify* IE deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes *E-DCH FDD Information* IE and the E-DCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE in addition to the *Continuous Packet Connectivity DTX-DRX Information* IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE in addition to the *Continuous Packet Connectivity HS-SCCH less Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE while the Continuous Packet Connectivity HS-SCCH less configuration isn't configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE while the Continuous Packet Connectivity *DTX-DRX* configuration isn't configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *DRX Information To Modify* IE in *Continuous Packet Connectivity DTX-DRX Information To Modify* IE while the Continuous Packet Connectivity *DRX* configuration is not configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH Indicator* IE set to “Uplink DCH only” but no *Transport Format Set* IE for the uplink for this DCH and the DRNC had ignored the configuration of Transport Format Set for uplink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH Indicator* IE set to “Downlink DCH only” but no *Transport Format Set* IE for the downlink for this DCH and the DRNC had ignored the configuration of Transport Format Set for downlink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Transport Bearer Not Requested Indicator* IE for a DCH or an E-DCH MAC-d flow but does not contain the corresponding *DCH ID* IE and the *Unidirectional DCH indicator* IE set to “Uplink DCH only” for the DCH in *DCH Information To Add* IE or does not contain the corresponding *E-DCH MAC-d Flow ID* IE in *E-DCH MAC-d Flows Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply MIMO, allowed to apply 64QAM, establish the secondary serving HS-DSCH Radio Link, apply MIMO with four transmit antennas or apply Dual Stream MIMO with four transmit antennas or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional HS Cell Information RL Reconf Req* IE indicating a new secondary serving cell that is not in the same Node B as the serving HS-DSCH cell (or new serving in case of simultaneous serving HS-DSCH cell change), then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH in the *RL Specific DCH Information* IE but does not include the *DCH ID* IE for the DCH in the *DCHs to Add* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for an E-DCH MAC-d flow in the *RL Specific E-DCH Information* IE but does not include the *E-DCH MAC-d flow ID* IE for the E-DCH MAC-d flow in the *E-DCH MAC-d flows Information* IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Continuous Packet Connectivity DTX-DRX Information* IE but the concerned UE Context is not previously configured to use F-DPCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to have the Serving E-DCH Radio Link but there is at least one E-DCH MAC-d flow which the transport bearer is not configured for the Serving E-DCH Radio Link in DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH or the E-DCH MAC-d Flow in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+If ALCAP is not used, if the concerned UE Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the DCH, the E-DCH MAC-d flow and/or HS-DSCH MAC-d flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use "Flexible RLC PDU Size" for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+If, in the new configuration, the concerned UE Context is configured to use MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use "Flexible RLC PDU Size", the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Req* IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the concerned UE Context is configured to apply more than one of MIMO, MIMO with four transmit antennas, Dual Stream MIMO with four transmit antennas and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional E-DCH Cell Information RL Reconf Req* IE and if the *E-DPCH Information* IE is not present or the E-DPCH Information was not configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional E-DCH Cell Information RL Reconf Req* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE in the *Additional E-DCH Cell Information RL Reconf Req* IE and the *C-ID* IE is not included but the RL indicated by the *E-DCH Additional RL ID* IE is not configured in the current UE context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional HS Cell Information RL Reconf Req* IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1" which are previously assigned to the RL or received in the *Ordinal Number Of Frequency* IE in the *HS-DSCH FDD Secondary Serving Information* IE or the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional HS Cell Information RL Reconf Req* IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *UL CLTD Information* IE but does not contain the *F-TPICH Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL CLTD Information* IE but without *F-TPICH Information* IE, then the DRNC shall reject the procedure using the RADIO LINK REQUEST FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *UL MIMO Information* IE in *E-DCH FDD Information* IE but does not contain the *UL CLTD Information* IE, or if it contains *HS-DSCH*
+
+*Preconfiguration Setup* IE with *UL MIMO Information* IE but without *UL CLTD Information* IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
+
+## 8.3.8 Physical Channel Reconfiguration
+
+### 8.3.8.1 General
+
+The Physical Channel Reconfiguration procedure is used by the DRNS to request the SRNC to reconfigure one of the configured physical channels.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The DRNS shall not initiate the Physical Channel Reconfiguration procedure if a Prepared Reconfiguration exists as defined in subclause 3.1, or if a Synchronised Radio Link Reconfiguration Preparation procedure, Unsynchronised Radio Link Reconfiguration procedure or Radio Link Deletion procedure is ongoing for the relevant UE context.
+
+### 8.3.8.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ DRNC->>SRNC: PHYSICAL CHANNEL RECONFIGURATION REQUEST
+ SRNC-->>DRNC: PHYSICAL CHANNEL RECONFIGURATION COMMAND
+
+```
+
+Sequence diagram showing the Physical Channel Reconfiguration procedure. The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION REQUEST to the DRNC, and the DRNC responds with a PHYSICAL CHANNEL RECONFIGURATION COMMAND.
+
+**Figure 16: Physical Channel Reconfiguration procedure, Successful Operation**
+
+When the DRNC detects the need to modify one of its physical channels, it shall send a PHYSICAL CHANNEL RECONFIGURATION REQUEST to the SRNC.
+
+The PHYSICAL CHANNEL RECONFIGURATION REQUEST message contains the new value(s) of the physical channel parameter(s) of the radio link for which the DRNC is requesting the reconfiguration.
+
+[FDD – If compressed mode is prepared or active and at least one of the downlink compressed mode methods is “SF/2”, the DRNC shall include the *Transmission Gap Pattern Sequence Scrambling Code Information* IE in the *DL Code Information* IE in the PHYSICAL CHANNEL RECONFIGURATION REQUEST message indicating for each DL Channelisation Code whether the alternative scrambling code will be used or not if the downlink compressed mode methods “SF/2” is activated.]
+
+[TDD – The SRNC shall apply the new values for any of [3.84Mcps TDD – *UL Code Information* IE, *Midamble Shift And Burst Type* IE,] [1.28Mcps TDD – *UL Code Information LCR* IE, *Midamble Shift LCR* IE,] [7.68 Mcps TDD – *UL Code Information 7.68 Mcps* IE, *Midamble Shift And Burst Type 7.68 Mcps* IE,] *TDD DPCH Offset* IE, *Repetition Period* IE, *Repetition Length* IE, or *TFCI presence* IE included in the *UL DPCH Information* IE within the PHYSICAL CHANNEL RECONFIGURATION REQUEST message, otherwise the previous values specified for this DPCH shall still apply.]
+
+[TDD – The SRNC shall apply the new values for any of [3.84Mcps TDD – *DL Code Information* IE, *Midamble Shift And Burst Type* IE,] [1.28Mcps TDD – *DL Code Information LCR* IE, *Midamble Shift LCR* IE,] [7.68 Mcps TDD – *DL Code Information 7.68 Mcps* IE, *Midamble Shift And Burst Type 7.68 Mcps* IE,] *TDD DPCH Offset* IE, *Repetition Period* IE, *Repetition Length* IE, or *TFCI presence* IE included in the *DL DPCH Information* IE within the PHYSICAL CHANNEL RECONFIGURATION REQUEST message, otherwise the previous values specified for this DPCH shall still apply.]
+
+[3.84 Mcps TDD – If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes *HS-PDSCH Timeslot Specific Information* IE the SRNC shall apply the values of the *Midamble Shift And Burst Type* IE for each HS-PDSCH timeslot.]
+
+[1.28 Mcps TDD – If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes *HS-PDSCH Timeslot Specific Information LCR* IE the SRNC shall apply the values of the *Midamble Shift LCR* IE for each HS-PDSCH timeslot.]
+
+[1.28 Mcps TDD – if the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes the *PLCH Information* IE the SRNC shall modify, delete or grant a new PLCH assignment to the indicated timeslot of the indicated UL DCH-type CCTrCH according to its content.]
+
+[7.68 Mcps TDD – If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes *HS-PDSCH Timeslot Specific Information 7.68 Mcps* IE the SRNC shall apply the values of the *Midamble Shift And Burst Type 7.68 Mcps* IE for each HS-PDSCH timeslot.]
+
+[FDD – If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes *F-DPCH Slot Format* IE the SRNC shall apply the values of the *F-DPCH Slot Formats* IE for F-DPCH Slot Format operation.]
+
+Upon receipt of the PHYSICAL CHANNEL RECONFIGURATION REQUEST, the SRNC shall decide an appropriate execution time for the change. The SRNC shall respond with a PHYSICAL CHANNEL RECONFIGURATION COMMAND message to the DRNC that includes the *CFN* IE indicating the execution time.
+
+At the CFN, the DRNC shall switch to the new configuration that has been requested, and release the resources related to the old physical channel configuration.
+
+[FDD – If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes the *F-TPICH Slot Format* IE in *F-TPICH Reconfiguration Information* IE the SRNC shall apply the values of the *F-TPICH Slot Format* IE for F-TPICH Slot Format operation.]
+
+[FDD – If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes the *F-TPICH Channelisation Code Number* IE in the *F-TPICH Reconfiguration Information* IE the SRNC shall use this information to configure the channelization code of F-TPICH.]
+
+### 8.3.8.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: PHYSICAL CHANNEL RECONFIGURATION REQUEST
+ DRNC->>SRNC: PHYSICAL CHANNEL RECONFIGURATION REQUEST
+ Note left of SRNC: PHYSICAL CHANNEL RECONFIGURATION FAILURE
+ SRNC-->>DRNC: PHYSICAL CHANNEL RECONFIGURATION FAILURE
+
+```
+
+Sequence diagram showing the Unsuccessful Operation of the Physical Channel Reconfiguration procedure. The diagram shows two vertical lifelines for SRNC and DRNC. A message labeled 'PHYSICAL CHANNEL RECONFIGURATION REQUEST' is sent from the DRNC to the SRNC. A return message labeled 'PHYSICAL CHANNEL RECONFIGURATION FAILURE' is sent from the SRNC to the DRNC.
+
+**Figure 17: Physical Channel Reconfiguration procedure, Unsuccessful Operation**
+
+If the SRNC cannot accept the reconfiguration request it shall send the PHYSICAL CHANNEL RECONFIGURATION FAILURE message to the DRNC, including the reason for the failure in the *Cause* IE.
+
+Typical cause values are:
+
+#### Radio Network Layer Causes:
+
+- Reconfiguration not Allowed.
+
+### 8.3.8.4 Abnormal Conditions
+
+While waiting for the PHYSICAL CHANNEL RECONFIGURATION COMMAND message, if the DRNC receives any of the RADIO LINK RECONFIGURATION PREPARE, RADIO LINK RECONFIGURATION REQUEST, or RADIO LINK DELETION REQUEST messages, the DRNC shall abort the Physical Channel Reconfiguration procedure. These messages thus override the DRNC request for physical channel reconfiguration.
+
+When the SRNC receives a PHYSICAL CHANNEL RECONFIGURATION REQUEST message while a Synchronised Radio Link Reconfiguration procedure, Unsynchronised Radio Link Reconfiguration procedure or Radio Link Deletion procedure is ongoing, the SRNC shall ignore the request message and assume that receipt of any of the messages RADIO LINK RECONFIGURATION PREPARE, RADIO LINK RECONFIGURATION REQUEST or RADIO LINK DELETION REQUEST by the DRNC has terminated the Physical Channel Reconfiguration procedure. In this case the SRNC shall not send a PHYSICAL CHANNEL RECONFIGURATION FAILURE message to the DRNC.
+
+## 8.3.9 Radio Link Failure
+
+### 8.3.9.1 General
+
+This procedure is started by the DRNS when one or more Radio Links [FDD – or Radio Link Sets][TDD – or CCTrCHs within a Radio Link] are no longer available.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The DRNS may initiate the Radio Link Failure procedure at any time after establishing a Radio Link.
+
+### 8.3.9.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of DRNC: RL unavailable
+ DRNC->>SRNC: RADIO LINK FAILURE INDICATION
+
+```
+
+Sequence diagram showing the Radio Link Failure procedure. A vertical line on the left represents the SRNC. A vertical line on the right represents the DRNC. Inside the DRNC's lifeline, there is a box labeled 'RL unavailable'. A horizontal arrow labeled 'RADIO LINK FAILURE INDICATION' points from the DRNC's lifeline to the SRNC's lifeline.
+
+**Figure 18: Radio Link Failure procedure, Successful Operation**
+
+When the DRNC detects that one or more Radio Link(s) [FDD – or Radio Link Set(s)] [TDD – or CCTrCHs within a Radio Link] are no longer available, it shall send the RADIO LINK FAILURE INDICATION message to the SRNC. The message indicates the failed Radio Link(s) [FDD – or Radio Link Set(s)] [TDD – or CCTrCHs] with the most appropriate cause values defined in the *Cause* IE. If the failure concerns one or more individual Radio Links the DRNC shall include the affected Radio Link(s) using the *RL Information* IE. [FDD – If the failure concerns one or more Radio Link Set(s) the DRNC shall include the affected Radio Link Set(s) using the *RL Set Information* IE.] [TDD – If the failure concerns only the failure of one or more CCTrCHs within in a radio link the DRNC shall include the affected CCTrCHs using the *CCTrCH ID* IE.]
+
+When the RL Failure procedure is used to notify loss of UL synchronisation of a [FDD – Radio Link Set] [TDD – Radio Link or CCTrCHs within a Radio Link] on the Uu interface, the RADIO LINK FAILURE INDICATION message shall be sent with the *Cause* IE set to “Synchronisation Failure” when indicated by the UL synchronisation detection algorithm defined in TS 25.214 [10] subclause 4.3 and TS 25.224 [22] subclause 4.4.2.
+
+[FDD – When the Radio Link Failure procedure is used to indicate permanent failure in one or more Radio Link(s)/Radio Link Set(s) due to the occurrence of an UL or DL frame with more than one transmission gap caused by one or more compressed mode pattern sequences, the DL transmission shall be stopped and the RADIO LINK FAILURE INDICATION message shall be sent with the *Cause Value* IE set to “Invalid CM Settings”. After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the DRNS shall not remove the Radio Link(s)/Radio Link Set(s) from the UE Context, or remove the UE Context itself.]
+
+[FDD – When the Radio Link Failure Procedure is used to indicate E-DCH non serving cell processing issue, the RADIO LINK FAILURE INDICATION shall be sent, with the *Cause* IE set to “Not enough user plane processing resources”.]
+
+In the other cases the Radio Link Failure procedure is used to indicate that one or more Radio Link(s) [FDD – or Radio Link Set(s)] are permanently unavailable and cannot be restored. After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the DRNS shall not remove the Radio Link from the UE Context, or remove the UE Context itself. When applicable, the allocation retention priorities associated with the transport channels shall be used by the DRNS to prioritise which Radio Links to indicate as unavailable to the SRNC.
+
+Typical cause values are:
+
+#### Radio Network Layer Causes:
+
+Synchronisation Failure;
+Invalid CM Settings.
+
+#### Transport Layer Causes:
+
+Transport Resources Unavailable.
+
+#### Miscellaneous Causes:
+
+Control Processing Overload;
+HW Failure;
+O&M Intervention;
+Not enough user plane processing resources.
+
+### 8.3.9.3 Abnormal Conditions
+
+-
+
+## 8.3.10 Radio Link Restoration
+
+### 8.3.10.1 General
+
+This procedure is used to notify establishment and re-establishment of UL synchronisation of one or more [FDD – RL Set(s)] [TDD – Radio Links or CCTrCH(s) in a Radio Link] on the Uu interface.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The DRNC may initiate the Radio Link Restoration procedure at any time after establishing a Radio Link.
+
+### 8.3.10.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: RADIO LINK RESTORE INDICATION
+ DRNC->>SRNC: RADIO LINK RESTORE INDICATION
+```
+
+Sequence diagram showing the Radio Link Restoration procedure. The diagram consists of two vertical lines representing the SRNC (left) and DRNC (right). A horizontal arrow labeled 'RADIO LINK RESTORE INDICATION' points from the DRNC to the SRNC.
+
+**Figure 19: Radio Link Restoration procedure, Successful Operation**
+
+The DRNC shall send the RADIO LINK RESTORE INDICATION message to the SRNC when and as specified by the UL Uu synchronisation detection algorithm defined in TS 25.214 [10] subclause 4.3 and TS 25.224 [22] subclause 4.4.2 [FDD -, or when the *Fast Reconfiguration Mode* IE has been included in the RADIO LINK RECONFIGURATION COMMIT message and the DRNS has detected that the UE has changed to the new configuration. The algorithm in TS 25.214 [10] shall use the minimum value of the parameters N\_INSYNC\_IND that are configured in the cells supporting the radio links of the RL Set.]
+
+[TDD – If the re-established UL Uu synchronisation concerns one or more individual Radio Links the DRNC shall include in the RADIO LINK RESTORE INDICATION message the *RL Information* IE to indicate the affected Radio Link(s). If the re-established synchronisation concerns one or more individual CCTrCHs within a radio link the DRNS shall include in the RADIO LINK RESTORE INDICATION message the *RL Information* IE to indicate the affected CCTrCHs.] [FDD – If the re-established UL Uu synchronisation concerns one or more Radio Link Sets the DRNC shall include in the RADIO LINK RESTORE INDICATION message the *RL Set Information* IE to indicate the affected Radio Link Set(s).]
+
+[FDD – The DRNC shall send the RADIO LINK RESTORE INDICATION message when the E-DCH processing issue condition has ceased.]
+
+### 8.3.10.3 Abnormal Conditions
+
+-
+
+## 8.3.11 Dedicated Measurement Initiation
+
+### 8.3.11.1 General
+
+This procedure is used by an SRNS to request the initiation of dedicated measurements in a DRNS.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Dedicated Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.11.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ SRNC->>DRNC: DEDICATED MEASUREMENT INITIATION REQUEST
+ DRNC-->>SRNC: DEDICATED MEASUREMENT INITIATION RESPONSE
+
+```
+
+Sequence diagram showing the Successful Operation of the Dedicated Measurement Initiation procedure. The diagram shows two vertical lifelines: SRNC on the left and DRNC on the right. A solid horizontal arrow points from SRNC to DRNC, labeled 'DEDICATED MEASUREMENT INITIATION REQUEST'. A dashed horizontal arrow points from DRNC back to SRNC, labeled 'DEDICATED MEASUREMENT INITIATION RESPONSE'.
+
+**Figure 20: Dedicated Measurement Initiation procedure, Successful Operation**
+
+The procedure is initiated with a DEDICATED MEASUREMENT INITIATION REQUEST message sent from the SRNC to the DRNC.
+
+Upon receipt, the DRNC shall initiate the requested dedicated measurement according to the parameters given in the DEDICATED MEASUREMENT INITIATION REQUEST message.
+
+If the Dedicated Measurement Object Type is indicated as being “RL” in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all the indicated Radio Links.
+
+[FDD – If the Dedicated Measurement Object Type is indicated as being “RLS” in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all the indicated Radio Link Sets.]
+
+[FDD – If the Dedicated Measurement Object Type is indicated as being “ALL RL” in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all current and future Radio Links within the UE Context.]
+
+[TDD – If the Dedicated Measurement Object Type is indicated as being “ALL RL” in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for one existing DPCH per CCTrCH in each used time slot of current and future Radio Links within the UE Context, provided the measurement type is applicable to the respective DPCH.]
+
+[FDD – If the Dedicated Measurement Object Type is indicated as being “ALL RLS” in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all the existing and future Radio Link Sets within the UE Context.]
+
+[TDD – If the *DPCH ID* IE or *DPCH ID 7.68Mcps* IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually. If no *DPCH ID* IE, *DPCH ID 7.68Mcps* IE or *HS-SICH ID* IE is provided within the RL Information the measurement request shall apply for one existing DPCH per CCTrCH in each used time slot of the Radio Link, provided the measurement type is applicable to this DPCH.]
+
+[TDD – If the *HS-SICH Information* IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually.]
+
+[TDD – If the *Dedicated Measurement Type* IE is set to “HS-SICH reception quality”, the DRNS shall initiate measurements of the failed, missed and total HS-SICH transmissions on all of the HS-SICH assigned to this UE Context. If either the failed or missed HS-SICH transmission satisfies the requested report characteristics, the DRNS shall report the result of both failed and missed transmission measurements along with the total number of transmissions.]
+
+#### Report characteristics
+
+The *Report Characteristics* IE indicates how the reporting of the dedicated measurement shall be performed. See also Annex B.
+
+If the *Report Characteristics* IE is set to “On Demand” and if the *CFN* IE is not provided, the DRNS shall report the measurement result immediately in the DEDICATED MEASUREMENT INITIATION RESPONSE message. If the
+
+*CFN* IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]).
+
+If the *Report Characteristics* IE is set to “Periodic” and if the *CFN* IE is not provided, the DRNS shall immediately and periodically initiate the Dedicated Measurement Reporting procedure for this measurement, with a frequency as specified by the *Report Periodicity* IE. If the *CFN* IE is provided, the DRNS shall initiate a Dedicated Measurement Reporting procedure for this measurement at the *CFN* indicated in the *CFN* IE, and shall repeat this initiation periodically thereafter with a frequency as specified by the *Report Periodicity* IE. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]).
+
+If the *Report Characteristics* IE is set to “Event A”, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the requested threshold, as specified by the *Measurement Threshold* IE, and then stays above the threshold for the requested hysteresis time, as specified by the *Measurement Hysteresis Time* IE. If the *Measurement Hysteresis Time* IE is not included, the DRNC shall use the value zero for the hysteresis time.
+
+If the *Report Characteristics* IE is set to “Event B”, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the requested threshold, as specified by the *Measurement Threshold* IE, and then stays below the threshold for the requested hysteresis time, as specified by the *Measurement Hysteresis Time* IE. If the *Measurement Hysteresis Time* IE is not included, the DRNC shall use the value zero for the hysteresis time.
+
+If the *Report Characteristics* IE is set to “Event C”, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises more than the requested threshold specified by the *Measurement Increase/Decrease Threshold* IE, and only when this rise occurs within the requested rising time specified by the *Measurement Change Time* IE. After reporting this type of event, DRNS shall not initiate the next C event reporting for the same measurement during the subsequent time specified by the *Measurement Change Time* IE.
+
+If the *Report Characteristics* IE is set to “Event D”, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls more than the requested threshold specified by the *Measurement Increase/Decrease Threshold* IE, and only when this falls occurs within the requested falling time specified by the *Measurement Change Time* IE. After reporting this type of event, the DRNS shall not initiate the next D event reporting for the same measurement during the subsequent time specified by the *Measurement Change Time* IE.
+
+If the *Report Characteristics* IE is set to “Event E”, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the *Measurement Threshold 1* IE and stays above the threshold for the *Measurement Hysteresis Time* IE (Report A). When the conditions for Report A are met and if the *Report Periodicity* IE is provided, the DRNS shall initiate the Dedicated Measurement Reporting procedure periodically with the requested report frequency specified by the *Report Periodicity* IE. If the conditions for Report A have been met and the measured entity falls below the *Measurement Threshold 2* IE and stays below the threshold for the *Measurement Hysteresis Time* IE, the DRNS shall initiate the Dedicated Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the *Measurement Threshold 2* IE is not present, the DRNS shall use the value of the *Measurement Threshold 1* IE instead. If the *Measurement Hysteresis Time* IE is not included, the DRNC shall use the value zero as hysteresis times for both Report A and Report B.
+
+If the *Report Characteristics* IE is set to “Event F”, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the *Measurement Threshold 1* IE and stays below the threshold for the *Measurement Hysteresis Time* IE (Report A). When the conditions for Report A are met and if the *Report Periodicity* IE is provided, the DRNS shall initiate the Dedicated Measurement Reporting procedure periodically with the requested report frequency specified by the *Report Periodicity* IE. If the conditions for Report A have been met and the measured entity rises above the *Measurement Threshold 2* IE and stays above the threshold for the *Measurement Hysteresis Time* IE, the DRNS shall initiate the Dedicated Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the *Measurement Threshold 2* IE is not present, the DRNS shall use the value of the *Measurement Threshold 1* IE instead. If the *Measurement Hysteresis Time* IE is not included, the DRNC shall use the value zero as hysteresis times for both Report A and Report B.
+
+If the *Report Characteristics* IE is not set to “On –Demand”, the DRNS is required to perform reporting for a dedicated measurement object, in accordance with the conditions provided in the DEDICATED MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no dedicated measurement object(s) for which a measurement is defined exists any more, the DRNS shall terminate the measurement locally without reporting this to the SRNC.
+
+If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the DRNS shall initiate the Dedicated Measurement Reporting procedure immediately, and then continue with the measurements as specified in the DEDICATED MEASUREMENT INITIATION REQUEST message.
+
+### Higher layer filtering
+
+The *Measurement Filter Coefficient* IE indicates how filtering of the dedicated measurement values shall be performed before measurement event evaluation and reporting.
+
+The averaging shall be performed according to the following formula.
+
+The variables in the formula are defined as follows:
+
+$F_n$ is the updated filtered measurement result.
+
+$F_{n-1}$ is the old filtered measurement result.
+
+$M_n$ is the latest received measurement result from physical layer measurements, the unit used for $M_n$ is the same unit as the reported unit in the DEDICATED MEASUREMENT INITIATION RESPONSE, DEDICATED MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for $F_n$ ).
+
+$A = 1/2^{(k/2)}$ , where $k$ is the parameter received in the *Measurement Filter Coefficient* IE. If the *Measurement Filter Coefficient* IE is not present, $a$ shall be set to 1 (no filtering)
+
+In order to initialise the averaging filter, $F_0$ is set to $M_1$ when the first measurement result from the physical layer measurement is received.
+
+### Measurement Recovery Behavior:
+
+If the *Measurement Recovery Behavior* IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the DRNS shall, if Measurement Recovery Behavior is supported, include the *Measurement Recovery Support Indicator* IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.3.12.2.
+
+### Response message
+
+If the DRNS was able to initiate the measurement requested by the SRNS it shall respond with the DEDICATED MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the DEDICATED MEASUREMENT INITIATION REQUEST message.
+
+In the case in which the *Report Characteristics* IE is set to “On Demand”:
+
+- The DRNC shall include the measurement result in the *Dedicated Measurement Value* IE within the DEDICATED MEASUREMENT INITIATION RESPONSE message.
+- If the *CFN Reporting Indicator* IE is set to “FN Reporting Required”, the *CFN* IE shall be included in the DEDICATED MEASUREMENT INITIATION RESPONSE message. The reported CFN shall be the CFN at the time when the dedicated measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]).
+- [TDD – If the measurement was made on a particular DPCH, the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the DPCH ID of that DPCH in the [1.28Mcps TDD and 3.84Mcps TDD – *DPCH ID* IE] [7.68Mcps TDD – *DPCH ID 7.68Mcps* IE].]
+- [TDD – If the measurement was made on a particular HS-SICH, the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the ID of that HS-SICH in the *HS-SICH ID* IE.]
+
+[FDD – If the *Alternative Format Reporting Indicator* IE is set to “Alternative format is allowed” in the DEDICATED MEASUREMENT INITIATION REQUEST message, the DRNC may include the *Extended Round Trip Time* IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message.]
+
+### 8.3.11.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: DEDICATED MEASUREMENT INITIATION REQUEST
+ SRNC->>DRNC: DEDICATED MEASUREMENT INITIATION REQUEST
+ Note right of DRNC: DEDICATED MEASUREMENT INITIATION FAILURE
+ DRNC-->>SRNC: DEDICATED MEASUREMENT INITIATION FAILURE
+```
+
+Sequence diagram showing the Unsuccessful Operation of the Dedicated Measurement Initiation procedure. The diagram shows two vertical lifelines for SRNC and DRNC. A horizontal arrow labeled 'DEDICATED MEASUREMENT INITIATION REQUEST' points from SRNC to DRNC. A return horizontal arrow labeled 'DEDICATED MEASUREMENT INITIATION FAILURE' points from DRNC back to SRNC.
+
+**Figure 21: Dedicated Measurement Initiation procedure, Unsuccessful Operation**
+
+If the requested measurement cannot be initiated for one of the RL/RLS, the DRNC shall send a DEDICATED MEASUREMENT INITIATION FAILURE message. The message shall include the same *Measurement ID* IE that was used in the DEDICATED MEASUREMENT INITIATION REQUEST message and shall include the *Cause* IE set to an appropriate value.
+
+If the DEDICATED MEASUREMENT INITIATION REQUEST message includes the *Partial Reporting Indicator* IE, the DRNS shall, if partial reporting is supported, separate the unsuccessful measurement initiations from the successful measurement initiations. For the successful measurement initiations on a RL or an RLS, the DRNS shall include the *Successful RL Information* IE or the *Successful RL Set Information* IE for the concerned RL or RLS if the *Report Characteristics* IE in the DEDICATED MEASUREMENT INITIATION REQUEST message was set to “On Demand”. For the unsuccessful measurement initiations, the DRNS shall include the *Individual Cause* IE set to an appropriate value if it differs from the value of the *Cause* IE.
+
+Typical cause values are:
+
+#### **Radio Network Layer Causes:**
+
+Measurement not Supported For The Object;
+Measurement Temporarily not Available.
+
+#### **Miscellaneous Causes:**
+
+Control Processing Overload;
+HW Failure.
+
+### 8.3.11.4 Abnormal Conditions
+
+The allowed combinations of the Dedicated Measurement Type and Report Characteristics Type are shown in the table below marked with “X”. For not allowed combinations, the DRNS shall reject the Dedicated Measurement Initiation procedure using the DEDICATED MEASUREMENT INITIATION FAILURE message.
+
+**Table 4: Allowed Dedicated Measurement Type and Report Characteristics Type combinations**
+
+| Dedicated Measurement Type | Report Characteristics Type | | | | | | | | |
+|---------------------------------------|-----------------------------|----------|---------|---------|---------|---------|---------|---------|-----------------|
+| | On Demand | Periodic | Event A | Event B | Event C | Event D | Event E | Event F | On Modification |
+| SIR | X | X | X | X | X | X | X | X | |
+| SIR Error | X | X | X | X | X | X | X | X | |
+| Transmitted Code Power | X | X | X | X | X | X | X | X | |
+| RSCP | X | X | X | X | X | X | X | X | |
+| Rx Timing Deviation | X | X | X | X | | | X | X | |
+| Round Trip Time | X | X | X | X | X | X | X | X | |
+| Rx Timing Deviation LCR | X | X | X | X | | | X | X | |
+| HS-SICH Reception Quality | X | X | X | X | | | X | X | |
+| Angle Of Arrival LCR | X | X | | | | | | | |
+| Rx Timing Deviation 7.68Mcps | X | X | X | X | | | X | X | |
+| Rx Timing Deviation 3.84Mcps Extended | X | X | X | X | | | X | X | |
+| UE transmission power headroom | X | X | | X | | | | X | |
+
+If the Dedicated Measurement Type received in the *Dedicated Measurement Type* IE is not defined in TS 25.215 [11] or TS 25.225 [14] to be measured on the Dedicated Measurement Object Type received in the DEDICATED MEASUREMENT INITIATION REQUEST message, the DRNS shall reject the Dedicated Measurement Initiation procedure.
+
+If the *CFN* IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message and the *Report Characteristics* IE is other than “Periodic” or “On Demand”, the DRNS shall reject the Dedicated Measurement Initiation procedure, and the DRNC shall send a DEDICATED MEASUREMENT INITIATION FAILURE message.
+
+## 8.3.12 Dedicated Measurement Reporting
+
+### 8.3.12.1 General
+
+This procedure is used by the DRNS to report the results of the successfully initiated measurements requested by the SRNS with the Dedicated Measurement Initiation procedure.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The DRNC may initiate the Dedicated Measurement Reporting procedure at any time after establishing a Radio Link.
+
+### 8.3.12.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of DRNC: DEDICATED MEASUREMENT REPORT
+ DRNC->>SRNC: DEDICATED MEASUREMENT REPORT
+
+```
+
+Sequence diagram showing the Dedicated Measurement Reporting procedure. A vertical line on the left is labeled SRNC and a vertical line on the right is labeled DRNC. A horizontal arrow points from the DRNC line to the SRNC line, labeled 'DEDICATED MEASUREMENT REPORT'.
+
+**Figure 22: Dedicated Measurement Reporting procedure, Successful Operation**
+
+If the requested measurement reporting criteria are met, the DRNS shall initiate the Dedicated Measurement Reporting procedure. If the measurement was initiated (by the Dedicated Measurement Initiation procedure) for multiple dedicated measurement objects, the DRNC may include dedicated measurement values in the *Dedicated Measurement Value Information* IE for multiple objects in the DEDICATED MEASUREMENT REPORT message.
+
+The *Measurement ID* IE shall be set to the Measurement ID provided by the SRNC when initiating the measurement with the Dedicated Measurement Initiation procedure.
+
+If the achieved measurement accuracy does not fulfil the given accuracy requirement specified in TS 25.133 [23] and TS 25.123 [24] or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Measurement not available shall be reported in the *Dedicated Measurement Value Information* IE in the DEDICATED MEASUREMENT REPORT message, otherwise the DRNC shall include the *Dedicated Measurement Value* IE within the *Dedicated Measurement Value Information* IE. If the DRNC was configured to perform the Measurement Recovery Behavior, the DRNC shall indicate Measurement Available to the SRNC when the achieved measurement accuracy again fulfils the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) and include the *Measurement Recovery Report Indicator* IE in the DEDICATED MEASUREMENT REPORT message if the requested measurement reporting criteria are not met.
+
+If the CFN Reporting Indicator when initiating the measurement with the Dedicated Measurement Initiation procedure was set to “FN Reporting Required”, the DRNC shall include the *CFN* IE in the DEDICATED MEASUREMENT REPORT message. The reported CFN shall be the CFN at the time when the dedicated measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]).
+
+[TDD – If the measurement was made on a particular DPCH, the DEDICATED MEASUREMENT REPORT message shall include the DPCH ID of that DPCH in the [1.28Mcps TDD and 3.84Mcps TDD – *DPCH ID* IE] [7.68Mcps TDD – *DPCH ID 7.68Mcps* IE].]
+
+[TDD – If the measurement was made on a particular HS-SICH, the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the ID of that HS-SICH in the *HS-SICH ID* IE.]
+
+[FDD – If the *Alternative Format Reporting Indicator* IE was set to “Alternative format is allowed” in the DEDICATED MEASUREMENT INITIATION REQUEST message setting up the measurement to be reported, the DRNC may include the *Extended Round Trip Time* IE in the DEDICATED MEASUREMENT REPORT message.]
+
+### 8.3.12.3 Abnormal Conditions
+
+-
+
+## 8.3.13 Dedicated Measurement Termination
+
+### 8.3.13.1 General
+
+This procedure is used by the SRNS to terminate a measurement previously requested by the Dedicated Measurement Initiation procedure.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Dedicated Measurement Termination procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.13.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note over SRNC, DRNC: DEDICATED MEASUREMENT TERMINATION REQUEST
+ SRNC->>DRNC: DEDICATED MEASUREMENT TERMINATION REQUEST
+
+```
+
+Sequence diagram showing the Dedicated Measurement Termination procedure. The SRNC sends a DEDICATED MEASUREMENT TERMINATION REQUEST message to the DRNC.
+
+**Figure 23: Dedicated Measurement Termination procedure, Successful Operation**
+
+This procedure is initiated with a DEDICATED MEASUREMENT TERMINATION REQUEST message, sent from the SRNC to the DRNC.
+
+Upon receipt, the DRNS shall terminate reporting of dedicated measurements corresponding to the received *Measurement ID* IE.
+
+### 8.3.13.3 Abnormal Conditions
+
+-
+
+## 8.3.14 Dedicated Measurement Failure
+
+### 8.3.14.1 General
+
+This procedure is used by the DRNS to notify the SRNS that a measurement previously requested by the Dedicated Measurement Initiation procedure can no longer be reported. When partial reporting is allowed and supported, this procedure shall be used to report that measurement for one or more RL/RLS can no longer be reported.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The DRNC may initiate the Dedicated Measurement Failure procedure at any time after establishing a Radio Link.
+
+### 8.3.14.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: DEDICATED MEASUREMENT FAILURE INDICATION
+ DRNC->>SRNC: DEDICATED MEASUREMENT FAILURE INDICATION
+
+```
+
+Sequence diagram showing the Dedicated Measurement Failure procedure. It features two vertical lifelines labeled SRNC and DRNC. A horizontal arrow points from the DRNC lifeline to the SRNC lifeline, with the text 'DEDICATED MEASUREMENT FAILURE INDICATION' centered above the arrow.
+
+**Figure 24: Dedicated Measurement Failure procedure, Successful Operation**
+
+This procedure is initiated with a DEDICATED MEASUREMENT FAILURE INDICATION message, sent from the DRNC to the SRNC, to inform the SRNC that a previously requested dedicated measurement can no longer be reported. The DRNC has locally terminated the indicated measurement. The DRNC shall include in the DEDICATED MEASUREMENT FAILURE INDICATION message the reason for the failure in the *Cause* IE.
+
+The DRNS shall include *Unsuccessful RL Information* IE or the *Unsuccessful RL Set Information* IE for the concerned RL or RLS if partial reporting is allowed and it is supported. The DRNS shall include the *Individual Cause* IE set to an appropriate value if it differs from the value of the *Cause* IE.
+
+Typical cause values are:
+
+#### Miscellaneous Causes:
+
+- Control Processing Overload;
+- HW Failure;
+- O&M Intervention.
+
+### 8.3.14.3 Abnormal Conditions
+
+-
+
+## 8.3.15 Downlink Power Control [FDD]
+
+### 8.3.15.1 General
+
+The purpose of this procedure is to balance the DL transmission powers of one or more radio links for one UE.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Downlink Power Control procedure may be initiated by the SRNC at any time after establishing a Radio Link. If the SRNC has initiated in this DRNS the deletion of the last Radio Link for this UE context, the Downlink Power Control procedure shall not be initiated.
+
+### 8.3.15.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: DL POWER CONTROL REQUEST
+ SRNC->>DRNC: DL POWER CONTROL REQUEST
+
+```
+
+Sequence diagram showing the Downlink Power Control procedure. A vertical line on the left is labeled SRNC and a vertical line on the right is labeled DRNC. A horizontal arrow points from the SRNC line to the DRNC line, with the text 'DL POWER CONTROL REQUEST' centered above the arrow.
+
+**Figure 25: Downlink Power Control procedure, Successful Operation**
+
+The Downlink Power Control procedure is initiated by the SRNC sending a DL POWER CONTROL REQUEST message to the DRNC.
+
+The *Power Adjustment Type* IE defines the characteristic of the power adjustment.
+
+If the value of the *Power Adjustment Type* IE is “Common”, the DRNS shall set the Power Balancing Adjustment Type of the UE Context set to “Common”. As long as the Power Balancing Adjustment Type of the UE Context is set to “Common”, the DRNS shall perform the power adjustment (see below) for all existing and future radio links for the UE Context and use a common DL reference power level.
+
+If the value of the *Power Adjustment Type* IE is “Individual”, the DRNS shall set the Power Balancing Adjustment Type of the UE Context set to “Individual”. The DRNS shall perform the power adjustment (see below) for all radio links addressed in the message using the given DL Reference Power per RL. If the Power Balancing Adjustment Type of the UE Context was set to “Common” before this message was received, power balancing on all radio links not addressed by the DL POWER CONTROL REQUEST message shall remain to be executed in accordance with the existing power balancing parameters which are now considered RL individual parameters. Power balancing will not be started on future radio links without a specific request.
+
+If the value of the *Power Adjustment Type* IE is “None”, the DRNS shall set the Power Balancing Adjustment Type of the UE Context set to “None” and the DRNS shall suspend on going power adjustments for all radio links for the UE Context.
+
+If the *Inner Loop DL PC Status* IE is present and set to “Active”, the DRNS shall activate inner loop DL power control for all radio links for the UE Context. If the *Inner Loop DL PC Status* IE is present and set to “Inactive”, the DRNS shall deactivate inner loop DL power control for all radio links for the UE Context according to TS 25.214 [10].
+
+#### Power Adjustment
+
+The power balancing adjustment shall be superimposed on the inner loop power control adjustment (see TS 25.214 [10]) if activated. The power balancing adjustment shall be such that:
+
+with an accuracy of $\pm 0.5$ dB
+
+where the sum is performed over an adjustment period corresponding to a number of frames equal to the value of the *Adjustment Period* IE, $P_{ref}$ is the value of the *DL Reference Power* IE, $P_{P-CPICH}$ is the power used on the primary CPICH, $P_{init}$ is the code power of the last slot of the previous adjustment period and $r$ is given by the *Adjustment Ratio* IE. If the last slot of the previous adjustment period is within a transmission gap due to compressed mode, $P_{init}$ shall be set to the same value as the code power of the slot just before the transmission gap.
+
+The adjustment within one adjustment period shall in any case be performed with the constraints given by the *Max Adjustment Step* IE and the DL TX power range set by the DRNC.
+
+The power adjustments shall be started at the first slot of a frame with CFN modulo the value of *Adjustment Period* IE equal to 0 and shall be repeated for every adjustment period and shall be restarted at the first slot of a frame with CFN=0, until a new DL POWER CONTROL REQUEST message is received or the RL is deleted.
+
+### 8.3.15.3 Abnormal Conditions
+
+-
+
+## 8.3.16 Compressed Mode Command [FDD]
+
+### 8.3.16.1 General
+
+The Compressed Mode Command procedure is used to activate or deactivate the compressed mode in the DRNS for one UE-UTRAN connection. This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Compressed Mode Command procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.16.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ SRNC->>DRNC: COMPRESSED MODE COMMAND
+
+```
+
+Sequence diagram showing the successful operation of the Compressed Mode Command procedure. A vertical line on the left represents the SRNC, and a vertical line on the right represents the DRNC. A horizontal arrow labeled 'COMPRESSED MODE COMMAND' points from the SRNC to the DRNC.
+
+**Figure 26: Compressed Mode Command procedure, Successful Operation**
+
+The procedure is initiated by the SRNC sending a COMPRESSED MODE COMMAND message to the DRNC.
+
+Upon receipt of the COMPRESSED MODE COMMAND message from the SRNC and at the CFN indicated in the *CM Configuration Change CFN* IE, the DRNS shall deactivate all the ongoing Transmission Gap Pattern Sequences. From that moment on all Transmission Gap Pattern Sequences included in *Transmission Gap Pattern Sequence Status* IE repetitions (if present) shall be started when the indicated *TGCFN* IE elapses. The *CM Configuration Change CFN* IE in the *Active Pattern Sequence Information* IE and *TGCFN* IE for each sequence refer to the next coming CFN with that value.
+
+If the values of the *CM Configuration Change CFN* IE and the *TGCFN* IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the *CM Configuration Change CFN* IE.
+
+If the *Affected HS-DSCH serving cell List* IE is included, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.
+
+If the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the downlink compressed mode method information, if existing, for the concerned Transmission Gap Pattern Sequence(s) in the Compressed Mode Configuration.
+
+### 8.3.16.3 Abnormal Conditions
+
+[FDD - If the *Affected HS-DSCH serving cell List* IE is included in the *Active Pattern Sequence Information* IE, and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall initiate the Radio Link Failure procedure with the cause value "Invalid CM Settings".]
+
+## 8.3.17 Downlink Power Timeslot Control [TDD]
+
+### 8.3.17.1 General
+
+The purpose of this procedure is to provide the DRNS with updated DL Timeslot ISCP values to use when deciding the DL TX Power for each timeslot.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Downlink Power Timeslot Control procedure can be initiated by the SRNC at any time after establishing a Radio Link. If the SRNC has initiated deletion of the last Radio Link in this DRNS, the Downlink Power Timeslot Control procedure shall not be initiated.
+
+### 8.3.17.2 Successful Operation
+
+
+
+Sequence diagram for Downlink Power Timeslot Control procedure, Successful Operation. It shows two vertical lifelines: SRNC on the left and DRNC on the right. A horizontal arrow labeled 'DL POWER TIMESLOT CONTROL REQUEST' points from the SRNC lifeline to the DRNC lifeline.
+
+**Figure 26A: Downlink Power Timeslot Control procedure, Successful Operation**
+
+The Downlink Power Timeslot Control procedure is initiated by the SRNC sending a DL POWER TIMESLOT CONTROL REQUEST message to the DRNC.
+
+Upon receipt of the DL POWER TIMESLOT CONTROL REQUEST message, the DRNS shall use the included [3.84Mcps TDD – *DL Timeslot ISCP Info IE*] [1.28Mcps TDD – *DL Timeslot ISCP Info LCR IE*] value when deciding the DL TX Power for each timeslot as specified in TS 25.224 [22], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link in which the interference is low, and increase the DL TX power in those timeslots in which the interference is high, while keeping the total downlink power in the radio link unchanged.
+
+If the *Primary CCPCH RSCP Delta IE* is included, the DRNS shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP Delta IE*. If the *Primary CCPCH RSCP Delta IE* is not included and the *Primary CCPCH RSCP IE* is included, the DRNS shall assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP IE*. The DRNS should use the indicated value for HS-DSCH scheduling and transmit power adjustment.
+
+### 8.3.17.3 Abnormal Conditions
+
+-
+
+## 8.3.18 Radio Link Pre-emption
+
+### 8.3.18.1 General
+
+This procedure is started by the DRNS when resources need to be freed.
+
+This procedure shall use the signalling bearer connection for the UE Context associated with the RL to be pre-empted.
+
+The DRNS may initiate the Radio Link Pre-emption procedure at any time after establishing a Radio Link.
+
+### 8.3.18.2 Successful Operation
+
+
+
+Sequence diagram for Radio Link Pre-emption procedure, Successful Operation. It shows two vertical lifelines: SRNC on the left and DRNC on the right. A horizontal arrow labeled 'RADIO LINK PREEMPTION REQUIRED INDICATION' points from the DRNC lifeline to the SRNC lifeline. On the DRNC lifeline, there is a rectangular box labeled 'RL to be pre-empted'.
+
+**Figure 26B: Radio Link Pre-emption procedure, Successful Operation**
+
+When DRNC detects that one or more Radio Link(s) should be pre-empted (see Annex A), it shall send the RADIO LINK PREEMPTION REQUIRED INDICATION message to the SRNC. If all Radio Links for a UE Context should be pre-empted, the *RL Information IE* shall not be included in the message. If one or several but not all Radio Link(s) should be pre-empted for an UE Context, the Radio Link(s) that should be pre-empted shall be indicated in the *RL Information IE*. The Radio Link(s) that should be pre-empted, should be deleted by the SRNC.
+
+[FDD – If only the E-DCH traffic on a Radio Link should be pre-empted, the DRNC shall indicate the EDCH MAC-d flows that should be pre-empted by including the *E-DCH MAC-d Flow Specific Information* IE in the RADIO LINK PREEMPTION REQUIRED INDICATION message.]
+
+When only the HS-DSCH traffic on a Radio Link should be pre-empted, the DRNC shall indicate the HS-DSCH MAC-d flow(s) that should be pre-empted by including the *HS-DSCH MAC-d Flow Specific Information* IE in the RADIO LINK PREEMPTION REQUIRED INDICATION message.
+
+### 8.3.18.3 Abnormal Conditions
+
+-
+
+## 8.3.19 Radio Link Congestion
+
+### 8.3.19.1 General
+
+This procedure is started by the DRNC when resource congestion is detected and the rate of one or more DCHs, corresponding to one or more radio links, is preferred to be limited in the UL and/or DL. This procedure is also used by the DRNC to indicate to the SRNC any change of the UL/DL resource congestion situation, affecting these radio links. This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The Radio Link Congestion procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.19.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: Radio Link Congestion detected
+ DRNC->>SRNC: RADIO LINK CONGESTION INDICATION
+ Note left of SRNC: Rate reduction applied
+
+```
+
+Sequence diagram showing the successful operation of the Radio Link Congestion procedure. It features two vertical lifelines labeled SRNC and DRNC. A horizontal arrow labeled 'RADIO LINK CONGESTION INDICATION' points from the DRNC lifeline to the SRNC lifeline.
+
+**Figure 26C: Radio Link Congestion procedure, Successful Operation**
+
+#### Start of an UL/DL Resource Congestion Situation
+
+When the DRNC detects the start of a UL/DL resource congestion situation and prefers the rate of one or more DCHs for one or more Radio Link(s) to be limited below the maximum rate currently configured in the UL/DL TFS, it shall send the RADIO LINK CONGESTION INDICATION message to the SRNC. The DRNC shall indicate the cause of the congestion in the *Congestion Cause* IE and shall indicate all the Radio Links for which the rate of a DCH needs to be reduced. For each DCH within the RL with UL congestion, the DRNC shall indicate the desired maximum UL data rate with the *Allowed UL Rate* IE in the *Allowed Rate Information* IE. For each DCH within the RL with DL congestion, the DRNC shall indicate the desired maximum DL data rate with the *Allowed DL Rate* IE in the *Allowed Rate Information* IE.
+
+[FDD – For each E-DCH MAC-d flow within the RL with UL congestion, the DRNC shall indicate all the MAC-d flows for which the rate cannot be fulfilled.]
+
+When receiving the RADIO LINK CONGESTION INDICATION message the SRNC should reduce the rate in accordance with the *Congestion Cause* IE and the indicated *Allowed DL Rate* IE and/or *Allowed UL Rate* IE for a DCH.
+
+[FDD – If the RADIO LINK CONGESTION INDICATION message includes the *DCH Indicator For E-DCH-HSDPA Operation* IE, then the SRNC shall ignore the *DCH Rate Information* IE in the RADIO LINK CONGESTION INDICATION message.]
+
+#### Change of UL/DL Resource Congestion Situation
+
+The DRNC shall indicate any change of the UL/DL resource congestion situation by sending the RADIO LINK CONGESTION INDICATION message in which the new allowed rate(s) of the DCHs are indicated by the *Allowed Rate Information* IE. In the case that for at least one DCH the new allowed rate is lower than the previously indicated allowed rate for that DCH, the *Congestion Cause* IE, indicating the cause of the congestion, shall also be included.
+
+When receiving a RADIO LINK CONGESTION INDICATION message indicating a further rate decrease on any DCH(s) on any RL, the SRNC should reduce the rate in accordance with the indicated congestion cause and the indicated allowed rate(s) for the DCH(s).
+
+### End of UL/DL Resource Congestion Situation
+
+The end of an UL resource congestion situation, affecting a specific RL, shall be indicated by including the TF corresponding to the highest data rate in the *Allowed UL Rate* IE in the *Allowed Rate Information* IE for the concerned RL. The end of a DL resource congestion situation, affecting a specific RL, shall be indicated by including the TF with the highest data rate in the *Allowed DL Rate* IE in the *Allowed Rate Information* IE for the concerned RL.
+
+### 8.3.19.3 Abnormal Conditions
+
+-
+
+## 8.3.20 Radio Link Activation
+
+### 8.3.20.1 General
+
+This procedure is used to activate or de-activate the DL transmission on the Uu interface regarding selected RLs.
+
+### 8.3.20.2 Successful Operation
+
+
+
+```
+
+graph LR
+ SRNC[SRNC] -- "RADIO LINK ACTIVATION COMMAND" --> DRNC[DRNC]
+
+```
+
+Diagram of the Radio Link Activation procedure. It shows two vertical lines representing the SRNC (left) and DRNC (right). A horizontal arrow points from the SRNC to the DRNC, labeled 'RADIO LINK ACTIVATION COMMAND'.
+
+**Figure 26D: Radio Link Activation procedure**
+
+This procedure is initiated by sending the RADIO LINK ACTIVATION COMMAND message from the SRNC to the DRNC. This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+Upon receipt, the DRNS shall for each concerned RL:
+
+- if the *Delayed Activation Update* IE indicates “Activate”:
+ - - if the *Activation Type* IE equals “Unsynchronised”:
+ - - [FDD – start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [4].]
+ - - [TDD – start transmission on the new RL immediately as specified in TS 25.427 [4].]
+ - - if the *Activation Type* IE equals “Synchronised”:
+ - - [FDD – start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [4], however never before the CFN indicated in the *Activation CFN* IE.]
+ - - [TDD – start transmission on the new RL at the CFN indicated in the *Activation CFN* IE as specified in TS 25.427 [4].]
+ - - [FDD – the DRNS shall apply the power level indicated in the *Initial DL Tx Power* IE to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or power balancing is activated. During this period no inner loop power control shall be performed and, unless activated by the DL POWER CONTROL REQUEST message, no power balancing shall be performed. The DL power shall then vary according to the inner loop power control (see TS 25.214 [10], subclause 5.2.1.2) and downlink power balancing adjustments (see 8.3.7).]
+
+- - [TDD – the DRNS shall apply the power level indicated in the *Initial DL Tx Power* IE to the transmission on each DL DPCH and on each Time Slot of the RL when starting transmission until the UL synchronisation on the Uu interface is achieved for the RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.224 [22], subclause 4.2.3.3).]
+ - - [FDD – if the *Propagation Delay* IE and optionally the *Extended Propagation Delay* IE are included, the DRNS may use this information to speed up the detection of UL synchronisation on the Uu interface.]
+ - - [FDD – if the *First RLS Indicator* IE is included, it indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The *First RLS Indicator* IE shall be used by the DRNS to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.]
+- if the *Delayed Activation Update* IE indicates “Deactivate”:
+- - stop DL transmission immediately if the *Deactivation Type* IE equals “Unsynchronised”, or at the CFN indicated by the *Deactivation CFN* IE if the *Deactivation Type* IE equals “Synchronised”.
+
+### 8.3.20.3 Abnormal Conditions
+
+[FDD – If the *Delayed Activation Update* IE is included in the RADIO LINK ACTIVATION COMMAND message, it indicates “Activate” and the *First RLS Indicator* IE is not included, the DRNC shall initiate the ERROR INDICATION procedure.]
+
+## 8.3.21 Radio Link Parameter Update
+
+### 8.3.21.1 General
+
+The Radio Link Parameter Update procedure is executed by the DRNS to update parameters related to HS-DSCH [FDD - or E-DCH or UL CLTD] on a radio link for a UE-UTRAN connection or to update phase reference on a list of the radio links.
+
+This procedure shall use the signalling bearer connection for the relevant UE context.
+
+The Radio Link Parameter Update procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.21.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: Initiate Radio Link Parameter Update
+ DRNC->>SRNC: RADIO LINK PARAMETER UPDATE INDICATION
+
+```
+
+Sequence diagram showing the successful operation of the Radio Link Parameter Update procedure. The diagram shows two vertical lines representing the SRNC (left) and DRNC (right). A horizontal arrow labeled 'RADIO LINK PARAMETER UPDATE INDICATION' points from the DRNC to the SRNC.
+
+**Figure 26E: Radio Link Parameter Update Indication, Successful Operation**
+
+The Radio Link Parameter Update procedure is initiated by the DRNS by sending the RADIO LINK PARAMETER UPDATE INDICATION message to the SRNC.
+
+#### HS-DSCH related Parameter(s) Updating:
+
+If RADIO LINK PARAMETER UPDATE INDICATION message is used to update the parameters related to HS-DSCH, it contains suggested value(s) of the HS-DSCH related parameter(s) that should be reconfigured on the radio link.
+
+If the DRNS needs to update HS-DSCH related parameters, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including [FDD – *HS-DSCH FDD Update Information* IE] [TDD – *HS-DSCH TDD Update Information* IE].
+
+If the DRNS needs to allocate new HS-SCCH Codes, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *HS-SCCH Code Change Indicator* IE.
+
+[FDD – If the DRNS needs to allocate new HS-PDSCH Codes, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *HS-PDSCH Code Change Indicator* IE.]
+
+[FDD – If the DRNS needs to update the CQI Feedback Cycle *k*, CQI Repetition Factor, ACK-NACK Repetition Factor, CQI Power Offset, ACK Power Offset and/or NACK Power Offset, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *CQI Feedback Cycle k* IE, *CQI Repetition Factor* IE, *ACK-NACK Repetition Factor* IE, *CQI Power Offset* IE, *ACK Power Offset* IE and/or *NACK Power Offset* IE.]
+
+[TDD – If the DRNS needs to update the TDD ACK-NACK Power Offset the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *TDD ACK-NACK Power Offset* IE.]
+
+[FDD – If the DRNS needs to update the Precoder weight set restriction , the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Precoder weight set restriction* IE.]
+
+#### **[FDD – Secondary Serving HS-DSCH related Parameter(s) Updating:]**
+
+[FDD – If RADIO LINK PARAMETER UPDATE INDICATION message is used to update the parameters related to secondary serving HS-DSCH, it contains suggested value(s) of the secondary serving HS-DSCH related parameter(s) that should be reconfigured on the radio link.]
+
+[FDD – If the DRNS needs to update secondary serving HS-DSCH related parameters, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message and include the *Additional HS Cell Information RL Param Upd* IE.]
+
+- [FDD – If the DRNS needs to allocate new secondary serving HS-SCCH Codes, the DRNS shall include the *HS-SCCH Code Change Indicator* IE in the *HS-DSCH FDD Secondary Serving Update Information* IE.]
+- [FDD – If the DRNS needs to update the Precoder weight set restriction , the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Update Information* IE.]
+
+#### **[FDD – Phase Reference Handling:]**
+
+[FDD – If DRNS needs to update phase reference for the channel estimation for one or several Radio Links, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Phase Reference Update Information* IE for the concerned RL(s).]
+
+#### **[FDD – E-DCH:]**
+
+[FDD – If DRNS needs to update E-DCH related parameters, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *E-DCH FDD Update Information* IE.]
+
+[FDD – If the DRNS needs to update the HARQ process allocation for non-scheduled transmission and/or HARQ process allocation for scheduled Transmission, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE for the concerned MAC-d Flows and/or *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE.]
+
+[FDD – If the DRNS needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *E-DCH DL Control Channel Change Information* IE.]
+
+[FDD – If the DRNS needs to update Additional E-DCH related parameters, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Additional E-DCH Cell Information RL Param Upd* IE.]
+
+- [FDD – If the DRNS needs to update the HARQ process allocation for scheduled Transmission, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* .]
+- [FDD – If the DRNS needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Additional E-DCH DL Control Channel Change Information* IE.]
+
+#### **[FDD – UL CLTD:]**
+
+[FDD - If the DRNS needs to update the local activation state of UL CLTD of the UE in UL CLTD operation, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION including the *UL CLTD State Update Information* IE.]
+
+**[FDD – CPC Recovery:]**
+
+[FDD – If the DRNS needs to indicate that the CPC Recovery has been initiated, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *CPC Recovery Report* IE.]
+
+### 8.3.21.3 Abnormal Conditions
+
+-
+
+## 8.3.22 UE Measurement Initiation [TDD]
+
+### 8.3.22.1 General
+
+This procedure is used by a DRNC to request the initiation of UE measurements by the SRNC.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The UE Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.22.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of DRNC: UE MEASUREMENT INITIATION REQUEST
+ DRNC->>SRNC: UE MEASUREMENT INITIATION REQUEST
+ Note left of SRNC: UE MEASUREMENT INITIATION RESPONSE
+ SRNC->>DRNC: UE MEASUREMENT INITIATION RESPONSE
+
+```
+
+Sequence diagram showing the UE Measurement Initiation procedure. The SRNC sends a UE MEASUREMENT INITIATION REQUEST to the DRNC, and the DRNC responds with a UE MEASUREMENT INITIATION RESPONSE.
+
+**Figure 26F: UE Measurement Initiation procedure, Successful Operation**
+
+The procedure is initiated with a UE MEASUREMENT INITIATION REQUEST message sent from the DRNC to the SRNC.
+
+Upon receipt the SRNC shall, provided that it determines that the measurement can be performed by the UE, initiate and forward the requested UE measurement according to the parameters given in the UE MEASUREMENT INITIATION REQUEST message. If the UE MEASUREMENT INITIATION REQUEST message includes the *UE Measurement Parameter Modification Allowed* IE with a value of “Parameter Modification Allowed” the *UE Measurement Report Characteristics* IE and the *Measurement Filter Coefficient* IE, if it is included, are suggested values, otherwise the values of these parameters must be fulfilled.
+
+[3.84 Mcps TDD – If the *UE Measurement Timeslot Information HCR* IE is provided, the measurement request shall apply for the requested timeslot(s) individually. If the *UE Measurement Timeslot Information HCR* IE are not provided the SRNC may choose the timeslots for measurements that apply to individual timeslots.]
+
+[1.28 Mcps TDD – If the *UE Measurement Timeslot Information LCR* IE is provided, the measurement request shall apply for the requested timeslot(s) individually. If the *UE Measurement Timeslot Information LCR* IE are not provided the SRNC may choose the timeslots for measurements that apply to individual timeslots.]
+
+[7.68 Mcps TDD – If the *UE Measurement Timeslot Information 7.68 Mcps* IE is provided, the measurement request shall apply for the requested timeslot(s) individually. If the *UE Measurement Timeslot Information 7.68 Mcps* IE are not provided the SRNC may choose the timeslots for measurements that apply to individual timeslots.]
+
+If the UE MEASUREMENT INITIATION REQUEST message includes the *Allowed Queuing Time* IE the SRNC may queue the request for a time period not to exceed the value of the *Allowed Queuing Time* IE before starting to execute the request.
+
+The SRNC is required to perform reporting for a UE measurement object, in accordance with the conditions provided in the UE MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no UE measurement object(s) for which a measurement is defined exists any more, the SRNC shall terminate the measurement locally without reporting this to the DRNC.
+
+If at the start of the measurement, the reporting criteria are fulfilled for any of Event 1h, Event 1i, Event 6a, Event 6b, Event 6c, or Event 6d, the SRNC shall initiate the UE Measurement Reporting procedure immediately, and then continue with the measurements as specified in the UE MEASUREMENT INITIATION REQUEST message.
+
+At the start of a periodic measurement, the SRNC shall not initiate UE Measurement Reporting procedure until the next measurement is received from the UE, even if measurement data is available.
+
+### Report characteristics
+
+The *UE Measurement Report Characteristics* IE indicates how the reporting of the dedicated measurement shall be performed. See TS 25.331 [16].
+
+### Higher layer filtering
+
+The *Measurement Filter Coefficient* IE indicates how filtering of the dedicated measurement values shall be performed before measurement event evaluation and reporting. If the *Measurement Filter Coefficient* IE is not present, *a* shall be set to 1 (no filtering). The use of the *Measurement Filter Coefficient* IE is shown in TS 25.331 [16].
+
+### Response message
+
+If the SRNC was able to initiate the measurement requested by the DRNC it shall respond with the UE MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the UE MEASUREMENT INITIATION REQUEST message.
+
+If the DRNC allowed parameter modification and the SRNC modified the *Measurement Filter Coefficient* IE the SRNC shall include the modified value in the UE MEASUREMENT INITIATION RESPONSE message.
+
+If the DRNC allowed parameter modification and the SRNC modified the *UE Measurement Report Characteristics* IE the SRNC shall include the modified value in the UE MEASUREMENT INITIATION RESPONSE message.
+
+## 8.3.22.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of SRNC: UE MEASUREMENT INITIATION REQUEST
+ SRNC->>DRNC: UE MEASUREMENT INITIATION REQUEST
+ Note left of DRNC: UE MEASUREMENT INITIATION FAILURE
+ DRNC-->>SRNC: UE MEASUREMENT INITIATION FAILURE
+
+```
+
+Sequence diagram showing the Unsuccessful Operation of UE Measurement Initiation. The SRNC sends a UE MEASUREMENT INITIATION REQUEST to the DRNC, and the DRNC responds with a UE MEASUREMENT INITIATION FAILURE.
+
+**Figure 26G: UE Measurement Initiation procedure, Unsuccessful Operation**
+
+If the requested measurement cannot be initiated, the SRNC shall send a UE MEASUREMENT INITIATION FAILURE message. The message shall include the same *Measurement ID* IE that was used in the UE MEASUREMENT INITIATION REQUEST message and shall include the *Cause* IE set to an appropriate value.
+
+Typical cause values are:
+
+### Radio Network Layer Causes:
+
+Measurement not Supported For The Object;
+ Measurement Temporarily not Available;
+ Measurement Repetition Rate not Compatible with Current Measurements;
+ UE not Capable to Implement Measurement.
+
+#### Miscellaneous Causes:
+
+Control Processing Overload;
+HW Failure.
+
+### 8.3.22.4 Abnormal Conditions
+
+-
+
+## 8.3.23 UE Measurement Reporting [TDD]
+
+### 8.3.23.1 General
+
+This procedure is used by the SRNC to report the results of the successfully initiated measurements requested by the DRNC with the UE Measurement Initiation procedure.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The SRNC may initiate the UE Measurement Reporting procedure at any time after establishing a Radio Link.
+
+### 8.3.23.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: UE Measurement Reporting procedure
+ SRNC->>DRNC: UE MEASUREMENT REPORT
+
+```
+
+Sequence diagram showing the UE Measurement Reporting procedure. The SRNC sends a UE MEASUREMENT REPORT message to the DRNC.
+
+**Figure 26H: UE Measurement Reporting procedure, Successful Operation**
+
+If the requested measurement reporting criteria was met in the UE and reported to the SRNC, the SRNC shall initiate the UE Measurement Reporting procedure. The *Measurement ID* IE shall be set to the Measurement ID provided by the DRNC when initiating the measurement with the UE Measurement Initiation procedure.
+
+If Primary CCPCH RSCP is being reported:
+
+- If the *Primary CCPCH RSCP Delta* IE is included, the DRNC shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP Delta* IE.
+- If the *Primary CCPCH RSCP Delta* IE is not included the DRNC shall assume that the reported value is in the non negative range as per TS 25.123 [24], and the value is equal to the *Primary CCPCH RSCP* IE.
+
+If the achieved measurement accuracy does not fulfil the given accuracy requirement specified in TS 25.123 [24], the Measurement not available shall be reported in the *UE Measurement Value Information* IE in the UE MEASUREMENT REPORT message, otherwise the SRNC shall include the *UE Measurement Value* IE within the *UE Measurement Value Information* IE.
+
+### 8.3.23.3 Abnormal Conditions
+
+-
+
+## 8.3.24 UE Measurement Termination [TDD]
+
+### 8.3.24.1 General
+
+This procedure is used by the DRNC to terminate a measurement previously requested by the UE Measurement Initiation procedure.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The UE Measurement Termination procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+### 8.3.24.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant DRNC
+ participant SRNC
+ Note right of DRNC: UE MEASUREMENT TERMINATION REQUEST
+ DRNC->>SRNC: UE MEASUREMENT TERMINATION REQUEST
+```
+
+Sequence diagram for UE Measurement Termination procedure, Successful Operation. It shows two vertical lifelines labeled SRNC and DRNC. A horizontal arrow points from the DRNC lifeline to the SRNC lifeline. Above the arrow, the text 'UE MEASUREMENT TERMINATION REQUEST' is displayed.
+
+**Figure 26I: UE Measurement Termination procedure, Successful Operation**
+
+This procedure is initiated with a UE MEASUREMENT TERMINATION REQUEST message, sent from the DRNC to the SRNC.
+
+Upon receipt, the SRNC shall terminate forwarding of UE measurements corresponding to the received *Measurement ID* IE.
+
+### 8.3.24.3 Abnormal Conditions
+
+-
+
+## 8.3.25 UE Measurement Failure [TDD]
+
+### 8.3.25.1 General
+
+This procedure is used by the SRNC to notify the DRNC that a measurement previously requested by the UE Measurement Initiation procedure can no longer be reported.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+The SRNC may initiate the UE Measurement Failure procedure at any time after establishing a Radio Link.
+
+### 8.3.25.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: UE MEASUREMENT FAILURE INDICATION
+ SRNC->>DRNC: UE MEASUREMENT FAILURE INDICATION
+```
+
+Sequence diagram for UE Measurement Failure procedure, Successful Operation. It shows two vertical lifelines labeled SRNC and DRNC. A horizontal arrow points from the SRNC lifeline to the DRNC lifeline. Above the arrow, the text 'UE MEASUREMENT FAILURE INDICATION' is displayed.
+
+**Figure 26J: UE Measurement Failure procedure, Successful Operation**
+
+This procedure is initiated with a UE MEASUREMENT FAILURE INDICATION message, sent from the SRNC to the DRNC, to inform the DRNC that a previously requested UE measurement can no longer be reported. The SRNC has locally terminated the forwarding of the indicated measurement. The SRNC shall include in the UE MEASUREMENT FAILURE INDICATION message the reason for the failure in the *Cause* IE.
+
+Typical cause values are:
+
+##### Miscellaneous Causes:
+
+- Control Processing Overload;
+- HW Failure;
+- O&M Intervention.
+
+#### 8.3.25.3 Abnormal Conditions
+
+-
+
+### 8.3.26 Iur Invoke Trace
+
+#### 8.3.26.1 General
+
+The purpose of the Iur Invoke Trace procedure is to inform the DRNC that it should begin a Trace Session for a given UE Context according to the Trace Parameters indicated by the SRNC. This procedure is used for Trace Parameter Propagation in the Signalling Based Activation mechanism as defined in TS 32.421 [48] and TS 32.422 [49].
+
+This procedure shall use the signalling bearer mode specified below.
+
+#### 8.3.26.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ SRNC->>DRNC: IUR INVOKE TRACE
+```
+
+Sequence diagram showing the Iur Invoke Trace procedure. A horizontal arrow labeled 'IUR INVOKE TRACE' points from SRNC to DRNC.
+
+**Figure 26K: Iur Invoke Trace procedure, Successful Operation**
+
+The Iur Invoke Trace procedure is invoked by the SRNC by sending an IUR INVOKE TRACE message to the DRNC.
+
+When the concerned UE is utilising one or more radio links in the DRNC the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the *D-RNTT* IE shall be included in the message to identify the UE Context in the DRNC.
+
+Upon receiving the IUR INVOKE TRACE message, the DRNC should begin a Trace Recording Session according to the parameters indicated in the IUR INVOKE TRACE message.
+
+If the *List Of Interfaces To Trace* IE is included in the IUR INVOKE TRACE message, the DRNC shall trace, for the concerned UE Context, the interfaces indicated by the *List Of Interfaces To Trace* IE. Otherwise, the DRNC shall trace, for the concerned UE Context, the Iur and Iub interfaces.
+
+The values of the *UE Identity* IE, *Trace Reference* IE and *Trace Recording Session Reference* IE are used to tag the Trace Record to allow simpler construction of the total record by the entity which combines Trace Records.
+
+If the DRNC does not support the requested value “Minimum” or “Medium” of the *Trace Depth* IE, the DRNC should begin a Trace Recording Session with maximum Trace Depth.
+
+The DRNC may not start a Trace Recording Session if there are insufficient resources available within the DRNC.
+
+If the *MDT Configuration* IE is included and the *MDT Activation* IE is set to “MDT and Trace” then the DRNC shall, if supported, initiate the requested trace function and MDT function (M3 Report, if indicated) as described in TS 32.422 [49].
+
+If the *MDT Configuration* IE is included and the *MDT Activation* IE is set to “MDT Only” then the DRNC shall, if supported, initiate the requested MDT function (M3 Report, if indicated) as described in TS 32.422 [49] and shall ignore the *List of Interfaces to Trace* IE and the *Trace Depth* IE.
+
+If *Trace Collection Entity IP Address* IE is included then the DRNC shall, if supported, store the Trace Collection Entity IP address and may use the Trace Collection Entity IP address when transferring trace records.
+
+#### 8.3.26.3 Abnormal Conditions
+
+If the *MDT Configuration* IE is included in the IUR INVOKE TRACE message and the *Trace Collection Entity IP Address* IE is not included, the DRNC shall ignore the MDT Configuration.
+
+### 8.3.27 Iur Deactivate Trace
+
+#### 8.3.27.1 General
+
+The purpose of the Iur Deactivate Trace procedure is to inform the DRNC that it should stop a Trace Session for the concerned UE Context and the indicated Trace Reference. This procedure is used for the Signalling Based Deactivation mechanism as defined in TS 32.421 [48] and TS 32.422 [49].
+
+This procedure shall use the signalling bearer mode specified below.
+
+#### 8.3.27.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ SRNC->>DRNC: IUR DEACTIVATE TRACE
+```
+
+Sequence diagram for Iur Deactivate Trace procedure. SRNC sends an IUR DEACTIVATE TRACE message to DRNC.
+
+**Figure 26L: Iur Invoke Trace procedure, Successful Operation**
+
+The Iur Deactivate Trace procedure is invoked by the SRNC by sending an IUR DEACTIVATE TRACE message to the DRNC.
+
+When the concerned UE is utilising one or more radio links in the DRNC the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the *D-RNTI* IE shall be included in the message to identify the UE Context in the DRNC.
+
+Upon receiving the IUR DEACTIVATE TRACE message, the DRNC shall stop for the concerned UE Context any ongoing Trace Recording Session for the Trace Session identified by the *Trace Reference* IE.
+
+#### 8.3.27.3 Abnormal Conditions
+
+-
+
+### 8.3.28 Enhanced Relocation
+
+#### 8.3.28.1 General
+
+This procedure is used for relocation of SRNS in case the SRNC and DRNC connect to same CN node.
+
+The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure in case the relevant UE Context does not exist for the UE.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context in the UE Context exists. The Enhanced Relocation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
+
+#### 8.3.28.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ SRNC->>DRNC: ENHANCED RELOCATION REQUEST
+ DRNC-->>SRNC: ENHANCED RELOCATION RESPONSE
+```
+
+Sequence diagram for Enhanced Relocation procedure. SRNC sends an ENHANCED RELOCATION REQUEST to DRNC, and DRNC responds with an ENHANCED RELOCATION RESPONSE.
+
+**Figure 26M: Enhanced Relocation procedure: Successful Operation**
+
+The SRNC initiates the procedure by sending an ENHANCED RELOCATION REQUEST message. When the SRNC sends the ENHANCED RELOCATION REQUEST message, it shall start the timer $T_{RELOCprep}$ . The ENHANCED RELOCATION REQUEST message shall contain the *Cause* IE with an appropriate value e.g.: "Time critical Relocation", "Resource optimisation relocation", "Relocation desirable for radio reasons", "Directed Retry", "Reduce Load in Serving Cell", "No Iu CS UP relocation".
+
+If the ENHANCED RELOCATION REQUEST message includes SRNC-ID, the DRNC shall create a UE Context for this UE, allocate a D-RNTI for the UE Context.
+
+#### 8.3.28.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ SRNC->>DRNC: ENHANCED RELOCATION REQUEST
+ DRNC-->>SRNC: ENHANCED RELOCATION FAILURE
+
+```
+
+A sequence diagram showing the interaction between SRNC and DRNC for an unsuccessful relocation. The SRNC sends an ENHANCED RELOCATION REQUEST message to the DRNC. The DRNC responds with an ENHANCED RELOCATION FAILURE message. Both messages are represented by horizontal arrows between vertical lines representing the SRNC and DRNC.
+
+Sequence diagram for Unsuccessful Operation
+
+**Figure 26N: Enhanced Relocation procedure: Unsuccessful Operation**
+
+If the DRNC is not able to accept any of the RABs or a failure occurs during the procedure, the DRNC shall send the ENHANCED RELOCATION FAILURE message to the SRNC. The message shall contain the *Cause* IE with an appropriate value.
+
+##### Interactions with Enhanced Relocation Cancel procedure:
+
+If there is no response from the DRNC to the ENHANCED RELOCATION REQUEST message before timer $T_{RELOCprep}$ expires in the DRNC, the SRNC should cancel the Enhanced Relocation procedure towards the DRNC by initiating the Enhanced Relocation Cancel procedure with the appropriate value for the *Cause* IE, e.g. " $T_{RELOCprep}$ expiry". The SRNC shall ignore any ENHANCED RELOCATION RESPONSE or ENHANCED RELOCATION FAILURE message received after the initiation of the Enhanced Relocation Cancel procedure and remove any reference and release any resources related to the concerned UE Context.
+
+#### 8.3.28.4 Abnormal Conditions
+
+-
+
+### 8.3.29 Enhanced Relocation Cancel
+
+#### 8.3.29.1 General
+
+This procedure is used to cancel an ongoing enhanced relocation or an already prepared relocation.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+#### 8.3.29.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ SRNC->>DRNC: ENHANCED RELOCATION CANCEL
+
+```
+
+A sequence diagram showing the interaction between SRNC and DRNC for a successful relocation cancel. The SRNC sends an ENHANCED RELOCATION CANCEL message to the DRNC, represented by a single horizontal arrow from the SRNC vertical line to the DRNC vertical line.
+
+Sequence diagram for Successful Operation
+
+**Figure 26O: Enhanced Relocation Cancel procedure: Successful Operation**
+
+The SRNC initiates the procedure by sending the ENHANCED RELOCATION CANCEL message to the DRNC. The SRNC shall indicate the reason for cancelling the relocation by means of an appropriate cause value. Typical cause values are " $T_{RELOCprep}$ expiry", "Relocation Cancelled", "Traffic Load In The Target Cell Higher Than In The Source Cell".
+
+At the reception of the ENHANCED RELOCATION CANCEL message, the DRNC shall remove any reference to, and release any resources previously reserved to the concerned UE context.
+
+#### 8.3.29.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.3.29.4 Abnormal Conditions
+
+-
+
+### 8.3.30 Enhanced Relocation Signalling Transfer
+
+#### 8.3.30.1 General
+
+The procedure is used by the SRNC to transfer DL L3 information to DRNC during enhanced relocation.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+#### 8.3.30.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: 8.3.30.2 Successful Operation
+ SRNC->>DRNC: ENHANCED RELOCATION SIGNALLING TRANSFER
+```
+
+Sequence diagram for Enhanced Relocation Signalling Transfer procedure, Successful Operation. It shows two vertical lifelines labeled SRNC and DRNC. A horizontal arrow labeled 'ENHANCED RELOCATION SIGNALLING TRANSFER' points from the SRNC lifeline to the DRNC lifeline.
+
+**Figure 26P: Enhanced Relocation Signalling Transfer procedure, Successful Operation**
+
+The procedure consists of the ENHANCED RELOCATION SIGNALLING TRANSFER message sent by the SRNC to the DRNC.
+
+The ENHANCED RELOCATION SIGNALLING TRANSFER message contains the L3 Information and after the receipt of the message, the DRNC shall send the L3 Information on the DCCH.
+
+#### 8.3.30.3 Abnormal Conditions
+
+-
+
+### 8.3.31 Enhanced Relocation Release
+
+#### 8.3.31.1 General
+
+The procedure is used by the DRNC to signal to the SRNC that resource for CN domain is released due to failure of the enhanced relocation.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+#### 8.3.31.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: 8.3.31.2 Successful Operation
+ DRNC->>SRNC: ENHANCED RELOCATION RELEASE
+```
+
+Sequence diagram for Enhanced Relocation Release procedure, Successful Operation. It shows two vertical lifelines labeled SRNC and DRNC. A horizontal arrow labeled 'ENHANCED RELOCATION RELEASE' points from the DRNC lifeline to the SRNC lifeline.
+
+**Figure 26Q: Enhanced Relocation Signalling Transfer procedure, Successful Operation**
+
+The procedure consists of the ENHANCED RELOCATION RELEASE message sent by the DRNC to the SRNC.
+
+Upon reception of the ENHANCED RELOCATION RELEASE message, the SRNC shall release related resources associated to indicated CN domain(s) by the *Released CN Domain* IE in the message for the UE context.
+
+#### 8.3.31.3 Abnormal Conditions
+
+-
+
+### 8.3.32 Secondary UL Frequency Reporting [FDD]
+
+#### 8.3.32.1 General
+
+The purpose of this procedure is to inform the DRNC about the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation.
+
+This procedure shall use the signalling bearer connection for the relevant UE Context.
+
+#### 8.3.32.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ SRNC->>DRNC: SECONDARY UL FREQUENCY REPORT
+```
+
+Sequence diagram for Figure 26R: Secondary UL Frequency Reporting procedure. It shows a message labeled 'SECONDARY UL FREQUENCY REPORT' being sent from the SRNC to the DRNC.
+
+**Figure 26R: Secondary UL Frequency Reporting procedure**
+
+The Secondary UL Frequency Reporting procedure is initiated by sending the SECONDARY UL FREQUENCY REPORT message from the SRNC to the DRNC.
+
+The *Activation Information* IE defines the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation.
+
+- If the value of *Uu Activation State* IE is “Activated”: the DRNC shall if supported use this information for resource allocation operation of the secondary E-DCH radio link(s), F-DPCH transmission and DPCCH detection.
+- If the value of *Uu Activation State* IE is “De-Activated”: the DRNC shall if supported use this information for release of the related resources for the secondary E-DCH radio link(s), cease of F-DPCH transmission and DPCCH detection.
+
+#### 8.3.32.3 Abnormal Conditions
+
+-
+
+### 8.3.33 Secondary UL Frequency Update [FDD]
+
+#### 8.3.33.1 General
+
+The purpose of this procedure is to inform the SRNC about updates to activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation.
+
+This procedure shall use the signalling bearer connection for the relevant UE context.
+
+#### 8.3.33.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC
+ Note right of DRNC: DRNC
+ DRNC->>SRNC: SECONDARY UL FREQUENCY UPDATE INDICATION
+```
+
+Sequence diagram for Figure 26S: Secondary UL Frequency Update procedure. It shows a message labeled 'SECONDARY UL FREQUENCY UPDATE INDICATION' being sent from the DRNC to the SRNC.
+
+**Figure 26S: Secondary UL Frequency Update procedure**
+
+The Secondary UL Frequency Update procedure is initiated by the DRNS by sending the SECONDARY UL FREQUENCY UPDATE INDICATION message to the SRNC.
+
+If the DRNS needs to update the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation, the DRNS shall send SECONDARY UL FREQUENCY UPDATE INDICATION message and include the *Activation Information* IE.
+
+#### 8.3.33.3 Abnormal Conditions
+
+-
+
+## 8.4 Common Transport Channel Procedures
+
+### 8.4.1 Common Transport Channel Resources Initialisation
+
+#### 8.4.1.1 General
+
+The Common Transport Channel Resources Initialisation procedure is used by the SRNC for the initialisation of the Common Transport Channel user plane towards the DRNC and/or for the initialisation of the Common Transport Channel resources in the DRNC to be used by a UE.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+#### 8.4.1.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: SRNC initiates procedure
+ SRNC->>DRNC: COMMON TRANSPORT CHANNEL RESOURCES REQUEST
+ Note right of DRNC: DRNC responds
+ DRNC-->>SRNC: COMMON TRANSPORT CHANNEL RESOURCES RESPONSE
+
+```
+
+Sequence diagram showing the Common Transport Channel Resources Initialisation procedure between SRNC and DRNC. The SRNC sends a COMMON TRANSPORT CHANNEL RESOURCES REQUEST message to the DRNC, and the DRNC responds with a COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.
+
+**Figure 27: Common Transport Channel Resources Initialisation procedure, Successful Operation**
+
+The SRNC initiates the procedure by sending the message COMMON TRANSPORT CHANNEL RESOURCES REQUEST message to the DRNC.
+
+If the value of the *Transport Bearer Request Indicator* IE is set to “Bearer Requested”, the DRNC shall store the received *Transport Bearer ID* IE. The DRNC may use the *Transport Layer Address* and *Binding ID* IEs included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message received from the SRNC when establishing a transport bearer for the common transport channel. In addition, the DRNC shall include its own *Binding ID* IE and *Transport Layer Address* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.
+
+If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the DRNC to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related common transport channels.
+
+If the value of the *Transport Bearer Request Indicator* IE is set to “Bearer not Requested”, the DRNC shall use the transport bearer indicated by the *Transport Bearer ID* IE.
+
+If the *C-ID* IE is included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall allocate a C-RNTI for the indicated cell and include the *C-RNTI* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.
+
+If the *C-ID* IE is included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall include the *FACH Info for UE Selected S-CCPCH* IE valid for the cell indicated by the *C-ID* IE and the corresponding *C-ID* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the *C-ID* IE is not included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall include the *FACH Info for UE Selected S-CCPCH* IE valid for the cell where the UE is located and the corresponding
+
+*C-ID* IE. The DRNC shall include the *FACH Scheduling Priority* IE and *FACH Initial Window Size* IE in the *FACH Flow Control Information* IE of the *FACH Info for UE Selected S-CCPCH* IE for each priority class that the DRNC has determined shall be used. The DRNC may include several *MAC-c/sh SDU Length* IEs for each priority class.
+
+If the DRNS has any RACH and/or FACH [FDD – and/or HS-DSCH] [1.28Mcps TDD – and/or HS-DSCH] resources previously allocated for the UE in another cell than the cell in which resources are currently being allocated, the DRNS shall release the previously allocated RACH and/or FACH resources [FDD – and/or HS-DSCH] [1.28Mcps TDD – and/or HS-DSCH].
+
+If the DRNS has successfully reserved the required resources, the DRNC shall respond to the SRNC with the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.
+
+If the *Permanent NAS UE Identity* IE is present in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNS shall store the information for the considered UE Context for the lifetime of the UE Context.
+
+If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes a *C-ID* IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is available in the DRNC for the considered UE Context, the DRNC shall use this information to determine whether it can reserve resources on a common transport channel in this cell or not.
+
+If the *MBMS Bearer Service List* IE is included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall, if supported, perform the UE Linking as specified in TS 25.346 [50], section 5.1.6. If an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in the cell identified by the *C-ID* IE, the DRNC shall include in the *Active MBMS Bearer Service List* IE the *Transmission Mode* IE for each of these active MBMS bearer services in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.
+
+[FDD – If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an *Enhanced FACH Support Indicator* IE, the DRNC may include the *Enhanced FACH Information Response* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If a HS-DSCH RNTI was not previously allocated to the UE or a new HS-DSCH RNTI is allocated to the UE, the DRNC shall include the *HS-DSCH-RNTI* IE in the *Enhanced FACH Information Response* IE. And if Enhanced PCH operation is activated in the cell indicated by the *C-ID* IE, the DRNC shall include the *Priority Queue Information for Enhanced PCH* IE in the *Enhanced FACH Information Response* IE.]
+
+[1.28Mcps TDD – If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an *Enhanced FACH Support Indicator* IE, the DRNC may include the *Enhanced FACH Information Response* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If a HS-DSCH RNTI was not previously allocated to the UE or a new HS-DSCH RNTI is allocated to the UE, the DRNC shall include the *HS-DSCH-RNTI* IE in the *Enhanced FACH Information Response* IE. And if Enhanced PCH operation is activated in the cell indicated by the *C-ID* IE, the DRNC shall include the *Priority Queue Information for Enhanced PCH* IE in the *Enhanced FACH Information Response* IE.]
+
+[FDD – If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an *Common E-DCH Support Indicator* IE, the DRNC may include the *Common E-DCH MAC-d Flow Specific Information* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the E-DCH MAC-d Flow Multiplexing List for a Common E-DCH MAC-d Flow is configured in DRNC, the DRNC shall include the *E-DCH MAC-d Flow Multiplexing List* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes the *C-ID* IE and the *Common E-DCH Support Indicator* IE, the DRNC may include the *E-RNTI* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.]
+
+[1.28Mcps TDD – If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an *Enhanced FACH Support Indicator* IE, the DRNC may include the *Common E-DCH MAC-d Flow Specific Information LCR* IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.]
+
+If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an *HS-DSCH physical layer category* IE, the DRNC may store the information for the considered UE Context for the lifetime of the UE Context.
+
+[FDD – If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an *UE with enhanced HS-SCCH support indicator* IE, the DRNC may store the information for the considered UE Context for the lifetime of the UE context.]
+
+#### 8.4.1.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of SRNC: COMMON TRANSPORT CHANNEL RESOURCES REQUEST
+ SRNC->>DRNC: COMMON TRANSPORT CHANNEL RESOURCES REQUEST
+ Note left of DRNC: COMMON TRANSPORT CHANNEL RESOURCES FAILURE
+ DRNC-->>SRNC: COMMON TRANSPORT CHANNEL RESOURCES FAILURE
+
+```
+
+The diagram illustrates a sequence of messages between an SRNC (Source RNC) and a DRNC (Dedicated RNC). The SRNC sends a 'COMMON TRANSPORT CHANNEL RESOURCES REQUEST' message to the DRNC. The DRNC responds with a 'COMMON TRANSPORT CHANNEL RESOURCES FAILURE' message, indicating an unsuccessful operation.
+
+Sequence diagram showing the Unsuccessful Operation of Common Transport Channel Resources Initialisation procedure between SRNC and DRNC.
+
+**Figure 28: Common Transport Channel Resources Initialisation procedure, Unsuccessful Operation**
+
+If the *Transport Bearer Request Indicator* IE is set to “Bearer Requested” and the DRNC is not able to provide a Transport Bearer, the DRNC shall reject the procedure and respond to the SRNC with the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message, including the reason for the failure in the *Cause* IE.
+
+If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message contains a *C-ID* IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is not available for the considered UE Context, the DRNC shall reject the procedure and send the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message, including the reason for the failure in the *Cause* IE.
+
+Typical cause values are:
+
+##### Radio Network Layer Causes:
+
+- Common Transport Channel Type not Supported;
+- Cell reserved for operator use.
+
+##### Transport Layer Causes:
+
+- Transport Resource Unavailable.
+
+#### 8.4.1.4 Abnormal Conditions
+
+If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE, and not both are present for a transport channel intended to be established, the DRNC shall reject the procedure using the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message.
+
+If ALCAP is not used, if the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message contains the *Transport Bearer Request Indicator* IE set to “Bearer Requested” but does not contain the *Transport Layer Address* IE and the *Binding ID* IE, the DRNC shall reject the procedure using the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message.
+
+### 8.4.2 Common Transport Channel Resources Release
+
+#### 8.4.2.1 General
+
+This procedure is used by the SRNC to request release of Common Transport Channel Resources for a given UE in the DRNS. The SRNC uses this procedure either to release the UE Context from the DRNC (and thus both the D-RNTI and the C-RNTI) or to release only the C-RNTI.
+
+This procedure shall use the connectionless mode of the signalling bearer.
+
+#### 8.4.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of SRNC: COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST
+ SRNC->>DRNC: COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST
+
+```
+
+Sequence diagram for Figure 29: Common Transport Channel Resources Release procedure, Successful Operation. It shows a message 'COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST' being sent from SRNC to DRNC.
+
+**Figure 29: Common Transport Channel Resources Release procedure, Successful Operation**
+
+The SRNC initiates the Common Transport Channel Resources Release procedure by sending the COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST message to the DRNC. Upon receipt of the message the DRNC shall release the UE Context identified by the D-RNTI and all its related RACH and/or FACH resources, unless the UE is using dedicated resources (DCH, [TDD – USCH and/or DSCH]) in the DRNS in which case the DRNC shall release only the C-RNTI and all its related RACH and/or FACH [FDD – and/or HS-DSCH] [1.28Mcps TDD – and/or HS-DSCH] resources allocated for the UE.
+
+#### 8.4.2.3 Abnormal Conditions
+
+-
+
+## 8.5 Global Procedures
+
+### 8.5.1 Error Indication
+
+#### 8.5.1.1 General
+
+The Error Indication procedure is initiated by a node to report detected errors in a received message, provided they cannot be reported by an appropriate response message.
+
+This procedure shall use the signalling bearer mode specified below.
+
+#### 8.5.1.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note right of RNC1: ERROR INDICATION
+ RNC1->>RNC2: ERROR INDICATION
+
+```
+
+Sequence diagram for Figure 30: Error Indication procedure, Successful Operation. It shows a message 'ERROR INDICATION' being sent from RNC1 to RNC2.
+
+**Figure 30: Error Indication procedure, Successful Operation**
+
+When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. This message shall use the same mode of the signalling bearer and the same signalling bearer connection (if connection oriented) as the message that triggers the procedure.
+
+When the ERROR INDICATION message is sent from a DRNC to an SRNC using connectionless mode of the signalling bearer, the *S-RNTI* IE shall be included in the message if the UE Context addressed by the *D-RNTI* IE which was received in the message triggering the Error Indication procedure exists. When the ERROR INDICATION message is sent from an SRNC to a DRNC using connectionless mode of the signalling bearer, the *D-RNTI* IE shall be included in the message if available.
+
+When a message using connectionless mode of the signalling bearer is received in the DRNC and there is no UE Context in the DRNC as indicated by the *D-RNTI* IE, the DRNC shall include the *D-RNTI* from the received message in the *D-RNTI* IE and set the *Cause* IE to “Unknown RNTI” in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.
+
+When a message using connectionless mode of the signalling bearer is received in the SRNC and there is no UE in the SRNC as indicated by the *S-RNTI* IE, the SRNC shall include the S-RNTI from the received message in the *S-RNTI* IE and set the *Cause* IE to “Unknown RNTI” in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.
+
+The ERROR INDICATION message shall include either the *Cause* IE, or the *Criticality Diagnostics* IE, or both the *Cause* IE and the *Criticality Diagnostics* IE to indicate the reason for the error indication.
+
+Typical cause values for the ERROR INDICATION message are:
+
+##### **Protocol Causes:**
+
+- Transfer Syntax Error;
+- Abstract Syntax Error (Reject);
+- Abstract Syntax Error (Ignore and Notify);
+- Message not Compatible with Receiver State;
+- Unspecified.
+
+##### 8.5.1.2.1 Successful Operation for Iur-g
+
+The RNC1/BSS1 and RNC2/BSS2 shall use the error indication procedure as specified in section 8.5.1.2.
+
+#### 8.5.1.3 Abnormal Conditions
+
+-
+
+### 8.5.2 Common Measurement Initiation
+
+#### 8.5.2.1 General
+
+This procedure is used by an RNC to request the initiation of measurements of common resources to another RNC. The requesting RNC is referred to as RNC1 and the RNC to which the request is sent is referred to as RNC2.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC1: RNC1
+ Note right of RNC2: RNC2
+ RNC1->>RNC2: COMMON MEASUREMENT INITIATION REQUEST
+ RNC2-->>RNC1: COMMON MEASUREMENT INITIATION RESPONSE
+
+```
+
+Sequence diagram showing the Common Measurement Initiation procedure between RNC1 and RNC2. RNC1 sends a COMMON MEASUREMENT INITIATION REQUEST to RNC2, and RNC2 responds with a COMMON MEASUREMENT INITIATION RESPONSE.
+
+**Figure 30A: Common Measurement Initiation procedure, Successful Operation**
+
+The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the RNC1 to the RNC2.
+
+Upon receipt, the RNC2 shall initiate the requested measurement according to the parameters given in the request.
+
+Unless specified below, the meaning of the parameters are given in other specifications.
+
+[TDD – If the [3.84 Mcps TDD and 7.68 Mcps TDD – *Time Slot* IE] [1.28 Mcps – *Time Slot LCR* IE] is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested time slot individually.]
+
+##### Common measurement type
+
+If the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then:
+
+- The RNC2 shall initiate the SFN-SFN Observed Time Difference measurements between the reference cell identified by the *Reference Cell Identifier* IE and the neighbouring cells identified by the *UTRAN Cell Identifier* IE (*UC-ID*) in the *Neighbouring Cell Measurement Information* IE.
+- [3.84 Mcps TDD – The RNC2 shall perform the measurement using the time slot specified in the *Time Slot* IE in the *Neighbouring TDD Cell Measurement Information* IE and using the midamble shift and burst type specified in the *Midamble Shift And Burst Type* IE in the *Neighbouring TDD Cell Measurement Information* IE. If *Time Slot* IE and *Midamble Shift And Burst Type* IE are not available in the *Neighbouring TDD Cell Measurement Information* IE, the RNC2 may use any appropriate time slots, midamble shifts and burst types to make the measurement.]
+- [7.68 Mcps TDD – The RNC2 shall perform the measurement using the time slot specified in the *Time Slot* IE in the *Neighbouring TDD Cell Measurement Information 7.68 Mcps* IE and using the midamble shift and burst type specified in the *Midamble Shift And Burst Type 7.68 Mcps* IE in the *Neighbouring TDD Cell Measurement Information 7.68 Mcps* IE. If *Time Slot* IE and *Midamble Shift And Burst Type 7.68 Mcps* IE are not available in the *Neighbouring TDD Cell Measurement Information 7.68 Mcps* IE, the RNC2 may use any appropriate time slots, midamble shifts and burst types to make the measurement.]
+
+If the *Common Measurement Type* IE is set to “load”, the RNC2 shall initiate measurements of uplink and downlink load on the measured object identified by the *Reference Cell Identifier* IE. If either uplink or downlink load satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink measurements.
+
+If the *Common Measurement Type* IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning”, “UTRAN GANSS Timing of Cell Frames for UE Positioning”, “transmitted carrier power”, “received total wide band power”, or “UL timeslot ISCP” the RNC2 shall initiate measurements on the measured object identified by the *Reference Cell Identifier* IE.
+
+If the *Common Measurement Type* IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning”, then the RNC2 shall initiate the UTRAN GANSS Timing of Cell Frames measurements using the GNSS system time identified by *GANSS Time ID* IE included in the COMMON MEASUREMENT INITIATION REQUEST message.
+
+- If the *Common Measurement Type* IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning” and the *GANSS Time ID* IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall assume that the corresponding GANSS time is “Galileo” system time.
+
+If the *Common Measurement Type* IE is set to “RT load”, the RNC2 shall initiate measurements of uplink and downlink estimated share of RT (Real Time) traffic of the load of the measured object. If either uplink or downlink RT load satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink measurements.
+
+If the *Common Measurement Type* IE is set to “NRT load Information”, the RNC2 shall initiate measurements of uplink and downlink NRT (Non Real Time) load situation on the measured object. If either uplink or downlink NRT load satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink measurements.
+
+##### Report characteristics
+
+The *Report Characteristics* IE indicates how the reporting of the measurement shall be performed. See also Annex B.
+
+If the *Report Characteristics* IE is set to “On Demand” and if the *SFN* IE is not provided, the RNC2 shall report the result of the requested measurement immediately in the COMMON MEASUREMENT INITIATION RESPONSE message. If the *SFN* IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the *SFN* IE is present and if the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then the *SFN* IE relates to the Radio Frames of the Reference Cell identified by the *Reference Cell Identifier* IE.
+
+If the *Report Characteristics* IE is set to “Periodic” and if the *SFN* IE is not provided, the RNC2 shall immediately and periodically initiate a Common Measurement Reporting procedure for this measurement, with a frequency as specified by the *Report Periodicity* IE. If the *SFN* IE is provided, the RNC2 shall initiate a Common Measurement Reporting procedure for this measurement at the SFN indicated in the *SFN* IE, and shall repeat this initiation periodically thereafter with a frequency as specified by the *Report Periodicity* IE. The provided measurement value shall be the one
+
+reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the *SFN IE* is present and if the *Common Measurement Type IE* is set to “SFN-SFN Observed Time Difference “, then the *SFN IE* relates to the Radio Frames of the Reference Cell identified by the *Reference Cell Identifier IE*.
+
+If the *Report Characteristics IE* is set to “Event A”, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity rises above the requested threshold, as specified by the *Measurement Threshold IE*, and then stays above the threshold for the requested hysteresis time, as specified by the *Measurement Hysteresis Time IE*. If the *Measurement Hysteresis Time IE* is not included, the RNC2 shall use the value zero for the hysteresis time.
+
+If the *Report Characteristics IE* is set to “Event B”, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity falls below the requested threshold, as specified by the *Measurement Threshold IE*, and then stays below the threshold for the requested hysteresis time, as specified by the *Measurement Hysteresis Time IE*. If the *Measurement Hysteresis Time IE* is not included, the RNC2 shall use the value zero for the hysteresis time.
+
+If the *Report Characteristics IE* is set to “Event C”, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity rises more than the requested threshold specified by the *Measurement Increase/Decrease Threshold IE*, and only when this rise occurs within the requested rising time specified by the *Measurement Change Time IE*. After reporting this type of event, the RNC2 shall not initiate the next C event reporting for the same measurement during the subsequent time specified by the *Measurement Change Time IE*.
+
+If the *Report Characteristics IE* is set to “Event D”, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity falls more than the requested threshold specified by the *Measurement Increase/Decrease Threshold IE*, and only when this fall occurs within the requested falling time specified by the *Measurement Change Time IE*. After reporting this type of event,, the RNC2 shall not initiate the next D event reporting for the same measurement during the subsequent time specified by the *Measurement Change Time IE*.
+
+If the *Report Characteristics IE* is set to “Event E”, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity rises above the *Measurement Threshold 1 IE* and stays above the threshold for the *Measurement Hysteresis Time IE* (Report A). When the conditions for Report A are met and if the *Report Periodicity IE* is provided, the RNC2 shall initiate the Common Measurement Reporting procedure periodically with the requested report frequency specified by the *Report Periodicity IE*. If the conditions for Report A have been met and the measured entity falls below the *Measurement Threshold 2 IE* and stays below the threshold for the *Measurement Hysteresis Time IE*, the RNC2 shall initiate the Common Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the *Measurement Threshold 2 IE* is not present, the RNC2 shall use the value of the *Measurement Threshold 1 IE* instead. If the *Measurement Hysteresis Time IE* is not included, the RNC2 shall use the value zero as hysteresis times for both Report A and Report B.
+
+If the *Report Characteristics IE* is set to “Event F”, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity falls below the *Measurement Threshold 1 IE* and stays below the threshold for the *Measurement Hysteresis Time IE* (Report A). When the conditions for Report A are met and if the *Report Periodicity IE* is provided, the RNC2 shall initiate the Measurement Reporting procedure periodically with the requested report frequency specified by the *Report Periodicity IE*. If the conditions for Report A have been met and the measured entity rises above the *Measurement Threshold 2 IE* and stays above the threshold for the *Measurement Hysteresis Time IE*, the RNC2 shall initiate the Common Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the *Measurement Threshold 2 IE* is not present, the RNC2 shall use the value of the *Measurement Threshold 1 IE* instead. If the *Measurement Hysteresis Time IE* is not included, the RNC2 shall use the value zero as hysteresis times for both Report A and Report B.
+
+[1.28Mcps TDD-If the *Report Characteristics IE* is set to “Event H” (figure B.7), the Measurement Reporting procedure (Report A) is initiated when the measurement value of measured entity rises above the *Measurement Threshold 1* and stays above the threshold for the *Measurement Hysteresis Time* ( $T_1$ in figure B.7).] The measurement value of measured entity in Report A substitutes the *Measurement Base value* for the consequent measurement reporting.
+
+When the Report A conditions has been met and the measurement value of measured entity rises above or falls below the *Measurement Base Value* by *Measurement Fluctuation Range* ( $H_1$ in figure B.7), and stays there for the *Measurement Hysteresis Time* ( $T_h$ in figure B.7) counting from the beginning of every *Report Periodicity*, the Measurement Reporting procedure (Report B or Report C) is initiated. The the measurement value of measured entity in (Report B or Report C) substitutes the *Measurement Base value* for the consequent measurement reporting.
+
+When the Report A conditions have been met and the measurement value of measured entity falls below the *Measurement Threshold 2* and stays there for the *Measurement Hysteresis Time* ( $T_h$ in figure B.7), the Measurement Reporting procedure (Report D) is initiated and the reporting is terminated.]
+
+If the *Report Characteristics* IE is set to “On Modification” and if the *SFN* IE is not provided, the RNC2 shall report the result of the requested measurement immediately. If the *SFN* IE is provided, it indicates the frame for which the first measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the *SFN* IE is present and if the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then the *SFN* IE relates to the Radio Frames of the Reference Cell identified by the *Reference Cell Identifier* IE. Following the first measurement report, the RNC2 shall initiate the Common Measurement Reporting procedure in accordance to the following conditions:
+
+1. If the *Common Measurement Type* IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning”:
+
+- - If the *TUTRAN-GPS Change Limit* IE is included in the *TUTRAN-GPS Measurement Threshold Information* IE, the RNC2 shall calculate the change of TUTRAN-GPS value (Fn) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of Fn rises above the threshold indicated by the *TUTRAN-GPS Change Limit* IE. The change of TUTRAN-GPS value (Fn) is calculated according to the following:
+ - Fn=0 for n=0
+ - $F_n = (M_n - M_{n-1}) \bmod 37158912000000 - ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + F_{n-1}$ for n>0
+ - Fn is the change of the TUTRAN-GPS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn.
+ - Mn-1 is the previous measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn-1.
+ - M1 is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.
+ - M0 is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered.
+- - If the *Predicted TUTRAN-GPS Deviation Limit* IE is included in the *TUTRAN-GPS Measurement Threshold Information* IE, the RNC2 shall update the Pn and F each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set n equal to zero when Fn rises above the threshold indicated by the *Predicted TUTRAN-GPS Deviation Limit* IE. The Pn and Fn are calculated according to the following:
+ - Pn=b for n=0
+ - $P_n = ((a/16) * ((SFN_n - SFN_{n-1}) \bmod 4096) / 100 + ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + P_{n-1}) \bmod 37158912000000$ for n>0
+ - $F_n = \min((M_n - P_n) \bmod 37158912000000, (P_n - M_n) \bmod 37158912000000)$ for n>0
+ - Pn is the predicted TUTRAN-GPS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - A is the last reported TUTRAN-GPS Drift Rate value.
+ - B is the last reported TUTRAN-GPS value.
+ - Fn is the deviation of the last measurement result from the predicted TUTRAN-GPS value (Pn) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn.
+
+- $M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.
+ - The $T_{UTRAN-GPS}$ Drift Rate is determined by the $RNS_2$ in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).
+2. If the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”:
+- - If the *SFN-SFN Change Limit* IE is included in the *SFN-SFN Measurement Threshold Information* IE, the $RNC_2$ shall calculate the change of SFN-SFN value ( $F_n$ ) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The $RNC_2$ shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set $n$ equal to zero when the absolute value of $F_n$ rises above the threshold indicated by the *SFN-SFN Change Limit* IE. The change of the SFN-SFN value is calculated according to the following:
+ - $F_n=0$ for $n=0$
+ - $[FDD - F_n = (M_n - a) \bmod 614400 \quad \text{for } n>0]$
+ - $[TDD - F_n = (M_n - a) \bmod 40960 \quad \text{for } n>0]$
+ - $F_n$ is the change of the SFN-SFN value expressed in unit [1/16 chip] when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - $A$ is the last reported SFN-SFN.
+ - $M_n$ is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at $SFN_n$ .
+ - $M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - - If the *Predicted SFN-SFN Deviation Limit* IE is included in the *SFN-SFN Measurement Threshold Information* IE, the $RNC_2$ shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]), update the $P_n$ and $F_n$ . The $RNC_2$ shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set $n$ equal to zero when $F_n$ rises above the threshold indicated by the *Predicted SFN-SFN Deviation Limit* IE. The $P_n$ and $F_n$ are calculated according to the following:
+ - $P_n=b$ for $n=0$
+ - $[FDD - P_n = ((a/16) * ((SFN_n - SFN_{n-1}) \bmod 4096)/100 + P_{n-1}) \bmod 614400 \quad \text{for } n>0]$
+ - $[FDD - F_n = \min((M_n - P_n) \bmod 614400, (P_n - M_n) \bmod 614400) \quad \text{for } n>0]$
+ - $[TDD - P_n = ((a/16) * (15*(SFN_n - SFN_{n-1}) \bmod 4096 + (TS_n - TS_{n-1})/1500 + P_{n-1})) \bmod 40960 \quad \text{for } n>0]$
+ - $[TDD - F_n = \min((M_n - P_n) \bmod 40960, (P_n - M_n) \bmod 40960) \quad \text{for } n>0]$
+ - $P_n$ is the predicted SFN-SFN value when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - $A$ is the last reported SFN-SFN Drift Rate value.
+ - $B$ is the last reported SFN-SFN value.
+ - $F_n$ is the deviation of the last measurement result from the predicted SFN-SFN value ( $P_n$ ) when $n$ measurements have been received after first Common Measurement Reporting at initiation or after the last event was triggered.
+ - $M_n$ is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at the [TDD – the Time Slot $TS_n$ of] the Frame $SFN_n$ .
+
+- $M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.
+ - The SFN-SFN Drift Rate is determined by the $RNS_2$ in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).
+3. If the *Common Measurement Type* IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning”:
+- - If the *TUTRAN-GANSS Change Limit* IE is included in the *TUTRAN-GANSS Measurement Threshold Information* IE, the RNC2 shall calculate the change of $T_{UTRAN-GANSS}$ value ( $F_n$ ) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set $n$ equal to zero when the absolute value of $F_n$ rises above the threshold indicated by the *TUTRAN-GANSS Change Limit* IE. The change of $T_{UTRAN-GANSS}$ value ( $F_n$ ) is calculated according to the following:
+ - $F_n=0$ for $n=0$
+ - $F_n = (GAM_n - GAM_{n-1}) \bmod 5308416000000 - ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + F_{n-1}$
+ - for $n > 0$
+ - $F_n$ is the change of the $T_{UTRAN-GANSS}$ value expressed in unit [1/16 chip] when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - $GAM_n$ is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at $SFN_n$ .
+ - $GAM_{n-1}$ is the previous GANSS measurement result received after point C in the GANSS measurement model, measured at $SFN_{n-1}$ .
+ - $GAM_1$ is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - $GAM_0$ is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered.
+ - GANSS measurement model is the timing between cell $j$ and GANSS Time Of Day. $T_{UE-GANSSj}$ is defined as the time of occurrence of a specified UTRAN event according to GANSS time. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell $j$ CPICH, where cell $j$ is a cell chosen by the UE. The reference point for $T_{UE-GANSSj}$ shall be the antenna connector of the UE.
+ - - If the *Predicted TUTRAN-GANSS Deviation Limit* IE is included in the *TUTRAN-GANSS Measurement Threshold Information* IE, the RNC2 shall update the $P_n$ and $F$ each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set $n$ equal to zero when $F_n$ rises above the threshold indicated by the *Predicted TUTRAN-GANSS Deviation Limit* IE. The $P_n$ and $F_n$ are calculated according to the following:
+ - $P_n=b$ for $n=0$
+ - $P_n = ((a/16) * ((SFN_n - SFN_{n-1}) \bmod 4096)/100 + ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + P_{n-1}) \bmod 5308416000000$ for $n > 0$
+ - $F_n = \min((GAM_n - P_n) \bmod 5308416000000, (P_n - GAM_n) \bmod 5308416000000)$ for $n > 0$
+ - $P_n$ is the predicted $T_{UTRAN-GANSS}$ value when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+ - $A$ is the last reported $T_{UTRAN-GANSS}$ Drift Rate value.
+ - $B$ is the last reported $T_{UTRAN-GANSS}$ value.
+
+- $F_n$ is the deviation of the last measurement result from the predicted $T_{UTRAN-GNSS}$ value ( $P_n$ ) when $n$ measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
+- $GAM_n$ is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at $SFN_n$ .
+- $GAM_1$ is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.
+- The $T_{UTRAN-GNSS}$ Drift Rate is determined by the $RNS_2$ in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).
+
+If the *Report Characteristics* IE is not set to “On Demand”, the $RNC_2$ is required to perform reporting for a common measurement object, in accordance with the conditions provided in the COMMON MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no common measurement object(s) for which a measurement is defined exists any more, the $RNC_2$ shall terminate the measurement locally without reporting this to $RNC_1$ .
+
+If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the $RNC_2$ shall initiate a Measurement Reporting procedure immediately, and then continue with the measurements as specified in the COMMON MEASUREMENT INITIATION REQUEST message.
+
+##### Common measurement accuracy
+
+If the *Common Measurement Type* IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning”, then the $RNC_2$ shall use the $T_{UTRAN-GPS}$ *Measurement Accuracy Class* IE included in the *Common Measurement Accuracy* IE according to the following:
+
+- If the $T_{UTRAN-GPS}$ *Measurement Accuracy Class* IE indicates “Class A”, then the concerned $RNC_2$ shall perform the measurement with the highest supported accuracy within the accuracy classes A, B or C.
+- If the $T_{UTRAN-GPS}$ *Measurement Accuracy Class* IE indicates the “Class B”, then the concerned $RNC_2$ shall perform the measurements with the highest supported accuracy within the accuracy classes B and C.
+- If the $T_{UTRAN-GPS}$ *Measurement Accuracy Class* IE indicates “Class C”, then the concerned $RNC_2$ shall perform the measurements with the highest supported accuracy according to class C.
+
+If the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then the concerned $RNC_2$ shall initiate the SFN-SFN observed Time Difference measurements between the reference cell identified by *UC-ID* IE and the neighbouring cells identified by their UC-ID. The *Report Characteristics* IE applies to each of these measurements.
+
+If the *Common Measurement Type* IE is set to “UTRAN GANSS Timing of Cell Frames for UE positioning”, then the $RNC_2$ shall use the $T_{UTRAN-GNSS}$ *Measurement Accuracy Class* IE included in the *Common Measurement Accuracy* IE according to the following:
+
+- If the $T_{UTRAN-GNSS}$ *Measurement Accuracy Class* IE indicates “Class A”, then the concerned $RNC_2$ shall perform the measurement with the highest supported accuracy within the accuracy classes A, B or C.
+- If the $T_{UTRAN-GNSS}$ *Measurement Accuracy Class* IE indicates the “Class B”, then the concerned $RNC_2$ shall perform the measurements with the highest supported accuracy within the accuracy classes B and C.
+- If the $T_{UTRAN-GNSS}$ *Measurement Accuracy Class* IE indicates “Class C”, then the concerned $RNC_2$ shall perform the measurements with the highest supported accuracy according to class C.
+
+##### Higher layer filtering
+
+The *Measurement Filter Coefficient* IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting.
+
+The averaging shall be performed according to the following formula.
+
+The variables in the formula are defined as follows
+
+$F_n$ is the updated filtered measurement result
+
+$F_{n-1}$ is the old filtered measurement result
+
+$M_n$ is the latest received measurement result from physical layer measurements, the unit used for $M_n$ is the same unit as the reported unit in the COMMON MEASUREMENT INITIATION RESPONSE, COMMON MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for $F_n$ ).
+
+$A = \frac{1}{2^{(k/2)}}$ , where $k$ is the parameter received in the *Measurement Filter Coefficient* IE. If the *Measurement Filter Coefficient* IE is not present, $a$ shall be set to 1 (no filtering).
+
+In order to initialise the averaging filter, $F_0$ is set to $M_1$ when the first measurement result from the physical layer measurement is received.
+
+##### Measurement Recovery Behavior:
+
+If the *Measurement Recovery Behavior* IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall, if Measurement Recovery Behavior is supported, include the *Measurement Recovery Support Indicator* IE in the COMMON MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.5.3.2.
+
+##### Response message
+
+If the RNC2 was able to initiate the measurement requested by RNC, it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the COMMON MEASUREMENT INITIATION REQUEST message.
+
+In the case in which the *Report Characteristics* IE is set to “On Demand” or “On Modification”:
+
+- The COMMON MEASUREMENT INITIATION RESPONSE message shall include the *Common Measurement Object Type* IE containing the measurement result. It shall also include the *Common Measurement Achieved Accuracy* IE if the *Common Measurement Type* IE is set to “UTRAN GPS Timing of Cell Frames for UE positioning” or “UTRAN GANSS Timing of Cell Frames for UE positioning”.
+- If the *Common Measurement Type* IE is not set to “SFN-SFN Observed Time Difference” and if the *SFN Reporting Indicator* IE is set to “FN Reporting Required”, then the RNC2 shall include the *SFN* IE in the COMMON MEASUREMENT INITIATION RESPONSE message. The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then the *SFN Reporting Indicator* IE is ignored.
+- If the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then the RNC2 shall report all the available measurements in the *Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information* IE, and the RNC2 shall report the neighbouring cells with no measurement result available in the *Unsuccessful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information* IE. For all available measurement results, the RNC2 shall include in the *Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE the *SFN-SFN Quality* IE and the *SFN-SFN Drift Rate Quality* IE, if available.
+
+If the *Common Measurement Type* IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning” and the *Report Characteristics* IE is set to “On Demand” or “On Modification”, the RNC2 shall include in the *TUTRAN-GPS Measurement Value Information* IE the *TUTRAN-GPS Quality* IE and the *TUTRAN-GPS Drift Rate Quality* IE, if available.
+
+If the *Common Measurement Type* IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning” and the *Report Characteristics* IE is set to “On Demand” or “On Modification”, the RNC2 shall include in the *TUTRAN-GANSS Measurement Value Information* IE, the *TUTRAN-GANSS Quality* IE and the *TUTRAN-GANSS Drift Rate Quality* IE, if available.
+
+##### 8.5.2.2.1 Successful Operation for Iur-g
+
+The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the RNC1 to the BSS2 or from the BSS1 to the RNC2/BSS2.
+
+Upon receipt, the RNC2 /BSS2 shall initiate the requested measurement according to the parameters given in the request.
+
+[1.28Mcps TDD-The procedure is also initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the TDD RNC1 to the BSS2 for multiple GERAN cells’ measurements by allocating unique Measurement ID for each GERAN cell. Upon receipt, the BSS2 shall initiate the requested measurement according to the parameters given in the request.]
+
+###### Common measurement type on Iur-g
+
+If the *Common Measurement Type* IE is set to “load”, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.2.2.
+
+If the *Common Measurement Type* IE is set to “RT load”, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.2.2.
+
+If the *Common Measurement Type* IE is set to “NRT load Information”, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.2.2.
+
+###### Report characteristics on Iur-g
+
+The *Report Characteristics* IE indicates how the reporting of the measurement shall be performed. This IE is used as described in section 8.5.2.2.
+
+###### Response message for Iur-g
+
+If the RNC2/BSS2 was able to initiate the measurement requested by RNC1/BSS1 it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message sent. The message shall include the same Measurement ID that was used in the measurement request. Only in the case when the *Report Characteristics* IE is set to “On Demand”, the COMMON MEASUREMENT INITIATION RESPONSE message shall contain the measurement result.
+
+[1.28Mcps TDD- If the BSS2 was able to initiate the measurement requested by RNC1, it shall respond with one or more COMMON MEASUREMENT INITIATION RESPONSE messages sent. The message(s) should include the same Measurement ID that was used in the measurement request.
+
+#### 8.5.2.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC1:
+ RNC1->>RNC2: COMMON MEASUREMENT INITIATION REQUEST
+ Note right of RNC2:
+ RNC2-->>RNC1: COMMON MEASUREMENT INITIATION FAILURE
+ Note left of RNC1:
+
+```
+
+Sequence diagram showing the Unsuccessful Operation of the Common Measurement Initiation procedure. RNC1 sends a COMMON MEASUREMENT INITIATION REQUEST to RNC2, and RNC2 responds with a COMMON MEASUREMENT INITIATION FAILURE.
+
+**Figure 30B: Common Measurement Initiation procedure, Unsuccessful Operation**
+
+If the requested measurement cannot be initiated, the RNC2 shall send a COMMON MEASUREMENT INITIATION FAILURE message. The message shall include the same *Measurement ID* IE that was used in the COMMON MEASUREMENT INITIATION REQUEST message and shall include the *Cause* IE set to an appropriate value.
+
+Typical cause values are as follows:
+
+##### Radio Network Layer Cause
+
+- Measurement not supported for the object;
+- Measurement Temporarily not Available.
+
+#### 8.5.2.4 Abnormal Conditions
+
+If the COMMON MEASUREMENT INITIATION REQUEST message contains the *SFN-SFN Measurement Threshold Information* IE (in the *Measurement Threshold* IE contained in the *Report Characteristics* IE) and it does not contain at least one IE, the RNC2 shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+If the COMMON MEASUREMENT INITIATION REQUEST message contains the *TUTRAN-GPS Measurement Threshold Information* IE (in the *Measurement Threshold* IE contained in the *Report Characteristics* IE) and it does not contain at least one IE, the RNC2 shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+If the COMMON MEASUREMENT INITIATION REQUEST message contains the *TUTRAN-GANSS Measurement Threshold Information IE* (in the *Measurement Threshold IE* contained in the *Report Characteristics IE*) and it does not contain at least one IE, the RNC2 shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+If the *Common Measurement Type IE* is set to “UTRAN GPS Timing of Cell Frames for UE positioning”, but the *TUTRAN-GPS Measurement Accuracy Class IE* in the *Common Measurement Accuracy IE* is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+If the *Common Measurement Type IE* is set to “UTRAN GANSS Timing of Cell Frames for UE positioning”, but the *TUTRAN-GANSS Measurement Accuracy Class IE* in the *Common Measurement Accuracy IE* is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+If the Common Measurement Type received in the *Common Measurement Type IE* is not “load”, “RT load” or “NRT load Information”, and if the Common Measurement Type received in the *Common Measurement Type IE* is not defined in TS 25.215 [11] or TS 25.225 [14] to be measured on the Common Measurement Object Type indicated in the COMMON MEASUREMENT INITIATION REQUEST message the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+If the *Common Measurement Type IE* is set to “SFN-SFN Observed Time Difference”, but the *Neighbouring Cell Measurement Information IE* is not received in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+The allowed combinations of the Common Measurement Type and Report Characteristics Type are shown in the table below marked with “X”. For not allowed combinations, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+**Table 5: Allowed Common Measurement Type and Report Characteristics Type Combinations**
+
+| Common measurement type | Report characteristics type | | | | | | | | | |
+|------------------------------------------------------|-----------------------------|----------|---------|---------|---------|---------|---------|---------|---------|-----------------|
+| | On Demand | Periodic | Event A | Event B | Event C | Event D | Event E | Event F | Event-H | On Modification |
+| Received total wide band power | X | X | X | X | X | X | X | X | | |
+| Transmitted Carrier Power | X | X | X | X | X | X | X | X | | |
+| UL Timeslot ISCP | X | X | X | X | X | X | X | X | | |
+| Load | X | X | X | X | X | X | X | X | X | |
+| UTRAN GPS Timing of Cell Frames for UE Positioning | X | X | | | | | | | | X |
+| SFN-SFN Observed Time Difference | X | X | | | | | | | | X |
+| RT load | X | X | X | X | X | X | X | X | | |
+| NRT load Information | X | X | X | X | X | X | X | X | | |
+| UpPTS interference | X | X | X | X | X | X | X | X | | |
+| UTRAN GANSS Timing of Cell Frames for UE Positioning | X | X | | | | | | | | X |
+
+[TDD – If the Common Measurement Type requires the Time Slot Information but the [3.84Mcps TDD and 7.68 Mcps TDD – *Time Slot IE*] [1.28Mcps TDD – *Time Slot LCR IE*] is not provided in the COMMON MEASUREMENT INITIATION REQUEST message the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.]
+
+If the *SFN IE* is included in the COMMON MEASUREMENT INITIATION REQUEST message and the *Report Characteristics* IE is other than “Periodic”, “On Demand” or “On Modification”, the RNS2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
+
+##### 8.5.2.4.1 Abnormal Conditions for Iur-g
+
+The measurements which can be requested on the Iur and Iur-g interfaces are shown in the table below marked with “X”.
+
+**Table 6: Allowed Common measurement type on Iur and Iur-g interfaces**
+
+| Common Measurement Type | Interface | |
+|------------------------------------------------------|-----------|-------|
+| | Iur | Iur-g |
+| Received total wide band power | X | |
+| Transmitted Carrier Power | X | |
+| UL Timeslot ISCP | X | |
+| Load | X | X |
+| UTRAN GPS Timing of Cell Frames for LCS | X | |
+| SFN-SFN Observed Time Difference | X | |
+| RT load | X | X |
+| NRT load Information | X | X |
+| UTRAN GANSS Timing of Cell Frames for UE Positioning | X | |
+
+If the RNC2 receives from the BSS1 a COMMON MEASUREMENT INITIATION REQUEST message in which a measurement, which is not applicable on the Iur-g interface, is requested, the RNC2 shall reject the Common Measurement Initiation procedure.
+
+If the BSS2 receives from the BSS1 / RNC1 a COMMON MEASUREMENT INITIATION REQUEST message in which a measurement, which is not applicable on the Iur-g interface, is requested, the BSS2 shall reject the Common Measurement Initiation procedure.
+
+If the RNC2 receives from the BSS1 a COMMON MEASUREMENT INITIATION REQUEST message in which the *SFN reporting indicator* IE is set to “FN Reporting Required”, the RNC2 shall ignore that IE.
+
+If the BSS2 receives from the BSS1 / RNC1 a COMMON MEASUREMENT INITIATION REQUEST message in which the *SFN reporting indicator* IE is set to “FN Reporting Required”, the BSS2 shall ignore that IE.
+
+The allowed combinations of the Common measurement type and Report characteristics type are shown in the table in section 8.5.2.4 marked with “X”. For not allowed combinations, the RNC2/BSS2 shall reject the Common Measurement Initiation procedure.
+
+### 8.5.3 Common Measurement Reporting
+
+#### 8.5.3.1 General
+
+This procedure is used by an RNC to report the result of measurements requested by another RNC using the Common Measurement Initiation.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.3.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note right of RNC2: Common Measurement Report
+ RNC2->>RNC1: COMMON MEASUREMENT REPORT
+
+```
+
+Diagram illustrating the Common Measurement Reporting procedure. RNC1 and RNC2 are shown as vertical lines. An arrow labeled 'COMMON MEASUREMENT REPORT' points from RNC2 to RNC1.
+
+**Figure 30C: Common Measurement Reporting procedure, Successful Operation**
+
+If the requested measurement reporting criteria are met, the RNC2 shall initiate the Common Measurement Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications.
+
+The *Measurement ID* IE shall be set to the Measurement ID provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure.
+
+If the achieved measurement accuracy does not fulfil the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the *Common Measurement Value Information* IE shall indicate Measurement not Available. If the RNC2 was configured to perform the Measurement Recovery Behavior, the RNC2 shall indicate Measurement Available to the RNC1 when the achieved measurement accuracy again fulfils the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) and include the *Measurement Recovery Report Indicator* IE in the COMMON MEASUREMENT REPORT message if the requested measurement reporting criteria are not met.
+
+For measurements included in the *Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE, the RNC2 shall include the *SFN-SFN Quality* IE and the *SFN-SFN Drift Rate Quality* IE if available.
+
+If the Common Measurement Type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was “UTRAN GPS Timing of Cell Frames for UE Positioning”, then the RNC2 shall include in the *TUTRAN-GPS Measurement Value Information* IE the *TUTRAN-GPS Quality* IE and the *TUTRAN-GPS Drift Rate Quality* IE, if available.
+
+If the Common Measurement Type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was “UTRAN GANSS Timing of Cell Frames for UE Positioning”, then the RNC2 shall include in the *TUTRAN-GANSS Measurement Value Information* IE the *TUTRAN-GANSS Quality* IE and the *TUTRAN-GANSS Drift Rate Quality* IE, if available.
+
+##### 8.5.3.2.1 Successful Operation for Iur-g
+
+If the requested measurement reporting criteria are met, the RNC2/BSS2 shall initiate a Measurement Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications.
+
+The *Common Measurement ID* IE shall be set to the Common Measurement ID provided by RNC1/BSS1 when initiating the measurement with the Common Measurement Initiation procedure.
+
+If the Common measurement type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was “SFN-SFN Observed Time Difference”, then RNC2 shall include in the COMMON MEASUREMENT REPORT all the available measurements in the *Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information* IE and shall include the neighbouring cells with no measurement result available in the *Unsuccessful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information* IE.
+
+If the Common measurement type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was not set to “SFN-SFN Observed Time Difference” and the SFN Reporting Indicator when initiating the measurement was set to “FN Reporting Required”, the RNC2 shall include the *SFN* IE in the COMMON MEASUREMENT REPORT message. The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the *Common Measurement Type* IE is set to “SFN-SFN Observed Time Difference”, then the *SFN Reporting Indicator* IE is ignored.
+
+#### 8.5.3.3 Abnormal Conditions
+
+-
+
+### 8.5.4 Common Measurement Termination
+
+#### 8.5.4.1 General
+
+This procedure is used by an RNC to terminate a measurement previously requested by the Common Measurement Initiation procedure.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.4.2 Successful Operation
+
+
+
+A sequence diagram showing the interaction between RNC1 and RNC2. RNC1 sends a message labeled "COMMON MEASUREMENT TERMINATION REQUEST" to RNC2. The message is represented by a horizontal arrow pointing from RNC1 to RNC2.
+
+Sequence diagram for Common Measurement Termination procedure, Successful Operation
+
+**Figure 30D: Common Measurement Termination procedure, Successful Operation**
+
+This procedure is initiated with a COMMON MEASUREMENT TERMINATION REQUEST message.
+
+Upon receipt, RNC2 shall terminate reporting of common measurements corresponding to the received *Measurement ID* IE.
+
+##### 8.5.4.2.1 Successful Operation for Iur-g
+
+The RNC1/BSS1 and RNC2/BSS2 shall use the Common Measurement Termination procedure as specified in section 8.5.4.2.
+
+#### 8.5.4.3 Abnormal Conditions
+
+-
+
+### 8.5.5 Common Measurement Failure
+
+#### 8.5.5.1 General
+
+This procedure is used by an RNC to notify another RNC that a measurement previously requested by the Common Measurement Initiation procedure can no longer be reported.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.5.2 Successful Operation
+
+
+
+A sequence diagram showing the interaction between RNC1 and RNC2. RNC2 sends a message labeled "COMMON MEASUREMENT FAILURE INDICATION" to RNC1. The message is represented by a horizontal arrow pointing from RNC2 to RNC1.
+
+Sequence diagram for Common Measurement Failure procedure, Successful Operation
+
+**Figure 30E: Common Measurement Failure procedure, Successful Operation**
+
+This procedure is initiated with a COMMON MEASUREMENT FAILURE INDICATION message, sent from RNC2 to RNC1 to inform the RNC1 that a previously requested measurement can no longer be reported. RNC2 has locally terminated the indicated measurement. The RNC2 shall include in the COMMON MEASUREMENT FAILURE INDICATION message the reason for the failure in the *Cause* IE.
+
+##### 8.5.5.2.1 Successful Operation for lur-g
+
+The RNC1/BSS1 and RNC2/BSS2 shall use the Common Measurement Failure procedure as specified in section 8.5.5.2.
+
+#### 8.5.5.3 Abnormal Conditions
+
+-
+
+### 8.5.6 Information Exchange Initiation
+
+#### 8.5.6.1 General
+
+This procedure is used by an RNC to request the initiation of an information exchange with another RNC.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.6.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC1: RNC1
+ Note right of RNC2: RNC2
+ RNC1->>RNC2: INFORMATION EXCHANGE INITIATION REQUEST
+ RNC2-->>RNC1: INFORMATION EXCHANGE INITIATION RESPONSE
+
+```
+
+Sequence diagram showing the Information Exchange Initiation procedure between RNC1 and RNC2. RNC1 sends an INFORMATION EXCHANGE INITIATION REQUEST to RNC2, and RNC2 responds with an INFORMATION EXCHANGE INITIATION RESPONSE.
+
+**Figure 30F: Information Exchange Initiation procedure, Successful Operation**
+
+The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from RNC1 to RNC2.
+
+Upon receipt, the RNC2 shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications.
+
+If the *Information Exchange Object Type* IE is set to “MBMS Bearer Service” and the *Information Type Item* IE is set to “MBMS Bearer Service Full Address”, the RNC2 shall report for each TMGI included in the received *MBMS Bearer Service Identifiers List* IE, the Access Point Name and the IP Multicast Address corresponding to this TMGI in the *MBMS Bearer Service Identifiers List* IE in the INFORMATION EXCHANGE INITIATION RESPONSE message.
+
+[FDD – If the *Information Exchange Object Type* IE is set to “MBMS Bearer Service in MBMS Cell” and the *Information Type Item* IE is set to “MBMS Counting Information”, the RNC2 shall perform counting in cells as defined in TS 25.346 [50] and report in the *Counting Result* IE for each TMGI included in the received *MBMS Bearer Service Identifiers List* IE for each cell included in the received *MBMS Cell List* IE either the counting information or, if relevant counting information is not available in RNC2 (TS 25.346 [50]), the value “0” in the INFORMATION EXCHANGE INITIATION RESPONSE message.]
+
+[FDD – If the *Information Exchange Object Type* IE is set to “MBMS Bearer Service in MBMS Cell” and the *Information Type Item* IE is set to “MBMS Transmission Mode”, the RNC2 shall report for each TMGI included in the received *MBMS Bearer Service Identifiers List* IE for each cell included in the received *MBMS Cell List* IE, the transmission mode for each TMGI in the cells of RNC2 that have a neighbour relation to the cells received in *MBMS Cell List* IE as defined in TS 25.346 [50] in the INFORMATION EXCHANGE INITIATION RESPONSE message. If no cells of RNC2 have a neighbour relation to a cell received in *MBMS Cell List* IE for a TMGI the value “Not Provided” shall be used.]
+
+[FDD – If the *Information Exchange Object Type* IE is set to “MBMS Cell” and the *Information Type Item* IE is set to “MBMS Neighbouring Cell Information”, the RNC2 shall report for each cell included in the received *MBMS Cell List* IE, the MBMS radio bearer information for each cells in the INFORMATION EXCHANGE INITIATION RESPONSE message.]
+
+[FDD – If the *Information Exchange Object Type* IE is set to “MBMS Bearer Service in MBMS Cell” and the *Information Type Item* IE is set to “MBMS RLC Sequence Number”, the RNC2 shall report for each TMGI included in the received *MBMS Bearer Service Identifiers List* IE for each cell included in the received *MBMS Cell List* IE, the
+
+RLC sequence number for each TMGI for the indicated cells in the INFORMATION EXCHANGE INITIATION RESPONSE message.]
+
+If the *Information Exchange Object Type* IE is set to “ANR Cell” and the *Information Type Item* IE is set to “ANR Cell Information”, the RNC2 shall, if supported, for each cell in the *ANR Cell List* IE that is controlled by RNC2, report the ANR Cell Information in the INFORMATION EXCHANGE INITIATION RESPONSE message.
+
+If the *Information Type* IE contains a *GANSS Generic Data* IE, at least one of the *GANSS Navigation Model And Time Recovery*, *GANSS Time Model GNSS-GNSS*, *GANSS UTC Model*, *GANSS Almanac*, *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *GANSS Additional Navigation Models And Time Recovery*, *GANSS Additional UTC Models*, *GANSS Auxiliary Information* IEs shall be present in the *GANSS Generic Data* IE.
+
+- If the *GANSS Generic Data* IE does not contain the *GANSS ID* IE, the RNC2 shall assume that the corresponding GANSS is “Galileo”.
+
+If the *Information Exchange Object Type* IE is set to “Common E-RGCH Cell” and the *Information Type Item* IE is set to “Common E-RGCH Cell Information”, the RNC2 shall, for each Common E-RGCH capable cell in the *Common E-RGCH Cell List* IE that is controlled by RNC2, report the Common E-RGCH Cell Information in the INFORMATION EXCHANGE INITIATION RESPONSE message.
+
+##### Information Report Characteristics:
+
+The *Information Report Characteristics* IE indicates how the reporting of the information shall be performed.
+
+If the *Information Report Characteristics* IE is set to “On Demand”, the RNC2 shall report the requested information immediately.
+
+If the *Information Report Characteristics* IE is set to “Periodic”, the RNC2 shall report the requested information immediately and then shall periodically initiate the Information Reporting procedure for all the requested information, with the report frequency indicated by the *Information Report Periodicity* IE.
+
+If the *Information Report Characteristics* IE is set to “On Modification”, the RNC2 shall report the requested information immediately if available. If the requested information is not available at the moment of receiving the INFORMATION EXCHANGE INITIATION REQUEST message, but expected to become available after some acquisition time, the RNC2 shall initiate the Information Reporting procedure when the requested information becomes available. The RNC2 shall then initiate the Information Reporting procedure in accordance to the following conditions:
+
+- If the *Information Type Item* IE is set to “IPDL Parameters”, the RNC2 shall initiate the Information Reporting procedure when any change in the parameters occurs.
+- If the *Information Type Item* IE is set to “DGPS Corrections”, the RNC2 shall initiate the Information Reporting procedure for this specific Information Type when either the PRC has drifted from the previously reported value more than the threshold indicated in the *PRC Deviation* IE in the *Information Threshold* IE or a change has occurred in the IODE.
+- If the *Information Type Item* IE is set to “GPS Information” and the *GPS Information Item* IE includes “GPS Navigation Model & Recovery Assistance”, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred regarding either the IODC or the list of visible satellites, identified by the *Sat ID* IEs.
+- If the *Information Type Item* IE is set to “GPS Information” and the *GPS Information Item* IE includes “GPS Ionospheric Model”, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred.
+- If the *Information Type Item* IE is set to “GPS Information” and the *GPS Information Item* IE includes “GPS UTC Model”, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred in the $t_{ot}$ or $WN_t$ parameter.
+- If the *Information Type Item* IE is set to “GPS Information” and the *GPS Information Item* IE includes “GPS Almanac”, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when a change in the $t_{oa}$ or $WN_a$ parameter has occurred.
+- If the *Information Type Item* IE is set to “GPS Information” and the *GPS Information Item* IE includes “GPS Real-Time Integrity”, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred.
+
+- If the *Information Type* IE is set to “Cell Capacity Class”, the RNC2 shall initiate the Information Reporting procedure for uplink and downlink cell capacity class when any change has occurred. If either uplink or downlink cell capacity class satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink cell capacity information.
+- If any of the above *Information Type* IEs becomes temporarily unavailable, the RNC2 shall initiate the Information Reporting procedure for this specific Information Item by indicating “Information Not Available” in the *Requested Data Value Information* IE. If the Information becomes available again, the RNC2 shall initiate the Information Reporting procedure for this specific Information.
+- If the *Information Type* IE is set to “NACC related data”, the RNC2 shall initiate the Information Reporting procedure for NACC related data if any change has occurred.
+- If the *Information Type* IE is set to “Inter-frequency Cell Information”, the RNC2 shall initiate the Information Reporting procedure for this specific Information Item when any change has occurred to the inter-frequency cell information broadcasted in the SIB11 or SIB12.
+- If the *Information Type Item* IE is set to “DGANSS Corrections”, the RNC2 shall initiate the Information Reporting procedure for this specific Information Type when either the PRC has drifted from the previously reported value more than the threshold indicated in the *PRC Deviation* IE in the *Information Threshold* IE or a change has occurred in the IODE.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Navigation Model And Time Recovery* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the *Sat ID* IEs.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Ionospheric Model* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS UTC Model* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change has occurred in the $t_{ot}$ or $WN_t$ parameter.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Almanac* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change in the $T_{oa}$ , $IOD_{as}$ , or Week Number parameter has occurred.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Real Time Integrity* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Data Bit Assistance* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred.
+- If the *Information Type Item* IE is set to “MBMS Transmission Mode”, the RNC2 shall initiate the Information Reporting procedure when any change in the parameter occurs.
+- If the *Information Type Item* IE is set to “MBMS Neighbouring Cell Information”, the RNC2 shall initiate the Information Reporting procedure when any change in the parameters occurs.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Additional Navigation Models And Time Recovery* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the *Sat ID* IEs.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Additional Ionospheric Model* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Additional UTC Models* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the $t_{ot}$ , $WN_{ot}$ , $WN_t$ , or $N^A$ parameter.
+
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Earth Orientation Parameters* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the *tEOP* parameter.
+- If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Auxiliary Information* IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the *Signals Available* or *Channel Number* IE parameter.
+- If the *Information Type Item* IE is set to “Common E-RGCH Cell Information”, the RNC2 shall initiate the Information Reporting procedure for this Common E-RGCH Information item when a change has occurred in the *Common E-RGCH Cell Information* IE parameter for the specific cell.
+
+##### Response message:
+
+If the RNC2 is able to determine the information requested by the RNC1, it shall respond with the INFORMATION EXCHANGE INITIATION RESPONSE message. The message shall include the *Information Exchange ID* IE set to the same value that was included in the INFORMATION EXCHANGE INITIATION REQUEST message. When the *Report Characteristics* IE is set to or “On Modification” or “Periodic”, the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the *Requested Data Value* IE if the data are available. When the *Report Characteristics* IE is set to “On Demand”, the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the *Requested Data Value* IE.
+
+If the *Requested DataValue* IE contains the *GANSS Common Data* IE, at least one of the *GANSS Ionospheric Model*, *GANSS RX Pos*, *GANSS Additional Ionospheric Model*, or *GANSS Earth Orientation Parameters* IEs shall be present.
+
+Any *GANSS Generic Data* IE associated with a given GANSS included in the *Requested DataValue* IE shall contain at least one of the *DGANSS Corrections*, *GANSS Navigation Model And Time Recovery*, *GANSS Time Model*, *GANSS UTC Model*, *GANSS Almanac*, *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *GANSS Additional Time Models*, *GANSS Additional Navigation Models And Time Recovery*, *GANSS Additional UTC Models*, or *GANSS Auxiliary Information* IEs.
+
+- If the *GANSS Generic Data* IE does not contain the *GANSS ID* IE, the corresponding GANSS is “Galileo”.
+- The *DGANSS Corrections* IE contains one or several *DGANSS Information* IE(s), each of them associated with a GANSS Signal. A *DGANSS Information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [16], clause 10.3.3.45a.
+- The *GANSS Real Time Integrity* IE contains one or several *Satellite Information* IEs, each of them associated with a satellite and a GANSS Signal. A *Satellite Information* IE for a particular GANSS that does not contain the *Bad GANSS Signal ID* IE is by default associated with all the signals of the corresponding satellite (see [53], IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], DTFA01-96-C-00025 [58], IS-QZSS [59], [60]).
+
+If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Time Model GNSS-GNSS* IE with exactly one bit set to value “1”, the RNC2 shall include the *GANSS Time Model* IE in the *Requested Data Value* IE with the requested time information.
+
+If the *Information Type Item* IE is set to “GANSS Information” and the *GANSS Information* IE includes the *GANSS Time Model GNSS-GNSS* IE with more than one bit set to value “1”, the RNC2 shall include the *GANSS Additional Time Models* IE in *Requested Data Value* IE with the requested time information for each GANSS.
+
+If the *Information Type Item* IE is set to “DGPS Corrections”, the RNC2 shall include the *DGPS Corrections* IE in *Requested Data Value* IE with the *DGNSS Validity Period* IE included, if available.
+
+If the *Information Type Item* IE is set to “DGANSS Corrections”, the RNC2 shall include the *DGANSS Corrections* IE in *Requested Data Value* IE with the *DGNSS Validity Period* IE included, if available.
+
+If the *Information Type Item* IE is set to “GPS Almanac”, the RNC2 shall include the *GPS Almanac* IE in *Requested Data Value* IE with the *Complete Almanac Provided* IE included, if available.
+
+If the *Information Type Item* IE is set to “GANSS Almanac”, the RNC2 shall include the *GANSS Almanac* IE in *Requested Data Value* IE with the *Complete Almanac Provided* IE included, if available.
+
+If the *Information Type Item* IE is set to “GANSS Time Model GNSS-GNSS”, the RNC2 shall include the *GANSS Time Model* IE in *Requested Data Value* IE with the *Delta\_T* IE included, if available.
+
+##### 8.5.6.2.1 Successful Operation for Iur-g
+
+The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from BSS1 to BSS2/RNC2 or by RNC1 to BSS2.
+
+Upon receipt, the BSS2/RNC2 shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications.
+
+###### Information Report Characteristics on Iur-g:
+
+If the *Information Type Item* IE is set to “Cell Capacity Class”, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.6.2.
+
+The *Information Report Characteristics* IE indicates how the reporting of the information shall be performed. This IE is used as described in section 8.5.6.2.
+
+#### 8.5.6.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC1: RNC1
+ Note right of RNC2: RNC2
+ RNC1->>RNC2: INFORMATION EXCHANGE INITIATION REQUEST
+ RNC2-->>RNC1: INFORMATION EXCHANGE INITIATION FAILURE
+
+```
+
+Sequence diagram showing the Information Exchange Initiation procedure for Unsuccessful Operation between RNC1 and RNC2. RNC1 sends an INFORMATION EXCHANGE INITIATION REQUEST to RNC2. RNC2 responds with an INFORMATION EXCHANGE INITIATION FAILURE message back to RNC1.
+
+**Figure 30G: Information Exchange Initiation procedure, Unsuccessful Operation**
+
+If the requested Information Type received in the *Information Type* IE indicates a type of information that RNC2 cannot provide, the RNC2 shall reject the Information Exchange Initiation procedure.
+
+If the requested information provision cannot be accessed, the RNC2 shall reject the procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+The message shall include the *Information Exchange ID* IE set to the same value that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the *Cause* IE set to an appropriate value.
+
+Typical cause values are as follows:
+
+##### Radio Network Layer Cause:
+
+- Information temporarily not available;
+- Information Provision not supported for the object.
+
+#### 8.5.6.4 Abnormal Conditions
+
+If the *Information Report Characteristics* IE is set to “On Modification”, and the *Information Type Item* IE is set to “DGPS Corrections”, but the *Information Threshold* IE is not received in the INFORMATION EXCHANGE INITIATION REQUEST message, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+If the *Information Exchange Object Type* IE is set to a value other than “GSM Cell” and the *Information Type Item* IE set to “NACC related data” the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+If the *Information Type Item* IE is set to the value “MBMS Bearer Service Full Address” and the *Information Exchange Object Type* IE is not set to “MBMS Bearer Service”, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+If the *Information Type Item* IE is set to the value “ANR Cell Information” and the *Information Exchange Object Type* IE is not set to “ANR Cell”, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+If the *Information Type Item* IE is set to the value “ANR Cell Information” and the *Information Exchange Object Type* IE is set to “ANR Cell”, but the RNC2 can only collect the “Requested Data Value” for the subset of the cells requested, RNC2 shall not reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION RESPONSE message with the information it could obtain.
+
+If the *Information Type Item* IE is set to the value “Common E-RGCH Cell Information” and the *Information Exchange Object Type* IE is not set to “Common E-RGCH Cell”, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+If the *Information Type Item* IE is set to the value “Common E-RGCH Cell Information” and the *Information Exchange Object Type* IE is set to “Common E-RGCH Cell”, but only the subset of the cells requested are Common E-RGCH capable, the RNC2 shall not reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION RESPONSE message with the information it could obtain.
+
+The allowed combinations of the Information type and Information Report Characteristics type are shown in the table below marked with “X”. For not allowed combinations, the RNC2 shall reject the Information Exchange Initiation procedure using the INFORMATION EXCHANGE INITIATION FAILURE message.
+
+**Table 6a: Allowed Information Type and Information Report Characteristics type combinations**
+
+| Type | Information Report Characteristics Type | | |
+|-------------------------------------------------------|-----------------------------------------|----------|-----------------|
+| | On Demand | Periodic | On Modification |
+| UTRAN Access Point Position with Altitude Information | X | | |
+| UTRAN Access Point Position | X | | |
+| IPDL Parameters | X | X | X |
+| GPS Information | X | X | X |
+| DGPS Corrections | X | X | X |
+| GPS RX Pos | X | | |
+| SFN-SFN Measurement Reference Point Position | X | | |
+| Cell Capacity Class | X | | X |
+| NACC related data | X | | X |
+| MBMS Bearer Service Full Address | X | | |
+| Inter-frequency Cell Information | X | | X |
+| GANSS Information | X | X | X |
+| DGANSS Corrections | X | X | X |
+| GANSS RX Pos | X | | |
+| MBMS Counting Information [FDD only] | X | | |
+| MBMS Transmission Mode [FDD only] | | | X |
+| MBMS Neighbouring Cell Information [FDD only] | X | | X |
+| MBMS RLC Sequence Number [FDD only] | X | | |
+| ANR Cell Information | X | | |
+| Common E-RGCH Cell Information | X | | X |
+
+##### 8.5.6.4.1 Abnormal Conditions for Iur-g
+
+The information types that can be requested on the Iur and Iur-g interfaces are shown in the table below marked with “X”. For information types that are not applicable on the Iur-g interface, the BSS shall reject the Information Exchange Initiation procedure.
+
+**Table 7: Allowed Information types on Iur and Iur-g interfaces**
+
+| Information Type | Interface | |
+|-------------------------------------------------------|-----------|-------|
+| | lur | lur-g |
+| UTRAN Access Point Position with Altitude Information | X | |
+| UTRAN Access Point Position | X | |
+| IPDL Parameters | X | |
+| DGPS Corrections | X | |
+| GPS Information | X | |
+| GPS RX Pos | X | |
+| SFN-SFN Measurement Reference Point Position | X | |
+| Cell Capacity Class | X | X |
+| NACC related data | X | |
+| MBMS Bearer Service Full Address | X | |
+| Inter-frequency Cell Information | X | |
+| DGANSS Corrections | X | |
+| GANSS Information | X | |
+| GANSS RX Pos | X | |
+| MBMS Counting Information [FDD only] | X | |
+| MBMS Transmission Mode [FDD only] | X | |
+| MBMS Neighbouring Cell Information [FDD only] | X | |
+| MBMS RLC Sequence Number [FDD only] | X | |
+
+### 8.5.7 Information Reporting
+
+#### 8.5.7.1 General
+
+This procedure is used by a RNC to report the result of information requested by another RNC using the Information Exchange Initiation.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.7.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note right of RNC2: INFORMATION REPORT
+ RNC2->>RNC1: INFORMATION REPORT
+
+```
+
+Sequence diagram showing the Information Reporting procedure. RNC2 sends an INFORMATION REPORT message to RNC1.
+
+**Figure 30H: Information Reporting procedure, Successful Operation**
+
+If the requested information reporting criteria are met, the RNC2 shall initiate an Information Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications.
+
+The *Information Exchange ID* IE shall be set to the Information Exchange ID provided by the RNC1 when initiating the information exchange with the Information Exchange Initiation procedure.
+
+The *Requested Data Value* IE shall include at least one IE containing the data to be reported.
+
+##### 8.5.7.2.1 Successful Operation for lur-g
+
+The RNC1/BSS1 and RNC2/BSS2 shall use the Information Reporting procedure as specified in section 8.5.7.2.
+
+#### 8.5.7.3 Abnormal Conditions
+
+-
+
+### 8.5.8 Information Exchange Termination
+
+#### 8.5.8.1 General
+
+This procedure is used by a RNC to terminate the information exchange requested using the Information Exchange Initiation.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.8.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note right of RNC1: INFORMATION EXCHANGE TERMINATION REQUEST
+ RNC1->>RNC2: INFORMATION EXCHANGE TERMINATION REQUEST
+```
+
+Sequence diagram for Information Exchange Termination procedure, Successful Operation. RNC1 sends an INFORMATION EXCHANGE TERMINATION REQUEST message to RNC2.
+
+**Figure 30I: Information Exchange Termination procedure, Successful Operation**
+
+This procedure is initiated with a INFORMATION EXCHANGE TERMINATION REQUEST message.
+
+Upon receipt, the RNC2 shall terminate the information exchange corresponding to the *Information Exchange ID* IE provided by the RNC1 when initiating the information exchange with the Information Exchange Initiation procedure.
+
+##### 8.5.8.2.1 Successful Operation for Iur-g
+
+The RNC1/BSS1 and RNC2/BSS2 shall use the Information Exchange Termination procedure as specified in section 8.5.8.2.
+
+#### 8.5.8.3 Abnormal Conditions
+
+-
+
+### 8.5.9 Information Exchange Failure
+
+#### 8.5.9.1 General
+
+This procedure is used by a RNC to notify another that the information exchange it previously requested using the Information Exchange Initiation can no longer be reported.
+
+This procedure uses the signalling bearer connection for the relevant Distant RNC Context.
+
+#### 8.5.9.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC2: INFORMATION EXCHANGE FAILURE INDICATION
+ RNC2->>RNC1: INFORMATION EXCHANGE FAILURE INDICATION
+```
+
+Sequence diagram for Information Exchange Failure procedure, Successful Operation. RNC2 sends an INFORMATION EXCHANGE FAILURE INDICATION message to RNC1.
+
+**Figure 30J: Information Exchange Failure procedure, Successful Operation**
+
+This procedure is initiated with a INFORMATION EXCHANGE FAILURE INDICATION message, sent from the RNC2 to the RNC1, to inform the RNC1 that information previously requested by the Information Exchange Initiation procedure can no longer be reported. The RNC2 shall include in the INFORMATION EXCHANGE FAILURE INDICATION message the *Information Exchange ID* IE set to the same value provided by the RNC1 when initiating the information exchange with the Information Exchange Initiation procedure, and the RNC2 shall include the *Cause* IE set to an appropriate value.
+
+Typical cause values are as follows:
+
+**Radio Network Layer Cause:**
+
+Information temporarily not available.
+
+##### 8.5.9.2.1 Successful Operation for Iur-g
+
+The RNC1/BSS1 and RNC2/BSS2 shall use the Information Exchange Failure procedure as specified in section 8.5.9.2.
+
+### 8.5.10 Reset
+
+#### 8.5.10.1 General
+
+The purpose of the reset procedure is to align the resources in RNC1 and RNC2 in the event of an abnormal failure.
+
+The procedure uses connectionless signalling.
+
+#### 8.5.10.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC1: RNC1
+ RNC1->>RNC2: RESET REQUEST
+ Note right of RNC2: RNC2
+ RNC2-->>RNC1: RESET RESPONSE
+
+```
+
+Sequence diagram of the Reset procedure. RNC1 sends a RESET REQUEST to RNC2, and RNC2 responds with a RESET RESPONSE.
+
+**Figure 30K: Reset procedure, Successful Operation**
+
+The procedure is initiated with a RESET REQUEST message sent from the RNC1 to the RNC2.
+
+If the *Reset Indicator* IE is set to “Context”, then:
+
+- For all indicated UE Contexts identified by the *S-RNTI* IE, the RNC2 in the role of DRNC, shall remove all the indicated UE Contexts and all the radio resources allocated for these UE Contexts. In addition, the RNC2 shall take actions according to Annex D.2.
+- For all indicated UE Contexts identified by the *D-RNTI* IE, the RNC2 in the role of SRNC, shall remove the information related to the RNC1 for all indicated UE Contexts and the radio resources allocated for these UE Contexts.
+
+If the *Reset Indicator* IE is set to “Context Group”, then:
+
+- For all indicated UE Context Groups identified by the *S-RNTI Group* IE, the RNC2 in the role of DRNC, shall remove all the indicated UE Contexts and all the radio resources allocated for these UE Contexts. In addition, the RNC2 shall take actions according to Annex D.2.
+
+If the *Reset Indicator* IE is set to “All Contexts”, then the RNC2 shall:
+
+- In the role of DRNC, remove all the UE Contexts for which the RNC1 is the SRNC and all the radio resources allocated for these UE Contexts. In addition, the RNC2 shall take actions according to Annex D.2.
+- In the role of SRNC, remove the information related to the RNC1 for all the UE Contexts and all the radio resources allocated for these UE Contexts.
+
+For all the removed UE Contexts and for all the UE Contexts for which the RNC2 has removed information related to the RNC1, the RNC2 shall also initiate release of the dedicated or common user plane resources that were involved in these UE Contexts. After clearing all related resources, the RNC2 shall return the RESET RESPONSE message to the RNC1.
+
+#### 8.5.10.3 Abnormal Conditions
+
+If the RESET message is received, any other ongoing procedure (except another Reset procedure) on same Iur interface related to a context indicated explicitly or implicitly in the message shall be aborted.
+
+### 8.5.11 Direct Information Transfer
+
+#### 8.5.11.1 General
+
+This procedure is used by an RNC to transfer information to another RNC spontaneously.
+
+This procedure shall use the connectionless mode of signalling bearer.
+
+#### 8.5.11.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note left of RNC1: DIRECT INFORMATION TRANSFER
+ RNC1->>RNC2: DIRECT INFORMATION TRANSFER
+
+```
+
+Diagram illustrating the Direct Information Transfer procedure. RNC1 sends a DIRECT INFORMATION TRANSFER message to RNC2.
+
+**Figure 30L: Direct Information Transfer procedure, Successful Operation**
+
+The procedure is initiated with an DIRECT INFORMATION TRANSFER message sent from RNC1 to RNC2.
+
+If the initiating RNC of this procedure is RNC1, RNC1 shall provide appropriate information in the *Provided Information IE*.
+
+##### MBMS Channel Type Indication:
+
+At the start time of a session for an MBMS bearer service, if the RNC1 is in the DRNC role for some Ues whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC2 and if the channel type is determined by the RNC1 for certain cells in the DRNS, the procedure shall be initiated by the RNC1 to the RNC2. In this case, the RNC1 shall include in the *Provided Information IE* the *Channel Type Information IE* in the DIRECT INFORMATION TRANSFER message.
+
+During a session of an MBMS bearer service, if the RNC1 is in the DRNC role for some Ues whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC2, then the RNC1 may initiate this procedure to indicate channel type change for the MBMS bearer service in certain cells. In this case, the RNC1 shall include in the *Provided Information IE* the *Channel Type Information IE* in the DIRECT INFORMATION TRANSFER message.
+
+The RNC1 shall include the available information within the *PTM Cell List IE*, the *PTP Cell List IE* and/or the *Not Provided Cell List IE* in the *Channel Type Information IE*.
+
+##### MBMS Preferred Frequency Layer Indication:
+
+At the start time of a session for an MBMS bearer service, if the RNC1 is in the DRNC role for at least one CELL\_DCH UE whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC2 and if the preferred frequency layer is determined by the RNC1 for certain cells that host at least one of these CELL\_DCH Ues whose SRNC is RNC2, the procedure shall be initiated by the RNC1 to the RNC2. In this case, the RNC1 shall include in the *Provided Information IE* the *Preferred Frequency Layer Information IE* in the DIRECT INFORMATION TRANSFER message.
+
+If some of the cells controlled by RNC1 that host at least one of these CELL\_DCH Ues whose SRNC is RNC2 are configured with different preferred frequencies, the *Additional Preferred Frequency IE* as well as *Default Preferred Frequency IE* shall be included in the *Preferred Frequency Layer Information IE*. In this case, for each preferred frequency different from the *Default Preferred Frequency IE*, one *Additional Preferred Frequency IE* shall be included containing at least one *Corresponding Cells IE*.
+
+##### ANR Report Indication:
+
+The message contains *ANR Report Indication IE* if the initiating RNC (RNC1) has decided to forward a logged ANR report received over Uu to RNC2. On reception of the *ANR Report Indication IE*, RNC2 may use the information to configure neighbour relations.
+
+### 8.5.12 Information Transfer Control
+
+#### 8.5.12.1 General
+
+This procedure is used by an RNC to control transfer of information (e.g. log information related to ANR) from an RNC to any other RNC. This procedure is initiated by an RNC to suspend or resume transfer of information.
+
+This procedure shall use the connectionless mode of signalling bearer.
+
+#### 8.5.12.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant RNC1
+ participant RNC2
+ Note right of RNC1: INFORMATION TRANSFER CONTROL REQUEST
+ RNC1->>RNC2: INFORMATION TRANSFER CONTROL REQUEST
+```
+
+Sequence diagram for Figure 30M: Information Transfer Control procedure, Successful Operation. It shows two vertical lifelines labeled RNC1 and RNC2. A horizontal arrow points from RNC1 to RNC2, with the text 'INFORMATION TRANSFER CONTROL REQUEST' centered above it.
+
+**Figure 30M: Information Transfer Control procedure, Successful Operation**
+
+The RNC1 initiates the procedure by sending the INFORMATION TRANSFER CONTROL REQUEST message to the RNC2.
+
+The *Control Type* IE within the INFORMATION TRANSFER CONTROL REQUEST message shall be used to either suspend or to resume (respectively indicated by *Suspension* IE or *Resume* IE in *Control Type* IE) the transfer of information for the specified scope of objects indicated by *Controlled Object Scope* IE.
+
+If the control of information transfer is intended for individual cells, those cells shall be indicated in the *UMTS Cell Information* IE within the *Controlled Object Scope* IE. If the *UMTS Cell Information* IE is not included, the procedure is intended for the whole entity indicated in *RNC-ID* IE or *Extended RNC-ID* IE. In shared network configurations, PLMN identities shall be indicated with *Multiple PLMN List* IE.
+
+#### 8.5.12.3 Abnormal Conditions
+
+-
+
+## 8.6 MBMS Procedures
+
+### 8.6.1 MBMS Attach
+
+#### 8.6.1.1 General
+
+The MBMS Attach procedure is used by the SRNC to either create a UE Link/URA Link in the DRNC or inform the DRNC about any addition of one or several MBMS bearer services in an already stored UE Link or URA Link.
+
+This procedure shall use the signalling bearer mode specified below.
+
+#### 8.6.1.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note right of SRNC: MBMS ATTACH COMMAND
+ SRNC->>DRNC: MBMS ATTACH COMMAND
+```
+
+Sequence diagram for Figure 31: MBMS Attach procedure, Successful Operation. It shows two vertical lifelines labeled SRNC and DRNC. A horizontal arrow points from SRNC to DRNC, with the text 'MBMS ATTACH COMMAND' centered above it.
+
+**Figure 31: MBMS Attach procedure, Successful Operation**
+
+The SRNC initiates the procedure by sending the message MBMS ATTACH COMMAND message to the DRNC.
+
+When the UE is utilising one or more radio links in the DRNC, the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If the UE is not utilising any radio link, the message shall be sent using the connectionless service of the signalling bearer.
+
+If no *UE State* IE is included in the message or the *UE State* IE is set to “CELL\_FACH/CELL\_PCH”, the DRNC shall perform the UE Linking as specified in TS 25.346 [50], section 5.1.6.
+
+If the *UE State* IE is set to “URA\_PCH”, the DRNC shall perform the URA Linking as specified in TS 25.346 [50], section 5.1.10.
+
+#### 8.6.1.3 Abnormal Conditions
+
+-
+
+### 8.6.2 MBMS Detach
+
+#### 8.6.2.1 General
+
+The MBMS Detach procedure is used by the SRNC to either delete a UE Link/URA Link in the DRNC or to inform DRNC about any removal of one or several MBMS bearer services in an already stored UE link or URA Link.
+
+This procedure shall use the signalling bearer mode specified below.
+
+#### 8.6.2.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant SRNC
+ participant DRNC
+ Note left of SRNC: MBMS DETACH COMMAND
+ SRNC->>DRNC: MBMS DETACH COMMAND
+```
+
+Sequence diagram showing the MBMS Detach procedure. The SRNC sends an MBMS DETACH COMMAND message to the DRNC.
+
+**Figure 32: MBMS Detach procedure, Successful Operation**
+
+The SRNC initiates the procedure by sending the message MBMS DETACH COMMAND message to the DRNC.
+
+When the UE is utilising one or more radio links in the DRNC, the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If the UE is not utilising any radio link, the message shall be sent using the connectionless service of the signalling bearer.
+
+If no *UE State* IE is included in the message or the *UE State* IE is set to “CELL\_FACH/CELL\_PCH”, the DRNC shall perform the UE De-linking as specified in TS 25.346 [50], section 5.1.6.
+
+If the *UE State* IE is set to “URA\_PCH”, the DRNC shall perform the URA De-linking as specified in TS 25.346 [50], section 5.1.10.
+
+#### 8.6.2.3 Abnormal Conditions
+
+-
+
+# --- 9 Elements for RNSAP Communication
+
+## 9.1 Message Functional Definition and Content
+
+### 9.1.1 General
+
+This subclause defines the structure of the messages required for the RNSAP protocol in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format
+
+in subclause 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, in which the tabular format shall take precedence.
+
+NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [28].
+
+### 9.1.2 Message Contents
+
+#### 9.1.2.1 Presence
+
+An information element can be of the following types:
+
+| | |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------|
+| M | IEs marked as Mandatory (M) shall always be included in the message. |
+| O | IEs marked as Optional (O) may or may not be included in the message. |
+| C | IEs marked as Conditional shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. |
+
+In the case of an Information Element group, the group is preceded by a name for the info group (in bold). It is also indicated how many times a group may be repeated in the message and whether the group is conditional. Each group may be also repeated within one message. The presence field of the Information Elements inside one group defines if the Information Element is mandatory, optional or conditional if the group is present.
+
+#### 9.1.2.2 Criticality
+
+Each information element or Group of information elements may have criticality information applied to it. Following cases are possible:
+
+| | |
+|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| – | No criticality information is applied explicitly. |
+| YES | Criticality information is applied. 'YES' is usable only for non-repeatable information elements. |
+| GLOBAL | The information element and all its repetitions together have one common criticality information. 'GLOBAL' is usable only for repeatable information elements. |
+| EACH | Each repetition of the information element has its own criticality information. It is not allowed to assign different criticality values to the repetitions. 'EACH' is usable only for repeatable information elements. |
+
+#### 9.1.2.3 Range
+
+The Range column indicates the allowed number of copies of repetitive IEs/IE groups.
+
+#### 9.1.2.4 Assigned Criticality
+
+This column provides the actual criticality information as defined in subclause 10.3.2, if applicable.
+
+### 9.1.3 RADIO LINK SETUP REQUEST
+
+#### 9.1.3.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------|--------------|-------|--------------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| SRNC-ID | M | | RNC-ID
9.2.1.50 | If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. | YES | reject |
+| S-RNTI | M | | 9.2.1.53 | If the Extended S-RNTI IE is included in the message, the S-RNTI IE shall be ignored. | YES | reject |
+| D-RNTI | O | | 9.2.1.24 | | YES | reject |
+| Allowed Queuing Time | O | | 9.2.1.2 | | YES | reject |
+| UL DPCH Information | | 1 | | | YES | reject |
+| >UL Scrambling Code | M | | 9.2.2.53 | | – | |
+| >Min UL Channelisation Code Length | M | | 9.2.2.25 | | – | |
+| >Max Number of UL DPDCHs | C – CodeLen | | 9.2.2.24 | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | For the UL. | – | |
+| >TFCS | M | | 9.2.1.63 | | – | |
+| >UL DPCCH Slot Format | M | | 9.2.2.52 | | – | |
+| >Uplink SIR Target | O | | Uplink SIR
9.2.1.69 | | – | |
+| >Diversity mode | M | | 9.2.2.8 | | – | |
+| >Not Used | O | | NULL | | – | |
+| >Not Used | O | | NULL | | – | |
+| >DPC Mode | O | | 9.2.2.12A | | YES | reject |
+| >UL DPDCH Indicator for E-DCH operation | O | | 9.2.2.52A | This IE may be present without the presence of the E-DPCH Information IE. | YES | reject |
+| DL DPCH Information | | 0..1 | | | YES | reject |
+| >TFCS | M | | 9.2.1.63 | | – | |
+| >DL DPCH Slot Format | M | | 9.2.2.9 | | – | |
+| >Number of DL Channelisation Codes | M | | 9.2.2.26A | | – | |
+| >TFCI Signalling Mode | M | | 9.2.2.46 | | – | |
+| >TFCI Presence | C-SlotFormat | | 9.2.1.55 | | – | |
+| >Multiplexing Position | M | | 9.2.2.26 | | – | |
+| >Power Offset Information | | 1 | | | – | |
+| >>PO1 | M | | Power Offset
9.2.2.30 | Power offset for the TFCI bits. | – | |
+| >>PO2 | M | | Power Offset
9.2.2.30 | Power offset for the TPC bits. | – | |
+| >>PO3 | M | | Power Offset | Power offset for the pilot | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| | | | 9.2.2.30 | bits. | | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|-----------------------|--------------------------|-----------------------------------|-----------------------|-------------|----------------------|
+| >FDD TPC Downlink Step Size | M | | 9.2.2.16 | | – | |
+| >Limited Power Increase | M | | 9.2.2.21A | | – | |
+| >Inner Loop DL PC Status | M | | 9.2.2.21a | | – | |
+| DCH Information | M | | DCH FDD Information 9.2.2.4A | | YES | reject |
+| RL Information | | 1.. | | | EACH | notify |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >C-ID | M | | 9.2.1.6 | | – | |
+| >First RLS Indicator | M | | 9.2.2.16A | | – | |
+| >Frame Offset | M | | 9.2.1.30 | | – | |
+| >Chip Offset | M | | 9.2.2.1 | | – | |
+| >Propagation Delay | O | | 9.2.2.33 | | – | |
+| >Diversity Control Field | C –
NotFirstRL | | 9.2.1.20 | | – | |
+| >Initial DL TX Power | O | | DL Power 9.2.1.21A | | – | |
+| >Primary CPICH Ec/No | O | | 9.2.2.32 | | – | |
+| >Not Used | O | | NULL | | – | |
+| >Transmit Diversity Indicator | C –
Diversity mode | | 9.2.2.48 | | – | |
+| >Enhanced Primary CPICH Ec/No | O | | 9.2.2.13I | | YES | ignore |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | YES | ignore |
+| >Delayed Activation | O | | 9.2.1.19Aa | | YES | reject |
+| >Cell Portion ID | O | | 9.2.2.E | | YES | ignore |
+| >RL specific E-DCH Information | O | | 9.2.2.35a | | YES | reject |
+| >E-DCH RL Indication | O | | 9.2.2.4E | | YES | reject |
+| >Extended Propagation Delay | O | | 9.2.2.33a | | YES | ignore |
+| >Synchronisation Indicator | O | | 9.2.2.45A | | YES | reject |
+| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.100 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.124 | | YES | ignore |
+| >F-TPICH Information | O | | 9.2.2.139 | | YES | ignore |
+| Transmission Gap Pattern Sequence Information | O | | 9.2.2.47A | | YES | reject |
+| Active Pattern Sequence Information | O | | 9.2.2.A | | YES | reject |
+| Permanent NAS UE Identity | O | | 9.2.1.73 | | YES | ignore |
+| DL Power Balancing Information | O | | 9.2.2.10A | | YES | ignore |
+| HS-DSCH Information | O | | HS-DSCH FDD Information 9.2.2.19a | | YES | reject |
+| HS-PDSCH RL ID | C –
InfoHSDS CH | | RL ID 9.2.1.49 | | YES | reject |
+| MBMS Bearer Service List | | 0.. | | | GLOBAL | notify |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| E-DPCH Information | | 0..1 | | | YES | reject |
+| >Maximum Set of E-DPCHs | M | | 9.2.2.24e | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------------------------------------------------|------------|-----------------------|---------------------------|------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >E-TFCS Information | M | | 9.2.2.4G | | – | |
+| >E-TTI | M | | 9.2.2.4J | | – | |
+| >E-DPCCH Power Offset | M | | 9.2.2.4K | | – | |
+| >E-RGCH 2-Index-Step Threshold | M | | 9.2.2.64 | | – | |
+| >E-RGCH 3-Index-Step Threshold | M | | 9.2.2.65 | | – | |
+| >HARQ Info for E-DCH | M | | 9.2.2.66 | | – | |
+| >HS-DSCH Configured Indicator | M | | 9.2.2.19C | | – | |
+| >Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.102 | | YES | ignore |
+| E-DCH FDD Information | C-EDCHInfo | | 9.2.2.4B | | YES | reject |
+| Serving E-DCH RL | O | | 9.2.2.38C | | YES | reject |
+| F-DPCH Information | | 0..1 | | | YES | reject |
+| >Power Offset Information | | 1 | | | – | |
+| >>PO2 | M | | Power Offset 9.2.2.30 | This IE shall be ignored by DRNS. | – | |
+| >FDD TPC Downlink Step Size | M | | 9.2.2.16 | | – | |
+| >Limited Power Increase | M | | 9.2.2.21A | | – | |
+| >Inner Loop DL PC Status | M | | 9.2.2.21a | | – | |
+| >F-DPCH Slot Format Support Request | O | | 9.2.2.86 | | YES | reject |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| Initial DL DPCH Timing Adjustment Allowed | O | | 9.2.2.21b | | YES | ignore |
+| DCH Indicator For E-DCH-HSDPA Operation | O | | 9.2.2.67 | | YES | reject |
+| Serving Cell Change CFN | O | | CFN 9.2.1.9 | | YES | reject |
+| Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.72 | | YES | reject |
+| Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.74 | | YES | reject |
+| Extended SRNC-ID | O | | Extended RNC-ID 9.2.1.50a | The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| Additional HS Cell Information RL Setup | | 0.. | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject |
+| >HS-PDSCH RL ID | M | | RL ID 9.2.1.49 | | – | |
+| >C-ID | M | | 9.2.1.6 | | – | |
+| >HS-DSCH Secondary Serving Information | M | | 9.2.2.19aa | | – | |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.137 | | YES | ignore |
+| Additional E-DCH Cell | | 0..1 | | For E-DCH | YES | reject |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|--------------------|-------------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Information RL Setup Req | | | | on multiple frequencies in this DRNS. | | |
+| >Multicell E-DCH Transport Bearer Mode | M | | 9.2.2.113 | | – | |
+| > Additional E-DCH Cell Information Setup | | 1.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>Additional E-DCH FDD Setup Information | M | | 9.2.2.110 | | - | |
+| Usefulness of Battery Optimization | O | | 9.2.2.127 | | YES | ignore |
+| UL CLTD Information | O | | 9.2.2.131 | | YES | reject |
+| Extended S-RNTI | O | | Extended RNTI 9.2.1.154 | The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. | YES | reject |
+
+| Condition | Explanation |
+|----------------|--------------------------------------------------------------------------------------------------------------|
+| CodeLen | The IE shall be present if Min UL Channelisation Code length IE equals to 4. |
+| SlotFormat | The IE shall be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16. |
+| NotFirstRL | The IE shall be present if the RL is not the first one in the RL Information IE. |
+| Diversity mode | The IE shall be present if Diversity Mode IE in UL DPCH Information IE is not equal to “none”. |
+| InfoHSDSCH | This IE shall be present if HS-DSCH Information IE is present. |
+| EDCHInfo | This IE shall be present if E-DPCH Information IE is present. |
+
+| Range bound | Explanation |
+|----------------------------|---------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+| maxNrOfMBMSServices | Maximum number of MBMS bearer services that a UE can join. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.3.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| SRNC-ID | M | | RNC-ID
9.2.1.50 | If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. | YES | reject |
+| S-RNTI | M | | 9.2.1.53 | If the Extended S-RNTI IE is included in the message, the S-RNTI IE shall be ignored. | YES | reject |
+| D-RNTI | O | | 9.2.1.24 | | YES | reject |
+| UL Physical Channel Information | | 1 | | | YES | reject |
+| >Maximum Number of Timeslots | M | | 9.2.3.3A | For the UL. | – | |
+| >Minimum Spreading Factor | M | | 9.2.3.4A | For the UL. | – | |
+| >Maximum Number of UL Physical Channels per Timeslot | M | | 9.2.3.3B | | – | |
+| >Support of 8PSK | O | | 9.2.3.7H | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >Minimum Spreading Factor 7.68Mcps | O | | 9.2.3.19 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| DL Physical Channel Information | | 1 | | | YES | reject |
+| >Maximum Number of Timeslots | M | | 9.2.3.3A | For the DL. | – | |
+| >Minimum Spreading Factor | M | | 9.2.3.4A | For the DL. | – | |
+| >Maximum Number of DL Physical Channels | M | | 9.2.3.3C | | – | |
+| >Maximum Number of DL Physical Channels per Timeslot | O | | 9.2.3.3D | | YES | ignore |
+| >Support of 8PSK | O | | 9.2.3.7H | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >Support of PLCCH | O | | 9.2.3.16 | Applicable to 1.28Mcps TDD only. | YES | ignore |
+
+| | | | | | | |
+|---------------------------------------------------------------|---|-----------------------------------|-------------------------------|-----------------------------------------------------------------------------|------|--------|
+| >Minimum Spreading Factor 7.68Mcps | O | | 9.2.3.19 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| >Maximum Number of DL Physical Channels 7.68Mcps | O | | 9.2.3.20 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| >Maximum Number of DL Physical Channels per Timeslot 7.68Mcps | O | | 9.2.3.21 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| Allowed Queuing Time | O | | 9.2.1.2 | | YES | reject |
+| UL CCTrCH Information | | 0..<max NrOfCCTrCHs> | | For DCH and USCH | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | M | | 9.2.1.63 | For the UL. | – | |
+| >TFCI Coding | M | | 9.2.3.11 | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | | – | |
+| >TDD TPC Uplink Step Size | O | | 9.2.3.10a | Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject |
+| DL CCTrCH Information | | 0..<max NrOfCCTrCHs> | | For DCH and DSCH. | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | M | | 9.2.1.63 | For the DL. | – | |
+| >TFCI Coding | M | | 9.2.3.11 | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | | – | |
+| >TDD TPC Downlink Step Size | M | | 9.2.3.10 | | – | |
+| >TPC CCTrCH List | | 0..<maxn oCCTrCHs> | | List of uplink CCTrCH which provide TPC. | – | |
+| >>TPC CCTrCH ID | M | | CCTrCH ID 9.2.3.2 | | – | |
+| DCH Information | O | | DCH TDD Information 9.2.3.2A | | YES | reject |
+| DSCH Information | O | | DSCH TDD Information 9.2.3.3a | | YES | reject |
+| USCH Information | O | | 9.2.3.15 | | YES | reject |
+| RL Information | | 1 | | | YES | reject |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >C-ID | M | | 9.2.1.6 | | – | |
+| >Frame Offset | M | | 9.2.1.30 | | – | |
+| >Special Burst Scheduling | M | | 9.2.3.7D | | – | |
+| >Primary CCPCH RSCP | O | | 9.2.3.5 | | – | |
+| >DL Time Slot ISCP Info | O | | 9.2.3.2D | Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | – | |
+| >DL Time Slot ISCP Info LCR | O | | 9.2.3.2F | Applicable to 1.28Mcps TDD only. | YES | reject |
+| >TSTD Support Indicator | O | | 9.2.3.13F | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | YES | ignore |
+
+| | | | | | | |
+|----------------------------------------------|----------------|----------------------------|-----------------------------------|-------------------------------------------------------------------------------------|--------|--------|
+| >Delayed Activation | O | | 9.2.1.19Aa | | YES | reject |
+| >UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject |
+| >>Uplink Synchronisation Step Size | M | | 9.2.3.13J | | – | |
+| >>Uplink Synchronisation Frequency | M | | 9.2.3.13I | | – | |
+| >Primary CCPCH RSCP Delta | O | | 9.2.3.5a | | YES | ignore |
+| >Idle Interval Configuration Indicator | O | | NULL | TDD only. | YES | ignore |
+| >Cell Portion LCR ID | O | | 9.2.3.73 | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| Permanent NAS UE Identity | O | | 9.2.1.73 | | YES | ignore |
+| HS-DSCH Information | O | | HS-DSCH TDD Information 9.2.3.3aa | | YES | reject |
+| HS-PDSCH RL ID | C – InfoHSDSCH | | RL ID 9.2.1.49 | | YES | reject |
+| PDSCH-RL-ID | O | | RL ID 9.2.1.49 | | YES | ignore |
+| MBMS Bearer Service List | | 0.. | | | GLOBAL | notify |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| E-DCH Information | | 0..1 | | 3.84Mcps TDD only. | YES | reject |
+| >E-PUCH Information | M | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | M | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.38 | | – | |
+| >E-DCH TDD Information | M | | 9.2.3.40 | | – | |
+| E-DCH Serving RL | O | | RL ID 9.2.1.49 | TDD only. | YES | reject |
+| E-DCH Information 7.68Mcps | | 0..1 | | 7.68Mcps TDD only. | YES | reject |
+| >E-PUCH Information | M | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | M | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.38 | | – | |
+| >E-DCH TDD Information 7.68Mcps | M | | 9.2.3.51 | | – | |
+| E-DCH Information 1.28Mcps | | 0..1 | | 1.28Mcps TDD only. | YES | reject |
+| >E-PUCH Information LCR | M | | 9.2.3.36a | | – | |
+| >E-TFCS Information TDD | M | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.38 | | – | |
+| >E-DCH TDD Information LCR | M | | 9.2.3.40a | | – | |
+| Extended SRNC-ID | O | | Extended RNC-ID 9.2.1.50a | The Extended SRNC-ID IE shall be used if the RNC identity has a value larger | YES | reject |
+
+| | | | | | | |
+|----------------------------------------------------|---|------|-------------------------|-----------------------------------------------------------------------------------------------------|-----|--------|
+| | | | | than 4095. | | |
+| Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.61 | 1.28 Mcps TDD only. | YES | reject |
+| HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.64 | 1.28 Mcps TDD only. | YES | reject |
+| E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.66 | 1.28 Mcps TDD only. | YES | reject |
+| RNTI Allocation Indicator | O | | ENUMERATED (True) | 1.28 Mcps TDD only. | YES | ignore |
+| DCH Measurement Type indicator | O | | 9.2.3.76 | 1.28 Mcps TDD only. | YES | reject |
+| Multi-Carrier E-DCH Information | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only. | YES | reject |
+| >Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.79 | 1.28 Mcps TDD only. | – | |
+| >Multi-Carrier E-DCH Information LCR | M | | 9.2.3.77 | 1.28 Mcps TDD only. | – | |
+| MU-MIMO Indicator | O | | 9.2.3.82 | 1.28 Mcps TDD only. | YES | reject |
+| Extended S-RNTI | O | | Extended RNTI 9.2.1.154 | The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. | YES | reject |
+
+| Condition | Explanation |
+|------------|-----------------------------------------------------------------------|
+| InfoHSDSCH | This IE shall be present if HS-DSCH Information IE is present. |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------|
+| maxNrOfCCTrCHs | Maximum number of CCTrCH for one UE. |
+| maxNrOfMBMSServices | Maximum number of MBMS bearer services that a UE can join. |
+
+### 9.1.4 RADIO LINK SETUP RESPONSE
+
+#### 9.1.4.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|-----------------|-----------------------------------|-------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| CN PS Domain Identifier | O | | 9.2.1.12 | | YES | ignore |
+| CN CS Domain Identifier | O | | 9.2.1.11 | | YES | ignore |
+| RL Information Response | | 1.. | | | EACH | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >RL Set ID | M | | 9.2.2.35 | | – | |
+| >URA Information | O | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >Received Total Wide Band Power | M | | 9.2.2.35A | | – | |
+| >Not Used | O | | NULL | | – | |
+| >DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | – | |
+| >CHOICE Diversity Indication | M | | | | – | |
+| >>Combining | | | | | – | |
+| >>>RL ID | M | | 9.2.1.49 | Reference RL ID for the combining. | – | |
+| >>>DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >>Non Combining or First RL | | | | | – | |
+| >>>DCH Information Response | M | | 9.2.1.16A | | – | |
+| >>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >SSDT Support Indicator | M | | 9.2.2.43 | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Closed Loop Timing Adjustment Mode | O | | 9.2.2.3A | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Primary Scrambling Code | O | | 9.2.1.45 | | – | |
+| >UL UARFCN | O | | UARFCN 9.2.1.66 | Corresponds to Nu in TS 25.104 [6]. | – | |
+| >DL UARFCN | O | | UARFCN 9.2.1.66 | Corresponds to Nd in TS 25.104 [6]. | – | |
+| >Primary CPICH Power | M | | 9.2.1.44 | | – | |
+| >Not Used | O | | NULL | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------|----------|---------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------|-------------|----------------------|
+| >PC Preamble | M | | 9.2.2.27a | | – | |
+| >SRB Delay | M | | 9.2.2.39A | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.15B | | YES | ignore |
+| >DL Power Balancing Activation Indicator | O | | 9.2.2.10B | | YES | ignore |
+| >HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >Primary CPICH Usage For Channel Estimation | O | | 9.2.2.32A | | YES | ignore |
+| >Secondary CPICH Information | O | | 9.2.2.38A | | YES | ignore |
+| >Active MBMS Bearer Service List | | 0..<maxNrOfActiveMBMSServices> | | | GLOBAL | ignore |
+| >>TMGI | M | | 9.2.1.80 | | – | |
+| >>Transmission Mode | O | | 9.2.1.81 | | – | |
+| >>Preferred Frequency Layer | O | | UARFCN
9.2.1.66 | | – | |
+| >E-DCH RL Set ID | O | | RL Set ID
9.2.2.35 | | YES | ignore |
+| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.4D | | YES | ignore |
+| >Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment
9.2.2.9A | | YES | ignore |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >Frame Offset | O | | 9.2.1.30 | | YES | ignore |
+| >Chip Offset | O | | 9.2.2.1 | | YES | ignore |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >HS-DSCH Preconfiguration Info | O | | 9.2.2.99 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.125 | | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| >F-TPICH Information Response | O | | 9.2.2.143 | | YES | ignore |
+| Uplink SIR Target | O | | Uplink SIR
9.2.1.69 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| HS-DSCH Information Response | O | | HS-DSCH FDD Information Response
9.2.2.19b | | YES | ignore |
+| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.75 | | YES | ignore |
+| SixtyfourQAM DL Support Indicator | O | | 9.2.1.123 | | YES | ignore |
+| Additional HS Cell Information Response | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore |
+| >HS-PDSCH RL ID | M | | RL ID
9.2.1.49 | | – | |
+| >HS-DSCH-RNTI | M | | 9.2.1.30P | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|---------------------------------|-----------------------|-------------------------------------------------------------------|-------------|----------------------|
+| >HS-DSCH FDD Secondary Serving Information Response | M | | 9.2.2.19ba | | – | |
+| >SixtyfourQAM DL Support Indicator | O | | 9.2.1.123 | | – | |
+| Additional E-DCH Cell Information Response | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | EACH | ignore |
+| >Additional E-DCH FDD Information Response | M | | 9.2.2.120 | | – | |
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.4.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------|----------|---------------------|-----------------------|------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| CN PS Domain Identifier | O | | 9.2.1.12 | | YES | ignore |
+| CN CS Domain Identifier | O | | 9.2.1.11 | | YES | ignore |
+| RL Information Response | | 0..1 | | Mandatory for 3.84Mcps TDD , not applicable to 1.28Mcps TDD or 7.68Mcps TDD. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >URA Information | O | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >UL Time Slot ISCP Info | M | | 9.2.3.13D | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >UARFCN | O | | 9.2.1.66 | Corresponds to Nt in TS 25.105 [7]. | – | |
+| >Cell Parameter ID | O | | 9.2.1.8 | | – | |
+| >Sync Case | O | | 9.2.1.54 | | – | |
+| >SCH Time Slot | C-Case2 | | 9.2.1.51 | | – | |
+| >SCTD Indicator | O | | 9.2.1.78 | | – | |
+| >PCCPCH Power | M | | 9.2.1.43 | | – | |
+| >Timing Advance Applied | M | | 9.2.3.12A | | – | |
+| >Alpha Value | M | | 9.2.3.a | | – | |
+| >UL PhysCH SF Variation | M | | 9.2.3.13B | | – | |
+| >Synchronisation Configuration | M | | 9.2.3.7E | | – | |
+| >Secondary CCPCH Info TDD | O | | 9.2.3.7B | | – | |
+| >UL CCTrCH Information | | 0.. | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information | M | | 9.2.3.13C | | – | |
+| >>Uplink SIR Target CCTrCH | O | | Uplink SIR 9.2.1.69 | | YES | ignore |
+| >DL CCTrCH Information | | 0.. | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------|
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information | M | | 9.2.3.2C | | | |
+| >>CCTrCH Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH. | YES | ignore |
+| >>CCTrCH Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH. | YES | ignore |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >DSCH Information Response | | 0 .. | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >USCH Information Response | | 0 .. | | | GLOBAL | ignore |
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >Time Slot for SCH | C-Case1 | | Time Slot 9.2.1.56 | | YES | ignore |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| Uplink SIR Target | M | | Uplink SIR 9.2.1.69 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| RL Information Response LCR | | 0..1 | | Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >URA Information | M | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >UL Time Slot ISCP Info LCR | M | | 9.2.3.13H | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR | | – | |
+
+| IE/Group Name | Presence | Range | IE Type
and
Reference | Semantics
Description | Criticality | Assigned
Criticality |
+|----------------------|-----------------|--------------|--------------------------------------|----------------------------------|--------------------|---------------------------------|
+| | | | 9.2.1.69 | | | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------------------------------------|------------------------|-------------------------------------|-------------|----------------------|
+| >Minimum Uplink SIR | M | | Uplink SIR
9.2.1.69 | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power
9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power
9.2.1.21A | | – | |
+| >UARFCN | O | | 9.2.1.66 | Corresponds to Nt in TS 25.105 [7]. | – | |
+| >Cell Parameter ID | O | | 9.2.1.8 | | – | |
+| >SCTD Indicator | O | | 9.2.1.78 | | – | |
+| >PCCPCH Power | M | | 9.2.1.43 | | – | |
+| >Alpha Value | M | | 9.2.3.a | | – | |
+| >UL PhysCH SF Variation | M | | 9.2.3.13B | | – | |
+| >Synchronisation Configuration | M | | 9.2.3.7E | | – | |
+| >Secondary CCPCH Info TDD LCR | O | | 9.2.3.7F | | – | |
+| >UL CCTrCH Information LCR | | 0..<maxNrOfCCTrCHsLCR> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information LCR | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information LCR | M | | 9.2.3.13G | | – | |
+| >>Uplink SIR Target CCTrCH | O | | Uplink SIR
9.2.1.69 | | YES | ignore |
+| >DL CCTrCH Information LCR | | 0..<maxNrOfCCTrCHsLCR> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information LCR | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information LCR | M | | 9.2.3.2E | | – | |
+| >>>TSTD Indicator | M | | 9.2.3.13E | | – | |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >DSCH Information Response LCR | | 0..<maxNoOfDSCHsLCR> | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >USCH Information Response LCR | | 0..<maxNoOfUSCHsLCR> | | | GLOBAL | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|--------------------------------|--------------------------------------------|------------------------------------------------------------------------------|-------------|----------------------|
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >Uplink Timing Advance Control LCR | M | | 9.2.3.13K | | YES | ignore |
+| >PowerControl GAP | O | | INTEGER (1..255) | Unit: umber of subframes
Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >SixtyfourQAM DL Support Indicator | O | | 9.2.1.123 | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >Idle Interval Information | O | | 9.2.3.60 | TDD only. | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| HS-DSCH Information Response | O | | HS-DSCH TDD Information Response 9.2.3.3ab | | YES | ignore |
+| DSCH-RNTI | O | | 9.2.3.3ah | | YES | ignore |
+| Active MBMS Bearer Service List | | 0.. | | | GLOBAL | ignore |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| >Transmission Mode | O | | 9.2.1.81 | | – | |
+| >Preferred Frequency Layer | O | | UARFCN 9.2.1.66 | | – | |
+| RL Information Response 7.68Mcps | | 0..1 | | Mandatory for 7.68Mcps TDD , not applicable to 1.28Mcps TDD or 3.84Mcps TDD. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >URA Information | O | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >UL Time Slot ISCP Info | M | | 9.2.3.13D | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power | | – | |
+
+| IE/Group Name | Presence | Range | IE Type
and
Reference | Semantics
Description | Criticality | Assigned
Criticality |
+|----------------------|-----------------|--------------|--------------------------------------|----------------------------------|--------------------|---------------------------------|
+| | | | 9.2.1.21A | | | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|----------------------------------|-----------------------|-------------------------------------|-------------|----------------------|
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >UARFCN | O | | UARFCN 9.2.1.66 | Corresponds to Nt in TS 25.105 [7]. | – | |
+| >Cell Parameter ID | O | | 9.2.1.8 | | – | |
+| >Sync Case | O | | 9.2.1.54 | | – | |
+| >SCH Time Slot | C-Case2 | | 9.2.1.51 | | – | |
+| >SCTD Indicator | O | | 9.2.1.78 | | – | |
+| >PCCPCH Power | M | | 9.2.1.43 | | – | |
+| >Timing Advance Applied | M | | 9.2.3.12A | | – | |
+| >Alpha Value | M | | 9.2.3.a | | – | |
+| >UL PhysCH SF Variation | M | | 9.2.3.13B | | – | |
+| >Synchronisation Configuration | M | | 9.2.3.7E | | – | |
+| >Secondary CCPCH Info 7.68Mcps TDD | O | | 9.2.3.22 | | – | |
+| >UL CCTrCH Information 7.68 Mcps | | 0..<maxNrOfCCTrCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information 7.68Mcps | M | | 9.2.3.26 | | – | |
+| >>Uplink SIR Target CCTrCH | O | | Uplink SIR 9.2.1.69 | | – | |
+| >DL CCTrCH Information 7.68 Mcps | | 0..<maxNrOfCCTrCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information 7.68Mcps | M | | 9.2.3.28 | | – | |
+| >>CCTrCH Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH. | – | |
+| >>CCTrCH Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH. | – | |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >DSCH Information Response 7.68 Mcps | | 0 .. <maxnoOfDSCHs> | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >USCH Information Response 7.68 Mcps | | 0 .. <maxNoOfUSCHs> | | | GLOBAL | ignore |
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-------|---------------------------------------------------|-----------------------|-------------|----------------------|
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | – | |
+| >HCS Prio | O | | 9.2.1.30N | | – | |
+| >Time Slot for SCH | C-Case1 | | Time Slot 9.2.1.56 | | – | |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| E-DCH Information Response | O | | E-DCH TDD Information Response 9.2.3.41 | 3.84Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 7.68Mcps | O | | E-DCH TDD Information Response 7.68Mcps 9.2.3.52 | 7.68Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 1.28Mcps | O | | E-DCH TDD Information Response 1.28Mcps 9.2.3.41a | 1.28Mcps TDD only. | YES | ignore |
+| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.63 | 1.28 Mcps TDD only. | YES | ignore |
+| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.68 | 1.28 Mcps TDD only. | YES | ignore |
+| E-DCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.69 | 1.28 Mcps TDD only. | YES | ignore |
+| E-RNTI for FACH | O | | E-RNTI 9.2.1.94 | 1.28 Mcps TDD only. | YES | ignore |
+| H-RNTI for FACH | O | | HS-DSCH-RNTI 9.2.1.30P | 1.28 Mcps TDD only. | YES | ignore |
+| DCH Measurement Occasion Information | O | | 9.2.3.75 | 1.28 Mcps TDD only. | YES | reject |
+| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.78 | 1.28 Mcps TDD only. | YES | ignore |
+| MU-MIMO Information | O | | 9.2.3.81 | 1.28 Mcps TDD only. | YES | reject |
+
+| Condition | Explanation |
+|-----------|----------------------------------------------------------------------|
+| Case2 | The IE shall be present if Sync Case IE is equal to "Case2". |
+| Case1 | This IE shall be present if Sync Case IE is equal to "Case1". |
+
+| Range bound | Explanation |
+|----------------------------------|-----------------------------------------------------------------------|
+| maxNoOfDSCHs | Maximum number of DSCHs for one UE for 3.84Mcps TDD or 7.68Mcps TDD. |
+| maxNoOfUSCHs | Maximum number of USCHs for one UE for 3.84Mcps TDD or 7.68Mcps TDD. |
+| maxNrOfCCTrCHs | Maximum number of CCTrCH for one UE for 3.84Mcps TDD or 7.68Mcps TDD. |
+| maxNoOfDSCHsLCR | Maximum number of DSCHs for one UE for 1.28Mcps TDD. |
+| maxNoOfUSCHsLCR | Maximum number of USCHs for one UE for 1.28Mcps TDD. |
+| maxNrOfCCTrCHsLCR | Maximum number of CCTrCH for one UE for 1.28Mcps TDD. |
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+
+### 9.1.5 RADIO LINK SETUP FAILURE
+
+#### 9.1.5.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------|-------------------------|-------------------|-----------------------------------|------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| CN PS Domain Identifier | O | | 9.2.1.12 | | YES | ignore |
+| CN CS Domain Identifier | O | | 9.2.1.11 | | YES | ignore |
+| CHOICE Cause Level | M | | | | YES | ignore |
+| > General | | | | | – | |
+| >> Cause | M | | 9.2.1.5 | | – | |
+| > RL Specific | | | | | – | |
+| >> Unsuccessful RL Information Response | | 1.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>Cause | M | | 9.2.1.5 | | – | |
+| >>>Max UE DTX Cycle | C-DTX-CycleNotAvailable | | 9.2.2.87 | | YES | ignore |
+| >> Successful RL Information Response | | 0.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>RL Set ID | M | | 9.2.2.35 | | – | |
+| >>>URA Information | O | | 9.2.1.70B | | – | |
+| >>>SAI | M | | 9.2.1.52 | | – | |
+| >>>Cell GAI | O | | 9.2.1.5A | | – | |
+| >>>UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >>>Received Total Wide Band Power | M | | 9.2.2.35A | | – | |
+| >>>Not Used | O | | NULL | | – | |
+| >>>DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | – | |
+| >>>CHOICE Diversity Indication | M | | | | – | |
+| >>>> Combining | | | | | – | |
+| >>>>>RL ID | M | | 9.2.1.49 | Reference RL ID for the combining. | – | |
+| >>>>>DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >>>>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >>>> Non Combining or First RL | | | | | – | |
+| >>>>>DCH Information Response | M | | 9.2.1.16A | | – | |
+| >>>>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >>>SSDT Support Indicator | M | | 9.2.2.43 | | – | |
+| >>>Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >>>Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >>>Closed Loop Timing Adjustment Mode | O | | 9.2.2.3A | | – | |
+| >>>Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >>>Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >>>Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >>>Primary CPICH | M | | 9.2.1.44 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|---------------------------------------------|--------------------------------------------|-------------------------------------|-------------|----------------------|
+| Power | | | | | | |
+| >>>Primary Scrambling Code | O | | 9.2.1.45 | | – | |
+| >>>UL UARFCN | O | | UARFCN 9.2.1.66 | Corresponds to Nu in TS 25.104 [6]. | – | |
+| >>>DL UARFCN | O | | UARFCN 9.2.1.66 | Corresponds to Nd in TS 25.104 [6]. | – | |
+| >>>Not Used | O | | NULL | | – | |
+| >>>Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >>>Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >>>PC Preamble | M | | 9.2.2.27a | | – | |
+| >>>SRB Delay | M | | 9.2.2.39A | | – | |
+| >>>Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >>>DL Power Balancing Activation Indicator | O | | 9.2.2.10B | | YES | ignore |
+| >>>HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >>>Primary CPICH Usage For Channel Estimation | O | | 9.2.2.32A | | YES | ignore |
+| >>>Secondary CPICH Information | O | | 9.2.2.38A | | YES | ignore |
+| >>>Active MBMS Bearer Service List | | 0..<maxNrOfActiveMBMSServices> | | | GLOBAL | ignore |
+| >>>>TMGI | M | | 9.2.1.80 | | – | |
+| >>>>Transmission Mode | O | | 9.2.1.81 | | – | |
+| >>>>Preferred Frequency Layer | O | | UARFCN 9.2.1.66 | | – | |
+| >>>E-DCH RL Set ID | O | | RL Set ID 9.2.2.35 | | YES | ignore |
+| >>>E-DCH FDD DL Control Channel Information | O | | 9.2.2.4D | | YES | ignore |
+| >>>Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment 9.2.2.9A | | YES | ignore |
+| >>>Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >>>HS-DSCH Preconfiguration Info | O | | 9.2.2.99 | | YES | ignore |
+| >>>F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >>>Non-Serving RL Preconfiguration Info | O | | 9.2.2.125 | | YES | ignore |
+| >>>Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| >>HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| >>HS-DSCH Information Response | O | | HS-DSCH FDD Information Response 9.2.2.19b | | YES | ignore |
+| >>Continuous Packet | O | | 9.2.2.75 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------|----------|------------------------------------|-----------------------|-------------------------------------------------------------------|-------------|----------------------|
+| Connectivity HS-SCCH less Information Response | | | | | | |
+| >>SixtyfourQAM DL Support Indicator | O | | 9.2.1.123 | | YES | ignore |
+| >> Additional HS Cell Information Response | O | 0..<maxNrOfHSDSC H-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore |
+| >>>HS-PDSCH RL ID | M | | RL ID 9.2.1.49 | | – | |
+| >>>HS-DSCH-RNTI | M | | 9.2.1.30P | | – | |
+| >>>HS-DSCH FDD Secondary Serving Information Response | M | | 9.2.2.19ba | | – | |
+| >>>SixtyfourQAM DL Support Indicator | O | | 9.2.1.123 | | – | |
+| >> Additional E-DCH Cell Information Response | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | EACH | ignore |
+| >>>Additional E-DCH FDD Information Response | M | | 9.2.2.120 | | – | |
+| Uplink SIR Target | O | | Uplink SIR 9.2.1.69 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+| Condition | Explanation |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------|
+| DTX-CycleNotAvailable | The IE shall be present if the Cause IE is set to Continuous Packet Connectivity UE DTX Cycle not Available “. |
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.5.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Cause Level | M | | | | YES | ignore |
+| > General | | | | | – | |
+| >>Cause | M | | 9.2.1.5 | | – | |
+| > RL Specific | | | | | – | |
+| >>Unsuccessful RL Information Response | | 1 | | | YES | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>Cause | M | | 9.2.1.5 | | – | |
+| >>SixtyfourQAM DL Support Indicator | O | | 9.2.1.123 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+### 9.1.6 RADIO LINK ADDITION REQUEST
+
+#### 9.1.6.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|---------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Uplink SIR Target | M | | Uplink SIR
9.2.1.69 | | YES | reject |
+| RL Information | | 1.. | | | EACH | notify |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >C-ID | M | | 9.2.1.6 | | – | |
+| >Frame Offset | M | | 9.2.1.30 | | – | |
+| >Chip Offset | M | | 9.2.2.1 | | – | |
+| >Diversity Control Field | M | | 9.2.1.20 | | – | |
+| >Primary CPICH Ec/No | O | | 9.2.2.32 | | – | |
+| >Not Used | O | | NULL | | – | |
+| >Transmit Diversity Indicator | O | | 9.2.2.48 | | – | |
+| >DL Reference Power | O | | DL Power
9.2.1.21A | Power on DPCH or on F-DPCH. | YES | ignore |
+| >Enhanced Primary CPICH Ec/No | O | | 9.2.2.13I | | YES | ignore |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | YES | ignore |
+| >Delayed Activation | O | | 9.2.1.19Aa | | YES | reject |
+| >RL specific E-DCH Information | O | | 9.2.2.35a | | YES | reject |
+| >E-DCH RL Indication | O | | 9.2.2.4E | | YES | reject |
+| >Synchronisation Indicator | O | | 9.2.2.45A | | YES | ignore |
+| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.100 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.124 | | YES | ignore |
+| >F-TPICH Information | O | | 9.2.2.139 | | YES | ignore |
+| Active Pattern Sequence Information | O | | 9.2.2A | Either all the already active Transmission Gap Sequence(s) are addressed (Transmission Gap Pattern sequence shall overlap with the existing one) or none of the transmission gap sequences is activated. | YES | reject |
+| DPC Mode | O | | 9.2.2.12A | | YES | reject |
+| Permanent NAS UE Identity | O | | 9.2.1.73 | | YES | ignore |
+| Serving E-DCH RL | O | | 9.2.2.38C | | YES | reject |
+| Initial DL DPCH Timing Adjustment Allowed | O | | 9.2.2.21b | | YES | ignore |
+| HS-DSCH Serving Cell Change Information | O | | 9.2.2.19f | | YES | reject |
+| Serving Cell Change CFN | O | | CFN
9.2.1.9 | | YES | reject |
+| E-DPCH Information | | 0..1 | | | YES | reject |
+
+| | | | | | | |
+|---------------------------------------------------------------------|------------|-------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------|------|--------|
+| >Maximum Set of E-DPDCHs | M | | 9.2.2.24e | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | | – | |
+| >E-TFCS Information | M | | 9.2.2.4G | | – | |
+| >E-TTI | M | | 9.2.2.4J | | – | |
+| >E-DPCCH Power Offset | M | | 9.2.2.4K | | – | |
+| >E-RGCH 2-Index-Step Threshold | M | | 9.2.2.64 | | – | |
+| >E-RGCH 3-Index-Step Threshold | M | | 9.2.2.65 | | – | |
+| >HARQ Info for E-DCH | M | | 9.2.2.66 | | – | |
+| >HS-DSCH Configured Indicator | M | | 9.2.2.19C | | YES | reject |
+| >Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.102 | | YES | ignore |
+| E-DCH FDD Information | C-EDCHInfo | | 9.2.2.4B | | YES | reject |
+| Additional HS Cell Information RL Addition | | 0.<max NrOfHS DSCH-1 > | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject |
+| >HS-PDSCH RL ID | M | | RL ID 9.2.1.49 | | – | |
+| >C-ID | M | | 9.2.1.6 | | – | |
+| >HS-DSCH FDD Secondary Serving Information | M | | 9.2.2.19aa | | – | |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.137 | | YES | ignore |
+| Additional E-DCH Cell Information RL Add Req | | 0..1 | | For E-DCH on multiple frequencies in this DRNS. | YES | reject |
+| >CHOICE Setup Or Addition Of E-DCH On Secondary UL Frequency | M | | | | YES | reject |
+| >> Setup | | | | Used when the secondary UL frequency does not exist or is not configured with E-DCH in the current UE context. | – | |
+| >>>Multicell E-DCH Transport Bearer Mode | M | | 9.2.2.113 | | – | |
+| >>>Additional E-DCH Cell Information Setup | | 1.<max NrOfED CH-1> | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>Additional E-DCH FDD Setup Information | M | | 9.2.2.110 | | – | |
+| >> Addition | | | | Used when there exist additional E- | – | |
+
+| | | | | | | |
+|-------------------------------------------------------------------|---|---------------------|---------------------|-------------------------------------------------------------------|-----|--------|
+| | | | | DCH RLs in the current UE context. | | |
+| >>>>Additional E-DCH Cell Information Addition | | 1. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>UL DPCH Information | | 1 | | | – | |
+| >>>>>Uplink SIR Target | M | | Uplink SIR 9.2.1.69 | | – | |
+| >>>>Additional E-DCH RL Specific Information To Add | M | | 9.2.2.116 | | – | |
+| >>>>Additional E-DCH FDD Information | O | | 9.2.2.112 | | – | |
+| >>>>Multicell E-DCH Information | O | | 9.2.2.114 | | YES | ignore |
+| UL CLTD Information | O | | 9.2.2.131 | | YES | reject |
+
+| Condition | Explanation |
+|-----------|----------------------------------------------------------------------|
+| EDCHInfo | This IE shall be present if E-DPCH Information IE is present. |
+
+| Range bound | Explanation |
+|------------------------|---------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of radio links for one UE. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.6.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|---------------------|-----------------------------------|-----------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information | | 1 | | | YES | reject |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >C-ID | M | | 9.2.1.6 | | – | |
+| >Frame Offset | M | | 9.2.1.30 | | – | |
+| >Diversity Control Field | M | | 9.2.1.20 | | – | |
+| >Primary CCPCH RSCP | O | | 9.2.3.5 | | – | |
+| >DL Time Slot ISCP Info | O | | 9.2.3.2D | Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | – | |
+| >DL Time Slot ISCP Info LCR | O | | 9.2.3.2F | Applicable to 1.28Mcps TDD only. | YES | reject |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | YES | ignore |
+| >Delayed Activation | O | | 9.2.1.19Aa | | YES | reject |
+| >UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject |
+| >>Uplink Synchronisation Step Size | M | | 9.2.3.13J | | – | |
+| >>Uplink Synchronisation Frequency | M | | 9.2.3.13I | | – | |
+| > Primary CCPCH RSCP Delta | O | | 9.2.3.5a | | YES | ignore |
+| > Idle Interval Configuration Indicator | O | | NULL | TDD only. | YES | ignore |
+| Permanent NAS UE Identity | O | | 9.2.1.73 | | YES | ignore |
+| UL CCTrCH Information | | 0.. | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TDD TPC Uplink Step Size | O | | 9.2.3.10a | Applicable to 1.28Mcps TDD only. | – | |
+| DL CCTrCH Information | | 0.. | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TDD TPC Downlink Step Size | O | | 9.2.3.10 | | – | |
+| HS-DSCH Information | O | | HS-DSCH TDD Information 9.2.3.3aa | | YES | reject |
+| HS-PDSCH RL ID | O | | RL ID 9.2.1.49 | | YES | reject |
+| E-DCH Information | | 0..1 | | 3.84Mcps TDD only. | YES | reject |
+| >E-PUCH Information | M | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | M | | 9.2.3.37 | | – | |
+
+| | | | | | | |
+|----------------------------------------------------|---|------|-------------------|---------------------------------------------------------------------|-----|--------|
+| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.38 | | – | |
+| >E-DCH TDD Information | M | | 9.2.3.40 | | – | |
+| E-DCH Serving RL | O | | RL ID
9.2.1.49 | 3.84Mcps
TDD only. | YES | reject |
+| E-DCH Information
7.68Mcps | | 0..1 | | 7.68Mcps
TDD only. | YES | reject |
+| >E-PUCH Information | M | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | M | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.38 | | – | |
+| >E-DCH TDD Information 7.68Mcps | M | | 9.2.3.51 | | – | |
+| E-DCH Information
1.28Mcps | | 0..1 | | 1.28Mcps
TDD only. | YES | reject |
+| >E-PUCH Information LCR | M | | 9.2.3.36a | | – | |
+| >E-TFCS Information TDD | M | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.38 | | – | |
+| >E-DCH TDD Information LCR | M | | 9.2.3.40a | | – | |
+| Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.61 | 1.28 Mcps
TDD only. | YES | reject |
+| HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.64 | 1.28 Mcps
TDD only. | YES | reject |
+| E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.66 | 1.28 Mcps
TDD only. | YES | reject |
+| DCH Measurement Type indicator | O | | 9.2.3.76 | 1.28 Mcps
TDD only. | YES | reject |
+| Multi-Carrier E-DCH Information | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only. | YES | reject |
+| >Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.79 | 1.28 Mcps
TDD only. | – | |
+| >Multi-Carrier E-DCH Information LCR | M | | 9.2.3.77 | 1.28 Mcps
TDD only. | – | |
+| MU-MIMO Indicator | O | | 9.2.3.82 | 1.28 Mcps
TDD only. | YES | reject |
+
+| Range bound | Explanation |
+|-----------------------|--------------------------------------|
+| maxNrOfCCTrCHs | Maximum number of CCTrCH for one UE. |
+
+### 9.1.7 RADIO LINK ADDITION RESPONSE
+
+#### 9.1.7.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|--------------------------------|-----------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information Response | | 1.. | | | EACH | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >RL Set ID | M | | 9.2.2.35 | | – | |
+| >URA Information | O | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >Received Total Wide Band Power | M | | 9.2.2.35A | | – | |
+| >Not Used | O | | NULL | | – | |
+| >DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | YES | ignore |
+| >CHOICE Diversity Indication | M | | | | – | |
+| >>Combining | | | | | – | |
+| >>>RL ID | M | | 9.2.1.49 | Reference RL ID. | – | |
+| >>>DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >>Non Combining | | | | | – | |
+| >>>DCH Information Response | M | | 9.2.1.16A | | – | |
+| >>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >SSDT Support Indicator | M | | 9.2.2.43 | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Closed Loop Timing Adjustment Mode | O | | 9.2.2.3A | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >PC Preamble | M | | 9.2.2.27a | | – | |
+| >SRB Delay | M | | 9.2.2.39A | | – | |
+| >Primary CPICH Power | M | | 9.2.1.44 | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >DL Power Balancing Activation Indicator | O | | 9.2.2.10B | | YES | ignore |
+| >HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >Active MBMS Bearer Service List | | 0.. | | | GLOBAL | ignore |
+| >>TMGI | M | | 9.2.1.80 | | – | |
+| >>Transmission Mode | O | | 9.2.1.81 | | – | |
+| >>Preferred Frequency | O | | UARFCN | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-----------------------------------|-------------------------------------------------------------|-------------------------------------------------------------------|-------------|----------------------|
+| Layer | | | 9.2.1.66 | | | |
+| >E-DCH RL Set ID | O | | RL Set ID
9.2.2.35 | | YES | ignore |
+| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.4D | | YES | ignore |
+| >Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment
9.2.2.9.A | | YES | ignore |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >HS-DSCH Preconfiguration Info | O | | 9.2.2.99 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.125 | | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| >F-TPICH Information Response | O | | 9.2.2.143 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH Serving Cell Change Information Response | O | | 9.2.2.19g | | YES | ignore |
+| E-DCH Serving Cell Change Information Response | O | | 9.2.2.19h | | YES | ignore |
+| MAC-hs Reset Indicator | O | | 9.2.1.34B | | YES | ignore |
+| Additional HS Cell Change Information Response | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore |
+| >HS-PDSCH RL ID | M | | RL ID
9.2.1.49 | | – | |
+| >HS-DSCH Secondary Serving Cell Change Information Response | M | | 9.2.2.19ga | | – | |
+| Additional E-DCH Cell Information Response RL Add | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | EACH | ignore |
+| >Additional E-DCH FDD Information Response | O | | 9.2.2.120 | | – | |
+| >Additional E-DCH Serving Cell Change Information response | O | | E-DCH Serving Cell Change Information Response
9.2.2.19h | | – | |
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of radio links for one UE. |
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.7.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------|----------|---------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information Response | | 0..1 | | Mandatory for 3.84Mcps TDD, not applicable to 1.28Mcps TDD or 7.68Mcps TDD. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >URA Information | O | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >UL Time Slot ISCP Info | M | | 9.2.3.13D | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >PCCPCH Power | M | | 9.2.1.43 | | – | |
+| >Timing Advance Applied | M | | 9.2.3.12A | | – | |
+| >Alpha Value | M | | 9.2.3.a | | – | |
+| >UL PhysCH SF Variation | M | | 9.2.3.13B | | – | |
+| >Synchronisation Configuration | M | | 9.2.3.7E | | – | |
+| >Secondary CCPCH Info TDD | O | | 9.2.3.7B | | – | |
+| >UL CCTrCH Information | | 0.. | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information | M | | 9.2.3.13C | | – | |
+| >DL CCTrCH Information | | 0.. | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information | M | | 9.2.3.2C | | – | |
+| >>CCTrCH Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH. | YES | ignore |
+| >>CCTrCH Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------|
+| >DCH Information | | 0..1 | | | – | |
+| >>CHOICE Diversity Indication | M | | | | – | |
+| >>>Combining | | | | | – | |
+| >>>>RL ID | M | | 9.2.1.49 | Reference RL. | – | |
+| >>>>DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >>>Non Combining | | | | | – | |
+| >>>>DCH Information Response | M | | 9.2.1.16A | | – | |
+| >DSCH Information Response | | 0 .. | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>CHOICE Diversity Indication | O | | | | – | |
+| >>>Non Combining | | | | | – | |
+| >>>>Binding ID | O | | 9.2.1.3 | | – | |
+| >>>>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >USCH Information Response | | 0 .. | | | GLOBAL | ignore |
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>CHOICE Diversity Indication | O | | | | – | |
+| >>>Non Combining | | | | | – | |
+| >>>>Binding ID | O | | 9.2.1.3 | | – | |
+| >>>>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| RL Information Response LCR | | 0..1 | | Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >URA Information | M | | 9.2.1.70B | | – | |
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------------------------------------|-----------------------|-----------------------|-------------|----------------------|
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >UL Time Slot ISCP Info LCR | M | | 9.2.3.13H | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >PCCPCH Power | M | | 9.2.1.43 | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Alpha Value | M | | 9.2.3.a | | – | |
+| >UL PhysCH SF Variation | M | | 9.2.3.13B | | – | |
+| >Synchronisation Configuration | M | | 9.2.3.7E | | – | |
+| >Secondary CCPCH Info TDD LCR | O | | 9.2.3.7F | | – | |
+| >UL CCTrCH Information LCR | | 0..<maxNrOfCCTrCHsLCR> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information LCR | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information LCR | M | | 9.2.3.13G | | – | |
+| >DL CCTrCH Information LCR | | 0..<maxNrOfCCTrCHsLCR> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information LCR | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information LCR | M | | 9.2.3.2E | | – | |
+| >>>TSTD Indicator | M | | 9.2.3.13E | | – | |
+| >DCH Information Response | M | | 9.2.1.16A | | – | |
+| >DSCH Information Response LCR | | 0 .. <maxNoOfDSCHsLCR> | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >USCH Information Response LCR | | 0 .. <maxNoOfUSCHsLCR> | | | GLOBAL | ignore |
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|---------------------------------------------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>CHOICE Diversity Indication | O | | | | – | |
+| >>> Non Combining | | | | | – | |
+| >>>>Binding ID | O | | 9.2.1.3 | | – | |
+| >>>>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >Uplink Timing Advance Control LCR | M | | 9.2.3.13K | | YES | ignore |
+| >PowerControl GAP | O | | INTEGER (1..255) | Unit: number of subframes
Applicable to 1.28Mcps
TDD only. | YES | ignore |
+| >UARFCN | O | | 9.2.1.66 | Applicable to 1.28Mcps
TDD only.
Mandatory for 1.28Mcps
TDD when using multiple frequencies.
Corresponds to Nt (3GPP TS 25.105) . | YES | ignore |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >Idle Interval Information | O | | 9.2.3.60 | TDD only. | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| Active MBMS Bearer Service List | | 0..<maxNrOfActiveMBMSServices> | | | GLOBAL | ignore |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| >Transmission Mode | O | | 9.2.1.81 | | – | |
+| >Preferred Frequency Layer | O | | UARFCN 9.2.1.66 | | – | |
+| HS-DSCH Information Response | O | | HS-DSCH TDD Information Response 9.2.3.3ab | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| RL Information Response 7.68Mcps | | 0..1 | | Mandatory for 7.68Mcps
TDD, not applicable to 1.28Mcps
TDD or 3.84Mcps
TDD. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >URA Information | O | | 9.2.1.70B | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|----------------------------------|-----------------------|--------------------------------|-------------|----------------------|
+| >SAI | M | | 9.2.1.52 | | – | |
+| >Cell GAI | O | | 9.2.1.5A | | – | |
+| >UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >UL Time Slot ISCP Info | M | | 9.2.3.13D | | – | |
+| >Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >PCCPCH Power | M | | 9.2.1.43 | | – | |
+| >Timing Advance Applied | M | | 9.2.3.12A | | – | |
+| >Alpha Value | M | | 9.2.3.a | | – | |
+| >UL PhysCH SF Variation | M | | 9.2.3.13B | | – | |
+| >Synchronisation Configuration | M | | 9.2.3.7E | | – | |
+| >Secondary CCPCH Info 7.68Mcps TDD | O | | 9.2.3.22 | | – | |
+| >UL CCTrCH Information 7.68 Mcps | | 0..<maxNrOfCCTrCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information 7.68 Mcps | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information 7.68Mcps | M | | 9.2.3.26 | | – | |
+| >DL CCTrCH Information 7.68 Mcps | | 0..<maxNrOfCCTrCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information 7.68 Mcps | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information 7.68Mcps | M | | 9.2.3.28 | | – | |
+| >>CCTrCH Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH. | – | |
+| >>CCTrCH Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH. | – | |
+| >DCH Information | | 0..1 | | | – | |
+| >>CHOICE Diversity Indication | M | | | | – | |
+| >>>Combining | | | | | – | |
+| >>>>RL ID | M | | 9.2.1.49 | Reference RL. | – | |
+| >>>>DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >>>Non Combining | | | | | – | |
+| >>>>DCH Information | M | | 9.2.1.16A | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|----------------------------|---------------------------------------------------|-----------------------|-------------|----------------------|
+| Response | | | | | | |
+| >DSCH Information
Response 7.68 Mcps | | 0 ..
DSCHs> | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>CHOICE Diversity Indication | O | | | | – | |
+| >>>Non Combining | | | | | – | |
+| >>>>Binding ID | O | | 9.2.1.3 | | – | |
+| >>>>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >USCH Information
Response 7.68 Mcps | | 0 ..
USCHs> | | | GLOBAL | ignore |
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>CHOICE Diversity Indication | O | | | | – | |
+| >>>Non Combining | | | | | – | |
+| >>>>Binding ID | O | | 9.2.1.3 | | – | |
+| >>>>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+| >Cell GA Additional Shapes | O | | 9.2.1.5B | | – | |
+| >HCS Prio | O | | 9.2.1.30N | | – | |
+| >Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| E-DCH Information Response | O | | E-DCH TDD Information Response 9.2.3.41 | 3.84Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 7.68Mcps | O | | E-DCH TDD Information Response 7.68Mcps 9.2.3.52 | 7.68Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 1.28Mcps | O | | E-DCH TDD Information Response 1.28Mcps 9.2.3.41a | 1.28Mcps TDD only. | YES | ignore |
+| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.63 | 1.28 Mcps TDD only. | YES | ignore |
+| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.68 | 1.28 Mcps TDD only. | YES | ignore |
+| E-DCH Semi-Persistent scheduling Information | O | | 9.2.3.69 | 1.28 Mcps TDD only. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Response LCR | | | | | | |
+| DCH Measurement Occasion Information | O | | 9.2.3.75 | 1.28 Mcps TDD only. | YES | reject |
+| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.78 | 1.28 Mcps TDD only. | YES | ignore |
+| MU-MIMO Information | O | | 9.2.3.81 | 1.28 Mcps TDD only. | YES | reject |
+
+| Range Bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNoOfDSCHs | Maximum number of DSCHs for one UE for 3.84Mcps TDD. |
+| maxNoOfUSCHs | Maximum number of USCHs for one UE for 3.84Mcps TDD. |
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for one UE for 3.84Mcps TDD. |
+| maxNoOfDSCHsLCR | Maximum number of DSCHs for one UE for 1.28Mcps TDD. |
+| maxNoOfUSCHsLCR | Maximum number of USCHs for one UE for 1.28Mcps TDD. |
+| maxNrOfCCTrCHsLCR | Maximum number of CCTrCH for one UE for 1.28Mcps TDD. |
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+
+### 9.1.8 RADIO LINK ADDITION FAILURE
+
+#### 9.1.8.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-------------------|-----------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Cause Level | M | | | | YES | ignore |
+| >General | | | | | – | |
+| >>Cause | M | | 9.2.1.5 | | – | |
+| >RL Specific | | | | | – | |
+| >>Unsuccessful RL Information Response | | 1.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>Cause | M | | 9.2.1.5 | | – | |
+| >>Successful RL Information Response | | 0.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>RL Set ID | M | | 9.2.2.35 | | – | |
+| >>>URA Information | O | | 9.2.1.70B | | – | |
+| >>>SAI | M | | 9.2.1.52 | | – | |
+| >>>Cell GAI | O | | 9.2.1.5A | | – | |
+| >>>UTRAN Access Point Position | O | | 9.2.1.70A | | – | |
+| >>>Received Total Wide Band Power | M | | 9.2.2.35A | | – | |
+| >>>Not Used | O | | NULL | | – | |
+| >>>DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | YES | ignore |
+| >>>CHOICE Diversity Indication | M | | | | – | |
+| >>>>Combining | | | | | – | |
+| >>>>>RL ID | M | | 9.2.1.49 | Reference RL ID. | – | |
+| >>>>>DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >>>>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >>>>Non Combining | | | | | – | |
+| >>>>>DCH Information Response | M | | 9.2.1.16A | | – | |
+| >>>>>E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >>>SSDT Support Indicator | M | | 9.2.2.43 | | – | |
+| >>>Minimum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >>>Maximum Uplink SIR | M | | Uplink SIR 9.2.1.69 | | – | |
+| >>>Closed Loop Timing Adjustment Mode | O | | 9.2.2.3A | | – | |
+| >>>Maximum Allowed UL Tx Power | M | | 9.2.1.35 | | – | |
+| >>>Maximum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >>>Minimum DL TX Power | M | | DL Power 9.2.1.21A | | – | |
+| >>>Neighbouring UMTS Cell Information | O | | 9.2.1.41A | | – | |
+| >>>Neighbouring GSM Cell Information | O | | 9.2.1.41C | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|---------------------------------------------|----------------------------------------|-----------------------------------------------------------------|-------------|----------------------|
+| >>>Primary CPICH Power | M | | 9.2.1.44 | | – | |
+| >>>PC Preamble | M | | 9.2.2.27a | | – | |
+| >>>SRB Delay | M | | 9.2.2.39A | | – | |
+| >>>Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| >>>DL Power Balancing Activation Indicator | O | | 9.2.2.10B | | YES | ignore |
+| >>>HCS Prio | O | | 9.2.1.30N | | YES | ignore |
+| >>>Active MBMS Bearer Service List | | 0..<maxNrOfActiveMBMSServices> | | | GLOBAL | ignore |
+| >>>>TMGI | M | | 9.2.1.80 | | – | |
+| >>>>Transmission Mode | O | | 9.2.1.81 | | – | |
+| >>>>Preferred Frequency Layer | O | | UARFCN
9.2.1.66 | | – | |
+| >>>E-DCH RL Set ID | O | | RL Set ID
9.2.2.35 | | YES | ignore |
+| >>>E-DCH FDD DL Control Channel Information | O | | 9.2.2.4D | | YES | ignore |
+| >>>Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment
9.2.2.9.A | | YES | ignore |
+| >>>Neighbouring E-UTRA Cell Information | O | | 9.2.1.41De | | YES | ignore |
+| >>>HS-DSCH Preconfiguration Info | O | | 9.2.2.99 | | YES | ignore |
+| >>>F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >>>Non-Serving RL Preconfiguration Info | O | | 9.2.2.125 | | YES | ignore |
+| >>>Neighbouring UMTS Cell Information Extension | O | | 9.2.1.141 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH Serving Cell Change Information Response | O | | 9.2.2.19g | | YES | ignore |
+| E-DCH Serving Cell Change Information Response | O | | 9.2.2.19h | | YES | ignore |
+| Additional HS Cell Change Information Response | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore |
+| >HS-PDSCH RL ID | M | | RL ID
9.2.1.49 | | – | |
+| >HS-DSCH Secondary Serving Cell Change Information Response | M | | 9.2.2.19ga | | – | |
+| MAC-hs Reset Indicator | O | | 9.2.1.34B | | YES | ignore |
+| Additional E-DCH Cell Information Response RL Add | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP | EACH | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|-------|----------------------------------------------------------|-----------------------|-------------|----------------------|
+| | | | | release. | | |
+| >Additional E-DCH FDD Information Response | O | | 9.2.2.120 | | – | |
+| >Additional E-DCH Serving Cell Change Information response | O | | E-DCH Serving Cell Change Information Response 9.2.2.19h | | – | |
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of radio links for one UE. |
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.8.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Cause Level | M | | | | YES | ignore |
+| > General | | | | | – | |
+| >> Cause | M | | 9.2.1.5 | | – | |
+| > RL Specific | | | | | – | |
+| >> Unsuccessful RL Information Response | | 1 | | | YES | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>> Cause | M | | 9.2.1.5 | | – | |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+### 9.1.9 RADIO LINK DELETION REQUEST
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------|----------|--------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information | | 1..< maxNrOfRLs > | | | EACH | notify |
+| >RL ID | M | | 9.2.1.49 | | – | |
+
+| Range bound | Explanation |
+|-------------------|------------------------------------------|
+| maxNrOfRLs | Maximum number of radio links for one UE |
+
+### 9.1.10 RADIO LINK DELETION RESPONSE
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+### 9.1.11 RADIO LINK RECONFIGURATION PREPARE
+
+#### 9.1.11.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------|---------------|------------------|---------------------------------|----------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Allowed Queuing Time | O | | 9.2.1.2 | | YES | reject |
+| UL DPCH Information | | 0..1 | | | YES | reject |
+| >UL Scrambling Code | O | | 9.2.2.53 | | – | |
+| >UL SIR Target | O | | Uplink SIR
9.2.1.69 | | – | |
+| >Min UL Channelisation Code Length | O | | 9.2.2.25 | | – | |
+| >Max Number of UL DPDCHs | C – CodeLen | | 9.2.2.24 | | – | |
+| >Puncture Limit | O | | 9.2.1.46 | For the UL. | – | |
+| >TFCS | O | | 9.2.1.63 | TFCS for the UL. | – | |
+| >UL DPCCH Slot Format | O | | 9.2.2.52 | | – | |
+| >Diversity Mode | O | | 9.2.2.8 | | – | |
+| >Not Used | O | | NULL | | – | |
+| >Not Used | O | | NULL | | – | |
+| >UL DPDCH Indicator For E-DCH Operation | O | | 9.2.2.52A | | YES | reject |
+| DL DPCH Information | | 0..1 | | | YES | reject |
+| >TFCS | O | | 9.2.1.63 | TFCS for the DL. | – | |
+| >DL DPCH Slot Format | O | | 9.2.2.9 | | – | |
+| >Number of DL Channelisation Codes | O | | 9.2.2.26A | | – | |
+| >TFCI Signalling Mode | O | | 9.2.2.46 | | – | |
+| >TFCI Presence | C- SlotFormat | | 9.2.1.55 | | – | |
+| >Multiplexing Position | O | | 9.2.2.26 | | – | |
+| >Limited Power Increase | O | | 9.2.2.21A | | – | |
+| >DL DPCH Power Information | | 0..1 | | | YES | reject |
+| >>Power Offset Information | | 1 | | | – | |
+| >>>PO1 | M | | Power Offset
9.2.2.30 | Power offset for the TFCI bits. | – | |
+| >>>PO2 | M | | Power Offset
9.2.2.30 | Power offset for the TPC bits. | – | |
+| >>>PO3 | M | | Power Offset
9.2.2.30 | Power offset for the pilot bits. | – | |
+| >>FDD TPC Downlink Step Size | M | | 9.2.2.16 | | – | |
+| >>Inner Loop DL PC Status | M | | 9.2.2.21a | | – | |
+| DCHs To Modify | O | | FDD DCHs To Modify
9.2.2.13C | | YES | reject |
+| DCHs To Add | O | | DCH FDD Information
9.2.2.4A | | YES | reject |
+| DCHs To Delete | | 0.. | | | GLOBAL | reject |
+| >DCH ID | M | | 9.2.1.16 | | – | |
+| RL Information | | 0.. | | | EACH | reject |
+| >RL ID | M | | 9.2.1.49 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|--------------------|-------|-------------------------------------------------|--------------------------------|-------------|----------------------|
+| >Not Used | O | | NULL | | – | |
+| >Not Used | O | | NULL | | – | |
+| >Transmit Diversity Indicator | C – Diversity mode | | 9.2.2.48 | | – | |
+| >DL Reference Power | O | | DL Power 9.2.1.21A | Power on DPCH. | YES | ignore |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | YES | ignore |
+| >DL DPCH Timing Adjustment | O | | 9.2.2.9A | Required RL Timing Adjustment. | YES | reject |
+| >Phase Reference Update Indicator | O | | 9.2.2.27B | | YES | ignore |
+| >RL specific E-DCH Information | O | | 9.2.2.35a | | YES | reject |
+| >E-DCH RL Indication | O | | 9.2.2.4E | | YES | reject |
+| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.100 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.124 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Removal | O | | Non-Serving RL Preconfiguration Setup 9.2.2.124 | | YES | ignore |
+| >F-TPICH Information Reconf | O | | 9.2.2.142 | | YES | ignore |
+| Transmission Gap Pattern Sequence Information | O | | 9.2.2.47A | | YES | reject |
+| HS-DSCH Information | O | | HS-DSCH FDD Information 9.2.2.19a | | YES | reject |
+| HS-DSCH Information To Modify | O | | 9.2.1.30Q | | YES | reject |
+| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information 9.2.1.30OA | | YES | reject |
+| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.30OB | | YES | reject |
+| HS-PDSCH RL ID | O | | RL ID 9.2.1.49 | | YES | reject |
+| E-DPCH Information | | 0..1 | | | YES | reject |
+| >Maximum Set of E-DPDCHs | O | | 9.2.2.24e | | – | |
+| >Puncture Limit | O | | 9.2.1.46 | | – | |
+| >E-TFCS Information | O | | 9.2.2.4G | | – | |
+| >E-TTI | O | | 9.2.2.4J | | – | |
+| >E-DPCCH Power Offset | O | | 9.2.2.4K | | – | |
+| >E-RGCH 2-Index-Step Threshold | O | | 9.2.2.64 | | – | |
+| >E-RGCH 3-Index-Step Threshold | O | | 9.2.2.65 | | – | |
+| >HARQ Info for E-DCH | O | | 9.2.2.66 | | – | |
+| >HS-DSCH Configured Indicator | O | | 9.2.2.19C | | – | |
+| >Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.102 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------------|----------|----------------------|-----------------------------------------|-----------------------------------------------------------------|-------------|----------------------|
+| E-DCH FDD Information | O | | 9.2.2.4B | | YES | reject |
+| E-DCH FDD Information to Modify | O | | 9.2.2.4F | | YES | reject |
+| E-DCH MAC-d Flows to Add | O | | E-DCH MAC-d flows Information 9.2.2.4MC | | YES | reject |
+| E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | YES | reject |
+| Serving E-DCH RL | O | | 9.2.2.38C | | YES | reject |
+| F-DPCH Information | | 0..1 | | | YES | reject |
+| >Power Offset Information | | 1 | | | – | |
+| >>PO2 | M | | Power Offset 9.2.2.30 | This IE shall be ignored by DRNS. | – | |
+| >FDD TPC Downlink Step Size | M | | 9.2.2.16 | | – | |
+| >Limited Power Increase | M | | 9.2.2.21A | | – | |
+| >Inner Loop DL PC Status | M | | 9.2.2.21a | | – | |
+| >F-DPCH Slot Format Support Request | O | | 9.2.2.86 | | YES | reject |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| Fast Reconfiguration Mode | O | | 9.2.2.70 | | YES | ignore |
+| CPC Information | | 0..1 | | | YES | reject |
+| >Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.72 | | – | |
+| >Continuous Packet Connectivity DTX-DRX Information To Modify | O | | 9.2.2.73 | | – | |
+| >Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.74 | | – | |
+| >Continuous Packet Connectivity HS-SCCH less Deactivate Indicator | O | | 9.2.2.75A | | YES | reject |
+| Additional HS Cell Information RL Reconf Prep | | 0.. | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject |
+| >HS-PDSCH RL ID | M | | RL ID 9.2.1.49 | | – | |
+| >C-ID | O | | 9.2.1.6 | | – | |
+| >HS-DSCH FDD Secondary Serving Information | O | | 9.2.2.19aa | | – | |
+| >HS-DSCH FDD Secondary Serving Information To Modify | O | | 9.2.2.19bb | | – | |
+| >HS-DSCH Secondary Serving Remove | O | | NULL | | – | |
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.137 | | YES | ignore |
+| Additional E-DCH Cell Information RL Reconf Prep | | 0..1 | | For E-DCH on multiple frequencies in this | YES | reject |
+
+| IE/Group Name | Presence | Range | IE Type
and
Reference | Semantics
Description | Criticality | Assigned
Criticality |
+|---------------|----------|-------|-----------------------------|--------------------------|-------------|-------------------------|
+| | | | | DRNS. | | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------------------------------|----------|--------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency | M | | | | YES | reject |
+| >>Setup | | | | Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current UE context. | – | |
+| >>>Multicell E-DCH Transport Bearer Mode | M | | 9.2.2.113 | | – | |
+| >>>Additional E-DCH Cell Information Setup | | 1.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>Additional E-DCH FDD Setup Information | M | | 9.2.2.110 | | – | |
+| >>Configuration Change | | | | Used when RLs with additional E-DCH on the secondary UL frequency exist in the current UE context and the configuration is modified (adding new RLs or modification of existing RLs). | – | |
+| >>>Additional E-DCH Cell Information Configuration Change | | 1.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>Additional E-DCH Configuration Change Information | M | | 9.2.2.111 | | – | |
+| >>Removal | | | | Used when all RLs on the indicated secondary UL | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|--------------------|-------------------------|-------------------------------------------------------------------|-------------|----------------------|
+| | | | | frequency is removed. | | |
+| >>>Additional E-DCH Cell Information Removal | | 1.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>RL on Secondary UL Frequency | M | | ENUMERATED (Remove, ..) | Removal of all RL on secondary UL frequency. | – | |
+| UL CLTD Information Reconf | O | | 9.2.2.130 | | YES | reject |
+
+| Condition | Explanation |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------|
+| CodeLen | The IE shall be present only if the Min UL Channelisation Code length IE equals to 4. |
+| SlotFormat | The IE shall only be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16. |
+| Diversity mode | The IE shall be present if Diversity Mode IE is present in the UL DPCH Information IE and is not equal to “none”. |
+
+| Range bound | Explanation |
+|------------------------|---------------------------------------------------------------|
+| maxNrOfDCHs | Maximum number of DCHs for a UE. |
+| maxNrOfRLs | Maximum number of RLs for a UE. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE |
+
+#### 9.1.11.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------|----------|-----------------------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Allowed Queuing Time | O | | 9.2.1.2 | | YES | reject |
+| UL CCTrCH To Add | | 0..<max NrOfCCTrCHs> | | For DCH and USCH. | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | M | | 9.2.1.63 | For the UL. | – | |
+| >TFCI Coding | M | | 9.2.3.11 | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | | – | |
+| >UL SIR Target | O | | Uplink SIR 9.2.1.69 | Mandatory for 1.28Mcps TDD; not applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject |
+| >TDD TPC Uplink Step Size | O | | 9.2.3.10a | Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject |
+| UL CCTrCH To Modify | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | O | | 9.2.1.63 | For the UL. | – | |
+| >TFCI Coding | O | | 9.2.3.11 | | – | |
+| >Puncture Limit | O | | 9.2.1.46 | | – | |
+| >UL SIR Target | O | | Uplink SIR 9.2.1.69 | Applicable to 1.28Mcps TDD only. | YES | reject |
+| >TDD TPC Uplink Step Size | O | | 9.2.3.10a | Applicable to 1.28Mcps TDD only. | YES | reject |
+| UL CCTrCH to Delete | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| DL CCTrCH To Add | | 0..<max NrOfCCTrCHs> | | For DCH and DSCH. | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | M | | 9.2.1.63 | For the DL. | – | |
+| >TFCI Coding | M | | 9.2.3.11 | | – | |
+| >Puncture Limit | M | | 9.2.1.46 | | – | |
+| >TPC CCTrCH List | | 0..<maxn oCCTrCHs> | | List of uplink CCTrCH which provide TPC. | – | |
+| >>TPC CCTrCH ID | M | | CCTrCH ID 9.2.3.2 | | – | |
+| >TDD TPC Downlink Step Size | O | | 9.2.3.10 | | YES | reject |
+| DL CCTrCH To Modify | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | O | | 9.2.1.63 | For the DL. | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|--------------------------------------------|-------------------------------|------------------------------------------------------|-------------|----------------------|
+| >TFCI Coding | O | | 9.2.3.11 | | – | |
+| >Puncture Limit | O | | 9.2.1.46 | | – | |
+| >TPC CCTrCH List | | 0..<maxn
oCCTrC
Hs> | | List of uplink CCTrCH which provide TPC. | – | |
+| >>TPC CCTrCH ID | M | | CCTrCH ID 9.2.3.2 | | – | |
+| >TDD TPC Downlink Step Size | O | | 9.2.3.10 | | YES | reject |
+| DL CCTrCH to Delete | | 0..<max
NrOfCCT
rCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| DCHs To Modify | O | | TDD DCHs To Modify 9.2.3.8B | | YES | reject |
+| DCHs To Add | O | | DCH TDD Information 9.2.3.2A | | YES | reject |
+| DCHs to Delete | | 0..<max
NrOfDC
Hs> | | | GLOBAL | reject |
+| >DCH ID | M | | 9.2.1.16 | | – | |
+| DSCHs To Modify | | 0..<max
NrOfDS
CHs> | | | GLOBAL | reject |
+| >DSCH ID | M | | 9.2.3.3ae | | – | |
+| >CCTrCH ID | O | | 9.2.3.2 | DL CCTrCH in which the DSCH is mapped. | – | |
+| >TrCH Source Statistics Descriptor | O | | 9.2.1.65 | | – | |
+| >Transport Format Set | O | | 9.2.1.64 | | – | |
+| >Allocation/Retention Priority | O | | 9.2.1.1 | | – | |
+| >Scheduling Priority Indicator | O | | 9.2.1.51A | | – | |
+| >BLER | O | | 9.2.1.4 | | – | |
+| >Transport Bearer Request Indicator | M | | 9.2.1.61 | | – | |
+| >Traffic Class | O | | 9.2.1.58A | | YES | ignore |
+| >Binding ID | O | | 9.2.1.3 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore |
+| >Transport Layer Address | O | | 9.2.1.62 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore |
+| >TNL QoS | O | | 9.2.1.56A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore |
+| DSCHs To Add | O | | DSCH TDD Information 9.2.3.3a | | YES | reject |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|---------------------|-----------------------|------------------------------------------------------|-------------|----------------------|
+| DSCHs to Delete | | 0.. | | | GLOBAL | reject |
+| >DSCH ID | M | | 9.2.3.3ae | | – | |
+| USCHs To Modify | | 0.. | | | GLOBAL | reject |
+| >USCH ID | M | | 9.2.3.14 | | – | |
+| >CCTrCH ID | O | | 9.2.3.2 | UL CCTrCH in which the USCH is mapped. | – | |
+| >TrCH Source Statistics Descriptor | O | | 9.2.1.65 | | – | |
+| >Transport Format Set | O | | 9.2.1.64 | | – | |
+| >Allocation/Retention Priority | O | | 9.2.1.1 | | – | |
+| >Scheduling Priority Indicator | O | | 9.2.1.51A | | – | |
+| >BLER | O | | 9.2.1.4 | | – | |
+| >Transport Bearer Request Indicator | M | | 9.2.1.61 | | – | |
+| >RB Info | | 0.. | | All Radio Bearers using this USCH | – | |
+| >>RB Identity | M | | 9.2.3.5B | | – | |
+| >Traffic class | O | | 9.2.1.58A | | YES | ignore |
+| >Binding ID | O | | 9.2.1.3 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore |
+| >Transport Layer Address | O | | 9.2.1.62 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore |
+| >TNL QoS | O | | 9.2.1.56A | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|----------------------------------|--------------------------------------------|-----------------------------------------------------------------------------|-------------|----------------------|
+| USCHs To Add | O | | USCH Information 9.2.3.15 | | YES | reject |
+| USCHs to Delete | | 0..<max NoOfUS CHs> | | | GLOBAL | reject |
+| >USCH ID | M | | 9.2.3.14 | | – | |
+| Primary CCPCH RSCP | O | | 9.2.3.5 | | YES | ignore |
+| DL Time Slot ISCP Info | O | | 9.2.3.2D | Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | YES | ignore |
+| DL Time Slot ISCP Info LCR | O | | 9.2.3.2F | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| HS-DSCH Information | O | | HS-DSCH TDD Information 9.2.3.3aa | | YES | reject |
+| HS-DSCH Information To Modify | O | | 9.2.1.30Q | | YES | reject |
+| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information 9.2.1.30OA | | YES | reject |
+| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.30OB | | YES | reject |
+| HS-PDSCH RL ID | O | | RL ID 9.2.1.49 | | YES | reject |
+| PDSCH-RL-ID | O | | RL ID 9.2.1.49 | | YES | ignore |
+| UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore |
+| >Uplink Synchronisation Step Size | M | | 9.2.3.13J | | – | |
+| >Uplink Synchronisation Frequency | M | | 9.2.3.13I | | – | |
+| RL Information | | 0..<max NrOfRLs.> | | | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | – | |
+| Primary CCPCH RSCP Delta | O | | 9.2.3.5a | | YES | ignore |
+| E-DCH Information | | 0..1 | | 3.84Mcps TDD only. | YES | reject |
+| >E-PUCH Information | O | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | O | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows to Add | O | | 9.2.3.38 | | – | |
+| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | – | |
+| >E-DCH TDD Information | O | | 9.2.3.40 | | – | |
+| >E-DCH TDD Information to Modify | O | | 9.2.3.42 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------------------------------------------------------|----------|-------|--------------------------|------------------------|-------------|----------------------|
+| E-DCH Serving RL | O | | RL ID
9.2.1.49 | 3.84Mcps
TDD only. | YES | reject |
+| E-DCH Information
7.68Mcps | | 0..1 | | 7.68Mcps
TDD only. | YES | reject |
+| >E-PUCH Information | O | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | O | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows to Add | O | | 9.2.3.38 | | – | |
+| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | – | |
+| >E-DCH TDD Information
7.68Mcps | O | | 9.2.3.51 | | – | |
+| >E-DCH TDD Information to Modify | O | | 9.2.3.42 | | – | |
+| E-DCH Information
1.28Mcps | | 0..1 | | 1.28Mcps
TDD only. | YES | reject |
+| >E-PUCH Information LCR | O | | 9.2.3.36a | | – | |
+| >E-TFCS Information TDD | O | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows to Add | O | | 9.2.3.38 | | – | |
+| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | – | |
+| >E-DCH TDD Information
LCR | O | | 9.2.3.40a | | – | |
+| >E-DCH TDD Information to Modify | O | | 9.2.3.42 | | – | |
+| Need for Idle Interval | O | | ENUMERATED (True, False) | TDD only. | YES | ignore |
+| CPC Information | | 0..1 | | 1.28Mcps
TDD only. | YES | reject |
+| >Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.61 | | – | |
+| >Continuous Packet Connectivity DRX Information To Modify LCR | O | | 9.2.3.62 | | – | |
+| >HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.64 | | – | |
+| >HS-DSCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.65 | | – | |
+| >HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.70 | | – | |
+| >E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.66 | | – | |
+| >E-DCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.67 | | – | |
+| >E-DCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.71 | | – | |
+| RNTI Allocation Indicator | O | | ENUMERATED (True) | 1.28 Mcps
TDD only. | YES | ignore |
+| DCH Measurement Type indicator | O | | 9.2.3.76 | 1.28 Mcps
TDD only. | YES | reject |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|------------------------------|-----------------------|---------------------------------------------------------------------|-------------|----------------------|
+| Multi-Carrier E-DCH Information Reconf | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only. | YES | reject |
+| >CHOICE continue, Setup or Change | M | | | | – | |
+| >>continue | | | | | – | |
+| >>Setup | | | | | – | |
+| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.79 | | – | |
+| >>>Multi-Carrier E-DCH Information LCR | M | | 9.2.3.77 | | – | |
+| >>change | | | | | – | |
+| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | O | | 9.2.3.79 | | – | |
+| >>>Multi-Carrier E-DCH Information LCR | O | | 9.2.3.77 | | – | |
+| >>>Removal UL Multi-Carrier info | | 0.. | | | – | |
+| >>>>UARFCN | M | | 9.2.1.66 | Corresponds to Nt TS 25.105 [17]. | – | |
+| MU-MIMO Indicator | O | | 9.2.3.82 | 1.28 Mcps TDD only. | YES | reject |
+
+| Range bound | Explanation |
+|-----------------------------|------------------------------------------------------------------------|
+| maxNrOfDCHs | Maximum number of DCHs for a UE. |
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+| maxNoOfDSCHs | Maximum number of DSCHs for one UE. |
+| maxNoOfUSCHs | Maximum number of USCHs for one UE. |
+| maxNrOfRLs | Maximum number of RLs for one UE |
+| maxNrOfULCarriersLCR | Maximum number of uplink frequencies in Multi-Carrier E-DCH Operation. |
+| maxNoOfRB | Maximum number of Radio Bearers for one UE. |
+
+### 9.1.12 RADIO LINK RECONFIGURATION READY
+
+#### 9.1.12.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------|----------|------------------------------------|-----------------------------------------------|-----------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information Response | | 0..<maxNrOfRLs> | | | EACH | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >Maximum Uplink SIR | O | | Uplink SIR
9.2.1.69 | | – | |
+| >Minimum Uplink SIR | O | | Uplink SIR
9.2.1.69 | | – | |
+| >Maximum DL TX Power | O | | DL Power
9.2.1.21A | | – | |
+| >Minimum DL TX Power | O | | DL Power
9.2.1.21A | | – | |
+| >Not Used | O | | NULL | | – | |
+| >DL Code Information | O | | FDD DL Code Information
9.2.2.14A | | YES | ignore |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >Not Used | O | | NULL | | – | |
+| >DL Power Balancing Updated Indicator | O | | 9.2.2.10D | | YES | ignore |
+| >Primary CPICH Usage For Channel Estimation | O | | 9.2.2.32A | | YES | ignore |
+| >Secondary CPICH Information Change | O | | 9.2.2.38B | | YES | ignore |
+| >E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >E-DCH RL Set ID | O | | RL Set ID
9.2.2.35 | | YES | ignore |
+| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.4D | | YES | ignore |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >HS-DSCH Preconfiguration Info | O | | 9.2.2.99 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.125 | | YES | ignore |
+| >F-TPICH Information Response | O | | 9.2.2.143 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| HS-DSCH Information Response | O | | HS-DSCH FDD Information Response
9.2.2.19b | | YES | ignore |
+| MAC-hs Reset Indicator | O | | 9.2.1.34B | | YES | ignore |
+| Fast Reconfiguration Permission | O | | 9.2.2.71 | FDD only. | YES | ignore |
+| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.75 | | YES | ignore |
+| Additional HS Cell Information Response | | 0..<maxNrOfHSDSC H-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore |
+| >HS-PDSCH RL ID | M | | RL ID
9.2.1.49 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------------|----------|--------------------|-----------------------|-------------------------------------------------------------------|-------------|----------------------|
+| >HS-DSCH-RNTI | M | | 9.2.1.30P | | – | |
+| >HS-DSCH FDD
Secondary Serving
Information Response | M | | 9.2.2.19ba | | – | |
+| Additional E-DCH Cell
Information Response
RLReconf | | 0.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | EACH | ignore |
+| >Additional E-DCH FDD
Information Response | O | | 9.2.2.120 | For new E-DCH Radio Links on secondary carrier. | – | |
+| >Additional Modified E-DCH FDD
Information Response | O | | 9.2.2.121 | | – | |
+
+| Range bound | Explanation |
+|------------------------|---------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for a UE. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.12.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-----------------------------------|-----------------------|----------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information Response | | 0..<max NrOfRLs> | | See Note 1 below. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >Maximum Uplink SIR | O | | Uplink SIR 9.2.1.69 | | – | |
+| >Minimum Uplink SIR | O | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum DL TX Power | O | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | O | | DL Power 9.2.1.21A | | – | |
+| >Secondary CCPCH Info TDD | O | | 9.2.3.7B | Applicable to 3.84Mcps TDD only. | – | |
+| >UL CCTrCH Information | | 0..<max NrOfCCTrCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH to be Added | | 0..1 | | Applicable to 3.84Mcps TDD only. | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>Rx Timing Deviation | O | | 9.2.3.7A | | – | |
+| >>>UL Timeslot Information | M | | 9.2.3.13C | | – | |
+| >>>Rx Timing Deviation 3.84 Mcps Extended | O | | 9.2.3.35 | | YES | ignore |
+| >>UL DPCH to be Modified | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | O | | 9.2.3.7 | | – | |
+| >>>Repetition Length | O | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | O | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information | | 0..<max NrOfTS> | | Applicable to 3.84Mcps TDD only. | – | |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type | O | | 9.2.3.4 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>UL Code Information | | 0..<max NrOfDPCHs> | | | – | |
+| >>>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>>TDD Channelisation Code | O | | 9.2.3.8 | | – | |
+| >>>UL Timeslot Information LCR | | 0..<max NrOfTSLCR> | | Applicable to 1.28Mcps TDD only. | GLOBAL | ignore |
+| >>>>Time Slot LCR | M | | 9.2.3.12a | | – | |
+| >>>>Midamble | O | | 9.2.3.4C | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|-------------------------------------|-----------------------|----------------------------------|-------------|----------------------|
+| Shift LCR | | | | | | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>UL Code Information LCR | | 0..<max NrOfDPC HsLCR> | | | GLOBAL | ignore |
+| >>>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>>TDD Channelisation Code LCR | O | | 9.2.3.8a | | – | |
+| >>>>>TDD UL DPCH Time Slot Format LCR | O | | 9.2.3.10C | | YES | reject |
+| >>>UL Timeslot Information 7.68Mcps | | 0..<max NrOfTS> | | Applicable to 7.68Mcps TDD only. | GLOBAL | ignore |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type 7.68Mcps | O | | 9.2.3.23 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>UL Code Information 7.68Mcps | | 0..<max NrOfDPC Hs768> | | | GLOBAL | ignore |
+| >>>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>>TDD Channelisation Code 7.68Mcps | O | | 9.2.3.25 | | – | |
+| >>UL DPCH to be Deleted | | 0..<max NrOfDPC Hs> | | | GLOBAL | ignore |
+| >>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>UL DPCH to be Added LCR | | 0..1 | | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information LCR | M | | 9.2.3.13G | | – | |
+| >>UL DPCH to be Added 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>Rx Timing Deviation 7.68Mcps | O | | 9.2.3.30 | | – | |
+| >>>UL Timeslot Information 7.68Mcps | M | | 9.2.3.26 | | – | |
+| >DL CCTrCH Information | | 0..<max NrOfCCT rCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH to be Added | | 0..1 | | Applicable to 3.84Mcps TDD only. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|------------------------|-----------------------|----------------------------------|-------------|----------------------|
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information | M | | 9.2.3.2C | | – | |
+| >>DL DPCH to be Modified | | 0..1 | | | YES | ignore |
+| >>>Repetition Period | O | | 9.2.3.7 | | – | |
+| >>>Repetition Length | O | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | O | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information | | 0.. | | Applicable to 3.84Mcps TDD only. | – | |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type | O | | 9.2.3.4 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>DL Code Information | | 0.. | | | – | |
+| >>>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>>TDD Channelisation Code | O | | 9.2.3.8 | | – | |
+| >>>DL Timeslot Information LCR | | 0.. | | Applicable to 1.28Mcps TDD only. | GLOBAL | ignore |
+| >>>>Time Slot LCR | M | | 9.2.3.12a | | – | |
+| >>>>Midamble Shift LCR | O | | 9.2.3.4C | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>DL Code Information LCR | | 0.. | | | GLOBAL | ignore |
+| >>>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>>TDD Channelisation Code LCR | O | | 9.2.3.8a | | – | |
+| >>>>>TDD DL DPCH Time Slot Format LCR | O | | 9.2.3.8E | | YES | reject |
+| >>>>Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH. | YES | ignore |
+| >>>>Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH. | YES | ignore |
+| >>>DL Timeslot Information 7.68Mcps | | 0.. | | Applicable to 7.68Mcps TDD only. | GLOBAL | ignore |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type 7.68Mcps | O | | 9.2.3.23 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>DL Code Information | | 0.. | | | – | |
+| >>>>>DPCH ID 7.68Mcps | M | | 9.2.3.34 | | – | |
+| >>>>>TDD Channelisation | O | | 9.2.3.25 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|------------------------------------|-----------------------|---------------------------------------------------------------------------------|-------------|----------------------|
+| Code 7.68Mcps | | | | | | |
+| >>DL DPCH to be Deleted | | 0..<max NrOfDPCHs> | | | GLOBAL | ignore |
+| >>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>DL DPCH to be Deleted 7.68Mcps TDD | | 0..<max NrOfDPCHs768> | | | GLOBAL | ignore |
+| >>>DPCH ID 7.68Mcps | M | | 9.2.3.34 | | – | |
+| >>DL DPCH to be Added LCR | | 0..1 | | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information LCR | M | | 9.2.3.2E | | – | |
+| >>DL DPCH to be Added 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| >>>Repetition Period | M | | 9.2.3.7 | | – | |
+| >>>Repetition Length | M | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | M | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information 7.68Mcps | M | | 9.2.3.28 | | – | |
+| >>CCTrCH Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | YES | ignore |
+| >>CCTrCH Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | YES | ignore |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >DSCH to be Added or Modified | | 0..<maxnof DSCHs> | | | GLOBAL | ignore |
+| >>DSCH ID | M | | 9.2.3.3ae | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>DSCH Flow Control Information | M | | 9.2.3.3ag | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+| >USCH to be Added or Modified | | 0..<maxNo OfUSCHs> | | | GLOBAL | ignore |
+| >>USCH ID | M | | 9.2.3.14 | | – | |
+| >>Transport Format Management | M | | 9.2.3.13 | | – | |
+| >>Binding ID | O | | 9.2.1.3 | | – | |
+| >>Transport Layer Address | O | | 9.2.1.62 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >Uplink Timing Advance Control LCR | O | | 9.2.3.13K | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >Secondary CCPCH Info TDD LCR | O | | 9.2.3.7F | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >Secondary CCPCH Info 7.68Mcps TDD | O | | 9.2.3.22 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| >UARFCN | O | | 9.2.1.66 | Applicable to 1.28Mcps TDD only. Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (3GPP TS 25.105). | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| HS-DSCH Information Response | O | | HS-DSCH TDD Information Response 9.2.3.3ab | | YES | ignore |
+| DSCH-RNTI | O | | 9.2.3.3ah | | YES | ignore |
+| MAC-hs Reset Indicator | O | | 9.2.1.34B | | YES | ignore |
+| E-DCH Information Response | O | | E-DCH TDD Information Response 9.2.3.41 | 3.84Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 7.68Mcps | O | | E-DCH TDD Information Response 7.68Mcps 9.2.3.52 | 7.68Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 1.28Mcps | O | | E-DCH TDD Information Response 1.28Mcps 9.2.3.41a | 1.28Mcps TDD only. | YES | ignore |
+| PowerControl GAP | O | | INTEGER (1..255) | 1.28Mcps TDD only. | YES | ignore |
+| Idle Interval Information | O | | 9.2.3.60 | TDD only | YES | ignore |
+| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.63 | 1.28 Mcps TDD only. | YES | ignore |
+| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.68 | 1.28 Mcps TDD only. | YES | ignore |
+| E-DCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.69 | 1.28 Mcps TDD only. | YES | ignore |
+| E-RNTI for FACH | O | | E-RNTI 9.2.1.94 | 1.28 Mcps TDD only. | YES | ignore |
+| H-RNTI for FACH | O | | HS-DSCH-RNTI 9.2.1.30P | 1.28 Mcps TDD only. | YES | ignore |
+| DCH Measurement Occasion | O | | 9.2.3.75 | 1.28 Mcps TDD | YES | reject |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Information | | | | only. | | |
+| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.78 | 1.28 Mcps TDD only. | YES | ignore |
+| MU-MIMO Information | O | | 9.2.3.81 | 1.28 Mcps TDD only. | YES | reject |
+
+Note 1: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfRLs are represented by separate ASN.1 structures with different criticalities.
+
+| Range bound | Explanation |
+|-------------------------|------------------------------------------------------------------------|
+| maxNrOfDSCHs | Maximum number of DSCHs for one UE. |
+| maxNrOfUSCHs | Maximum number of USCHs for one UE. |
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+| maxNrOfTS | Maximum number of Timeslots for a UE for 3.84Mcps TDD or 7.68Mcps TDD. |
+| maxNrOfDPCHs | Maximum number of DPCH for a UE for 3.84Mcps TDD. |
+| maxNrOfTS_LCR | Maximum number of Timeslots for a UE for 1.28Mcps TDD. |
+| maxNrOfDPCHs_LCR | Maximum number of DPCH for a UE for 1.28Mcps TDD. |
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+| maxNrOfDPCHs768 | Maximum number of DPCH for a UE for 7.68Mcps TDD. |
+
+### 9.1.13 RADIO LINK RECONFIGURATION COMMIT
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CFN | M | | 9.2.1.9 | | YES | ignore |
+| Active Pattern Sequence Information | O | | 9.2.2.A | FDD only. | YES | ignore |
+| Fast Reconfiguration Mode | O | | 9.2.2.70 | FDD only. | YES | reject |
+
+### 9.1.14 RADIO LINK RECONFIGURATION FAILURE
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|-------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Cause Level | M | | | | YES | ignore |
+| > General | | | | | – | |
+| >> Cause | M | | 9.2.1.5 | | – | |
+| > RL Specific | | | | | – | |
+| >> RLs Causing Reconfiguration Failure | | 0.. maxNrOfRLs | | | EACH | ignore |
+| >>> RL ID | M | | 9.2.1.49 | | – | |
+| >>> Cause | M | | 9.2.1.5 | | – | |
+| >>> Max UE DTX Cycle | | C-DTX-CycleNotAvailable | 9.2.2.87 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+| Condition | Explanation |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------|
+| DTX-CycleNotAvailable | The IE shall be present if the Cause IE is set to “Continuous Packet Connectivity UE DTX Cycle not Available “. |
+
+| Range bound | Explanation |
+|-------------------|---------------------------------|
+| maxNrOfRLs | Maximum number of RLs for a UE. |
+
+### 9.1.15 RADIO LINK RECONFIGURATION CANCEL
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+
+### 9.1.16 RADIO LINK RECONFIGURATION REQUEST
+
+#### 9.1.16.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|------------------|-------------------------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Allowed Queuing Time | O | | 9.2.1.2 | | YES | reject |
+| UL DPCH Information | | 0..1 | | | YES | reject |
+| >TFCS | O | | 9.2.1.63 | TFCS for the UL. | – | |
+| >UL DPDCH Indicator For E-DCH Operation | O | | 9.2.2.52A | | YES | reject |
+| DL DPCH Information | | 0..1 | | | YES | reject |
+| >TFCS | O | | 9.2.1.63 | TFCS for the DL. | – | |
+| >TFCI Signalling Mode | O | | 9.2.2.46 | | – | |
+| >Limited Power Increase | O | | 9.2.2.21A | | – | |
+| DCHs To Modify | O | | FDD DCHs To Modify 9.2.2.13C | | YES | reject |
+| DCHs To Add | O | | DCH FDD Information 9.2.2.4A | | YES | reject |
+| DCHs To Delete | | 0.. | | | GLOBAL | reject |
+| >DCH ID | M | | 9.2.1.16 | | – | |
+| Transmission Gap Pattern Sequence Information | O | | 9.2.2.47A | | YES | reject |
+| RL Information | | 0.. | | | EACH | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | – | |
+| >RL specific E-DCH Information | O | | 9.2.2.35a | | YES | reject |
+| >E-DCH RL Indication | O | | 9.2.2.4E | | YES | reject |
+| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.100 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.124 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Removal | O | | Non-Serving RL Preconfiguration Setup 9.2.2.124 | | YES | ignore |
+| >F-TPICH Information Reconf | O | | 9.2.2.142 | | YES | ignore |
+| DL Reference Power Information | O | | 9.2.2.10C | | YES | ignore |
+| HS-DSCH Information | O | | HS-DSCH FDD Information 9.2.2.19a | | YES | reject |
+| HS-DSCH Information To Modify Unsynchronised | O | | 9.2.1.30NA | | YES | reject |
+| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information 9.2.1.30OA | | YES | reject |
+| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.30OB | | YES | reject |
+| HS-PDSCH RL ID | O | | RL ID 9.2.1.49 | | YES | reject |
+
+| | | | | | | |
+|---------------------------------------------------------------------|---|------------------------------------|-----------------------------------------|-----------------------------------------------------------------|------|--------|
+| E-DPCH Information | | 0..1 | | | YES | reject |
+| >Maximum Set of E-DPDCHs | O | | 9.2.2.24e | | – | |
+| >Puncture Limit | O | | 9.2.1.46 | | – | |
+| >E-TFCS Information | O | | 9.2.2.4G | | – | |
+| >E-TTI | O | | 9.2.2.4J | | – | |
+| >E-DPCCH Power Offset | O | | 9.2.2.4K | | – | |
+| >E-RGCH 2-Index-Step Threshold | O | | 9.2.2.64 | | – | |
+| >E-RGCH 3-Index-Step Threshold | O | | 9.2.2.65 | | – | |
+| >HARQ Info for E-DCH | O | | 9.2.2.66 | | – | |
+| >Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.102 | | YES | ignore |
+| >HS-DSCH Configured Indicator | O | | 9.2.2.19C | | – | |
+| E-DCH FDD Information | O | | 9.2.2.4B | | YES | reject |
+| E-DCH FDD Information to Modify | O | | 9.2.2.4F | | YES | reject |
+| E-DCH MAC-d Flows to Add | O | | E-DCH MAC-d flows Information 9.2.2.4MC | | YES | reject |
+| E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | YES | reject |
+| Serving E-DCH RL | O | | 9.2.2.38C | | YES | reject |
+| CPC Information | | 0..1 | | | YES | reject |
+| >Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.72 | | – | |
+| >Continuous Packet Connectivity DTX-DRX Information To Modify | O | | 9.2.2.73 | | – | |
+| >Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.74 | | – | |
+| >Continuous Packet Connectivity HS-SCCH less Deactivate Indicator | O | | 9.2.2.75A | | YES | reject |
+| No of Target Cell HS-SCCH Order | O | | INTEGER (1..30) | | YES | ignore |
+| Additional HS Cell Information RL Reconf Req | | 0..<maxNrOfHSDSC H-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject |
+| >HS-PDSCH RL ID | M | | RL ID 9.2.1.49 | | – | |
+| >C-ID | O | | 9.2.1.6 | | – | |
+| >HS-DSCH FDD Secondary Serving Information | O | | 9.2.2.19aa | | – | |
+| >HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised | O | | 9.2.2.19bc | | – | |
+| >HS-DSCH Secondary Serving Remove | O | | NULL | | – | |
+
+| | | | | | | |
+|------------------------------------------------------------------------------------------|---|--------------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|
+| UE Aggregate Maximum Bit Rate | O | | 9.2.1.137 | | YES | ignore |
+| Additional E-DCH Cell Information RL Reconf Req | | 0..1 | | For E-DCH on multiple frequencies in this DRNS. | YES | reject |
+| >CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency | M | | | | YES | reject |
+| >>Setup | | | | Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current UE context. | – | |
+| >>>Multicell E-DCH Transport Bearer Mode | M | | 9.2.2.113 | | – | |
+| >>> Additional E-DCH Cell Information Setup | | 1.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>Additional E-DCH FDD Setup Information | M | | 9.2.2.110 | | – | |
+| >> Configuration Change | | | | Used when RLs with additional E-DCH on the secondary UL frequency exist in the current UE context and the configuration is modified (adding new RLs or modification of existing RLs). | – | |
+| >>> Additional E-DCH Cell Information Configuration Change | | 1.. | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>Additional E-DCH Configuration Change Information | M | | 9.2.2.111 | | – | |
+| >> Removal | | | | Used when all RLs on the indicated secondary UL | – | |
+
+| | | | | | | |
+|--------------------------------------------------------------|---|---------------------------------|--------------------------|-------------------------------------------------------------------|-----|--------|
+| | | | | frequency is removed. | | |
+| >>>Additional E-DCH Cell Information Removal | | 1..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency – max 1 in this 3GPP release. | – | |
+| >>>>RL on Secondary UL Frequency | M | | ENUMERATED (Remove, . .) | Removal of all RL on secondary UL frequency. | – | |
+| UL CLTD Information Reconf | O | | 9.2.2.130 | | YES | reject |
+
+| Range Bound | Explanation |
+|------------------------|---------------------------------------------------------------|
+| maxNrOfDCHs | Maximum number of DCHs for one UE. |
+| maxNrOfRLs | Maximum number of RLs for a UE. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE |
+
+#### 9.1.16.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-----------------------------------|-----------------------------------------------|-------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Allowed Queuing Time | O | | 9.2.1.2 | | YES | reject |
+| UL CCTrCH Information To Modify | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | O | | 9.2.1.63 | | – | |
+| >UL SIR Target | O | | Uplink SIR
9.2.1.69 | Applicable to 1.28Mcps TDD only. | YES | reject |
+| UL CCTrCH Information to Delete | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| DL CCTrCH Information To Modify | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >TFCS | O | | 9.2.1.63 | | – | |
+| DL CCTrCH Information to Delete | | 0..<max NrOfCCTrCHs> | | | EACH | notify |
+| >CCTrCH ID | M | | 9.2.3.2 | | – | |
+| DCHs To Modify | O | | TDD DCHs To Modify
9.2.3.8B | | YES | reject |
+| DCHs To Add | O | | DCH TDD Information
9.2.3.2A | | YES | reject |
+| DCHs to Delete | | 0..<max NrOfDCHs> | | | GLOBAL | reject |
+| >DCH ID | M | | 9.2.1.16 | | – | |
+| RL Information | | 0..<max NrOfRLs> | | | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >RL Specific DCH Information | O | | 9.2.1.49A | | – | |
+| UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD. | YES | ignore |
+| >Uplink Synchronisation Step Size | M | | 9.2.3.13J | | – | |
+| >Uplink Synchronisation Frequency | M | | 9.2.3.13I | | – | |
+| HS-DSCH Information | O | | HS-DSCH TDD Information
9.2.3.3aa | | YES | reject |
+| HS-DSCH Information To Modify Unsynchronised | O | | 9.2.1.30NA | | YES | reject |
+| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information
9.2.1.30OA | | YES | reject |
+| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.30OB | | YES | reject |
+| HS-PDSCH RL ID | O | | RL ID | | YES | reject |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| | | | 9.2.1.49 | | | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------------------------------------------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------|
+| E-DCH Information | | 0..1 | | 3.84Mcps
TDD only. | YES | reject |
+| >E-PUCH Information | O | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | O | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows to Add | O | | 9.2.3.38 | | – | |
+| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | – | |
+| >E-DCH TDD Information | O | | 9.2.3.40 | | – | |
+| >E-DCH TDD Information to Modify | O | | 9.2.3.42 | | – | |
+| E-DCH Serving RL | O | | RL ID
9.2.1.49 | 3.84Mcps
TDD only. | YES | reject |
+| E-DCH Information
7.68Mcps | | 0..1 | | 7.68Mcps
TDD only. | YES | reject |
+| >E-PUCH Information | O | | 9.2.3.36 | | – | |
+| >E-TFCS Information TDD | O | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows to Add | O | | 9.2.3.38 | | – | |
+| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | – | |
+| >E-DCH TDD Information
7.68Mcps | O | | 9.2.3.51 | | – | |
+| >E-DCH TDD Information to Modify | O | | 9.2.3.42 | | – | |
+| E-DCH Information
1.28Mcps | | 0..1 | | 1.28Mcps
TDD only. | YES | reject |
+| >E-PUCH Information LCR | O | | 9.2.3.36a | | – | |
+| >E-TFCS Information TDD | O | | 9.2.3.37 | | – | |
+| >E-DCH MAC-d Flows to Add | O | | 9.2.3.38 | | – | |
+| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.90 | | – | |
+| >E-DCH TDD Information
LCR | O | | 9.2.3.40a | | – | |
+| >E-DCH TDD Information to Modify | O | | 9.2.3.42 | | – | |
+| Need for Idle Interval | O | | ENUMERATED (True, False) | TDD only. | YES | ignore |
+| CPC Information | | 0..1 | | | YES | reject |
+| >Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.61 | | – | |
+| >Continuous Packet Connectivity DRX Information To Modify LCR | O | | 9.2.3.62 | | – | |
+| >HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.64 | | – | |
+| >HS-DSCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.65 | | – | |
+| >HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.70 | | – | |
+| >E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.66 | | – | |
+| >E-DCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.67 | | – | |
+| >E-DCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.71 | | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|-----------------------------|-----------------------|---------------------------------------------------------------------|-------------|----------------------|
+| RNTI Allocation Indicator | O | | ENUMERATED (True) | 1.28 Mcps TDD only. | YES | ignore |
+| DCH Measurement Type indicator | O | | 9.2.3.76 | 1.28 Mcps TDD only. | YES | reject |
+| Multi-Carrier E-DCH Information Reconf | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only. | YES | reject |
+| >CHOICE continue, Setup or Change | M | | | | – | |
+| >> continue | | | | | – | |
+| >> Setup | | | | | – | |
+| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.79 | | – | |
+| >>>Multi-Carrier E-DCH Information LCR | M | | 9.2.3.77 | | – | |
+| >> Change | | | | | – | |
+| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | O | | 9.2.3.79 | | – | |
+| >>>Multi-Carrier E-DCH Information LCR | O | | 9.2.3.77 | | – | |
+| >>>Removal UL Multi-Carrier info | | 0.. | | | – | |
+| >>>>UARFCN | M | | 9.2.1.66 | Corresponds to Nt TS 25.105 [17]. | – | |
+| MU-MIMO Indicator | O | | 9.2.3.82 | 1.28 Mcps TDD only. | YES | reject |
+
+| Range Bound | Explanation |
+|-----------------------------|------------------------------------------------------------------------|
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+| maxNrOfDCHs | Maximum number of DCHs for one UE. |
+| maxNrOfRLs | Maximum number of RLs for one UE |
+| maxNrOfULCarriersLCR | Maximum number of uplink frequencies in Multi-Carrier E-DCH Operation. |
+
+### 9.1.17 RADIO LINK RECONFIGURATION RESPONSE
+
+#### 9.1.17.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------|----------|----------------------|-----------------------------------------------|-----------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information Response | | 0.. | | | EACH | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >Maximum Uplink SIR | O | | Uplink SIR
9.2.1.69 | | – | |
+| >Minimum Uplink SIR | O | | Uplink SIR
9.2.1.69 | | – | |
+| >Maximum DL TX Power | O | | DL Power
9.2.1.21A | | – | |
+| >Minimum DL TX Power | O | | DL Power
9.2.1.21A | | – | |
+| >Not Used | O | | NULL | | – | |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >DL Code Information | O | | FDD DL Code Information
9.2.2.14A | | YES | ignore |
+| >DL Power Balancing Updated Indicator | O | | 9.2.2.10D | | YES | ignore |
+| >E-DCH FDD Information Response | O | | 9.2.2.4C | | YES | ignore |
+| >E-DCH RL Set ID | O | | RL Set ID
9.2.2.35 | | YES | ignore |
+| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.4D | | YES | ignore |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >HS-DSCH Preconfiguration Info | O | | 9.2.2.99 | | YES | ignore |
+| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.125 | | YES | ignore |
+| >F-TPICH Information Response | O | | 9.2.2.143 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| HS-DSCH Information Response | O | | HS-DSCH FDD Information Response
9.2.2.19b | | YES | ignore |
+| MAC-hs Reset Indicator | O | | 9.2.1.34B | | YES | ignore |
+| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.75 | | YES | ignore |
+| Additional HS Cell Information Response | | 0.. | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore |
+| >HS-PDSCH RL ID | M | | RL ID
9.2.1.49 | | – | |
+| >HS-DSCH-RNTI | M | | 9.2.1.30P | | – | |
+| >HS-DSCH FDD Secondary Serving Information Response | M | | 9.2.2.19ba | | – | |
+| Additional E-DCH Cell Information Response RLReconf | | 0.. | | E-DCH on Secondary uplink | EACH | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------|-------------|----------------------|
+| | | | | frequency – max 1 in this 3GPP release. | | |
+| >Additional E-DCH FDD Information Response | O | | 9.2.2.120 | For new E-DCH Radio Links on secondary carrier. | – | |
+| >Additional Modified E-DCH FDD Information Response | O | | 9.2.2.121 | | – | |
+
+| Range Bound | Explanation |
+|------------------------|---------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for a UE. |
+| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. |
+| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE. |
+
+#### 9.1.17.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|------------------------------------|--------------------------------------------|---------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information Response | | 0..<max NrOfRL s> | | See note 1 below. | YES | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >Maximum Uplink SIR | O | | Uplink SIR 9.2.1.69 | | – | |
+| >Minimum Uplink SIR | O | | Uplink SIR 9.2.1.69 | | – | |
+| >Maximum DL TX Power | O | | DL Power 9.2.1.21A | | – | |
+| >Minimum DL TX Power | O | | DL Power 9.2.1.21A | | – | |
+| >DCH Information Response | O | | 9.2.1.16A | | YES | ignore |
+| >DL CCTrCH Information | | 0..<max NrOfCC TrCHs> | | For DCH. | GLOBAL | ignore |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH To Modify LCR | | 0..1 | | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| >>>DL Timeslot Information LCR | | 0..<max NrOfTs LCR> | | | – | |
+| >>>>Time Slot LCR | M | | 9.2.3.12a | | – | |
+| >>>>Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH. | – | |
+| >>>>Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH. | – | |
+| >>CCTrCH Maximum DL TX Power | O | | DL Power 9.2.1.21A | Maximum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | YES | ignore |
+| >>CCTrCH Minimum DL TX Power | O | | DL Power 9.2.1.21A | Minimum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only. | YES | ignore |
+| >Uplink Timing Advance Control LCR | O | | 9.2.3.13K | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| HS-DSCH Information Response | O | | HS-DSCH TDD Information Response 9.2.3.3ab | | YES | ignore |
+| MAC-hs Reset Indicator | O | | 9.2.1.34B | | YES | ignore |
+| E-DCH Information Response | O | | E-DCH TDD Information Response 9.2.3.41 | 3.84Mcps TDD only. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-------|---------------------------------------------------|-----------------------|-------------|----------------------|
+| E-DCH Information Response 7.68Mcps | O | | E-DCH TDD Information Response 7.68Mcps 9.2.3.52 | 7.68Mcps TDD only. | YES | ignore |
+| E-DCH Information Response 1.28Mcps | O | | E-DCH TDD Information Response 1.28Mcps 9.2.3.41a | 1.28Mcps TDD only. | YES | ignore |
+| PowerControl GAP | O | | INTEGER (1..255) | 1.28Mcps TDD only. | YES | ignore |
+| Idle Interval Information | O | | 9.2.3.60 | TDD only. | YES | ignore |
+| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.63 | 1.28 Mcps TDD only. | YES | ignore |
+| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.68 | 1.28 Mcps TDD only. | YES | ignore |
+| E-DCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.69 | 1.28 Mcps TDD only. | YES | ignore |
+| E-RNTI for FACH | O | | E-RNTI 9.2.1.94 | 1.28 Mcps TDD only. | YES | ignore |
+| H-RNTI for FACH | O | | HS-DSCH-RNTI 9.2.1.30P | 1.28 Mcps TDD only. | YES | ignore |
+| DCH Measurement Occasion Information | O | | 9.2.3.75 | 1.28 Mcps TDD only. | YES | reject |
+| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.78 | 1.28 Mcps TDD only. | YES | ignore |
+| MU-MIMO Information | O | | 9.2.3.81 | 1.28 Mcps TDD only. | YES | reject |
+
+Note 1: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfRLs are represented by separate ASN.1 structures with different criticalities.
+
+| Range bound | Explanation |
+|-----------------------|--------------------------------------------------------|
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+| maxNrOfTsLCR | Maximum number of Timeslots for a UE for 1.28Mcps TDD. |
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+
+### 9.1.18 RADIO LINK FAILURE INDICATION
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------|----------|--------------------|-----------------------|-------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Reporting Object | M | | | Object for which the Failure shall be reported. | YES | ignore |
+| >RL | | | | | – | |
+| >>RL Information | | 1.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>Cause | M | | 9.2.1.5 | | – | |
+| >RLS | | | | FDD only. | – | |
+| >>RL Set Information | | 1.. | | | EACH | ignore |
+| >>>RL Set ID | M | | 9.2.2.35 | | – | |
+| >>>Cause | M | | 9.2.1.5 | | – | |
+| >CCTrCH | | | | TDD only. | – | |
+| >>RL ID | M | | 9.2.1.49 | | – | |
+| >>CCTrCH List | | 1.. | | | EACH | ignore |
+| >>>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>>Cause | M | | 9.2.1.5 | | – | |
+
+| Range bound | Explanation |
+|-----------------------|---------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+| maxNrOfRLSets | Maximum number of RL Sets for one UE. |
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+
+### 9.1.19 RADIO LINK RESTORE INDICATION
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------|----------|--------------------|-----------------------|-----------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Reporting Object | M | | | Object for which the Restoration shall be reported. | YES | ignore |
+| >RL | | | | TDD only. | – | |
+| >>RL Information | | 1.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >RLS | | | | FDD only. | – | |
+| >>RL Set Information | | 1.. | | | EACH | ignore |
+| >>>RL Set ID | M | | 9.2.2.35 | | – | |
+| >CCTrCH | | | | TDD only. | – | |
+| >>RL ID | M | | 9.2.1.49 | | – | |
+| >>CCTrCH List | | 1.. | | | EACH | ignore |
+| >>>CCTrCH ID | M | | 9.2.3.2 | | – | |
+
+| Range bound | Explanation |
+|-----------------------|---------------------------------------|
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+| maxNrOfRLSets | Maximum number of RL Sets for one UE. |
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+
+### 9.1.20 DL POWER CONTROL REQUEST [FDD]
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------------------------------|----------------------|-----------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Power Adjustment Type | M | | 9.2.2.28 | | YES | ignore |
+| DL Reference Power | C-Common | | DL Power 9.2.1.21A | | YES | ignore |
+| Inner Loop DL PC Status | O | | 9.2.2.21a | | YES | ignore |
+| DL Reference Power Information | C-Individual | 1.. | | | EACH | ignore |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >DL Reference Power | M | | DL Power 9.2.1.21A | | – | |
+| Max Adjustment Step | C-CommonOrIndividual | | 9.2.2.23 | | YES | ignore |
+| Adjustment Period | C-CommonOrIndividual | | 9.2.2.B | | YES | ignore |
+| Adjustment Ratio | C-CommonOrIndividual | | 9.2.2.C | | YES | ignore |
+
+| Condition | Explanation |
+|--------------------|----------------------------------------------------------------------------------------------------|
+| Common | The IE shall be present if the Power Adjustment Type IE is set to "Common". |
+| Individual | The IE shall be present if the Power Adjustment Type IE is set to "Individual". |
+| CommonOrIndividual | The IE shall be present if the Power Adjustment Type IE is set to "Common" or "Individual". |
+
+| Range Bound | Explanation |
+|-------------------|-----------------------------------|
+| maxNrOfRLs | Maximum number of RLs for one UE. |
+
+### 9.1.21 PHYSICAL CHANNEL RECONFIGURATION REQUEST
+
+#### 9.1.21.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|-----------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information | | 1 | | | YES | reject |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | YES | notify |
+| >F-DPCH Slot Format | O | | 9.2.2.85 | | YES | ignore |
+| >F-TPICH Reconfiguration Information | O | | 9.2.2.144 | | YES | ignore |
+
+#### 9.1.21.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|---------------------|---------------------------------------|----------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| RL Information | | 1 | | | YES | reject |
+| >RL ID | M | | 9.2.1.49 | | – | |
+| >UL CCTrCH Information | | 0.. | | | GLOBAL | reject |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>UL DPCH Information | | 1 | | | YES | notify |
+| >>>Repetition Period | O | | 9.2.3.7 | | – | |
+| >>>Repetition Length | O | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | O | | 9.2.3.8A | | – | |
+| >>>UL Timeslot Information | | 0.. | | Applicable to 3.84Mcps TDD only. | – | |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type | O | | 9.2.3.4 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>UL Code Information | O | | TDD UL Code Information 9.2.3.10A | | – | |
+| >>>UL Timeslot Information LCR | | 0.. | | Applicable to 1.28Mcps TDD only. | GLOBAL | reject |
+| >>>>Time Slot LCR | M | | 9.2.3.12a | | – | |
+| >>>>Midamble Shift LCR | O | | 9.2.3.4C | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>UL Code Information LCR | O | | TDD UL Code Information LCR 9.2.3.10B | | – | |
+| >>>>PLCCH Information | O | | 9.2.3.17 | | YES | Reject |
+| >>>UL Timeslot Information 7.68Mcps | | 0.. | | Applicable to 7.68Mcps TDD only. | GLOBAL | reject |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type 7.68Mcps | O | | 9.2.3.23 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>UL Code Information 7.68Mcps | O | | TDD UL Code Information 9.2.3.27 | | – | |
+| >DL CCTrCH Information | | 0.. | | | GLOBAL | reject |
+| >>CCTrCH ID | M | | 9.2.3.2 | | – | |
+| >>DL DPCH Information | | 1 | | | YES | notify |
+| >>>Repetition Period | O | | 9.2.3.7 | | – | |
+| >>>Repetition Length | O | | 9.2.3.6 | | – | |
+| >>>TDD DPCH Offset | O | | 9.2.3.8A | | – | |
+| >>>DL Timeslot Information | | 0.. | | Applicable to 3.84Mcps TDD only. | – | |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift | O | | 9.2.3.4 | | – | |
+
+| | | | | | | |
+|------------------------------------------------------------|---|----------------------------------|-------------------------------------------|----------------------------------|--------|--------|
+| And Burst Type | | | | | | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>DL Code Information | O | | TDD DL Code Information 9.2.3.8C | | – | |
+| >>>DL Timeslot Information LCR | | 0..<maxNrOfTsLCR> | | Applicable to 1.28Mcps TDD only. | GLOBAL | reject |
+| >>>>Time Slot LCR | M | | 9.2.3.12a | | – | |
+| >>>>Midamble Shift LCR | O | | 9.2.3.4C | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>DL Code Information LCR | O | | TDD DL Code Information LCR 9.2.3.8D | | – | |
+| >>>DL Timeslot Information 7.68Mcps | | 0..<maxNrOfTs> | | Applicable to 7.68Mcps TDD only. | GLOBAL | reject |
+| >>>>Time Slot | M | | 9.2.1.56 | | – | |
+| >>>>Midamble Shift And Burst Type 7.68Mcps | O | | 9.2.3.23 | | – | |
+| >>>>TFCI Presence | O | | 9.2.1.55 | | – | |
+| >>>>DL Code Information 7.68Mcps | O | | TDD DL Code Information 7.68Mcps 9.2.3.29 | | – | |
+| >HS-PDSCH Timeslot Specific Information | | 0..<maxNrOfDLTs> | | Applicable to 3.84Mcps TDD only. | GLOBAL | reject |
+| >>Time Slot | M | | 9.2.1.56 | | – | |
+| >>Midamble Shift And Burst Type | M | | 9.2.3.4 | | – | |
+| >HS-PDSCH Timeslot Specific Information LCR | | 0..<maxNrOfDLTsLCR> | | Applicable to 1.28Mcps TDD only. | GLOBAL | reject |
+| >>Time Slot LCR | M | | 9.2.3.12a | | – | |
+| >>Midamble Shift LCR | M | | 9.2.3.4C | | – | |
+| >HS-PDSCH Timeslot Specific Information 7.68Mcps | | 0..<maxNrOfDLTs> | | Applicable to 7.68Mcps TDD only. | GLOBAL | reject |
+| >>Time Slot | M | | 9.2.1.56 | | – | |
+| >>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.23 | | – | |
+| >UARFCN | O | | 9.2.1.66 | Applicable to 1.28Mcps TDD only. | YES | ignore |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------------------------------|
+| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE. |
+| maxNrOfTS | Maximum number of Timeslots for a UE for 3.84Mcps TDD or 7.68Mcps TDD. |
+| maxNrOfTsLCR | Maximum number of Timeslots for a UE for 1.28Mcps TDD. |
+| maxNrOfDLTs | Maximum number of downlink time slots per Radio Link for 3.84Mcps TDD or 7.68Mcps TDD. |
+| maxNrOfDLTsLCR | Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD. |
+
+### 9.1.22 PHYSICAL CHANNEL RECONFIGURATION COMMAND
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CFN | M | | 9.2.1.9 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+### 9.1.23 PHYSICAL CHANNEL RECONFIGURATION FAILURE
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Cause | M | | 9.2.1.5 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+
+### 9.1.24 UPLINK SIGNALLING TRANSFER INDICATION
+
+#### 9.1.24.1 FDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| UC-ID | M | | 9.2.1.71 | | YES | ignore |
+| SAI | M | | 9.2.1.52 | | YES | ignore |
+| Cell GA1 | O | | 9.2.1.5A | | YES | ignore |
+| C-RNTI | M | | 9.2.1.14 | | YES | ignore |
+| S-RNTI | M | | 9.2.1.53 | If the Extended S-RNTI IE is included in the message, the S-RNTI IE shall be ignored. | YES | ignore |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| Propagation Delay | M | | 9.2.2.33 | | YES | ignore |
+| STTD Support Indicator | M | | 9.2.2.45 | | YES | ignore |
+| Closed Loop Mode1 Support Indicator | M | | 9.2.2.2 | | YES | ignore |
+| L3 Information | M | | 9.2.1.32 | | YES | ignore |
+| CN PS Domain Identifier | O | | 9.2.1.12 | | YES | ignore |
+| CN CS Domain Identifier | O | | 9.2.1.11 | | YES | ignore |
+| URA Information | O | | 9.2.1.70B | | YES | ignore |
+| Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| DPC Mode Change Support Indicator | O | | 9.2.2.56 | | YES | ignore |
+| Common Transport Channel Resources Initialisation Not Required | O | | 9.2.1.12F | | YES | ignore |
+
+| | | | | | | |
+|-----------------------------------------|---------------------|---------------------------------------------|------------------------------------------|-----------------------------------------------------------------------------------------------------|--------|--------|
+| Cell Capability Container FDD | O | | 9.2.2.D | | YES | ignore |
+| SNA Information | O | | 9.2.1.52Ca | | YES | ignore |
+| Cell Portion ID | O | | 9.2.2.E | | YES | ignore |
+| Active MBMS Bearer Service List | | 0..<maxNrOfActiveMBMSServices> | | | GLOBAL | ignore |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| >Transmission Mode | M | | 9.2.1.81 | | – | |
+| Inter-frequency Cell List | | 0..<maxCellsMeas> | | | GLOBAL | ignore |
+| >DL UARFCN | M | | UARFCN
9.2.1.66 | | – | |
+| >UL UARFCN | O | | UARFCN
9.2.1.66 | | – | |
+| >Primary Scrambling Code | M | | 9.2.1.45 | | – | |
+| Extended Propagation Delay | O | | 9.2.2.33a | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| Multiple PLMN List | O | | 9.2.1.117 | | YES | ignore |
+| E-RNTI | O | | 9.2.1.94 | | YES | ignore |
+| Max UE DTX Cycle | C-DTX-DRXCapability | | 9.2.2.87 | | YES | ignore |
+| Cell Capability Container Extension FDD | O | | 9.2.2.123 | | YES | ignore |
+| Secondary Serving Cell List | O | | 9.2.2.101 | | YES | ignore |
+| Dual Band Secondary Serving Cell List | O | | Secondary Serving Cell List
9.2.2.101 | | YES | ignore |
+| Extended S-RNTI | O | | Extended RNTI
9.2.1.154 | The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. | YES | ignore |
+
+| Condition | Explanation |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DTX-DRXCapability | The IE shall be present if the Continuous Packet Connectivity DTX-DRX Support Indicator IE in Cell Capability Container FDD IE is set to 1. |
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+| maxCellsMeas | Maximum number of inter-frequency cells measured by a UE. |
+
+#### 9.1.24.2 TDD Message
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------------------------------------------|----------|-----------------------------------------------|-------------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| UC-ID | M | | 9.2.1.71 | | YES | ignore |
+| SAI | M | | 9.2.1.52 | | YES | ignore |
+| Cell GA | O | | 9.2.1.5A | | YES | ignore |
+| C-RNTI | M | | 9.2.1.14 | | YES | ignore |
+| S-RNTI | M | | 9.2.1.53 | If the Extended S-RNTI IE is included in the message, the S-RNTI IE shall be ignored. | YES | ignore |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| Rx Timing Deviation | M | | 9.2.3.7A | | YES | ignore |
+| L3 Information | M | | 9.2.1.32 | | YES | ignore |
+| CN PS Domain Identifier | O | | 9.2.1.12 | | YES | ignore |
+| CN CS Domain Identifier | O | | 9.2.1.11 | | YES | ignore |
+| URA Information | O | | 9.2.1.70B | | YES | ignore |
+| Cell GA Additional Shapes | O | | 9.2.1.5B | | YES | ignore |
+| Common Transport Channel Resources Initialisation Not Required | O | | 9.2.1.12F | | YES | ignore |
+| Cell Capability Container TDD | O | | 9.2.3.1a | Applicable to 3.84Mcps TDD only. | YES | ignore |
+| Cell Capability Container TDD LCR | O | | 9.2.3.1b | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| SNA Information | O | | 9.2.1.52Ca | | YES | ignore |
+| Active MBMS Bearer Service List | | O..<max NrOfActiveMBMSService s> | | | GLOBAL | ignore |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| >Transmission Mode | M | | 9.2.1.81 | | – | |
+| Cell Capability Container 7.68Mcps TDD | O | | 9.2.3.31 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| Rx Timing Deviation 7.68Mcps | O | | 9.2.3.30 | Applicable to 7.68Mcps TDD only. | YES | ignore |
+| Rx Timing Deviation 3.84Mcps Extended | O | | 9.2.3.35 | Applicable to 3.84Mcps TDD only. | YES | ignore |
+| Multiple PLMN List | O | | 9.2.1.117 | | YES | ignore |
+| HS-DSCH-RNTI | O | | 9.2.1.30P | | YES | ignore |
+| E-RNTI | O | | 9.2.1.94 | | YES | ignore |
+| Cell Portion LCR ID | O | | 9.2.3.73 | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| Cell Capability Container Extension TDD LCR | O | | 9.2.3.80 | Applicable to 1.28Mcps TDD only. | YES | ignore |
+| Extended S-RNTI | O | | Extended RNTI 9.2.1.154 | The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger | YES | ignore |
+
+| | | | | | | |
+|--|--|--|--|------------------|--|--|
+| | | | | than
1048575. | | |
+|--|--|--|--|------------------|--|--|
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------|
+| maxNrOfActiveMBMSServices | Maximum number of MBMS bearer services that are active in parallel. |
+
+### 9.1.24A GERAN UPLINK SIGNALLING TRANSFER INDICATION
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|----------------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| UC-ID | M | | 9.2.1.71 | UC-ID may be a GERAN cell identifier. | YES | ignore |
+| SAI | M | | 9.2.1.52 | | YES | ignore |
+| S-RNTI | M | | 9.2.1.53 | If the Extended S-RNTI IE is included in the message, the S-RNTI IE shall be ignored. | YES | ignore |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| L3 Information | M | | 9.2.1.32 | | YES | ignore |
+| CN PS Domain Identifier | O | | 9.2.1.12 | | YES | ignore |
+| CN CS Domain Identifier | O | | 9.2.1.11 | | YES | ignore |
+| URA Information | O | | 9.2.1.70B | URA information may be GRA information. | YES | ignore |
+| Extended S-RNTI | O | | Extended RNTI
9.2.1.154 | The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. | YES | ignore |
+
+### 9.1.25 DOWNLINK SIGNALLING TRANSFER REQUEST
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------------------------|----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| C-ID | M | | 9.2.1.6 | May be a GERAN cell identifier. | YES | ignore |
+| D-RNTI | M | | 9.2.1.24 | | YES | ignore |
+| L3 Information | M | | 9.2.1.32 | | YES | ignore |
+| D-RNTI Release Indication | M | | 9.2.1.25 | | YES | ignore |
+| URA-ID | O | | 9.2.1.70 | | YES | ignore |
+| MBMS Bearer Service List | | 0.. | | | GLOBAL | ignore |
+| >TMGI | M | | 9.2.1.80 | | – | |
+| Old URA-ID | O | | URA-ID
9.2.1.70 | | YES | ignore |
+| SRNC-ID | C-URA | | RNC-ID
9.2.1.50 | If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. | YES | ignore |
+| Extended SRNC-ID | O | | Extended RNC-ID
9.2.1.50a | The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| Enhanced PCH Capability | O | | 9.2.1.132 | FDD and 1.28Mcps TDD only. | YES | ignore |
+
+| Condition | Explanation |
+|-----------|-------------------------------------------------------------------------------------|
+| URA | The IE shall be present if the URA-ID IE or Old URA-ID IE is present. |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------|
+| maxNrOfMBMSServices | Maximum number of MBMS bearer services that a UE can join. |
+
+### 9.1.26 RELOCATION COMMIT
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| D-RNTI | O | | 9.2.1.24 | | YES | ignore |
+| RANAP Relocation Information | O | | 9.2.1.47 | | YES | ignore |
+
+### 9.1.27 PAGING REQUEST
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-------|------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | ignore |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| CHOICE Paging Area | M | | | | YES | ignore |
+| >URA | | | | | – | |
+| >>URA-ID | M | | 9.2.1.70 | May be a GRA-ID. | – | |
+| >Cell | | | | UTRAN only. | – | |
+| >>C-ID | M | | 9.2.1.6 | | – | |
+| SRNC-ID | M | | RNC-ID
9.2.1.50 | May be a BSC-ID.
If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. | YES | ignore |
+| S-RNTI | M | | 9.2.1.53 | If the Extended S-RNTI IE is included in the message, the S-RNTI IE shall be ignored. | YES | ignore |
+| IMSI | M | | 9.2.1.31 | | YES | ignore |
+| DRX Cycle Length Coefficient | M | | 9.2.1.26 | | YES | ignore |
+| CN Originated Page to Connected Mode UE | | 0..1 | | | YES | ignore |
+| >Paging Cause | M | | 9.2.1.41E | | – | |
+| >CN Domain Type | M | | 9.2.1.11A | | – | |
+| >Paging Record Type | M | | 9.2.1.41F | | – | |
+| Extended SRNC-ID | O | | Extended RNC-ID
9.2.1.50a | The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject |
+| Enhanced PCH Capability | O | | 9.2.1.132 | FDD and 1.28Mcps
TDD only. | YES | ignore |
+| Extended S-RNTI | O | | Extended RNTI
9.2.1.154 | The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. | YES | ignore |
+
+### 9.1.28 DEDICATED MEASUREMENT INITIATION REQUEST
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|----------------------|----------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Measurement ID | M | | 9.2.1.37 | | YES | reject |
+| CHOICE Dedicated Measurement Object Type | M | | | | YES | reject |
+| >RL | | | | | – | |
+| >>RL Information | | 1.. | | | EACH | reject |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>DPCH ID | O | | 9.2.3.3 | TDD only. | – | |
+| >>>DPCH ID 7.68Mcps | O | | 9.2.3.34 | 7.68Mcps TDD only. | – | |
+| >>>HS-SICH Information | | 0.. | | TDD only. | GLOBAL | reject |
+| >>>>HS-SICH ID | M | | 9.2.3.3ad | | – | |
+| >RLS | | | | FDD only. | – | |
+| >>RL Set Information | | 1.. | | | EACH | reject |
+| >>>RL Set ID | M | | 9.2.2.35 | | – | |
+| >ALL RL | | | NULL | | – | |
+| >ALL RLS | | | NULL | FDD only. | – | |
+| Dedicated Measurement Type | M | | 9.2.1.18 | | YES | reject |
+| Measurement Filter Coefficient | O | | 9.2.1.36 | | YES | reject |
+| Report Characteristics | M | | 9.2.1.48 | | YES | reject |
+| CFN reporting indicator | M | | FN reporting indicator 9.2.1.28A | | YES | reject |
+| CFN | O | | 9.2.1.9 | | YES | reject |
+| Partial Reporting Indicator | O | | 9.2.1.41Fa | | YES | ignore |
+| Measurement Recovery Behavior | O | | 9.2.1.38A | | YES | ignore |
+| Alternative Format Reporting Indicator | O | | 9.2.1.2D | | YES | ignore |
+
+| Range bound | Explanation |
+|----------------------|-----------------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of individual RLs a measurement can be started on. |
+| maxNrOfRLSets | Maximum number of individual RL Sets a measurement can be started on. |
+
+### 9.1.29 DEDICATED MEASUREMENT INITIATION RESPONSE
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|----------|-----------------------------|-----------------------|-----------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Measurement ID | M | | 9.2.1.37 | | YES | ignore |
+| CHOICE Dedicated Measurement Object Type | O | | | Dedicated Measurement Object Type the measurement was initiated with. | YES | ignore |
+| >RL or ALL RL | | | | See Note 1. | – | |
+| >>RL Information | | 1.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>DPCH ID | O | | 9.2.3.3 | TDD only. | – | |
+| >>>DPCH ID 7.68Mcps | O | | 9.2.3.34 | 7.68Mcps TDD only. | – | |
+| >>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >>>CFN | O | | 9.2.1.9 | Dedicated Measurement Time Reference. | – | |
+| >>>HS-SICH ID | O | | 9.2.3.3ad | TDD only | YES | reject |
+| >>>Multiple Dedicated Measurement Value Information | | 0.. | | Applicable to 3.84Mcps TDD only. | GLOBAL | ignore |
+| >>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >>>Multiple Dedicated Measurement Value Information LCR | | 0.. | | Applicable to 1.28Mcps TDD only. | GLOBAL | ignore |
+| >>>>DPCH ID | M | | 9.2.3.3 | | – | |
+| >>>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >>>Multiple HS-SICH Measurement Value Information | | 0.. | | TDD only. | GLOBAL | ignore |
+| >>>>HS-SICH ID | M | | 9.2.3.3ad | | – | |
+| >>>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >>>Multiple Dedicated Measurement Value Information 7.68Mcps | | 0.. | | Applicable to 7.68Mcps TDD only. | GLOBAL | ignore |
+| >>>>DPCH ID 7.68Mcps | M | | 9.2.3.34 | | – | |
+| >>>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >RLS or ALL RLS | | | | FDD only See Note 2. | – | |
+| >>RL Set Information | | 1.. | | | EACH | ignore |
+| >>>RL Set ID | M | | 9.2.2.35 | | – | |
+| >>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >>>CFN | O | | 9.2.1.9 | Dedicated | – | |
+
+| | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|-----------|-----------------------------|-----|--------|
+| | | | | Measurement Time Reference. | | |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | Ignore |
+| Measurement Recovery Support Indicator | O | | 9.2.1.38C | | YES | ignore |
+| Note 1: This is a simplified representation of the ASN.1: there are two different choice tags "RL" and "ALL RL" in the ASN.1, each having exactly the same structure. | | | | | | |
+| Note 2: This is a simplified representation of the ASN.1: there are two different choice tags "RLS" and "ALL RLS" in the ASN.1, each having exactly the same structure. | | | | | | |
+
+| Range bound | Explanation |
+|-----------------------------|----------------------------------------------------------------------------------|
+| maxNrOfRLs | Maximum number of individual RLs the measurement can be started on. |
+| maxNrOfRLSets | Maximum number of individual RL Sets the measurement can be started on. |
+| maxNrOfDPCHsPerRL | Maximum number of DPCHs per RL a measurement can be started on for 3.84Mcps TDD. |
+| maxNrOfDPCHsLCRPerRL | Maximum number of DPCHs per RL a measurement can be started on for 1.28Mcps TDD. |
+| maxNrOfHSSICHs | Maximum number of HSSICHs per RL a measurement can be started on. |
+| maxNrOfDPCHs768PerRL | Maximum number of DPCHs per RL a measurement can be started on for 7.68Mcps TDD. |
+
+### 9.1.30 DEDICATED MEASUREMENT INITIATION FAILURE
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.1.40 | | YES | reject |
+| Transaction ID | M | | 9.2.1.59 | | – | |
+| Measurement ID | M | | 9.2.1.37 | | YES | ignore |
+| Cause | M | | 9.2.1.5 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.1.13 | | YES | ignore |
+| CHOICE Dedicated Measurement Object Type | O | | | Dedicated Measurement Object Type the measurement was initiated with. | YES | ignore |
+| >RL or ALL RL | | | | | – | |
+| >>Unsuccessful RL Information | | 1.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>Individual Cause | O | | Cause 9.2.1.5 | | – | |
+| >>Successful RL Information | | 0.. | | | EACH | ignore |
+| >>>RL ID | M | | 9.2.1.49 | | – | |
+| >>>DPCH ID | O | | 9.2.3.3 | TDD only. | – | |
+| >>>Dedicated Measurement Value | M | | 9.2.1.19 | | – | |
+| >>>CFN | O | | 9.2.1.9 | Dedicated Measurement Time Reference. | – | |
+| >>>HS-SICH ID | O | | 9.2.3.3ad | TDD only. | YES | reject |
+| >RLS or ALL RLS | | | | FDD only. | – | |
+| >>Unsuccessful RL Set Information | | 1..