@@ -602,7 +602,6 @@ Inter-frequency and inter-RAT test cases are performed without frequency overlap
>\- For bands with bandwidth not accommodating all the NR cells required in the test without frequency overlapping, inter band testing shall be done according to clause 3A.5. If the UE does not support the combination given in clause 3A.5, the relevant tests are applicable only to the bands with the necessary bandwidth.
>
>\- In case when frequency overlapping occurs due to the frequency channel selection defined for the test (i.e. Cell number as per Annex D), other frequency channels which avoid the frequency overlapping shall be selected. If no suitable selection is found the test is not applicable for the affected band.
>
### 3A.1.1   Test coverage across 5G NR connectivity options
The test cases in this specification cover both NR/5GC (including FR1+ FR2 CA or FR1+FR2 NR-DC) as well as EN-DC and NGEN-DC testing. Below shall be the understanding with respect to coverage across 5G NR connectivity options:
@@ -1588,6 +1587,20 @@ Message contents are according to TS 38.508-1 \[14\] clause 7.3 with the followi
Table 4.3.2.2.1.5-1 defines the primary level settings for contention based random access test in FR1 for PSCell in EN-DC. Table 4.3.2.2.1.5-2, Table 4.3.2.2.1.5-3 and Table 4.3.2.2.1.5-4 define the Absolute power limits, Relative power limits and uplink timing error limits respectively, and all include test tolerances.
Equations can be entered using the Latex language. A basic overview for Latex math can be found [here](https://www.cmor-faculty.rice.edu/~heinken/latex/symbols.pdf). Ideally, the equations should use the bare minimum set of required features as to avoid complexity. Inline equations are wrapped with \$ and \$, and must be defined entirely on a single line.
The below example how Es/Iot is handled as equations in Table 4.3.2.2.1.5-1: General test parameters.
Simple tables without merged cells are directly supported by Markdown. In the example below, which is identical except for the lack of merged cells, a three column table is written using *pipe tables*. Alignment is not required between columns, and all columns, even empty ones, must be included.
The number of dashes, or *-* characters, indicate the proportion of the page width the column should use in relation to the other columns. For example, `|-|---|` would result in one cell with 25% of the width of the table, and another with 75% of the width of the table. An example of such a table is shown below.
| 25% | 75% |
|-|---|
|Small Column| Long column with more text |
Alignment is possible on a per-column basis using the following options. The alignment syntax is shown in the following table.<br/>
| Alignment | Syntax |
|-|-|
| Left | `|:-|` |
| Right | `|-:|` |
| Center | `|:-:|` |
<br />
<div class="notable-source">
```
| Conditions | Tolerance |
|:----------:|:---------:|
| Normal | ± 19.1 dB |
```
</div>
</div>
<br />
| Conditions | Tolerance |
|:----------:|:---------:|
| Normal | ± 19.1 dB |
@@ -1834,8 +1878,41 @@ Table: **Table 4.3.2.2.1.5-3: Relative power tolerance Test requirements**
Tables with merged cells are not supported by most Markdown table formats. Those which support merged cells require manual formatting to align columns, which is too burdensom to be feasible. One alternative called List table for Pandoc helps write tables as list of cells and rows.
It supports merging of rows and columns, column/row alignments, row/cell attributes. More information can be found [here](https://github.com/pandoc-ext/list-table?) An example of such table is listed below.<br/>
<div class="notable-source">
```
:::{.list-table aligns=c,c,c,c}
**Table 4.3.2.2.1.5-4: T~e~ Timing error Test requirements**
* - **Frequency Range**
-**SCS of SSB signals (kHz)**
-**SCS of uplink signals (kHz)**
-**T~e~**
* - []{rowspan=2} 1
- 15
- 15
- 880\*T~c~
* - 30
- 30
- 624\*T~c~
* - []{colspan=4 align=l} NOTE: T~c~ is the basic timing unit defined in TS 38.211 \[7\]
:::
```
</div>
</div>
<br />
:::{.list-table aligns=c,c,c,c}
Table: **Table 4.3.2.2.1.5-4: T~e~ Timing error Test requirements**
**Table 4.3.2.2.1.5-4: T~e~ Timing error Test requirements**
